Opposition · USPTO

Opposition 91200140

OtherUSPTO

Opposition 91200140 at USPTO between Lenovo (Singapore) Pte. Ltd. and H. Co. Computer Products, over the mark THINK! NETWORKING PRODUCTS, filed Jun 6, 2011. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 6, 2011
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Lenovo (Singapore) Pte. Ltd.

Respondent

H. Co. Computer Products

Timeline

How the case has moved

Dates from the USPTO record and the THINK! NETWORKING PRODUCTS filing.

  1. THINK! NETWORKING PRODUCTS filed

    Application 77883626 filed at the USPTO.
  2. Opposition filed

    Lenovo (Singapore) Pte. Ltd. started opposition 91200140 at USPTO against THINK! NETWORKING PRODUCTS.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
THINK! NETWORKING PRODUCTSContested77883626USPTO
THINK PADRelied on74074338USPTO
THINKPADRelied on74526170USPTO
THINKPADRelied on75248281USPTO
THINKLIGHTRelied on75797819USPTO
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_7d8b3961-dc9a-4c63-a61b-c33d51fe6c21
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7d8b3961-dc9a-4c63-a61b-c33d51fe6c21",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91200140",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-06-06",
  "parties": [
    {
      "name": "Lenovo (Singapore) Pte. Ltd.",
      "role": "opponent"
    },
    {
      "name": "H. Co. Computer Products",
      "role": "respondent"
    }
  ]
}