Opposition · USPTO

Opposition 91289378

OtherUSPTO

Opposition 91289378 at USPTO between Bose Corporation and Shenzhen Ahaha Technology Co., Ltd., over the mark KEBOSE, filed Jan 23, 2024. Status in the office record: other.

View KEBOSEGet this data via the API
Status
Other
Result
Other
Filed
Jan 23, 2024
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Bose Corporation

Company trademarks
Respondent

Shenzhen Ahaha Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the KEBOSE filing.

  1. KEBOSE filed

    Application 97791077 filed at the USPTO.

  2. Opposition filed

    Bose Corporation started opposition 91289378 at USPTO against KEBOSE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
KEBOSEContested97791077USPTO
BOSERelied on72255691USPTO
BOSERelied on72450949USPTO
BOSERelied on74112160USPTO
BOSERelied on74145597USPTO
BOSERelied on74408123USPTO
BOSERelied on74415018USPTO
BOSERelied on75573700USPTO
BOSERelied on77938552USPTO
BOSERelied on87619476USPTO
BOSERelied on87911358USPTO
BOSERelied on90242036USPTO
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_5c145ecc-1378-4d1d-adf3-ef0a6720d43d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5c145ecc-1378-4d1d-adf3-ef0a6720d43d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91289378",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-01-23",
  "parties": [
    {
      "name": "Bose Corporation",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Ahaha Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}