Opposition · USPTO

Opposition 91254618

OtherUSPTO

Opposition 91254618 at USPTO between UMG Recordings, Inc. and Mo Hitz LLC, over the mark M MO' HITZ, filed Mar 11, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 11, 2020
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

UMG Recordings, Inc.

Company trademarks
Respondent

Mo Hitz LLC

Timeline

How the case has moved

Dates from the USPTO record and the M MO' HITZ filing.

  1. M MO' HITZ filed

    Application 88498582 filed at the USPTO.
  2. Opposition filed

    UMG Recordings, Inc. started opposition 91254618 at USPTO against M MO' HITZ.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
M MO' HITZContested88498582USPTO
MOTOWNRelied on72281609USPTO
MOTOWNRelied on72427385USPTO
M MOTOWNRelied on73095605USPTO
MOTOWNRelied on75866346USPTO
MOTOWNRelied on77045567USPTO
MOTOWNRelied on77193039USPTO
MOTOWNRelied on77784098USPTO
MOTOWNRelied on77784105USPTO
MOTOWN DETROIT PONTIAC ANN ARBOR FT. WAYNE ERIERelied on86459769USPTO
MOTOWNRelied on86496738USPTO
MOTOWNRelied on87024125USPTO

+5 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 /v1/proceedings/{id}
ID=prc_6dedba26-7112-4538-b454-96d3a557c94b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6dedba26-7112-4538-b454-96d3a557c94b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254618",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-03-11",
  "parties": [
    {
      "name": "UMG Recordings, Inc.",
      "role": "opponent"
    },
    {
      "name": "Mo Hitz LLC",
      "role": "respondent"
    }
  ]
}