Opposition · USPTO

Opposition 91222328

OtherUSPTO

Opposition 91222328 at USPTO between Apple Inc. and Shenzhen Ecapple Technology Co., Ltd, over the mark ECAPPLE, filed Jun 10, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 10, 2015
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Shenzhen Ecapple Technology Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the ECAPPLE filing.

  1. ECAPPLE filed

    Application 86396928 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91222328 at USPTO against ECAPPLE.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
ECAPPLEContested86396928USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
APPLE STORERelied on77388365USPTO
APPLECARERelied on77499797USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78156920USPTO
APPLE LIGHTNINGRelied on85726560USPTO
DESIGNED BY APPLE IN CALIFORNIARelied on86096239USPTO
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_c1210e03-9dcc-425f-9856-62d3dc1f619b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c1210e03-9dcc-425f-9856-62d3dc1f619b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91222328",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-06-10",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Ecapple Technology Co., Ltd",
      "role": "respondent"
    }
  ]
}