Opposition · USPTO

Opposition 91265682

OtherUSPTO

Opposition 91265682 at USPTO between Sony Corporation and Mettler Electronics Corporation, over the mark SONI TOOL, filed Oct 28, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 28, 2020
Marks involved
26
Parties

Who is involved

The parties as named in the office record.

Opponent

Sony Corporation

Respondent

Mettler Electronics Corporation

Timeline

How the case has moved

Dates from the USPTO record and the SONI TOOL filing.

  1. SONI TOOL filed

    Application 88811816 filed at the USPTO.
  2. Opposition filed

    Sony Corporation started opposition 91265682 at USPTO against SONI TOOL.
Marks

Marks involved

1 contested mark, 25 marks the challenger relies on.

MarkRoleApplicationOffice
SONI TOOLContested88811816USPTO
SONYRelied on72171393USPTO
SONYRelied on72171578USPTO
SONYRelied on72204017USPTO
SONYRelied on72304830USPTO
SONYRelied on73301025USPTO
SONYRelied on73399964USPTO
SONYRelied on73755377USPTO
SONY CLASSICALRelied on74024541USPTO
SONY CLASSICALRelied on74210396USPTO
SONY PICTURES CLASSICSRelied on74250870USPTO
SONYRelied on74414069USPTO

+14 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_db6a53dc-91c8-436e-b116-6ad4e4bf3a99
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_db6a53dc-91c8-436e-b116-6ad4e4bf3a99",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91265682",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-10-28",
  "parties": [
    {
      "name": "Sony Corporation",
      "role": "opponent"
    },
    {
      "name": "Mettler Electronics Corporation",
      "role": "respondent"
    }
  ]
}