Cancellation · USPTO

Cancellation 92077539

OtherUSPTO

Cancellation 92077539 at USPTO between Apple Inc. and Amer Group, Inc. and Banker of Mobi, Inc., over the mark AIPHONE, filed Jul 8, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 8, 2021
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Petitioner

Apple Inc.

Company trademarks
Respondent

Amer Group, Inc. and Banker of Mobi, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the AIPHONE filing.

  1. AIPHONE filed

    Application 87195054 filed at the USPTO.
  2. AIPHONE registered

  3. Cancellation filed

    Apple Inc. started cancellation 92077539 at USPTO against AIPHONE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
AIPHONEContested87195054USPTO
IPHONERelied on77007808USPTO
IPHONERelied on77078484USPTO
IPHONERelied on77078485USPTO
IPHONERelied on77078490USPTO
IPHONERelied on77078493USPTO
IPHONERelied on77078496USPTO
IPHONERelied on77353055USPTO
IPHONERelied on77975076USPTO
IPHONERelied on77976400USPTO
IPHONERelied on77977745USPTO
IPHONERelied on86501899USPTO
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_c431ee8b-d160-4e88-a172-a9cca4e6ae30
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c431ee8b-d160-4e88-a172-a9cca4e6ae30",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92077539",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-07-08",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "petitioner"
    },
    {
      "name": "Amer Group, Inc. and Banker of Mobi, Inc.",
      "role": "respondent"
    }
  ]
}