Encryption device, system on chip including the encryption device, and electronic device
By introducing counters, encryption/decryption units and timers into the SoC, data and timestamps are encrypted, and the timestamps are verified by checking the logical device to verify the timestamp of the decrypted data, the data security problem when the SoC communicates with external storage devices is solved, and the data security problem is realized. Resistance to various attacks.
Patent Information
- Application Number
- CN201811403347.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-11-23
- Filing Date
- 2018-11-22
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2038-11-22
AI Technical Summary
When existing SoCs communicate with external storage devices, there is a risk that data is detected and accumulated by attackers, and it is difficult to resist various types of attacks.
An encryption device is designed, including a counter, encryption/decryption unit and a timer, for encrypting data and timestamps, and verifying the timestamp of the decrypted data by checking the logical device to ensure the security of the data.
It effectively resists the replay attacks and other types of attacks carried out by attackers, ensures the security of data in storage devices, and further enhances security by periodically updating timestamps.
Smart Images

Figure CN109829316B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the priority of Korean Patent Application No. 10-2017-0157210 filed on November 23, 2017, in the Korean Intellectual Property Office, the entire contents of which are incorporated herein by reference. Technical Field
[0003] Embodiments of the present disclosure relate to an encryption device, a system on chip (SoC) including the encryption device, and an electronic device. More specifically, embodiments of the present disclosure relate to an encryption device for encrypting data and a timestamp, a SoC including the encryption device, and an electronic device. Background Art
[0004] The application processor (AP) may be implemented as a SoC. The SoC may be a chip that integrates various (multiple different) systems, for example, on a single integrated substrate. Since various systems are integrated into the SoC, the capacity of the internal memory (e.g., static random access memory (SRAM)) of the SoC may be limited. Since the capacity of the internal memory is limited, the SoC may communicate with an external storage device.
[0005] When the SoC and the external storage device communicate with each other through physical lines and pins exposed to the outside, there is a risk that an attacker may detect the data transmitted between the SoC and the external storage device. To address this risk, the SoC may send data in an encrypted form to the storage device. The encrypted data may be stored in the storage device. Nevertheless, the attacker may observe and accumulate the encrypted data and may attack the storage device and the SoC. Therefore, security technology that can resist various types of attacks is required. Summary of the invention
[0006] Embodiments of the present disclosure provide an encryption device for encrypting data and a timestamp, a SoC including the encryption device, and an electronic device.
[0007] According to one aspect of the present disclosure, an encryption device may include a counter, an encryption / decryption unit, and a timer. The counter is configured to generate a first timestamp for a first time. The encryption / decryption unit is configured to cascade security data and the first timestamp, encrypt the cascaded data into encrypted data, send the encrypted data to a storage device, and decrypt the read data sent from the storage device into decrypted data. The timer is configured to notify the counter and the encryption / decryption unit that time has passed from the first time to the second time, so that the counter generates a second timestamp for the second time, and the encryption / decryption unit decrypts the read data into decrypted data. The check logic device implemented by the encryption device is configured to check whether the decryption timestamp of the decrypted data is the same as the first timestamp.
[0008] According to another aspect of the present disclosure, a system on chip (SoC) may include a processor, a counter, a timer, and an encryption / decryption unit. The processor is configured to generate security data. The counter is configured to generate a timestamp to be concatenated with the security data. The timer is configured to periodically request an update of the timestamp. The encryption / decryption unit is configured to concatenate the security data and the timestamp; encrypt the concatenated data into encrypted data; and send the encrypted data to a storage device in response to a write command of the processor so that the security data is stored in the storage device; and in response to a request of the timer or a request of the processor, decrypt the read data sent from the storage device into decrypted data. The check logic device implemented by the SoC is configured to check whether the decryption timestamp of the decrypted data is valid.
[0009] According to another aspect of the present disclosure, an electronic device may include a storage device and a system on chip (SoC). The storage device is configured to store first encrypted data, wherein the first encrypted data is encrypted by first security data and a first timestamp. The system on chip (SoC) is configured to decrypt the first encrypted data stored in the storage device, check whether the first timestamp is valid, and based on the check result, store second encrypted data instead of the first encrypted data in the storage device, wherein the second encrypted data is encrypted by first security data and a second timestamp different from the first timestamp. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The above and other objects and features will become apparent from the following description with reference to the following drawings, wherein like reference numerals refer to like parts throughout the various drawings unless otherwise specified, and in the drawings:
[0011] Figure 1 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure;
[0012] Figure 2 It shows Figure 1 A block diagram of the detailed configuration of the encryptor;
[0013] Figure 3 It is shown by Figure 1 A block diagram of the timestamp update performed by the encryptor;
[0014] Figure 4 It shows that Figure 1 A map of encrypted data stored in an encrypted data area;
[0015] Figure 5 FIG. 1 is a diagram showing another embodiment of the present disclosure. Figure 1 A block diagram of a timestamp update performed by an encryptor;
[0016] Figure 6 It is shown by Figure 5 The encryptor is Figure 1 A map of encrypted data stored in an encrypted data area;
[0017] Figure 7 It shows Figure 5 A block diagram of the detailed configuration of the check logic device;
[0018] Figure 8 It shows Figure 1 The processor requests a diagram of an example of data stored in the encrypted data area;
[0019] Fig. 9 is a block diagram showing the operation of an encryptor, wherein the encryptor processes as shown in reference Figure 8 a read command of the processor;
[0020] Fig.10 It shows Figure 1 The processor requests a diagram of an example of data stored in the encrypted data area;
[0021] Fig.11 is a block diagram showing the operation of an encryptor, wherein the encryptor processes as shown in reference Fig.10 a read command of the processor;
[0022] Fig.12 It is shown by Figure 1 A graph of operations of an encryptor updating a timestamp stored in a storage device;
[0023] Fig.13 It shows Figure 1 A signal sequence diagram of operations between a processor, an encryptor, and a storage device;
[0024] Fig.14 It shows Figure 1 A signal sequence diagram of operations between a processor, an encryptor, and a storage device;
[0025] Fig.15 is a flow chart showing the operation of an encryptor according to an embodiment of the present disclosure;
[0026] Fig.16 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure;
[0027] Fig.17 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure;
[0028] Fig.18 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure;
[0029] Fig.19 It shows Fig.18 A diagram of the processor's address space;
[0030] Fig. 20 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure; and
[0031] Fig.21 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. DETAILED DESCRIPTION
[0032] Hereinafter, embodiments of the present disclosure are described clearly in detail so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art.
[0033] Figure 1 1 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure. The electronic device 100 may include a system on chip (SoC) 110 and a storage device 160.
[0034] The SoC 110 may be configured to drive an operating system (OS) and control the overall operation of the electronic device 100. The SoC 110, as an application processor (AP), may execute various applications supported by the electronic device 100. To this end, the SoC 110 may include a processor 120 that performs various operations. For example, the processor 120 may be one of a central processing unit (CPU), an image signal processing unit (ISP), a digital signal processing unit (DSP), a graphics processing unit (GPU), a visual processing unit (VPU), and a neural processing unit (NPU). Figure 1 In the embodiment, the embodiment is illustrated as only one processor 120. However, the embodiment is not limited thereto. For example, the SoC 110 may include one or more processors.
[0035] SoC 110 may include an encryptor 130 for encrypting data stored in storage device 160. Encryptor 130 may be referred to as an encryption device or an encryption circuit. That is, encryptor 130 and any other elements of SoC 110 described herein should be considered to include elements of devices (such as processors and memories), and / or elements of circuits (such as electronic circuits). Encryptor 130 may be configured to perform encryption operations on security data sent from processor 120 according to an encryption algorithm. Encryptor 130 may be configured to perform decryption operations on encrypted data sent from storage device 160.
[0036] The storage device 160 may store data or may send stored data to the SoC 110 in response to a request of the SoC 110. For example, the storage device 160 may operate as a main memory that the SoC 110 can quickly access. The storage device 160 may be a dynamic random access memory (DRAM) device. Due to storage capacity, limited size of the SoC 110, etc., the storage device 160 may be located outside the SoC 110. Figure 1 , an attacker can detect or observe the data between SoC 110 and storage device 160.
[0037] In one embodiment, in order to resist attacks by attackers, SoC 110 may send encrypted data to storage device 160, and storage device 160 may include an encrypted data area 161 for storing encrypted data. Storage device 160 may send the encrypted data stored in encrypted data area 161 to SoC 110. Therefore, the attacker may only obtain the encrypted data and may not know the data before encryption.
[0038] An attacker can observe and accumulate encrypted data sent and received between the SoC 110 and the storage device 160 for a long time. When any encrypted data is stored in the storage device 160, the attacker can observe operations performed by the SoC 110, applications executed by the SoC 110, etc. Although the SoC 110 and the storage device 160 send and receive encrypted data to each other, the attacker can use the encrypted data obtained by observation to attack. Such an attack by the attacker may be called a replay attack.
[0039] The SoC 110 will be described in detail to resist the replay attack of the attacker. The processor 120 can send the security data to the encryptor 130. In this article, it should be possible to protect the security data from various attacks by the attacker. Since the processor 120 and the encryptor 130 are both implemented in the SoC 110, the security data sent from the processor 120 to the encryptor 130 can have an unencrypted form. Similarly, the security data sent from the encryptor 130 to the processor 120 can have an unencrypted form.
[0040] The encryptor 130 may concatenate the security data and the timestamp, and may encrypt the concatenated data into the encrypted data. The timestamp may include a value associated with a year, month, day, hour, minute, or second, or a value associated with an operation time. The operation time may include, for example, the time when the processor 120 issues a command for writing the security data to the storage device 160, the time when the encryptor 130 receives the security data, the time when the encryption operation is performed, the time previously determined in the encryptor 130, etc.
[0041] exist Figure 1In the embodiment, the embodiment is illustrated as only concatenating the security data and the timestamp in the encrypted data. However, the embodiment is not limited to this. For example, the encrypted data and the timestamp can be mixed with each other through an encryption operation, and the encrypted data can have an encrypted form. An attacker may not be able to verify whether any part of the encrypted data corresponds to the timestamp. Hereinafter, the encryptor 130 will be described in detail.
[0042] Figure 2 It shows Figure 1 The detailed configuration of the encryptor is shown in the block diagram. Figure 1 To describe Figure 2 In order to resist the replay attack by the attacker, the encryptor 130 can periodically update Figure 1 The timestamp stored in the storage device 160 of the encryptor 130 is used. To this end, the encryptor 130 may include a timer 131 and a counter 132. The encryptor 130 may also include an encryption / decryption unit 133. The encryption / decryption unit 133 may be implemented as a circuit, or as a combination of a processor and software executed by the processor, and may also be implemented by a combination of a circuit and a processor that executes software and software executed by the processor.
[0043] The timer 131 can calculate the update cycle of the timestamp. The timestamp can be concatenated with the security data and can be encrypted. When the time elapses the update cycle, the timer 131 is configured to request the counter 132 and the encryption / decryption unit 133 to update the timestamp. Specifically, the timer 131 can generate an update signal for updating the timestamp.
[0044] In one embodiment, the update cycle may be a predetermined value. As the update cycle is shorter, security may be more enhanced, but the time period for accessing the storage device 160 may be shorter. The update cycle may be determined in consideration of both security and access to the storage device 160.
[0045] In another embodiment, the update period may be based on Figure 1 The value may be changed at the request of the processor 120 or the user. The processor 120 or the user may request the encryptor 130 to change the update cycle according to the security data. When specific security data is stored in the storage device 160, the processor 120 or the user may immediately request the encryptor 130 to update the timestamp regardless of the update cycle.
[0046] The counter 132 may generate a timestamp in response to a request from the timer 131, and may send the generated timestamp to the encryption / decryption unit 133. The counter 132 may include a plurality of triggers. The output of the counter 132 may be used as a timestamp. The output of the counter 132 may be used in conjunction with the Figure 1The output of the counter 132 may be increased, decreased, or randomly changed. For example, the output of the counter 132 may be determined as a timestamp when the request of the timer 131 occurs.
[0047] The encryption / decryption unit 133 can be Figure 1 The processor 120 may receive the security data and may receive the time stamp from the counter 132. The encryption / decryption unit 133 may concatenate the security data and the time stamp, may encrypt the concatenated data into encrypted data, and may transmit the encrypted data to the storage device 160.
[0048] In one embodiment, the encryption / decryption unit 133 may perform encryption operations on the concatenated data according to an encryption algorithm. For example, the encryption algorithm may be an Advanced Encryption Standard (AES), a Data Encryption Standard (DES), a Triple DES, a SEED, a High Security and Lightweight (HIGHT), an Association Research Institute Agency (ARIA), a Lightweight Encryption Algorithm (LEA), etc. In one embodiment, the encryption algorithm may perform encryption operations in a block encryption mode. The block encryption mode may be an Electronic Code Book (ECB) mode, a Cipher Block Chaining (CBC) mode, a Counter (CTR) mode, a Propagation Cipher Block Chaining (PCBC) mode, a Cipher Feedback (CFB) mode, etc.
[0049] In one embodiment, the size of the security data may be the same as the unit of the encryption operation of the encryption / decryption unit 133. For example, the unit of the encryption operation may be 128 bits. The size of the timestamp may be the same as the unit of the encryption operation. Figure 2 In contrast to what is shown in , the concatenation size of the security data and timestamp can be the same as the unit of the cryptographic operation.
[0050] refer to Figure 2 , the embodiment is exemplified as the timestamp of the encrypted data is the first timestamp. Figure 3 The operation of the encryptor 130 to update the time stamp according to the request of the timer 131 is described.
[0051] Figure 3 It is shown by Figure 1 A block diagram of the timestamp update performed by the cipher in . Figure 1 and Figure 2 To describe Figure 3 The encryptor 130 may also include a check logic device 134. The check logic device may be implemented as a circuit, for example, using a memory element, a comparator, and other forms of circuit elements. The check logic device may also be implemented as a combination of a processor and software executed by the processor, or as a combination of a circuit and a processor that executes the software and software executed by the processor.
[0052] exist Figure 3 In FIG. 1 , it is assumed that after the encrypted data including the first timestamp is stored in the storage device 160 , the timer 131 requests to update the first timestamp. Figure 1 There is no attack on the storage device 160.
[0053] The counter 132 may update the first timestamp to a second timestamp in response to a request of the timer 131. The second timestamp and the first timestamp may be different from each other. The counter 132 may send the second timestamp to the encryption / decryption unit 133.
[0054] The encryption / decryption unit 133 may send a read command to the storage device 160 in response to the request of the timer 131. The encryption / decryption unit 133 may receive the encrypted data (or read data) including the first timestamp using the read command. The encryption / decryption unit 133 may decrypt the encrypted data into decrypted data. The encryption / decryption unit 133 may send the decrypted timestamp to the inspection logic device 134. Since there is no attack, the decrypted timestamp may be the first timestamp.
[0055] The check logic device 134 can determine or check whether the first timestamp is valid. When the first timestamp is invalid, the check logic device 134 is configured to Figure 1 The components in the SoC 110 (e.g., Figure 1 The processor 120) outputs an error indicating that the storage device 160 has been attacked.
[0056] In one embodiment, before the request of the timer 131 occurs, the check logic device 134 may store the first timestamp in advance. In another embodiment, when the request of the timer 131 occurs, the check logic device 134 may receive the first timestamp from the counter 132 and may store the first timestamp. The check logic device 134 may include a register for storing the first timestamp. Since the first timestamp sent from the counter 132 and stored in the check logic device 134 exists in the SoC 110, it may be valid. The check logic device 134 may compare the first timestamp stored in the check logic device 134 with the decryption timestamp sent from the encryption / decryption unit 133, and may determine or check whether the decryption timestamp is valid based on the comparison result.
[0057] exist Figure 3 In the example, since there is no assumption of an attack, the check logic 134 may determine or check that the decrypted timestamp is valid and does not output an error.
[0058] The encryption / decryption unit 133 may perform an update (or re-encryption) of the timestamp based on the determination result or the inspection result so as to change the first timestamp to the second timestamp. Figure 2 The operation of the encryption / decryption unit 133 described above is to update the timestamp. In this article, the timestamp sent from the counter 132 is not the first timestamp but the second timestamp. Specifically, when the decrypted timestamp is the same as the first timestamp stored in the check logic device 134, the encryption / decryption unit 133 can cascade the security data of the decrypted data and the second timestamp, can encrypt the cascaded data into new encrypted data, and can send the new encrypted data to the storage device 160.
[0059] Figure 4 It shows that Figure 1 A diagram of the encrypted data stored in the encrypted data area of . Figure 1 and Figure 3 To describe Figure 4 .exist Figure 4 In the example, it is assumed that according to the update of the timestamp, the timestamp of the encrypted data is updated from the first timestamp to the second timestamp.
[0060] The first security data Security Data1 and the second timestamp Timestamp2 can be stored as the first encrypted data in Figure 1 The second security data Security Data2 to the ninth security data Security Data9 may be stored in the encrypted data area 161 as the second to ninth encrypted data, respectively, in a manner similar to the first security data Security Data1. Figure 4 In , one row may indicate encrypted data, and first to ninth encrypted data may be stored in data areas corresponding to first to ninth addresses Address1 to Address9, respectively. Figure 4 In the embodiment, the security data and the timestamp are separated. However, the embodiment is not limited to this. For example, the security data and the timestamp can be stored in the encrypted data area 161 in an encrypted form. The number of addresses and the number of encrypted data are not limited to the numbers shown.
[0061] The attacker may observe the fourth encrypted data stored in the area corresponding to the fourth address Address4. The attacker's observation may be performed before the second timestamp Timestamp2 is updated. After the second timestamp Timestamp2 is updated, the attacker may write the previously observed fourth encrypted data (i.e., the first attack Attack1) in the encrypted data area 161. In this case, the timestamp of the fourth encrypted data written by the attacker in the encrypted data area 161 may be earlier than the second timestamp Timestamp2.
[0062] Regarding the first attack Attack1, in response to Figure 3 The request of timer 131, Figure 3 The encryption / decryption unit 133 can decrypt the fourth encrypted data into decrypted data and Figure 3 The check logic device 134 can determine or check whether the decryption timestamp is valid. The decryption timestamp can be stored in the encrypted data area 161 by the first attack Attack1. Since the decryption timestamp is different from the second timestamp stored in the check logic device 134, the check logic device 134 can output an error indicating that the encrypted data area 161 has been attacked. In other words, Figure 1 The encryptor 130 can resist the first attack Attack1.
[0063] According to an embodiment of the present disclosure, the encryptor 130 may periodically update the timestamp stored in the encrypted data area 161. Therefore, the encryptor 130 may resist the first attack Attack1 using the previous timestamp.
[0064] The attacker may write or copy the eighth encrypted data stored in the data area corresponding to the eighth address Address8 to the data area corresponding to the sixth address Address6 (i.e., the second attack Attack2). In this article, the address accessed by the attacker may be only an example. The sixth security data Security Data6 of the sixth encrypted data may be changed to the eighth security data Security Data8 through the second attack Attack2. When the second attack Attack2 is performed within the update cycle of the timestamp of the encryptor 130, since the second timestamp Timestamp2 is not changed by the second attack Attack2, the encryptor 130 may not be able to resist the second attack Attack2. In order to resist the second attack Attack2, the encryptor 130 may also cascade the address and timestamp of the security data with the security data to generate encrypted data. In the following, reference will be made to Figure 5 An example of further concatenating the address with the security data is described.
[0065] Figure 5 FIG. 1 is a diagram showing another embodiment of the present disclosure. Figure 1 Block diagram of the timestamp update performed by the cipher of FIG. Figure 5 In the description Figure 5 The encryptor 130 and Figure 3 The difference between the encryptors 130.
[0066] The encryption / decryption unit 133 may also concatenate an address and a time stamp with the security data. Figure 1 The processor 120 may send Figure 1 The encryptor 130 sends the secure data stored in Figure 1 The address of the encrypted data area 161 indicates the location of the encrypted data area 161. The data concatenated with the security data can be called a "tag". Figure 2 and Figure 3 In , a label can consist of only a timestamp, but in Figure 5 In the example, the tag may further include an address. The encryption / decryption unit 133 may encrypt the cascade data. In other words, the encrypted data may further include an encrypted address. The encryption / decryption unit 133 may perform a decryption operation and may send a decryption address and a decryption timestamp of the decrypted data to the inspection logic device 134.
[0067] In one embodiment, the size of the security data may be the same as the unit of the encryption operation of the encryption / decryption unit 133. The concatenated size of the address and the timestamp may be smaller than the unit of the encryption operation of the encryption / decryption unit 133, but different from the unit of the encryption operation of the encryption / decryption unit 133. Alternatively, the concatenated size of the address and the timestamp may be the same as the unit of the encryption operation of the encryption / decryption unit 133. The size of the timestamp may be preset so that the concatenated size of the address and the timestamp is the same as the unit of the encryption operation.
[0068] In another embodiment, the concatenation size of the security data, address and timestamp may be the same as the unit of the encryption operation of the encryption / decryption unit 133. In this case, the size of the timestamp may be preset so that the concatenation size of the security data, address and timestamp is the same as the unit of the encryption operation.
[0069] The check logic device 134 can determine or check whether each of the decryption address and the decryption timestamp is valid. In this case, when the decryption address is invalid or when the decryption timestamp is invalid, the check logic device 134 can send a Figure 1 A component output in the SoC 110 is erroneous.
[0070] The check logic device 134 may store in advance Figure 1 The encryptor 130 may further include an address generator 139 that generates an address for accessing the encrypted data area 161 of the storage device 160. For example, the address generator 139 may be implemented using at least one counter.
[0071] The addresses generated by the address generator 139 may be sequentially increased or decreased, or may be randomly changed. In response to a request from the timer 131, the address generator 139 may generate an address for accessing all encrypted data areas 161. The encryption / decryption unit 133 may access all encrypted data areas 161 in response to a request from the timer 131 without a request from the processor 120. The address generator 139 may send an address to the encryption / decryption unit 133, and the encryption / decryption unit 133 may access the encrypted data area 161 using the address generated by the address generator 139. Of course, the address generator 139 may be used in Figure 3 In the encryptor 130.
[0072] The address generated by the address generator 139 may be used by the check logic device 134. Since the address generated by the address generator 139 exists in the SoC 110, the address may be valid and may be the same as the address sent by the processor 120. The check logic device 134 may compare the address of the address generator 139 (i.e., the address of the security data) with the decrypted address sent from the encryption / decryption unit 133, and may determine or check whether the decrypted address is valid based on the comparison result.
[0073] When the decryption address is the same as the address of the address generator 139 (i.e., the address of the security data) and when the decryption timestamp is the same as the first timestamp stored in the inspection logic device 134, the encryption / decryption unit 133 can cascade the security data, the decryption address and the second timestamp of the decrypted data, can encrypt the cascaded data into new encrypted data, and can send the new encrypted data to the storage device 160.
[0074] Figure 6 It is shown by Figure 5 The encryptor is Figure 1 A diagram of the encrypted data stored in the encrypted data area of . Figure 4 and Figure 5 To describe Figure 6 .exist Figure 4 In the encrypted data, the encrypted address is not included, but in Figure 6 In, the encrypted address can be included in the encrypted data. Figure 4 Shown by Figure 3 The encryptor 130 stores the encrypted data. Figure 6 Shown by Figure 5 The encryptor 130 stores the encrypted data.
[0075] Similar to reference Figure 4 As described, Figure 5 The encryptor 130 can resist the first attack Attack1 of the attacker. Figure 4Contrary to what is described, Figure 5 The encryptor 130 can also resist the attacker's second attack Attack2. The second attack Attack2 does not change the second timestamp Timestamp2 of the sixth encrypted data, but the second attack Attack2 can change the sixth address Address6 to the eighth address Address8. Regarding the second attack Attack2, Figure 5 The encryption / decryption unit 133 can decrypt the sixth encrypted data into decrypted data and Figure 5 The check logic device 134 can determine or check whether each of the decryption timestamp and the decryption address is valid. In this article, since the decryption address (ie, the eighth address Address8) is changed by the second attack Attack2, it may be different from Figure 1 The address of the address generator 139 in the SoC 110 is different. Therefore, the check logic device 134 can output an error, and the encryptor 130 can resist the second attack Attack2.
[0076] Figure 7 It shows Figure 5 The detailed configuration of the logic device is shown in the block diagram. Figure 1 and Figure 5 To describe Figure 7 . Figure 5 The check logic device 134 may include a timestamp comparator 136 , an address comparator 137 , and an error generator 138 .
[0077] The timestamp comparator 136 can be Figure 1 The storage device 160 sends and is sent by Figure 5 The timestamp decrypted by the encryption / decryption unit 133 is Figure 1 The timestamp comparator 136 may be compared with a timestamp in the SoC 110. The timestamp in the SoC 110 may be a timestamp generated by the counter 132 and not output to the outside of the SoC 110. The timestamp comparator 136 may send the comparison result to the error generator 138.
[0078] The address comparator 137 may compare the address sent from the storage device 160 and decrypted with the address in the SoC 110. The address in the SoC 110 may be a Figure 5 The address generator 139 generates an address which is not output to the outside of the SoC 110. The address comparator 137 may send a comparison result to the error generator 138.
[0079] Error generator 138 may output an error based on the comparison results of timestamp comparator 136 and address comparator 137. Error generator 138 may output an error when the comparison result of timestamp comparator 136 indicates that the decrypted timestamp is invalid or when the comparison result of address comparator 137 indicates that the decrypted address is invalid.
[0080] In an embodiment, an error may be sent to Figure 1 The processor 120 can be Figure 1 The error may be outputted via a dedicated pin assigned between the processor 120 and the encryptor 130. The error may be outputted via a bus (not shown) that operates according to an interface between the processor 120 and the encryptor 130. When the error is outputted via the bus, the form of the error outputted from the error generator 138 may be predefined according to a protocol between the processor 120 and the encryptor 130.
[0081] In another embodiment, the error may be sent to Figure 1 The error may be sent to another element (not shown) of the electronic device 100 of the embodiment of the present invention. For example, the error may be sent to a display serial interface (DSI) device (not shown) so that a user can check the error. The error may be output through a dedicated pin assigned between the SoC 110 and another element or through a bus operated according to an interface between the SoC 110 and another element.
[0082] Figure 8 It shows Figure 1 FIG. 10 is a diagram of an example of a processor requesting data stored in an encrypted data area. Figure 1 and Figure 6 To describe Figure 8 .exist Figure 8 In, similar to Figure 6 , the first to ninth encrypted data may be stored in the encrypted data area 161. The number of encrypted data is not limited to the number shown. The timestamps of the first to ninth encrypted data may be updated from the Nth timestamp to the N+1th timestamp. Figure 8 In the example, it is assumed that the time stamps of the first to third encrypted data are updated to the N+1th time stamps. It is assumed that the time stamps of the fourth to ninth encrypted data are not updated to the N+1th time stamps.
[0083] Figure 1 The processor 120 may send a read command for the fourth security data Security Data4 to Figure 1 The encryptor 130 may respond to the read command of the processor 120 and request Figure 1The storage device 160 sends the fourth encrypted data including the fourth security data Security Data 4. According to the above assumption, the timestamp included in the fourth encrypted data may be the Nth timestamp. Hereinafter, the operation of processing the read command of the processor 120 will be described.
[0084] Fig. 9 is a block diagram showing the operation of an encryptor, wherein the encryptor processes as shown in reference Figure 8 The processor reads the command. Figure 1 , Figure 5 and Figure 8 To describe Fig. 9 . Will describe Fig. 9 The encryptor 130 and Figure 5 The differences between the cipher 130 and the processing Figure 1 The operation of the processor 120 to read the command.
[0085] When the time elapses for the update period of the timestamp, the timer 131 may request the counter 132 and the encryption / decryption unit 133 to update the timestamp so that Figure 8 The timestamp of the encrypted data stored in the encrypted data area 161 is updated from the Nth timestamp to the N+1th timestamp. The counter 132 may transmit the N+1th timestamp to the encryption / decryption unit 133 in response to the request of the timer 131.
[0086] In an embodiment, the check logic device 134 may store all Nth timestamps and N+1th timestamps therein. While updating the timestamp of the encrypted data, such as Figure 8 As shown, each time stamp of the encrypted data area 161 may be an Nth time stamp or an N+1th time stamp. Therefore, when the decrypted time stamp is the same as one of the Nth time stamp and the N+1th time stamp, the check logic device 134 may determine or check whether the decrypted data is valid. To this end, the check logic device 134 may perform a comparison operation on the two time stamps (i.e., the Nth time stamp and the N+1th time stamp), respectively.
[0087] refer to Fig. 9 , the encryption / decryption unit 133 may decrypt the fourth encrypted data into decrypted data, and may send the decrypted address and the Nth time stamp to the check logic device 134. The check logic device 134 may determine or check whether each of the decrypted address and the Nth time stamp is valid.
[0088] In an embodiment, the check logic device 134 can determine or check that the decrypted address is the same as the address from Figure 1In other words, when the check logic device 134 operates in response to the read command of the processor 120, the address generated by the address generator 139 may not be used for the comparison operation of the check logic device 134. On the other hand, when the check logic device 134 operates in response to the request of the timestamp of the timer 131, the address generated by the address generator 139 may be used for the comparison operation of the check logic device 134.
[0089] If both the decrypted address and the Nth timestamp are valid, the check logic device 134 does not output an error. The encryption / decryption unit 133 may output the fourth security data Security Data4 to the processor 120 based on the determination result or the check result. In other words, the read command of the processor 120 may be processed.
[0090] Fig.10 It shows Figure 1 FIG. 10 is a diagram of an example of a processor requesting data stored in an encrypted data area. Figure 1 and Figure 8 To describe Fig.10 .exist Fig.10 In, with Figure 8 Different, it is assumed that the timestamps of the first to fifth encrypted data are updated to the N+1th timestamps. It is assumed that the timestamps of the sixth to ninth encrypted data are not updated to the N+1th timestamps. Similar to Figure 8 , Figure 1 The processor 120 may send a read command for the fourth security data Security Data4 to Figure 1 The encryptor 130 may respond to the read command of the processor 120 and request Figure 1 The storage device 160 sends the fourth encrypted data including the fourth security data Security Data4.
[0091] Fig.11 is a block diagram showing the operation of an encryptor, wherein the encryptor processes as shown in reference Fig.10 The processor reads the command. Fig. 9 and Fig.10 To describe Fig.11 . Will describe Fig.11 The encryptor 130 and Fig. 9 The difference between the encryptors 130.
[0092] The encryption / decryption unit 133 may decrypt the fourth encrypted data into decrypted data, and may send the decrypted address and the N+1th timestamp to the check logic device 134. Figure 1When the storage device 160 is attacked by the check logic device 134, the check logic device 134 can determine or check whether each of the address and the N+1th time stamp is valid and does not output an error. The encryption / decryption unit 133 can output the fourth security data Security Data4 to the Figure 1 The processor 120.
[0093] Fig.12 It is shown by Figure 1 FIGURE 10.1 shows an operation of an encryptor to update a timestamp stored in a storage device. Figures 1 to 3 To describe Fig.12 .exist Fig.12 In the example, it is assumed that the first to third encrypted data are stored in Figure 1 In the encrypted data area 161. Herein, the number of the first to third encrypted data is not limited to the number shown, and the first to third addresses (not shown) encrypted by the encryption / decryption unit 133 are also included in the first to third encrypted data.
[0094] Time T1 may indicate the time when the timestamps of the first to third encrypted data are updated to the Nth timestamp. During time T1 to time T2, each of the timestamps of the first to third encrypted data may be the Nth timestamp. The Nth timestamp may be stored in the check logic device 134 as a valid timestamp. During time T1 to time T2, when Figure 1 When the processor 120 issues a read command, the encryptor 130 may determine or check whether the timestamp of the encrypted data according to the read request is the same as the Nth timestamp.
[0095] At time T2, the encryptor 130 may start an operation of updating all timestamps of the first to third encrypted data to the N+1th timestamp. During time T2 to time T3, the encryptor 130 may sequentially update the timestamps of the first to third encrypted data to the N+1th timestamp. In this article, contrary to what is shown, the encryptor 130 may randomly update the timestamps of the first to third encrypted data to the N+1th timestamp.
[0096] The interval between time T2 and time T3 may correspond to an interval for performing updates, rather than an update cycle. Fig.12 In the embodiment, the interval between time T1 and time T2 is the same as the interval between time T2 and time T3. However, the embodiment is not limited thereto. For example, the interval between time T2 and time T3 may be shorter than the interval between time T1 and time T2.
[0097] During time T2 to time T3, the Nth timestamp and the N+1th timestamp may be respectively stored as valid timestamps in the check logic device 134. During time T2 to time T3, when the processor 120 issues a read command, the encryptor 130 may determine or check whether the timestamp of the encrypted data according to the read request is the same as the Nth timestamp or the N+1th timestamp.
[0098] Time T3 may indicate the time when the encryptor 130 updates the timestamps of the first to third encrypted data to the N+1th timestamp. The operation of the encryptor 130 during time T3 to time T4 may be similar to the operation of the encryptor 130 between time T1 and time T2. In addition, the operation of the encryptor 130 after time T4 may be similar to the operation of the encryptor 130 after time T2. After time T4, the first to third encrypted data having the N+1th timestamp may be stored in the encrypted data instead of the first to third encrypted data having the Nth timestamp. Figure 1 The encrypted data area 161 is in the encrypted data area 161.
[0099] In an embodiment, the interval between time T2 and time T4 may be the same as the update period of the timestamp. For example, the timer 131 may be configured to notify the counter 132 and the encryption / decryption unit 133 that time has passed from time T2 to time T4 and request the counter 132 and the encryption / decryption unit 133 to update the timestamp.
[0100] Fig.13 It shows Figure 1 The signal sequence diagram of the operations between the processor, encryptor and storage device. Figures 1 to 12 To describe Fig.13 .
[0101] In operation S110, the processor 120 may send the security data and the address of the security data to the encryptor 130. Herein, the address may be the address of the storage device 160 and may be used to access the storage device 160. Figure 1 A specific location in the encrypted data area 161.
[0102] In operation S115, the encryptor 130 may concatenate the security data, the address, and the time stamp, and may encrypt the concatenated data into the encrypted data. In an embodiment, the encryptor 130 may concatenate the security data and the time stamp, and may not concatenate the address.
[0103] In operation S120, the encryptor 130 may transmit the encrypted data to the storage device 160. The encrypted data may be stored in the encrypted data area 161 of the storage device 160. After operation S120, the encryptor 130 may periodically update the timestamp stored in the encrypted data area 161 to resist various attacks from attackers.
[0104] In operation S125, the encryptor 130 may determine whether time has elapsed by the update period of the time stamp. When the time has elapsed (S125=Yes), operation S135 may be performed. When the time has not elapsed (S125=No), operation S130 may be performed.
[0105] In operation S130, the encryptor 130 may check whether there is an update request from the processor 120. In an embodiment, the processor 120 may request the encryptor 130 to update the timestamp regardless of the update cycle of the timestamp. The update request from the processor 120 may occur according to a user's request. Alternatively, the update request from the processor 120 may occur according to the importance of the security data transmitted in operation S110 or according to the importance of the security data pre-stored in the storage device 160.
[0106] If there is no update request of the processor 120 (S130=No), operation S125 may be performed again. In this case, the encryptor 130 may process various commands such as a write command or a read command of the processor 120. For example, when the processor 120 issues a write command, operations S110 to S120 may be repeated.
[0107] When the time has passed the update cycle of the timestamp (S125=Yes) or when there is an update request of the processor 120 (S130=Yes), operation S135 may be performed. In operation S135, the encryptor 130 may request the storage device 160 to send the encrypted data. For example, the encryptor 130 may send a read command for reading the encrypted data to the storage device 160. In operation S140, in response to the request of the encryptor 130, the storage device 160 may send the encrypted data to the encryptor 130.
[0108] In operation S145, the encryptor 130 may decrypt the encrypted data sent from the storage device 160 into decrypted data. In operation S150, the encryptor 130 may determine or check whether each of the decryption address and the decryption timestamp is valid. In an embodiment, the encryptor 130 may determine or check whether only the decryption timestamp is valid. When it is determined that each of the decryption address and the decryption timestamp is valid (S150=Yes), operations S155 and S160 may be performed. When it is determined that each or any one of the decryption address and the decryption timestamp is invalid (S150=No), operation S165 may be performed, in which the encryptor 130 notifies the processor 120 of an error.
[0109] When it is determined that both the decrypted address and the decrypted timestamp are valid (S150=Yes), the process proceeds to the operation at S155. In operation S155, the encryptor 130 may concatenate the security data, the address, and the new timestamp, and may encrypt the concatenated data into encrypted data. Operation S155 may be similar to operation S115, but the timestamp of operation S155 may be different from the timestamp of operation S115. In other words, the timestamp of the security data may be updated. In operation S160, the encryptor 130 may send the encrypted data to the storage device 160.
[0110] In operation S165, the encryptor 130 may send an error to the processor 120. The error may indicate that the storage device 160 is attacked. In operation S170, the processor 120 may detect the error and resist the attack. For example, the processor 120 may restart the storage device 160. Figure 1 The electronic device 100 may rewrite the security data into the storage device 160, or may generate and store a log file of the error. The log file may be used to analyze the attack and resist the attack.
[0111] In an embodiment, operations S135 to S170 may be performed on all addresses assigned to the encrypted data area 161 of the storage device 160. Therefore, all time stamps of the encrypted data stored in the encrypted data area 161 may be updated to new time stamps.
[0112] Fig.14 It shows Figure 1 Signal sequence diagram of operations between the processor, encryptor, and storage device. Fig.14 An example in which the processor 120 issues a read command is shown. Figures 1 to 13 To describe Fig.14 .
[0113] In operation S210, the processor 120 may send a read command for security data to the encryptor 130. The processor 120 is configured to request security data. The processor 120 may send an address of the storage device 160 for the security data to the encryptor 130.
[0114] In an embodiment, when the encryptor 130 updates the timestamp of the storage device 160, the processor 120 may send a read command to the encryptor 130. The time of sending the read command may be Fig.12 The encryptor 130 may determine or check whether both timestamps (i.e., the timestamp sent to the storage device 160 and stored in the encryptor 130 and the new timestamp generated by the encryptor 130 for updating) are valid. When updating the timestamp of the storage device 160, the encryptor 130 may process the command sent from the processor 120.
[0115] In another embodiment, when the encryptor 130 does not update the timestamp of the storage device 160, the processor 120 may send a read command to the encryptor 130. The time of sending the read command may be, for example, Fig.12 between time T1 and time T2 or Fig.12 In this case, the encryptor 130 may determine or check that only one timestamp (ie, the timestamp sent to the storage device 160 and stored in the encryptor 130) is valid.
[0116] Operations S215 to S240 may be similar to Fig.13 In this document, the address used by the check logic device 134 for the comparison operation in operation S230 may be different from the address used by the check logic device 134 for the comparison operation in operation S150. The address used by the check logic device 134 for the comparison operation in operation S230 may be the address used for the read command sent from the processor 120 in operation S210. On the other hand, the check logic device 134 Fig.13 The address used for the comparison operation in operation S150 may be an address generated by the address generator 139 in response to an update request of the time stamp.
[0117] If the check logic device 134 determines that the address and time stamp of the decrypted data are valid (S230=Yes), the process proceeds to S245. In operation S245, after determining or checking that both the decrypted address and the decrypted time stamp are valid at S230, the encryptor 130 sends the security data to the processor 120. The processor 120 can receive and process the security data. If it is determined at S230 that the address and / or time stamp of the decrypted data are invalid (S230=No), the process proceeds to S235, and an error is sent from the encryptor 130 to the processor 120.
[0118] Fig.15 is a flowchart showing the operation of an encryptor according to an embodiment of the present disclosure. Figures 1 to 14 To describe Fig.15 .
[0119] In operation S310, the encryptor 130 may determine whether the time has elapsed for the update period of the timestamp. Operation S310 may be performed by the timer 131 of the encryptor 130 and may correspond to Fig.13 Operation S125.
[0120] When it is determined at S310 that the update period has elapsed (S310=Yes), the process proceeds to operation at S320. In operation S320, the encryptor 130 may generate a new time stamp for updating. Operation S320 may be performed by the counter 132 of the encryptor 130.
[0121] In operation S330, the encryptor 130 may read the encrypted data of the storage device 160. The encryptor 130 may receive the encrypted data (or read the data) from the storage device 160. In operation S340, the encryptor 130 may decrypt the encrypted data. In an embodiment, operation S320 may be performed together with operations S330 and S340, or may be performed after operations S330 and S340 are performed.
[0122] In operation S350, the encryptor 130 may determine or check whether each of the decryption address and the decryption timestamp is valid. Specifically, the encryptor 130 may determine or check whether the decryption address is the same as the address of the address generator 139, and may determine or check whether the decryption timestamp is the same as the timestamp stored in the check logic device 134. If both the decryption address and the decryption timestamp are valid (S350=Yes), operation S360 may be performed. If the decryption address or the decryption timestamp is invalid (S350=No), operation S380 may be performed.
[0123] In operation S360, the encryptor 130 may concatenate the security data and the decrypted address of the decrypted data and the new timestamp generated in operation S320, and may encrypt the concatenated data. In operation S370, the encryptor 130 may write the encrypted data whose timestamp is updated to the storage device 160. In operation S380, the encryptor 130 may send an error.
[0124] Although not shown, the encryptor 130 may repeatedly perform operations S320 to S380 after operation S370 or S380. Operations S320 to S380 may be repeated until all time stamps of the encrypted data area 161 are updated.
[0125] If the update cycle has not elapsed at S310 (S310=No), the process proceeds to the operation at S390. In operation S390, the encryptor 130 may process the command of the processor 120. When the processor 120 accesses the security data stored in the encrypted data area 161 of the storage device 160, the encryptor 130 may determine or check whether the timestamp stored in the encrypted data area 161 is valid and may determine whether the storage device 160 is attacked.
[0126] Fig.16 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. Figures 1 to 15 To describe Fig.16 The electronic device 200 may include a SoC 210 and first to fourth storage devices 261 to 264. The SoC 210 may include a processor 220, an encryptor 230, and first to fourth memory controllers 241 to 244. The processor 220 may be substantially the same as the reference Figures 1 to 14 The processor 120 described is the same.
[0127] The encryptor 230 may be substantially similar to the reference Figures 1 to 15 The encryptor 230 may encrypt security data transmitted through the bus 250, or may decrypt encrypted data transmitted from at least one of the first to fourth memory controllers 241 to 244. For example, the encryptor 230 may be a slave device for the processor 220, and may be a master device for the first to fourth memory controllers 241 to 244.
[0128] The encryptor 230 may operate as a secure memory and may receive an address space from the processor 220. The processor 220 may send a write command for secure data to the encryptor 230 via the bus 250 using an address assigned to the encryptor 230 (see the first path Path1). The encryptor 230 may concatenate the secure data and the timestamp according to the write command, may encrypt the concatenated data, and may send the encrypted data to at least one of the first to fourth memory controllers 241 to 244 via the bus 250 (see the second path Path2). At least one of the first to fourth memory controllers 241 to 244 may store the sent encrypted data in at least one of the first to fourth storage devices 261 to 264.
[0129] Herein, since the encrypted data is not stored in the encryptor 230 and is stored in the encrypted data areas of the first to fourth storage devices 261 to 264, the encryptor 230 may be referred to as an "encryptor in transit".
[0130] The encryptor 230 may update the timestamp stored in the encrypted data areas of the first storage device 261 to the fourth storage device 264. The encryptor 230 may read the encrypted data from the first memory controller 241 to the fourth memory controller 244. The encryptor 230 may sequentially or randomly access the encrypted data areas of the first storage device 261 to the fourth storage device 264. The encryptor 230 may access the encrypted data areas of the first storage device 261 to the fourth storage device 264 in an interleaved manner.
[0131] The encryptor 230 may decrypt the encrypted data and may check whether the decrypted timestamp is valid. Thereafter, the encryptor 230 may send the encrypted data obtained by encrypting the new timestamp to the first memory controller 241 to the fourth memory controller 244 via the bus 250. Thereafter, the new timestamp may be stored in the encrypted data area of the first storage device 261 to the fourth storage device 264. In other words, one encryptor 230 may manage the timestamps of the first storage device 261 to the fourth storage device 264. The first storage device 261 to the fourth storage device 264 may share one encryptor 230.
[0132] The processor 220 may send a read command for security data to the encryptor 230 via the bus 250 using the address assigned to the encryptor 230 (see the first path Path1). The encryptor 230 may receive encrypted data from at least one of the first memory controller 241 to the fourth memory controller 244 according to the read command (see the second path Path2). The encryptor 230 may decrypt the encrypted data and may determine whether each of the decryption timestamp and the decryption address is valid. If each of the decryption timestamp and the decryption address is valid, the encryptor 230 may send the security data to the processor 220 via the bus 250 (see the first path Path1).
[0133] In an embodiment, contrary to the illustrated case, the SoC 210 may include the same number of encryptors as the number of the first to fourth storage devices 261 to 264. In this case, the encryptors may respectively access the first to fourth storage devices 261 to 264. For example, the illustrated encryptor 230 may only update the timestamp of the encrypted data area 261_1 of the first storage device 261, and may not access the second to fourth storage devices 262 to 264.
[0134] The first to fourth memory controllers 241 to 244 may control the first to fourth storage devices 261 to 264, respectively, according to a request of the processor 220 or the encryptor 230. Each of the first to fourth memory controllers 241 to 244 may provide an interface for communication between the SoC 210 and the first to fourth storage devices 261 to 264. The first to fourth memory controllers 241 to 244 may send data to the first to fourth storage devices 261 to 264, respectively, according to a request of the processor 220 or the encryptor 230. The first to fourth memory controllers 241 to 244 may also provide the data sent from the first to fourth storage devices 261 to 264, respectively, to the processor 220 or the encryptor 230.
[0135] In an embodiment, the first to fourth memory controllers 241 to 244 may operate according to an interface protocol associated with a double data rate (DDR). In another embodiment, the first to fourth memory controllers 241 to 244 may operate according to one or more of various interface protocols associated with the first to fourth storage devices 261 to 264, for example, a universal serial bus (USB), a small computer system interface (SCSI), a peripheral component express interconnect (PCIe), a mobile PCIe (M-PCIe), an advanced technology attachment (ATA), a parallel ATA (PATA), a serial ATA (SATA), a serial attached SCSI (SAS), an integrated drive electronics (IDE), and a universal flash memory (UFS).
[0136] The bus 250 may provide a data input / output path, a command input / output path, etc. between the processor 220, the encryptor 230, and the first to fourth memory controllers 241 to 244. For example, the bus 250 may be implemented as an advanced microcontroller bus architecture (AMBA), an advanced high-performance bus (AHB), an advanced peripheral bus (APB), an advanced extensible interface (AXI), an advanced system bus (ASB), an AXI consistency extension (ACE), or a combination thereof. However, the embodiment is not limited thereto.
[0137] The first to fourth memory devices 261 to 264 may operate based on controls of the first to fourth memory controllers 241 to 244 , respectively. Fig.16 The number of the first to fourth storage devices 261 to 264 shown in FIG. 1 is only one example. The number of memory controllers for controlling the storage devices is not limited to the number shown.
[0138] The first storage device 261 may include an encrypted data area 261_1. For example, all data areas of the first storage device 261 may be pre-set as the encrypted data area 261_1 according to a request of the SoC 210.
[0139] In one embodiment, the first storage device 261 may be one or a combination of various dynamic random access memory (DRAM) devices, such as DDR synchronous DRAM (DDR SDRAM), DDR2 SDRAM, DDR3 SDRAM, DDR4 SDRAM, DDR5 SDRAM, low power double data rate (LPDDR) SDRAM, LPDDR2 SDRAM, LPDDR3 SDRAM, LPDDR4 SDRAM, LPDDR4X SDRAM, LPDDR5 SDRAM, graphic double data rate (GDDR) synchronous graphics RAM (SGRAM), GDDR2 SGRAM, GDDR3 SGRAM, GDDR4 SGRAM, GDDR5 SGRAM, and GDDR6 SGRAM. In addition, the first storage device 261 may be a storage device of stacked DRAM dies, such as high bandwidth memory (HBM), HBM2, or HBM3. In addition, the first storage device 261 can be a static random access memory (SRAM) device, a NAND flash memory device, a NOR flash memory device, a resistive random access memory (RRAM) device, a ferroelectric RAM (FRAM) device, a phase change RAM (PRAM) device, a thyristor RAM (TRAM) device, a magnetic RAM (MRAM) device, etc.
[0140] Each of the second storage device 262 to the fourth storage device 264 may be implemented in the same manner as the first storage device 261 or may not be implemented in this manner. One of the first storage device 261 to the fourth storage device 264 may be different from the other storage devices. For example, each of the first storage device 261 to the third storage device 263 may be a general-purpose DRAM device, and the fourth storage device 264 may be a DRAM device for graphics, or may be an HBM device for high bandwidth. Regardless of the type of the first storage device 261 to the fourth storage device 264, the encryptor 230 according to an embodiment of the present disclosure may store a timestamp together with the encrypted data in the encrypted data area of the first storage device 261 to the fourth storage device 264, and may periodically update the stored timestamp.
[0141] In another embodiment, the first storage device 261 to the fourth storage device 264 can be configured with a dual in-line memory module (DIMM) that complies with the Joint Electronic Device Engineering Council (JEDEC) standard. Alternatively, the first storage device 261 to the fourth storage device 264 can be configured with a registered DIMM (RDIMM), a load-reduced DIMM (LRDIMM), an unbuffered DIMM (UDIMM), a fully buffered DIMM (FB-DIMM), a small outline DIMM (SO-DIMM) or another storage module (e.g., a single in-line memory module (SIMM)).
[0142] In another embodiment, the first memory device 261 may be implemented using various semiconductor packages. For example, the semiconductor package may include a package on package (PoP), a ball grid array (BGA), a chip scale package (CSP), a plastic lead chip carrier (PLCC), a plastic dual in-line package (PDIP), a die in a wafer package, a die in wafer form, a chip on board (COB), a ceramic dual in-line package (CERDIP), a metric quad flat package (MQFP), a thin quad flat package (TQFP), a small outline integrated circuit (SOIC), a shrink small outline package (SSOP), a thin small outline package (TSOP), a system-in-package (SIP), a multi-chip package (MCP), a wafer-level manufacturing package (WFP), a wafer-level processing stack package (WSP), etc. Each of the second memory devices 262 to the fourth memory devices 264 may be implemented using any of the various semiconductor packages described above. Each of the first memory devices 261 to the fourth memory devices 264 may be a memory die, and all of the first memory devices 261 to the fourth memory devices 264 may be included in one package (using through silicon vias). The SoC 210 may be implemented using the various semiconductor packages described above.
[0143] Fig.17 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. Fig.17 In the following, the electronic device 300 and Fig.16 The differences between the electronic devices 200.
[0144] Can basically be Fig.16 SoC 310 may be implemented in the same manner as SoC 210 of the present invention. Herein, SoC 310 may set the data area of the first storage device 361 and the second storage device 362 as an unencrypted data area, and may set the data area of the third storage device 363 and the fourth storage device 364 as an encrypted data area. The operation of SoC 310 accessing the third storage device 363 and the fourth storage device 364 may be substantially the same as Fig.16The operation of the SoC 210 accessing the first to fourth storage devices 261 to 264 is the same.
[0145] The processor 320 may store general data instead of security data in the first storage device 361 and the second storage device 362, or may read general data from the first storage device 361 and the second storage device 362 (see the third path Path3). In other words, in the case of general data, the processor 320 may immediately use the first memory controller 341 and the second memory controller 342 without using the encryptor 330. Therefore, the input / output path of general data (e.g., the third path Path3) and the input / output path of security data (e.g., the fourth path Path4 and the fifth path Path5) are separated. In other words, there is no delay caused by the encryptor 330 in the data input / output of general data.
[0146] Fig.18 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. Fig.18 In the embodiment, the electronic device 400 and Fig.16 The electronic device 200 and Fig.17 The differences between the electronic devices 300.
[0147] Can basically be Fig.16 SoC 410 is implemented in the same manner as SoC 210 of the present invention. Herein, SoC 410 may set a portion of the data area of each of the first storage device 461 to the fourth storage device 464 as an encrypted data area, and may set the rest of the data area as an unencrypted data area. Fig.16 The first to fourth storage devices 461 to 464 may be implemented in the same manner as the first to fourth storage devices 261 to 264 , but data areas of the storage devices may be set differently according to the setting of the SoC 410 .
[0148] According to the setting of SoC 410, the data area of the first storage device 461 may be divided into an encrypted data area 461_1 and a non-encrypted data area 461_2. The data areas of the second storage device 462 to the fourth storage device 464 may be set in a similar manner to the data area of the first storage device 461. Herein, the encrypted data areas of the first storage device 461 to the fourth storage device 464 may be the same size as each other, or may be different in size from each other. Additionally, the non-encrypted data areas of the first storage device 461 to the fourth storage device 464 may be the same size as each other, or may be different in size from each other.
[0149] In an embodiment, the operation of the SoC 410 accessing the encrypted data area of the first storage device 461 to the fourth storage device 464 may be substantially the same as Fig.16 The operation of the SoC 210 accessing the first storage device 261 to the fourth storage device 264 is the same. The operation of the SoC 410 accessing the unencrypted data area of the first storage device 461 to the fourth storage device 464 can be basically the same as Fig.17 The operations of the SoC 310 accessing the first storage device 361 and the second storage device 362 are the same.
[0150] Fig.19 It shows Fig.18 A diagram of the processor's address space. Fig.18 To describe Fig.19 The processor address space 500 may be composed of Fig.18 The logical address space accessed by the processor 420. The address space 500 of the processor may include an address space 510 of the encryptor and an address space 520 of the first storage device 461 to the fourth storage device 464.
[0151] The address space 510 of the encryptor may be identified by the processor 420, which is similar to the address space 520 of the first storage device 461 to the fourth storage device 464. The address space 520 of the first storage device 461 to the fourth storage device 464 may be formed while a portion of the data area of the first storage device 461 to the fourth storage device 464 is interleaved with each other. A row of the address space 520 of the first storage device 461 to the fourth storage device 464 may indicate a space capable of storing encrypted data. For example, the size of a row may correspond to a unit of encryption operation of the encryption / decryption unit 133, for example, 128 bits or 256 bits.
[0152] The address space 520 of the first to fourth storage devices 461 to 464 may include an address space 521 of an encrypted data area and an address space 522 of a non-encrypted data area. For example, the address space 521 of the encrypted data area may be the same in size as the address space 510 of the encryptor.
[0153] Fig. 20 6 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. The electronic device 600 may include a SoC 610 and a storage device 660. Fig. 20 In the embodiment, the electronic device 600 and Figures 16 to 18 The differences between electronic devices.
[0154] The SoC 610 may include a processor 620 and first to fourth encryptors 631 to 634. The processor 620 and the first to fourth encryptors 631 to 634 may communicate with each other via a bus 650.
[0155] Can basically be compared with reference Figures 1 to 15 Each of the first to fourth encryptors 631 to 634 is implemented in the same manner as the encryptor 130 described above. Figures 16 to 18 In the example, each of the encryptors 230, 330, and 430 can manage the timestamps of the encrypted data areas of one or more storage devices. Fig. 20 In the embodiment, each of the first to fourth encryptors 631 to 634 can manage the time stamp of each of the first to fourth encrypted data areas 661 to 664. Therefore, the number of valid time stamps in the storage device 660 may be one or more, and the first to fourth encryptors 631 to 634 can independently update the time stamps of the first to fourth encrypted data areas 661 to 664.
[0156] In an embodiment, although not shown, when the electronic device 600 includes four storage devices, each of the first to fourth encryptors 631 to 634 may manage the timestamp of the encrypted data area of each of the four storage devices. The number of encryptors, the number of encrypted data areas, and the number of storage devices are not limited to Fig. 20 The quantity shown in .
[0157] Fig.21 1 is a block diagram showing a configuration of an electronic device according to another embodiment of the present disclosure. The electronic device 1000 may be implemented to be able to use or support an interface proposed by the Mobile Industry Processor Interface (MIPI) Alliance. For example, the electronic device 1000 may be, but is not limited to, one of the following: a server, a computer, a smart phone, a tablet computer, a personal digital assistant (PDA), a digital camera, a portable multimedia player (PMP), a wearable device, an Internet of Things (IoT) device, etc.
[0158] The electronic device 1000 may include a SoC 1100 and a storage device 1600. The SoC 1100 may include a processor 1120 and an encryptor 1130, and may be substantially similar to the reference 1100. Figures 1 to 20 The storage device 1600 may include an encrypted data area 1610 and a non-encrypted data area 1620, and may be substantially the same as the SoC 110, SoC 210, SoC 310, SoC 410, and SoC 610 described above. Figures 1 to 20The described storage devices 160, 261 to 264, 361 to 364, 461 to 464 and 660 are implemented in the same manner.
[0159] The electronic device 1000 may further include a display 1710 communicating with the SoC 1100. The SoC 1100 may communicate with a DSI device 1715 (Display Serial Interface Device) according to the DSI. For example, an optical deserializer DES may be implemented in the DSI device 1715.
[0160] The electronic device 1000 may further include an image sensor 1720 that communicates with the SoC 1100. The SoC 1100 may communicate with a CSI device 1725 (camera serial interface device) according to the CSI. For example, an optical serializer SER may be implemented in the CSI device 1725.
[0161] The electronic device 1000 may further include an RF chip 1730 (radio frequency chip) that communicates with the SoC 1100. The RF chip 1730 may include a PHY 1731 (physical layer), a DigRF slave device 1732, and an antenna 1733. For example, the PHY 1731 of the RF chip 1730 and the SoC 1100 may exchange data with each other through a DigRF interface proposed by the MIPI Alliance.
[0162] The electronic device 1000 may further include an embedded / card-type storage device 1740. The embedded / card-type storage device 1740 may store data provided from the SoC 1100, and may permanently store data provided from the storage device 1600. The electronic device 1000 may communicate with an external system through Worldwide Interoperability for Microwave Access (WiMAX) 1750, a Wireless Local Area Network (WLAN) 1760, an Ultra Wideband (UWB) 1770, and the like.
[0163] Apart from Fig.21 In addition to the components shown in FIG. 1 , the electronic device 1000 may further include other components (eg, a speaker, a microphone, a global positioning system GPS, etc.).
[0164] According to an embodiment of the present disclosure, in the electronic device 1000, security data may be stored in the encrypted data area 1610 of the storage device 1600. The encryptor 1130 may periodically update the timestamp of the security data, and may determine whether the timestamp stored in the encrypted data area 1610 is changed due to an attack. Therefore, the electronic device 1000 may resist attacks on the storage device 1600.
[0165] According to an embodiment of the present disclosure, an encryption device can encrypt security data and a timestamp, and can store the encrypted data in a storage device. Therefore, the encryption device can periodically update the timestamp stored in the storage device. The encryption device can determine whether the timestamp stored in the storage device has changed due to an attack on the storage device. Therefore, the encryption device can resist attacks on the storage device.
[0166] Although the inventive concept of the present disclosure has been described with reference to exemplary embodiments, it is apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the inventive concept. Therefore, it should be understood that the above embodiments are not restrictive but illustrative.
Claims
1. An encryption device, include: a counter configured to generate a first timestamp for a first time; an encryption / decryption unit configured to concatenate security data with the first timestamp into concatenated data, encrypt the concatenated data into encrypted data, send the encrypted data to a storage device, and decrypt the read data sent from the storage device into decrypted data; as well as a timer configured to request the counter and the encryption / decryption unit to update a timestamp so that the timestamp of the encrypted data of the storage device is updated from the first timestamp to a second timestamp for a second time, The check logic device implemented by the encryption device is configured to check whether the decryption timestamp of the decrypted data is the same as the first timestamp before the timestamp of the encrypted data of the storage device is updated to the second timestamp.
2. The encryption device according to claim 1, in, Each of a size of the security data and a size of the first time stamp is the same as a size of a unit of an encryption operation of the encryption / decryption unit.
3. The encryption device according to claim 1, in, The check logic device is further configured to output an error indicating that the storage device has been attacked when the decryption timestamp is different from the first timestamp.
4. The encryption device according to claim 1, in, The encryption / decryption unit is further configured to: when the decryption timestamp is the same as the first timestamp, concatenating the security data of the decrypted data with the second timestamp; Encrypt the concatenated data into new encrypted data; as well as The new encrypted data is sent to the storage device.
5. The encryption device according to claim 1, in, The encryption / decryption unit is further configured to: concatenate the address of the security data with the concatenation data, wherein the concatenation data is formed by concatenating the security data with the first timestamp.
6. The encryption device according to claim 5, in, Each of a concatenated size of the address of the security data and the first time stamp and a size of the security data is identical to a size of a unit of an encryption operation of the encryption / decryption unit.
7. The encryption device according to claim 5, in, The check logic device is further configured to output an error indicating that the storage device is attacked when the decryption timestamp is different from the first timestamp or the decryption address of the decrypted data is different from the address of the security data.
8. The encryption device according to claim 5, in, The encryption / decryption unit is further configured to: when the decryption timestamp is the same as the first timestamp and the decryption address of the decrypted data is the same as the address of the security data, Cascading the security data of the decrypted data, the decryption address of the decrypted data and the second timestamp; Encrypt the concatenated data into new encrypted data; as well as The new encrypted data is sent to the storage device.
9. A system on a chip SoC, include: a processor configured to generate security data; a counter configured to generate a timestamp to be concatenated with the security data; an encryption / decryption unit configured to concatenate the security data and the timestamp into concatenated data; encrypting the concatenated data into encrypted data; and sending the encrypted data to a storage device in response to a write command from the processor so as to store the secure data in the storage device; and decrypting the read data sent from the storage device into decrypted data in response to a request of a timer or a request of the processor; as well as a timer configured to periodically request an update of a timestamp of the encrypted data stored in the storage device, The checking logic device implemented by the system on chip is configured to check whether the decryption timestamp of the decrypted data is the same as the previously concatenated timestamp.
10. The system on chip according to claim 9, in, The update period of the time stamp is a predetermined value or a value changed by a request of the processor.
11. The system on chip according to claim 10, in, The counter is further configured to increase or decrease the value of the timestamp for each update period.
12. The system on chip according to claim 9, in, The check logic device is further configured to output an error indicating that the storage device has been attacked to the processor when the decryption timestamp is invalid.
13. The system on chip according to claim 9, in, The encryption / decryption unit is further configured to: when the decryption timestamp is valid, in response to a request from the timer, concatenating the security data of the decrypted data with a new timestamp updated by the counter; Encrypt the concatenated data into new encrypted data; as well as The new encrypted data is sent to the storage device.
14. The system on chip according to claim 13, in, The checking logic device is further configured to compare the new timestamp updated by the counter with the decryption timestamp.
15. An electronic device, include: A storage device configured to store first encrypted data, wherein the first encrypted data is encrypted by encrypting first security data and a first timestamp; as well as A system on chip (SoC) configured to decrypt the first encrypted data stored in the storage device into decrypted data; and check whether a timestamp of the decrypted data is the same as the first timestamp to obtain a check result; Updating the first timestamp in the decrypted data to a second timestamp; And storing second encrypted data in the storage device instead of the first encrypted data, wherein the second encrypted data is obtained by encrypting the decrypted data updated with the second time stamp.
16. The electronic device according to claim 15, in, The system on chip comprises: a counter configured to generate a second timestamp indicating a second time and a third timestamp indicating a first time when the first encrypted data was stored in the storage device; a timer configured to request an update of the first timestamp when time elapses from the first time to the second time; and The encryption / decryption unit is configured to respond to a request of the timer, concatenate the first security data with the second timestamp into concatenated data based on a check result, encrypt the concatenated data into second encrypted data, and send the second encrypted data to the storage device.
17. The electronic device according to claim 16, in, The system on chip further comprises: The checking logic device is configured to check whether the first time stamp is the same as the third time stamp.
18. The electronic device according to claim 16, in, The check logic device implemented by the system on chip is configured to check whether the first time stamp is the same as the third time stamp or the second time stamp.
19. The electronic device according to claim 16, in, The system on chip further includes a processor configured to request the first security data of the first encrypted data stored in the storage device.
20. The electronic device according to claim 19, in, The encryption / decryption unit is further configured to: output the first security data to the processor in response to a request of the processor when the first timestamp is valid.
