IP Library Granted Patent US 7,620,047
Granted Patent B2
US 7,620,047 · App. 10/997,300 · Granted Nov 17, 2009

Method of transporting a RapidIO packet over an IP packet network

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 7,620,047
App. No.
10/997,300
Granted
Nov 17, 2009
Kind
B2
Abstract

A method of transporting a RapidIO packet ( 135 ) from an initiator RapidIO domain ( 102 ) over an IP packet network ( 110 ) to a receiver RapidIO domain ( 104 ) can include the initiator RapidIO domain creating the RapidIO packet and reading a destination domain ID ( 483 ) of the RapidIO packet, where the destination domain ID corresponds to the receiver RapidIO domain. The destination domain ID is mapped to a receiver RapidIO domain IP address ( 473 ). The RapidIO packet is encapsulated in an IP packet ( 436 ) and the IP packet is communicated to the receiver RapidIO domain over the IP packet network.

Claims (67)

1. In a computer network, a method of transporting a RapidIO packet from an initiator RapidIO domain over an IP packet network to a receiver RapidIO domain, comprising:

the initiator RapidIO domain creating the RapidIO packet;

reading a destination domain ID of the RapidIO packet, wherein the destination domain ID corresponds to the receiver RapidIO domain;

mapping the destination domain ID to a receiver RapidIO domain IP address;

encapsulating the RapidIO packet in an IP packet; and

communicating the IP packet to the receiver RapidIO domain over the IP packet network.

2. The method of claim 1 , further comprising:

the receiver RapidIO domain de-encapsulating the RapidIO packet from the IP packet;

mapping the receiver RapidIO domain IP address to the destination domain ID; and

issuing the RapidIO packet to the receiver RapidIO domain on a RapidIO network.

3. The method of claim 2 , further comprising placing the destination domain ID into a RapidIO header of the RapidIO packet.

4. The method of claim 1 , further comprising placing the receiver RapidIO domain IP address into an IP header of the IP packet.

5. The method of claim 1 , further comprising:

mapping a source domain ID of the initiator RapidIO domain to a source RapidIO domain IP address; and

placing the source RapidIO domain IP address into an IP header of the IP packet.

6. The method of claim 1 , wherein each of the initiator RapidIO domain and the receiver RapidIO domain has a plurality of RapidIO nodes communicating with each other over a RapidIO network.

7. The method of claim 1 , further comprising

the receiver domain initiating a communication with a third RapidIO domain;

the receiver domain creating a second RapidIO packet;

reading a second destination domain ID of the second RapidIO packet, wherein the second destination domain ID corresponds to the third RapidIO domain;

mapping the second destination domain ID to a third RapidIO domain IP address;

encapsulating the second RapidIO packet in an second IP packet; and

communicating the second IP packet to the third RapidIO domain over the IP packet network.

8. In a computer network, a method of transporting a RapidIO packet from an initiator RapidIO domain over an IP packet network to a receiver RapidIO domain, comprising:

the initiator RapidIO domain receiving a transaction signal from a non-RapidIO source;

the initiator RapidIO domain creating the RapidIO packet from the transaction signal;

reading a destination domain ID of the RapidIO packet, wherein the destination domain ID corresponds to the receiver RapidIO domain;

mapping the destination domain ID to a receiver RapidIO domain IP address;

encapsulating the RapidIO packet in an IP packet; and

communicating the IP packet to the receiver RapidIO domain over the IP packet network.

9. The method of claim 8 , further comprising the transaction signal accessing the initiator RapidIO domain through a memory-mapped interface.

10. The method of claim 8 , further comprising the transaction signal accessing the initiator RapidIO domain through a port-mapped interface.

11. The method of claim 8 , further comprising:

the receiver RapidIO domain de-encapsulating the RapidIO packet from the IP packet;

mapping the receiver RapidIO domain IP address to the destination domain ID; and

issuing the RapidIO packet to the receiver RapidIO domain on a RapidIO network.

12. The method of claim 11 , further comprising placing the destination domain ID into a RapidIO header of the RapidIO packet.

13. The method of claim 8 , further comprising placing the receiver RapidIO domain IP address into an IP header of the IP packet.

14. In a computer network, a method of remotely creating a RapidIO packet on a receiver RapidIO domain, comprising:

a non-RapidIO source initiating a transaction signal having a receiver RapidIO domain IP address;

the transaction signal traversing an IP packet network to the receiver RapidIO domain;

at the receiver RapidIO domain, creating the RapidIO packet;

mapping the receiver RapidIO domain IP address to a destination domain ID;

placing the destination domain ID into a RapidIO header of the RapidIO packet; and

issuing the RapidIO packet to the receiver RapidIO domain on a RapidIO network.

15. A RapidIO domain, comprising:

a RapidIO network; and

a RapidIO-to-IP encapsulation module coupled to the RapidIO network, wherein the RapidIO-to-IP encapsulation module couples the RapidIO domain to an IP packet network, wherein the RapidIO-to-IP encapsulation module is coupled to map a destination domain ID of a RapidIO packet to a receiver RapidIO domain IP address, and wherein the RapidIO-to-IP encapsulation module is coupled to encapsulate the RapidIO packet into an IP packet.

16. The RapidIO domain of claim 15 , wherein the RapidIO-to-IP encapsulation module is coupled to communicate the IP packet to a receiver RapidIO domain over the IP packet network.

17. The RapidIO domain of claim 15 , wherein the RapidIO-to-IP encapsulation module is coupled to place the receiver RapidIO domain IP address into an IP header of the IP packet.

18. The RapidIO domain of claim 15 , wherein the RapidIO-to-IP encapsulation module is coupled to map a source domain ID to a source RapidIO domain IP address and place the source RapidIO domain IP address into an IP header of the IP packet.

19. A RapidIO domain, comprising:

a RapidIO network; and

a RapidIO-to-IP encapsulation module coupled to the RapidIO network, wherein the RapidIO-to-IP encapsulation module couples the RapidIO domain to an IP packet network, wherein the RapidIO-to-IP encapsulation module is coupled to de-encapsulate a RapidIO packet from an IP packet, wherein the RapidIO-to-IP encapsulation module is coupled to map a receiver RapidIO domain IP address to a destination domain ID, wherein the RapidIO-to-IP encapsulation module is coupled to place the destination domain ID into a RapidIO header of the RapidIO packet, and wherein the RapidIO-to-IP encapsulation module is coupled to issue the RapidIO packet on a RapidIO network.

20. In a RapidIO domain, a method of communicating a RapidIO packet over an IP packet network, comprising:

creating the RapidIO packet;

reading a destination domain ID of the RapidIO packet;

mapping the destination domain ID to a receiver RapidIO domain IP address;

encapsulating the RapidIO packet in an IP packet; and

communicating the IP packet to a receiver RapidIO domain over the IP packet network.

21. The RapidIO domain of claim 20 , further comprising placing the receiver RapidIO domain IP address into an IP header of the IP packet.

22. In a RapidIO domain, a method of communicating a RapidIO packet over an IP packet network, comprising:

receiving an IP packet over the IP packet network, wherein the IP packet comprises the RapidIO packet;

de-encapsulating the RapidIO packet from the IP packet;

mapping a receiver RapidIO domain IP address to a destination domain ID; and

issuing the RapidIO packet to the RapidIO domain on a RapidIO network.

23. The RapidIO domain of claim 22 , further comprising placing the destination domain ID into a RapidIO header of the RapidIO packet.

Assignments (11)
PATENT SECURITY AGREEMENT Recorded Jun 30, 2025
From: CREELED, INC.; PENGUIN SOLUTIONS CORPORATION (DE); SMART EMBEDDED COMPUTING, INC.; SMART HIGH RELIABILITY SOLUTIONS LLC; SMART MODULAR TECHNOLOGIES, INC.; PENGUIN COMPUTING, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 071755/0001 →
RELEASE OF PATENT SECURITY INTEREST RECORDED AT R/F 058983/0001 Recorded Jun 25, 2025
From: CITIZENS BANK, N.A.
To: SMART MODULAR TECHNOLOGIES, INC.; SMART EMBEDDED COMPUTING, INC.; SMART HIGH RELIABILITY SOLUTIONS LLC; CREELED, INC.
Reel/Frame 071725/0207 →
SECURITY INTEREST Recorded Feb 7, 2022
From: SMART MODULAR TECHNOLOGIES, INC.; SMART HIGH RELIABILITY SOLUTIONS, LLC; SMART EMBEDDED COMPUTING, INC.; CREELED, INC.
To: CITIZENS BANK, N.A.
Reel/Frame 058983/0001 →
CHANGE OF NAME Recorded Jun 24, 2020
From: ARTESYN EMBEDDED COMPUTING, INC.
To: SMART EMBEDDED COMPUTING, INC.
Reel/Frame 053023/0953 →
CHANGE OF NAME Recorded Jun 18, 2020
From: EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.
To: ARTESYN EMBEDDED COMPUTING, INC.
Reel/Frame 052978/0634 →
RELEASE OF SECURITY INTEREST Recorded Jul 9, 2019
From: ARTESYN EMBEDDED COMPUTING, INC. (F/K/A EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.)
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049698/0222 →
PARTIAL RELEASE OF SECURITY INTEREST Recorded Jul 8, 2019
From: BANK OF AMERICA, N.A.
To: ARTESYN EMBEDDED COMPUTING, INC. (F/K/A EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.)
Reel/Frame 049694/0096 →
SECURITY AGREEMENT Recorded Nov 26, 2013
From: ARTESYN TECHNOLOGIES, INC.; ARTESYN NORTH AMERICA LLC; EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 031731/0048 →
SECURITY AGREEMENT Recorded Nov 25, 2013
From: ARTESYN TECHNOLOGIES, INC.; ARTESYN NORTH AMERICA LLC; EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT AND GRANTEE
Reel/Frame 031719/0417 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 22, 2008
From: MOTOROLA, INC.
To: EMERSON NETWORK POWER - EMBEDDED COMPUTING, INC.
Reel/Frame 020540/0714 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 23, 2004
From: SANDY, DOUGLAS L.; HARRIS, JEFFREY M.; TUFFORD, ROBERT C.
To: MOTOROLA, INC.
Reel/Frame 016036/0261 →