Opposition · USPTO

Opposition 91275006

OtherUSPTO

Opposition 91275006 at USPTO between Best Buy Health, Inc. and Nomo International, LLC, over the mark LIVESURELY, filed Mar 11, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 11, 2022
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Best Buy Health, Inc.

Respondent

Nomo International, LLC

Timeline

How the case has moved

Dates from the USPTO record and the LIVESURELY filing.

  1. LIVESURELY filed

    Application 90620705 filed at the USPTO.
  2. Opposition filed

    Best Buy Health, Inc. started opposition 91275006 at USPTO against LIVESURELY.
Marks

Marks involved

5 contested marks, 8 marks the challenger relies on.

MarkRoleApplicationOffice
LIVESURELYContested90620705USPTO
LIVESURELYContested90620709USPTO
LIVESURELYContested90620716USPTO
LIVESURELYContested90623629USPTO
LIVESURELYContested90623646USPTO
LIVELYRelied on85742506USPTO
LIVELYRelied on88805699USPTO
LIVELYRelied on88882104USPTO
LIVELYRelied on88982868USPTO
LIVELYRelied on88982870USPTO
LIVELYRelied on90461192USPTO
LIVELYRelied on90461217USPTO

+1 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_cca4d554-7cb4-442c-b84f-40e57619aab2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_cca4d554-7cb4-442c-b84f-40e57619aab2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91275006",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-03-11",
  "parties": [
    {
      "name": "Best Buy Health, Inc.",
      "role": "opponent"
    },
    {
      "name": "Nomo International, LLC",
      "role": "respondent"
    }
  ]
}