Opposition · USPTO

Opposition 91236714

OtherUSPTO

Opposition 91236714 at USPTO between Sony Corporation and Rotks Inc, Rotks, Inc., over the mark SONIFORCE, filed Sep 18, 2017. Status in the office record: other.

View SONIFORCEGet this data via the API
Status
Other
Result
Other
Filed
Sep 18, 2017
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

Sony Corporation

Respondent

Rotks Inc, Rotks, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the SONIFORCE filing.

  1. SONIFORCE filed

    Application 87110621 filed at the USPTO.

  2. Opposition filed

    Sony Corporation started opposition 91236714 at USPTO against SONIFORCE.
Marks

Marks involved

2 contested marks, 22 marks the challenger relies on.

MarkRoleApplicationOffice
SONIFORCEContested87110621USPTO
SONIFORCEContested87275284USPTO
SONYRelied on72171393USPTO
SONYRelied on72171578USPTO
SONYRelied on72171579USPTO
SONYRelied on72204017USPTO
SONYRelied on72304825USPTO
SONYRelied on72304827USPTO
SONYRelied on72304828USPTO
SONYRelied on72304830USPTO
SONYRelied on72304832USPTO
SONYRelied on73301025USPTO

+12 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_509bd720-5ece-4d75-9841-4d34deb1dd18
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_509bd720-5ece-4d75-9841-4d34deb1dd18",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91236714",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-09-18",
  "parties": [
    {
      "name": "Sony Corporation",
      "role": "opponent"
    },
    {
      "name": "Rotks Inc, Rotks, Inc.",
      "role": "respondent"
    }
  ]
}