Opposition · USPTO

Opposition 91283104

OtherUSPTO

Opposition 91283104 at USPTO between Deutsche Telekom AG and Secureworks Corp., over the mark T, filed Jan 30, 2023. Status in the office record: other.

View TGet this data via the API
Status
Other
Result
Other
Filed
Jan 30, 2023
Marks involved
31
Parties

Who is involved

The parties as named in the office record.

Opponent

Deutsche Telekom AG

Company trademarks
Respondent

Secureworks Corp.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the T filing.

  1. T filed

    Application 97014190 filed at the USPTO.

  2. Opposition filed

    Deutsche Telekom AG started opposition 91283104 at USPTO against T.
Marks

Marks involved

1 contested mark, 30 marks the challenger relies on.

MarkRoleApplicationOffice
TContested97014190USPTO
TRelied on74720652USPTO
TRelied on74720656USPTO
T-MOBILERelied on75093051USPTO
T-SYSTEMRelied on75093059USPTO
T MOBILERelied on75095186USPTO
T-MOBILERelied on75248964USPTO
T-SYSTEMSRelied on76166309USPTO
TRelied on76252927USPTO
T-MOBILE USARelied on76350166USPTO
TRelied on77307279USPTO
T MOBILERelied on77311132USPTO

+19 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_8fe38d02-f961-46f0-a1f1-f561825b913e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8fe38d02-f961-46f0-a1f1-f561825b913e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283104",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-01-30",
  "parties": [
    {
      "name": "Deutsche Telekom AG",
      "role": "opponent"
    },
    {
      "name": "Secureworks Corp.",
      "role": "respondent"
    }
  ]
}