WO2024005419A1

WO2024005419A1 - Electronic device for providing encryption service and operation method thereof

Info

Publication number: WO2024005419A1
Application number: PCT/KR2023/008366
Authority: WO
Inventors: 문의성
Original assignee: 삼성전자 주식회사
Priority date: 2022-07-01
Filing date: 2023-06-16
Publication date: 2024-01-04

Abstract

Disclosed is an electronic device comprising a communication circuit and at least one processor operatively connected to the communication circuit. The at least one processor may be configured to: receive, from an external electronic device that does not support a security function, an authentication request including unique information through the communication circuit; allocate, on the basis of the unique information, a security storage area for the external electronic device; generate a data encryption key for the external electronic device, and store the data encryption key in the security storage area; generate a session key for session communication with the external electronic device; and in response to a request from the external electronic device encrypted with the session key, provide an encryption and/or decryption service based on the data encryption key to the external electronic device.

Description

Electronic device providing encryption service and method of operation thereof

This disclosure relates to an electronic device that provides encryption services and a method of operating the same.

Due to the development of wireless communication technology, it has become possible to conveniently control objects by including communication functions in various objects and forming a network. In this way, connecting objects to a network including communication functions is called the Internet of Things (IoT) and is widely used in real life. This IoT is used in various fields such as smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliances, or advanced medical service through the convergence and combination of existing IT technology and various industries. It can be applied.

In the case of a smart home environment, various IoT-based services can be provided using various IoT devices. Electronic devices such as smartphones can run applications for managing IoT devices.

As the number of IoT devices increases and the market expands rapidly, security for IoT devices is becoming a big issue. Typically, electronic devices such as mobile devices or IoT devices can perform various functions using security data such as private information or cryptographic keys. If an electronic device is attacked by a malicious user while storing secure data, the secure data may be stolen.

In particular, IoT devices used in smart home environments (e.g. door locks, home CCTV, or wall pads) can store or manage very private personal data (e.g. door lock access records or captured images), and these personal data Being hijacked can cause great anxiety and discomfort to the user. However, many IoT devices may not have high-level security features (for example, a high assurance level storage area for storing encryption keys) to satisfy the user's needs, and thus There may be a high risk of personal data being stolen.

An electronic device according to an embodiment may include a communication circuit and at least one processor operatively connected to the communication circuit. The at least one processor may be configured to receive an authentication request including unique information from an external electronic device that does not support a security function through the communication circuit. The at least one processor may be configured to allocate a secure storage area for the external electronic device based on the unique information. The at least one processor may be configured to generate a data encryption key for the external electronic device and store it in the secure storage area. The at least one processor may be configured to generate a session key for session communication with the external electronic device. The at least one processor may be configured to provide an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key.

An electronic device according to an embodiment may include a communication interface and at least one processor operatively connected to the communication interface. The at least one processor may be configured to transmit an authentication request including unique information to an external electronic device supporting a security function through the communication interface. The at least one processor may be configured to receive first session key creation information from the external electronic device. The at least one processor may be configured to generate a session key for session communication with the external electronic device based on the first session key generation information. The at least one processor may be configured to transmit second session key generation information for verification of the session key to the external electronic device. The at least one processor may be configured to use an encryption and/or decryption service provided by the external electronic device based on the session key.

A method of operating an electronic device according to an embodiment may include receiving an authentication request including unique information from an external electronic device that does not support a security function. The method may include allocating a secure storage area for the external electronic device based on the unique information. The method may include generating a data encryption key for the external electronic device and storing it in the secure storage area. The method may include generating a session key for session communication with the external electronic device. The method may include providing an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key.

A method of operating an electronic device according to an embodiment may include transmitting an authentication request including unique information to an external electronic device that supports a security function. The method may include receiving first session key creation information from the external electronic device. The method may include generating a session key for session communication with the external electronic device based on the first session key generation information. The method may include transmitting second session key generation information for verification of the session key to the external electronic device. The method may include using an encryption and/or decryption service provided by the external electronic device based on the session key.

According to one embodiment, a non-transitory computer-readable storage medium storing one or more programs, wherein the one or more programs, when executed by at least one processor of an electronic device, causes the electronic device to: Receive an authentication request containing unique information from, allocate a secure storage area for the external electronic device based on the unique information, generate a data encryption key for the external electronic device and store it in the secure storage area, and , Generating a session key for session communication with the external electronic device, and providing an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key. It may contain commands that configure it to do so.

According to one embodiment, a non-transitory computer-readable storage medium storing one or more programs, wherein the one or more programs, when executed by at least one processor of an electronic device, cause the electronic device to: Transmit an authentication request containing unique information, receive first session key generation information from the external electronic device, and generate a session key for session communication with the external electronic device based on the first session key generation information. and transmitting second session key creation information for verification of the session key to the external electronic device, and configuring to use an encryption and/or decryption service provided by the external electronic device based on the session key. may include.

1 illustrates an internet of things (IoT) system according to various embodiments.

2 is a block diagram of an electronic device in a network environment, according to various embodiments.

Figure 3 is a diagram for explaining an IoT network according to an embodiment.

Figure 4 is a block diagram for explaining the configuration of an electronic device according to an embodiment.

Figure 5 is a block diagram for explaining the configuration of an external electronic device according to an embodiment.

FIG. 6 is a flowchart illustrating a procedure in which an electronic device provides an encryption service according to an embodiment.

FIG. 7 is a flowchart illustrating a procedure in which an external electronic device provides an encryption service according to an embodiment.

Figure 8 shows a signal flow diagram for explaining a procedure for performing device authentication and session key generation according to one embodiment.

Figure 9 shows an example of a user interface screen that confirms the use of a security element in an electronic device, according to an embodiment.

FIG. 10 is a flowchart illustrating a procedure in which an electronic device provides an encryption service according to an embodiment.

FIG. 11 is a flowchart illustrating a procedure in which an external electronic device uses an encryption service according to an embodiment.

Figure 12 shows a signal flow diagram to explain a procedure for providing encryption services according to an embodiment.

Figure 13 shows a signal flow diagram to explain a procedure for providing a decryption service according to an embodiment.

FIG. 14 is a diagram illustrating safe storage of a password according to an embodiment.

FIG. 15 is a diagram illustrating safe storage of image data according to an embodiment.

Figure 16 shows a signal flow diagram for explaining a procedure for updating a session key according to one embodiment.

FIG. 17 is a signal flow diagram illustrating a procedure for generating an asymmetric key for server authentication according to an embodiment.

1 illustrates an internet of things (IoT) system 100 according to various embodiments. Meanwhile, at least some of the components in FIG. 1 may be omitted, and may be implemented to include additional components not shown.

Referring to FIG. 1, the IoT system 100 according to one embodiment includes a plurality of electronic devices connectable to the

data network

116 or 146. For example, the IoT system 100 includes a first IoT server 110, a first node 120, a voice assistance server 130, a second IoT server 140, and a second node. 150, or may include at least one of the

devices

121, 122, 123, 124, 125, 136, 137, 151, 152, and 153.

According to one embodiment, the first IoT server 110 may include at least one of a communication interface 111, a processor 112, or a storage unit 113. The second IoT server 140 may include at least one of a communication interface 141, a processor 142, or a storage unit 143. “IoT server” in this document refers to a relay device (e.g., first node 120 or second node (120), for example, based on a data network (e.g., data network 116 or data network 146). One or more devices (e.g.,

devices

121, 122, 123, 124, 125, 151, 152, 153) can be remotely controlled and/or monitored via 150)) or directly without a relay device. “Device” herein refers to a sensor, appliance, office electronic device, or It is a device for performing processes, and there are no restrictions on its type. A device that receives a control command and performs an operation corresponding to the control command may be named a “target device.” The IoT server may be called a central server in that it selects a target device among a plurality of devices and provides control commands.

According to one embodiment, the first IoT server 110 may communicate with the

devices

121, 122, and 123 through the data network 116. Data network 116 may refer to a network for long-distance communication, such as the Internet or a computer network (e.g., LAN or WAN), or may include a cellular network.

According to one embodiment, the first IoT server 110 may be connected to the data network 116 through the communication interface 111. The communication interface 111 may include a communication device (or communication module) to support communication of the data network 116, and may be integrated into one component (e.g., a single chip), or may be integrated into a plurality of separate components. It can be implemented with components (e.g., multiple chips). The first IoT server 110 may communicate with the

devices

121, 122, and 123 through the first node 120. The first node 120 may receive data from the first IoT server 110 through the data network 116 and transmit the received data to at least some of the

devices

121, 122, and 123. Alternatively, the first node 120 may receive data from at least some of the

devices

121, 122, and 123, and transmit the received data to the first IoT server 110 through the data network 116. The first node 120 may function as a bridge between the data network 116 and the

devices

121, 122, and 123. Meanwhile, in FIG. 1, it is shown as if there is only one first node 120, but this is simply an example and there is no limit to the number.

A “node” in this document may be an edge computing system, or may be a hub device. According to one embodiment, the first node 120 supports wired and/or wireless communication of the data network 116, and may also support wired and/or wireless communication with the

devices

121, 122, and 123. . For example, the first node 120 may be configured to communicate via a short-range communication network such as at least one of Bluetooth, Wi-Fi, Wi-Fi direct, Z-wave, Zig-bee, INSETEON, X10, or IrDA (infrared data association). It can be connected to

devices

121, 122, and 123, but there is no limitation on the type of communication. The first node 120 is placed in an environment such as a home, office, factory, building, external location, or other types of premises. (or, location). Accordingly, the

devices

121, 122, and 123 may be monitored and/or controlled by the service provided by the first IoT server 110, and the

devices

121, 122, and 123 may be connected to the first IoT server 110. It may not be required to have the capability of complete network communication (e.g., Internet communication) for direct connection to the IoT server 110.

Devices

121, 122, and 123 may include, for example, a light switch, a proximity sensor, Although it is shown as being implemented as an electronic device in a home environment, such as a temperature sensor, this is illustrative and is not limiting.

According to one embodiment, the first IoT server 110 may support direct communication with the

devices

124 and 125. Here, “direct communication” may mean communication that does not go through a relay device such as the first node 120, for example, communication through a cellular communication network and/or a data network.

According to one embodiment, the first IoT server 110 may transmit a control command to at least some of the

devices

121, 122, 123, 124, and 125. Here, “control command” may mean data that causes a controllable device to perform a specific operation, and the specific operation is an operation performed by the device, such as outputting information, sensing information, reporting information, It may include management of information (e.g. deletion or creation), and there is no limit to the type. For example, the processor 112 generates a control command from an external source (e.g., the voice assistant server 130, the second IoT server 140, the external system 160, or at least some of the

devices

121, 122, 123, 124, and 125). Information (or request) to do so may be obtained, and a control command may be generated based on the obtained information. Alternatively, the processor 112 may generate a control command based on the monitoring results of at least some of the

devices

121, 122, 123, 124, and 125 satisfying specified conditions. The processor 112 may control the communication interface 111 to transmit control commands to the target device.

According to one embodiment, the processor 112, or the processor 132, or the processor 142 is a central processing unit (CPU), a digital signal processor (DSP), an application processor (AP), a communication processor (CP), etc. It may be implemented as a combination of one or more of a general-purpose processor, a graphics-specific processor such as a graphical processing unit (GPU), a vision processing unit (VPU), or an artificial intelligence-specific processor such as a neural processing unit (NPU). Those skilled in the art will understand that the above-described processing unit is merely an example, and that the processor 112 is not limited to any computational means that can, for example, execute instructions stored in the memory 113 and output the executed result.

According to one embodiment, the processor 112 may configure a web-based interface based on the API 114 or expose resources managed by the first IoT server 110 to the outside. . The web-based interface may support communication between the first IoT server 110 and an external web service, for example. The processor 112 may, for example, allow the external system 160 to control and/or access the

devices

121, 122, and 123. External system 160 may be, for example, an independent system that is not related to or part of system 100. External system 160 may be, for example, an external server or a website. However, security is required for access to the

devices

121, 122, and 123 from the external system 160 or the resources of the first IoT server 110. According to one embodiment, the processor 112 and the automation application may expose an API endpoint (eg, a universal resource locator (URL)) based on the API 114 to the outside. According to the above description, the first IoT server 110 may transmit a control command to the target device among the

devices

121, 122, and 123. Meanwhile, the description of the communication interface 141, the processor 142, the API 144 of the storage unit 143, and the database 145 of the second IoT server 140 are described in detail in the communication of the first IoT server 110. It may be substantially the same as the description of the interface 111, the processor 112, the API 114 of the storage unit 113, and the database 115. In addition, the description of the second node 150 may be substantially the same as the description of the first node 120. The second IoT server 140 may transmit a control command to a target device among the

devices

151, 152, and 153. The first IoT server 110 and the second IoT server 140 may be operated by the same service provider in one embodiment, but may be operated by different service providers in another embodiment.

According to one embodiment, the voice assistant server 130 may transmit and receive data with the first IoT server 110 through the data network 116. The voice assistant server 130 according to one embodiment may include at least one of a communication interface 131, a processor 132, and a storage unit 133. The communication interface 131 may communicate with the smart phone 136 or the AI speaker 137 through a data network (not shown) and/or a cellular network (not shown). The smart phone 136 or the AI speaker 137 may include a microphone, acquire a user voice, convert it into a voice signal, and transmit the voice signal to the voice assistant server 130. The processor 132 may receive a voice signal from the smart phone 136 or the AI speaker 137 through the communication interface 131. The processor 132 may process the received voice signal based on the stored model 134. The processor 132 may generate (or confirm) a control command using the processing result based on information stored in the database 135. According to one embodiment, the

storage units

113, 133, and 143 include flash memory type, hard disk type, multimedia card micro type, and card type memory (e.g. SD or It may include at least one type of non-transitory storage medium among memory, magnetic memory, magnetic disk, and optical disk, and there is no limit to its type.

In various embodiments, at least one device (e.g., device 124) communicating with the first IoT server 110 may be a smartphone (e.g., electronic device 201 of FIG. 2) in a network environment. .

FIG. 2 is a block diagram of an electronic device 201 in a network environment 200, according to various embodiments.

Referring to FIG. 2, in the network environment 200, the electronic device 201 communicates with the electronic device 202 through the first network 298 (e.g., a short-range wireless communication network) or through the second network 299. It is possible to communicate with at least one of the electronic device 204 or the server 208 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 201 may communicate with the electronic device 204 through the server 208. According to one embodiment, the electronic device 201 includes a processor 220, a memory 230, an input module 250, an audio output module 255, a display module 260, an audio module 270, and a sensor module ( 276), interface 277, connection terminal 278, haptic module 279, camera module 280, power management module 288, battery 289, communication module 290, subscriber identification module 296 , or may include an antenna module 297. In some embodiments, at least one of these components (eg, the connection terminal 278) may be omitted, or one or more other components may be added to the electronic device 201. In some embodiments, some of these components (e.g., sensor module 276, camera module 280, or antenna module 297) are integrated into one component (e.g., display module 260). It can be.

Processor 220, for example, executes software (e.g., program 240) to operate at least one other component (e.g., hardware or software component) of electronic device 201 connected to processor 220. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of the data processing or computation, the processor 220 stores instructions or data received from another component (e.g., the sensor module 276 or the communication module 290) in the volatile memory 232. The commands or data stored in the volatile memory 232 can be processed, and the resulting data can be stored in the non-volatile memory 234. According to one embodiment, the processor 220 includes a main processor 221 (e.g., a central processing unit or an application processor) or an auxiliary processor 223 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 201 includes a main processor 221 and a auxiliary processor 223, the auxiliary processor 223 may be set to use lower power than the main processor 221 or be specialized for a designated function. You can. The auxiliary processor 223 may be implemented separately from the main processor 221 or as part of it.

The auxiliary processor 223 may, for example, act on behalf of the main processor 221 while the main processor 221 is in an inactive (e.g., sleep) state, or while the main processor 221 is in an active (e.g., application execution) state. ), together with the main processor 221, at least one of the components of the electronic device 201 (e.g., the display module 260, the sensor module 276, or the communication module 290) At least some of the functions or states related to can be controlled. According to one embodiment, coprocessor 223 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 280 or communication module 290). there is. According to one embodiment, the auxiliary processor 223 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 201 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 208). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

The memory 230 may store various data used by at least one component (eg, the processor 220 or the sensor module 276) of the electronic device 201. Data may include, for example, input data or output data for software (e.g., program 240) and instructions related thereto. Memory 230 may include volatile memory 232 or non-volatile memory 234.

The program 240 may be stored as software in the memory 230 and may include, for example, an operating system 242, middleware 244, or application 246.

The input module 250 may receive commands or data to be used in a component of the electronic device 201 (e.g., the processor 220) from outside the electronic device 201 (e.g., a user). The input module 250 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 255 may output sound signals to the outside of the electronic device 201. The sound output module 255 may include, for example, a speaker or a receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 260 can visually provide information to the outside of the electronic device 201 (eg, a user). The display module 260 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 260 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 270 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 270 acquires sound through the input module 250, the sound output module 255, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 201). Sound may be output through an electronic device 202 (e.g., speaker or headphone).

The sensor module 276 detects the operating state (e.g., power or temperature) of the electronic device 201 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 276 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 277 may support one or more designated protocols that can be used to connect the electronic device 201 directly or wirelessly with an external electronic device (eg, the electronic device 202). According to one embodiment, the interface 277 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 278 may include a connector through which the electronic device 201 can be physically connected to an external electronic device (eg, the electronic device 202). According to one embodiment, the connection terminal 278 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 279 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 279 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 280 can capture still images and moving images. According to one embodiment, the camera module 280 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 288 can manage power supplied to the electronic device 201. According to one embodiment, the power management module 288 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

Battery 289 may supply power to at least one component of electronic device 201. According to one embodiment, the battery 289 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

Communication module 290 provides a direct (e.g., wired) communication channel or wireless communication channel between electronic device 201 and an external electronic device (e.g., electronic device 202, electronic device 204, or server 208). It can support establishment and communication through established communication channels. Communication module 290 operates independently of processor 220 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 290 is a wireless communication module 292 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 294 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 298 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 299 (e.g., legacy It may communicate with an external electronic device 204 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 292 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 296 within a communication network such as the first network 298 or the second network 299. The electronic device 201 can be confirmed or authenticated.

The wireless communication module 292 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 292 may support high frequency bands (e.g., mmWave bands), for example, to achieve high data rates. The wireless communication module 292 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive array multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 292 may support various requirements specified in the electronic device 201, an external electronic device (e.g., electronic device 204), or a network system (e.g., second network 299). According to one embodiment, the wireless communication module 292 supports Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 297 may transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module 297 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 297 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 298 or the second network 299 is, for example, connected to the plurality of antennas by the communication module 290. can be selected. Signals or power may be transmitted or received between the communication module 290 and an external electronic device through the at least one selected antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 297.

According to various embodiments, the antenna module 297 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes: a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( (e.g. commands or data) can be exchanged with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device 201 and the external electronic device 204 through the server 208 connected to the second network 299. Each of the external

electronic devices

202 or 204 may be of the same or different type as the electronic device 201. According to one embodiment, all or part of the operations performed in the electronic device 201 may be executed in one or more of the external

electronic devices

202, 204, or 208. For example, when the electronic device 201 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 201 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device 201. The electronic device 201 may process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 201 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 204 may include an Internet of Things (IoT) device. Server 208 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 204 or server 208 may be included in the second network 299. The electronic device 201 may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

Figure 3 is a diagram for explaining an IoT network according to an embodiment.

Referring to FIG. 3, the IoT network 300 supports an electronic device 201 capable of communicating with the server 310 through network communication (e.g., the Internet), and IoT technology and supports network communication (e.g., the Internet). ) at least one external electronic device 320 capable of communicating with the server 310 or the electronic device 201 (e.g., a television 320a, a refrigerator 320b, a washing machine 320d, a light 320e) , or a controlled device such as CCTV 320b. In one embodiment, the external electronic device 320 may communicate with the electronic device 201 and/or the server 310 through a hub device (not shown). In one embodiment, the electronic device 201 is configured via the server 310, via a hub device (not shown), via long-range wireless communication (e.g., second network 299), or short-range wireless communication (e.g., For example, it is possible to communicate with the external electronic device 320 through the first network 298).

In one embodiment, the external electronic device 320 may be controlled (e.g., report status and/or execute a specific function) by a remote command (e.g., a control command of the electronic device 201 or the server 310). and, for example, may include at least one of a television, an air conditioner, a refrigerator, a washing machine, a lighting device, a security camera, a sensor, or a window treatment. The external electronic device 320 may communicate directly with the electronic device 201 (for example, without going through the server 310 or a hub device). In one embodiment, the external electronic device 320 is connected to the electronic device 201 via long-range wireless communication (e.g., second network 299) or short-range wireless communication (e.g., first network 298). It may be configured to communicate with. In one embodiment, the external electronic device 320 connects to the server 310 via long-range wireless communication (e.g., the second network 299) or using short-range wireless communication (e.g., the first network 298). It may be configured to communicate with.

In one embodiment, the electronic device 201 checks the status of the external electronic device 320 that the user will use for the IoT control service, or controls the external electronic device 320 (for example, reads personal information or specifies A control command instructing to execute a function can be transmitted. The electronic device 201 can discover the external electronic device 320 and authenticate the discovered external electronic device 320. In one embodiment, the external electronic device 320 may be registered with the server 310 to be associated with a user account. The electronic device 201 can monitor and control the external electronic device 320 registered in the server 310 using the user account.

In one embodiment, the electronic device 201 may be a personal electronic device, such as a smart phone, tablet, or wearable device, or an electronic device that includes a display and a user interface, such as a television or control console. In one embodiment, the electronic device 201 supports a security function (eg, security element 420) of a designated high security level and may perform encryption and/or decryption of data. In one embodiment, the external electronic device 320 may be configured not to support a required level of security function (e.g., a security element), and may provide encryption and/or decryption services through the security function of the electronic device 201. Available.

Referring to FIG. 4 , an electronic device (eg, electronic device 201) may include an application processor (AP) 410 and a security element (SE) 420. In one embodiment, the application processor 410 and the security element 420 may be included in at least one processor 220 of the electronic device 201. In one embodiment, the application processor 410 may execute an application (eg, a client application) capable of controlling at least one external electronic device 320. The application processor 410 may communicate with the external electronic device 320 through execution of the client application.

In one embodiment, the secure element 420 may be implemented as a system on chip that includes a secure storage area 422 (e.g., internal memory). In one embodiment, the secure storage area 422 may be a unique storage space included in the secure element 420. The security element 420 may perform attack security, secure key generation, and/or secure storage functions, such that even if the application processor 410 is hacked, the data therein (e.g., within the secure storage area 422) may be protected. It can provide a strong security mechanism to safely protect data.

In one embodiment, the security element 420 is at least EAL 6 or higher (EAL 6) among the seven evaluation assurance levels (EALs) defined to standardize the assurance level of information security products in the common criteria (CC). For example, a security level of EAL 6 augmented (EAL6+) may be provided. The security element 420 of EAL 6 or higher may provide a higher level of security functionality compared to a hardware security module (HSM) of EAL 4, a virtual private network (VPN) of EAL 3, or a trusted execution environment (TEE) of EAL 2. You can.

In one embodiment, the security element 420 generates a data encryption key (D_key) 424 to be used for encryption or decryption for the external electronic device 320, and sets the data encryption key 424 to a specified security level ( For example, it can be safely stored in the secure storage area 422 with EAL 6 or higher). The application processor 410 may transmit data requiring encryption or decryption of the external electronic device 320 and a request for encryption or decryption to the security element 420. The security element 420 encrypts or decrypts the data using the data encryption key 424 in response to the request, and then sends the resulting data (e.g., encrypted data or decrypted data) to the application processor 410. It can be provided to the external electronic device 320 through . The data encryption key 424 is used for encryption or decryption inside the security element 420, and is safely stored in the secure storage area 422 of the security element 420 without being leaked to the outside of the security element 420. It can be.

In one embodiment, the secure storage area 422 may further store key-related information (key_info) 426 to be used for secure communication with the external electronic device 320. In one embodiment, the key-related information 426 may include at least a secret key among the asymmetric key pair for the external electronic device 320 to use for server authentication. The security element 420 may generate the asymmetric key pair and provide one of the asymmetric key pair, for example, a public key, to the external electronic device 320. The external electronic device 320 can obtain authentication to use the cloud service with the server 310 using the public key. The key-related information 426 may further include the other one of the asymmetric key pair, for example, the public key. The public key may be included in the session key-related information 426 and safely stored in the secure storage area 422, or may be stored in another storage area of the electronic device 201.

In one embodiment, the external electronic device 320 may be registered with the electronic device 201 to initiate communication with the electronic device 201. In one embodiment, when the external electronic device 320 is first installed or booted (or powered on), or when the external electronic device 320 communicates with the electronic device 201 for the first time, the external electronic device 320 may be registered in the electronic device 201. In one embodiment, the registration procedure for the external electronic device 320 includes an operation by the electronic device 201 to authenticate (or identify) the external electronic device 320, and unique information (e.g., a serial number) of the external electronic device 320. An operation of storing a serial number (SN) or MAC (media access control) address) in a memory (e.g., memory 230), or security data (e.g., a session key ( It may include at least one of the operations of generating a data encryption key 428) and/or a data encryption key 424).

In one embodiment, when the external electronic device 320 is registered with the electronic device 201, the electronic device 201 generates a session key 428 for communication with the external electronic device 320 through the security element 420. can be created. In one embodiment, the session key 428 may be generated at the request of the external electronic device 320 every time the external electronic device 320 boots. In one embodiment, session key 428 may be used to ensure secure end-to-end communication between external electronic device 320 and secure element 420. In one embodiment, session key 428 may be stored within secure storage area 422 of secure element 420. The session key 428 may have a designated lifetime, and may be deleted (or deactivated) by the security element 420 when the lifetime has elapsed. In one embodiment, when the external electronic device 320 and/or the secure element 420 boots, the session key 428 stored in the secure storage area 422 of the secure element 420 may be deleted (or deactivated). .

In one embodiment, the application processor 410 may execute a client application to control the external electronic device 320. The application processor 410 may support communication between the external electronic device 320 and the security element 420. In one embodiment, the application processor 410 may receive data and a request for encryption or decryption (hereinafter referred to as encryption/decryption) from the external electronic device 320, and transmit the data and request to the security element 420. there is. In one embodiment, the application processor 410 sends a message (for example, a request message) received from the external electronic device 320 to an application protocol data unit (APDU) for communication between the external electronic device 320 and the security element 420. ) format and transmit it to the security element 420, or the APDU received from the security element 420 can be converted into a message in a format that the external electronic device 320 can understand and transmit it to the external electronic device 320. .

Referring to FIG. 5, an external electronic device (e.g., external electronic device 320) includes a processor 510, a communication interface 520, a memory 530, and a native function unit 540. can do. The unique function unit 540 is hardware and/or software that performs the unique function of the external electronic device 320 (for example, a television reception circuit, a motor control module of a washing machine, or a CCTV filming module) under the control of the processor 510. Can contain modules. In one embodiment, processor 510 may include processing circuitry that communicates with electronic device 201 (e.g., application processor 410) and/or server 310 through communication interface 520. In one embodiment, the communication interface 520 uses a communication method (e.g., the first network 298) such as at least one of Bluetooth, Wi-Fi, Wi-Fi direct, Z-wave, Zig-bee, or IrDA. You can communicate with the electronic device 201 using. In one embodiment, the communication interface 520 may communicate with the server 310 using a communication method such as at least one of Wi-Fi or a cellular network (eg, the second network 299).

In one embodiment, the processor 510 may register with the electronic device 201 by sending the authentication request through the communication interface 520 when it first communicates with the electronic device 201 after power-on or booting. In one embodiment, the processor 510 may request generation of a data encryption key (e.g., data encryption key 424) by transmitting an authentication request to the electronic device 201 through the communication interface 520.

In one embodiment, the processor 510 may transmit data requiring encryption and an encryption request to the electronic device 201, and in response, receive data encrypted by a data encryption key from the electronic device 201. You can receive it. In one embodiment, the processor 510 may transmit data requiring decryption and a decryption request to the electronic device 201, and may receive data decrypted using a data encryption key from the electronic device 201 in response. .

In one embodiment, processor 510 may share the same session key (e.g., session key 428) with electronic device 201 when registered with electronic device 201. In one embodiment, the processor 510 may encrypt a message containing data and an encryption/decryption request using a session key and transmit it to the electronic device 201. In one embodiment, the processor 510 may decrypt a message received from the electronic device 201 using a session key to obtain encrypted/decrypted data. In one embodiment, the session key may be stored in memory 530 (e.g., volatile memory) for a specified validity time, when the specified validity time elapses or when the external electronic device 320 is powered off or booted. It may be erased (or deactivated) from memory 530 (e.g., volatile memory).

FIG. 6 is a flowchart illustrating a procedure in which an electronic device provides an encryption service according to an embodiment. At least one of the operations described later may be executed by a processor (eg, processor 220) of the electronic device 201. According to embodiments, at least one of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 6 , in operation 605, the electronic device 201 (eg, processor 220) may receive an authentication request from the external electronic device 320. In one embodiment, the authentication request may include unique information (eg, serial number or MAC address) of the external electronic device 320. In one embodiment, the authentication request may include an indicator indicating that the external electronic device 320 requests encryption/decryption service by the security element 420. The electronic device 201 (eg, the processor 220) can register the external electronic device 320 with the electronic device 201 by storing the serial number.

In operation 610, the electronic device 201 (eg, the processor 220) may allocate a secure storage area (eg, the secure storage area 422) for the external electronic device 320. In one embodiment, the electronic device 201 (e.g., the processor 220) may allocate a secure storage area 422 within the secure element 420 that can be used exclusively for the external electronic device 320. In one embodiment, secure storage area 422 may be some storage space within the non-volatile memory of secure element 420. In one embodiment, secure element 420 may provide a security level of EAL 6 or higher for secure storage area 422. In one embodiment, the electronic device 201 (e.g., the processor 220) may execute

operations

610, 615, 620, and 645 in response to the indicator in the authentication request. In one embodiment, the electronic device 201 (e.g., processor 220) receives a user input (e.g., user input 910 of FIG. 9) that allows the external electronic device 320 to utilize the secure element 420. In response to receiving ),

operations

610, 615, 620, and 645 may be executed.

In operation 615, the electronic device 201 (e.g., processor 220) generates a data encryption key (e.g., data encryption key 424) for the external electronic device 320 and uses the data encryption key as the security key. It can be stored in the storage area 422. In operation 620, the electronic device 201 (e.g., the processor 220) may generate a session key (e.g., the session key 428) to be used for session communication with the external electronic device 320. The session key may be an encryption key used to encrypt messages on a communication session with the external electronic device 320. In one embodiment, operation 620 may include at least one of operation 625, operation 630, operation 635, or operation 640.

In operation 625, the electronic device 201 (e.g., the processor 220) generates first session key generation information (e.g., at least one random number) for device authentication of the external electronic device 320. A public key (including at least one of a public key (PK) or a certificate) may be transmitted to the external electronic device 320. In operation 630, the electronic device 201 (e.g., the processor 220) receives second session key generation information (e.g., at least one random number value, or at least one public key) from the external electronic device 320 that has successfully authenticated the device. includes at least one of the keys).

In operation 635, the electronic device 201 (eg, the processor 220) may generate a session key for session communication with the external electronic device 320 based on the second session key generation information. In one embodiment, the session key may be generated using a public key included in the second session key generation information, and may be verified by a random number value included in the second session key generation information. In one embodiment, the external electronic device 320 may generate and store the same session key based on the first session key generation information. In operation 640, the electronic device 201 (eg, the processor 220) may transmit session key verification information related to the session key to the external electronic device 320. In one embodiment, the session key verification information may include at least one random number encrypted by the session key. The external electronic device 320 may confirm that the external electronic device 320 shares the same session key as the electronic device 201 based on the session key verification information.

In operation 645, the electronic device 201 (e.g., processor 220) performs encryption and encryption based on the data encryption key in response to a request (e.g., encryption request or decryption request) from the external electronic device encrypted with the session key. /Or, a decryption service may be provided to the external electronic device 320. In one embodiment, the encryption service may include receiving data and encryption requests and transmitting encrypted data according to the procedure of FIG. 12. In one embodiment, the decryption service may include receiving data and a decryption request and transmitting the decrypted data according to the procedure of FIG. 13.

FIG. 7 is a flowchart illustrating a procedure in which an external electronic device provides an encryption service according to an embodiment. At least one of the operations described later may be executed by a processor (eg, processor 220) of the external electronic device 320. According to embodiments, at least one of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 7 , in operation 705, the external electronic device 320 (eg, processor 510) may transmit an authentication request to the electronic device 201. The authentication request may be transmitted when the external electronic device 320 is powered on or booted, or when the external electronic device 320 determines that encrypted communication is necessary, and unique information (e.g., For example, a serial number) may be included. In one embodiment, the authentication request may include an indicator indicating that the external electronic device 320 requests encryption/decryption service by the security element 420. In operation 710, the external electronic device 320 (eg, processor 510) may generate a session key to be used for session communication with the electronic device 201. In one embodiment, operation 710 may include at least one of operation 715, operation 720, operation 725, operation 730, operation 735, or operation 740. In one embodiment, operation 710 may include at

least operations

715, 730, and 735.

In operation 715, the external electronic device 320 (e.g., processor 510) receives first session key generation information (e.g., at least one random number) for device authentication of the external electronic device 320 from the electronic device 201. value, at least one public key, or a certificate). In operation 720, the external electronic device 320 (eg, processor 510) may transmit a verification request for device authentication of the external electronic device 320 to the server 310. In one embodiment, the verification request may include unique information (eg, serial number) for identifying the external electronic device 320. In operation 725, the external electronic device 320 (e.g., processor 510) receives a verification key from the server 310 and verifies the certificate in the first session key generation information using the verification key to successfully verify the device. You can.

In operation 730, the external electronic device 320 (eg, processor 510) may generate a session key using the public key in the first session key generation information. In operation 735, the external electronic device 320 (e.g., processor 510) generates second session key generation information (e.g., including at least one of at least one random number value or at least one public key). It can be transmitted to the device 201. In operation 740, the external electronic device 320 (e.g., processor 510) receives session key verification information (e.g., including at least one random number value) from the electronic device 201 and Based on this, it can be confirmed that the electronic device 201 shares the same session key as the external electronic device 320.

In operation 745, the external electronic device 320 (eg, processor 510) may use the encryption service and/or decryption service of the electronic device 201 based on the session key. In one embodiment, the encryption service may include sending data and encryption requests and receiving encrypted data according to the procedure of FIG. 12. In one embodiment, the decryption service may include transmitting data and a decryption request and receiving decrypted data according to the procedure of FIG. 13.

Figure 8 shows a signal flow diagram (sequence diagram) to explain a procedure for performing device authentication and session key generation according to an embodiment. At least some of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 8, in operation 802, the external electronic device 320 provides unique information (e.g., serial number (SN)) of the external electronic device 320 to the electronic device 201 (e.g., the application processor 410). ) can be transmitted. In one embodiment, the authentication request is made when the external electronic device 320 first initiates communication with the electronic device 201 (for example, when the external electronic device 320 is powered on or booted). It may be transmitted through a communication session established between the device 320 and the application processor 410. In one embodiment, the external electronic device 320 may transmit the authentication request to use the encryption/decryption service provided by the session element 420 of the electronic device 201.

In operation 804, the application processor 410 of the electronic device 201 may identify the external electronic device 320 using the serial number included in the authentication request and store the serial number. In one embodiment, the application processor 410 sends a message (e.g., an image and text of the external electronic device 320) indicating that the external electronic device 320 is registered based on the serial number to a display module (e.g., a display module). It can be output through module 260). The user can directly authenticate the external electronic device 320 by checking the message. In one embodiment, the application processor 410 may store the serial number in response to receiving a user input accepting registration of the external electronic device 320. In operation 804-1, the application processor 410 may transmit unique information for the external electronic device 320, including the serial number, to the server 310. Server 310 may store the serial number.

In operation 806, the application processor 410 may transmit an allocation request for the external electronic device 320 to the secure element 420. In one embodiment, the allocation request may include information (eg, serial number) identifying the external electronic device 320. In one embodiment, the application processor 410 may transmit the allocation request in response to a user input (e.g., user input 910 in FIG. 9) allowing the external electronic device 3200 to utilize the secure element 420. there is.

In operation 808, the security element 420 of the electronic device 201 allocates a unique secure storage area (e.g., secure storage area 422) for the external electronic device 320 within the internal memory in response to the allocation request. can do. In operation 810, the security element 420 generates a data encryption key (e.g., data encryption key 424) for the external electronic device 320 and stores the generated data encryption key in the secure storage area 422. You can. In one embodiment, the data encryption key may include an advanced encryption standard (AES) key used for data encryption/decryption. AES is a symmetric key algorithm that can be used equally for encryption and decryption, and the AES key can be used for both encryption and decryption.

In operation 812, the security element 420 may transmit first session key generation information for device authentication of the external electronic device 320 to the application processor 410. In one embodiment, the first session key creation information may be delivered in the format of an APDU. In one embodiment, the security element 420 includes a certificate ('CERT'), a key pair according to the elliptic curve key agreement algorithm (ECKA) (e.g., an ephemeral secret key (eSK) and an ephemeral public key (ePK)), and RSA ( Generating at least one of a key pair (e.g. a secret key (SK) and a public key (PK)) according to the Rivest / Shamir / Adleman asymmetric algorithm, or a first random number value ('rand') And, the digital signature ('Sign (rand||ePK)') including the first random number value and the ePK and the CERT may be encrypted by the SK to generate the first session key generation information. The first session key creation information may include an encrypted digital signature and an encrypted CERT ('Sign (rand||ePK) || CERT'). In operation 814, the application processor 410 may transmit the first session key creation information ('Sign (rand||ePK) || CERT') to the external electronic device 320.

In operation 816, the external electronic device 320 may transmit a verification request including unique information (eg, serial number) of the external electronic device 320 to the server 310. In one embodiment, the server 310 may verify the external electronic device 320 by confirming that the serial number obtained in operation 804-1 matches the serial number included in the unique information. In operation 818, the server 310 may transmit a verification key for the certificate to the external electronic device 320. In operation 820, the external electronic device 320 verifies that the certificate and the digital signature are normal using the verification key and generates a session key for session communication with the secure element 420. In one embodiment, the external electronic device 320 generates a key pair (e.g., eSK' and ePK') according to ECKA, and creates a session key based on eSK' and ePK obtained through the first session key generation information. ('SSK') (e.g. SSK = eSK' + ePK). In one embodiment, SSK can be created by appending or adding ePK to eSK'. In one embodiment, the SSK may be generated through a designated key derivation function with eSK' and ePK as input.

In operation 822, the external electronic device 320 may transmit second session key creation information to the application processor 410 of the electronic device 201. In one embodiment, the external electronic device 320 generates a second random number value ('rand2'), and combines the first random number value ('rand') obtained from the first session key generation information with the second random number value. Encrypted random number information ('Enc (SSK, rand || rand2)') can be generated by encryption using the session key. The external electronic device 320 may generate the second session key generation information including the encrypted random number information and the ePK'. In operation 824, the application processor 410 may convert the second session key creation information ('Enc (SSK, rand || rand2) || ePK') into an APDU format and transmit it to the security element 420.

In operation 826, the security element 420 may generate a session key (eg, session key 428) based on the second session key generation information. In one embodiment, the security element 420 may generate a session key ('SSK') based on ePK' and eSK included in the second session key generation information (for example, SSK = ePK' + eSK). . The security element 420 decrypts the encrypted random number information ('Enc (SSK, rand || rand2)') using the session key to obtain a first random number value (rand) and a second random number value (rand2). And, it can be confirmed that the first random number value is the same as the first random number value transmitted in operation 812. In operation 828, the security element 420 encrypts the second random number value with the session key to generate session key verification information ('Enc (SSK, rand2)') including the encrypted second random number value, The session key verification information may be transmitted to the application processor 410 in the format of an APDU. In operation 830, the application processor 410 may transmit the session key verification information ('Enc (SSK, rand2)') to the external electronic device 320.

In operation 832, the external electronic device 320 may confirm that the session key generated in operation 820 is the same as the session key generated in the security element 420 based on the session key verification information. In one embodiment, the external electronic device 320 decrypts the session key verification information using the session key to obtain the second random number value, and the second random number value is equal to the second random number value transmitted in operation 822. The session key can be verified by confirming that it is identical. Through the above operations, the security element 420 can store a data encryption key (for example, an AES key) for the external electronic device 320 in the secure storage area 422, and the security element 420 and the external electronic device 320 may share the same session key ('SSK').

Referring to FIG. 9, the electronic device 201 (e.g., the application processor 410) receives, for example, an authentication request in operation 802 from the external electronic device 320, and the external electronic device 320 uses the security element. (420) A message may be displayed asking permission to use (e.g., 'Do you want to allow IoT devices to utilize your SE?'). If a user input 910 allowing use of the security element 420 is received, the electronic device 201 (eg, the application processor 410) may proceed with operations following operation 806.

FIG. 10 is a flowchart illustrating a procedure in which an electronic device provides an encryption service according to an embodiment. At least one of the operations described later may be executed by a processor (eg, processor 220) of the electronic device 201. According to embodiments, at least one of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 10 , in operation 1005, the electronic device 201 (eg, processor 220) may receive a first encrypted message from the external electronic device 320 and proceed to operation 1010. In one embodiment, the first encryption message may be received together with at least one of unique information about the external electronic device 320 or information indicating that encryption has been applied. In operation 1010, the electronic device 201 (e.g., processor 220) performs the first encryption using a session key (e.g., session key 428) (e.g., the session key SSK generated in operation 826). By decoding the message, {data and encryption request} included in the first encrypted message can be obtained. In one embodiment, the data may include personal information (e.g., password) and/or personal data (e.g., video captured within a home network or door lock access record) for which the external electronic device 320 requests encryption. You can.

In operation 1015, the electronic device 201 (e.g., processor 220) retrieves a data encryption key (e.g., data encryption key 424) stored in the secure storage area 422 within the secure element 420 (e.g. The data may be encrypted using the AES key generated in operation 810 to generate encrypted data. In operation 1020, the electronic device 201 (eg, processor 220) may encrypt the encrypted data using a session key to generate a second encrypted message. In operation 1025, the electronic device 201 (eg, processor 220) may transmit the second encrypted message to the external electronic device 320.

FIG. 11 is a flowchart illustrating a procedure in which an external electronic device uses an encryption service according to an embodiment. At least one of the operations described later may be executed by a processor (eg, processor 510) of the external electronic device 320. According to embodiments, at least one of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 11 , in operation 1105, the external electronic device 320 (eg, processor 510) may identify that data requiring encryption exists and proceed to operation 1110. In one embodiment, the data may include personal information or personal data such as passwords. In one embodiment, when the external electronic device 320 (for example, the processor 510) receives a newly set password for controlling the external electronic device 320 from the user, it proceeds to operation 1110 to encrypt and store the password. You can proceed. In one embodiment, the external electronic device 320 (e.g., processor 510) proceeds to operation 1110 to encrypt and store personal data such as captured image data or door lock access records according to a user request or a specified cycle. You can.

In operation 1110, the external electronic device 320 (e.g., processor 510) sends data requiring encryption (e.g., the password or the image data) and an encryption request with a session key (e.g., session key 428). The first encrypted message may be generated by encryption using (for example, the session key SSK generated in operation 820). The first encrypted message may include {data and encryption request} encrypted with the session key. In operation 1115, the external electronic device 320 (eg, processor 510) may transmit the first encrypted message to the electronic device 201. In one embodiment, the first encrypted message may be transmitted along with at least one of unique information about the external electronic device 320 or information indicating that encryption has been applied.

In operation 1120, the external electronic device 320 (eg, processor 510) may receive a second encrypted message from the electronic device 201. In operation 1125, the external electronic device 320 (e.g., processor 510) decrypts the second encrypted message using the session key to obtain {encrypted data} included in the second encrypted message. You can. The second encrypted message may include data encrypted by a data encryption key (e.g., data encryption key 424) (e.g., the AES key generated in operation 810), corresponding to the data transmitted in operation 1115. You can. In one embodiment, the second encrypted message may be received in response to the first encrypted message.

In one embodiment, the external electronic device 320 (e.g., processor 510) may recognize that the second encrypted message includes encrypted data corresponding to the original data transmitted through the first encrypted message. . The obtained encrypted data may be safely stored in the memory (eg, memory 530) of the external electronic device 320. In one embodiment, the external electronic device 320 (eg, processor 510) may store the encrypted data and delete the original data.

Figure 12 shows a signal flow diagram to explain a procedure for providing encryption services according to an embodiment. At least some of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 12, in operation 1202, the external electronic device 320 may detect that data requiring encryption (eg, password or personal data) is generated. In one embodiment, the external electronic device 320 may determine that encryption of data is necessary periodically, when a specified condition is satisfied, or in response to a user input, and proceed to operation 1204. In operation 1204, the external electronic device 320 sends the data requiring encryption and an encryption request related to the data using a session key (e.g., session key 428) (e.g., the session key SSK generated in operation 820). The first encrypted message ('Enc (SSK, Data || Encrypt Request)') can be generated by encryption. In operation 1206, the external electronic device 320 may transmit the first encryption message ('Enc (SSK, Data || Encrypt Request)') to the application processor 410 of the electronic device 201. In one embodiment, the first encrypted message may be transmitted along with unique information of the external electronic device 320.

In operation 1208, the application processor 410 may convert the first encrypted message (and unique information) into an APDU format and transmit it to the security element 420. In operation 1210, the security element 420 uses a pre-stored session key for the external electronic device 320 (e.g., the session key SSK generated in operation 826) (e.g., the session key 428) to By decoding the encrypted message, {data and encryption request} included in the first encrypted message can be obtained. In operation 1212, the secure element 420 generates a data encryption key (e.g., data encryption key 424) stored in the secure storage area 422 (e.g., the AES key generated in operation 810) in response to the encryption request. By encrypting the data, encrypted data ('Enc (AES, Data)') can be created. In operation 1214, the security element 420 may encrypt the encrypted data using a session key to generate a second encrypted message ('Enc (SSK, Enc (AES, Data))'. In operation 1216, the security element 420 may transmit the second encrypted message to the application processor 410 in the format of an APDU. In operation 1218, the application processor 410 may transmit the second encrypted message to the external electronic device 320.

In operation 1220, the external electronic device 320 can obtain encrypted data ('Enc (AES, Data)') included in the second encrypted message by decrypting the second encrypted message using the session key. there is. The external electronic device 320 may store the obtained encrypted data in the memory 530. In one embodiment, the external electronic device 320 (eg, processor 510) may store the encrypted data and delete the original data transmitted in operation 1206.

In one embodiment, the procedure for providing a decryption service by the electronic device 201 to the external electronic device 320 may be similar to FIG. 10, and the external electronic device 320 uses the decryption service through the electronic device 201. The procedure may be similar to Figure 11. For a detailed description of the operations performed by the electronic device 201 and the external electronic device 320, refer to FIG. 13 below.

Figure 13 shows a signal flow diagram to explain a procedure for providing a decryption service according to an embodiment. At least some of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 13, in operation 1302, the external electronic device 320 may detect that decryption of the encrypted data ('E(D)') is necessary. In one embodiment, the external electronic device 320 may proceed to operation 1304 to use the encrypted data (for example, to confirm a password or play video data). In operation 1304, the external electronic device 320 encrypts the encrypted data and the decryption request related to the encrypted data using a session key (e.g., session key 428) (e.g., the session key SSK generated in operation 820). Thus, the first encrypted message ('Enc (SSK, E(D) || Decrypt Request)') can be generated. In operation 1306, the external electronic device 320 may transmit the first encryption message ('Enc (SSK, E(D) || Decrypt Request)') to the application processor 410 of the electronic device 201. In one embodiment, the first encrypted message may be transmitted along with unique information of the external electronic device 320.

In operation 1308, the application processor 410 may transmit the first encrypted message (and unique information) to the security element 420 in the format of an APDU. In operation 1310, the security element 420 uses a pre-stored session key for the external electronic device 320 (e.g., the session key SSK generated in operation 826) (e.g., the session key 428) to By decoding the encrypted message, {encrypted data and decryption request} included in the first encrypted message can be obtained. In operation 1312, the secure element 420 generates a data encryption key (e.g., data encryption key 424) stored in the secure storage area 422 (e.g., the AES key generated in operation 810) in response to the decryption request. Original data ('Data') can be generated by decrypting the encrypted data using . In operation 1314, the security element 420 may encrypt the original data using a session key to generate a second encrypted message ('Enc (SSK, Data)'). In operation 1316, the security element 420 may transmit the second encrypted message to the application processor 410 in the format of an APDU. In operation 1318, the application processor 410 may transmit the second encrypted message to the external electronic device 320.

In operation 1320, the external electronic device 320 can obtain original data ('Data') included in the second encrypted message by decrypting the second encrypted message using the session key. The external electronic device 320 may at least temporarily store the acquired original data in the memory 530 or use it, for example, to confirm a password or play an image. In one embodiment, the external electronic device 320 (eg, processor 510) may delete the original data for security purposes after using the original data.

Referring to FIG. 14, the external electronic device 320 may receive a password 1410 set for controlling the external electronic device 320 from the user. The password 1410 may include a string entered by the user (for example, "FDF778523...") along with the string "PASSWORD", and therefore there is a risk of it being stolen by an attacker. The external electronic device 320 may transmit the password 1410 along with an encryption request to the electronic device 201 and receive the encrypted password 1420 as a corresponding response. The encrypted password 1420 is an encrypted string generated using a data encryption key (e.g., data encryption key 424) (e.g., an AES key) by the security element 420 of the electronic device 201 ( For example, it may include "0008E0A..."), and the data encryption key is not leaked outside of the security element 420. Even if an attacker steals the encrypted password (1420), the original string (for example, the password (1410)) cannot be known. The external electronic device 320 may store the encrypted password 1420 and delete the original password 1410.

In one embodiment, when decryption of the encrypted password 1420 is required to authenticate a user who wishes to control the external electronic device 320, the external electronic device 320 sends the encrypted password 1420 electronically along with a decryption request. It can be transmitted to the device 201, and the original password 1410 decrypted using the data encryption key by the security element 420 can be received in response. After authenticating the user using the original password 1410, the external electronic device 320 may delete the original password 1410 and continue to store only the encrypted password 1420.

Referring to FIG. 15, the external electronic device 320 can capture images within the home network through a security camera and generate image data 1510. According to a designated period or user request, the external electronic device 320 may transmit the video data 1510 to the electronic device 201 along with an encryption request, and receive encrypted video data 1520 in response. there is. Encrypted image data 1520 may be generated by the security element 420 of the electronic device 201 using a data encryption key (eg, data encryption key 424) (eg, AES key). The external electronic device 320 may store the encrypted image data 1520 and delete the original image data 1510.

In one embodiment, encrypted video data 1520 cannot be played normally without decryption. When a user requests playback of encrypted video data 1520, the external electronic device 320 transmits the encrypted video data 1520 to the electronic device 201 along with a decryption request, and sends a security element in response. Original image data 1510 decrypted using a data encryption key can be received at 420. The external electronic device 320 can play the original video data 1510, delete the original video data 1510 after playback is completed or a specified time after playback is completed, and continue to only encrypt the video data 1520. You can save it.

Figure 16 shows a signal flow diagram for explaining a procedure for updating a session key according to an embodiment. At least some of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 16, in operation 1602, the external electronic device 320 generates a session key (e.g., session key 428) for the electronic device 201 (e.g., the session key generated in operation 820). It may be determined that a need exists and proceed to operation 1604. In one embodiment, the external electronic device 320 starts counting the specified validity time when generating each session key, deletes the previous session key when the validity time elapses, and then operates 1604 to generate a new session key. You can proceed with . In one embodiment, each session key may be stored in a volatile memory (not shown) of the external electronic device 320, and the external electronic device 320 performs operation 1604 to generate a new session key when the external electronic device 320 is powered on or booted. You can proceed with .

In operation 1604, the external electronic device 320 transmits to the electronic device 201 (e.g., the application processor 410) a session key request containing unique information (e.g., a serial number) of the external electronic device 320. You can. In operation 1606, the application processor 410 determines that the external electronic device 320 has already been registered based on the unique information (for example, the data encryption key of the external electronic device 320 is stored in the security element 420). ), the external electronic device 320 can be authenticated.

In operation 1608, the application processor 410 may transmit a session key request for the external electronic device 320 to the secure element 420. In one embodiment, the allocation request may include information (eg, serial number) identifying the external electronic device 320. In operation 1610, the security element 420 may generate first session key generation information for device authentication of the external electronic device 320. In one embodiment, the secure element 420 is configured to include a certificate ('CERT'), a key pair according to ECKA (e.g. eSK and ePK), a key pair according to RSA (e.g. SK and PK), or a first random number value. ('rand'), and encrypt the digital signature ('Sign (rand||ePK)') including the first random number value and the ePK and the CERT by the SK to establish the first session. Key creation information can be generated. The first session key creation information may include an encrypted digital signature and an encrypted CERT ('Sign (rand||ePK) || CERT'). In operation 1612, the security element 420 may transmit the first session key creation information ('Sign (rand||ePK) || CERT') to the application processor 410 in the format of an APDU. In operation 1614, the application processor 410 may transmit the first session key creation information ('Sign (rand||ePK) || CERT') to the external electronic device 320.

In operation 1616, the external electronic device 320 may transmit a verification request including unique information (eg, serial number) of the external electronic device 320 to the server 310. In operation 1618, the server 310 identifies and verifies the external electronic device 320 using the unique information and transmits a verification key for the certificate to the external electronic device 320. In operation 1620, the external electronic device 320 may use the verification key to verify that the certificate and the digital signature are normal and generate a session key for session communication with the secure element 420. In one embodiment, the external electronic device 320 generates a key pair (e.g., eSK' and ePK') according to ECKA, and creates a session key based on eSK' and ePK obtained through the first session key generation information. ('SSK') (e.g. SSK = eSK' + ePK). In one embodiment, the session key may be stored in the memory 530 (eg, volatile memory) of the external electronic device 320 for a designated validity period.

In operation 1622, the external electronic device 320 may transmit second session key creation information to the application processor 410 of the electronic device 201. In one embodiment, the external electronic device 320 generates a second random number value ('rand2'), and combines the first random number value ('rand') obtained from the first session key generation information with the second random number value. Encrypted random number information ('Enc (SSK, rand || rand2)') can be generated by encryption using the session key. The external electronic device 320 may generate the second session key generation information including the encrypted random number information and the ePK'. In operation 1624, the application processor 410 may convert the second session key creation information ('Enc (SSK, rand || rand2) || ePK') into an APDU format and transmit it to the security element 420.

In operation 1626, the security element 420 may generate a session key (eg, session key 428) based on the second session key generation information. In one embodiment, the security element 420 may generate a session key based on ePK' and eSK included in the second session key generation information (for example, SSK=ePK'+eSK). The session key may be stored in a storage area (eg, secure storage area 422) of the electronic device 201 for a designated validity period. The security element 420 may provide an encryption and/or decryption service to the external electronic device 320 using the session key, for example, as in the procedures of FIGS. 12 and/or 13 .

FIG. 17 is a signal flow diagram illustrating a procedure for generating an asymmetric key for server authentication according to an embodiment. At least some of the operations described below may be omitted, modified, or changed in order.

Referring to FIG. 17, in operation 1702, the external electronic device 320 may determine to generate an asymmetric key to be used to obtain server authentication and proceed to operation 1704. In one embodiment, a server (e.g., server 310) may provide a cloud service for an external electronic device 320, and the external electronic device 320 may use an asymmetric key to obtain authentication of the server 310. can be used.

In operation 1704, the external electronic device 320 encrypts the asymmetric key request ('Asym key Request') by a session key (e.g., session key 428) (e.g., the session key SSK generated in operation 820) The first encrypted message ('Enc (SSK, Asym key Request)') can be generated. In operation 1706, the external electronic device 320 may transmit the first encrypted message ('Enc (SSK, Asym key Request)') to the application processor 410 of the electronic device 201. In one embodiment, the first encrypted message may be transmitted along with unique information of the external electronic device 320.

In operation 1708, the application processor 410 may convert the first encrypted message (and unique information) into an APDU format and transmit it to the security element 420. In operation 1710, the security element 420 uses a pre-stored session key for the external electronic device 320 (e.g., the session key SSK generated in operation 826) (e.g., the session key 428) to By decoding the encrypted message, {asymmetric key request} included in the first encrypted message can be obtained. In operation 1712, the secure element 420 may generate an asymmetric key pair (e.g., SK and PK) in response to the asymmetric key request. In one embodiment, the security element 420 may generate the asymmetric key pair in a manner according to open secure socket layer (SSL).

In operation 1714, the security element 420 may store the SK in the secure storage area 422 and encrypt the PK with the session key to generate a second encrypted message ('Enc (SSK, PK)'). In operation 1716, the security element 420 may transmit the second encrypted message to the application processor 410 in the format of an APDU. In operation 1718, the application processor 410 may transmit the second encrypted message to the external electronic device 320.

In operation 1720, the external electronic device 320 can obtain the PK included in the second encrypted message by decrypting the second encrypted message using the session key. In operation 1722, the external electronic device 320 may perform an authentication procedure with the server 310 based on the PK. The server 310 may generate the same asymmetric key pair using the same key generation algorithm used in the external electronic device 320 and authenticate the external electronic device 320 using the SK of the asymmetric key pair. there is.

In one embodiment, the authentication procedure involves the external electronic device 320 transmitting the PK to the server 310 to create a cloud registry in the server 310 and storing the device information of the external electronic device 320 and the PK in the cloud. An operation of storing in the registry, and an operation of the external electronic device 320 generating a web token (e.g., JWT (JSON Web token)) for device authentication, signing the web token with a private key, and transmitting it to the server 310. and, the server 310 confirming that the external electronic device 320 has been authenticated by verifying the signed web token based on the PK stored in the cloud registry.

Through the procedure of FIG. 17 , an asymmetric key (eg, SK and PK) required for authentication of the external electronic device 320 can be generated in the security element 420 and the SK can be safely stored.

The disclosed embodiments utilize the security element 420 mounted on the electronic device 201 for an external electronic device not equipped with a security element (e.g., the external electronic device 320) to achieve high security level encryption/ Decryption service can be provided. For example, the data encryption key used to safely protect data and prevent leakage of personal information in an external electronic device 320 that can be implemented as an IoT device in a home network is stored in the security element 420 of the electronic device 201. It can be used and stored safely.

The electronic device 201 according to one embodiment may include a communication circuit 290 and at least one processor 220 operatively connected to the communication circuit. The at least one processor may be configured to receive an authentication request including unique information from an external electronic device 320 that does not support a security function through the communication circuit. The at least one processor may be configured to allocate a secure storage area for the external electronic device based on the unique information. The at least one processor may be configured to generate a data encryption key for the external electronic device and store it in the secure storage area. The at least one processor may be configured to generate a session key for session communication with the external electronic device. The at least one processor may be configured to provide an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key.

In one embodiment, the session key has a designated validity time and may be stored in volatile memory within the electronic device.

In one embodiment, the at least one processor includes an application processor (AP) 410 that communicates with the external electronic device, and the secure storage that communicates with the external electronic device through the application processor and provides a specified security level. area, and may include a security element (SE) 420 configured to generate the data encryption key for the external electronic device and store the data encryption key within the secure storage area.

In one embodiment, the at least one processor may be configured to receive a first encryption message including data and an encryption request from the external electronic device through the communication circuit. The at least one processor may be configured to obtain the data and the encryption request by decrypting the first encrypted message using the session key by the security element. The at least one processor may be configured to generate encrypted data by encrypting the data using the data encryption key by the security element. The at least one processor may be configured to encrypt the encrypted data using the session key by the security element to generate a second encrypted message including the encrypted data. The at least one processor may be configured to transmit the second encrypted message to the external electronic device through the communication circuit.

In one embodiment, the at least one processor may be configured to generate at least one of a certificate, a first key pair, a second key pair, or a first random number value for device authentication of the external electronic device. The at least one processor may be configured to encrypt the digital signature including the random value and the first public key of the first key pair and the certificate with a private key of the second key pair. The at least one processor may be configured to transmit first session key generation information including the encrypted digital signature and the encrypted certificate to the external electronic device. The at least one processor may be configured to receive second session key generation information including encrypted random number information and a second public key from the external electronic device. The at least one processor may be configured to generate the session key based on the private key of the first key pair and the second public key. The at least one processor may be configured to obtain the first random number value and the second random number value by decrypting the encrypted random number information using the session key. The at least one processor may be configured to encrypt the second random number value using the session key. The at least one processor may be configured to transmit session key verification information including the encrypted second random number value to the external electronic device.

In one embodiment, the at least one processor may be configured to receive a session key request from the external electronic device. The at least one processor may be configured to generate a new session key in response to the session key request.

In one embodiment, the at least one processor may be configured to receive a first encryption message including an asymmetric key request from the external electronic device. The at least one processor may be configured to obtain the asymmetric key request by decrypting the first encrypted message using the session key. The at least one processor may be configured to generate an asymmetric key pair including a private key and a public key for server authentication in response to the asymmetric key request. The at least one processor may be configured to generate a second encrypted message by encrypting the public key with the session key. The at least one processor may be configured to transmit the second encrypted message to the external electronic device.

The electronic device 320 according to one embodiment may include a communication interface 520 and at least one processor 510 operatively connected to the communication interface. The at least one processor may be configured to transmit an authentication request including unique information to an external electronic device 201 supporting a security function through the communication interface. The at least one processor may be configured to receive first session key creation information from the external electronic device. The at least one processor may be configured to generate a session key for session communication with the external electronic device based on the first session key generation information. The at least one processor may be configured to transmit second session key generation information for verification of the session key to the external electronic device. The at least one processor may be configured to use an encryption and/or decryption service provided by the external electronic device based on the session key.

In one embodiment, the at least one processor may be configured to detect the occurrence of data requiring encryption. The at least one processor may be configured to generate a first encrypted message by encrypting the data and the encryption request using the session key. The at least one processor may be configured to transmit the first encrypted message to the external electronic device through the communication interface. The at least one processor may be configured to receive a second encrypted message from the external electronic device. The at least one processor may be configured to decrypt the second encrypted message using the session key to obtain encrypted data corresponding to the data.

A method of operating the electronic device 201 according to an embodiment may include an operation 605 of receiving an authentication request including unique information from an external electronic device 320 that does not support the security function. The method may include an operation 615 of allocating a secure storage area for the external electronic device based on the unique information. The method may include an operation 615 of generating a data encryption key for the external electronic device and storing it in the secure storage area. The method may include an operation 620 of generating a session key for session communication with the external electronic device. The method may include an operation 645 of providing an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key.

In one embodiment, the electronic device includes an application processor (AP) that communicates with the external electronic device, and the secure storage area that communicates with the external electronic device through the application processor and provides a specified security level, and a security element (SE) configured to generate the data encryption key for the external electronic device and store the data encryption key in the secure storage area.

In one embodiment, the operation of providing the encryption service includes receiving a first encryption message including data and an encryption request from the external electronic device (1005), and using the session key by the security element to An operation (1010) of decrypting a first encryption message to obtain the data and the encryption request, and an operation (1015) of encrypting the data using the data encryption key by the security element to generate encrypted data, An operation of encrypting the encrypted data using the session key by the security element to generate a second encrypted message including encrypted data (1020), and transmitting the second encrypted message to the external electronic device ( 1025).

In one embodiment, the operation 620 of generating the session key includes generating at least one of a certificate for device authentication of the external electronic device, a first key pair, a second key pair, or a first random number value; , encrypting the digital signature including the random value and the first public key of the first key pair and the certificate with the private key of the second key pair, and encrypting the encrypted digital signature and the encrypted certificate. Transmitting first session key generation information including encrypted random number information and a second public key from the external electronic device; Generating the session key based on the secret key of one key pair and the second public key, and obtaining the first random number value and the second random number value by decrypting the encrypted random number information using the session key. It may include an operation of encrypting the second random number value using the session key, and an operation of transmitting session key verification information including the encrypted second random number value to the external electronic device.

In one embodiment, the method may include

operations

1604 and 1608 of receiving a session key request from the external electronic device. The method may include an operation 1610 of generating a new session key in response to the session key request.

In one embodiment, the method may include

operations

1706 and 1708 of receiving a first encryption message including an asymmetric key request from the external electronic device. The method may include an operation 1710 of obtaining the asymmetric key request by decrypting the first encrypted message using the session key. The method may include an operation 1712 of generating an asymmetric key pair including a private key and a public key for server authentication in response to the asymmetric key request. The method may include an operation 1714 of encrypting the public key with the session key to generate a second encrypted message. The method may include

operations

1716 and 1718 of transmitting the second encrypted message to the external electronic device.

A method of operating the electronic device 320 according to an embodiment may include an operation 705 of transmitting an authentication request including unique information to an external electronic device 201 that supports a security function. The method may include an operation 715 of receiving first session key creation information from the external electronic device. The method may include an operation 730 of generating a session key for session communication with the external electronic device based on the first session key generation information. The method may include an operation 735 of transmitting second session key generation information for verification of the session key to the external electronic device. The method may include an operation 745 of using an encryption and/or decryption service provided by the external electronic device based on the session key.

In one embodiment, the operation of using the encryption service includes an operation of detecting the occurrence of data requiring encryption (1105), and an operation of generating a first encryption message by encrypting the data and the encryption request using the session key (1110). ), an operation 1115 of transmitting the first encrypted message to the external electronic device, an operation 1120 of receiving a second encrypted message from the external electronic device, and the second encryption using the session key. It may include an operation 1125 of decrypting the message and obtaining encrypted data corresponding to the data.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or replacements of the embodiments. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” When mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

The term “module” used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used as A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document are one or more instructions stored in a storage medium (e.g., built-in memory 236 or external memory 238) that can be read by a machine (e.g., electronic device 201). It may be implemented as software (e.g., program 240) including these. For example, a processor (e.g., processor 220) of a device (e.g., electronic device 201) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, methods according to various embodiments disclosed in this document may be provided and included in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or via an application store (e.g. Play Store ^TM ) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

Claims

In the electronic device 201,

communication circuit 290; and

At least one processor 220 operatively connected to the communication circuit, the at least one processor comprising:

Receiving an authentication request containing unique information through the communication circuit from an external electronic device 320 that does not support the security function,

Allocating a secure storage area for the external electronic device based on the unique information,

Generate a data encryption key for the external electronic device and store it in the secure storage area,

Generate a session key for session communication with the external electronic device,

An electronic device configured to provide an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key.
The method of claim 1, wherein the session key is:

An electronic device having a specified validity time and being stored in a volatile memory within the electronic device.
The method of claim 1 or 2, wherein the at least one processor:

an application processor (AP) 410 that communicates with the external electronic device;

Communicates with the external electronic device through the application processor, includes the secure storage area providing a specified level of security, generates the data encryption key for the external electronic device, and stores the data encryption key within the secure storage area. An electronic device comprising a security element (SE) 420 configured to store.
The method of claim 3, wherein the at least one processor:

Receiving a first encrypted message containing data and an encryption request from the external electronic device through the communication circuit,

Decrypt the first encrypted message using the session key by the secure element to obtain the data and the encryption request,

Encrypting the data using the data encryption key by the security element to generate encrypted data,

Encrypting the encrypted data using the session key by the security element to generate a second encrypted message containing the encrypted data,

An electronic device configured to transmit the second encrypted message to the external electronic device through the communication circuit.
The method of any one of claims 1 to 4, wherein the at least one processor:

Generate at least one of a certificate, a first key pair, a second key pair, or a first random number value for device authentication of the external electronic device,

encrypting the digital signature including the random value and the first public key of the first key pair and the certificate with the private key of the second key pair;

Transmitting first session key creation information including the encrypted digital signature and the encrypted certificate to the external electronic device,

Receive second session key generation information including encrypted random number information and a second public key from the external electronic device,

Generate the session key based on the private key of the first key pair and the second public key,

Obtaining the first random number value and the second random number value by decrypting the encrypted random number information using the session key,

Encrypting the second random number value using the session key,

An electronic device configured to transmit session key verification information including the encrypted second random number value to the external electronic device.
The method of any one of claims 1 to 5, wherein the at least one processor:

Receive a session key request from the external electronic device,

An electronic device configured to generate a new session key in response to the session key request.
The method of any one of claims 1 to 6, wherein the at least one processor:

Receiving a first encryption message including an asymmetric key request from the external electronic device,

Decrypt the first encrypted message using the session key to obtain the asymmetric key request,

In response to the asymmetric key request, generate an asymmetric key pair including a secret key and a public key for server authentication,

Encrypting the public key with the session key to generate a second encrypted message,

An electronic device configured to transmit the second encrypted message to the external electronic device.
In the electronic device 320,

communication interface 520; and

At least one processor 510 operatively connected to the communication interface, the at least one processor comprising:

Transmitting an authentication request containing unique information to an external electronic device 201 supporting a security function through the communication interface,

Receive first session key creation information from the external electronic device,

Generating a session key for session communication with the external electronic device based on the first session key generation information,

Transmitting second session key creation information for verification of the session key to the external electronic device,

An electronic device configured to use encryption and/or decryption services provided by the external electronic device based on the session key.
The method of claim 8, wherein the session key is:

An electronic device having a specified validity time and being stored in a volatile memory within the electronic device.
The method of claim 8 or 9, wherein the at least one processor:

Detect the occurrence of data requiring encryption,

Encrypting the data and encryption request using the session key to generate a first encrypted message,

Transmitting the first encrypted message to the external electronic device through the communication interface,

Receiving a second encrypted message from the external electronic device,

An electronic device configured to obtain encrypted data corresponding to the data by decrypting the second encrypted message using the session key.
In the method of operating the electronic device 201,

An operation 605 of receiving an authentication request containing unique information from an external electronic device 320 that does not support the security function;

An operation 615 of allocating a secure storage area for the external electronic device based on the unique information;

An operation 615 of generating a data encryption key for the external electronic device and storing it in the secure storage area;

An operation 620 of generating a session key for session communication with the external electronic device;

A method comprising providing an encryption and/or decryption service based on the data encryption key to the external electronic device in response to a request from the external electronic device encrypted with the session key (645).
The method of claim 11, wherein the session key is:

A method having a specified validity time and being stored in a volatile memory within the electronic device.
The electronic device of claim 11 or 12, wherein:

an application processor (AP) 410 that communicates with the external electronic device;

Communicates with the external electronic device through the application processor, includes the secure storage area providing a specified level of security, generates the data encryption key for the external electronic device, and stores the data encryption key within the secure storage area. A method comprising a security element (SE) 420 configured to store.
The method of claim 13, wherein the operation of providing the encryption service includes:

An operation (1005) of receiving a first encrypted message including data and an encryption request from the external electronic device;

An operation (1010) of decrypting the first encrypted message by the security element using the session key to obtain the data and the encryption request;

An operation (1015) of encrypting the data by the security element using the data encryption key to generate encrypted data;

An operation (1020) of encrypting the encrypted data using the session key by the security element to generate a second encrypted message including the encrypted data;

A method comprising an operation (1025) of transmitting the second encrypted message to the external electronic device.
In the method of operating the electronic device 320,

An operation 705 of transmitting an authentication request including unique information to an external electronic device 201 supporting a security function;

An operation 715 of receiving first session key creation information from the external electronic device;

An operation 730 of generating a session key for session communication with the external electronic device based on the first session key generation information;

An operation 735 of transmitting second session key creation information for verification of the session key to the external electronic device;

A method comprising using an encryption and/or decryption service provided by the external electronic device based on the session key (745).