Opposition · USPTO

Opposition 91290580

OtherUSPTO

Opposition 91290580 at USPTO between STMicroelectronics International, N.V. and NTE Holdings S.R.L., over the mark STM MICROTEC, filed Mar 22, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 22, 2024
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

STMicroelectronics International, N.V.

Company trademarks
Respondent

NTE Holdings S.R.L.

Timeline

How the case has moved

Dates from the USPTO record and the STM MICROTEC filing.

  1. STM MICROTEC filed

    Application 79339792 filed at the USPTO.
  2. Opposition filed

    STMicroelectronics International, N.V. started opposition 91290580 at USPTO against STM MICROTEC.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
STM MICROTECContested79339792USPTO
STRelied on73688278USPTO
STRelied on75389355USPTO
STM8Relied on79055408USPTO
STMOD+Relied on79206114USPTO
ESTMRelied on79260117USPTO
STM32TRUSTRelied on79290470USPTO
STM32 ZESTRelied on79329700USPTO
STM32CUBERelied on79360454USPTO
STRelied on85008787USPTO
STRelied on85522548USPTO
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_bc1b9381-03f1-4976-a2ab-557ed7aea345
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bc1b9381-03f1-4976-a2ab-557ed7aea345",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91290580",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-03-22",
  "parties": [
    {
      "name": "STMicroelectronics International, N.V.",
      "role": "opponent"
    },
    {
      "name": "NTE Holdings S.R.L.",
      "role": "respondent"
    }
  ]
}