IP Library Granted Patent US 7,324,516
Granted Patent B2
US 7,324,516 · App. 10/217,644 · Granted Jan 29, 2008

Data packet header conversion

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,324,516
App. No.
10/217,644
Granted
Jan 29, 2008
Kind
B2
Abstract

A method of converting a data packet that has a header includes storing the data packet and generating a header template having a plurality of static fields. The method further includes generating at least one dynamic field and merging the header template with the header. The method further includes inserting the at least one dynamic field to form a converted header.

Claims (36)

1. A method of converting a data packet from a first format compatible with a first network to a second format compatible with a second network, said method comprising:

storing the data packet, wherein the data packet has a first header in the first format;

generating a header template having a plurality of static fields, the header template including, for an egress packet buffer, an IP header configured to be written to a first three quadwords of the egress packet buffer, an UDP header configured to be written to a fourth quadword of the egress packet buffer and an RTP header configured to be written to a fifth quadword of the egress packet buffer, the header template including, for an ingress packet buffer, a DSP header configured to be written to a fourth quadword and a fifth quadword of the ingress packet buffer;

generating at least one dynamic field; and

merging the header template with the first header and inserting the at least one dynamic field to form a converted header in the second format.

2. The method of claim 1 , wherein the data packet is stored in a packet buffer.

3. The method of claim 1 , wherein the first header is a DSP proprietary header.

4. The method of claim 1 , wherein the converted header is an IP/UDP/RTP header.

5. The method of claim 1 , wherein the static fields are constant for all packets on a communication system.

6. The method of claim 1 , wherein the static fields are constant for a duration of a telephone call on a communication system.

7. The method of claim 1 , wherein the data packet has a payload, further comprising:

aligning the header template with the payload.

8. A method of converting a first data packet from a first format compatible with a first network to a second format compatible with a second network, comprising:

receiving the first data packet from the first network, the first data packet comprising a header having a plurality of fields in the first format;

generating a header template having a plurality of static fields, the header template including, for an egress packet buffer, an IP header configured to be written to a first three quadwords of the egress packet buffer, an UDP header configured to be written to a fourth quadword of the egress packet buffer and an RTP header configured to be written to a fifth quadword of the egress packet buffer, the header template including, for an ingress packet buffer, a DSP header configured to be written to a fourth quadword and a fifth quadword of the ingress packet buffer; and

merging the header template with the first data packet, wherein at least one of the static fields replaces at least one of the plurality of data packet fields.

9. The method of claim 8 , wherein the merging generates a second data packet having the second format, further comprising:

transmitting the second data packet on the second network.

10. The method of claim 9 , wherein the first network is a TDM network, and the second network is an IP network.

11. The method of claim 9 , wherein the first data packet comprises a payload, further comprising:

aligning the header template with the payload.

12. The method of claim 8 , wherein at least one of the static fields is constant.

13. The method of claim 12 , wherein at least one of the static fields is constant for a duration of a telephone call.

14. The method of claim 8 , further comprising generating a dynamic field.

15. A computer readable medium having instructions stored thereon that, when executed by a processor, cause the processor to:

store a data packet, wherein the data packet has a first header in a first format compatible with a first network;

generate a header template having a plurality of static fields, the header template including, for an egress packet buffer, an IP header configured to be written to a first three quadwords of the egress packet buffer, an UDP header configured to be written to a fourth quadword of the egress packet buffer and an RTP header configured to be written to a fifth quadword of the egress packet buffer, the header template including, for an ingress packet buffer, a DSP header configured to be written to a fourth quadword and a fifth quadword of the ingress packet buffer;

generate at least one dynamic field; and

merge the header template with the first header and insert the at least one dynamic field to form a converted header in a second format compatible with a second network.

16. The computer readable medium claim 15 , wherein the data packet is stored in a packet buffer.

17. The computer readable medium claim 15 , wherein the first header is a DSP proprietary header.

18. The computer readable medium claim 15 , wherein the converted header is an IP/UDP/RTP header.

19. The computer readable medium claim 15 , wherein the static fields are constant for all packets on a communication system.

20. The computer readable medium claim 15 , wherein the static fields are constant for a duration of a telephone call on a communication system.

21. The computer readable medium claim 15 , wherein the data packet has a payload, the instructions further causing the processor to:

align the header template with the payload.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Nov 12, 2019
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: MICRON TECHNOLOGY, INC.; MICRON SEMICONDUCTOR PRODUCTS, INC.
Reel/Frame 051028/0001 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2019
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: MICRON TECHNOLOGY, INC.
Reel/Frame 050937/0001 →
RELEASE OF SECURITY INTEREST Recorded Aug 23, 2018
From: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: MICRON TECHNOLOGY, INC.
Reel/Frame 047243/0001 →
SECURITY INTEREST Recorded Jul 13, 2018
From: MICRON TECHNOLOGY, INC.; MICRON SEMICONDUCTOR PRODUCTS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 047540/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REPLACE ERRONEOUSLY FILED PATENT #7358718 WITH THE CORRECT PATENT #7358178 PREVIOUSLY RECORDED ON REEL 038669 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Jun 8, 2017
From: MICRON TECHNOLOGY, INC.
To: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 043079/0001 →
PATENT SECURITY AGREEMENT Recorded Jun 2, 2016
From: MICRON TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 038954/0001 →
SECURITY INTEREST Recorded May 12, 2016
From: MICRON TECHNOLOGY, INC.
To: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 038669/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 4, 2013
From: INTEL CORPORATION
To: MICRON TECHNOLOGY, INC.
Reel/Frame 030747/0001 →