Opposition 91244364
OtherUSPTO
Opposition 91244364 at USPTO between Intel Corporation and ExosomeLife LLC, over the mark EXOINTEL, filed Oct 24, 2018. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Oct 24, 2018
- Marks involved
- 34
Parties
Who is involved
The parties as named in the office record.
Opponent
Intel Corporation
Respondent
ExosomeLife LLC
Timeline
How the case has moved
Dates from the USPTO record and the EXOINTEL filing.
EXOINTEL filed
Application 87819575 filed at the USPTO.Opposition filed
Intel Corporation started opposition 91244364 at USPTO against EXOINTEL.
Marks
Marks involved
1 contested mark, 33 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| EXOINTEL | Contested | 87819575 | USPTO |
| INTEL | Relied on | 72384319 | USPTO |
| INTEL | Relied on | 72384320 | USPTO |
| INTEL | Relied on | 73035122 | USPTO |
| INTEL INSIDE | Relied on | 74159673 | USPTO |
| INTEL | Relied on | 74225506 | USPTO |
| INTEL | Relied on | 74225623 | USPTO |
| INTEL INSIDE | Relied on | 75160103 | USPTO |
| INTEL | Relied on | 75160105 | USPTO |
| INTEL | Relied on | 75160106 | USPTO |
| INTEL | Relied on | 75163576 | USPTO |
| INTEL | Relied on | 75349837 | USPTO |
+22 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_9fdf24d9-a256-4df8-8d4c-4eaa87d05bd4
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_9fdf24d9-a256-4df8-8d4c-4eaa87d05bd4",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91244364",
"status": "other",
"office_code": "US",
"filed_date": "2018-10-24",
"parties": [
{
"name": "Intel Corporation",
"role": "opponent"
},
{
"name": "ExosomeLife LLC",
"role": "respondent"
}
]
}