Opposition · USPTO

Opposition 91276794

OtherUSPTO

Opposition 91276794 at USPTO between Apple Inc. and Shenzhen Arington Technology Co.,Ltd., over the mark SPORTSPODS, filed Jun 15, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 15, 2022
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Shenzhen Arington Technology Co.,Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the SPORTSPODS filing.

  1. SPORTSPODS filed

    Application 90856421 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91276794 at USPTO against SPORTSPODS.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
SPORTSPODSContested90856421USPTO
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_19ef91cd-cec1-4af7-865f-519a587f1ace
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_19ef91cd-cec1-4af7-865f-519a587f1ace",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91276794",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-06-15",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Arington Technology Co.,Ltd.",
      "role": "respondent"
    }
  ]
}