Cancellation · USPTO

Cancellation 92068163

OtherUSPTO

Cancellation 92068163 at USPTO between Chanel, Inc. and Guan Jianghe, over the mark - COCOESSENCE -, filed Mar 21, 2018. Status in the office record: other.

View - COCOESSENCE -Get this data via the API
Status
Other
Result
Other
Filed
Mar 21, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Petitioner

Chanel, Inc.

Company trademarks
Respondent

Guan Jianghe

Timeline

How the case has moved

Dates from the USPTO record and the - COCOESSENCE - filing.

  1. - COCOESSENCE - filed

    Application 87551498 filed at the USPTO.

  2. - COCOESSENCE - registered

  3. Cancellation filed

    Chanel, Inc. started cancellation 92068163 at USPTO against - COCOESSENCE -.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
- COCOESSENCE -Contested87551498USPTO
COCORelied on72237534USPTO
COCORelied on73206836USPTO
COCO CHANELRelied on73535356USPTO
COCORelied on73653479USPTO
COCORelied on73818611USPTO
COCO MADEMOISELLERelied on76054884USPTO
ROUGE COCORelied on77768562USPTO
COCO NOIRRelied on85360730USPTO
COCO CODERelied on86925184USPTO
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_7b4deac4-f33e-4092-84b4-4b7b78c6607c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7b4deac4-f33e-4092-84b4-4b7b78c6607c",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92068163",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-03-21",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Guan Jianghe",
      "role": "respondent"
    }
  ]
}