Opposition · USPTO

Opposition 91247189

OtherUSPTO

Opposition 91247189 at USPTO between Tessco Communications Incorporated and Prime Telecom, LLC, over the mark TESSO, filed Mar 26, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 26, 2019
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Tessco Communications Incorporated

Company trademarks
Respondent

Prime Telecom, LLC

Timeline

How the case has moved

Dates from the USPTO record and the TESSO filing.

  1. TESSO filed

    Application 88091384 filed at the USPTO.
  2. Opposition filed

    Tessco Communications Incorporated started opposition 91247189 at USPTO against TESSO.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
TESSOContested88091384USPTO
TESSCORelied on74127417USPTO
TESSCO TECHNOLOGIESRelied on74254117USPTO
TESSCO.COMRelied on75828363USPTO
TESSCORelied on76063991USPTO
TESSCORelied on76096752USPTO
TESSCO CONNECTRelied on86047572USPTO
TESSCO SOLUTION ARCHITECTURERelied on86512226USPTO
TESSCO FLEET VISIBILITYRelied on86801969USPTO
TESSCO FLEET MOBILITYRelied on86802016USPTO
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_6e72ff24-625c-4b72-b941-29521fe16039
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6e72ff24-625c-4b72-b941-29521fe16039",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91247189",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-03-26",
  "parties": [
    {
      "name": "Tessco Communications Incorporated",
      "role": "opponent"
    },
    {
      "name": "Prime Telecom, LLC",
      "role": "respondent"
    }
  ]
}