Opposition · USPTO

Opposition 91285741

OtherUSPTO

Opposition 91285741 at USPTO between Caterpillar Inc. and Virtual Power Systems, Inc., over the mark CATO, filed Jun 27, 2023. Status in the office record: other.

View CATOGet this data via the API
Status
Other
Result
Other
Filed
Jun 27, 2023
Marks involved
52
Parties

Who is involved

The parties as named in the office record.

Opponent

Caterpillar Inc.

Company trademarks
Respondent

Virtual Power Systems, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the CATO filing.

  1. CATO filed

    Application 97363391 filed at the USPTO.

  2. Opposition filed

    Caterpillar Inc. started opposition 91285741 at USPTO against CATO.
Marks

Marks involved

3 contested marks, 49 marks the challenger relies on.

MarkRoleApplicationOffice
CATOContested97363391USPTO
CATO DIGITALContested97363401USPTO
CATO AIContested97363414USPTO
CATRelied on71575190USPTO
CATRelied on72137716USPTO
CATRelied on72164427USPTO
CATRelied on72174081USPTO
CATRelied on72181522USPTO
CATRelied on72299526USPTO
CATRelied on72452924USPTO
CATRelied on73001719USPTO
CATRelied on73392831USPTO

+40 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_3d14aa07-7ac1-4437-b119-2fd8b1a78c4a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3d14aa07-7ac1-4437-b119-2fd8b1a78c4a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91285741",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-06-27",
  "parties": [
    {
      "name": "Caterpillar Inc.",
      "role": "opponent"
    },
    {
      "name": "Virtual Power Systems, Inc.",
      "role": "respondent"
    }
  ]
}