Opposition · USPTO

Opposition 91178284

OtherUSPTO

Opposition 91178284 at USPTO between lenovo (Singapore) Pte. Ltd and Thomas L. Pierce, over the mark THINKBLADE, filed Jul 9, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 9, 2007
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

lenovo (Singapore) Pte. Ltd

Respondent

Thomas L. Pierce

Timeline

How the case has moved

Dates from the USPTO record and the THINKBLADE filing.

  1. THINKBLADE filed

    Application 78895294 filed at the USPTO.
  2. Opposition filed

    lenovo (Singapore) Pte. Ltd started opposition 91178284 at USPTO against THINKBLADE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
THINKBLADEContested78895294USPTO
THINK PADRelied on74074338USPTO
THINKPADRelied on74526170USPTO
THINKPADRelied on75248281USPTO
THINKSTATIONRelied on75662613USPTO
THINKSTATIONRelied on75662614USPTO
THINKLIGHTRelied on75797819USPTO
THINKSCRIBERelied on76227482USPTO
THINKCENTRERelied on78157926USPTO
THINKVANTAGERelied on78157927USPTO
THINKVISIONRelied on78193728USPTO
THINKCENTRERelied on78975083USPTO
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_b6337a4f-7c25-464f-b8d7-4092ade66e31
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b6337a4f-7c25-464f-b8d7-4092ade66e31",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91178284",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-07-09",
  "parties": [
    {
      "name": "lenovo (Singapore) Pte. Ltd",
      "role": "opponent"
    },
    {
      "name": "Thomas L. Pierce",
      "role": "respondent"
    }
  ]
}