Opposition · USPTO

Opposition 91294220

OtherUSPTO

Opposition 91294220 at USPTO between Sony Group Corporation and Lichun Zhang, over the mark GEWISSONY, filed Sep 26, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 26, 2024
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Sony Group Corporation

Company trademarks
Respondent

Lichun Zhang

Timeline

How the case has moved

Dates from the USPTO record and the GEWISSONY filing.

  1. GEWISSONY filed

    Application 98173514 filed at the USPTO.
  2. Opposition filed

    Sony Group Corporation started opposition 91294220 at USPTO against GEWISSONY.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
GEWISSONYContested98173514USPTO
SONYRelied on72171579USPTO
SONYRelied on72204017USPTO
SONYRelied on73755377USPTO
SDDS SONY DYNAMIC DIGITAL SOUNDRelied on74505016USPTO
SONY CLASSICALRelied on76340494USPTO
SONY PICTURESRelied on76620492USPTO
SONYRelied on77030850USPTO
SONY MUSICRelied on77643937USPTO
SONY REWARDSRelied on85752085USPTO
SONYRelied on86978329USPTO
SONYRelied on87735737USPTO

+1 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_2f9cda11-88e7-4900-b4b1-399faa2bdd8c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2f9cda11-88e7-4900-b4b1-399faa2bdd8c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294220",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-09-26",
  "parties": [
    {
      "name": "Sony Group Corporation",
      "role": "opponent"
    },
    {
      "name": "Lichun Zhang",
      "role": "respondent"
    }
  ]
}