Cancellation 92057732
OtherUSPTO
Cancellation 92057732 at USPTO between Quantum Corporation and Cisco Technology, Inc., over the mark QUANTUM NETWORK SUITE, filed Dec 3, 2014. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Dec 3, 2014
- Marks involved
- 10
Parties
Who is involved
The parties as named in the office record.
Respondent
Cisco Technology, Inc.
Timeline
How the case has moved
Dates from the USPTO record and the QUANTUM NETWORK SUITE filing.
QUANTUM NETWORK SUITE filed
Application 77929560 filed at the USPTO.QUANTUM NETWORK SUITE registered
Cancellation filed
Quantum Corporation started cancellation 92057732 at USPTO against QUANTUM NETWORK SUITE.
Marks
Marks involved
1 contested mark, 9 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| QUANTUM NETWORK SUITE | Contested | 77929560 | USPTO |
| QUANTUM | Relied on | 72327773 | USPTO |
| QUANTUM | Relied on | 73127739 | USPTO |
| QUANTUM | Relied on | 74242149 | USPTO |
| QUANTUM | Relied on | 75052261 | USPTO |
| QUANTUM | Relied on | 75387699 | USPTO |
| QUANTUM | Relied on | 75552214 | USPTO |
| QUANTUM | Relied on | 75601999 | USPTO |
| QUANTUM | Relied on | 75604153 | USPTO |
| QUANTUM | Relied on | 75608837 | USPTO |
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_a0138684-6383-4d9f-8f04-4f249747b08b
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_a0138684-6383-4d9f-8f04-4f249747b08b",
"object": "proceeding",
"proceeding_type": "cancellation",
"proceeding_number": "92057732",
"status": "other",
"office_code": "US",
"filed_date": "2014-12-03",
"parties": [
{
"name": "Quantum Corporation",
"role": "petitioner"
},
{
"name": "Cisco Technology, Inc.",
"role": "respondent"
}
]
}