Opposition · USPTO

Opposition 91302037

OtherUSPTO

Opposition 91302037 at USPTO between Apple Inc. and Jianfeng Xie, over the mark AMPLECARE, filed Sep 29, 2025. Status in the office record: other.

View AMPLECAREGet this data via the API
Status
Other
Result
Other
Filed
Sep 29, 2025
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Respondent

Jianfeng Xie

Timeline

How the case has moved

Dates from the USPTO record and the AMPLECARE filing.

  1. AMPLECARE filed

    Application 98638052 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91302037 at USPTO against AMPLECARE.
Marks

Marks involved

2 contested marks, 16 marks the challenger relies on.

MarkRoleApplicationOffice
AMPLECAREContested98638052USPTO
AMPPLECAREContested98638171USPTO
APPLECARERelied on73425447USPTO
APPLE STORERelied on76400649USPTO
APPLECARERelied on77499807USPTO
APPLECARERelied on77499829USPTO
APPLECARERelied on77499837USPTO
APPLECARERelied on77499847USPTO
[Design mark]Relied on78155188USPTO
APPLERelied on78170383USPTO
[Design mark]Relied on78943482USPTO
APPLE NEWSRelied on86819744USPTO

+6 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_d90caf81-3a2d-438d-841e-77ea509e60fb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d90caf81-3a2d-438d-841e-77ea509e60fb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302037",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-09-29",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Jianfeng Xie",
      "role": "respondent"
    }
  ]
}