Opposition · USPTO

Opposition 91299932

PendingUSPTO

Opposition 91299932 at USPTO between BMC Software, Inc. and Simply Nuc, Inc., over the mark BMC-ENABLED EXTREMEEDGE SERVER, filed Jun 25, 2025. Status in the office record: pending.

View BMC-ENABLED EXTREMEEDGE SERVERGet this data via the API
Status
Pending
Filed
Jun 25, 2025
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

BMC Software, Inc.

Respondent

Simply Nuc, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the BMC-ENABLED EXTREMEEDGE SERVER filing.

  1. BMC-ENABLED EXTREMEEDGE SERVER filed

    Application 98498130 filed at the USPTO.

  2. Opposition filed

    BMC Software, Inc. started opposition 91299932 at USPTO against BMC-ENABLED EXTREMEEDGE SERVER.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
BMC-ENABLED EXTREMEEDGE SERVERContested98498130USPTO
BMC SOFTWARERelied on74724420USPTO
BMC SOFTWARERelied on75716094USPTO
BMCRelied on76250242USPTO
BMCRelied on86441351USPTO
BMCRelied on86441362USPTO
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_4199bbfb-1261-423b-9778-6c753abe8d88
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4199bbfb-1261-423b-9778-6c753abe8d88",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299932",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-06-25",
  "parties": [
    {
      "name": "BMC Software, Inc.",
      "role": "opponent"
    },
    {
      "name": "Simply Nuc, Inc.",
      "role": "respondent"
    }
  ]
}