Visible to Intel only — GUID: mqs1584134967537
Ixiasoft
4.3.8.1. eCPRI Message Type 0- IQ Data Transfer
4.3.8.2. eCPRI Message Type 1- Bit Sequence Transfer
4.3.8.3. eCPRI Message Type 2- Real Time Control Data
4.3.8.4. eCPRI Message Type 3- Generic Data Transfer
4.3.8.5. eCPRI Message Type 4- Remote Memory Access
4.3.8.6. eCPRI Message Type 5- One-Way Delay Measurement
4.3.8.7. eCPRI Message Type 6- Remote Reset
4.3.8.8. eCPRI Message Type 7- Event Indication
4.3.8.9. eCPRI Message Type 64- 255 Vendor Specific
5.1. eCPRI IP Clock Signals
5.2. Power, Reset, and Firewalls Signals
5.3. TX Time of Day Interface
5.4. RX Time of Day Interface
5.5. Interrupt
5.6. Configuration Avalon® Memory-Mapped Interface
5.7. Ethernet MAC Source Interface
5.8. Ethernet MAC Sink Interface
5.9. External ST Source Interface
5.10. External ST Sink Interface
5.11. eCPRI IP Source Interface
5.12. eCPRI IP Sink Interface
5.13. Miscellaneous Interface Signals
5.14. IWF Type 0 eCPRI Interface
5.15. IWF Type 0 CPRI MAC Interface
5.15.1. CPRI 32-bit IQ Data TX Interface
5.15.2. CPRI 64-bit IQ Data TX Interface
5.15.3. CPRI 32-bit Ctrl_AxC TX Interface
5.15.4. CPRI 64-bit Ctrl_AxC TX Interface
5.15.5. CPRI 32-bit Vendor Specific TX Interface
5.15.6. CPRI 64-bit Vendor Specific TX Interface
5.15.7. CPRI 32-bit Real-time Vendor Specific TX Interface
5.15.8. CPRI 64-bit Real-time Vendor Specific TX Interface
5.15.9. CPRI Gigabit Media Independent Interface (GMII)
5.15.10. CPRI IP L1 Control and Status Interface
Visible to Intel only — GUID: mqs1584134967537
Ixiasoft
4.3.3. Concatenation/De-concatenation
The Concatenation/De-concatenation blocks of the eCPRI IP implements concatenation logic of the eCPRI messages into single Ethernet frame or single IP/UDP packet. The sink_concatenation sideband signal identifies packets that required concatenation. The below diagrams illustrates the eCPRI messages with and without concatenation.
Figure 8. eCPRI Message Concatenation
When multiple eCPRI messages are concatenated together, 0 to 3 "zero" padding bytes are added if the following message does not start at a 4 byte boundary. The payload size specified in the eCPRI common header does not include this extra zero padding bytes.
Figure 9. Concatenation/De-concatenation Example Waveform
The above waveform shows two incoming eCPRI messages entering to eCPRI IP, first eCPRI message with concatenation sideband interface signal = 1 and the second eCPRI message with concatenation sideband interface signal = 0. These two eCPRI messages are combined and send through single transport network layer protocol. On the receiving end, the combined eCPRI message will then de-concatenate into 2 eCPRI messages and output to Avalon® streaming interface.
There is a timeout counter used to detect the end of the concatenation message. If the counter overflows and no message with C=0 is detected, an error will be logged and the message with C=1 will be converted to message with C=0 and send to MAC.
The message type allowed for concatenation is restricted to message type 0,1,2,3 and 6. The de-concatenation is supported on all message type except message type 5.
There are 2 different eCPRI packet concatenation scenarios which trigger error and it is shown in below diagram.
Figure 10. eCPRI Packet Concatenation Scenario 1
In the first scenario, there are three incoming Avalon® streaming interface packets payload size of 500 bytes, 600 bytes and 700 bytes. The total payload size after concatenation is 1800 bytes which is bigger than maximum eCPRI IP supported maximum transmission unit (MTU) size of 1500 bytes. In this case, error will be logged in the eCPRI TX error message register and payload 0 and 1 will be sent as concatenated packets while payload 2 will be sent by itself.
Figure 11. eCPRI Packet Concatenation Scenario 2
In the second scenario, the first packet payload size is more than 1500 bytes. In this case, all the packets drop and error logged in eCPRI TX error message register.