Browse Prior Art Database

OSD DATABASE MEMORY SAVING

IP.com Disclosure Number: IPCOM000021385D
Original Publication Date: 2000-Nov-01
Included in the Prior Art Database: 2004-Jan-16
Document File: 1 page(s) / 21K

Publishing Venue

Sony Technical Digest

Related People

Harel Wheitz: INVENTOR [+2]

Abstract

This invention seeks to address the limited memory space within a computer's microprocessor by reducing the amount of space consumed by the OSD database. The OSD database pages are made out of rows of data, and in order to load the data from each row or save data to each row, the number of bytes must be the same for each row. If a row does not have the same number of bytes as the others, End of Line (EOL) codes must be inserted at the end of the row in order to align the byte count with the rest of the rows. In general, 011 of the rows in an OSD page must have the same number of bytes as the row with the most bytes. This method consumes a lot of space in the microprocessors memory.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 71% of the total text.

Sony Technical Digest, Volume 3, November 2000, ISSN 1521-5180

OSD DATABASE MEMORY SAVING

Invention by:

Harel Wheitz

Shin Fujimori

This invention seeks to address the limited memory space within a computer's microprocessor by reducing the amount of space consumed by the OSD database. The OSD database pages are made out of rows of data, and in order to load the data from each row or save data to each row, the number of bytes must be the same for each row. If a row does not have the same number of bytes as the others, End of Line (EOL) codes must be inserted at the end of the row in order to align the byte count with the rest of the rows. In general, 011 of the rows in an OSD page must have the same number of bytes as the row with the most bytes. This method consumes a lot of space in the microprocessors memory.

The key element of this invention is to include the number of bytes for each row of an OSD page at the beginning of the row definition in the database-the first byte of the row will declare the number of total bytes for that specific row. By using this method, the program learns how many bytes will be loaded for any specific row before the computer reads the row. As a consequence, the EOL code does not have to be inserted at the end of each row. Because the program already knows the number of bytes that the OSD rows consist of, an EOL code at the end of the row is not needed. By using this method, the size of the microprocessor memory program is limited, whereas the fu...