Opposition · USPTO

Opposition 91272934

OtherUSPTO

Opposition 91272934 at USPTO between Apple Inc. and Shenzhen Kaijingda Technology Ltd., over the mark TONEMAC, filed Nov 15, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 15, 2021
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Shenzhen Kaijingda Technology Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the TONEMAC filing.

  1. TONEMAC filed

    Application 90562505 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91272934 at USPTO against TONEMAC.
Marks

Marks involved

1 contested mark, 23 marks the challenger relies on.

MarkRoleApplicationOffice
TONEMACContested90562505USPTO
MACRelied on74357318USPTO
IMACRelied on74366045USPTO
MAC OSRelied on74547403USPTO
MACRelied on74802249USPTO
IMACRelied on75476800USPTO
IMACRelied on76070198USPTO
BACK TO MY MACRelied on77338132USPTO
MACBOOK AIRRelied on77371650USPTO
MACINTOSHRelied on77532612USPTO
MACBOOKRelied on78821058USPTO
MAC PRORelied on78885695USPTO

+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 /v1/proceedings/{id}
ID=prc_1c1cdb10-44f3-46bc-9b04-4b6e187748c8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1c1cdb10-44f3-46bc-9b04-4b6e187748c8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91272934",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-11-15",
  "parties": [
    {
      "name": "APPLE INC.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Kaijingda Technology Ltd.",
      "role": "respondent"
    }
  ]
}