Opposition · USPTO

Opposition 91245451

OtherUSPTO

Opposition 91245451 at USPTO between Deutsche Telekom AG and T Suite LLC, over the mark T-SUITE, filed Dec 21, 2018. Status in the office record: other.

View T-SUITEGet this data via the API
Status
Other
Result
Other
Filed
Dec 21, 2018
Marks involved
41
Parties

Who is involved

The parties as named in the office record.

Opponent

Deutsche Telekom AG

Company trademarks
Respondent

T Suite LLC

Timeline

How the case has moved

Dates from the USPTO record and the T-SUITE filing.

  1. T-SUITE filed

    Application 87543612 filed at the USPTO.

  2. Opposition filed

    Deutsche Telekom AG started opposition 91245451 at USPTO against T-SUITE.
Marks

Marks involved

1 contested mark, 40 marks the challenger relies on.

MarkRoleApplicationOffice
T-SUITEContested87543612USPTO
TRelied on74720652USPTO
TRelied on74720656USPTO
T-MOBILERelied on75093051USPTO
T-SYSTEMRelied on75093059USPTO
T MOBILERelied on75095186USPTO
T-MOBILERelied on75248963USPTO
T-MOBILERelied on75248964USPTO
T-SYSTEMSRelied on76166309USPTO
TRelied on76252927USPTO
T-MOBILE USARelied on76350166USPTO
TRelied on77307271USPTO

+29 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_da51ac05-d728-4e4a-b679-d9ce89ef7a9e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_da51ac05-d728-4e4a-b679-d9ce89ef7a9e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91245451",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-12-21",
  "parties": [
    {
      "name": "Deutsche Telekom AG",
      "role": "opponent"
    },
    {
      "name": "T Suite LLC",
      "role": "respondent"
    }
  ]
}