Opposition · USPTO

Opposition 91281970

OtherUSPTO

Opposition 91281970 at USPTO between Dell Inc. and Shenzhen Weishijie Technology Co., LTD, over the mark CISIDELL, filed Nov 23, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 23, 2022
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Dell Inc.

Company trademarks
Respondent

Shenzhen Weishijie Technology Co., LTD

Timeline

How the case has moved

Dates from the USPTO record and the CISIDELL filing.

  1. CISIDELL filed

    Application 97163717 filed at the USPTO.
  2. Opposition filed

    Dell Inc. started opposition 91281970 at USPTO against CISIDELL.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
CISIDELLContested97163717USPTO
DELLRelied on74021331USPTO
DELLRelied on74250269USPTO
DELLRelied on75453373USPTO
DELLRelied on78152472USPTO
DELLRelied on78234058USPTO
DELLRelied on78717252USPTO
DELLRelied on79212728USPTO
DELL TECHNOLOGIESRelied on79212993USPTO
DELL SAFESCREENRelied on88361186USPTO
DELL SAFEDATARelied on88361198USPTO
DELL SAFEIDRelied on88361204USPTO

+3 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_c316fff3-16bd-4ff2-95fb-6bdfb33ac1ee
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c316fff3-16bd-4ff2-95fb-6bdfb33ac1ee",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91281970",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-11-23",
  "parties": [
    {
      "name": "Dell Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Weishijie Technology Co., LTD",
      "role": "respondent"
    }
  ]
}