text: in an embodiment of the present invention , during a partial write operation to mlc flash memory , a temporary storage location , a partial write collector ( pwc ), of at least one block in size , is used to store data that is to be written during the write operation , serving basically as a basket of information , and later when the write operation resumes , the temporarily stored data is retrieved and written thereby ensuring successful writing of data during the write operation . the temporary storage location includes , at least , the last page that is to be or was written . otherwise , when data is being written not in a partial write operation manner , it is written to a more permanent location within the mlc flash memory . the pwc can be used in a wear leveling method to enhance reliability and performance of the mlc flash memory . for a more detailed discussion of an exemplary mlc flash memory which can be used with the various embodiments and methods of the present invention , the reader is directed to u . s . pat . no . 7 , 082 , 056 , entitled “ flash memory device and architecture with multi level cells ”, by ben w . chen et al ., and issued on jul . 25 , 2006 , which is herein incorporated by reference as though set forth in full . referring now to fig1 , a flash ( or non - volatile ) memory system 200 , which may be a part of a computer ( personal computer ( pc )), digital camera and the like is shown in accordance with an embodiment of the present invention , is shown to include a flash controller 202 and a flash memory 204 . the flash memory 204 includes mlc flash memory , either in the form of an array or otherwise , for storing digital information and is organized into blocks of pages and is programmed or written thereto using the various techniques to be discussed shortly in accordance with the teachings of the present invention . the term flash memory represents one or more flash memory devices . the flash memory system 200 is shown coupled to a host 210 , which is shown to include a flash controller 202 . the flash memory system 200 may be implemented as a printed circuit board ( pcb ) or flash card . the flash memory system 200 can store various types of data including image data and other types of multimedia data . accordingly , the flash memory system 200 can also be referred to as a multimedia card ( mmc ). the flash memory 204 is shown to include a pwc block 250 for temporary storage of information including data and spare being written by the user host 210 . in the case where the flash memory 204 is mlc flash memory , being large in size , such as 2 kilo ( k ) bytes , are written to the memory . in the case where a partial write of a page is being conducted , that is , a portion of a page is written and then the writing stops and the remaining portion is to be written , the write operation is performed inefficiently using current systems and techniques . however , in the embodiment ( s ) of the present invention , partial write to a page followed by writing of the remainder of the page is advantageously efficiently performed . fig2 shows a flow chart 300 of the steps performed by the flash memory system 200 of fig1 in performing a write operation to the mlc flash memory within the flash memory 204 as a partial or full write . in fig2 , at step 302 , the write operation begins , next , at step 304 , a determination is made as to whether or not the address of the last data in a partial write collector ( pwc ) block s the same as the address to be written thereto . the pwc block is one or more blocks of memory within the flash memory 204 used as a temporary location within which information to be written during a write operation is stored in the case where the write operation is a partial write operation . the address to which information is to be written is initially provided by the flash controller 202 through the flash card interface , shown in fig1 . upon a determination that the address to which information is to be written during the write operation matches that of the pwc block , the flow of fig2 , continues to step 306 where data to be written is collected or stored in the buffer 240 . next , at 308 , a determination is made as to whether or not a page worth of data has been collected . in the case where a page is 2k bytes , a 2k byte boundary is checked . if it is determined , at 308 , that a page boundary is encountered , the process continues to 310 where a determination is made as to whether or not a “ stop ” command has been received from the flash controller 202 . if at 310 , it is determined that the a “ stop ” command has been received by the flash memory system 200 , step 312 is performed where a copy of the data stored in the pwc block as well as the data saved in the buffer memory 240 are stored in the pwc block , an example of which is shown in fig8 and will be discussed further relative to the latter . the foregoing essentially serves to save the data that is being written by the host , in a continuous or sequential form , in the pwc block . in the event , at 304 , in fig2 , it is determined that the address of the last data in the pwc block does not match the address of the location to which data is being written during this write operation , the process continues to step 314 where the most recent or last data written in the pwc is copied to its target destination at a location identified by a target physical address . one way to reach the step 314 is by having started a write operation and then having had to stop it , i . e . partial write operation , and then are now resuming it , which would lead to the address of the last data stored in the pwc block not being that of the address of the information being written . during a write operation , data or information to be written to flash memory is collected in the buffer 240 . in the where a partial write operation is being performed , data is also collected in the pwc block . next , at step 316 , the data being written by the host is collected in the buffer memory 240 followed by a determination of a page boundary at 318 . if at 318 , it is determined that a page boundary is hit , the process continues to step 322 where data that is being written is , in its entirety , written to its target destination identified by the target physical address , as shown in fig4 . in the case where the process gets to step 322 , no partial write may have occurred in which case the write operation was contiguous during the writing of the entire page . if at 318 , it is determined that a page boundary has not been encountered , then , the process continues to 320 where a determination is made as to whether or not a “ stop ” command is received from the host and if not , the process continues to step 316 , otherwise , the process goes on to step 324 where data to be written by the host is copied or stored in the pwc block , as shown in fig5 . if at 308 , it is determined that a page boundary is encountered , the process continues to 326 where a determination is made as to whether or not the data in the buffer memory 240 is a page in size , such as 2k bytes and if so , the process goes on to step 328 where information from the buffer memory 240 , written thereto by the host , is copied ( or moved ), in its entirety , to a target destination , identified by a target physical address , such as shown in fig6 . in the foregoing case , no partial write is performed because a page boundary is hit and the data buffer is filled with the entire page of information . the target destination in cases in fig2 is in the flash memory 204 as that is where the host intends to store information , as previously discussed . if at 326 , it is determined that the information stored in the buffer memory 240 is not a page in size ( or 2k bytes for example ), a partial write has occurred ( otherwise , the buffer memory would be full ) and the process continues to step 330 where the current information stored in the pwc block 250 is copied along with the current information in the buffer memory 240 to the target destination , as identified by a target physical address and shown in fig7 . current information refers to information , from the host , that has not yet been written or stored but need be stored and it is valid information as opposed to old or not current or defective information . current or old information is identified by flags in the spare area . after step 330 , the process returns and continues at step 306 . fig3 shows an example of a block including 128 pages with each page having 2k bytes of data area and 64 bytes of spare area . fig3 ( a ) and 3 ( b ) show different structures , as examples , of a page of fig3 . the pages of the block are written thereto by the host in accordance with the embodiments and methods of the present invention . in fig3 ( a ), a page is shown to include 4 * 512 bytes of data in a data area 352 and 4 * 16 bytes of spare in a spare area 354 . each of the 512 bytes of data has a corresponding 16 byte spare located in the spare area 354 . each 512 bytes of data and its corresponding spare are at times referred to as sector . thus , in fig3 ( a ), the four 512 bytes of data are sequentially located or located adjacent to each other and each of their corresponding spares are located after the data area 352 but also in sequential order . in fig3 ( b ), a page 360 is shown to include 4 *( 512 bytes + 16 bytes ) where each of the 512 bytes of data 362 are of data in a data area 352 and 4 * 16 bytes of spare in a spare area 354 . each of the 512 bytes of data has a corresponding 16 byte spare located in the spare area 354 . each 512 bytes of data 362 and its corresponding spare 364 are at times referred to as sector . in fig3 ( b ) each of the data 362 and corresponding spare 364 are shown adjacent to each other and adjacent to the data - spare pair is located the next 512 bytes of data 364 and its corresponding spare 364 . fig4 - 8 show examples of the contents of various memories corresponding to the various steps shown in fig2 . for example , fig4 shows a target physical address block 400 , which is included in the flash memory 204 of fig1 , and further show the buffer memory 240 . the block 400 is the block within which the information being provided by the host is to be written . the block 400 is shown to include 128 pages in the embodiment of fig4 , however , other number of pages may be included in the block 400 . one of the ways the status of the block 400 and the buffer memory 240 are as shown in fig4 , is by performance of the steps , 316 , and 322 in fig2 . as noted earlier , the block 400 includes 128 pages including a page n , which is where the information from the buffer memory 240 is copied thereto . the information stored in the buffer memory 240 is information collected at step 316 in fig2 and its data appears at the fourth 512 byte data area of page n and its spare appears at the last spare area of page n . the information stored in the first three 512 bytes of the data area of page n , in fig4 , and the first three 16 bytes of spare areas of page n are filled with 0xff . the target address here refers to the address within the spare ( or flag within the spare ) of the corresponding page . the target address at step 314 is the address of the information stored within the pwc block . the target address at step 322 is the address of the information stored in the buffer 240 . thus , the target address at step 314 is different than the target address at step 322 . the first three 512 bytes of the data of the four sections of the page n are either empty ( filled with 0xff ) or filled with data from the buffer 240 . in fig4 - 8 different shadings of the pages indicate the status of the information . for example , in fig5 , the dark shading in target physical address block 400 indicates “ current ” or “ used ” or “ old ” information that can be valid or current . the dark shading in partial write collector block 250 indicates ‘ used ’ or ‘ old ’ or ‘ garbage ’ information , i . e . information that is no longer valid or current . blank or white areas indicate no information or empty . the darker checkered areas indicate information that is current and just stored in the page n ( from the buffer memory 240 ) and the lighter checkered shading indicates optionally filled . in fig4 , essentially , the page boundary was encountered and the current information is present in the buffer 240 , thus , some of the page n information comes from the buffer memory and some information is filled with 0xff , as shown by the shadings . indication of current information within the pwc block 250 is through the flags located in the corresponding spare area of a 512 byte data area . fig5 shows a target physical address block 400 , which is included in the flash memory 204 of fig1 , and further show the buffer memory 240 and the pwc block 250 . the block 400 is the block within which the information being provided by the host is to be written . the blocks 400 and 250 are each shown to include 128 pages in the embodiment of fig5 , however , other number of pages may be included therein . one of the ways the status of the block 400 and the buffer memory 240 and the block 250 are as shown in fig5 , is by performance of the step 324 . that is , a “ stop ” command has been received by the flash memory system 200 , yet an entire page has not yet been written , as commanded by the host , thus , during the stop period , the information already written by the host , which now resides in the data buffer memory 240 , is written or copied to the page m of the block 250 . since , so far , only some of the first three 512 byte data and their respective spares have been written by the host , only they are copied to corresponding locations in page m in the block 250 . the status of the page m in the block 250 may be any of the following : the first , second and third 512 - byte sections of data of the page are filled with data from the buffer 240 and the fourth 512 - byte data is don &# 39 ; t care or it does not matter what it is ; the first and second or second and third 512 - byte sections of data of a page are filled with data and it does not matter what the remaining 512 - byte sections of the page include ; the first , second or third 512 - byte sections of data of a page are filled with data and it does not matter what the remaining 512 - byte sections of the page include ; or the status of the 16 - byte spare of the four sections of a page match the status of their corresponding data . fig6 shows a target physical address block 400 , which is included in the flash memory 204 of fig1 , and further shows the buffer memory 240 . the block 400 is the block within which the information being provided by the host is to be written . the block 400 is shown to include 128 pages in the embodiment of fig4 , however , other number of pages may be included in the block 400 . one of the ways the status of the block 400 and the buffer memory 240 are as shown in fig6 , is by performance of the step 330 . in the example of fig6 , as no partial write occurs , the information stored in the buffer memory 240 , which is an entire page of information , is copied to the block 400 . fig7 shows a target physical address block 400 , which is included in the flash memory 204 of fig1 , and further show the buffer memory 240 and the pwc block 250 . the block 400 is the block within which the information being provided by the host is to be written . the blocks 400 and 250 are each shown to include 128 pages in the embodiment of fig5 , however , other number of pages may be included therein . one of the ways the status of the block 400 and the buffer memory 240 and the block 250 are as shown in fig7 , is by performance of the step 330 , in fig2 . pages 0 -( m - 1 ) of the block 250 include garbage or old information , whereas , page m thereof includes current information , as denoted by respective flags of the 512 bytes of data in their spare . since hit the 2k boundary , the 4 th 512 bytes information must come from the buffer memory . since a page of information was not stored in its entirety in the buffer memory 240 , the first 512 bytes information must come from the pwc 250 . the remainder comes either from the block 250 or form the buffer memory 240 . it should be noted that in fig4 - 8 , spare corresponding to a 512 byte data is stored accordingly although in alternative embodiments , spare corresponding to a 512 byte data can be stored in an area that does not readily show such correspondence in which case additional information is required to correlate a spare to its data . fig8 shows a target physical address block 400 , which is included in the flash memory 204 of fig1 , and further shows the buffer memory 240 . the block 400 is the block within which the information being provided by the host is to be written . the block 400 is shown to include 128 pages in the embodiment of fig4 , however , other number of pages may be included in the block 400 . one of the ways the status of the block 400 and the buffer memory 240 are as shown in fig8 , is by performance of the step 312 . in this case , information from page m - 1 of the block 250 is copied to page m thereof but only as to information that was not collected in the buffer memory 240 , and as a page boundary was not encountered , therefore a page worth of information was not stored in the buffer memory 240 , the remainder of the page information comes either from the buffer memory 240 , to the extent it was collected or from the block 250 . the block 250 may include more than one block of information . although the present invention has been described in terms of specific embodiments it is anticipated that alterations and modifications thereof will no doubt become apparent to those skilled in the art . it is therefore intended that the following claims be interpreted as covering all such alterations and modification as fall within the true spirit and scope of the invention .