Cancellation · USPTO

Cancellation 92056010

OtherUSPTO

Cancellation 92056010 at USPTO between Puma SE and Precision Transducer Systems, Inc., over the mark PUMA AUDIO, filed Aug 7, 2012. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 7, 2012
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Petitioner

Puma SE

Company trademarks
Respondent

Precision Transducer Systems, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the PUMA AUDIO filing.

  1. PUMA AUDIO filed

    Application 77264240 filed at the USPTO.
  2. PUMA AUDIO registered

  3. Cancellation filed

    Puma SE started cancellation 92056010 at USPTO against PUMA AUDIO.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
PUMA AUDIOContested77264240USPTO
PUMARelied on72205343USPTO
PUMARelied on72343354USPTO
PUMARelied on73037072USPTO
PUMARelied on73037100USPTO
PUMARelied on73086445USPTO
PUMARelied on73269046USPTO
PUMARelied on73269236USPTO
PUMARelied on73292656USPTO
PUMARelied on73293742USPTO
PUMARelied on73298231USPTO
PUMARelied on73453035USPTO

+4 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_a30aefd7-15c6-4295-9168-a7a8dc22a9ef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a30aefd7-15c6-4295-9168-a7a8dc22a9ef",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92056010",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-08-07",
  "parties": [
    {
      "name": "PUMA SE",
      "role": "petitioner"
    },
    {
      "name": "Precision Transducer Systems, Inc.",
      "role": "respondent"
    }
  ]
}