| Predicate |
Object |
| assignee |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_51d028c578ae85cb937b5b34a5129fbc |
| classificationCPCAdditional |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C2029-0409
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C2029-4402
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C2029-1204 |
| classificationCPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-82
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-44
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-3459
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-14
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-3404
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-3431
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-04
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C7-12
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F11-1012
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F3-0614
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-24
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-26
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-025
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F11-076
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-0483
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-4401
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C16-3445
http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G11C29-88 |
| classificationIPCInventive |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G11C16-26
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G11C16-34
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G11C16-24
http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G11C29-02 |
| filingDate |
2020-06-26^^<http://www.w3.org/2001/XMLSchema#date> |
| inventor |
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_b589452b007e31f8e184425afb95c87e
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_73afff2f235bdc68e087817eadb64ad9
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_470a9574f86c9febf265da2cd0a62aa7
http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_3fc1d5ca86c1f77db950abd7d4b35135 |
| publicationDate |
2021-03-16^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber |
KR-20210029661-A |
| titleOfInvention |
Defective bit line management in connection with a memory access |
| abstract |
An example herein relates to determining the number of defective bit lines in a memory area prior to applying a program or erase voltage. If the threshold number of bit lines passing during a program or erase verify operation is used to determine whether a program or erase operation passes or fails, the determined number of defective bit lines may be used to adjust the determined number of passes or failures. In some cases, the examples described herein can avoid the use of an extra bit line and lookup table circuit to be used in place of a defective bit line and save silicon space and cost associated with the use of an extra bit line. In some examples, the starting size of the program voltage signal can be determined by taking into account the number of defective bit lines. In some examples, identification of an open or shorted bit line may be used to identify a read operation involving such an open or shorted bit line as weak in connection with performing soft bit read corrections. |
| priorityDate |
2019-09-06^^<http://www.w3.org/2001/XMLSchema#date> |
| type |
http://data.epo.org/linked-data/def/patent/Publication |