IP Library Granted Patent US 12,411,788
Granted Patent B2
US 12,411,788 · App. 18/807,849 · Granted Sep 9, 2025

Chiplet system and method for communicating between chiplets in chiplet system

Inventors: Young-Jae Jin (Seongnam-si, KR); Chang-Hyo Yu (Seongnam-si, KR)
Assignee: REBELLIONS INC.
G06F13/4004G06F13/4282G06F15/7807G06F2213/40
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,411,788
App. No.
18/807,849
Granted
Sep 9, 2025
Kind
B2
Abstract

The present disclosure relates to a method for communicating between chiplets in a chiplet system. The chiplet system includes a first chiplet and a second chiplet, and the method includes, by the first chiplet, generating a die-to-die interface flit from a first protocol type transaction based on conversion information, by the first chiplet, transmitting the die-to-die interface flit to the second chiplet, and, by the second chiplet, generating a second protocol type transaction from the die-to-die interface flit based on the conversion information.

Claims (66)

1. A method for communicating between chiplets in a chiplet system, wherein the chiplet system includes a first chiplet and a second chiplet, the method comprising:

by the first chiplet, generating a die-to-die interface flit from a first protocol type transaction based on conversion information;

by the first chiplet, transmitting the die-to-die interface flit to the second chiplet; and

by the second chiplet, generating a second protocol type transaction from the die-to-die interface flit based on the conversion information,

wherein the conversion information includes information on a packet ID, a payload type code, a payload type size, and a payload size.

2. The method according to claim 1 , wherein

the first chiplet includes a controller including a protocol layer and an adapter layer, and

the generating by the first chiplet the die-to-die interface flit from the first protocol type transaction based on the conversion information includes:

by the protocol layer of the first chiplet, generating a payload of the die-to-die interface flit from the first protocol type transaction based on the conversion information;

by the adapter layer of the first chiplet, generating a header of the die-to-die interface flit; and

by the adapter layer of the first chiplet, generating the die-to-die interface flit by combining the header and the payload.

3. The method according to claim 1 , wherein

the first chiplet further includes a physical (PHY) layer, and

the transmitting by the first chiplet the die-to-die interface flit to the second chiplet includes:

by the adapter layer of the first chiplet, transmitting the die-to-die interface flit to the PHY layer of the first chiplet; and

by the PHY layer of the first chiplet, transmitting the die-to-die interface flit to the second chiplet.

4. The method according to claim 1 , before generating the die-to-die interface flit, further comprising, by the first chiplet and the second chiplet, exchanging the conversion information.

5. The method according to claim 1 , wherein the payload type code includes a write address code, a write data code, a write response code, a read address code, and a read data code.

6. The method according to claim 1 , wherein

the second chiplet includes a PHY layer, and

the transmitting by the first chiplet the die-to-die interface flit to the second chiplet includes, by the first chiplet, transmitting the die-to-die interface flit to the PHY layer of the second chiplet.

7. The method according to claim 1 , wherein

the second chiplet includes a controller including an adapter layer and a protocol layer, and

the generating by the second chiplet the second protocol type transaction from the die-to-die interface flit based on the conversion information includes:

by the adapter layer of the second chiplet, extracting a payload of the die-to-die interface flit from the flit; and

by the protocol layer of the second chiplet, generating the second protocol type transaction from the payload.

8. The method according to claim 1 , wherein

the first protocol relates to the first chiplet,

the second protocol relates to the second chiplet, and

the first protocol and the second protocol are different from each other.

9. The method according to claim 1 , wherein

the first chiplet and the second chiplet are designed based on universal chiplet interconnect express (UCIe) standard, and

the die-to-die interface flit includes a UCIe flit.

10. A chiplet system, wherein

the chiplet system includes a first chiplet and a second chiplet,

the first chiplet is configured to generate a die-to-die interface flit from a first protocol type transaction based on conversion information, and transmit the die-to-die interface flit to the second chiplet, and

the second chiplet is configured to generate a second protocol type transaction from the die-to-die interface flit based on the conversion information,

wherein the conversion information includes information on a packet ID, a payload type code, a payload type size, and a payload size.

11. The chiplet system according to claim 10 , wherein

the first chiplet includes a controller including a protocol layer and an adapter layer, and

the generating the die-to-die interface flit from the first protocol type transaction based on the conversion information includes:

by the protocol layer of the first chiplet, generating a payload of the die-to-die interface flit from the first protocol type transaction based on the conversion information;

by the adapter layer of the first chiplet, generating a header of the die-to-die interface flit; and

by the adapter layer of the first chiplet, generating the die-to-die interface flit by combining the header and the payload.

12. The chiplet system according to claim 10 , wherein

the first chiplet further includes a PHY layer, and

the transmitting the die-to-die interface flit to the second chiplet includes:

by the adapter layer of the first chiplet, transmitting the die-to-die interface flit to the PHY layer of the first chiplet; and

by the PHY layer of the first chiplet, transmitting the die-to-die interface flit to the second chiplet.

13. The chiplet system according to claim 10 , wherein, before generating the die-to-die interface flit, the first chiplet and the second chiplet exchange the conversion information.

14. The chiplet system according to claim 10 , wherein the payload type code includes a write address code, a write data code, a write response code, a read address code, and a read data code.

15. The chiplet system according to claim 10 , wherein

the second chiplet includes a PHY layer, and

the transmitting the die-to-die interface flit to the second chiplet includes transmitting the die-to-die interface flit to the PHY layer of the second chiplet.

16. The chiplet system according to claim 10 , wherein

the second chiplet includes a controller including an adapter layer and a protocol layer, and

the generating the second protocol type transaction from the die-to-die interface flit based on the conversion information includes:

by the adapter layer of the second chiplet, extracting a payload of the die-to-die interface flit from the flit; and

by the protocol layer of the second chiplet, generating a second protocol type transaction from the payload.

17. The chiplet system according to claim 10 , wherein

the first protocol relates to the first chiplet,

the second protocol relates to the second chiplet, and

the first protocol and the second protocol are different from each other.

18. The chiplet system according to claim 10 , wherein

the first chiplet and the second chiplet are designed based on the universal chiplet interconnect express (UCIe) standard, and

the die-to-die interface flit includes a UCIe flit.

Assignments (2)
MERGER AND CHANGE OF NAME Recorded May 22, 2025
From: REBELLIONS INC.; SAPEON KOREA INC.
To: REBELLIONS INC.
Reel/Frame 071355/0107 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2024
From: JIN, YOUNG-JAE; YU, CHANG-HYO
To: REBELLIONS INC.
Reel/Frame 068679/0300 →
Priority Claims (2)
KR 10-2023-0114968 · Aug 30, 2023 · national
KR 10-2023-0181259 · Dec 13, 2023 · national
Continuity (1)
Related Publication 20250077457A1 · Mar 6, 2025
References Cited (33)
US 6678535B1 · Narayanaswami · 2004 [cited by examiner]
US 6898766B2 · Mowery · 2005 [cited by examiner]
US 20020136224A1 · Motley · 2002 [cited by examiner]
US 20050021874A1 · Georgiou · 2005 [cited by examiner]
US 20080086588A1 · Danilak · 2008 [cited by examiner]
US 20080183916A1 · Bellows · 2008 [cited by examiner]
US 20130077635A1 · Deivasigamani · 2013 [cited by examiner]
US 20150016046A1 · Shaeffer · 2015 [cited by examiner]
US 20150248371A1 · Zheng · 2015 [cited by examiner]
US 20160026742A1 · Schelle · 2016 [cited by examiner]
US 20190095377A1 · Brown · 2019 [cited by examiner]
US 20190179785A1 · Keeth · 2019 [cited by examiner]
US 20190243700A1 · Brewer · 2019 [cited by examiner]
US 20200133902A1 · Tang · 2020 [cited by examiner]
US 20220066969A1 · Patrick · 2022 [cited by examiner]
US 20220070089A1 · Brewer · 2022 [cited by examiner]
US 20220070284A1 · Patrick · 2022 [cited by examiner]
US 20220222194A1 · Chandwani · 2022 [cited by examiner]
US 20230080284A1 · Lee · 2023 [cited by applicant]
US 20230123826A1 · Magee · 2023 [cited by examiner]
US 20230162766A1 · Jo · 2023 [cited by examiner]
US 20230409332A1 · Safranek · 2023 [cited by examiner]
US 20240045827A1 · Li · 2024 [cited by examiner]
US 20240295989A1 · Kavala · 2024 [cited by examiner]
US 20250006642A1 · Haba · 2025 [cited by examiner]
KR 1020180094113A · 2018 [cited by applicant]
KR 1020210135996A · 2021 [cited by applicant]
KR 1020230038082A · 2023 [cited by applicant]
KR 1020230125324A · 2023 [cited by applicant]
WO 2017123284A1 · 2017 [cited by applicant]
WO 2020190369A1 · 2020 [cited by applicant]
WO 2022149080A1 · 2022 [cited by applicant]
WO 2023121812A1 · 2023 [cited by applicant]