Opposition · USPTO

Opposition 91283577

OtherUSPTO

Opposition 91283577 at USPTO between Apple Inc. and Siping Zhonglian Technology Co., Ltd., over the mark SPORKPODS, filed Feb 22, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 22, 2023
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Siping Zhonglian Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the SPORKPODS filing.

  1. SPORKPODS filed

    Application 97294008 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91283577 at USPTO against SPORKPODS.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
SPORKPODSContested97294008USPTO
IPODRelied on75982871USPTO
IPODRelied on77013000USPTO
IPODRelied on78089144USPTO
IPODRelied on78653661USPTO
EARPODSRelied on85724049USPTO
EARPODSRelied on85743152USPTO
AIRPODSRelied on86764566USPTO
HOMEPODRelied on87486392USPTO
HOMEPODRelied on87486450USPTO
AIRPODS PRORelied on88676261USPTO
AIRPODS PRORelied on88831036USPTO

+2 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_c48aa0e3-dd4f-4192-b34b-6a21ce4cd52b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c48aa0e3-dd4f-4192-b34b-6a21ce4cd52b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283577",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-02-22",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Siping Zhonglian Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}