Opposition · USPTO

Opposition 91264808

OtherUSPTO

Opposition 91264808 at USPTO between Gucci America, Inc. and Xiamen Yajiehang Network Technology Co.,Ltd., over the mark GUCITE, filed Sep 16, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 16, 2020
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Gucci America, Inc.

Respondent

Xiamen Yajiehang Network Technology Co.,Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the GUCITE filing.

  1. GUCITE filed

    Application 88848164 filed at the USPTO.
  2. Opposition filed

    Gucci America, Inc. started opposition 91264808 at USPTO against GUCITE.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
GUCITEContested88848164USPTO
GUCCIRelied on72300192USPTO
GUCCIRelied on72421386USPTO
GUCCIRelied on73129001USPTO
GUCCIRelied on73201929USPTO
GUCCIRelied on73219348USPTO
GUCCIRelied on73219350USPTO
GUCCIRelied on73270300USPTO
GUCCIRelied on85471661USPTO
GUCCIRelied on85894344USPTO
GUCCIRelied on86104604USPTO
GUCCIRelied on86104635USPTO

+7 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_b453ebb0-fa9f-4cc5-a1f5-421a821f4a43
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b453ebb0-fa9f-4cc5-a1f5-421a821f4a43",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264808",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-09-16",
  "parties": [
    {
      "name": "Gucci America, Inc.",
      "role": "opponent"
    },
    {
      "name": "Xiamen Yajiehang Network Technology Co.,Ltd.",
      "role": "respondent"
    }
  ]
}