Opposition · USPTO

Opposition 91216802

OtherUSPTO

Opposition 91216802 at USPTO between Deutsche Telekom AG and Taratech Enterprise Inc., over the mark T T, filed Jun 11, 2014. Status in the office record: other.

View T TGet this data via the API
Status
Other
Result
Other
Filed
Jun 11, 2014
Marks involved
31
Parties

Who is involved

The parties as named in the office record.

Opponent

Deutsche Telekom AG

Company trademarks
Respondent

Taratech Enterprise Inc.

Timeline

How the case has moved

Dates from the USPTO record and the T T filing.

  1. T T filed

    Application 85817039 filed at the USPTO.

  2. Opposition filed

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

Marks involved

1 contested mark, 30 marks the challenger relies on.

MarkRoleApplicationOffice
T TContested85817039USPTO
TRelied on74720652USPTO
TRelied on74720656USPTO
T-MOBILERelied on75093051USPTO
T SYSTEMRelied on75095185USPTO
T MOBILERelied on75095186USPTO
TRelied on76252927USPTO
REAL ICTRelied on77224896USPTO
REAL ICTRelied on77224897USPTO
TRelied on77307271USPTO
TRelied on77307277USPTO
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_126ffa15-be17-4774-b493-7ecf77def696
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_126ffa15-be17-4774-b493-7ecf77def696",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91216802",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-06-11",
  "parties": [
    {
      "name": "Deutsche Telekom AG",
      "role": "opponent"
    },
    {
      "name": "Taratech Enterprise Inc.",
      "role": "respondent"
    }
  ]
}