Opposition · USPTO

Opposition 91251358

OtherUSPTO

Opposition 91251358 at USPTO between ARM Limited and Beijing Orion Star Technology Co., Ltd., over the mark ARMOS, filed Oct 2, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 2, 2019
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

ARM Limited

Company trademarks
Respondent

Beijing Orion Star Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ARMOS filing.

  1. ARMOS filed

    Application 88156545 filed at the USPTO.
  2. Opposition filed

    ARM Limited started opposition 91251358 at USPTO against ARMOS.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
ARMOSContested88156545USPTO
ARM7TDMIRelied on75713153USPTO
ARMRelied on75713155USPTO
ARMRelied on75713156USPTO
ARMRelied on75713165USPTO
ARM POWEREDRelied on75750700USPTO
ARM POWEREDRelied on75750721USPTO
ARM7TDMIRelied on75750726USPTO
ARM POWEREDRelied on76139898USPTO
ARM POWEREDRelied on76298758USPTO
ARM CONNECTEDRelied on77542728USPTO
ARM7TDMIRelied on86390868USPTO

+4 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_1cbe756a-63a5-4e56-9aec-a8bc751044f6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1cbe756a-63a5-4e56-9aec-a8bc751044f6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91251358",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-10-02",
  "parties": [
    {
      "name": "ARM Limited",
      "role": "opponent"
    },
    {
      "name": "Beijing Orion Star Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}