US7302529B2 - Method for comparing contents of memory components - Google Patents

Method for comparing contents of memory components Download PDF

Info

Publication number
US7302529B2
US7302529B2 US10/747,779 US74777903A US7302529B2 US 7302529 B2 US7302529 B2 US 7302529B2 US 74777903 A US74777903 A US 74777903A US 7302529 B2 US7302529 B2 US 7302529B2
Authority
US
United States
Prior art keywords
electronic device
checksum values
contents
checksum
data transmission
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US10/747,779
Other languages
English (en)
Other versions
US20050007838A1 (en
Inventor
Jakke Mäkelä
Jukka-Pekka Vihmalo
Marko T. Ahvenainen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
RPX Corp
Nokia USA Inc
Original Assignee
Nokia Oyj
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Oyj filed Critical Nokia Oyj
Assigned to NOKIA CORPORATION reassignment NOKIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MAKELA, JAKKE, AHVENAINEN, MARKO T., VIHMALO, JUKKA-PEKKA
Publication of US20050007838A1 publication Critical patent/US20050007838A1/en
Application granted granted Critical
Publication of US7302529B2 publication Critical patent/US7302529B2/en
Assigned to NOKIA TECHNOLOGIES OY reassignment NOKIA TECHNOLOGIES OY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA CORPORATION
Assigned to CORTLAND CAPITAL MARKET SERVICES, LLC reassignment CORTLAND CAPITAL MARKET SERVICES, LLC SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PROVENANCE ASSET GROUP HOLDINGS, LLC, PROVENANCE ASSET GROUP, LLC
Assigned to PROVENANCE ASSET GROUP LLC reassignment PROVENANCE ASSET GROUP LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALCATEL LUCENT SAS, NOKIA SOLUTIONS AND NETWORKS BV, NOKIA TECHNOLOGIES OY
Assigned to NOKIA USA INC. reassignment NOKIA USA INC. SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PROVENANCE ASSET GROUP HOLDINGS, LLC, PROVENANCE ASSET GROUP LLC
Assigned to NOKIA US HOLDINGS INC. reassignment NOKIA US HOLDINGS INC. ASSIGNMENT AND ASSUMPTION AGREEMENT Assignors: NOKIA USA INC.
Assigned to PROVENANCE ASSET GROUP LLC, PROVENANCE ASSET GROUP HOLDINGS LLC reassignment PROVENANCE ASSET GROUP LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: NOKIA US HOLDINGS INC.
Assigned to PROVENANCE ASSET GROUP HOLDINGS LLC, PROVENANCE ASSET GROUP LLC reassignment PROVENANCE ASSET GROUP HOLDINGS LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CORTLAND CAPITAL MARKETS SERVICES LLC
Assigned to RPX CORPORATION reassignment RPX CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PROVENANCE ASSET GROUP LLC
Assigned to BARINGS FINANCE LLC, AS COLLATERAL AGENT reassignment BARINGS FINANCE LLC, AS COLLATERAL AGENT PATENT SECURITY AGREEMENT Assignors: RPX CORPORATION
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C15/00—Digital stores in which information comprising one or more characteristic parts is written into the store and in which information is read-out by searching for one or more of these characteristic parts, i.e. associative or content-addressed stores

Definitions

  • the invention relates to memory components, and particularly to comparing contents of memory components.
  • a mobile station for instance, is no longer used merely for speaking, but also as a camera, a calendar, an Internet browser or a game device, for example.
  • Such numerous new multimedia and other applications require improved performance, and particularly greater memory capacity and lower energy consumption.
  • the memory components in electronic devices are significant for the performance and energy consumption of the whole electronic device.
  • DRAM memory components Dynamic Random Access Memory
  • SRAM memory components Static Random Access Memory
  • Integrating memory components according to the prior art into portable electronic devices, such as mobile stations, is thus difficult due to the great energy consumption and physical size of the memory components.
  • problems are caused by disappearance of the data stored in DRAM and SRAM memory components when the power supply stops, synchronization between different memory components and corruption of files and file systems.
  • An object of the invention is thus to provide a method and an apparatus implementing the method in such a way that disadvantages of the above-mentioned problems can be reduced.
  • the object of the invention is achieved with a method, system, device and software that are characterized in what is stated in the independent claims. Preferred embodiments of the invention are described in the dependent claims.
  • An initialization message INIT is transmitted from the first electronic device A to the second electronic device B, the message comprising at least the first device identifier ID(A) and the first and the second checksum value CS 1 (A) and CS 2 (A), or information for determining them.
  • the device identifiers ID(A), ID(B), the first checksum values CS 1 (A), CS 1 (B) and the second checksum values CS 2 (A), CS 2 (B) of the first and the second electronic device A and B are compared with each other, and consequently, if the device identifiers ID(A), ID(B), the first checksum values CS 1 (A), CS 1 (B) and the second checksum values CS 2 (A), CS 2 (B) do not correspond to each other, the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other, or if the device identifiers ID(A), ID(B), the first checksum values CS 1 (A), CS 1 (B) and the second checksum values CS 2 (A), CS 2 (B) do correspond to each other, the contents of the memory components NVC(A), NVC(B) are noted to correspond to each other.
  • the contents of the memory components NVC(A) and NVC(B) are noted to correspond to each other if the device identifiers ID(A), ID(B), the first checksum values CS 1 (A), CS 1 (B) and the second checksum values CS 2 (A), CS 2 (B) correspond to each other.
  • the device identifiers ID(A) and ID(B) are included in the first and/or the second checksum value CS 1 and/or CS 2 .
  • the device identifier ID(A) of the first electronic device A is included in the first and/or the second checksum value CS 1 (A), CS 2 (A), and the device identifier ID(B) of the second electronic device B is included in the first and/or the second checksum value CS 1 (B), CS 2 (B).
  • the device identifier ID(B) of the second electronic device B as well as the first and the second checksum value CS 1 (B), CS 2 (B) are determined after the second electronic device B has received the initialization message INIT.
  • an acknowledgement message ACK INIT comprising the device identifier ID(B) and the first and the second checksum value CS 1 (B), CS 2 (B) or information for determining them is transmitted from the second electronic device B to the first electronic device A after the device identifier ID(B) and the first and the second checksum value CS 1 (B), CS 2 (B) have been determined.
  • the device identifiers ID(A) and ID(B) are compared with each other. Consequently, if the device identifiers ID(A) and ID(B) do not correspond to each other, the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other, or if the device identifiers ID(A) and ID(B) do correspond to each other, the first checksum values CS 1 (A) and CS 1 (B) are compared.
  • the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other, or if the first checksum values CS 1 (A) and CS 1 (B) do correspond to each other, the second checksum values CS 2 (A) and CS 2 (B) are compared. Consequently, the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other if the second checksum values CS 2 (A) and CS 2 (B) do not correspond to each other.
  • the first checksum values CS 1 (A) and CS 1 (B) are compared with each other, and consequently, if the first checksum values CS 1 (A) and CS 1 (B) do not correspond to each other, the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other, or if the first checksum values CS 1 (A) and CS 1 (B) do correspond to each other, the second checksum values CS 2 (A) and CS 2 (B) are compared. Consequently, the contents of the memory components NVC(A) and NVC(B) are caused to correspond to each other if the second checksum values CS 2 (A) and CS 2 (B) do not correspond to each other.
  • One advantage is that the arrangement allows robust, i.e. accurate, data transmission, whereby, for example, data transmission between memory components can be interrupted and continued later on at the same point.
  • One of the advantages is also that data transmission rate can be increased, maintaining at the same time data robustness.
  • Still another advantage is that data robustness is improved under shutdown conditions, because the stored data does not disappear when the power supply stops.
  • One advantage is also that an NVRAM cache memory is usually less expensive than an SRAM cache memory, which has equally high memory capacity.
  • a further advantage is that the energy consumption of the electronic device can be optimised. The arrangement according to the invention can thus simplify and enable the use of high-capacity mass memory technology, for instance in mobile stations.
  • FIG. 1 shows a block diagram of a system comprising two electronic devices
  • FIG. 3 shows a flow chart of comparing functionality of the memory component contents in two electronic devices
  • FIG. 4 shows an algorithm for reading a file in an external storing device
  • FIG. 5 shows data transmission according to an embodiment of the invention between two electronic devices for comparing the memory component contents in the electronic devices.
  • wireless data transmission connections such as Bluetooth connections
  • the invention can be applied to any data transmission connections, such as fixed data transmission connections.
  • the memory components in electronic devices are significant for the performance of the whole electronic device, particularly for data transmission rates and energy consumption.
  • memories are usually used for storing data. Different memory types differ from each other mainly with regard to the operational rate, storing capacity and preservability of the stored data. Therefore, electronic devices generally comprise several different memories for different objects of use.
  • Memories can generally be divided into volatile and non-volatile memories on the basis of their operation. When the power supply is interrupted, a volatile memory generally loses all data it has stored, but a non-volatile memory typically preserves the data it has stored.
  • RAM memories Random Access Memory are usually volatile memories in which data can be written and read out when the power source is switched on.
  • the main memory used by the central processing unit CPU of an electronic device is usually RAM memory.
  • RAM memories can be further divided into SRAM memories (Static Random Access Memory) and DRAM memories (Dynamic Random Access Memory).
  • an SRAM memory cell the information is typically stored in a flip-flop comprising generally four to six transistors.
  • the structure of an SRAM memory is thus complex and takes a lot of space. Owing to its fastness and low energy consumption, an SRAM memory is used particularly for executing a program code and as a cache memory.
  • a DRAM memory cell typically comprises one capacitor, in which data is stored as electric charge, and a MOSFET transistor (Metal Oxide Semiconductor Field Effect Transistor), which functions as a switch when the capacitor is charged and discharged.
  • a DRAM memory is small in size and inexpensive. For example, millions of memory cells can be implemented for one integrated circuit.
  • the use of one-transistor DRAM cells compared with the use of six-transistor SRAM cells saves up to millions of transistors with an integrated circuit.
  • a DRAM memory requires refresh functionality, i.e. recharging of the capacitor, periodically. Despite the refresh functionality, the DRAM memory is rapid, and it is used particularly for storing data temporarily.
  • a ROM memory is typically a non-volatile read-only memory. Storing data in a ROM memory can be permanent or reprogrammable, depending on the manufacturing technology.
  • the ROM memories can be divided into mask ROM memories, PROM memories (Programmable Read Only Memory) and EPROM memories (Erasable and Programmable Read Only Memory), for example.
  • Mask ROM memories are programmed as early as upon manufacture; PROM memories can be programmed once by the user; and EPROM memories can be reprogrammed several times. ROM memories are fast and their power consumption is usually low. ROM memories are used particularly for mass-storing permanent data, such as for storing programs and microcodes.
  • NVRAM memories Non-Volatile Random Access Memories
  • An NVRAM memory thus preserves the data it has stored although the power supply is stopped. Operation of an NVRAM memory is generally fast, and the memory is typically used as mass memories MM, for instance in mobile stations.
  • NVRAM memories include for instance an FeRAM memory (Ferroelectric Random Access Memory), an MRAM memory (Magnetoresistive Random Access Memory) and an OUM memory (Ovonic Unified Memory).
  • FIG. 1 shows a system in which a large mass memory MM ( 104 ) has been implemented in an electronic device, such as a mobile station ( 100 ) by functionally connecting to the mobile station ( 100 ) a second electronic device, such as a storing device SD ( 102 ), comprising a mass memory.
  • a data transmission connection for example a wireless Bluetooth connection BT ( 108 )
  • BT wireless Bluetooth connection
  • BT-IF Bluetooth interfaces
  • FIG. 1 shows a system in which a large mass memory MM ( 104 ) has been implemented in an electronic device, such as a mobile station ( 100 ) by functionally connecting to the mobile station ( 100 ) a second electronic device, such as a storing device SD ( 102 ), comprising a mass memory.
  • a data transmission connection for example a wireless Bluetooth connection BT ( 108 )
  • the wireless interfaces for instance Bluetooth interfaces BT-IF ( 106 )
  • the storing device SD ( 102 ) preferably has a power supply system of its own, whereby it does not load the mobile station MP ( 100 ). Once the mass memory MM ( 104 ) of the storing device SD ( 102 ) has been implemented in the mobile station MP ( 100 ), the physical size and energy consumption of the memory component is no longer a problem.
  • FIG. 2 shows a system in which a wireless connection WL ( 206 ), such as a Bluetooth connection, can be established between the wireless interfaces WL-IF ( 204 ), for instance Bluetooth interfaces, of two electronic devices A ( 200 ) and B ( 202 ).
  • the electronic devices A ( 200 ) and B ( 202 ) comprise for instance a processor MCU (Micro Controller Unit) ( 208 ) arranged to determine the identifiers used for identifying the electronic devices A ( 200 ) and B ( 202 ), i.e.
  • MCU Micro Controller Unit
  • first checksum values CS 1 (A), CS 1 (B) and second checksum values CS 2 (A), CS 2 B of which the first checksum values CS 1 (A), CS 1 (B) represent checksum values relating to the preceding, preferably confirmed data transmission event, and the second checksum values CS 2 (A), CS 2 (B) represent checksum values of a new data transmission event.
  • the device identifier ID(A) of the first electronic device A can also be included in the first and/or the second checksum value CS 1 (A) and/or CS 2 (B), and the device identifier ID(B) of the second electronic device B can be included in the first and/or the second checksum value CS 1 (B) and/or CS 2 (B).
  • the processor MCU ( 208 ) is typically arranged to determine the device identifiers ID(A) and ID(B) and the first checksum values CS 1 (A) and CS 1 (B), for example by accessing them from the memory. Further, the processor MCU ( 208 ) is typically arranged to determine also the second checksum values CS 2 (A) and CS 2 (B).
  • the electronic device B ( 202 ) functioning as a separate storing device SD
  • a minimum amount of data is exchanged between it and the electronic device A ( 202 ), such as a mobile station, and that the data transmission is as robust and reliable as possible. This can be achieved by checking the contents of the memory components NVC(A) ( 212 ) and NVC(B) ( 214 ) with a minimum amount of data transmission in the start-up step of the wireless connection WL ( 206 ). Owing to the small amount of data transmission, the energy consumption can be reduced in the electronic devices.
  • FIG. 3 which has the same reference numerals as FIG. 2 , shows a flow chart of the coherence check functionality of the contents of cache memory components, preferably NVRAM cache memory components NVC(A) ( 212 ) and NVC(B) ( 214 ).
  • the checking is preferably performed each time in the start-up step ( 300 ) of the wireless connection WL ( 206 ).
  • the checking is carried out with what is called a handshake procedure, in which the device identifiers ID(A), ID(B) of the first and the second electronic devices A ( 200 ), B ( 202 ) as well as the separate checksum values CS 1 , CS 2 are exchanged between the first and the second electronic device A ( 200 ), B ( 202 ).
  • the device identifier ID(A) ( 302 ) of the first electronic device A ( 200 ) or information for determining the device identifier ID(A), and the first checksum value CS 1 (A) ( 304 ) relating to the preceding, preferably confirmed data transmission event or information for determining it are accessed from the memory of the first electronic device A ( 200 ).
  • a second checksum value CS 2 (A) ( 306 ) is determined for a new data transmission event.
  • the checksum values are determined for example with an algorithm, and preferably with such an algorithm that takes the continuous zero cycles into account.
  • the algorithm is preferably continuous, in which case, when there is an interruption, calculation of the checksum value can be continued later on at the point where the calculation was interrupted.
  • Accessing the device identifier ID(A) ( 302 ) and the first checksum value CS 1 (A) ( 304 ) as well as determining ( 306 ) the second checksum value CS 2 (A) can be carried out in any order relative to each other.
  • the device identifier ID(A) as well as the first checksum value CS 1 (A) and the second checksum value CS 2 (A) are transmitted in an initialization message ( 308 ) to the second electronic device B ( 202 ).
  • the device identifier ID(B) ( 310 ) of the second electronic device B ( 202 ) or information for determining the device identifier ID(B) and the first checksum value CS 1 (B) ( 312 ) relating to the preceding, preferably confirmed data transmission event are accessed from the memory of the second electronic device B ( 202 ).
  • a second checksum value CS 2 (B) ( 314 ) is determined for a new data transmission event.
  • Accessing the device identifier ID(B) ( 310 ) and the first checksum value CS 1 (B) ( 312 ) as well as determining ( 314 ) the second checksum value CS 2 (B) can be carried out in any order relative to each other.
  • the device identifier ID(B) as well as the first checksum value CS 1 (B) and the second checksum value CS 2 (B) are transmitted in an acknowledgement message ( 316 ) to the first electronic device A ( 200 ), after which the device identifiers ID(A) and ID(B) of the first and the second electronic device A ( 200 ), B ( 202 ) are compared ( 318 ) with each other.
  • the contents of the NVRAM cache memory component NVC(A) ( 212 ) in the first electronic device A ( 200 ) and of the cache memory component NVC(B) ( 214 ) in the second electronic device B ( 202 ) are caused to correspond ( 320 ) to each other if the device identifiers ID(A) and ID(B) of the electronic devices A ( 200 ) and B ( 202 ) do not correspond to each other in comparison ( 318 ).
  • the handshake procedure can be performed again partly or as a whole, for instance beginning from the access ( 302 ) of the device identifier ID(A).
  • the first checksum values CS 1 (A) and CS 1 (B) are next compared ( 322 ) with each other.
  • the contents of the NVRAM cache memory component NVC(A) ( 212 ) in the first electronic device A ( 200 ) and in the NVRAM cache memory component NVC(B) ( 214 ) in the second electronic device B ( 202 ) are caused to correspond ( 320 ) to each other if the first checksum values CS 1 (A) and CS 1 (B) of the electronic devices A ( 200 ) and B ( 202 ) do not correspond to each other in the comparison ( 322 ).
  • This can be implemented for instance in the way described above.
  • the device identifiers ( 318 ) ID(A), ID(B), the first checksum values ( 322 ) CS 1 (A) and CS 1 (B) and/or the second checksum values ( 324 ) CS 2 (A) and CS 2 (B) can be compared with each other again, on the basis of which the required further measures are taken for instance in the way described above. If the second checksum values CS 2 (A) and CS 2 (B) correspond to each other, the contents of the NVRAM cache components NVC(A) ( 212 ) and NVC(B) ( 214 ) are noted to correspond ( 328 ) to each other.
  • data is accessed in such a way that each piece of accessed data fits into the NVRAM cache memory component NVC(A) ( 212 ) and/or NVC(B) ( 214 ) or into that part of the NVRAM cache memory which is intended for data transmission.
  • FIG. 4 shows a sample algorithm for reading a file in an external storing device SD ( 402 ).
  • the functionality of the algorithm can also be extended to writing in a mass memory or to any one-way data transfer.
  • the algorithm can also have preferred embodiments other than the ones presented here.
  • the following algorithms are independent of the embodiments of the file allocation table FAT.
  • the file allocation tables FAT are stored in NVRAM cache memory components, in which case the synchronization is simpler and more robust.
  • Reading the file in the external storing device SD ( 402 ) can be performed for instance in the following manner.
  • an access request is transmitted from the file system MPFS ( 406 ) of an electronic device, such as a mobile station MP ( 400 ), comprising a file allocation table MPFAT ( 404 ) to the driver MPDR ( 408 ) of the mobile station MP ( 400 ).
  • the mirror version MPFAT′ ( 410 ) of the file allocation table MPFAT ( 404 ) is checked in order to see the length FR of the file and the pointer FR′ in the memory space.
  • the access request is transmitted to a driver BTDR ( 414 ) via a wireless connection, such as a Bluetooth connection BT ( 412 ).
  • a wireless connection such as a Bluetooth connection BT ( 412 ).
  • the Bluetooth connection BT ( 412 ) is started and initialized between the mobile station ( 400 ) and the external storing device SD ( 402 ). It is checked with the handshake procedure presented above whether the contents of the mirror version MPFAT′ ( 410 ) of the file allocation table and the real file allocation table MPFAT ( 404 ) are coherent.
  • the file allocation table SDFAT ( 420 ) is copied to the NVRAM cache memory component NVC(SD) ( 418 ) of the storing device SD ( 402 ), beginning from the pointer XM′.
  • the pointer XM′ is transmitted to the driver MPDR ( 408 ) of the mobile station MP ( 400 ) via the Bluetooth connection BT ( 412 ).
  • the pointer XT′ is allocated in the NVRAM cache memory component NVC(MP) ( 426 ) of the mobile station MP ( 400 ).
  • XT′ XM′.
  • the contents of the NVRAM cache memory component NVC(SD) ( 418 ) of the storing device SD ( 402 ) are transmitted to the NVRAM cache memory component NVC(MP) ( 426 ) of the mobile station MP ( 400 ). It is checked whether the transfer was successful by means of the above-described handshake procedure, for example. If the transfer was successful, the contents of the NVRAM cache memory component NVC(MP) ( 426 ) are copied to the mirror version MPFAT′ ( 410 ) of the file allocation table.
  • Copying the NVRAM cache memory component NVC(MP) ( 426 ) can be carried out in the following manner, for example.
  • a “Read F 0 ” command is transmitted from the driver MPDR ( 408 ) of the mobile station MP ( 400 ) to the driver SDDR ( 416 ) of the storing device SD ( 402 ).
  • a pointer YM′ is allocated from the NVRAM cache memory component NVC(SD) ( 418 ) of the storing device SD ( 402 ) and a pointer YT′ from the NVRAM cache memory component NVC(MP) ( 426 ) of the mobile station MP ( 400 ).
  • XT′ XM′.
  • the contents of the file are copied from the file system SDFS ( 424 ) of the storing device SD ( 402 ) to the NVRAM cache memory component NVC(SD) ( 418 ) of the storing device SD ( 402 ), beginning from the pointer YM′. If the length of the file is greater than the size NVS of the NVRAM cache memory component NVC(MP) ( 426 ), only NVS bits are copied at a time and synchronized. Preferably, it can be assumed that the data is accessed in such a way that the access always fits into the NVRAM cache memory component. Thus, no module arithmetics are needed. This requires, however, that the size of the NVRAM cache memory component be determined sufficiently large to cover possible cases of copying.
  • the contents of the NVRAM cache memory component NVC(SD) ( 418 ) can be copied to the file system MPFS ( 406 ) of the mobile station ( 400 ).
  • Device identifiers ID(A) and ID(B) as well as checksum values CS 1 and CS 2 or corresponding values are used to check in the above-described manner whether the version of the file system MPFS ( 406 ) is the same as in the storing device SD ( 402 ). If the contents of the file systems MPFS ( 406 ) and SDFS ( 424 ) are coherent, the file allocation table MPFAT ( 404 ) of the mobile station ( 400 ) is updated. A confirmation of successful update is transmitted to the storing device SD ( 402 ) via a wireless connection, such as a Bluetooth connection BT ( 412 ).
  • a wireless connection such as a Bluetooth connection BT ( 412 ).
  • the data transmission event can be continued for instance from the copying of file contents from the file system SDFS ( 424 ) of the storing device SD ( 402 ) to the NVRAM cache memory component NVC(SD) ( 418 ) of the storing device SD ( 402 ) when it has been checked that the file allocation tables SDFAT ( 420 ) and SDFAT′ ( 422 ) are still synchronized, in other words that they are still in synchronization with each other.
  • Reading and writing in one direction can be performed in a plurality of ways. Generally, the easiest way is to separate the cache memory components into two or more parts, using them as two separate cache memory components, for example. If their lengths are NVS 1 and NVS 2 , modulo-NVS 1 and modulo-NVS 2 algebra is used for each part.
  • the file allocation tables FAT are only updated when the files have been completely and correctly copied.
  • Reading and writing can also be performed in the following manner.
  • the synchronization of the file allocation tables FAT In order for the synchronization of the file allocation tables FAT to be successful, it is required that the synchronization have priority over all other operations. For instance, read and write operations are typically interrupted when the file allocation table FAT is synchronized.
  • Reading and writing can also be performed in two directions. This makes the keeping of the file allocation tables FAT synchronized somewhat more complicated. However, this can be avoided in the manner described earlier.
  • the comparison method for comparing the contents of memory components NVC(A) ( 504 ) and NVC(B) ( 506 ) according to the invention can be implemented with a preferred embodiment of the comparison system according to the invention.
  • a first electronic device A ( 500 ) and a second electronic device B ( 502 ) in the system are arranged to establish a wireless connection WL ( 508 ) to each other.
  • the first electronic device A ( 500 ) is arranged to access from the memory its own device identifier ID(A) ( 510 ) or information for determining it, and a first checksum value CS 1 (A) ( 512 ) relating to the preceding, preferably confirmed data transmission event or information for determining it.
  • the first electronic device A ( 500 ) is arranged to determine a second checksum value CS 2 (A) ( 514 ) for a new data transmission event or information for determining it. Accessing the device identifier ID(A) ( 510 ) and the first checksum value CS 1 (A) ( 512 ) and determining the second checksum value CS 2 (A) ( 514 ) can be performed in any order relative to each other.
  • the first electronic device A ( 500 ) is arranged to transmit its own device identifier ID(A) ( 510 ) as well as the first checksum value CS 1 (A) ( 512 ) and the second checksum value CS 2 (A) ( 514 ) or information for determining them to the second electronic device B ( 502 ) in an initialization message INIT ( 512 ).
  • the second electronic device B ( 502 ) is arranged to receive the initialization message INIT ( 516 ) transmitted by the first electronic device A ( 500 ) and to access from the memory a device identifier ID(B) ( 518 ) or information for determining it, and a checksum value CS 1 (B) ( 520 ) relating to the preceding, preferably confirmed data transmission event or information for determining it. After this, the second electronic device B ( 502 ) is arranged to determine a second checksum value CS 2 (B) ( 522 ) for a new data transmission event.
  • Accessing of the device identifier ID(B) ( 518 ) and the first checksum value CS 1 (B) ( 520 ) as well as determining the second checksum value CS 2 (B) ( 522 ) can be performed in any order relative to each other.
  • the second electronic device B ( 502 ) is arranged to transmit the device identifier ID(B) ( 418 ) as well as the first and the second checksum value CS 1 (B) ( 520 ) and CS 2 (B) ( 522 ) or information for determining it to the first electronic device A ( 500 ) in an acknowledgement message ACK INIT ( 524 ).
  • the first electronic device ( 500 ) is arranged to receive an acknowledgement message ACK INIT ( 524 ).
  • the first electronic device A ( 500 ) is arranged to compare ( 526 ) the device identifiers ID(A) ( 510 ) and ID(B) ( 518 ) of the first electronic device A ( 500 ) and the second electronic device B ( 502 ).
  • the first and/or the second electronic device A ( 500 ) and/or B ( 502 ) is/are arranged to cause the contents of the cache memory component NVC(A) ( 504 ) in the electronic device A ( 500 ) and the cache memory component NVC(B) ( 506 ) in the second electronic device B ( 502 ) to correspond to each other in the above-described manner if the device identifiers ID(A) ( 510 ) and ID(B) ( 518 ) of the first and the second electronic device A ( 500 ) and B ( 502 ) do not correspond to each other in the comparison ( 526 ).
  • the first and/or the second electronic device A ( 500 ) and/or B ( 502 ) is/are arranged to cause the contents of the cache memory component NVC(A) ( 504 ) in the electronic device (A) ( 500 ) and the cache memory component NVC(B) ( 506 ) in the second electronic device B ( 502 ) to correspond to each other in the above-described manner if the fist checksum values CS 1 (A) and CS 1 (B) of the first electronic device A ( 500 ) and the second electronic device B ( 502 ) do not correspond to each other in the comparison.
  • the first electronic device A ( 500 ) is arranged to compare ( 534 ) the second checksum values CS 2 (A) and CS 2 (B) with each other.
  • the first electronic device A ( 500 ) is arranged to re-compare the device identifiers ID(A), ID(B), the first checksum values CS 1 (A), CS 1 (B) and/or the second checksum values CS 2 (A) and CS 2 (B), on the basis of which the further measures are taken, for instance in the above-described manner.
  • the first and/or the second electronic device A ( 500 ) and B ( 502 ) is/are arranged to note that the contents of the cache memory components NVC(A) ( 504 ) and NVC(B) ( 506 ) correspond ( 538 ) to each other.
  • the comparing functionality can preferably be achieved with a software product arrangeable in an electronic device, comprising a software code for determining a device identifier ID(A) used for identifying a first electronic device A, a first checksum value CS 1 (A) relating to an earlier data transmission event and a second checksum value CS 2 (A) relating to a second data transmission event, for receiving the device identifier ID(B) of the second electronic device B as well as the first and the second checksum value CS 1 (B), CS 2 (B) or information used for determining them, for comparing the device identifiers ID(A), ID(B) of the first and the second electronic devices A, B, the first checksum values CS 1 (A), CS 1 (B) and the second checksum values CS 2 (A), CS 2 (B) with each other, for updating the contents of the memory component NVC(A) to correspond to the contents of the memory component in the

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Techniques For Improving Reliability Of Storages (AREA)
US10/747,779 2002-12-31 2003-12-29 Method for comparing contents of memory components Active 2024-11-16 US7302529B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20022297A FI20022297A (sv) 2002-12-31 2002-12-31 Förfarande för jämförelse av innehåll hos minneskomponenter
FI20022297 2002-12-31

Publications (2)

Publication Number Publication Date
US20050007838A1 US20050007838A1 (en) 2005-01-13
US7302529B2 true US7302529B2 (en) 2007-11-27

Family

ID=8565167

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/747,779 Active 2024-11-16 US7302529B2 (en) 2002-12-31 2003-12-29 Method for comparing contents of memory components

Country Status (6)

Country Link
US (1) US7302529B2 (sv)
EP (1) EP1579344A1 (sv)
CN (1) CN1732466A (sv)
AU (1) AU2003288302A1 (sv)
FI (1) FI20022297A (sv)
WO (1) WO2004059527A1 (sv)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060223582A1 (en) * 2005-03-31 2006-10-05 Nokia Corporation Switching device via power key initiated wizard

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6456234B1 (en) * 2000-06-07 2002-09-24 William J. Johnson System and method for proactive content delivery by situation location
US7451353B2 (en) * 2005-12-23 2008-11-11 Intel Corporation Cache disassociation detection
US7484116B2 (en) * 2006-01-03 2009-01-27 International Business Machines Corporation Apparatus, system, and method for accessing redundant data
US7478217B2 (en) * 2006-04-07 2009-01-13 Mediatek Inc. Method of storing both large and small files in a data storage device and data storage device thereof
US10367848B2 (en) * 2014-09-25 2019-07-30 Nec Corporation Transmitting relay device identification information in response to broadcast request if device making request is authorized
US10915270B2 (en) * 2017-07-24 2021-02-09 Clipchamp Ip Pty Ltd Random file I/O and chunked data upload

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5193093A (en) 1989-01-27 1993-03-09 Fujitsu Limited Data transfer process with loop checking
US5404485A (en) 1993-03-08 1995-04-04 M-Systems Flash Disk Pioneers Ltd. Flash file system
EP0667579A1 (en) 1994-02-09 1995-08-16 Ballard Synergy Corporation Cache for optical storage device
US5581726A (en) 1990-12-21 1996-12-03 Fujitsu Limited Control system for controlling cache storage unit by using a non-volatile memory
US5634109A (en) 1994-06-20 1997-05-27 International Business Machines Corporation Method and system for enhanced data management efficiency in memory subsystems utilizing redundant arrays of disk memory devices and a nonvolatile cache
US5732238A (en) 1996-06-12 1998-03-24 Storage Computer Corporation Non-volatile cache for providing data integrity in operation with a volatile demand paging cache in a data storage system
US5765172A (en) * 1996-01-23 1998-06-09 Dsc Communications Corporation System and method for verifying integrity of replicated databases
WO1999017200A1 (en) 1997-09-30 1999-04-08 Tandem Computers Incorporated A method of comparing replicated databases using checksum information
US6141784A (en) 1997-11-26 2000-10-31 International Business Machines Corporation Method and system in a data communications system for the retransmission of only an incorrectly transmitted portion of a data packet
WO2001038990A1 (en) 1999-11-24 2001-05-31 Telia Ab Procedure and system for determining a measure of probability regarding the identity between different examples of a data file
US6944623B2 (en) * 2000-08-21 2005-09-13 Lg Electronics Inc. Method for data synchronization in web-based communications management system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5381539A (en) * 1992-06-04 1995-01-10 Emc Corporation System and method for dynamically controlling cache management
US5615329A (en) * 1994-02-22 1997-03-25 International Business Machines Corporation Remote data duplexing
US5592618A (en) * 1994-10-03 1997-01-07 International Business Machines Corporation Remote copy secondary data copy validation-audit function
US5720029A (en) * 1995-07-25 1998-02-17 International Business Machines Corporation Asynchronously shadowing record updates in a remote copy session using track arrays
US6539462B1 (en) * 1999-07-12 2003-03-25 Hitachi Data Systems Corporation Remote data copy using a prospective suspend command

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5193093A (en) 1989-01-27 1993-03-09 Fujitsu Limited Data transfer process with loop checking
US5581726A (en) 1990-12-21 1996-12-03 Fujitsu Limited Control system for controlling cache storage unit by using a non-volatile memory
US5404485A (en) 1993-03-08 1995-04-04 M-Systems Flash Disk Pioneers Ltd. Flash file system
EP0667579A1 (en) 1994-02-09 1995-08-16 Ballard Synergy Corporation Cache for optical storage device
US5634109A (en) 1994-06-20 1997-05-27 International Business Machines Corporation Method and system for enhanced data management efficiency in memory subsystems utilizing redundant arrays of disk memory devices and a nonvolatile cache
US5765172A (en) * 1996-01-23 1998-06-09 Dsc Communications Corporation System and method for verifying integrity of replicated databases
US5732238A (en) 1996-06-12 1998-03-24 Storage Computer Corporation Non-volatile cache for providing data integrity in operation with a volatile demand paging cache in a data storage system
WO1999017200A1 (en) 1997-09-30 1999-04-08 Tandem Computers Incorporated A method of comparing replicated databases using checksum information
US6141784A (en) 1997-11-26 2000-10-31 International Business Machines Corporation Method and system in a data communications system for the retransmission of only an incorrectly transmitted portion of a data packet
WO2001038990A1 (en) 1999-11-24 2001-05-31 Telia Ab Procedure and system for determining a measure of probability regarding the identity between different examples of a data file
US6944623B2 (en) * 2000-08-21 2005-09-13 Lg Electronics Inc. Method for data synchronization in web-based communications management system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060223582A1 (en) * 2005-03-31 2006-10-05 Nokia Corporation Switching device via power key initiated wizard

Also Published As

Publication number Publication date
CN1732466A (zh) 2006-02-08
WO2004059527A1 (en) 2004-07-15
FI20022297A (sv) 2004-07-01
EP1579344A1 (en) 2005-09-28
US20050007838A1 (en) 2005-01-13
AU2003288302A1 (en) 2004-07-22
FI20022297A0 (sv) 2002-12-31

Similar Documents

Publication Publication Date Title
US10747299B2 (en) Card and host apparatus
US6693840B2 (en) Non-volatile semiconductor memory device with enhanced erase/write cycle endurance
KR100877610B1 (ko) 페이지 데이터 저장 방법과 저장 장치
US7730232B2 (en) Data transfer method and system
US8719492B1 (en) Non-volatile storage module having magnetic random access memory (MRAM) with a buffer window
TWI438629B (zh) 記憶體系統以及其初始化方法
KR20110013867A (ko) 메모리 링크 아키텍쳐에서 플래시 레스 부팅 기능을 갖는 멀티 프로세서 시스템
TWI790456B (zh) 記憶體定址方法及相關聯的控制器
US6523755B2 (en) Semiconductor memory device
KR20110013868A (ko) 멀티 코멘드 셋 동작 및 우선처리 동작 기능을 갖는 멀티 프로세서 시스템
US7302529B2 (en) Method for comparing contents of memory components
US8886915B2 (en) Multiprocessor system having direct transfer function for program status information in multilink architecture
JP2004102508A (ja) 半導体記憶装置
US6131177A (en) System including a ferroelectric memory
US20050157563A1 (en) Memory Device and mobile communication device using a specific access procedure
US6883078B2 (en) Microcomputer with reduced memory usage and associated method
JP2002207715A (ja) マイクロコンピュータ及びそれに用いるメモリ制御方法
US9916103B2 (en) Memory control device, memory device, and memory control method
JP2003345650A (ja) フラッシュメモリシステム
US20030200401A1 (en) Microcomputer system automatically backing-up data written in storage medium in transceiver, and transceiver connected thereto
US20010012326A1 (en) Interface circuit and method for transmitting data between a serial interface and a processor
KR101639946B1 (ko) 듀얼 포트 메모리 시스템의 접근 제어 방법
KR20210008216A (ko) 메모리 장치 및 이를 포함하는 메모리 시스템
JP2020170448A (ja) 情報処理システム

Legal Events

Date Code Title Description
AS Assignment

Owner name: NOKIA CORPORATION, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MAKELA, JAKKE;VIHMALO, JUKKA-PEKKA;AHVENAINEN, MARKO T.;REEL/FRAME:015140/0522;SIGNING DATES FROM 20040312 TO 20040315

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: NOKIA TECHNOLOGIES OY, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035558/0700

Effective date: 20150116

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001

Effective date: 20170912

Owner name: NOKIA USA INC., CALIFORNIA

Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001

Effective date: 20170913

Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS

Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001

Effective date: 20170913

AS Assignment

Owner name: NOKIA US HOLDINGS INC., NEW JERSEY

Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682

Effective date: 20181220

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: 11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1556); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104

Effective date: 20211101

Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104

Effective date: 20211101

Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723

Effective date: 20211129

Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723

Effective date: 20211129

AS Assignment

Owner name: RPX CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001

Effective date: 20211129

AS Assignment

Owner name: BARINGS FINANCE LLC, AS COLLATERAL AGENT, NORTH CAROLINA

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:RPX CORPORATION;REEL/FRAME:063429/0001

Effective date: 20220107