Integrated circuit data stream processing using paged buffering

Paged buffering in integrated circuits optimizes data decoding for IoT devices by enabling parallel processing and reducing resource consumption, addressing inefficiencies in existing buffering methods.

JP2024166128AActive Publication Date: 2024-11-28EDGECORTIX INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024078441
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-02-28
Filing Date
2024-05-14
Publication Date
2024-11-28
Estimated Expiration
2044-05-14

AI Technical Summary

Technical Problem

Efficient decoding of data encoded with FEC codes is essential for wireless communication, particularly for IoT devices with limited power and processing capabilities, where existing buffering methods in integrated circuits are inefficient and resource-intensive.

Method used

Implementing paged buffering in integrated circuits with shared random access memory and counters for upstream and downstream processors, allowing random access and reducing the need for continuous sequences, thereby optimizing data processing and reducing resource consumption.

Benefits of technology

Enhances decoding efficiency by allowing parallel processing and reducing the number of clock cycles required for data transfer, improving performance in devices with limited resources.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024166128000001_ABST
    Figure 2024166128000001_ABST
Patent Text Reader

Abstract

To provide an integrated circuit and method for making wireless communication reliable and efficient.SOLUTION: Integrated circuit data stream processing using paged buffering is performed by an integrated circuit including an upstream random access memory, a local read counter, a downstream random access memory, a local write counter, and a processor. The local read counter stores a value indicating whether any accessible data blocks are stored in the upstream memory and a value indicating whether any downstream pages of the downstream memory are available for recording. The processor adjusts the local read counter to indicate a page release, adjusts the local write counter to indicate a page occupy, reads a first data block recorded to the upstream memory, processes the first data block to generate a second data block, and records the second data block to the downstream memory.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority to Provisional Application No. 63 / 502,417, filed May 16, 2023, the contents of which are incorporated herein by reference in their entirety. [Background technology] Wireless data communication has become ubiquitous in modern society. As digital data transmission became more prevalent, the usefulness of reliable, error-free communication over noisy wireless channels became apparent. This led to the creation of Forward Error Correction (FEC) codes. FEC codes are mathematical algorithms used to add redundant information to transmitted data, allowing the receiver to correct errors that may have occurred during transmission. FEC codes have become essential as wireless communication systems have expanded, especially with the advent of mobile telephony and data-intensive applications. Without FEC, wireless data transmissions would suffer from higher error rates, leading to data corruption and costly retransmissions. FEC codes, such as Low-Density Parity-Check (LDPC) codes, are an essential component of modern wireless technology, making wireless communication reliable and efficient by improving data integrity and mitigating the effects of channel impairments. [Brief description of the drawings]

[0002] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It is noted that, according to standard industry practice, various features have not been drawn to scale. In fact, dimensions of various features may be arbitrarily increased or decreased for clarity of discussion.

[0003] [Figure 1] 1 is a schematic diagram of a system for low-density parity-check (LDPC) data transmission in accordance with at least one embodiment of the present invention.

[0004] [Diagram 2] FIG. 1 is a schematic diagram of an integrated circuit encoder for LDPC data encoding in accordance with at least one embodiment of the present invention.

[0005] [Diagram 3] FIG. 1 is a schematic diagram of an integrated circuit decoder for LDPC data decoding in accordance with at least one embodiment of the present invention.

[0006] [Figure 4] FIG. 1 is a schematic diagram of an integrated circuit that utilizes paged buffering for data stream processing in accordance with at least some embodiments of the present invention.

[0007] [Diagram 5] FIG. 2 is a schematic diagram of another integrated circuit that utilizes paged buffering for data stream processing in accordance with at least some embodiments of the present invention.

[0008] [Figure 6] FIG. 6 is a schematic diagram of an integrated circuit encoder 601 that utilizes a buffer for LDPC data encoding, in accordance with at least one embodiment of the present invention.

[0009] [Figure 7] FIG. 2 is a schematic diagram of an encoding section of an integrated circuit encoder for LDPC data encoding utilizing paged buffering, in accordance with at least one embodiment of the present invention.

[0010] [Figure 8] 1 is an operational flow for LDPC data decoding utilizing paged buffering in accordance with at least some embodiments of the present invention.

[0011] [Figure 9] 1 is an operational flow for data probability value segment decoding utilizing paged buffering in accordance with at least one embodiment of the present invention.

[0012] [Figure 10] 1 is an operational flow for buffer checking in accordance with at least one embodiment of the present invention.

[0013] [Figure 11] 1 is an operational flow for data block processing in accordance with at least one embodiment of the present invention.

[0014] [Figure 12] 1 is an operational flow for confirming completion in accordance with at least one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] The following disclosure provides many different embodiments or examples for implementing different features of the provided subject matter. Specific examples of components, values, operations, materials, or arrangements, etc. are described below to simplify the disclosure. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, or arrangements, etc. are contemplated. In addition, the disclosure may repeat reference numerals and / or letters in the various examples. This repetition is for the purposes of brevity and clarity and does not in itself dictate a relationship between the various embodiments and / or configurations discussed.

[0016] Efficient decoding of data encoded with FEC codes plays a key role in the proliferation of wireless communications to a vast array and variety of connected devices, such as Internet of Things (IoT) devices, many of which have limited power and processing capabilities.

[0017] FIG. 1 is a schematic diagram of a system for low-density parity check (LDPC) data transmission, in accordance with at least one embodiment of the present invention. The system includes an encoder 101, a transmitter 103, a receiver 106, and a decoder 108. In at least some embodiments, the encoder 101 and the transmitter 103 are part of a single device, such as a transmission tower of a wireless access network. In at least some embodiments, the receiver 106 and the decoder 108 are part of a single device, such as a smartphone, that communicates with the wireless access network. In at least some embodiments, such a single device has the encoder, the transmitter, the receiver, and the decoder, allowing two-way communication. In FIG. 1, the encoder 101 and the transmitter 103 are not part of the same device as the receiver 106 and the decoder 108, since the transmitter 103 is in direct communication with the receiver 106.

[0018] The encoder 101 is configured to receive original data 100 and transmit encoded data 102 to a transmitter 103. In at least some embodiments, the encoder 101 is configured to receive the original data 100 in one or more blocks of a predetermined length. In at least some embodiments, the encoder 101 is configured to apply FEC coding to the original data 100 to generate encoded data 102. In at least some embodiments, the encoder 101 is configured to apply LDPC coding to the original data 100 to generate encoded data 102. In at least some embodiments, the encoder 101 is an integrated circuit, such as a Field-Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), or the like. In at least some embodiments, the encoder 101 is a computer having a processor and a memory that stores instructions for execution by the processor.

[0019] The transmitter 103 is configured to receive the encoded data 102 from the encoder 101 over wireless communication and transmit binary values ​​104 of the encoded data 102 to the receiver 106. In at least some embodiments, the transmitter 103 is configured to transmit the encoded data 102 in one or more blocks of a predetermined length. In at least some embodiments, the transmitter 103 is configured to transmit the binary values ​​104 according to a standard wireless protocol, such as 5G, BLUETOOTH, BLE, WiFi, 3G GPRS, 3G EVDO, 3G HSPA, 4G WiMAX, 4G E-UTRAN (LTE), etc. Although not all of the aforementioned standards, such as 3G and 4G, currently utilize LDPC, in at least some embodiments, the transmitter 103 includes configurations for multiple standard wireless protocols. In at least some embodiments, the transmitter 103 is configured to transmit in a frequency and timing scheme according to the standard wireless protocol. In at least some embodiments, the transmitter 103 is configured to transmit the binary value 104 over a data channel and other information for decoding the encoded data 102, such as information representing a parity check matrix, over a control channel.

[0020] The receiver 106 is configured to receive probability values ​​105 through wireless reception and transmit encoded probability values ​​107 to the decoder 108. In at least some embodiments, the receiver 106 is configured to record the probability values ​​105 when attempting to receive the binary value 104, the probability values ​​105 representing one or more probabilities that the binary value received from the transmission of the binary value 104 as transmitted by the transmitter 103 represents a 1 or a 0. In at least some embodiments, the receiver 106 records probability values ​​during reception having a reliability proportional to the signal-to-noise ratio. In at least some embodiments, the receiver 106 is configured to record more reliable probability values ​​during instances of a higher signal-to-noise ratio and record less reliable probability values ​​during instances of a lower signal-to-noise ratio. In at least some embodiments, the received values ​​are represented as follows: z i =y i +n i formula 1 Here, z i represents the received value, and y i represents the transmitted value, and n i Let x denote Additive White Gaussian Noise (AWGN), i from 1 to N, where N is the number of received coded probability values. In at least some embodiments, receiver 106 converts the received values ​​to the Log-Likelihood Ratio (LLR) domain as follows:

number

[0021] In at least some embodiments, the receiver 106 is configured to use multiple bits of data to record one or more of the probability values ​​105 corresponding to one of the binary values ​​104. In at least some embodiments, the number of bits of data used to record each one of the probability values ​​105 depends on the hardware capabilities of the receiver 106 or the decoder 108. In at least some embodiments, the receiver 106 is configured to use 6 bits of data to record one or more of the probability values ​​105 corresponding to one of the binary values ​​104. In at least some embodiments, the receiver 106 is configured to receive the probability values ​​105 in one or more blocks of predetermined length. In at least some embodiments, the receiver 106 is configured to assemble the probability values ​​105 into the coded probability values ​​107 using a format that defines a correspondence between the probability values ​​of the coded probability values ​​107 and the binary values ​​of the coded data 102. In at least some embodiments, the receiver 106 is configured to receive the probability values ​​105 over a data channel and other information for decoding the encoded data 102, such as information representing a parity check matrix, over a control channel.

[0022] The decoder 108 is configured to receive the coded probability values ​​107 from the receiver 106 and output decoded data 109. In at least some embodiments, the decoder 108 is configured to decode the coded probability values ​​107 into decoded data 109. In at least some embodiments, the decoder 108 is configured to apply FEC decoding to the coded probability values ​​107 to generate the decoded data 109. In at least some embodiments, the decoder 108 is configured to apply LDPC decoding to the coded probability values ​​107 to generate the decoded data 109. In at least some embodiments, the decoder 108 is an integrated circuit such as an FPGA, an ASIC, or the like. In at least some embodiments, the decoder 108 is a computer having a processor and a memory that stores instructions for execution by the processor.

[0023] 2 is a schematic diagram of an integrated circuit encoder 201 for LDPC data encoding in accordance with at least one embodiment of the present invention. The integrated circuit encoder 201 includes a segmentation processor 210, an encoding processor 213, a concatenation processor 216, and a parameter processor 219.

[0024] The segmentation processor 210 is configured to receive the original data block 200 and transmit data segments 211 to the encoding processor 213 and the concatenation processor 216. In at least some embodiments, the segmentation processor 210 is configured to divide the original data block 200 into a plurality of data segments. In at least some embodiments, the segmentation processor 210 is configured to divide the original data block 200 into one or more segments of a predetermined length. In at least some embodiments, the segmentation processor 210 is configured to divide the original data block 200 into segments having a length according to the length of the original data block 200. In at least some embodiments, the segmentation processor 210 is configured to divide the original data block into a plurality of data segments according to the columns of the LDPC-based graph. In at least some embodiments, the original data block 200 corresponds to an "information block" in the 5G standard, which is the result of a previous segmentation of a transport block that is not performed by the segmentation processor 210.

[0025] The encoding processor 213 is configured to receive the data segments 211 and transmit the parity segments 214 to the concatenation processor 216. In at least some embodiments, the encoding processor 213 is configured to apply a parity check matrix to the data segments 211 to generate the parity segments 214. In at least some embodiments, the encoding processor 213 is configured to apply an LDPC parity check matrix to the data segments 211 to generate the parity segments 214. In at least some embodiments, the encoding processor 213 is configured to apply one or more cyclic shifts to each data segment 211 according to the parity check matrix to generate the parity segments 214. In at least some embodiments, the encoding processor 213 is configured to apply one or more cyclic shifts to some of the parity segments, such as the "core" parity segments of the parity segments 214 according to the parity check matrix to generate other parity segments among the parity segments 214. In at least some embodiments, the encoding processor 213 is configured to input a value to each bit of each parity segment such that the sum of the bit values ​​and binary values ​​in a subset of values ​​of one or more data segments and other parity segments corresponding to that bit is an even number.

[0026] The concatenation processor 216 is configured to receive the data segments 211 and the parity segments 214 and output the encoded data block 202. In at least some embodiments, the concatenation processor 216 is configured to concatenate the data segments 211 with the parity segments 214 to generate the encoded data block 202. In at least some embodiments, the concatenation processor 216 is configured to concatenate the data segments 211 with the parity segments 214 into a format that defines a correspondence between a subset of values ​​in the data segments 211 and the parity segments 214.

[0027] The parameter processor 219 is configured to receive the parameter stream 218 and send information to the segmentation processor 210, the encoding processor 213, and the concatenation processor 216. In at least some embodiments, the parameter processor 219 is configured to receive the parameter stream 218 over a control channel. In at least some embodiments, the parameter processor 219 is configured to receive information indicative of a parity check matrix corresponding to the original data block 200 in the parameter stream 218. In at least some embodiments, the parameter processor 219 is configured to send associated parameters to each of the segmentation processor 210, the encoding processor 213, and the concatenation processor 216. In at least some embodiments, the parameter processor 219 is configured to send information indicative of the segment size to the segmentation processor 210. In at least some embodiments, the parameter processor 219 is configured to send information indicative of the parity check matrix corresponding to the original data block 200 to the encoding processor 213. In at least some embodiments, the parameter processor 219 is configured to send information indicative of the parity check matrix corresponding to the original data block 200 to the concatenation processor 216.

[0028] 3 is a schematic diagram of an integrated circuit decoder 308 for LDPC data decoding in accordance with at least one embodiment of the invention. The integrated circuit decoder 308 includes a segmentation processor 320, one or more decoding processors 323, a concatenation processor 326, and a parameter processor 329.

[0029] The segmentation processor 320 is configured to receive the data block of coded probability values ​​307 and transmit probability value segments 321 to the decoding processor 323. In at least some embodiments, the probability value segments 321 include a data probability value segment and a parity probability value segment. In at least some embodiments, the segmentation processor 320 is configured to divide the data block of coded probability values ​​307 into a plurality of data probability value segments and a plurality of parity probability value segments, each probability value of the coded data block representing a likelihood between binary values. In at least some embodiments, the segmentation processor 320 is configured to divide the data block of coded probability values ​​307 into segments having a length according to the length of the data block of coded probability values ​​307.

[0030] The decode processors 323 are each configured to receive the probability value segments 321 and send the decoded binary value segments 324 to the concatenation processor 326. In at least some embodiments, each decode processor 323 is configured to adjust the probability values ​​of the encoded data block based on a parity check matrix according to an iteration variable accuracy parameter, the parity check matrix defining the correspondence between the data probability value segments and the parity probability value segments, where the iteration variable accuracy parameter represents a trade-off between accuracy and computational efficiency. In at least some embodiments, the decode processors 323 are each configured to apply the parity check matrix to the probability value segments 321 to generate the decoded binary value segments 324. In at least some embodiments, the decode processors 323 are each configured to apply the LDPC parity check matrix to the probability value segments 321 to generate the decoded binary value segments 324. In at least some embodiments, each of the decode processors 323 is configured to apply one or more cyclic shifts to each data probability value segment and each parity probability value segment of the probability value segments 321 according to the parity check matrix to generate a decoded binary value segment 324. In at least some embodiments, each of the decode processors 323 is configured to compare binary values ​​in a subset of values ​​of corresponding data probability value segments and parity probability value segments to ensure that the sum of the values ​​is even. In at least some embodiments, each of the decode processors 323 includes a sorter for sorting the probability values ​​into segments to find a minimum value, a calculator for calculating an update value from the minimum value, a function selector for selecting an accuracy function for determining an adjustment amount based on the minimum value, and an accuracy parameter selector for selecting an iteration variable accuracy parameter.

[0031] The concatenation processor 326 is configured to receive the decoded binary value segments 324 and output a decoded data block 309. In at least some embodiments, the concatenation processor 326 is configured to concatenate likely binary values ​​that satisfy a parity check matrix associated with the probability values ​​of each data probability value segment to form a decoded data block. In at least some embodiments, the concatenation processor 326 is configured to concatenate the decoded binary value segments 324 to generate the decoded data block 309. In at least some embodiments, the concatenation processor 326 is configured to concatenate the decoded binary value segments 324 to form the same format as the original data block.

[0032] The parameter processor 329 is configured to receive the parameter stream 328 and send information to the segmentation processor 320, the decoding processor 323, and the concatenation processor 326. In at least some embodiments, the parameter processor 329 is configured to send a plurality of parameters to each of the segmentation processor, the decoding processor, and the concatenation processor, where the plurality of parameters correspond to the encoded data block. In at least some embodiments, the parameter processor 329 is configured to receive the parameter stream 328 over a control channel. In at least some embodiments, the parameter processor 329 is configured to receive information indicative of a parity check matrix corresponding to the data block 307 of the encoded probability values ​​in the parameter stream 328. In at least some embodiments, the parameter processor 329 is configured to send associated parameters to each of the segmentation processor 320, the decoding processor 323, and the concatenation processor 326. In at least some embodiments, the parameter processor 329 is configured to send information indicative of a segment size to the segmentation processor 320. In at least some embodiments, the parameter processor 329 is configured to send information representing a parity check matrix corresponding to the data block 307 of coded probability values ​​to the decoding processor 323. In at least some embodiments, the parameter processor 329 is configured to send information representing a parity check matrix corresponding to the data block 307 of coded probability values ​​to the concatenation processor 326.

[0033] Generally, performing tasks in parallel increases decoding efficiency. At least some integrated circuits configured to decode data include multiple processors, each processor performing a different task to process a block of data, the data being processed by each processor in turn. In response to a processor completing a task, that processor examines the next block of data from an upstream processor.

[0034] In at least some integrated circuits, a buffer such as a First-In-First-Out (FIFO) unit is used to hold a block of data processed by an upstream processor until the instant processor is ready. However, to ensure that the data held by the FIFO unit is ready, the instant processor checks a flag in the FIFO. Before processing the data held by the FIFO unit, the instant processor also checks another flag in the downstream FIFO to ensure that the downstream FIFO is ready to store the output data. At least some of such checking processes last for multiple clock cycles due to flag update delays. Most FIFO units are not designed for random access of stored data, which requires that all operations on a block be performed as a continuous sequence. Thus, in applications that perform non-sequential operations requiring random access, the downstream processor reads a block of data from the FIFO and then stores the block in a random access memory, which consumes more cycles in the transfer from the FIFO to the random access memory, and the random access memory consumes additional chip resources.

[0035] In at least some embodiments of the subject disclosure, an integrated circuit includes a random access memory shared between an upstream processor and a downstream processor, a read counter that stores a value representing the number of accessible data blocks stored in the memory, and a write counter that stores a value representing the number of pages of memory available for recording. In at least some embodiments, the read counter is in direct communication with the downstream processor, so that the read counter is readable by the downstream processor without consuming any additional clock cycles while waiting to determine whether the next data block is ready for processing. In at least some embodiments, the write counter is in direct communication with the upstream processor, so that the write counter is readable by the upstream processor without consuming any additional clock cycles while waiting to determine whether the memory has an available page in which to store the next data block.

[0036] 4 is a schematic diagram of an integrated circuit 430 utilizing paged buffering in accordance with at least some embodiments of the invention. The integrated circuit 430 includes an upstream processing section 431A and a downstream processing section 431B. The upstream processing section 431A includes an upstream processor 433A and a write counter 435. The downstream processing section 431B includes a downstream processor 433B, a read counter 436, and a random access memory (RAM) 437.

[0037] Upstream processor 433A is configured to communicate with write counter 435, read counter 436, and RAM 437. In at least some embodiments, upstream processor 433A is configured to retrieve counter value 440 from write counter 435. In at least some embodiments, upstream processor 433A is configured to output data block 441 and record data block 441 in RAM 437 in response to counter value 440 being greater than zero. In at least some embodiments, upstream processor 433A is configured to perform an upstream operation in response to determining that write counter 435 contains a value indicating at least one page of memory is available for recording. In at least some embodiments, upstream processor 433A is configured to perform an upstream operation including recording data block 441 in active write page 438 of at least three pages of memory 437. In at least some embodiments, upstream processor 433A is configured to record data block 441 in active write page 438 of at least three pages of memory 437 while downstream processor 433B reads data block 446 recorded in active read page 439 of memory 437. In at least some embodiments, upstream processor 433A is configured to send a decrement command 442 to write counter 435 and an increment command 443 to read counter 436. In at least some embodiments, upstream processor 433A is configured to perform operations in response to starting recording of data block 441, including adjusting write counter 435 to indicate page occupancy. In at least some embodiments, upstream processor 433A is further configured to perform operations in response to completing recording of data block 441, including adjusting read counter 436 to indicate page occupancy. In at least some embodiments, these increment / decrement commands cause the respective counters to be adjusted, e.g., the internally stored values ​​to be changed accordingly.In at least some embodiments, upstream processor 433A is configured to send write page update command 444 to RAM 437 in response to recording data block 441 in RAM 437. In at least some embodiments, upstream processor 433A is configured to update a write page address in memory 437 in response to completing the recording of data block 441. In at least some embodiments, write page update command 444 causes RAM 437 to indicate that a page subsequent to page 438 in which data block 441 is stored will become active for a subsequent record operation.

[0038] The downstream processor 433B is configured to communicate with the write counter 435, the read counter 436, and the RAM 437. In at least some embodiments, the downstream processor 433B is configured to retrieve a counter value 445 from the read counter 436. In at least some embodiments, the downstream processor 433B is configured to read a data block 446 from the RAM 437 in response to the counter value 445 being greater than zero. In at least some embodiments, the downstream processor 433B is configured to perform a downstream operation in response to determining that the read counter 436 contains a value indicating that at least one accessible data block is stored in the memory. In at least some embodiments, the downstream processor 433B is configured to perform a downstream operation including reading the data block 446 recorded in an active read page 439 of the memory 437. In at least some embodiments, downstream processor 433B is configured to send a decrement instruction 447 to read counter 436 and an increment instruction 448 to write counter 435 in response to reading data block 446 from RAM 437. In at least some embodiments, downstream processor 433B is configured to perform downstream operations including adjusting read counter 436 to indicate page freeing in response to initiating a read of data block 446. In at least some embodiments, downstream processor 433B is configured to process data block 446. In at least some embodiments, downstream processor 433B is further configured to perform downstream operations including adjusting write counter 435 to indicate page freeing in response to completing a read of data block 446. In at least some embodiments, these increment / decrement instructions cause the respective counters to be adjusted, e.g., their internally stored values ​​to be changed accordingly.In at least some embodiments, downstream processor 433B is configured to send a read page update command 449 to RAM 437 in response to reading data block 446 from RAM 437. In at least some embodiments, downstream processor 433B is configured to update a read page address in memory 437 in response to completing the read of data block 446. In at least some embodiments, read page update command 449 causes RAM 437 to indicate that a page subsequent to page 439 from which data block 446 was read becomes active for a subsequent read operation.

[0039] Write counter 435 is in upstream processing section 431A and is configured to communicate with upstream processor 433A and downstream processor 433B. In at least some embodiments, write counter 435 is a counter configured to store a single value, such as counter value 440. In at least some embodiments, write counter 435 is a write counter that stores counter value 440 indicating whether any pages of memory 437 are available for recording. In at least some embodiments, write counter 435 is configured to respond to instructions, such as decrease value instruction 442 and increase value instruction 448, and change the stored value accordingly. In at least some embodiments, write counter 435 is configured to respond to a request to read the stored value by transmitting the stored value. In at least some embodiments, write counter 435 is in direct communication with upstream processor 433A and is readable by upstream processor 433A without consuming any additional clock cycles waiting to determine whether RAM 437 has an available page for storing data block 441. In at least some embodiments, the write counter 435 is considered to be local to the upstream processor 433A and remote from the downstream processor 433B because the write counter 435 is quickly readable by the upstream processor 433A.

[0040] The read counter 436 is in the downstream processing section 431B and is configured to communicate with the upstream processor 433A and the downstream processor 433B. In at least some embodiments, the read counter 436 is a counter configured to store a single value, such as a counter value 445. In at least some embodiments, the read counter 436 is a read counter that stores a counter value 445 that indicates whether any accessible data blocks are stored in the memory 437. In at least some embodiments, the read counter 436 is configured to respond to instructions, such as a decrease value instruction 447 and an increase value instruction 443, and to change the stored value accordingly. In at least some embodiments, the read counter 436 is configured to respond to a request to read the stored value by transmitting the stored value. In at least some embodiments, the read counter 436 is in direct communication with the downstream processor 433B and is readable by the downstream processor 433B without consuming any additional clock cycles in waiting to determine whether the RAM 437 has a page storing the data block 446 ready for reading. In at least some embodiments, the read counter 436 is considered to be local to the downstream processor 433B and remote from the upstream processor 433A because the read counter 436 is rapidly readable by the downstream processor 433B.

[0041] RAM 437 is in communication with upstream processor 433A and downstream processor 433B. In at least some embodiments, RAM 437 is configured to allow reading and writing of data in any order, allowing upstream processor 433A to record data in data block 441 as the data is output, and allowing downstream processor 433B to read data in data block 446 as the data is required by the processing algorithm. In at least some embodiments, RAM 437 includes at least three pages. In other words, in at least some embodiments, RAM 437 includes a capacity sufficient to store at least three data blocks, such as data block 441 and data block 446. In at least some embodiments, the capacity of a page is large enough to store the maximum size of a data block according to the processing algorithm executed by integrated circuit 430. In at least some embodiments, RAM 437 is a random access memory having at least three pages, and the memory is configured to store a data block in each of the at least three pages. In at least some embodiments, RAM 437 is configured to designate one page as active for reading and a different page as active for writing, and in at least some embodiments, RAM 437 is configured to change the active read page designation or the active write page designation in response to instructions.

[0042] In at least some embodiments of the subject disclosure, the integrated circuit comprises a processor configured to process data while reading unprocessed data from an upstream random access memory and recording processed data in a downstream random access memory. Such embodiments comprise a read counter that stores a value representative of the number of accessible data blocks stored in the upstream memory and a write counter that stores a value representative of the number of pages of the downstream memory available for recording. In at least some embodiments, the read counter and the write counter are in direct communication with the processor such that the read counter and the write counter are readable by the processor within one clock cycle to determine both whether the upstream memory is ready for reading and whether the downstream memory is ready for recording.

[0043] 5 is a schematic diagram of another integrated circuit utilizing paged buffering in accordance with at least some embodiments of the invention. Integrated circuit 550 includes upstream processing section 531A and downstream processing section 531B. Upstream processing section 531A includes processor 533, write counter 535, read counter 536, and upstream RAM 537A. Downstream processing section 531B includes downstream RAM 537B.

[0044] Processor 533 is in communication with write counter 535, read counter 536, upstream RAM 537A, and downstream RAM 537B. In at least some embodiments, processor 533 is a processor, microprocessor, programmable logic circuit, or the like, configured to retrieve counter value 550 from read counter 536 and counter value 551 from write counter 535. In at least some embodiments, processor 533 is configured to, in response to counter value 550 being greater than zero and counter value 551 also being greater than zero, read a first data block 552 from upstream RAM 537A, perform operations to process first data block 552 to generate a second data block 554, and record second data block 554 in downstream RAM 537B. In at least some embodiments, counter value 550 being greater than zero indicates to processor 533 that upstream RAM 537A has at least one data block ready to be read. In at least some embodiments, processor 533 is configured to perform an operation in response to determining that read counter 536 includes a value indicating that at least one accessible data block is stored in the upstream memory and write counter 535 includes a value indicating that at least one downstream page of the downstream memory is available for recording. In at least some embodiments, processor 533 is configured to perform an operation including reading a first data block 552 recorded in upstream memory 537A. In at least some embodiments, a state in which counter value 551 is greater than zero indicates to processor 533 that downstream RAM 537B has at least one data block available for recording. In at least some embodiments, processor 533 is configured to send a decrease value instruction 553 to read counter 536 and an increase value instruction 556A to the upstream write counter.In at least some embodiments, the processor 533 is configured to perform operations including adjusting the read counter 536 to indicate a page free. In at least some embodiments, the processor 533 is configured to adjust the remote write counter to indicate a page free in response to the first data block 552 being read. In at least some embodiments, the processor 533 is configured to perform operations including processing the first data block 522 to generate a second data block 554. In at least some embodiments, the processor 533 is configured to perform operations including recording the second data block 554 in downstream memory 537B. In at least some embodiments, the processor 533 is configured to send a decrease command 555 to the write counter 535 and an increase command 558A to the downstream read counter. In at least some embodiments, the processor 533 is configured to decrease the write counter 535. In at least some embodiments, the processor 533 is configured to adjust the remote read counter to indicate a page occupancy in response to the second data block 554 being recorded. In at least some embodiments, these increment / decrement commands cause the respective counters to be adjusted, e.g., the internally stored values ​​to be changed accordingly. In at least some embodiments, the processor 533 is configured to send a read page update command 557 to the upstream RAM 537A in response to reading the first data block 552 from the upstream RAM 537A. In at least some embodiments, the processor 533 is configured to update a read page address in the upstream memory 537A in response to the reading of the first data block 552 being completed. In at least some embodiments, the read page update command 557 causes the upstream RAM 537A to indicate that a subsequent page of the page 539 from which the first data block 552 was read is to become active for a subsequent read operation.In at least some embodiments, the processor 533 is configured to send a write page update command 559 to the downstream RAM 537B in response to recording the second data block 554 in the downstream RAM 537B. In at least some embodiments, the processor 533 is configured to update a write page address in the downstream memory 537B in response to completing the recording of the second data block 554. In at least some embodiments, the write page update command 559 causes the downstream RAM 537B to indicate that a subsequent page of the page 538 in which the second data block 554 is stored becomes active for a subsequent record operation.

[0045] The write counter 535 is in the upstream processing section 531A and is configured to communicate with the processor 533. In at least some embodiments, the write counter 535 is a counter configured to store a single value, such as a counter value 551. In at least some embodiments, the write counter 535 is configured to respond to instructions, such as a decrease value instruction 555 and an increase value instruction 558B, to change the stored value accordingly. In at least some embodiments, the write counter 535 is configured to respond to a request to read the stored value by transmitting the stored value. In at least some embodiments, the write counter 535 is in direct communication with the processor 533 and is readable by the processor 533 within one clock cycle to determine whether the downstream RAM 537B has an available page for storing the second data block 554. In at least some embodiments, because the write counter 535 is rapidly readable by the processor 533, the write counter 535 is considered to be local to the processor 533 and remote from the processors of other sections, such as the downstream section 531B. In at least some embodiments, the write counter 535 is a local write counter configured to store a value indicating whether any downstream pages of the downstream memory 537B are available for recording.

[0046] The read counter 536 is in the upstream processing section 531A and is configured to communicate with the processor 533. In at least some embodiments, the read counter 536 is a counter configured to store a single value, such as counter value 550. In at least some embodiments, the read counter 536 is configured to respond to instructions, such as decrement value instruction 553 and increment value instruction 556B, to change the stored value accordingly. In at least some embodiments, the read counter 536 is configured to respond to a request to read the stored value by transmitting the stored value. In at least some embodiments, the read counter 536 is in direct communication with the processor 533 and is readable by the processor 533 within one clock cycle to determine whether the upstream RAM 537A has a page storing the first data block 552 ready for reading. In at least some embodiments, because the read counter 536 is rapidly readable by the processor 533, the read counter 536 is considered to be local to the processor 533 and remote from the processors of other sections, such as the downstream section 531B. In at least some embodiments, read counter 536 is a local read counter configured to store a value indicating whether any accessible data blocks are stored in upstream memory 537A.

[0047] The upstream RAM 537A is in communication with the processor 533. In at least some embodiments, the upstream RAM 537A is configured to allow data to be read and written in any order and to allow the processor 533 to read data of the data block 552 when the data is required by the processing algorithm. In at least some embodiments, the upstream RAM 537A includes at least three pages. In other words, in at least some embodiments, the upstream RAM 537A includes a capacity sufficient to store at least three data blocks, such as the first data block 552. In at least some embodiments, the upstream random access memory 537A has at least three upstream pages, and the upstream memory 537A is configured to store a data block in each of the at least three upstream pages. In at least some embodiments, the capacity of a page is large enough to store a maximum size of a data block according to the processing algorithm executed by the integrated circuit 550. In at least some embodiments, the upstream RAM 537A is configured to indicate one page as active for reading and one different page as active for writing. In at least some embodiments, the upstream RAM 537A is configured to change the active read page indication or the active write page indication in response to an instruction from the processor 533, such as a write page update 557.

[0048] The downstream RAM 537B is in communication with the processor 533. In at least some embodiments, the downstream RAM 537B is configured to allow data to be read and written in any order and to allow the processor 533 to record the data of the second data block 554 as the data is output. In at least some embodiments, the downstream RAM 537B includes at least three pages. In other words, in at least some embodiments, the downstream RAM 537B includes a capacity sufficient to store at least three data blocks, such as the second data block 554. In at least some embodiments, the downstream random access memory 537B has at least three downstream pages, and the downstream memory 537B is configured to store a data block in each of the at least three downstream pages. In at least some embodiments, the capacity of a page is large enough to store a maximum size of a data block according to a processing algorithm executed by the integrated circuit 550. In at least some embodiments, the downstream RAM 537B is configured to indicate one page as active for reading and one different page as active for writing. In at least some embodiments, the downstream RAM 537B is configured to change the active read page indication or the active write page indication in response to instructions from the processor 533, such as a read page update 559.

[0049] 6 is a schematic diagram of an integrated circuit encoder 601 utilizing a buffer for LDPC data encoding in accordance with at least one embodiment of the present invention. The integrated circuit encoder 601 includes a segmentation section 631A, an encoding section 631B, a concatenation section 631C, and a parameter section 631D. Each of the segmentation section 631A, the encoding section 631B, the concatenation section 631C, and the parameter section 631D includes a processor and one or more buffers.

[0050] Segmentation section 631A includes buffer 632A, buffer 632B, and segmentation processor 610. In at least some embodiments, buffer 632A stores original data blocks until segmentation processor 610 has completely read the original data blocks. In at least some embodiments, buffer 632B stores parameter values ​​associated with segmentation of the original data blocks. In at least some embodiments, buffer 632B stores parameter values ​​received from parameter processor 619 until segmentation processor 610 has completely read the parameter values ​​associated with a given original data block.

[0051] The encoding section 631B includes a buffer 632C, a buffer 632D, and an encoding processor 613. In at least some embodiments, the buffer 632C stores data segments received from the segmentation processor 610 corresponding to original data blocks until the encoding processor 613 has completely read the data segments. In at least some embodiments, the buffer 632D stores parameter values ​​associated with encoding the data segments. In at least some embodiments, the buffer 632D stores parameter values ​​received from the parameter processor 619 until the encoding processor 613 has completely read the parameter values ​​associated with the data segment corresponding to a given original data block.

[0052] The concatenation section 631C includes a buffer 632E, a buffer 632F, a buffer 632G, and a concatenation processor 616. In at least some embodiments, the buffer 632E stores parity segments corresponding to original data blocks received from the encoding processor 613 until the concatenation processor 616 has completely read the parity segments. In at least some embodiments, the buffer 632F stores data segments corresponding to original data blocks received from the segmentation processor 610 until the concatenation processor 616 has completely read the data segments. In at least some embodiments, the buffer 632G stores parameter values ​​associated with concatenating the data segments and the parity segments. In at least some embodiments, the buffer 632G stores parameter values ​​received from the parameter processor 619 until the concatenation processor 616 has completely read the parameter values ​​associated with the data segments and the parity segments corresponding to a given original data block.

[0053] The parameter section 631D includes a buffer 632H and a parameter processor 619. In at least some embodiments, the buffer 632H stores parameter values ​​associated with encoding an original data block into an encoded data block. In at least some embodiments, the buffer 632H stores parameter values ​​until the parameter processor 619 has completely read the parameter values ​​associated with encoding a given original data block into an encoded data block. In at least some embodiments, the buffer 632H stores parameter values ​​until the parameter processor 619 has completely read the parameter values ​​for a single one of the segmentation processor 610, the encoding processor 613, and the concatenation processor 616 to perform the respective operations associated with the given original data block. In at least some embodiments, the buffer 632H stores parameter values ​​until the parameter processor 619 has completely read and transformed a set of parameter values ​​for all of the segmentation processor 610, the encoding processor 613, and the concatenation processor 616 to perform the respective operations associated with the given original data block.

[0054] Each of the segmentation processor 610, the encoding processor 613, the concatenation processor 616, and the parameter processor 619 are substantially similar in structure and function to the segmentation processor 210, the encoding processor 213, the concatenation processor 216, and the parameter processor 219 of Figure 2, respectively.

[0055] In at least some embodiments, the buffers in some sections are FIFO units and the buffers in other sections are RAM. In at least some embodiments, the section that includes a RAM buffer includes similar structure and performs similar functions as downstream processing section 431B of FIG. 4 and upstream processing section 531A of FIG. 5. In at least some embodiments, adjacent sections that include a RAM buffer include similar structure and perform similar functions as upstream processing section 431A and downstream processing section 431B of FIG. 4, respectively, and upstream processing section 531A and downstream processing section 531B of FIG. 5, respectively. For example, in at least some embodiments in which buffer 632C is a RAM buffer, segmentation section 631A includes similar structure and performs similar functions as upstream processing section 431A of FIG. 4 and upstream processing section 531A of FIG. 5, while encoding section 631B includes similar structure and performs similar functions as downstream processing section 431B of FIG. 4 and downstream processing section 531B of FIG. 5.

[0056] 7 is a schematic diagram of an encoding section 731 of an integrated circuit encoder for LDPC data encoding utilizing paged buffering in accordance with at least one embodiment of the present invention. The encoding section 731 includes an encoding processor 713, a write counter 735, a read counter 736A, a read counter 736B, a RAM 737A, and a RAM 737B.

[0057] In at least some embodiments, read counter 736A and RAM 737A are in communication with a segmentation processor in the segmentation section. In at least some embodiments, read counter 736B and RAM 737B are in communication with a parameter processor in the parameter section. In at least some embodiments, RAM 737B is a parameter random access memory having at least three parameter pages, and parameter memory 737B is configured to store parameter value blocks in each parameter page of the at least three parameter pages. In at least some embodiments, read counter 736B is a local parameter read counter configured to store a value indicating whether any accessible data blocks are stored in parameter memory 737B.

[0058] Encoding section 731 shows a detailed example in which buffer 632C and buffer 632D of FIG. 6 are RAM buffers in RAM 737A and RAM 737B, respectively. Except as described below, the functional interactions between encoding processor 713, write counter 735, read counter 736A, and RAM 737A are substantially similar to the functional interactions between processor 533, write counter 535, read counter 536, and upstream RAM 537A of FIG. 5. In at least some embodiments, encoding processor 713 is configured to read data segment 711 from RAM 737A in response to the counter value read from read counter 736A being a value greater than zero. In at least some embodiments, encoding processor 713 is configured to read data segment 711 from active read page 739A of RAM 737A while segmentation processor records data segments of a subsequent data block in active write page 738A of RAM 737A. In at least some embodiments, the encoding processor 713 is configured to perform operations to process the data segment 711 to generate a parity check segment 714 and output the parity check segment 714, all in response to the counter value read from the write counter 735 being a value greater than zero. In at least some embodiments, the encoding processor 713 is configured to read parameter data 715 from the RAM 737B in response to the counter value read from the read counter 736B being a value greater than zero. In at least some embodiments, the encoding processor 713 is further configured to process the data segment 711 according to the parameter value block. In at least some embodiments, the encoding processor 713 is configured to read the parameter data 715 from the active read page 739B of the RAM 737B while the parameter processor writes parameter data for a subsequent data block to the active write page 738B of the RAM 737B.In at least some embodiments, the encoding processor 713 is configured to perform an action in response to determining that the read counter 736A includes a value indicating that at least one accessible block of data is stored in the RAM 737A, the write counter 735 includes a value indicating that at least one page of the downstream RAM is available for recording, and the read counter 736B includes a value indicating that at least one accessible block of parameter values ​​is stored in the RAM 737B. In at least some embodiments, the encoding processor 713 is configured to read a block of parameter values ​​715 recorded in the parameter memory 737B. In at least some embodiments, the encoding processor 713 is configured to send a decrease value command to the read counter 736A and an increase value command to the upstream write counter. In at least some embodiments, the encoding processor 713 is configured to send a write page update command to the RAM 737A in response to reading the data segment 711 from the RAM 737A. In at least some embodiments, the encoding processor 713 is configured to send a decrease value instruction to the write counter 735 and an increase value instruction to the downstream read counter. In at least some embodiments, the encoding processor 713 is configured to send a read page update instruction to the downstream RAM in response to recording the parity check segment 714 in the downstream RAM. In at least some embodiments, the encoding processor 713 is configured to send a single instruction that is received by the downstream read counter as an increase value instruction and by the downstream RAM as a read page update instruction.

[0059] 8 is an operational flow for LDPC data decoding using paged buffering in accordance with at least some embodiments of the present invention. The operational flow provides a method of LDPC data decoding using paged buffering. In at least some embodiments, the method is performed by an integrated circuit, such as integrated circuit decoder 308 shown in FIG.

[0060] At S860, the segmentation processor segments the LDPC encoded data block. In at least some embodiments, the segmentation processor segments the low density parity check (LDPC) encoded data block of probability values ​​by dividing the encoded data block into a plurality of data probability value segments and a plurality of parity probability value segments, each probability value of the encoded data block representing a likelihood between binary values. In at least some embodiments, the segmentation processor divides the encoded data block into one or more segments of a predetermined length. In at least some embodiments, the segmentation processor divides the encoded data block into segments having a length according to the length of the encoded data block. In at least some embodiments, the segmentation processor performs de-interleaving and rate matching.

[0061] At S863, the decoding processor decodes the data probability value segment. In at least some embodiments, the decoding processor applies a parity check matrix to the data probability value segment and the parity probability value segment to generate a decoded binary value segment. In at least some embodiments, the decoding processor applies an LDPC parity check matrix to the data probability value segment and the parity probability value segment to generate a decoded binary value segment. In at least some embodiments, the decoding processor applies one or more cyclic shifts to the data probability value segment and the parity probability value segment according to the parity check matrix to generate a decoded binary value segment. In at least some embodiments, the decoding processor compares the binary values ​​in a subset of values ​​of corresponding data probability value segments and parity probability value segments to ensure that the values ​​sum to an even number. In at least some embodiments, the decoding processor decodes the encoded data block by adjusting the probability values ​​of the encoded data block based on a parity check matrix according to an iteration variable accuracy parameter, the parity check matrix defining the correspondence between the data probability value segments and the parity probability value segments, where the iteration variable accuracy parameter represents a trade-off between accuracy and computational efficiency. In at least some embodiments, the decoding processor performs the operational flow shown in FIG. 9, which is described below.

[0062] At S869, the concatenation processor concatenates the likely binary values. In at least some embodiments, the concatenation processor concatenates the likely binary values ​​that fill a parity check matrix associated with the probability values ​​of each data probability value segment to form a decoded data block. In at least some embodiments, the concatenation processor concatenates the likely binary value segments to generate a decoded data block. In at least some embodiments, the concatenation processor concatenates the likely binary value segments to form the same format as the original data block.

[0063] 9 is an operational flow for data probability value segment decoding utilizing paged buffering in accordance with at least one embodiment of the present invention. The operational flow provides a method of data probability value segment decoding utilizing paged buffering. In at least some embodiments, the method is performed by a decode processor, such as one of the decode processors 323 shown in FIG.

[0064] At S970, the decode processor checks the buffer. In at least some embodiments, the decode processor determines whether the upstream buffer has data probability segments of the encoded data block that are completely recorded and ready to be read by the decode processor. In at least some embodiments, the decode processor determines whether the downstream buffer has pages that are ready for recording of likely binary values ​​by the decode processor. In at least some embodiments, the decode processor determines whether the parameter buffer has parameter values ​​for decoding the encoded data block that are completely recorded and ready to be read by the decode processor. In at least some embodiments, the decode processor performs the operational flow shown in FIG. 10, which is described below.

[0065] At S980, the decoding section processes the data block. In at least some embodiments, the decoding processor processes the first data block to generate a second data block. In at least some embodiments, the processing of the first data block is in accordance with the parameter value block. In at least some embodiments, the decoding processor applies a parity check matrix to the data probability value segments and the parity probability value segments to generate decoded binary value segments. In at least some embodiments, the decoding processor applies an LDPC parity check matrix to the data probability value segments and the parity probability value segments to generate decoded binary value segments. In at least some embodiments, the decoding processor applies one or more cyclic shifts to the data probability value segments and the parity probability value segments according to the parity check matrix to generate decoded binary value segments. In at least some embodiments, the decoding processor compares the binary values ​​in a subset of values ​​of corresponding data probability value segments and parity probability value segments to ensure that the values ​​sum to an even number. In at least some embodiments, the decoding processor decodes the encoded data block by adjusting the probability values ​​of the encoded data block based on a parity check matrix according to an iteration variable accuracy parameter, the parity check matrix defining a correspondence between data probability value segments and parity probability value segments, where the iteration variable accuracy parameter represents a trade-off between accuracy and computational efficiency. In at least some embodiments, the decoding processor performs the operational flow shown in FIG. 11, which is described below.

[0066] At S990, the decode section confirms completion. In at least some embodiments, the decode processor issues an increment command to an upstream write counter to indicate that the upstream buffer from which the data probability segment was read has at least one page ready for recording. In at least some embodiments, the decode processor issues a page read command to the upstream buffer to indicate that a subsequent page of the page from which the data probability segment was read is active for a subsequent read operation. In at least some embodiments, the decode processor issues an increment command to a downstream read counter to indicate that the downstream buffer from which the likely binary value was recorded is now ready to be read. In at least some embodiments, the decode processor issues a page write command to the downstream buffer to indicate that a subsequent page of the page from which the likely binary value was recorded is active for a subsequent record operation. In at least some embodiments, the decode processor executes the operational flow shown in FIG. 12, which is described below.

[0067] 10 is an operational flow for buffer checking in accordance with at least one embodiment of the present invention. The operational flow provides a method of buffer checking. In at least some embodiments, the method is performed by a decode processor, such as one of the decode processors 323 shown in FIG.

[0068] At S1073, the decode processor determines whether the parameter read counter has a non-zero value. In at least some embodiments, the decode processor retrieves a counter value from the parameter read counter. In response to a determination that the parameter read counter does not have a non-zero value, the operational flow returns to the parameter read counter determination at S1073. In response to a determination that the parameter read counter has a non-zero value, the operational flow proceeds to the data block read counter determination at S1076.

[0069] At S1076, the decode processor determines whether the data block read counter has a non-zero value. In at least some embodiments, the decode processor retrieves the counter value from the data block read counter. In response to a determination that the data block read counter does not have a non-zero value, the operational flow returns to the data block read counter determination at S1076. In response to a determination that the data block read counter has a non-zero value, the operational flow proceeds to the data block write counter determination at S1079.

[0070] At S1079, the decode processor determines whether the write counter has a non-zero value. In at least some embodiments, the decode processor retrieves the counter value from the data block write counter. In response to a determination that the data block write counter does not have a non-zero value, the operational flow returns to the data block write counter determination at S1079. In response to a determination that the data block write counter has a non-zero value, the operational flow ends.

[0071] In this embodiment, operations S1073, S1076, and S1079 are performed sequentially, although these operations may be performed in any order in other embodiments. In at least some embodiments, these operations are performed simultaneously.

[0072] 11 is an operational flow for data block processing according to at least one embodiment of the present invention. The operational flow provides a method of data block processing. In at least some embodiments, the method is performed by a decode processor, such as one of the decode processors 323 shown in FIG. 3. In at least some embodiments, the decode processor performs the method in response to determining that a local read counter of the integrated circuit includes a value indicating that at least one accessible data block is stored in an upstream memory of the integrated circuit and that a local write counter of the integrated circuit includes a value indicating that at least one downstream page of a downstream memory of the integrated circuit is available for recording. In at least some embodiments, the decode processor performs the method further in response to determining that a local parameter read counter of the integrated circuit includes a value indicating that at least one accessible parameter value block is stored in a parameter memory of the integrated circuit.

[0073] At S1182, the decode processor decrements one or more local read counters. In at least some embodiments, the decode processor adjusts the local read counters. In at least some embodiments, the decode processor issues a decrement command to a local data read counter to indicate that the upstream buffer being read has one less unread data block. In at least some embodiments, the decode processor issues a decrement command to a local parameter read counter to indicate that the parameter buffer being read has one less unread parameter value block.

[0074] At S1183, the decode processor decrements a local write counter. In at least some embodiments, the decode processor adjusts the local write counter to indicate page occupancy. In at least some embodiments, the decode processor issues a decrement command to the local data write counter to indicate that the downstream buffer in which the output is being recorded has one less page available for recording.

[0075] At S1184, the decode processor begins reading. In at least some embodiments, the decode processor reads the first data block recorded in the upstream memory. In at least some embodiments, the decode processor begins reading the first data block from the upstream buffer and reading the parameter values ​​from the parameter buffer. In at least some embodiments, the decode processor reads the parameter value block recorded in the parameter random access memory. In at least some embodiments, the decode processor begins reading the first data block of the data probability value segment and the parity probability value segment.

[0076] At S1185, the decode processor begins processing. In at least some embodiments, the decode processor begins processing the first data block to generate a second data block. In at least some embodiments, the decode processor reads portions of the first data block while processing other portions of the first data block. In at least some embodiments, the decode processor re-reads portions of the first data block and parameter values. In at least some embodiments, the decode processor first reads all parameter values ​​and then begins reading and processing the first data block.

[0077] At S1186, the decode processor begins recording the output. In at least some embodiments, the decode processor records, by the processor, the second data block in a downstream memory of the integrated circuit. In at least some embodiments, the decode processor begins recording the second data block in the downstream buffer. In at least some embodiments, the decode processor begins recording the second data block of likely binary values. In at least some embodiments, the decode processor begins recording the second data block in the downstream buffer in response to starting processing the first data block read from the upstream buffer. In at least some embodiments, the decode processor overwrites a portion of the second data block already recorded in response to processing the updated data. In at least some embodiments, the decode processor records a portion of the second data block while processing a portion of the first data block.

[0078] At S1188, the decode processor determines whether processing is complete. In at least some embodiments, the decode processor continues to read and record the output until processing is complete. In at least some embodiments, the decode processor determines processing is complete in response to performing each of a set of tasks. In at least some embodiments, the decode processor determines processing is complete in response to likely binary values ​​associated with the probability values ​​filling a parity check matrix. In at least some embodiments, the decode processor determines processing is complete in response to performing a threshold number of decoding iterations. In response to determining that processing is not complete, the operational flow returns to the processing completion determination at S1188. In response to determining that processing is complete, the operational flow ends.

[0079] 12 is an operational flow for confirming completion in accordance with at least one embodiment of the present invention. The operational flow provides a method for confirming completion. In at least some embodiments, the method is performed by a decode processor, such as one of the decode processors 323 shown in FIG.

[0080] At S1292, the decode processor completes the read. In at least some embodiments, the decode processor determines that decoding the data block does not require further reading of data from the upstream buffer. In at least some embodiments, the decode processor determines that further reading of parameter values ​​is not required.

[0081] At S1293, the decode processor increments one or more remote write counters. In at least some embodiments, the decode processor adjusts the remote write counter to indicate a page free in response to completing the read of the first data block. In at least some embodiments, the decode processor issues an increment command to an upstream write counter to indicate that the upstream buffer from which the data probability segment was read has one more page ready for recording.

[0082] At S1294, the decode processor updates the read page address. In at least some embodiments, the decode processor updates the read page address of the upstream memory in response to the reading of the first data block being completed. In at least some embodiments, the decode processor issues a read page update command to the upstream buffer to indicate that a page subsequent to the page from which the first data block was read becomes active for a subsequent read operation.

[0083] In S1296, the decode processor completes the recording. In at least some embodiments, the decode processor determines that all plausible binary values ​​have been recorded in the downstream buffer.

[0084] At S1297, the decode processor increments the remote read counter. In at least some embodiments, the decode processor adjusts the remote read counter to indicate page occupancy in response to completing the recording of the second data block. In at least some embodiments, the decode processor issues an increment command to the downstream read counter to indicate that the downstream buffer in which the likely binary value was recorded has one more page ready to be read.

[0085] At S1298, the decode processor updates the write page address. In at least some embodiments, the decode processor updates the write page address of the downstream memory in response to completing the recording of the second data block. In at least some embodiments, the decode processor issues a write page update command to the downstream buffer to indicate that a page subsequent to the page in which the second data block was stored becomes active for the subsequent recording operation.

[0086] In at least some embodiments, the apparatus is a separate device capable of processing logical functions to perform the operations herein. In at least some embodiments, the controller and storage unit need not be entirely separate devices, and in some embodiments share circuitry or one or more computer-readable media. In at least some embodiments, the storage unit includes a hard drive that stores both computer-executable instructions and data accessed by the controller, and the controller includes a combination of a central processing unit (CPU) and RAM into which the computer-executable instructions can be copied in whole or in part for execution by the CPU during performance of the operations herein.

[0087] At least some embodiments are described with reference to flow charts and block diagrams, whose blocks represent (1) steps of a process in which an operation is performed, or (2) sections of a controller responsible for performing an operation. In at least some embodiments, certain steps and sections are implemented by dedicated circuitry, programmable circuitry provided with computer readable instructions stored on a computer readable medium, and / or a processor provided with computer readable instructions stored on a computer readable medium. In at least some embodiments, the dedicated circuitry includes digital and / or analog hardware circuitry, including integrated circuits (ICs) and / or discrete circuits. In at least some embodiments, the programmable circuitry includes reconfigurable hardware circuitry, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), etc., including logical AND, OR, XOR, NAND, NOR and other logic operations, flip-flops, registers, memory elements, etc.

[0088] In at least some embodiments, a computer readable storage medium includes a tangible device capable of maintaining and storing instructions for use by an instruction execution device. In some embodiments, a computer readable storage medium includes, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer readable storage media includes the following: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge structures in grooves on which instructions are recorded, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be construed as being a transitory signal per se, such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable), or an electrical signal transmitted through a wire.

[0089] In at least some embodiments, the computer readable program instructions described herein can be downloaded from a computer readable storage medium to the respective computing / processing device or to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. In at least some embodiments, the network includes copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. In at least some embodiments, a network adapter card or network interface in each computing / processing device receives the computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing / processing device.

[0090] In at least some embodiments, the computer readable program instructions that perform the operations described above are either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including object oriented programming languages, such as Smalltalk, or C++, and traditional procedural programming languages, such as the "C" programming language or similar programming languages. In at least some embodiments, the computer readable program instructions are executed entirely on the user's computer, partially on the user's computer as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In at least some embodiments, in the latter scenario, the remote computer is connected to the user's computer through any type of network, including a local area network (LAN) or wide area network (WAN), or a connection is made to an external computer (e.g., through the Internet using an Internet Service Provider). In at least some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), executes computer readable program instructions by utilizing state information of the computer readable program instructions to individualize the electronic circuitry to perform aspects of the invention.

[0091] Although the embodiments of the present invention have been described, the scope of any subject matter described in the claims is not limited to the above-described embodiments. Those skilled in the art will understand that various modifications and improvements to the above-described embodiments are possible. Those skilled in the art will also understand that the scope of the claims includes embodiments to which such modifications or improvements have been made.

[0092] The operations, procedures, steps, and stages of each process performed by the apparatus, system, program, and method shown in the claims, embodiments, or figures can be performed in any order, unless the order is indicated by "prior to" or "before" or the like, and unless output from a previous process is used in a later process. Even if a process flow is described in the claims, embodiments, or figures using phrases such as "first" or "next," such description does not necessarily mean that the processes must be performed in the order described.

[0093] In at least some embodiments, integrated circuit data stream processing utilizing paged buffering is performed by an integrated circuit including an upstream random access memory, a local read counter, a downstream random access memory, a local write counter, and a processor. The local read counter is configured to store a value indicative of whether any accessible data blocks are stored in the upstream memory. The local write counter is configured to store a value indicative of whether any downstream pages of the downstream memory are available for recording. The processor is configured to adjust the local read counter to indicate a page release, adjust the local write counter to indicate a page occupancy, read a first data block recorded in the upstream memory, process the first data block to generate a second data block, and record the second data block in the downstream memory.

[0094] The foregoing has outlined features of several embodiments so that those skilled in the art may better understand the aspects of the present disclosure. Those skilled in the art should appreciate that the present disclosure may be readily used as a basis for designing or modifying other processes and structures for carrying out the same purposes and / or achieving the same advantages as the embodiments introduced herein. Those skilled in the art should also recognize that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations of the present disclosure are possible without departing from the spirit and scope of the present disclosure.

Claims

1. an upstream random access memory having at least three upstream pages, the upstream random access memory configured to store a data block in each upstream page of the at least three upstream pages; a local read counter configured to store a value indicating whether any accessible data blocks have been recorded in the upstream random access memory; a downstream random access memory having at least three downstream pages, said downstream random access memory configured to store a data block in each downstream page of said at least three downstream pages; a local write counter configured to store a value indicating whether any downstream pages of the downstream random access memory are available for recording; 11. A processor configured to perform an operation in response to determining that the local read counter includes a value indicating that at least one accessible data block is stored in the upstream random access memory and the local write counter includes a value indicating that at least one downstream page of the downstream random access memory is available for recording, the operation comprising: adjusting the local read counter to indicate a page free; adjusting said local write counter to indicate page occupancy; reading a first data block recorded in the upstream random access memory; processing the first data block to generate a second data block; and storing said second block of data in said downstream random access memory. A processor having 1. An integrated circuit comprising:

2. The processor is further configured to adjust a remote write counter to indicate a page release in response to the reading of the first data block being completed; The processor is further configured to adjust a remote read counter to indicate page occupancy in response to the recording of the second data block being completed.

10. The integrated circuit of claim 1.

3. The processor is further configured to update a read page address of the upstream random access memory in response to the reading of the first data block being completed; The processor is further configured to update a write page address of the downstream random access memory in response to the recording of the second data block being completed.

10. The integrated circuit of claim 1.

4. a parameter random access memory having at least three parameter pages, said parameter random access memory configured to store a parameter value block in each parameter page of said at least three parameter pages; a local parameter read counter configured to store a value indicative of whether any accessible parameter value blocks are stored in said parameter random access memory; Further comprising: wherein the processor is further configured to perform the operation in response to determining that the local parameter read counter contains a value indicating that at least one accessible parameter value block is stored in the parameter random access memory; wherein the operation further comprises the step of reading the parameter value block stored in the parameter random access memory; wherein the processor is further configured to process the first data block according to the parameter value block.

10. The integrated circuit of claim 1.

5. The processor is a segmentation processor configured to divide the original data block of the first data block into a plurality of data segments in the second data block of one or more predetermined lengths defined by the parameter value block.

5. The integrated circuit of claim 4.

6. the processor is an encoding processor configured to apply a parity check matrix in the parameter value block to a plurality of data segments in the first data block to generate parity segments in the second data block.

5. The integrated circuit of claim 4.

7. The processor is a concatenation processor configured to concatenate a plurality of data segments in the first data block with a plurality of parity segments to generate an encoded data block of the second data block.

5. The integrated circuit of claim 4.

8. the processor is a segmentation processor configured to divide the coded data probability value block of the first data block into a plurality of data probability value segments in the second data block and a plurality of parity probability value segments in the second data block of one or more predetermined lengths defined by the parameter value block.

5. The integrated circuit of claim 4.

9. the processor is a decoding processor configured to adjust probability values ​​of encoded data blocks of the first data block based on a parity check matrix in the parameter value block to generate likely binary values ​​in the second data block.

5. The integrated circuit of claim 4.

10. The processor is a concatenation processor configured to concatenate a plurality of decoded binary value segments in the first data block to generate a decoded data block of the second data block.

5. The integrated circuit of claim 4.

11. a random access memory having at least three pages, said random access memory configured to store a block of data in each page of said at least three pages; a read counter that stores a value indicating whether any accessible data blocks are stored in said random access memory; a write counter that stores a value indicating whether any page of said random access memory is available for recording; an upstream processor configured to perform an upstream operation in response to determining that the write counter contains a value indicating that at least one page of the random access memory is available for recording, the upstream operation comprising: adjusting the write counter to indicate page occupancy; recording a first block of data in a first page of the at least three pages of the random access memory; and and adjusting the read counter to indicate page occupancy, further responsive to the recording of the first data block being completed. an upstream processor having a downstream processor configured to, in response to determining that the read counter contains a value indicating that at least one accessible data block is stored in the random access memory, perform a downstream operation, the downstream operation comprising: adjusting the read counter to indicate a page free; reading the first data block recorded in the first page of the random access memory; processing the first block of data; and and further responsive to the reading of the first data block being completed, adjusting the write counter to indicate a page release. A downstream processor having 1. An integrated circuit comprising:

12. The upstream processor is further configured to record a second data block in a second page of the at least three pages of the random access memory while the downstream processor reads the first data block recorded in the first page of the random access memory.

12. The integrated circuit of claim 11.

13. the upstream processor in direct communication with the write counter; The downstream processor is in direct communication with the read counter.

12. The integrated circuit of claim 11.

14. The upstream processor is further configured to update a write page address of the random access memory in response to the recording of the first data block being completed; The downstream processor is further configured to update a read page address of the random access memory in response to completing the reading of the first data block.

12. The integrated circuit of claim 11.

15. the upstream processor is a segmentation processor configured to divide the original data block into a plurality of data segments in a second data block; The downstream processor is an encoding processor configured to apply a parity check matrix to a plurality of data segments in the first data block to generate parity segments.

15. The integrated circuit of claim 14.

16. the upstream processor is an encoding processor configured to apply a parity check matrix to a plurality of data segments to generate parity segments within a second data block; The downstream processor is a concatenation processor configured to concatenate a plurality of data segments in the first data block with a plurality of parity segments in the first data block to generate an encoded data block.

15. The integrated circuit of claim 14.

17. performing an action in response to a processor of an integrated circuit determining that a local read counter of the integrated circuit contains a value indicating that at least one accessible data block is stored in an upstream memory of the integrated circuit and a local write counter of the integrated circuit contains a value indicating that at least one downstream page of a downstream memory of the integrated circuit is available for recording. and wherein the operations include: adjusting the local read counter to indicate a page free; adjusting said local write counter to indicate page occupancy; reading a first data block recorded in the upstream memory; processing the first data block to generate a second data block; and recording said second block of data in a downstream memory of said integrated circuit; The method comprising:

18. adjusting a remote write counter to indicate a page release in response to the reading of the first data block being completed; and adjusting a remote read counter to indicate page occupancy in response to said recording of said second data block being completed. The method of claim 17 further comprising:

19. updating a read page address of the upstream memory in response to the reading of the first data block being completed; and updating a write page address of the downstream memory in response to the recording of the second data block being completed. The method of claim 17 further comprising:

20. The operations further include reading a block of parameter values ​​stored in a parameter random access memory of the integrated circuit; The step of performing the operation is further responsive to determining that a local parameter read counter contains a value indicating that at least one accessible parameter value block is stored in the parameter random access memory; The processing of the first data block is in accordance with the parameter value block.

20. The method of claim 17.

Citation Information

Patent Citations

  • Storage device, computer system, and data processing method for storage device

    JP2008146253A

  • Optimizing processor memory via page access count.

    JP2015534200A

  • Memory system

    JP2020042512A

  • Systems, methods, and apparatus for page migration in memory systems

    US20220382478A1