Opposition · USPTO

Opposition 91270636

OtherUSPTO

Opposition 91270636 at USPTO between Beats Electronics, LLC and Cui Guangquan, over the mark BEATLONE, filed Jul 22, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 22, 2021
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

Beats Electronics, LLC

Company trademarks
Respondent

Cui Guangquan

Timeline

How the case has moved

Dates from the USPTO record and the BEATLONE filing.

  1. BEATLONE filed

    Application 90212637 filed at the USPTO.
  2. Opposition filed

    Beats Electronics, LLC started opposition 91270636 at USPTO against BEATLONE.
Marks

Marks involved

1 contested mark, 22 marks the challenger relies on.

MarkRoleApplicationOffice
BEATLONEContested90212637USPTO
BEATSRelied on77664171USPTO
BEATS BY DR. DRERelied on77786492USPTO
BEATSRelied on77786522USPTO
BEATSRelied on77980257USPTO
BEATSRelied on77982434USPTO
BEATS BY DR. DRERelied on77983185USPTO
BEATSRelied on77983303USPTO
BEATS BY DR. DRERelied on77983608USPTO
BEATS STUDIORelied on85554241USPTO
BEATS PRORelied on85976944USPTO
URBEATSRelied on85978526USPTO

+11 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_ec72f069-a398-437a-8f84-7c212806690d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ec72f069-a398-437a-8f84-7c212806690d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91270636",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-07-22",
  "parties": [
    {
      "name": "Beats Electronics, LLC",
      "role": "opponent"
    },
    {
      "name": "Cui Guangquan",
      "role": "respondent"
    }
  ]
}