Opposition · USPTO

Opposition 91288328

OtherUSPTO

Opposition 91288328 at USPTO between Apple Inc. and 1.4G Holdings LLC, over the mark [Design Mark], filed Nov 20, 2023. Status in the office record: other.

View [Design Mark]Get this data via the API
Status
Other
Result
Other
Filed
Nov 20, 2023
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

1.4G Holdings LLC

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 97484635 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91288328 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested97484635USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLE STORERelied on75857151USPTO
THE APPLE STORERelied on75857191USPTO
APPLE STORERelied on76400649USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78155188USPTO
TODAY AT APPLERelied on87607171USPTO
PARKRelied on87809618USPTO
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_048f567c-42e2-4ce8-8711-018890f4803c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_048f567c-42e2-4ce8-8711-018890f4803c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91288328",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-11-20",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "1.4G Holdings LLC",
      "role": "respondent"
    }
  ]
}