Opposition · USPTO

Opposition 91248618

OtherUSPTO

Opposition 91248618 at USPTO between Vans, Inc. and Shenzhen Junning Network Technology Co., Ltd, over the mark VANLANO, filed Jun 5, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 5, 2019
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

Vans, Inc.

Company trademarks
Respondent

Shenzhen Junning Network Technology Co., Ltd

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the VANLANO filing.

  1. VANLANO filed

    Application 88270412 filed at the USPTO.
  2. Opposition filed

    Vans, Inc. started opposition 91248618 at USPTO against VANLANO.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

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

+24 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_03e265a6-964b-454b-a8d2-30ce8126ebed
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_03e265a6-964b-454b-a8d2-30ce8126ebed",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91248618",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-06-05",
  "parties": [
    {
      "name": "Vans, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Junning Network Technology Co., Ltd",
      "role": "respondent"
    }
  ]
}