Opposition · USPTO

Opposition 91269554

OtherUSPTO

Opposition 91269554 at USPTO between Vans, Inc. and Shenzhen Shengdatong Technology Development Co., Ltd., over the mark VANSSI, filed May 26, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
May 26, 2021
Marks involved
32
Parties

Who is involved

The parties as named in the office record.

Opponent

Vans, Inc.

Company trademarks
Respondent

Shenzhen Shengdatong Technology Development Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the VANSSI filing.

  1. VANSSI filed

    Application 90264444 filed at the USPTO.
  2. Opposition filed

    Vans, Inc. started opposition 91269554 at USPTO against VANSSI.
Marks

Marks involved

1 contested mark, 31 marks the challenger relies on.

MarkRoleApplicationOffice
VANSSIContested90264444USPTO
VANSRelied on73396311USPTO
VANSRelied on73396312USPTO
VANSRelied on73396323USPTO
VANSRelied on73399859USPTO
VANSRelied on73441417USPTO
VANSRelied on74239429USPTO
VANSRelied on74458715USPTO
VANSRelied on74458716USPTO
VANSRelied on75364137USPTO
VANSRelied on75505409USPTO
VANSRelied on77802906USPTO

+20 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_53a98d91-ab76-4125-a4b9-eda9e675dceb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_53a98d91-ab76-4125-a4b9-eda9e675dceb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91269554",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-05-26",
  "parties": [
    {
      "name": "Vans, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Shengdatong Technology Development Co., Ltd.",
      "role": "respondent"
    }
  ]
}