Opposition · USPTO

Opposition 91240836

OtherUSPTO

Opposition 91240836 at USPTO between General Electric Company and Jiaozi E-commerce (Shenzhen) Ltd., over the mark GEBOREN, filed Apr 18, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 18, 2018
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

General Electric Company

Company trademarks
Respondent

Jiaozi E-commerce (Shenzhen) Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the GEBOREN filing.

  1. GEBOREN filed

    Application 87510089 filed at the USPTO.
  2. Opposition filed

    General Electric Company started opposition 91240836 at USPTO against GEBOREN.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
GEBORENContested87510089USPTO
GERelied on70035089USPTO
GERelied on72396531USPTO
GERelied on72404063USPTO
GERelied on72455729USPTO
GERelied on72455733USPTO
GENERAL ELECTRIC GERelied on73036922USPTO
GERelied on73036924USPTO
GERelied on73071173USPTO
GERelied on73082141USPTO
GERelied on73102821USPTO
GERelied on73162520USPTO

+38 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_33748ac7-bd49-4771-85d2-8e5f953f5231
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_33748ac7-bd49-4771-85d2-8e5f953f5231",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91240836",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-04-18",
  "parties": [
    {
      "name": "General Electric Company",
      "role": "opponent"
    },
    {
      "name": "Jiaozi E-commerce (Shenzhen) Ltd.",
      "role": "respondent"
    }
  ]
}