Secure communication between middleware and network

By using encrypted communication and intermediate signature in the memory device, the problem of information transmission security in the memory device is solved, and the secure and reliable transmission of information is achieved.

CN113728582BActive Publication Date: 2024-12-03MICRON TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080030989.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-03-25
Filing Date
2020-03-04
Publication Date
2024-12-03
Estimated Expiration
2040-03-04

AI Technical Summary

Technical Problem

The prior art is difficult to securely transmit and retrieve information in memory devices, and is susceptible to interception and manipulation by hackers or malicious entities, resulting in data security and reliability problems.

Method used

By implementing encrypted communication between the intermediate device and the network device, encrypting the identifier using the network public key and providing it with the intermediate signature to ensure authorized transmission and verification of the information, ensuring the security and integrity of the information.

Benefits of technology

Secure communication of information in the memory device is realized, unauthorized access and tampering are prevented, and reliable transmission and storage of information are ensured.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113728582B_ABST
    Figure CN113728582B_ABST
Patent Text Reader

Abstract

The present disclosure includes apparatus, methods, and systems for secure communication between an intermediate device and a network. An example apparatus includes a memory and a circuit system. The circuit system is configured to, in response to receiving a request for information corresponding to a specific category, determine an identifier associated with the specific category. The circuit system is further configured to provide the determined identifier to a network device together with a signature, wherein the requested information is received in response to the network device verifying the signature.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to semiconductor memory and methods, and more particularly, to secure communications between an intermediary device and a network. Background Art

[0002] Memory devices are typically provided as internal semiconductor integrated circuits and / or external removable devices in computers or other electronic devices. There are many different types of memory, including volatile and non-volatile memory. Volatile memory may require power to maintain its data, and may include random access memory (RAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (SDRAM), etc. Non-volatile memory can provide permanent data by saving the stored data when not powered, and may include NAND flash memory, NOR flash memory, read-only memory (ROM), and resistance variable memory, such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetic random access memory (MRAM), etc.

[0003] Memory devices may be combined together to form solid state drives (SSDs), embedded multimedia cards (e.MMCs), and / or universal flash storage (UFS) devices. SSDs, e.MMCs, and / or UFS devices may include non-volatile memory (e.g., NAND flash memory and / or NOR flash memory), and / or may include volatile memory (e.g., DRAM and / or SRAM), as well as various other types of non-volatile and volatile memory. Non-volatile memory may be used in a wide range of electronic applications, such as personal computers, portable memory sticks, digital cameras, cellular phones, portable music players such as MP3 players, movie players, and the like.

[0004] Flash memory devices may include memory cells that store data in a charge storage structure such as a floating gate. Flash memory devices typically use single-transistor memory cells that allow for high memory density, high reliability, and low power consumption. Resistance variable memory devices may include resistive memory cells that can store data based on the resistance state of a storage element (e.g., a resistive memory element having a variable resistance).

[0005] Memory cells can be arranged in an array, and memory cells in the array architecture can be programmed to a target (e.g., desired) state. For example, charge can be placed on or removed from a charge storage structure (e.g., a floating gate) of a flash memory cell to program the cell to a specific data state. The stored charge on the charge storage structure of the cell can indicate the threshold voltage (Vt) of the cell. The state of a flash memory cell can be determined by sensing the stored charge (e.g., Vt) on the charge storage structure of the cell.

[0006] Many threats can affect the data stored in the memory cells of a memory device. For example, such threats may include failures occurring in the memory device and / or threats from hackers or other malicious users. Such threats may cause significant financial losses, and / or may cause significant safety and / or security issues. Summary of the invention

[0007] In one aspect, the present application provides an apparatus comprising: a memory; and a controller configured to: in response to receiving a request for information corresponding to one or more categories, determine one or more identifiers used to identify the one or more categories; encrypt the determined one or more identifiers using a network public key previously received from a network device; and provide the determined and encrypted one or more identifiers together with a signature to the network device to retrieve the requested information from a network in which the network device is configured as a node in response to the network device verifying the signature.

[0008] In another aspect, the present application provides a method comprising: in response to receiving a request for information corresponding to multiple categories, determining corresponding identifiers that will identify the multiple categories based on a database maintained by an intermediate device, wherein the database includes multiple tables that each correspond to a corresponding category in the multiple categories; encrypting the determined identifier using a network public key previously received from one or more network devices; and providing the determined and encrypted identifier together with an intermediate signature to the one or more network devices to retrieve the information corresponding to the multiple categories and identifiable by the identifier from the network, wherein the one or more network devices are configured as corresponding nodes of the network.

[0009] In another aspect, the present application provides a system comprising: a network device; an intermediate device configured to: in response to receiving a request for information corresponding to multiple categories, determine corresponding identifiers associated with the multiple categories; encrypt the determined identifier using a network public key received from the network device; and provide the determined encrypted identifier to the network device together with at least one of an intermediate credential or an intermediate signature; wherein the network device is configured to: decrypt the received identifier using a network private key generated together with the network public key; in response to verifying the identity of the intermediate device based on at least one of the intermediate credential or the intermediate signature, identify the information corresponding to the multiple categories based on the received identifier; and provide the data corresponding to the identified information to the intermediate device together with at least one of the network credential or the network signature. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A block diagram illustrating a system including an intermediate device and a network device according to an embodiment of the present disclosure.

[0011] Figure 2 A diagram illustrating a portion of a memory array having several physical blocks according to an embodiment of the disclosure.

[0012] Figure 3 is a block diagram of a computing system including an apparatus in the form of a memory device that can communicate with a host and / or a different memory device according to an embodiment of the present disclosure.

[0013] Figure 4A A block diagram illustrating a network including nodes and intermediaries coupled to the network according to an embodiment of the present disclosure.

[0014] Figure 4B An example of a block that can be used in a blockchain to index data in the blockchain according to an embodiment of the present disclosure is described.

[0015] Figure 4C A block diagram illustrating an example transaction stored in a block and having information and an identifier assigned to each information according to an embodiment of the present disclosure.

[0016] Figure 5 An example of a database in the form of several tables having identifiers associated with the several tables according to an embodiment of the present disclosure is described.

[0017] Fig. 6A An example of a pair of registers for defining a secure memory array according to an embodiment of the present disclosure is described.

[0018] Figure 6BA diagram illustrating a portion of a memory array including a defined secure memory array according to an embodiment of the present disclosure.

[0019] Figure 7 is a block diagram of an example system including a host and a memory device according to an embodiment of the present disclosure.

[0020] Figure 8 is a block diagram of an example process for determining several parameters according to an embodiment of the present disclosure.

[0021] Fig. 9 is a block diagram of an example process for determining several parameters according to an embodiment of the present disclosure.

[0022] Fig.10 is a block diagram of an example process for verifying credentials according to an embodiment of the present disclosure.

[0023] Fig.11 is a block diagram of an example process for verifying a signature according to an embodiment of the present disclosure.

[0024] Fig.12 is a block diagram of an example memory device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] The present disclosure includes apparatus, methods, and systems for secure communication between an intermediate device and a network. An example apparatus includes a memory and a circuit system. The circuit system is configured to, in response to receiving a request for information corresponding to a specific category, determine an identifier associated with the specific category. The circuit system is further configured to provide the determined identifier to a network device together with a signature, wherein the requested information is received in response to the network device verifying the signature.

[0026] Various communication techniques may be used to retrieve data corresponding to particular information from a database. In some instances, due to the nature of the structural complexity of the database and the necessity to retrieve particular information in a timely manner, the communication techniques used to retrieve information from the database may lack mechanisms to securely transmit the information even when there is a security necessity. For example, a hacker or other entity may intercept and / or manipulate information being retrieved from the database in order to change the information, repeat requests for the information to gain unauthorized access to an emergency vehicle or other vehicle, and the like.

[0027] Therefore, embodiments of the present disclosure provide benefits such as ensuring that information exchanged with a database is from an authorized entity and / or provided to an authorized requester. Therefore, embodiments of the present disclosure produce secure communications with a database while maintaining a certain level of performance in satisfying those information requests in a timely manner.

[0028] As used herein, "a / an" or "several" may refer to one or more of something, and "multiple" may refer to two or more of such things. For example, a memory device may refer to one or more memory devices, and multiple memory devices may refer to two or more memory devices. In addition, the designators "R", "B", "S", and "N" as used herein, particularly with respect to the reference numerals in the drawings, indicate that several of the particular features so designated may be included with several embodiments of the present disclosure. The numbers between the designations may be the same or different.

[0029] The figures herein follow a numbering convention in which the first one or more digits correspond to the figure number and the remaining digits identify an element or component in the figure. Similar elements or components between different figures may be identified by using similar numerals. For example, 201 may represent Figure 2 Component "01" in , and similar components can be found in Figure 3 It is represented as 301 in Chinese.

[0030] Figure 1 A block diagram of a system 100 including an intermediate device 102 and a network device 104 is illustrated according to an embodiment of the present disclosure. The intermediate device 102 and / or the network device 104 may be or may be part of a laptop computer, a personal computer, a digital camera, a digital recording and playback device, a mobile phone, a PDA, a memory card reader, an interface hub, or an Internet of Things (IoT) enabled device, such as an automotive (e.g., vehicle and / or transportation infrastructure) IoT enabled device or a medical (e.g., implantable and / or health monitoring) IoT enabled device, as well as other host systems, and may include a memory access device (e.g., a processor). One of ordinary skill in the art will appreciate that a "processor" may be one or more processors, such as a parallel processing system, multiple coprocessors, and the like.

[0031] Network device 104 may be a device for storing information that can be retrieved by intermediate device 102. In some examples, network device 104 may be configured as a node of a network including multiple nodes. As an example, network device 104 may be a node of a network that supports distributed ledger technology (DLT) (e.g., "block chain" technology). A distributed ledger is a database spread across several nodes or computing devices, and a block chain (e.g., a continuously growing list of encrypted records) is a database in which multiple nodes (such as a combination of nodes) are connected to each other. Figure 4A The nodes 420 described above can share and store a form of DLT in a peer-to-peer network. Additional details of the block chain network are described in conjunction with FIG.

[0032] Various information associated with the transaction may be recorded in the network device 104. As used herein, a transaction may refer to an exchange that occurs between parties (e.g., one or more parties). A transaction may involve various forms of exchange. In one example, the information that may be exchanged between the parties may include vehicle information, such as a vehicle identification number (VIN) and / or a license plate combination (e.g., letters and / or numbers) that may be used to identify a respective vehicle, a route taken by a particular vehicle for a single trip (e.g., a route taken by an emergency vehicle for a single dispatch), a station to which a particular emergency vehicle belongs, and / or a date and / or time when a particular emergency vehicle was dispatched. In another example, the exchange may be a monetary exchange, including information such as a sender (e.g., or a buyer), a receiver (e.g., or a seller), an amount exchanged between the sender and the receiver, a date on which the exchange occurs, and the like.

[0033] The intermediate device 102 is capable of communicating with the network device 104 and can perform various operations associated with the information stored in the network device 104 (e.g., as an indexer and / or a query device). In one example, the intermediate device 102 can be configured to act as an indexer to organize (e.g., index) the information stored in the network device 104 according to various categories. For example, the intermediate device 102 can be configured to index the senders that can be identified from multiple (e.g., all) transactions into the same category (e.g., sender category). Similarly, buyers, topics for which transaction data is being exchanged, etc. can be indexed into corresponding categories. In this way, embodiments of the present disclosure can provide the benefit of timely compliance with requests for information that can be distributed over multiple transactions. In another example, the intermediate device 102 can be configured to act as a query device, identifying nodes / devices (e.g., network devices, such as the network device 104) that store the requested information and retrieving the requested information from the nodes / devices. Additional details of using the intermediate device 102 as a query device / indexer are described in conjunction with Figures 4-5.

[0034] Figure 2 A diagram illustrating a portion of a memory array 201 having several physical blocks according to an embodiment of the present disclosure. The memory array 201 may be, for example, a flash memory array, such as a NAND flash memory array. As an additional example, the memory array 201 may be a resistance variable memory array, such as a PCRAM, RRAM, MMRAM, or a spin torque transfer (STT) array, among others. However, embodiments of the present disclosure are not limited to a particular type of memory array. Additionally, the memory array 201 may be a secure memory array, as will be further described herein. Furthermore, although Figure 2 Not shown in FIG. 2 , memory array 201 may be located on a particular semiconductor die along with various peripheral circuitry associated with its operation.

[0035] like Figure 2As shown in , the memory array 201 has several physical blocks 207-0 (block 0), 207-1 (block 1), ..., 207-B (block B) of memory cells. The memory cells may be single-level cells and / or multi-level cells, such as two-level cells, three-level cells (TLC), or quad-level cells (QLC). As examples, the number of physical blocks in the memory array 201 may be 128 blocks, 512 blocks, or 1024 blocks, but embodiments are not limited to a specific power of two or any specific number of physical blocks in the memory array 201.

[0036] A plane of memory cells may include several physical blocks of memory cells (e.g., blocks 207-0, 207-1, ..., 207-B), and a die may include several planes of memory cells. Figure 2 In the example shown in , each physical block 207-0, 207-1, ..., 207-B can be part of a single die. That is, Figure 2 The portion of memory array 201 illustrated in may be a die of memory cells.

[0037] like Figure 2 As shown in , each physical block 207-0, 207-1, ..., 207-B includes a number of physical rows (e.g., 203-0, 203-1, ..., 203-R) of memory cells coupled to access lines (e.g., word lines). The number of rows (e.g., word lines) in each physical block can be 32, but embodiments are not limited to a specific number of rows 203-0, 203-1, ..., 203-R per physical block. In addition, although Figure 2 Not shown, but memory cells can be coupled to columns of sense lines (eg, data lines and / or digit lines).

[0038] As will be appreciated by those skilled in the art, each row 203-0, 203-1, ..., 203-R may include several pages (e.g., physical pages) of memory cells. A physical page refers to cells that are programmed and / or sensed (e.g., several memory cells that are programmed and / or sensed together as a functional group). Figure 2In the embodiment shown in , each row 203-0, 203-1, ..., 203-R includes one physical page of memory cells. However, the embodiments of the present disclosure are not limited thereto. For example, in an embodiment, each row may include multiple physical pages of memory cells (e.g., one or more even memory cell pages are coupled to even-numbered data lines, and one or more odd memory cell pages are coupled to odd-numbered data lines). In addition, for embodiments including multi-level cells, a physical page of memory cells may store multiple data pages (e.g., logical pages) (e.g., an upper data page and a lower data page, where each cell in the physical page stores one or more bits toward the upper data page and one or more bits toward the lower data page).

[0039] like Figure 2 As shown in , a memory cell page may include several physical sectors 205-0, 205-1, ..., 205-S (e.g., subsets of memory cells). Each physical sector 205-0, 205-1, ..., 205-S of a cell may store several logical data sectors. In addition, each logical data sector may correspond to a portion of a particular data page. As an example, a first logical sector of data stored in a particular physical sector may correspond to a logical sector corresponding to a first data page, and a second logical sector of data stored in a particular physical sector may correspond to a second data page. Each physical sector 205-0, 205-1, ..., 205-S may store system and / or user data, and / or may include overhead data, such as error correction code (ECC) data, logical block address (LBA) data, and metadata.

[0040] Logical block addressing is a scheme that a host can use to identify logical sectors of data. For example, each logical sector may correspond to a unique logical block address (LBA). In addition, an LBA may also correspond to (e.g., dynamically map to) a physical address, such as a physical block address (PBA), that may indicate the physical location of a logical sector of data in memory. A logical sector of data may be a number of bytes of data (e.g., 256 bytes, 512 bytes, 1,024 bytes, or 4,096 bytes). However, embodiments are not limited to these examples.

[0041] It should be noted that other configurations for physical blocks 207-0, 207-1, ..., 207-B, rows 203-0, 203-1, 203-R, sectors 205-0, 205-1, ..., 205-S, and pages are possible. For example, rows 203-0, 203-1, ..., 203-R of physical blocks 207-0, 207-1, ..., 207-B may each store data corresponding to a single logical sector, which may include, for example, more or less than 512 bytes of data.

[0042] Figure 32 is a block diagram of a computing system 200 including an apparatus in the form of a memory device 306 that can communicate with a host and / or a different memory device according to an embodiment of the present disclosure. The host 309 and the memory device 306 may be similar to the one in combination with Figure 1 The intermediate device 102 and / or network device 104 described herein. As used herein, "device" may refer to, but is not limited to, any of a variety of structures or combinations of structures, such as a circuit or circuit system, one or more dies, one or more modules, one or more devices, or one or more systems. In addition, in one embodiment, the computing system 200 may include several memory devices similar to the memory device 306.

[0043] exist Figure 3 In the embodiment described in FIG. 1 , the memory device 306 may include a memory 316 having a memory array 301. The memory array 301 may be similar to the memory array 316 described previously in conjunction with FIG. Figure 2 Memory array 301 is described. In addition, memory array 301 can be a secure array, as will be further described herein. Figure 3 One memory array 301 is shown in FIG. 3 , but memory 316 may include any number of memory arrays similar to memory array 301 .

[0044] like Figure 3 , host / memory device 309 can be coupled to memory device 306 via interface 333. Host / memory device 309 and memory device 306 can communicate over interface 333 (eg, send commands and / or data).

[0045] Host / memory device 309 and / or memory device 306 may be or be part of a portable computer, a personal computer, a digital camera, a digital recording and playback device, a mobile phone, a PDA, a memory card reader, an interface hub, or an Internet of Things (IoT) enabled device, such as an automotive (e.g., vehicle and / or transportation infrastructure) IoT enabled device or a medical (e.g., implantable and / or health monitoring) IoT enabled device, as well as other host systems, and may include a memory access device (e.g., a processor). A person of ordinary skill in the art will understand that a "processor" may be one or more processors, such as a parallel processing system, multiple coprocessors, etc.

[0046] The interface 333 may be used for wired and / or wireless communication between the host / memory device 309 and the memory device 306. In one example, the interface 333 may be in the form of a standardized physical interface. For example, when the memory device 306 is used for information storage in the computing system 200, the interface 333 may be a Serial Advanced Technology Attachment (SATA) physical interface, a Peripheral Component Interconnect Express (PCIe) physical interface, a Universal Serial Bus (USB) physical interface, or a Small Computer System Interface (SCSI), among other physical connectors and / or interfaces. However, in general, the interface 333 may provide an interface for transferring control, address, information (e.g., data), and other signals between the memory device 306 and a host / memory device 309 having a compatible receiver for the interface 333.

[0047] In another example, interface 333 may be an interface for wireless communication technology, such as different generations of broadband mobile telecommunication technology (e.g., 1-5G), device-to-device communication including Bluetooth, Zigbee, 1-5G and / or Long Term Evolution (LTE) device-to-device communication technology, and / or other wireless communications utilizing another device (e.g., WiFi utilizing an access point AP), which may be used to communicate with different entities.

[0048] Memory device 306 includes a controller 308 that communicates with a host / memory device 309 and memory 316 (e.g., memory array 301). For example, controller 308 may send commands to perform operations on memory array 301, including operations to sense (e.g., read), program (e.g., write), move, and / or erase data, among other operations.

[0049] The controller 308 may be included on the same physical device (e.g., the same die) as the memory 316. Alternatively, the controller 308 may be included on a separate physical device that is communicatively coupled to the physical device that includes the memory 316. In an embodiment, the components of the controller 308 may be spread across multiple physical devices as a distributed controller (e.g., some components on the same die as the memory and some components on different dies, modules, or boards).

[0050] Host / memory device 309 may include a host controller ( Figure 3 309). The host controller may send commands to the memory device 306 via the interface 333. The host controller may communicate with the memory device 306 and / or the controller 308 on the memory device 306 to read, write and / or erase data, among other operations. In addition, in an embodiment, the host / memory device 309 may be an IoT-enabled device with IoT communication capabilities as previously described herein.

[0051] The controller 308 on the memory device 306 and / or the host controller on the host / memory device 309 may include control circuitry and / or logic (e.g., hardware and firmware). In an embodiment, the controller 308 on the memory device 306 and / or the host controller on the host / memory device 309 may be an application specific integrated circuit (ASIC) coupled to a printed circuit board that includes the physical interface. Also, the memory device 306 and / or the host / memory device 309 may include a buffer and a number of registers of volatile and / or non-volatile memory.

[0052] like Figure 3 As shown in , the memory device may include circuitry 335. Figure 3 In the embodiment illustrated in , the circuit system 335 is included in the controller 308. However, the embodiments of the present disclosure are not limited thereto. For example, in an embodiment, the circuit system 335 may be included in the memory 316 (e.g., on the same die) (e.g., instead of the controller 308). The circuit system 335 may include, for example, hardware, firmware, and / or software.

[0053] In an embodiment, the circuit system 335 may divide the data stored in the memory array 301 into multiple segments and associate a different cryptographic hash with each respective segment. For example, the circuit system 335 may use an authenticated (e.g., secure) and anti-replay protected command received from the host / memory device 309 to generate (e.g., calculate) a different cryptographic hash for each respective segment (e.g., so that only the memory device 306 knows these cryptographic hashes and only the memory device 306 can generate and update these cryptographic hashes). The cryptographic hash generated for each respective segment may be referred to herein as a golden hash of the segment and may include, for example, a SHA-256 cryptographic hash. These golden hashes may be stored in a specific location (e.g., a register) of the circuit system 335 that is not accessible to the memory device 306 and / or a user of the host / memory device 309 (e.g., a "hidden" area of ​​the memory device 306) and may be used during the process of verifying the data stored in the memory array 301, as will be further described herein.

[0054] Each segment defined by circuit system 335 may correspond to a block (e.g., block 337) of a block chain, and multiple segments defined by circuit system 335 may correspond to a block chain. Thus, a block chain may be stored in memory array 301. The block chain within memory array 301 may be an indexed block chain, such as previously associated with Figure 1 The described index block chain 120. However, the embodiment is not limited thereto. As an example, the block chain within the memory array 301 may be a global block chain, such as the one previously described in conjunction with Figure 1 The global blockchain 110 is described.

[0055] A block may contain a header, a cryptographic hash of the previous block, a cryptographic graph hash of the data stored in the block, and a digital signature.

[0056] A cryptographic hash of the data stored in memory array 301 may be generated (e.g., calculated), for example, by circuitry 335. In this example, the cryptographic hash of the stored data may be generated internally by memory device 306 without moving external data over interface 333. As an additional example, the cryptographic hash of the data may be transmitted from an external entity. For example, host / memory device 309 may generate a cryptographic hash of the data stored in memory array 301 and send the generated cryptographic hash to memory device 306 (e.g., circuitry 335 may receive the cryptographic hash of the data stored in memory array 301 from host / memory device 309).

[0057] The digital signature associated with block 337 may be generated (e.g., calculated), for example, by circuit system 335 based on (e.g., in response to) an external command (e.g., a command received from host / memory device 309). For example, the digital signature may be generated using symmetric or asymmetric cryptography. As an additional example, host / memory device 309 may generate a digital signature and send (e.g., provide) the generated digital signature to memory device 306 (e.g., circuit system 335 may receive the digital signature from host / memory device 309).

[0058] The blocks of the block chain including block 337 may be stored in a secure array of memory array 301. In such embodiments, a pair of non-volatile registers may be used to define the secure array. Figure 3 In the embodiment described in , the circuit system 335 includes registers 314-1 and 314-2 that can be used to define the security array. For example, register 314-1 can define the address of the security array (e.g., the starting LBA of the data), and register 314-2 can define the size of the security array (e.g., the ending LBA of the data). Figure 6A-6B ) will be further described in detail below. Once the security array is defined, the circuit system 335 can be used to generate (e.g., calculate) a cryptographic hash associated with the security array using authenticated anti-replay protection commands (e.g., such that only the memory device 306 knows the golden hash and only the memory device 306 can generate and update the golden hash), which may be referred to herein as the golden hash. The golden hash can be stored in an inaccessible portion of the memory array 301 (e.g., the same inaccessible portion in which the block 337 is stored) and can be used in the process of verifying the data of the security array, as will be further described herein.

[0059] The circuit system 335 may verify (e.g., during power-on) data stored in each respective segment of the first plurality of segments using the golden hash associated with the respective segment. As used herein, verifying data may include and / or refer to authenticating and / or confirming that the data is authentic (e.g., the same as originally programmed data) and has not been altered by hacking activity or other unauthorized changes.

[0060] For example, the circuit system 335 may generate (e.g., calculate) a different runtime cryptographic hash of the data stored in each respective segment of the first number of segments, and compare the runtime cryptographic hash generated for the data stored in each respective segment to a golden hash previously generated (e.g., and stored in a register in the circuit system 335). Based on the comparison indicating that the runtime cryptographic hash generated for the data stored in the respective segment matches the golden hash of the respective segment, it may be determined that the data stored in the respective segment has not been altered, and thus the data stored in the respective segment may be verified (e.g., may be determined to be valid). Thus, the data stored in each respective segment may be verified in a manner independent of the data stored in the other segments.

[0061] However, if the comparison indicates that the runtime cryptographic hash generated for the data stored in the respective segment does not match the golden hash of the respective segment, this may indicate that the data stored in the respective segment has been altered (e.g., due to a hacker or a malfunction in the memory), and thus the data stored in the respective segment may not be valid (e.g., may be determined to be invalid). In this case, the circuit system 335 may repair (e.g., attempt to repair) the data stored in the respective segment. Repairing the data stored in the respective segment may include, for example, determining whether data repair is allowed, and if repair is allowed, retrieving the data from the memory 316 (e.g., from a repair block included in the memory, such as in conjunction with Fig.12 The repair block 1260 ) described further recovers (eg, restores) the data.

[0062] The memory device 306 (e.g., the circuit system 335) may send the block 337 along with the digital signature associated with the block 337 to the host / memory device 309 via the interface 333 to verify the data stored in the memory array 301. For example, in response to the memory device 306 being powered (e.g., powered on and / or powered up), the circuit system 335 may sense (e.g., read) the block 337 stored in the memory array 301 and send the sensed block to the host / memory device 309 to verify the data stored in the array 301. Thus, verification of the data stored in the memory array 301 may be initiated (e.g., automatically) when the memory device 306 is powered.

[0063] As an additional example, the circuit system 335 can send the block 337 along with the digital signature associated with the block 337 to the host / memory device 309 when an external entity, such as the host / memory device 309, initiates verification of the data stored in the memory array 301. For example, the host / memory device 309 can send a command to sense the block 337 to the memory device 306 (e.g., the circuit system 335), and the circuit system 335 can execute the command of the sense block 337 in response to receiving the command and send the sensed block to the host / memory device 309 to verify the data stored in the array 301.

[0064] Upon receiving block 337, the host / memory device 309 may verify (e.g., determine whether to verify) the data stored in the memory array 301 using the received block. For example, the host / memory device 309 may verify the data using a cryptographic hash of the previous block in the block chain and a cryptographic hash of the data stored in the memory array 301. In addition, the host / memory device 309 may verify the digital signature associated with the block 337 to determine that the block is included (e.g., eligible for inclusion) in the block chain. As used herein, verifying the data stored in the memory array 301 may include and / or refer to authenticating and / or confirming that the data is authentic (e.g., the same as originally programmed data) and has not been altered by hacking or other unauthorized changes.

[0065] In embodiments where the memory array 301 is a secure array, the golden hash previously described herein may also be used to verify data stored in the memory array 301. For example, a runtime cryptographic hash may be generated (e.g., calculated) and compared to the golden hash. If the comparison indicates that the runtime and golden hashes match, then it may be determined that the secure array has not been altered, and therefore the data stored therein is valid. However, if the comparison indicates that the runtime and golden hashes do not match, then this may indicate that the data stored in the secure array has been altered (e.g., due to a hacker or a malfunction in the memory), and this may be reported to the host / memory device 309.

[0066] After verifying the data stored in memory array 301, circuit system 335 may generate an additional (e.g., next) block in the block chain for use in verifying the data stored in memory array 301 in a manner similar to the generation of block 337. For example, this additional block may include a cryptographic hash of block 337 (which now becomes the previous block in the block chain) and a new cryptographic hash of the data stored in memory array 301. In addition, this additional block may include a header with a timestamp indicating when this block was generated, and may have a digital signature associated with it indicating that this block is included in the block chain. This document will (for example, in conjunction with Figure 3) further describes an example for illustrating such additional local blocks. In addition, in embodiments where the memory array 301 is a secure array, additional (eg, new) golden hashes may be generated.

[0067] The additional block and the digital signature and additional golden hash associated with the additional block can be stored in the memory array 301. For example, the additional block can replace the block 337 (e.g., the previous block) in the memory array 301. The additional block, digital signature, and additional golden hash can then be used by the host / memory device 309 to verify the data stored in the memory array 301, in a manner similar to that previously described herein for block 337. Additional blocks in the chain of blocks can continue to be generated by the circuit system 335 in this manner throughout the useful life of the memory device 306 and used by the host / memory device 309 to verify the data stored in the memory array 301.

[0068] Figure 3 The embodiments described herein may include additional circuitry, logic, and / or components that are not described so as not to obscure the embodiments of the present disclosure. For example, memory device 306 may include address circuitry that latches address signals provided on an I / O connector by I / O circuitry. A row decoder and a column decoder may receive and decode address signals to access memory array 301. Additionally, memory device 306 may include a main memory, such as a DRAM or SDRAM, that is separate from and / or included in addition to memory array 301. Fig.12 ) further describes examples of additional circuit systems, logic, and / or components used to further illustrate memory device 306.

[0069] 4 illustrates a block diagram of an example blockchain network 410 including nodes and an intermediate device 402 coupled to the blockchain network according to an embodiment of the present disclosure. Although the network 410 illustrated in FIG4 includes four nodes, such as 420-1, 420-2, 420-3, and 420-4 (collectively referred to as nodes 420), embodiments are not limited to a specific number of nodes that the network 410 may include.

[0070] The network 410 may support distributed ledger technology (DLT), such as "blockchain" technology. A "blockchain" is a growing list of encrypted records. A blockchain is a form of DLT in which multiple nodes (e.g., node 420) can share and store a distributed list of records in a peer-to-peer network. As described herein, a "block" in a blockchain is a collection of information, such as data, headers, transactions, encryption, etc. If a block is verified, it can be added to the growing list of records in the ledger. Blocks are added to the blockchain ledger in chronological order.

[0071] A distributed ledger is a database spread across several nodes or computing devices (e.g., nodes 420). As an example, a given node (e.g., one or more nodes 420) may maintain a copy of a current list or record in a ledger manner. Nodes 420 may each represent a different host (e.g., a computing device with processing resources). For ease of illustration, a host or multiple nodes (e.g., nodes 420) may be considered in relation to a blockchain of autonomous and / or non-autonomous transportation vehicles, cars, buses, emergency vehicles, etc. However, embodiments are not limited to this example.

[0072] Various wireless communication technologies may be utilized when communicating with different nodes 420 (and / or between the network 410 and the intermediate device 402). For example, different generations of broadband mobile communication technologies (e.g., first to fifth generations (1-5G)), device-to-device (e.g., vehicle-to-vehicle (v2v)) communications including Bluetooth, Zigbee, and / or LTE device-to-device communication technologies, and / or other wireless communications utilizing intermediate devices (e.g., WiFi utilizing an access point (AP)) may be used for communication with different nodes.

[0073] In the example, in combination Figure 1 The network device 104 illustrated in the description of may be configured as at least one of the nodes 420 of the network 410. The network device of the node 420 may perform secure communications among the nodes and / or with the intermediate device 402 to add / modify data stored in the network device. Secure communications may be performed in various ways (e.g., at both the device level and the network level). In one example for device-level authentication, data being communicated among the nodes 420 and / or with the intermediate device 402 may be discarded / rejected before the identity of the data transmitter (e.g., one of the nodes 420 and / or intermediate devices 402 that transmits data to other nodes 420 and / or intermediate devices 402) and / or the data itself is verified. As described herein, various mechanisms may be used for authentication. For example, credentials (e.g., 881 and / or 982) provided from the transmitter may be used (e.g., as combined with Fig.10 ) and / or using a signature contained within the data (e.g., as combined with Figure 4B In another example for device-level authentication, data being communicated between node 420 and / or intermediate device 102 may be provided as encrypted, such as in conjunction with Figure 8 and 9 As an example for network level authentication, each network device may communicate with other network devices configured as other nodes for performing, for example, Merkle tree authentication.

[0074] Each network device being configured as at least a portion of node 420 may include firmware that performs the functions of device-level and / or network-level verification. In one embodiment, individual network devices may be configured to perform both device-level and network-level verification. In another example, when a first network device may be configured to perform device-level verification, a second network device (e.g., a bridge controller) coupled to the first network device may be configured to communicate with other nodes and perform network-level verification (e.g., and device-level verification) instead of the first network device. In this example, having two different network devices that are both configured to perform device-level verification can provide benefits such as further strengthening communication security by performing device-level verification twice. In an example, the first and / or second network device may be configured to and act as a node (e.g., node 420) of network 410.

[0075] Intermediary device 402 coupled to network 410 may operate as an indexer and / or a query device. In one example, as an indexer, intermediary device 402 may be configured to organize information of a transaction (e.g., organized in chronological order among nodes 420) in a manner that more efficiently retrieves specific information (e.g., that may be stored in multiple transactions and / or nodes 420). As an example, intermediary device 402 may be configured to assign each information stored in a transaction a corresponding identifier indicating a category to which the information belongs.

[0076] In another example, as a query device, the intermediary device 402 may be configured to receive a request for specific information stored in the network 410 and retrieve the specific information from the network 410 in a secure manner. The intermediary device 402 as a query device may be a programmable silicon device capable of performing high-speed symbolic pattern matching, which allows for comprehensive search and analysis of complex and / or unstructured databases (e.g., the network 410). In an example where information stored in a transaction is assigned a corresponding identifier, the intermediary device 402 may be configured to retrieve the information using the identifier assigned to the information. Additional details of utilizing the intermediary device 402 as an indexer / query device are described below.

[0077] Figure 4B The embodiment of the present disclosure can be used for indexing in a block chain (for example, in conjunction with Figure 3 4. For example, the example of a block of data (e.g., block 426-1 and block 426-2) in a chain of blocks in the memory array 301 described above may be used in conjunction with Figure 3 The depicted circuitry 310 generates blocks 426-1 and 426-2. For example, block 426-2 may be generated after block 426-1 has been used to verify data stored in memory (eg, block 426-2 may be the next block in the chain of blocks after block 426-1).

[0078] like Figure 4B As shown in FIG. 1 , each respective block 426-1 and 426-2 may include a header, a cryptographic hash of the previous block in the block chain, and a cryptographic hash of the data stored in the memory, in a manner similar to that previously described in conjunction with FIG. Figure 3 Block 337 is described. For example, block 426-1 includes a header 428-1 with a timestamp indicating when block 426-1 was generated, a cryptographic hash 430-1 of a previous block in the block chain, and a cryptographic hash 432-1 of data stored in memory. In addition, block 426-2 includes a header 428-2 with a timestamp indicating when block 426-2 was generated, a cryptographic hash 430-2 of a previous block in the block chain (e.g., block 426-1), and a subsequent (e.g., new) cryptographic hash 432-2 of data stored in memory.

[0079] like Figure 4B As shown in , the cryptographic hash 432-1 of block 426-1 may be used as the cryptographic hash 430-2 of block 426-2. That is, block 426-2 may contain the cryptographic hash 432-1 of the data stored in memory from block 426-1 as the cryptographic hash 430-2 of the previous block in the block chain.

[0080] like Figure 4B As shown in Figure 3 As described above with respect to block 337, each respective block 426-1 and 426-2 may have a digital signature associated therewith (e.g., digital signatures 434-1 and 434-2, respectively) indicating that the block is included in the block chain. For example, digital signature 434-1 is associated with block 426-1, and digital signature 434-2 is associated with block 426-2. Figure 4B It is not specified, but each block 426 may also contain transactions, such as Figure 4C Transaction 427 described in .

[0081] Figure 4C A block diagram illustrating an example transaction stored in a block and having information and an identifier assigned to each information according to an embodiment of the present disclosure. Transaction 427 may be stored in a block similar to that in conjunction with Figure 4B In the blocks described in blocks 426-1 and / or 426-2.

[0082] like Figure 4C As shown in FIG. 4 , transaction 427 includes various information, such as the parties associated with transaction 427 (e.g., parties 417-1 (e.g., party_1) and 417-2 (party_2)) and transaction information 419-1, ..., 419-X. Although two parties are described as being included in transaction 427, embodiments are not limited to the number of parties associated with and / or included in transaction 427. Figure 1As described, parties 417-1 and 417-2 may be a sender and a receiver, respectively. As an example, in a monetary transaction, party 417-1 may be a payer and party 417-2 may be a payee of the transaction. Example transaction information (e.g., transaction information 419-1, ..., 419-X) may include a vehicle identification number (VIN) and / or a license plate combination (e.g., letters and / or numbers) that may be used to identify a corresponding vehicle, a route taken by a particular vehicle for a single trip (e.g., a route taken by an emergency vehicle for a single dispatch), a station to which a particular emergency vehicle belongs and / or the date, time, amount of money exchanged between the sender and the receiver, and the date the exchange occurred, as previously described in conjunction with Figure 1 described.

[0083] In some examples, the same identifier may be assigned to each party (e.g., party 417-1 and party 417-2). In this example, the sender (e.g., payer) and the receiver (e.g., payee) may be identified separately by assigning flags to each party. For example, Figure 4C , party 417 - 1 is assigned a flag of “S” to indicate that party 417 - 1 is a sender, and party 417 - 2 is assigned a flag of “R” to indicate that party 417 - 2 is a receiver.

[0084] Each identifier (eg, identifier 423-1, ..., 423-P) may be used to identify the corresponding category to which each piece of information belongs. Figure 5 Further describing, identifiers may be associated with each other. Associating identifiers with each other may be used to retrieve information associated with multiple categories. As an example, an intermediate device (e.g., intermediate device 402) may receive a request to retrieve information corresponding to multiple categories associated with "buyers who purchased a specific product during a specific time period" and / or "extracting all models, brands, and credential data for any vehicle using a specific version of firmware", such as characteristics of a party (e.g., a recipient and / or a sender), products associated with a transaction, data when each transaction occurred, etc. In this example, the intermediate device may provide those identifiers associated with the multiple information to a node (e.g., node 420) of a network (e.g., network 410) so that specific information corresponding to the multiple categories can be identified based on the provided identifiers. In combination Figure 5 Describes additional details of using identifiers to retrieve information.

[0085] Figure 5 An example of a database in the form of several tables having identifiers associated with the several tables according to an embodiment of the present disclosure is illustrated. A particular device, such as the intermediate device 102, may generate, update and / or maintain tables 515-1, 515-2, 515-3, 515-4, 515-5, 515-6 and / or 515-7 (collectively referred to as tables 515).

[0086] Table 515 may correspond to a corresponding category (e.g., include information corresponding to a corresponding category). Example categories corresponding to table 515 may include customer (e.g., customer's name, address, phone number, and / or customer number), order (e.g., order number, order data, required data, shipping data, status, notes, customer number of order), quote (e.g., quote date), bill (e.g., bill date), item (e.g., item name and / or price), order details (e.g., order quantity), and / or invoice (e.g., invoice date), although embodiments are not limited thereto.

[0087] like Figure 5 As described in , each table is assigned a specific identifier. As an example, table 515-1 is assigned identifier 513-1, table 515-2 is assigned identifier 513-2, table 515-3 is assigned identifier 513-3, table 515-4 is assigned identifier 513-4, table 515-5 is assigned identifier 513-5, table 515-6 is assigned identifier 513-6, and table 515-7 is assigned identifier 513-7. Identifiers 513-1, ..., 513-7 (collectively referred to as identifiers 513) can be used to access data stored in table 515 and / or store the location of information corresponding to the corresponding identifier. As an example, the information of each table (e.g., table 515) can be virtually stored in the intermediate device 102, and the physical data corresponding to the virtual data of table 515 is stored in the network, and the network device (e.g., network device 104) in the network is configured as a node of the network. As an example, each table (eg, table 515) may include an address for each message, and the address may be used to locate the location (eg, within a network) where physical data corresponding to each message is stored.

[0088] In an example, table 515 may be stored in various locations. In an example, table 515 may be stored in intermediate device 402 and / or network 410 described in conjunction with FIG. 4 (eg, may be distributed on one or more nodes 410).

[0089] Each table 515 is coupled (e.g., linked) to each other. Figure 5 As illustrated in , table 515-1 is coupled to table 515-2, table 515-2 is coupled to 515-3, 515-4, 515-6, and 515-7, and table 515-5 is coupled to table 515-6. Information stored in those tables coupled to each other can be accessed using keys stored in each table (e.g., in sequence). As an example, table 515-1 can be accessed from table 515-2 using key 575-1, table 515-2 can be accessed from tables 515-6, 515-3, 515-4, and 515-7 using keys 575-5, 575-2, 575-3, and 575-4, respectively, and table 515-5 can be accessed from table 515-6 using key 575-6.

[0090] Thus, information corresponding to multiple categories (e.g., specific customers who purchased specific products during a specific time period) may be retrieved from multiple tables using key 575 stored in table 515. As an example, when retrieving information corresponding to categories of tables 515-1, 515-2, and 515-3, table 515-3 may be accessed first, then table 515-2 may be accessed using key 575-2 stored in table 515-3, and then table 515-1 may be accessed using key 575-1 stored in table 515-1. Similarly, when retrieving information corresponding to categories of tables 515-1, 515-2, and 515-4, table 515-4 may be accessed first, then table 515-2 may be accessed using key 575-3 stored in table 515-4, and then table 515-1 may be accessed using key 575-1 stored in table 515-1. Similarly, when retrieving information corresponding to the categories of tables 515-1, 515-2, and 525-7, table 515-7 may be accessed first, then table 515-2 may be accessed using key 575-4 stored in table 515-7, and then table 515-1 may be accessed using key 575-1 stored in table 515-1. Similarly, when retrieving information corresponding to the categories of tables 515-1, 515-2, and 525-6, table 515-6 may be accessed first, then table 515-2 may be accessed using key 575-5 stored in table 515-6, and then table 515-1 may be accessed using key 575-1 stored in table 515-1. Similarly, when retrieving information corresponding to a category of tables 515-5 and 515-6, table 515-6 may be accessed first, and then table 515-5 may be accessed using key 575-5 stored in table 515-6.

[0091] A particular device / node, such as intermediary 402, may maintain table 515. In one example, intermediary 402 may keep track of information that has been recently added to table 515. As an example, a recently occurring transaction may be added to network 410, and in this example, a category corresponding to the information associated with the new transaction may be determined, and the information may be distributed to the corresponding table according to its determined category. In this way, intermediary 402 does not need to identify what category the information belongs to each time a corresponding transaction is added to network 410, which may provide benefits such as retrieving information in a timely manner and providing the retrieved information to the requester.

[0092] Combination Figure 7-11 Describes additional details for retrieving information stored on the network and / or in tables in a secure manner.

[0093] Fig. 6A An example of a pair of registers 614-1 and 614-2 for defining a secure memory array according to an embodiment of the present disclosure is illustrated, and Figure 6B A diagram illustrating a portion of a memory array 601 including a secure memory array defined using registers 614-1 and 614-2 according to an embodiment of the present disclosure. For example, registers 614-1 and 614-2 may be respectively the same as previously described in connection with Figure 3 The registers 314-1 and 314-2 described above, and for example, the secure memory array 601 may be previously combined with Figure 3 The memory array 301 described above. For example, Figure 6B As shown in FIG. 6 , the secure memory array 601 may include a plurality of physical blocks of memory cells 607-0, 607-1, ..., 607-B, each physical block including a plurality of physical rows 603-0, 603-1, ..., 603-R having a plurality of memory cell sectors, in a manner similar to that previously described in conjunction with FIG. Figure 2 A memory array 201 is described.

[0094] like Fig. 6A As shown in , register 614-1 can define the address of the security array (e.g., the address of the different parts of the security array), and register 614-2 can define the size of the security array (e.g., the size of the different parts of the security array). The address of the security array defined by register 614-1 can correspond to, for example, the starting point (e.g., the starting LBA) of the security array (e.g., the starting point of the different parts of the security array), and the size of the security array defined by register 614-2 can correspond to, for example, the ending point (e.g., the ending LBA) of the security array (e.g., the ending point of the different parts of the security array).

[0095] For example, if Fig. 6A As shown, registers 614-1 and 614-2 may define N pairs of values, where each corresponding pair includes an address value (e.g., addr) defined by register 614-1 and a size value (e.g., size) defined by register 614-2. Fig. 6A In the example described in , Pair0 includes an address value addr0 and a size value size0 (eg, Pair0 = [addr0, size0]), Pair1 includes an address value addr1 and a size value size1 (eg, Pair1 = [addr1, size1]), and so on, where Pair N Including address value addr N and size value size N (For example, Pair N =[addr N ,size N]). The address value of a pair may correspond to the starting point of a portion of the security array (e.g., the starting LBA), and the sum of the address value and the size value of the pair may correspond to the ending point of the portion of the security array (e.g., the ending LBA). Thus, the entire security array (e.g., the portion that constitutes the entire security array) may be given by the following formula: [addr0, addr0+size0]∪[addr1, addr1+size1]∪…∪[addr N ,addr N +size N ].

[0096] The first pair of zeros defined by register 614-2 may stop the definition of the security array. Fig. 6A In the example illustrated in , if the size value of Pair2 is zero, then the secure array will be given by: [addr0, addr0+size0]∪[addr1, addr1+size1].

[0097] exist Figure 6B An example of a security array defined by registers 614-1 and 614-2 is illustrated in FIG. 6 (e.g., where all size values ​​are defined by register 614-2 as non-zero). Figure 6B As shown in FIG. 6 , the address (e.g., LBA) associated with sector 605-0 of memory array 601 is addr0, the address associated with sector 605-1 of memory array 601 is addr0+size0, the address associated with sector 605-2 of memory array 601 is addr1, the address associated with sector 605-3 of memory array 601 is addr1+size1, and the address associated with sector 605-4 of memory array 601 is addr0+size0. N , and the address associated with sector 605-5 of memory array 601 is addr N +size N Thus, the security array includes sectors (e.g., data stored in the sectors) 605-0 to 605-1, sectors 605-2 to 605-3, and 605-4 to 605-5. However, sectors in memory array 601 prior to sector 605-0 and sectors 605-1 to 605-2 of memory array 601 are not part of the security array (e.g., the security array includes a subset of array 601).

[0098] Figure 7 706 is a block diagram of an example system including a host 709 and a memory device 706 according to an embodiment of the present disclosure. For example, the host 709 and / or the memory device 706 may be a system previously described in conjunction with Figure 1The intermediate device 102 and / or network device 104 described herein. As used herein, the public key, public identification, and certificate generated at the intermediate device may be referred to as an intermediate public key, an intermediate public identification, and an intermediate certificate, respectively. Similarly, the public key, public identification, and certificate generated at the network device may be referred to as a network public key, a network public identification, and a network certificate, respectively.

[0099] A computing device can be booted in stages using layers, where each layer authenticates and loads subsequent layers and provides increasingly complex runtime services at each layer. One layer can be served by the previous layer and serve subsequent layers, thereby creating an interconnected network of layers that build on lower layers and serve higher layers. Figure 7 As illustrated in FIG. 1 , layer 0 (“L0”) 751 and layer 1 (“L1”) 753 are within the host. Layer 0 751 may provide a firmware derived secret (FDS) key 752 to layer 1 753. FDS key 752 may describe the identity of the code of layer 1 753 and other security-related data. In an example, a specific protocol (e.g., the Robust Internet of Things (RIOT) core protocol) may use FDS 752 to verify the code of layer 1 753 that it loads. In an example, the specific protocol may include a device identification combination engine (DICE) and / or the RIOT core protocol. As an example, the FDS may include the layer 1 firmware image itself, a list that cryptographically identifies authorized layer 1 firmware, a firmware version number of the firmware signed in the context of a secure boot implementation, and / or security-critical configuration settings of the device. Device secrets 758 may be used to create FDS 752 and stored in a memory of the host 709.

[0100] As illustrated by arrow 754, the host may transmit data to the memory device 706. The transmitted data may include a public identification, a credential, and / or a public key. A layer 2 ("L2") 755 of the memory device 706 may receive the transmitted data and execute the data in operation of an operating system ("OS") 757 and on a first application 759-1 and a second application 759-2.

[0101] In an example operation, the host 709 may read the device secret 758, hash the identity of layer 1 753, and perform calculations including:

[0102] K L1 =KDF[Fs(s),Hash("unchanged information")]

[0103] Where K L1is the public key, KDF (e.g., the KDF defined in National Institute of Standards and Technology (NIST) Specific Publication 800-108) is a key derivation function (e.g., HMAC-SHA256), and Fs(s) is the device secret 758. FDS 752 may be determined by performing the following calculation:

[0104] FDS = HMAC-SHA256[Fs(s), SHA256("unchanged information")]

[0105] Likewise, memory device 706 may transmit data to host 709 as illustrated by arrow 756 .

[0106] The embodiments are not limited to Figure 7 As an example, Figure 7 Host 709 and memory device 706 are illustrated as communicating entities (eg, transmitting 754 and receiving 756). However, such communications may also be performed between other entities, such as between two memory devices (eg, nodes 420 of network 410).

[0107] Figure 8 is a block diagram of an example process for determining several parameters according to an embodiment of the present disclosure. Figure 8 is an example of determining parameters including a public identification, a credential, and a public key, which are then sent to a memory device (e.g., Figure 7 706 in ) (e.g., layer 2 755). Figure 8 Layer 0 ("L0") 851 in corresponds to Figure 7 751 in FIG. 8 , similarly, FDS 852 corresponds to FDS 752 , layer 1 853 corresponds to layer 1 753 , and arrows 854 and 856 correspond to arrows 754 and 756 , respectively.

[0108] The FDS 852 from layer 0 851 is sent to layer 1 853 and is used by asymmetric ID generator 861 to generate a public identifier (“ID lk public ”) 865 and private identifier 867. In the abbreviation “ID lk public ”, “lk” indicates layer k (layer 1 in this example), and “public” indicates that the identifier is publicly shared. The public identifier 865 is illustrated as being shared by an arrow extending to the right and beyond layer 1 853 of the host. The generated private identifier 867 is used as a key input into the encryptor 873. The encryptor 873 can be any processor, computing device, etc. used to encrypt data.

[0109] Layer 1 853 of the host may include an asymmetric key generator 863. In at least one example, a random number generator (RND) 836 may optionally input a random number into the asymmetric key generator 863. The asymmetric key generator 863 may generate a random number such as Figure 7 The host-associated public key (“K Lk public ”)869 and the private key (“K LK private ”) 871. Public key 869 may be input as input (as “data”) to encryptor 873. Encryptor 873 may use the input of private identity 867 and public key 869 to produce a result K′875. Private key 871 and result K′875 may be input to additional encryptor 877, thereby producing output K″879. Output K″879 is transmitted to layer 2 ( Figure 7 755) credentials ("ID L1 The credential 881 may provide the ability to verify and / or authenticate the source of data sent from the device. As an example, by verifying the credential, data sent from the host may be associated with the host's identity, such as by combining Figure 8 Further description. In addition, the public key (“K L1 public key ”) 883 may be transmitted to layer 2. Thus, the host's public identification 865, credential 881, and public key 883 may be transmitted to layer 2 of the memory device.

[0110] Fig. 9 is a block diagram of an example process for determining several parameters according to an embodiment of the present disclosure. Fig. 9 Description Generate an ID (“ID L2 public") 966, device credentials ("ID L2 Certificate”)982 and the public key (“K L2 public key ”) 984 memory device (e.g., Figure 7 Layer 2 955 of the memory device 706 in.

[0111] As described in FIG. 6 , the public key (“K L1 public key ”) 983 is used by the asymmetric ID generator 962 of the memory device to generate a public identifier (“ID lk public ”) 966 and private identifier 968. In the abbreviation “ID lk public ”, “lk” indicates layer k (layer 2 in this example), and “public” indicates that the identifier is publicly shared. The public identifier 966 is illustrated as being shared by an arrow extending to the right and beyond layer 2 955. The generated private identifier 968 is used as a key input into the encryptor 974.

[0112] Layer 2 955 of the memory device may include an asymmetric key generator 964. In at least one example, a random number generator (RND) 938 may optionally input a random number into the asymmetric key generator 964. The asymmetric key generator 964 may generate a random number associated with the memory device (e.g., Figure 7 The public key (“K Lk public ”)970 (called the public key) and the private key (“K LK private ”) 972 (referred to as the private key). The public key 970 may be input as an input (as “data”) into an encryptor 974. The encryptor 974 may use the input of the private identity 968 and the public key 970 to produce a result K′ 976. The private key 972 and the result K′ 976 may be input into an additional encryptor 978, thereby producing an output K″ 980. The output K″ 980 is transmitted back to layer 1 ( Figure 7 753) of the device credentials ("ID L2 Device credentials 982 may provide the ability to verify and / or authenticate the source of data sent from the device. As an example, by verifying the credentials, data sent from the memory device may be associated with the identity of the memory device, such as by combining Fig.10 Further description. In addition, the public key (“K L2 public key ”) 984 can be transmitted to Layer 1. Therefore, the public identification 966, certificate 982 and public key 984 of the memory device can be transmitted to Layer 1 of the host.

[0113] In an example, in response to the host receiving a public key from the memory device, the host can encrypt data (e.g., an identifier) ​​to be sent to the memory device using the public key. Conversely, the memory device can encrypt data (e.g., information) to be sent to the host using the public key. In response to the memory device receiving data encrypted using the public key, the memory device can decrypt the data (e.g., the identifier) ​​using its own private key. Similarly, in response to the host receiving data encrypted using the public key, the host can decrypt the data (e.g., information) using its own private key. Because the private key is not shared with another device external to the memory device, and the private key is not shared with another device external to the host, the data sent to the memory device and the host remains secure.

[0114] In an embodiment, the first entity that initially requests a handshake with the second entity may generate a first public key, a first public identifier, and a first credential based on its own device secret. On the other hand, the second entity that receives the handshake request may generate a second public key, a second public identifier, and a second credential based on the first public key provided by the first entity. For example, Figure 7 , 8The embodiments described in 9 illustrate the host (e.g., host 709) as an entity that requests a handshake with the memory device (e.g., memory device 706) at the beginning. In this embodiment, the host 709 generates a public key (e.g., public key 883), a public identification (e.g., public identification 865), and a certificate (e.g., certificate 881) based on a device secret stored in itself, and the memory device generates those public keys, public identifications, and certificates based on the public key provided from the host. However, the embodiments are not so limited. For example, the memory device may initially request a handshake with the memory device so that the memory device generates a public key, a public identification, and a certificate using its own device secret, while the host generates those public keys, public identifications, and certificates based on the public key provided from the memory device.

[0115] Fig.10 is a block diagram of an example process for verifying credentials according to an embodiment of the present disclosure. Figure 8 In the illustrated example, from a host (e.g., from Figure 7 Layer 1 753 of the host 709 in ) provides a public key 1083, a credential 1081, and a public identification 1067. The data of the credential 1081 and the public key 1083 can be used as input to enter the decryptor 1085. The decryptor 1085 can be any processor, computing device, etc. for decrypting data. The decryption result of the credential 1081 and the public key 1083 can be used as input to the secondary decryptor 1087 together with the public identification, thereby generating an output. As illustrated at 1089, the public key 1083 and the output from the decryptor 1087 can indicate whether the credential is verified, thereby generating a yes or no 1091 as an output. In response to the credential being verified, the data received from the verified device can be accepted, decrypted and / or processed. In response to the credential not being verified, the data received from the device being verified can be discarded, removed and / or ignored. In this way, illegal devices that send illegal data can be detected and avoided. As an example, a hacker who sends data to be processed can be identified and the hacker data is not processed.

[0116] Fig.11 is a block diagram of an example process for verifying a signature according to an embodiment of the present disclosure. In the case where a device is sending data that can be verified to avoid subsequent repudiation, a signature can be generated and sent with the data. For example, a first device can make a request to a second device, and once the second device performs the request, the first device can indicate that the first device never made such a request. Anti-repudiation methods such as using signatures can avoid repudiations by the first device and ensure that the second device can perform the requested task without subsequent difficulties.

[0117] Memory device 1106 (eg, Figure 3The memory device 306 in the embodiment may send data 1190 to the host / memory device 1109, which may be Figure 1 The host 102 and / or comprising Figure 1 1106 may generate a signature 1196 using the device private key 1172 at 1194. The signature 1196 may be transmitted to the host / memory device 1109. The host / memory device 1109 may verify the signature using the previously received data 1192 and the public key 1184 at 1198. In this way, the signature is generated using the private key and verified using the public key. In this way, the unique signature for each device may remain private to the device that sent the signature while allowing the receiving device to be able to decrypt the signature for verification. This is in contrast to the encryption / decryption of data, which is encrypted by the sending device using the public key of the receiving device and decrypted by the receiving device using the private key of the receiver. In at least one example, the device may verify the digital signature by using an internal cryptographic process, such as an elliptic curve digital signature (ECDSA) or similar process.

[0118] Fig.12 1 is a block diagram of an example memory device 1299 according to an embodiment of the present disclosure. For example, the memory device 1299 may be a memory device 1299 previously described in conjunction with Figure 1 Intermediary device 102 and / or network device 104 are described.

[0119] like Fig.12 As shown in FIG. 1 , the memory device 1299 may include a plurality of memory arrays 1201-1 to 1201-7. The memory arrays 1201-1 to 1201-7 may be similar to those previously described in conjunction with Figure 2 The memory array 121 described above. Fig.12 In the example illustrated in FIG. 1 , memory array 1201-3 is a security array, subset 1211 of memory array 1201-6 includes a security array, and subsets 1249 and 1250 of memory array 1201-7 include security arrays. Subsets 1211, 1249, and 1250 may each contain, for example, 4 kilobytes of data. However, embodiments of the present disclosure are not limited to a particular number or arrangement of memory arrays or security arrays.

[0120] like Fig.12 As shown in FIG. 1 , the memory device 1299 may include a repair (e.g., recovery) block 1260. The repair block 1260 may be used as a source of data in the event that an error (e.g., a mismatch) may occur during operation of the memory device 1299. The repair block 1260 may be outside of an area of ​​the memory device 1299 that is addressable by a host.

[0121] like Fig.12As shown in , the memory device 1299 may include a serial peripheral interface (SPI) 1233 and a controller 1208. The memory device 1299 may use the SPI 1233 and the controller 1208 to communicate with the host and the memory arrays 1201-1 to 1201-7, as previously described herein (e.g., in conjunction with Figure 3 ) described.

[0122] like Fig.12 As shown in , the memory device 1299 may include a security register 1286 for managing the security of the memory device 1299. For example, the security register 1286 may configure the application controller and be communicated to the application controller externally. In addition, the security register 1286 may be modified by an authentication command.

[0123] like Fig.12 As shown, memory device 1299 may include key 1288. For example, memory device 1299 may include eight different slots to store keys, such as root keys, DICE-RIOT keys, and / or other external session keys.

[0124] like Fig.12 As shown in , memory device 1299 may include an electronically erasable programmable read-only memory (EEPROM) 1293. EEPROM 1293 may provide a secure non-volatile area available to the host in which individual bytes of data may be erased and programmed.

[0125] like Fig.12 As shown in , the memory device 1299 may include a counter (e.g., a monotonic counter) 1295. The counter 1295 may be used as an anti-replay mechanism (e.g., a freshness generator) for commands received from and / or sent to the host (e.g., to sign a set or sequence of commands). For example, the memory device 1299 may include six different monotonic counters, two of which may be used by the memory device 1299 for authenticated commands and four of which may be used by the host.

[0126] like Fig.12 , the memory device 1299 may include a SHA-256 cryptographic hash function 1297, and / or an HMAC-SHA256 cryptographic hash function 1229. The SHA-256 and / or HMAC-SHA256 cryptographic hash functions 1297 and 1229 may be used by the memory device 1299 to generate cryptographic hashes, such as the cryptographic hash of block 220 previously described herein, and / or golden hashes to verify data stored in the memory arrays 1201-1 to 1201-7. In addition, the memory device 1299 may support L0 and L1 of the DICE-RIOT 1231.

[0127] Although specific embodiments have been shown and described herein, it will be appreciated by those skilled in the art that arrangements calculated to achieve the same results may replace the specific embodiments shown. The present disclosure is intended to cover adaptations or variations of several embodiments of the present disclosure. It should be understood that the above description is provided in an illustrative and not restrictive manner. Upon reviewing the above description, the combination of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art. The scope of several embodiments of the present disclosure includes other applications in which the above structures and methods are used. Therefore, the scope of several embodiments of the present disclosure should be determined with reference to the attached claims and the full scope of equivalents to which such claims are assigned.

[0128] In the foregoing Detailed Description, some features are grouped together in a single embodiment for the purpose of simplifying the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the disclosed embodiments of the disclosure must use more features than are expressly recited in each claim. In fact, as reflected in the appended claims, the subject matter of the present invention lies in less than all of the features of a single disclosed embodiment. Therefore, the appended claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

1. A device comprising: Memory; and A circuit system configured to: In response to receiving a request for information corresponding to one or more categories from another device, determining one or more identifiers for identifying the one or more categories to which the requested information stored in the network device belongs, wherein one of the one or more identifiers is used to access information associated with another of the one or more identifiers, and wherein the determination is based on a database comprising a plurality of tables that each correspond to a respective category of the one or more categories; encrypting the determined identifier using a network public key generated at the network device; and The determined and encrypted identifiers are provided to the network device along with the signature to retrieve the requested information from a network in which the network device is configured as a node in response to the signature being verified and the one or more identifiers being decrypted at the network device.

2. The apparatus of claim 1 , wherein the circuit system is configured to: Generate a private key; and The signature is generated using the private key.

3. The apparatus of claim 2, wherein the apparatus comprises an asymmetric key generator, and the circuit system is configured to control the asymmetric key generator to generate the private key based on a password input into the asymmetric key generator.

4. A method comprising: In response to receiving a request for information corresponding to a plurality of categories from another device, determining, based on a database maintained by the intermediary device, respective identifiers for identifying the plurality of categories to which the requested information belongs, wherein one of the respective identifiers is used to access information associated with another of the respective identifiers, wherein the database includes a plurality of tables each corresponding to a respective category of the plurality of categories; encrypting the determined identifier using a network public key generated at the network device; and The determined and encrypted identifier is provided along with the intermediate signature to the network device to retrieve the information corresponding to the plurality of categories and identifiable based on the identifier decrypted at the network device from a network, wherein the network device is configured as a respective node of the network.

5. The method of claim 4, wherein the method further comprises, in response to receiving information that has not been previously added to the network, performing the following operations: determining an identifier associated with a particular category to which the received information corresponds; and A data packet is generated including the received information and the determined identifier such that the received information is identifiable based on the determined identifier.

6. The method according to any one of claims 4 to 5, wherein the method further comprises maintaining the database by: A corresponding table of the plurality of tables is updated in response to an occurrence of an event to be recorded as specific information to the database.

7. The method of any one of claims 4-5, wherein the method further comprises updating the database in response to the intermediate device being powered on.

8. The method according to any one of claims 4 to 5, wherein: The plurality of tables include a first table and a second table having an access key associated with the first table; and The method additionally includes accessing data stored in the second table from the first table using the access key stored in the first table.

9. A system comprising: Network devices; An intermediate device configured to: In response to receiving a request for information corresponding to a plurality of categories from another device, determining respective identifiers associated with the plurality of categories to which the requested information belongs, wherein one of the respective identifiers is used to access information associated with another of the respective identifiers, and wherein the determining is based on a database comprising a plurality of tables that each corresponds to a respective category of the plurality of categories; encrypting the determined identifier using a network public key generated at said network device; and providing the determined encrypted identifier to the network device along with at least one of an intermediate credential or an intermediate signature generated at the intermediate device; The network device is configured to: decrypting the received identifier using a network private key generated together with the network public key; In response to verifying the identity of the intermediate device based on the at least one of the intermediate credential or the intermediate signature, identifying the information corresponding to the plurality of categories based on the received identifier; and The data corresponding to the identified information is provided to the intermediary device along with at least one of a network credential or a network signature.

10. The system of claim 9, wherein the intermediate device is configured to: generating an intermediate public key and an intermediate private key, wherein the intermediate signature is generated based on the intermediate private key; and The intermediate public key generated together with the intermediate private key is provided to the network device so that the intermediate signature is verified by the network device using the intermediate public key.

11. The system of claim 9, wherein: The intermediate device is configured to provide a request to add data to the network device; The network device is configured to, in response to receiving the request, add the data upon verifying the identity of the intermediary device; The network device is one of a plurality of network devices configured as a corresponding node; and The network device is configured to, in response to receiving the request and the data to be modified from the intermediate device, perform the following operations: broadcasting the added data received from the intermediate device to other nodes of the network; and The data is added to the network device in response to obtaining corresponding approvals from greater than a threshold number of nodes.

12. The system of claim 11, wherein each node that receives the request broadcast by the network device is configured to: Execute the Merkle tree verification algorithm; and Approval is provided back to the network device in response to verifying that the data to be modified is authentic.

13. The system of claim 9, wherein: The intermediate device is configured to provide an intermediate public key and an intermediate public identification generated at the intermediate device together with the intermediate credential to the network device; and The network device is configured to verify the identity of the intermediate device based on a comparison among the intermediate credential, the intermediate public key, and the intermediate public identification.

14. The system of claim 13, wherein the network device comprises a first decryptor and a second decryptor, and wherein the network device is configured to: inputting the intermediate public key and the intermediate credential into the first decryptor; inputting the intermediate public identification and the output of the first decryptor into the second decryptor; and The output of the second decryptor is compared to the intermediate public key, wherein the identity of the intermediate device is verified when the output of the second decryptor is equal to the intermediate public key.

15. The system of claim 13, wherein the network device is configured to discard an identifier received from the intermediary device in response to not verifying the identity of the intermediary device.

16. The system of any one of claims 9 to 15, wherein: The network device is one of a plurality of network devices being configured as a respective node of a network, and The intermediate device is configured to: generating and maintaining a database including a plurality of tables each corresponding to a respective one of the plurality of categories, wherein each table is associated with a respective one of the plurality of identifiers; and In response to receiving specific information that has not been previously added to the network, the database is updated based on identifiers corresponding to respective categories associated with the specific information.

17. The system of claim 16, wherein the database is distributed among the respective nodes of the network such that the network device includes at least a portion of the database.