IP Library Granted Patent US 7,324,549
Granted Patent B2
US 7,324,549 · App. 10/378,653 · Granted Jan 29, 2008

Synchronisation communication systems

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,549
App. No.
10/378,653
Granted
Jan 29, 2008
Kind
B2
Abstract

A method and apparatus of transmitting data at a line rate to a bus operating at a bus rate includes transmitting the data in a packet format having a plurality of frames each having a plurality of time slots. Each time slot has successive message groups, and each message group includes a plurality of data messages containing the data and an idle code containing none of the data. A number of idle codes in each frame is selected such that the bus rate matches the line rate. Various communication buses, and methods of synchronizing data are implemented.

Claims (30)

1. A method of transmitting data at a line rate to a bus operating at a bus rate, the method comprising transmitting the data in a packet format consisting of a plurality of frames each having a plurality of time slots, each time slot having successive message groups, wherein each message group comprises a plurality of data messages containing said data and an idle code containing no said data;

wherein the number of idle codes in each frame is selected so that the bus rate matches the line rate.

2. A method according to claim 1 , wherein said data messages are of a fixed length.

3. A method according to claim 1 , wherein each said message group contains a control message.

4. A method according to claim 1 , wherein the bus rate is derived from an integer multiple of an independently generated reference system clock.

5. A communication bus operable at a bus rate and having at least a first node and a second node that are linked by communication channels for transmitting at said bus rate data generated at a line rate, said first node having a transmitting element and said second node having a receiving element, wherein the transmitting element of said first node is operable to transmit data in a packet format consisting of a plurality of frames each having a plurality of time slots, each time slot having successive message groups, wherein each message group comprises a plurality of data messages containing said data and an idle code containing no said data;

wherein said number of idle codes in each frame is selected so that the bus rate matches the line rate and wherein the receiving element of the second node is arranged to detect said idle codes for synchronization purposes.

6. A communication bus according to claim 5 , wherein said communication channels comprise a first set of channels for transferring data in one direction and a second set of channels for transferring data in the opposite direction.

7. A communication bus according to claim 6 , wherein said first node comprises a receiving element and said second node comprises a transmitting element, such that the transmitting element of the first node communicates with the receiving element of the second node over said first set of channels and said transmitting element of the second node communicates with the receiving node of the first node over said second set of channels.

8. A communication bus according to claim 5 , wherein at least one of said idle codes inserted into the frame is different from the other idle codes in the frame and is used to mark a frame boundary.

9. A method of synchronising a data communication over a bus in a packet format, said data having been generated at a line rate to a bus operating at a bus rate, the method comprising transmitting the data in a packet format consisting of a plurality of frames each having a plurality of time slots, each time slot having successive message groups, wherein each message group comprises a predetermined number of data messages containing said data and an idle code containing no said data, the method comprising detecting at a bus node said idle codes until a predetermined number of said idle codes have been detected indicating successful synchronization.

10. A method according to claim 9 , wherein at least one of said idle codes inserted into the frame is a unique idle code, said unique idle code being different from the other idle codes and being used to mark a frame boundary.

11. A method according to claim 9 , wherein a check on the quality of the bus is achieved by synchronisation of each node comprising the steps of:

transmitting message groups containing only idle codes so that no data messages are transmitted;

receiving said idle codes so that if all idle codes are received correctly a valid message group is received; and

counting the number of consecutive valid message groups received and, when said number reaches a predetermined value, indicating that synchronisation of said bus node has been achieved.

12. A method according to claim 9 , wherein a check on the quality of the bus is achieved by synchronisation of each node comprising the steps of:

transmitting message groups containing only idle codes so that no data messages are transmitted;

receiving said idle codes so that if one or several idle codes are received erroneously an invalid message group is received;

counting the number of consecutive invalid message groups received and, when said number reaches a predetermined value, indicating a failure of synchronisation of the bus link.

13. A method according to claim 9 , wherein for data communications that are unsynchronised, the synchronisation of said bus is achieved by performing the following steps:

transmitting said message groups containing data messages and an idle code;

receiving said message groups where a message group is considered valid if an idle code exists at the end of the message group and no idle codes exist in the remainder of said message group;

counting the number of consecutive valid message groups received and, when said number reaches a predetermined value, indicating a synchronised state.

14. A method according to claim 13 , wherein a message group is considered valid if an idle code exists at the end of the message group, no idle codes exist in the remainder of said message groups, and there exist no 8b10b decoding errors in the message group.

15. A method according to claim 9 , wherein for data communications that are synchronised, an unsynchronised state of said bus is detected by performing the following steps:

transmitting said message groups containing data messages and an idle code;

receiving said message groups where a message group is considered invalid if an idle code does not exist at the end of the message group or an idle code exists in the remainder of said message group or there exists 8b10b decoding errors in the message group;

counting the number of consecutive invalid message groups received and, when said number reaches a predetermined value, indicating an unsynchronised state.

16. A method according to claim 1 , when applied to a protocol stack, comprising an application layer, a transport layer and a physical layer, wherein data is transferred across the physical layer using said packet format and wherein said physical layer is able to report the synchronisation status of said bus to said upper transport and application layers.

Assignments (13)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
CHANGE OF NAME Recorded Nov 19, 2014
From: NOKIA SIEMENS NETWORKS OY
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 034294/0603 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2008
From: NOKIA CORPORATION
To: NOKIA SIEMENS NETWORKS OY
Reel/Frame 020550/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 9, 2003
From: ADDY, TIM; VAINIKKA, MARKKU; VIERO, TIMO; BROCKINGTON, WILLIAM; VAHATAINI, MARKKU
To: NOKIA CORPORATION
Reel/Frame 014589/0344 →