Opposition · USPTO

Opposition 91272003

OtherUSPTO

Opposition 91272003 at USPTO between Wipro Limited and Wipro TradeMarks Holding Limited and ViscoTec Pumpen- u. Dosiertechnik GmbH, over the mark VIPRO, filed Sep 22, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 22, 2021
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Wipro Limited and Wipro TradeMarks Holding Limited

Respondent

ViscoTec Pumpen- u. Dosiertechnik GmbH

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the VIPRO filing.

  1. VIPRO filed

    Application 79253394 filed at the USPTO.
  2. Opposition filed

    Wipro Limited and Wipro TradeMarks Holding Limited started opposition 91272003 at USPTO against VIPRO.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
VIPROContested79253394USPTO
WIPRORelied on76005173USPTO
WIPRORelied on79048647USPTO
WIPRO HOLMES ARTIFICIAL INTELLIGENCE PLATFORMRelied on86657414USPTO
WIPRORelied on87389863USPTO
WIPRORelied on87419739USPTO
WIPRO HOLMESRelied on87580879USPTO
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_62d118b3-cccf-478c-bfba-24b041e3f5d7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_62d118b3-cccf-478c-bfba-24b041e3f5d7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91272003",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-09-22",
  "parties": [
    {
      "name": "Wipro Limited and Wipro TradeMarks Holding Limited",
      "role": "opponent"
    },
    {
      "name": "ViscoTec Pumpen- u. Dosiertechnik GmbH",
      "role": "respondent"
    }
  ]
}