TWI672612B - Wearable device,method of generating encryption key and non-transitory computer-readable recording medium - Google Patents

Abstract

A wearable device includes a user information obtainer configured to Obtaining user information; a controller configured to selectively generate an encoding key for encoding content of an external device in response to the user being authenticated based on the user information; and a communicator configured to transmit the encoding Key to external device.

Description

Wearable device, method for generating encoding key, and non-transitory Current computer-readable recording media

This application claims Korean Patent Application No. 10-2014-0098478 filed on July 31, 2014, Korean Patent Application No. 10-2015-0002023 filed on January 7, 2015, and filed on February 17, 2015 The Korean Intellectual Property Office has applied for priority of Korean Patent Application No. 10-2015-0024018, the disclosure of which is incorporated herein by reference in its entirety.

The apparatus and method according to one or more exemplary embodiments relate to a method and apparatus for encoding or decoding content.

Important data related to the privacy of the user can be stored in the content of the device, and there is an increasing need for protecting the privacy of the user. Therefore, techniques for encoding and decoding content have been developed.

However, since a user must execute a program for encoding or decoding content independently of other programs related to the content, there is a growing need for a simplified content encoding program and a content decoding program.

One or more exemplary embodiments may provide a method and apparatus for encoding or decoding content.

One or more exemplary embodiments may also provide a non-transitory computer-readable recording medium having recorded thereon a program for performing the method by using a computer.

Additional aspects will be explained in part in the following description, and part will be apparent from the description, or may be learned through the exemplary embodiments presented in practice.

According to an aspect of the exemplary embodiment, the wearable device includes: a user information obtainer configured to obtain user information; and a controller configured to select in response to the user being identified based on the user information Generating an encoding key for encoding the content of the external device; and a communicator configured to transmit the encoding key to the external device.

The controller may be further configured to calculate a distance between the wearable device and an external device, and in response to determining that the distance is equal to or less than a predetermined distance, the controller may generate an encoding key.

The communicator may be further configured to receive a notification from the external device indicating that the content is stored in the external device, and the controller may be further configured to generate an encoding key in response to the notification being received.

The communicator may be configured to receive a notification from an external device indicating that a program for executing content is executed in the external device, and the controller may be further configured to generate an encoding key in response to the notification being received.

In response to the user being authenticated, the controller may be configured to determine whether the user is allowed to access the external device.

The encoding key may include an encoding key for a symmetric key algorithm, or may include an encoding key for an asymmetric key algorithm.

User information can include biological information about the user.

The biometric information may include information about one of a user's fingerprint, iris, retina, vein, skeletal portion, or face.

User information can include user account information.

The wearable device may further include a memory configured to store the encoding key.

According to an aspect of another exemplary embodiment, a method for generating a coding key (the method is performed by a wearable device) includes the following operations: obtaining user information; identifying a user of the wearable device based on the user information ; In response to a user selectively generating an encoding key for encoding content in the external device by authenticating; and transmitting the encoding key to the external device.

The method may further include an operation of calculating a distance between the wearable device and an external device, and the generated operation may be performed when the distance is equal to or less than a predetermined distance.

The method may further include an operation of receiving a notification indicating that the content is stored in the external device from the external device, and performing the generated execution in response to receiving the notification.

The method may further include an operation of receiving a notification from the external device indicating that the program for executing the content is executed in the external device, and may execute the operation generated by the execution in response to receiving the notification.

The method may further include an operation of determining whether to allow the user to access the external device in response to the user being authenticated by authentication.

The encoding key can contain the encoding key used for the symmetric key algorithm, or Contains the encoding key used in the asymmetric key algorithm.

User information can include biological information about the user.

The biometric information may include information about one of a user's fingerprint, iris, retina, vein, skeletal portion, or face.

User information can include user account information.

According to an aspect of another exemplary embodiment, the non-transitory computer-readable recording medium includes a recording program for executing a method by using a computer.

10‧‧‧ Wearable

11, 5370‧‧‧Memory

20‧‧‧ users

30‧‧‧External device

31, 32‧‧‧screen

310, 320, 330, 410, 420, 430, 440, 450, 460, 470, 480, 490, 510, 520, 810, 820, 830, 910, 920, 930, 1410, 1420, 1430, 1610, 1620, 1630, 1720, 1740, 1810, 1820, 1830, 1840, 1920, 1930, 2010, 2020, 2030, 2040, 2050, 2060, 2070, 2080, 2090, 2095, 2120, 2140, 2210, 2211, 2220, 2221 2230, 2231, 2240, 2241, 2250, 2251, 2260, 2261, 2270, 2280, 2290, 2295, 2321, 2330, 2350, 2351, 2361, 2410, 2420, 2810, 2820, 2830, 2840, 2850, 2860, 2910, 2920, 2930, 3010, 3030, 3040, 3110, 3120, 3130, 3140, 3150, 3160, 3170, 3180, 3220, 3310, 3320, 3330, 3410, 3420, 3430, 3610, 3620, 3630, 3810, 3820, 3830, 3920, 3930, 4210, 4220, 4230, 4310, 4320, 4330, 4340, 4350, 4360, 4370, 4380, 4390, 4410, 4420, 4430, 4440, 4450, 4460, 4470, 4480, 4490, 4510, 4520, 4530, 4540, 4550, 4560, 4570, 4580, 4590, 4610, 4620, 4630, 4710, 4720, 4730, 4740, 4750, 4760, 4770, 4780, 4910, 4920, 5010, 5020, 5030, 5040, 5050, 5060, 5070, 5110, 5120, 5130, 5140, 5150, 5160‧‧‧ operation

311 ~ 316, 321 ~ 325‧‧‧

326, 2310‧‧‧ Run screen

610, 620, 710, 720, 1030, 1130, 1230, 1330, 1510, 1530, 1730, 2130, 2340, 2341, 2711, 3230, 3530, 3710, 3730, 4011

1010, 3510‧‧‧face images

1020, 1120, 1220, 1320, 3520‧‧‧ images

1110‧‧‧Iris image

1210‧‧‧ vein image

1310‧‧‧Skeleton image

1520, 3720‧‧‧ID and password

1710, 1910, 2110, 2320, 3210‧‧‧ objects

2610‧‧‧Server

2710, 4010 ‧ ‧ ‧ watches / wearable devices

2720, 4020‧‧‧ glasses / wearable devices

2730, 4030 ‧‧‧ wristband / wearable device

2740, 4040‧‧‧ Ring / Wearable

5300‧‧‧device

5310‧‧‧User Input Unit

5320‧‧‧Output unit

5321‧‧‧display unit

5322‧‧‧Sound output unit

5323‧‧‧Vibration Motor

5330‧‧‧Controller / Processor

5340‧‧‧communication unit

5341‧‧‧Short range communication unit

5342‧‧‧Mobile communication unit

5343‧‧‧Broadcast receiving unit

5350‧‧‧Sensing unit

5351‧‧‧Magnetic sensor

5352‧‧‧Acceleration sensor

5353‧‧‧Temperature / Humidity Sensor

5354‧‧‧Infrared sensor

5355‧‧‧Gyroscope sensor

5356‧‧‧Position Sensor

5357‧‧‧Barometric sensor

5358‧‧‧Proximity sensor

5359‧‧‧RGB sensor

5360‧‧‧Audio / video (A / V) input unit

5361‧‧‧Camera

5362‧‧‧Microphone

5371‧‧‧User Interface (UI) Module

5372‧‧‧Touch screen module

5373‧‧‧Alarm module

5380‧‧‧User Information Obtainer

De_Key 1‧‧‧ Decoding Key

En_Key 1, En_Key 2‧‧‧ encoding key

These and / or other aspects will become apparent and more comprehensible from the following description of exemplary embodiments taken in conjunction with the accompanying drawings, in which: FIG. 1 illustrates a wearable device in which Examples of encoding or decoding keys.

2A and 2B illustrate a relationship between a wearable device and encoding and decoding of content according to an exemplary embodiment.

3 is a flowchart illustrating an example in which a wearable device generates an encoding key according to a result of user authentication according to an exemplary embodiment.

4 is a flowchart illustrating an example in which a wearable device generates an encoding key and an external device encodes content according to an exemplary embodiment.

5 is a flowchart illustrating an example in which a wearable device maintains a connection with one of a plurality of devices according to an exemplary embodiment.

FIG. 6 illustrates an example in which the wearable device selects one of a plurality of devices according to an exemplary embodiment.

FIG. 7 illustrates where a wearable device selects multiple devices according to another exemplary embodiment. Of one of the three devices.

FIG. 8 is a flowchart illustrating an example in which a wearable device authenticates a user according to an exemplary embodiment.

9 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's biometric information according to an exemplary embodiment.

FIG. 10 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's face information according to an exemplary embodiment.

11 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's iris information or retinal information according to an exemplary embodiment.

FIG. 12 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's vein information according to an exemplary embodiment.

FIG. 13 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's skeleton information according to an exemplary embodiment.

14 is a flowchart illustrating an example in which a wearable device authenticates a user by using a user's account information according to an exemplary embodiment.

15 illustrates an example in which a wearable device authenticates a user by using a user's identification (ID) and password, according to an exemplary embodiment.

16 is a flowchart of an example in which a wearable device generates an encoding key and transmits the generated encoding key to an external device according to an exemplary embodiment.

FIG. 17 illustrates an example of a condition under which a wearable device generates an encoding key for a user according to an exemplary embodiment.

18 is a flowchart of an example in which a wearable device generates an encoding key and transmits the generated encoding key to an external device according to another exemplary embodiment.

FIG. 19 illustrates a wearable device generating an encoding according to another exemplary embodiment An instance of the condition by which the key is borrowed.

20 is a flowchart illustrating an example in which a wearable device generates an encoding key and an external device encodes content, according to another exemplary embodiment.

FIG. 21 illustrates an example in which a wearable device generates an encoding key when an external device executes a program according to an exemplary embodiment.

22A is a flowchart illustrating an example in which a wearable device generates an encoding key and an external device encodes content according to another exemplary embodiment.

FIG. 22B illustrates an example in which a wearable device generates an encoding key when an external device exits a program according to an exemplary embodiment.

FIG. 23A is a flowchart illustrating an example in which a wearable device generates an encoding key and an external device encodes content, according to another exemplary embodiment.

FIG. 23B illustrates an example in which an external device encodes content by using a pre-received encoding key according to an exemplary embodiment.

FIG. 24 is a flowchart illustrating an example in which an external device encodes content according to an exemplary embodiment.

FIG. 25 illustrates an example in which an external device matches an encoding key with a wearable device and stores matching information according to an exemplary embodiment.

FIG. 26 illustrates an example in which an external device transmits matching information to a server or a wearable device according to an exemplary embodiment.

FIG. 27 illustrates an example in which a wearable device outputs an alert when an external device has completed encoding of content, according to an exemplary embodiment.

FIG. 28 is a flowchart illustrating an example in which a wearable device generates a decoding key and an external device decodes content according to an exemplary embodiment.

FIG. 29 and FIG. 30 illustrate a method in which a wearable device is manufactured according to an exemplary embodiment. Examples of generating a decoding key and transmitting the decoding key to an external device.

FIG. 31 is a flowchart illustrating an example in which a wearable device generates a decoding key and transmits the decoding key to an external device according to another exemplary embodiment.

FIG. 32 illustrates an example in which a wearable device obtains user information in order to generate a decoding key according to an exemplary embodiment.

FIG. 33 is a flowchart illustrating an example in which a wearable device authenticates a user to generate a decoding key according to an exemplary embodiment.

FIG. 34 is a flowchart illustrating an example in which the wearable device authenticates a user to generate a decoding key by using the user's biological information according to an exemplary embodiment.

FIG. 35 illustrates an example in which a wearable device authenticates a user by using a user's face information according to an exemplary embodiment.

FIG. 36 is a flowchart illustrating an example in which a wearable device authenticates a user to generate a decoding key by using the user's account information according to an exemplary embodiment.

FIG. 37 illustrates an example in which a wearable device authenticates a user by using a user's ID and password according to an exemplary embodiment.

FIG. 38 is a flowchart of an example in which a wearable device generates a decoding key and transmits the generated decoding key to an external device according to an exemplary embodiment.

FIG. 39 illustrates an example of a condition under which a wearable device generates a decoding key according to an exemplary embodiment.

FIG. 40 illustrates an example in which a wearable device outputs an alert when an external device has completed decoding of content, according to an exemplary embodiment.

FIG. 41 illustrates where an external device generates a coding key according to an exemplary embodiment Or an instance of a decoding key.

FIG. 42 is a flowchart illustrating an example in which the wearable device performs user authentication and transmits a result of the user authentication to an external device according to an exemplary embodiment.

43 is a flowchart illustrating an example in which an external device encodes content by using a user authentication result received from a wearable device according to an exemplary embodiment.

FIG. 44 is a flowchart illustrating an example in which an external device encodes content by using a user authentication result received from a wearable device according to another exemplary embodiment.

FIG. 45 is a flowchart illustrating an example in which an external device encodes content by using a user authentication result received from a wearable device according to another exemplary embodiment.

FIG. 46 is a flowchart illustrating an example in which an external device generates a decoding key and decodes content according to an exemplary embodiment.

FIG. 47 is a flowchart illustrating an example in which an external device generates a decoding key and decodes content according to another exemplary embodiment.

FIG. 48 illustrates an example in which a wearable device sets an access right to an external device according to an exemplary embodiment.

FIG. 49 is a flowchart illustrating an example in which the wearable device sets an access right to an external device.

FIG. 50 is a flowchart illustrating an example in which a wearable device sets an access right to an external device based on a result of user authentication according to an exemplary embodiment.

FIG. 51 is a flowchart illustrating an example in which the wearable device determines whether to activate an external device for which an access right has been set, according to an exemplary embodiment.

FIG. 52 illustrates an example embodiment in which Examples (a) and (b) of wearing a wearable device to determine whether a user can use an external device.

53 and 54 illustrate a structure of an example of a wearable device or an external device according to one or more exemplary embodiments.

Reference will now be made in detail to the illustrative embodiments, examples of which are illustrated in the accompanying drawings. In this regard, the exemplary embodiments of the present invention should be considered only in a descriptive sense and not intended to limit the scope of the inventive concept. All differences that can be easily made by the experts in this technology from the self-description and exemplary embodiments will be understood to be included in the scope of the inventive concept.

Throughout this specification, it will also be understood that when an element is referred to as being "connected to" another element, the element can be directly connected to the other element or be electrically connected to the other element, and intervening elements may also be present. Furthermore, when a part "includes" or "includes" an element, the part may further include other elements, but does not include other elements, unless there is a specific contrary description.

Throughout the specification, the term "indicative action" indicates an action performed on the screen of a terminal in order to control the user of the terminal. For example, the gestures can include touch gestures, touch and hold gestures, double touch gestures, drag gestures, horizontal movement gestures, toggle gestures, drag and land gestures, and hand shake gestures. Wait.

Throughout the manual, the expression "screen to device" indicates that a particular screen is displayed on the screen of the device. Therefore, the expression "output to the screen of the device" may be synonymous with the expression "display on the screen of the device", but it is not required.

As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. When preceded by a component list, expressions such as "at least one of" modify the entire list of components and do not modify individual components of the list.

Hereinafter, one or more exemplary embodiments will be described in detail with reference to the accompanying drawings.

FIG. 1 illustrates an example in which the wearable device 10 generates an encoding key or a decoding key according to an exemplary embodiment.

FIG. 1 illustrates a wearable device 10, a user 20 of the wearable device 10, and an external device 30.

Referring to FIGS. 1, 53 and 54, the wearable device 10 obtains user information from the user 20. According to an exemplary embodiment, the user information instructs the wearable device 10 to identify information required by the user 20 (eg, to identify the user 20).

For example, the user information may include biological information of the user 20. In more detail, the biological information of the user 20 may include information about at least one of a fingerprint, an iris, a retina, a vein, a skeletal part, and a face of the user 20. The wearable device 10 can obtain the biological information of the user 20 by using the user information obtainer 5380. For example, the wearable device 10 may obtain information about the fingerprint, vein, or skeleton portion of the user 20 by using a sensor included in the sensing unit 5350, and may use the audio / video ( audio / video; A / V) The camera in the input unit 5360 obtains information about the iris, retina, or face of the user 20. However, the wearable device 10 may obtain the biological information of the user 20 by using methods other than the above-mentioned methods.

The wearable device 10 is a device that can be attached to the body of the user 20 and can perform computing operations. Furthermore, the wearable device 10 can exchange data with external devices. The wearable device 10 may be embodied in various forms including watches, glasses, bracelets, rings, necklaces, shoes, stickers, etc. that can be attached to the body of the user 20.

One or more exemplary embodiments of the wearable device 10 are applicable to a mobile device that can be moved while held by the user 20 or can be moved with the user 20 as an accessory of the user 20. The mobile device may include various mobile devices, such as a smart phone, a tablet computer, a notebook computer, a personal digital assistant (PDA), a camera electronic photo frame, a navigation device, and the like.

In an exemplary embodiment, the mobile device may obtain user information, and when the user is identified based on the obtained user information, the mobile device may generate an encoding key for encoding content of the external device. The mobile device may then transmit the generated encoding key to an external device. In another exemplary embodiment, the mobile device may obtain user information, and when the user is identified based on the obtained user information, the mobile device may generate a decoding key for decoding content of the external device. The mobile device may then transmit the generated decoding key to an external device.

As another example, the user information may include account information of the user 20. In more detail, the account information of the user 20 may include a unique identification (ID) and password of the user 20. The wearable device 10 can obtain the account information of the user 20 by using the user information obtainer 5380. For example, the wearable device 10 may obtain an ID and a password from the user 20 via the user input unit 5310.

The wearable device 10 identifies the user 20 based on the obtained user information. For example, the wearable device 10 may identify the user 20 by comparing the obtained user information with pre-registered information. In other words, if the obtained user information matches the pre-annotation Information, the wearable device 10 can determine that the user 20 is authenticated. An example in which the wearable device 10 authenticates the user 20 based on the obtained user information will be described later with reference to FIGS. 8 to 15.

Before the wearable device 10 obtains user information for user authentication, the wearable device 10 may register user information in advance.

For example, the wearable device 10 may register the user information by obtaining the user information and by storing the user information in the memory 5370 of the wearable device 10.

As another example, the wearable device 10 may register user information by obtaining user information and transmitting user information to a server. According to an exemplary embodiment, the server may store user information, and may transmit user information to the wearable device 10 according to a request from the wearable device 10 (for example, when the wearable device 10 performs user authentication). .

When the user 20 is authenticated, the wearable device 10 generates an encoding key. According to an exemplary embodiment, the encoding key is a key for encoding content of the external device 30. For example, the wearable device 10 may generate an encoding key for a symmetric key algorithm or may generate an encoding key for an asymmetric key algorithm.

Alternatively, the wearable device 10 may randomly generate the encoding key or may generate the encoding key based on the biological information of the user 20. For example, the wearable device 10 may use biological information of the user 20 (e.g., at least one of a fingerprint, an iris, a retina, a vein, a skeleton portion, and a face of the user 20) by using a predetermined mathematical algorithm. Information) into a template. The template may be data (bit stream) obtained by encoding biological information extracted by using a predetermined sensor.

The wearable device 10 may set the result as an encoding key, wherein the conclusion The result is obtained by using a template as a factor of a predetermined function (for example, a cryptographic hash function). Alternatively, the template can be used partially as a factor of a function. The above example of generating an encoding key uses biological information. However, one or more exemplary embodiments are not limited thereto, and various methods of generating an encoding key may be used.

For example, a predetermined calculation (e.g., XOR operation) using a preset value of a specific length (e.g., 128 bits) can be applied to the template, and only the value corresponding to the specific length from the result value can be set as the encoding key key. Alternatively, a Password Based Key Derivation Function 2 (PBKDF2) may be used.

The content includes objects that can be stored in the external device 30 and can be reproduced by the external device 30.

For example, the content may include a text file or a multimedia file. According to an exemplary embodiment, a text file or a multimedia file may include an object for which an operation is performed in a Microsoft word program, a Microsoft Excel program, a Microsoft PowerPoint program, and the like installed in the external device 30. According to an exemplary embodiment, operations include reading, editing, deleting, etc. of a text file or a multimedia file.

As another example, the content may include photos, images, videos, music, and the like. For example, the content may include objects targeted for performing operations in a photo execution program, an image execution program, a video execution program, a music execution program, and the like installed in the external device 30. According to an exemplary embodiment, operations include reading, editing, deleting, and the like of content.

As another example, the content contains programs. For example, the content may include programs installed in the external device 30 and capable of executing text files, multimedia files, photos, images, videos, or music.

The wearable device 10 transmits an encoding key to the external device 30. Then, outside The external device 30 encodes the content by using an encoding key. According to an exemplary embodiment, the wearable device 10 may transmit the encoding key to the external device 30 by using a wireless or wired communication method. For example, the wearable device 10 may transmit the encoding key to the external device 30 via a data cable connected to the external device 30. Furthermore, the wearable device 10 may transmit a coding key to an external device via wireless communication including near field communication (NFC), ZigBee, Bluetooth, ultra-wideband (UWB), and the like. 30.

Furthermore, the wearable device 10 can directly encode content by using an encoding key. According to an exemplary embodiment, the external device 30 may transmit content to the wearable device 10, and the wearable device 10 may encode content. The wearable device 10 may then transmit the encoded content to the external device 30. Content exchange between the wearable device 10 and the external device 30 may be performed by using the above-mentioned wireless or wired communication method.

Even if it has been described that the wearable device 10 generates an encoding key according to the result of user authentication, the wearable device 10 can still read the encoding key stored in the memory 5370 according to the result of user authentication.

When the user 20 is authenticated, the wearable device 10 generates a decoding key. According to an exemplary embodiment, the decoding key is a key for decoding content of the external device 30. When the user 20 attempts to execute the encoded content stored in the external device 30, the wearable device 10 may generate a decoding key according to the result of the user authentication. For example, the wearable device 10 may generate a decoding key for a symmetric key algorithm or may generate a decoding key for an asymmetric key algorithm.

The wearable device 10 may transmit the generated decoding key to the external device 30, and the external device 30 may decode the encoded content by using the decoding key. Alternatively, the wearable device 10 may directly decode the encoded content by using a decoding key. In can Data exchange between the wearable device 10 and the external device 30 may be performed by using the above-mentioned wireless or wired communication method. The wearable device 10 reads the decoding key stored in the memory 5370 according to the result of user authentication.

That is, the wearable device 10 may generate a key for encoding the content of the external device 30 and may generate another key for decoding the content encoded by the wearable device 10. Therefore, the content encoded by the wearable device 10 can be decoded by using a decoding key generated only by the wearable device 10.

Hereinafter, the encoding and decoding of the content of the external device 30 is described below with reference to FIGS. 2A and 2B.

2A and 2B illustrate a relationship between a wearable device 10 and encoding and decoding of content according to an exemplary embodiment.

FIG. 2A illustrates an example of the screen 31 output by the external device 30 when the user 20 is not wearing the wearable device 10. Among the contents 311, 312, 313, 314, and 315 stored in the external device 30, the contents 311, 312, and 314 may be encoded, and the contents 313 and 315 may be unencoded. According to an exemplary embodiment, it is assumed that content encoding is performed by using an encoding key generated by the wearable device 10.

When the user 20 who is not wearing the wearable device 10 attempts to execute the encoded content 314, the external device 30 may not execute the content 314 and may output an image 316 indicating that execution of the content 314 is rejected. In other words, if the user 20 is not wearing the wearable device 10, decoding of the encoded content 311, 312, and 314 is not performed.

FIG. 2B illustrates an example of the screen 32 output by the external device 30 when the user 20 wears the wearable device 10. As shown in FIG. 2A, among the contents 321, 322, 323, 324, and 325 stored in the external device 30, the contents 321, 322 and And 324 may be encoded, and content 323 and 325 may be unencoded. Furthermore, it is assumed that the content encoding is performed by using an encoding key generated by the wearable device 10.

When the user 20 wearing the wearable device 10 attempts to execute the encoded content 324, the external device 30 may execute the content 324 and may output an execution screen 326 related to the content 324. In other words, while the user 20 wears the wearable device 10, the wearable device 10 can perform user authentication, and thus the wearable device 10 can generate a decoding key.

2A and 2B illustrate decoding of the content, but encoding of the content can be performed in the same manner. In other words, while the user 20 is wearing the wearable device 10, the wearable device 10 can perform user authentication, and thus the wearable device 10 can generate an encoding key.

The encoding key or the decoding key generated by the wearable device 10 may be transmitted to the external device 30, and the external device 30 may encode or decode the content.

Alternatively, the wearable device 10 may encode or decode content by using an encoding key or a decoding key. For example, when the external device 30 transmits content to the wearable device 10, the wearable device 10 may encode or decode content, and may transmit the encoded content or decoded content to the external device 30.

Even though it has been described that the wearable device 10 generates an encoding key or a decoding key based on the result of user authentication, the wearable device 10 can still read the encoding key or decoding stored in the memory 5370 according to the result of user authentication Key.

Referring to FIGS. 1 to 2B, the wearable device 10 generates an encoding key or a decoding key for encoding or decoding content stored in the external device 30, but one or more exemplary embodiments are not limited thereto. In other words, the wearable device 10 may generate an encoding key or a decoding key of content to be transmitted to an external device. According to the example implementation For example, the external device may be a cloud server or another device other than the external device 30.

For example, when the external device 30 transmits content to the cloud server, the wearable device 10 may generate an encoding key for encoding the content. According to an exemplary embodiment, the wearable device 10 may transmit the encoding key to the external device 30, and the external device 30 may encode the content and then may transmit the encoded content to the cloud server. Furthermore, when the wearable device 10 transmits the encoding key to the cloud server, and the external device 30 transmits the content to the cloud server, the cloud server can encode the content by using the encoding key.

As another example, when the external device 30 receives the encoded content from the cloud server, the wearable device 10 may generate a decoding key for decoding the encoded content. According to an exemplary embodiment, the wearable device 10 may transmit a decoding key to the external device 30, and then the external device 30 may decode the encoded content received from the cloud server. Alternatively, the wearable device 10 may transmit a decoding key to the cloud server, and then the cloud server may decode the encoded content by using the decoding key and may transmit the decoded content to the external device 30.

1 to 2B, the wearable device 10 generates an encoding key or a decoding key, but one or more exemplary embodiments are not limited thereto. In other words, each of the plurality of wearable devices may generate an encoding key or a decoding key, and the content may be encoded based on the plurality of encoding keys or may be decoded based on the plurality of decoding keys.

For example, the encoding or decoding level of the content may change depending on the importance or security level of the content. If the content is encoded by using a single encoding key compared to the content encoded by using a plurality of encoding keys, the content can be easily decoded by a third party not intended by the user 20. Therefore, if each of the wearable devices generates an encoding key, and the content is encoded by using the plurality of encoding keys, the security level of the content can be increased.

For example, the wearable device may generate an encoding key separately, and may encode content based on the encoding key. If it is assumed that the first wearable device generates a first encoding key and the second wearable device generates a second encoding key, the content can be mainly encoded by using the first encoding key, and can be used by The second encoding key is secondary encoded.

As another example, the wearable device may separately generate portions of the encoding key, and the content may be encoded by using the encoding keys obtained by combining the portions. If it is assumed that the first wearable device generates the part of the encoding key and the second wearable device generates the remainder of the encoding key, the content can be generated by combining the first and second wearable devices by using Partially obtained encoding key.

Content encoded by using an encoding key generated by using a wearable device can be decoded by using a decoding key generated by using a wearable device.

For example, assume that content is primarily encoded by using a first encoding key and secondaryly encoded by using a second encoding key. According to an exemplary embodiment, the encoded content may be mainly decoded by using a second decoding key generated by the second wearable device, and may be used by using the first generated by the first wearable device. The decoding key is decoded secondary.

As another example, it is assumed that the content is encoded by using an encoding key, which is a combination of parts generated by the first and second wearable devices. According to an exemplary embodiment, the first wearable device may generate a portion of a decoding key, the second wearable device may generate a remaining portion of the decoding key, and then the content may be combined by using the first and the first by using The two wearable devices generate the decoding key obtained by the part and decode it.

As another example, to be transmitted to the cloud server via the external device 30 The content can be pre-encoded by using an encoding key. For example, the content may be pre-encoded by the external device 30 by using an encoding key received from the wearable device 10. Alternatively, the content may be pre-encoded by the external device 10 and then may be transmitted from the external device 10.

In this case, if the external device 30 transmits content to the cloud server, the external device 30 may decode the encoded content and then may transmit the content to the cloud server. For example, the external device 30 may receive a decoding key from the wearable device 10, may decode the encoded content by using the decoding key, and may transmit the content to a cloud server. Alternatively, when user authentication is performed in the wearable device 10, the external device 30 may decode the encoded content by using a pre-stored decoding key and may transmit the content to the cloud server.

The external device 30 may transmit the decoded content to the cloud server based on a user input. For example, when the external device 30 transmits content to the cloud server, the external device 30 may output a pop-up window to ask the user whether to decode the content. In this case, in response to a user input allowing decoding of the content, the external device 30 may decode the content and may transmit the decoded content to the cloud server.

Hereinafter, an example in which the wearable device 10 generates an encoding key is described with reference to FIGS. 3 to 27.

FIG. 3 is a flowchart illustrating an example in which the wearable device 10 generates an encoding key according to a result of user authentication according to an exemplary embodiment.

The exemplary embodiment of FIG. 3 includes operations processed by the wearable device 10 shown in FIG. 1 in chronological order. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 3.

In operation 310, the wearable device 10 identifies a user based on the user information input to the wearable device 10. The wearable device 10 can identify the user by comparing the input user information with the pre-stored user information.

The wearable device 10 may perform user authentication based on at least one of the biometric information and the ID and the password.

The wearable device 10 may authenticate the user 20 only before the wearable device 10 generates the encoding key or may authenticate the user 20 regardless of the generation of the encoding key. In other words, although the wearable device 10 generates an encoding key according to a result of user authentication, if the encoding key has not been generated, the wearable device 10 may perform user authentication without a time limit.

For example, the wearable device 10 may generate an encoding key, and may perform user authentication before the wearable device 10 transmits the generated encoding key to the external device 30. Alternatively, when a program providing content is executed or ended in the external device 30, the wearable device 10 may automatically perform user authentication within a preset period of time. Alternatively, when the wearable device 10 is connected with the external device 30 for communication, the wearable device 10 may automatically perform user authentication within a preset period of time. Alternatively, when the wearable device 10 determines that the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined distance, the wearable device 10 may automatically perform user authentication within a preset period of time.

As described above, if the user authentication is performed before the encoding key is transmitted to the external device 30, the user 20 can feel that the content encoding time is reduced.

In operation 320, when the user is authenticated, the wearable device 10 generates an encoding key for encoding content in the external device 30. For example, the wearable device 10 may generate an encoding key for a symmetric key algorithm or may generate Encoding key for a symmetric key algorithm. When the user is authenticated, the wearable device 10 can read the encoding key pre-stored in the memory 5370.

In operation 330, the wearable device 10 transmits the generated encoding key to the external device 30. Then, the external device 30 may encode the content by using the received encoding key. Alternatively, the wearable device 10 may directly encode the content by using an encoding key.

FIG. 4 is a flowchart illustrating an example in which the wearable device 10 generates an encoding key and the external device 30 encodes content according to an exemplary embodiment.

The exemplary embodiment of FIG. 4 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 4.

In operation 410, the wearable device 10 and the external device 30 are connected to each other. According to the exemplary embodiment, connection means that data exchange is possible between them. For example, the wearable device 10 and the external device 30 may be connected to each other by using a wireless or wired communication method, and an example of the wireless and wired communication method is described above with reference to FIG. 1.

If multiple devices can be connected to the wearable device 10, the wearable device 10 can select one of the multiple devices and can maintain a connection with the selected device.

Hereinafter, an example in which the wearable device 10 maintains a connection with one of the plurality of devices is described with reference to FIGS. 5 to 7.

FIG. 5 is a flowchart illustrating an example in which the wearable device 10 maintains a connection with one of the plurality of devices according to an exemplary embodiment.

The exemplary embodiment of FIG. 5 includes The illustrated wearable device 10 handles the operations. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 5.

In operation 510, the wearable device 10 selects one of the plurality of devices. If the wearable device 10 is connected to the external device 30 by using a wireless communication method, the wearable device 10 may search for a device that can be connected to the wearable device 10. For example, it is assumed that the wearable device 10 and the external device 30 are connected via Bluetooth, and the wearable device 10 can first search for a neighboring device by using its Bluetooth module. Then, if multiple devices are discovered, the wearable device 10 may select one of the discovered devices.

For example, the wearable device 10 may select one of the discovered devices according to user input. As another example, the wearable device 10 may select one of the discovered devices according to historical indication information about the pre-selected device.

Hereinafter, an example in which the wearable device 10 selects one of a plurality of devices is described with reference to FIGS. 6 and 7. In the exemplary embodiments of FIGS. 6 and 7, the wearable device 10 and the external device 30 are connected to each other via Bluetooth, but one or more exemplary embodiments are not limited thereto. An example in which the wearable device 10 and the external device 30 can be connected to each other is described above with reference to FIG. 1.

FIG. 6 illustrates an example in which the wearable device 10 selects one of a plurality of devices according to an exemplary embodiment.

If the plurality of devices can be connected to the wearable device 10, the wearable device 10 can output a pop-up window 610 indicating that the plurality of devices are found. For example, the wearable device 10 may search for a neighboring device by using the Bluetooth module of the wearable device 10, and if the plurality of devices are found, the wearable device 10 may display a bomb Out of window 610.

Then, the wearable device 10 may output a pop-up window 620 requesting the user 20 to select one of the plurality of devices. For example, if two devices are discovered by the wearable device 10, the wearable device 10 may mark the name of the discovered device on the pop-up window 620 ('device 1' and 'device 2' referred to in FIG. 6) ), And the user 20 may select one of the discovered devices.

FIG. 7 illustrates an example in which the wearable device 10 selects one of a plurality of devices according to another exemplary embodiment.

If the plurality of devices can be connected to the wearable device 10, the wearable device 10 can output a pop-up window 710 indicating that the plurality of devices are found. For example, the wearable device 10 may search for a neighboring device by using a Bluetooth module of the wearable device 10, and if the plurality of devices are found, the wearable device 10 may display a pop-up window 710.

Then, the wearable device 10 may select one of the plurality of devices by referring to the selection history. For example, if it is assumed that the wearable device 10 has selected 'device 3', the wearable device 10 may store a history including information indicating that 'device 3' has been selected in the memory 5370. Then, if the plurality of devices including 'device 3' are found, the wearable device 10 may automatically select 'device 3'.

The wearable device 10 may output a pop-up window 720 to ask whether the user 20 is connected to 'device 3', and the user 20 may enter information to allow the wearable device 10 to connect to 'device 3'.

Referring back to FIG. 5, in operation 520, the wearable device 10 maintains a connection with the selected external device 30. In other words, the wearable device 10 maintains a state in which data is exchanged with the external device 30.

According to the description with reference to FIG. 5, the wearable device 10 is connected to one external device 30, but one or more exemplary embodiments are not limited thereto. In other words, the wearable device 10 may be connected to a plurality of devices, and may transmit an encoding key to each of the plurality of connected devices or may receive content from each of the plurality of connected devices.

Referring back to FIG. 4, in operation 420, the wearable device 10 obtains user information. For example, the user information may be biological information of the user 20 or account information of the user 20.

In operation 430, the wearable device 10 authenticates the user 20 by using the user information. For example, the wearable device 10 may identify the user 20 by determining whether the obtained user information matches the pre-stored user information.

The wearable device 10 may authenticate the user 20 only before the wearable device 10 generates the encoding key, or may authenticate the user 20 regardless of the generation of the encoding key. That is, although the wearable device 10 generates an encoding key according to a result of user authentication, if the encoding key has not been generated, the wearable device 10 may perform user authentication without a time limit.

Hereinafter, an example in which the wearable device 10 authenticates the user 20 is described with reference to FIGS. 8 to 15.

FIG. 8 is a flowchart illustrating an example in which the wearable device 10 authenticates a user 20 according to an exemplary embodiment.

The exemplary embodiment of FIG. 8 includes operations processed by the wearable device 10 shown in FIG. 1 in chronological order. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 8.

In operation 810, the wearable device 10 obtains biological information from the user 20.

In operation 820, the wearable device 10 obtains an ID and a password from the user 20.

In operation 830, the wearable device 10 performs user authentication based on at least one of the biometric information and the ID and the password. That is, the wearable device 10 may perform user authentication by using biometric information or by using ID and password. Alternatively, the wearable device 10 may perform user authentication by using all biometric information and ID and password.

FIG. 9 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 by using the biometric information of the user 20 according to an exemplary embodiment.

In operation 910, the wearable device 10 obtains biological information of the user 20. According to an exemplary embodiment, the biological information may be information about at least one of a fingerprint, an iris, a retina, a vein, a skeletal portion, and a face of the user 20. For example, the wearable device 10 may obtain information about the fingerprint, vein or skeleton portion of the user 20 by using a sensor included in the sensing unit 5350, and may use the A / V input by using The camera in unit 5360 obtains information about the iris, retina, or face of the user 20.

In operation 920, the wearable device 10 determines whether the obtained biological information matches the pre-stored biological information. In other words, the wearable device 10 can store the biological information of the user 20 in the memory 5370, and can determine whether the biological information obtained later from the user 20 matches the biological information stored in the memory 5370.

If the wearable device 10 determines that the obtained biological information matches the pre-stored biological information, the wearable device 10 performs operation 930, and if it does not match, the wearable device 10 can be worn. The wearable device 10 ends the procedure.

In operation 930, the wearable device 10 determines that the user 20 is authenticated.

FIG. 10 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 by using the face information of the user 20 according to an exemplary embodiment.

The wearable device 10 obtains face information of the user 20. For example, the wearable device 10 may obtain a face image 1010 of the user 20 by using a camera disposed at the wearable device 10.

The wearable device 10 searches the user information in the memory 11 for an image 1020 corresponding to the face image 1010 of the user 20. According to an exemplary embodiment, the image 1020 contains information corresponding to the positions of the eyes, nose, mouth, or face contours shown in the face image 1010.

Each person has the only characteristic of his or her face. For example, the position or distance between the eyes, nose, and mouth may be different for each person. Furthermore, the contour of the face or where the eyes, nose, and mouth are placed on the face may be different for each person. Therefore, even if a person changes hair style or makeup, the characteristics of the face do not change.

The wearable device 10 extracts features from the face image 1010 and extracts features from the image 1020 stored in the memory 11. Then, the wearable device 10 searches for an image 1020 of the user 20 corresponding to the face image 1010 and among a plurality of information blocks stored in the memory 11, and the wearable device 10 compares the extracted features. Alternatively, the wearable device 10 may convert the face features of the user 20 into data in advance, may store the data, and may compare the stored data with features extracted from the face image 1010.

As a search result, if an image 1020 corresponding to the face image 1010 is stored in the memory 11 (alternatively, if it corresponds to a feature extracted from the face image 1010 Data is stored in the memory 11), the wearable device 10 determines that the user 20 is authenticated. In this case, the wearable device 10 may output a pop-up window 1030 indicating that the user authentication is completed.

FIG. 11 is a flowchart illustrating an example in which the wearable device 10 uses the iris information or the retinal information of the user 20 to identify the user 20 according to an exemplary embodiment.

The wearable device 10 obtains face information of the user 20. For example, the wearable device 10 may obtain an iris image or a retinal image of the user 20 by using a camera configured at the wearable device 10. Hereinafter, it is assumed that the wearable device obtains an iris image 1110 of the user 20.

The wearable device 10 searches the user information in the memory 11 for an image 1120 corresponding to the iris image 1110 of the user 20. According to an exemplary embodiment, the image 1120 contains information corresponding to the pattern of the iris shown in the iris image 1110.

Each person has a unique iris pattern. In other words, the pattern of the iris of the user A is different from the pattern of the iris of the user B. Therefore, the wearable device 10 can identify the user 20 by identifying the pattern of the iris of the user 20.

The wearable device 10 extracts features from the iris image 1110 and extracts features from the image 1120 stored in the memory 11. Next, the wearable device 10 searches for an image 1120 of the user 20 corresponding to the iris image 1110 and among a plurality of information blocks stored in the memory 11, and the wearable device 10 compares the extracted features. Alternatively, the wearable device 10 may convert the iris pattern of the user 20 into data in advance, may store the data, and may compare the stored data with features extracted from the iris image 1110.

As a search result, if the image 1120 corresponding to the iris image 1110 is stored in the memory 11 (alternatively, if the data corresponding to the feature extracted from the iris image 1110 is stored in the memory 11), the wearable device 10 It is determined that the user 20 is identified. In this case, the wearable device 10 may output a pop-up window 1130 indicating that the user authentication is completed.

FIG. 12 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 by using the vein information of the user 20 according to an exemplary embodiment.

The wearable device 10 obtains vein information of the user 20. For example, the wearable device 10 may obtain a vein image 1210 of the user 20 by using a sensor included in the sensing unit 5350.

The wearable device 10 searches the user information in the memory 11 for an image 1220 corresponding to the vein image 1210 of the user 20. According to an exemplary embodiment, the image 1220 contains information corresponding to the pattern (or shape) of the veins shown in the vein image 1210.

Each has a unique vein pattern. Furthermore, the shape of the veins distributed in each person is different. Therefore, the wearable device 10 can identify the user 20 by identifying the vein pattern or vein shape of the user 20.

The wearable device 10 extracts features from the vein image 1210 and extracts features from the image 1220 stored in the memory 11. Then, the wearable device 10 searches for an image 1220 of the user 20 corresponding to the vein image 1210 and among a plurality of information blocks stored in the memory 11, and the wearable device 10 compares the extracted features. Alternatively, the wearable device 10 may convert the vein pattern of the user 20 into data in advance, may store the data, and may compare the stored data with features extracted from the vein image 1210.

As a search result, if the image 1220 corresponding to the vein image 1210 is stored in the memory 11 (alternatively, if the data corresponding to the feature extracted from the vein image 1210 is stored in the memory 11), the wearable device 10 It is determined that the user 20 is identified. In this case, the wearable device 10 may output a pop-up window 1230 indicating that the user authentication is completed.

FIG. 13 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 by using the skeleton information of the user 20 according to an exemplary embodiment.

The wearable device 10 obtains skeleton information of the user 20. For example, the wearable device 10 may obtain a skeleton image 1310 of the user 20 by using a sensor included in the sensing unit 5350.

The wearable device 10 searches the user information in the memory 11 for an image 1320 corresponding to the skeleton image 1310 of the user 20. According to an exemplary embodiment, the image 1320 contains information about the shape, configuration, or size of the bones shown in the skeleton image 1310.

The wearable device 10 extracts features from the skeleton image 1310 and extracts features from the image 1320 stored in the memory 11. Then, the wearable device 10 searches the user 13 for an image 1320 corresponding to the skeleton image 1310 and among a plurality of information blocks stored in the memory 11, and the wearable device 10 compares the extracted features. Alternatively, the wearable device 10 may convert the features of the skeleton portion of the user 20 into data in advance, may store the data, and may compare the stored data with features extracted from the skeleton image 1310.

As a search result, if an image 1320 corresponding to the skeleton image 1310 is stored in the memory 11 (alternatively, if data corresponding to features extracted from the skeleton image 1310 is stored in the memory 11), the wearable device 10 Determine users 20 were identified. In this case, the wearable device 10 may output a pop-up window 1330 indicating that the user authentication has been completed.

Although not illustrated in FIGS. 10 to 13, the wearable device 10 can obtain the fingerprint information of the user 20 by using a sensor, can compare the obtained fingerprint information with the pre-stored fingerprint information of the user 20, and therefore The user 20 can be identified.

FIG. 14 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 by using the account information of the user 20 according to an exemplary embodiment.

In operation 1410, the wearable device 10 obtains account information of the user 20. Here, the account information may indicate the unique ID and password of the user 20 (for example, "PW"). For example, the wearable device 10 may receive an ID and a password from the user 20 via the user input unit 5310.

In operation 1420, the wearable device 10 determines whether the obtained account information matches the pre-stored information. That is, the wearable device 10 may store the ID and password of the user 20 in the memory 5370, and may determine whether the ID and password obtained from the user 20 later match the ID and password stored in the memory 5370. .

If the wearable device 10 determines that the obtained account information matches the pre-stored information, the wearable device 10 performs operation 1430, and if it does not match, the wearable device 10 ends the procedure.

In operation 1430, the wearable device 10 determines that the user 20 is authenticated.

Furthermore, as in the above-mentioned various methods, in the case where the user 20 is authenticated, after the user 20 is authenticated, when the wearable device 10 generates an encoding key for encoding content and transmits the encoding key to the outside When the device 30 is installed, the wearable device 10 may use an ID and a password (which are input by the user 20) for execution. Content ID and password.

In this case, when the wearable device 100 transmits the ID and password to the external device 30 and the user 20 is not wearing the wearable device 100, the external device 30 can execute the content by using the received ID and password.

FIG. 15 illustrates an example in which the wearable device 10 authenticates the user 20 by using the ID and password of the user 20 according to an exemplary embodiment.

The wearable device 10 outputs a pop-up window 1510 to the user 20 to request the user 20 to input the ID and password, and the user 20 inputs the ID 'Samsung_1' and the password '1234' via the user input unit 5310.

The wearable device 10 compares the ID “Samsung_1” and the password “1234” input by the user 20 with the ID and the password 1520 stored in the memory 11. If the wearable device 10 determines that the input ID and password match the stored ID and password 1520, the wearable device 10 determines that the user 20 is authenticated. In this case, the wearable device 10 may output a pop-up window 1530 indicating that the user authentication has been completed.

Referring back to FIG. 4, in operation 440, the external device 30 stores the content.

According to an exemplary embodiment, the content indicates an object to be encoded. An example of content is described above with reference to FIG. 1.

The time during which the external device 30 stores the content does not depend on when the wearable device 10 authenticates the user 20. In other words, the external device 30 may store content after the wearable device 10 performs user authentication, or the wearable device 10 may perform user authentication after the external device 30 stores content.

In operation 450, the external device 30 notifies the wearable device 10 that the content has been stored.

In operation 460, the wearable device 10 generates an encoding key for encoding content. For example, the wearable device 10 may generate an encoding key for a symmetric key algorithm or may generate an encoding key for an asymmetric key algorithm. Referring to FIG. 4, when the wearable device 10 receives a notification about the stored content from the external device 30, the wearable device 10 may automatically generate an encoding key without receiving input from the user 20, but one One or more exemplary embodiments are not limited thereto. That is, the wearable device 10 may generate an encoding key according to the selection of the user 20. An example in which the user selects whether to encode content (for example, whether to generate an encoding key) is described later with reference to FIGS. 16 and 17.

In operation 470, the wearable device 10 stores the generated encoding key. Furthermore, the wearable device 10 may not store independently but may directly delete the generated encoding key.

In operation 480, the wearable device 10 transmits the encoding key to the external device 30.

Hereinafter, an example in which the wearable device 10 generates an encoding key and transmits the generated encoding key to the external device 30 is described with reference to FIGS. 16 to 19.

FIG. 16 is a flowchart of an example in which the wearable device 10 generates an encoding key and transmits the generated encoding key to the external device 30 according to an exemplary embodiment.

In operation 1610, the wearable device 10 determines whether the content stored in the external device 30 is the encoding target content. As described above with reference to operation 450 in FIG. 4, the external device 30 may notify the wearable device 10 that the content is stored. After receiving the notification, the wearable device 10 may determine whether the content stored in the external device 30 is the encoding target content.

As described above with reference to FIG. 4, when the wearable device 10 is from an external device 30 When receiving the notification about the storage of the content, the wearable device 10 may generate the encoding key without determining whether the content is the encoding target content. Alternatively, if the wearable device 10 receives a notification about the storage of the content from the external device 30 before the wearable device 10 generates the encoding key, the wearable device 10 may determine whether the content is the encoding target content, and may An encoding key is generated based on the result of the determination. Therefore, the content stored in the external device 30 may be selectively encoded.

If the wearable device 10 determines that the content related to the storage notification from the external device 30 is the encoding target content, the wearable device 10 performs operation 1620, and if not, the wearable device 10 ends the procedure.

In operation 1620, the wearable device 10 generates an encoding key to be used for encoding content. The wearable device 10 then stores the generated encoding key.

In operation 1630, the wearable device 10 transmits the generated encoding key to the external device 30.

Hereinafter, the exemplary embodiment of FIG. 16 is described in detail with reference to FIG. 17.

FIG. 17 illustrates an example of conditions under which the wearable device 10 generates an encoding key for a user 20 according to an exemplary embodiment.

First, the external device 30 stores content. For example, when the external device 30 receives a user input requesting to store content, the external device 30 may store the content. For example, if the user 20 selects a 'save' object 1710 that is output to the screen of the external device 30, the content may be stored. According to an exemplary embodiment, the object 1710 may include an icon, a pop-up window, and the like.

As another example, the external device 30 may automatically store content at regular intervals. In other words, even if there is no request from the user 20, the external device 30 can automatically store the executed content at regular intervals.

When the content is stored, the external device 30 notifies the wearable device 10 that the content has been stored in operation 1720.

When receiving the notification from the external device 30, the wearable device 10 may output a pop-up window 1730 to ask the user 20 whether to encode the content. That is, the wearable device 10 may output a pop-up window 1730 to ask the user 20 whether to generate an encoding key. According to an exemplary embodiment, if the wearable device 10 receives a user input requesting to generate an encoding key via the user input unit 5310, the wearable device 10 generates an encoding key. Then, in operation 1740, the wearable device 10 transmits the generated encoding key to the external device 30.

Alternatively, the wearable device 10 may not ask the user 20 whether to generate an encoding key. In other words, if the wearable device 10 receives a notification about the storage of the content from the external device 30, the wearable device 10 can directly generate the encoding key and can transmit the generated encoding key to the external device 30.

FIG. 18 is a flowchart of an example in which the wearable device 10 generates an encoding key and transmits the generated encoding key to the external device 30 according to another exemplary embodiment.

Operations 1810, 1830, and 1840 in FIG. 18 are the same as operations 1610 to 1630 in FIG. 16, and therefore, detailed descriptions thereof are omitted here.

In operation 1820, the wearable device 10 determines whether the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value. In other words, the wearable device 10 calculates the distance between the wearable device 10 and the external device 30 and determines whether the distance is equal to or smaller than a predetermined value.

When the user 20 executes content by using the external device 30, in general, the user 20 and the external device 30 are adjacent to each other by having a small distance therebetween. because Here, the distance between the user 20 and the external device 30 may be a standard, and the user 20 determines whether to execute the content by using the external device 30 by using the standard.

Since the wearable device 10 according to an exemplary embodiment of the present invention can obtain biometric information to perform user authentication, it is assumed in this case that the user 20 is currently wearing the wearable device 10. Therefore, if the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value, the user 20 and the external device 30 can be positioned adjacent to each other.

Therefore, by determining whether the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value, it is possible to prevent the encoding key or the decoding key from being generated by someone other than the user 20.

Hereinafter, the exemplary embodiment of FIG. 18 is described in detail with reference to FIG. 19.

FIG. 19 illustrates an example of a condition by which the wearable device 10 generates an encoding key according to another exemplary embodiment.

First, the external device 30 stores content. For example, when the external device 30 receives a user input requesting the external device 30 to store the content, the external device 30 may store the content. For example, if the user 20 selects a 'save' object 1910 that is output to the screen of the external device 30, the content may be stored. According to an exemplary embodiment, the 'stored' object 1910 may include icons, pop-up windows, and the like.

As another example, the external device 30 may automatically store content at regular intervals. In other words, even if there is no request from the user 20, the external device 30 can automatically store the executed content at regular intervals.

When the content is stored, the external device 30 notifies the wearable device 10 that the content has been stored in operation 1920.

When a notification is received from the external device 30, the wearable device 10 calculates The distance between the wearable device 10 and the external device 30. For example, the wearable device 10 may output a specific signal, may receive a signal that is a signal reflected from the external device 30, and may calculate a distance between the wearable device 10 and the external device 30 by using the received signal.

Alternatively, the wearable device 10 may calculate the wearable device 10 and the wearable device 10 by using the strength of the signal received from the external device 30 and a received signal strength indicator (RSSI) value corresponding to the strength of the signal. The distance between the external devices 30. For example, when it is assumed that the wearable device 10 and the external device 30 are connected by using a wireless communication method (such as Bluetooth, Wi-Fi, etc.), the wearable device 10 may calculate the strength. Then, the wearable device 10 may calculate a distance between the wearable device 10 and the external device 30 by using an RSSI value corresponding to the strength of the radio signal.

Then, the wearable device 10 determines whether the calculated distance is equal to or smaller than a predetermined value. For example, when it is assumed that the distance between the wearable device 10 and the external device 30 is A cm, the wearable device 10 determines whether the A cm is equal to or less than a predetermined value.

If the wearable device 10 determines that the A cm is equal to or less than a predetermined value, the wearable device 10 generates an encoding key and transmits the encoding key to the external device 30 in operation 1930.

Alternatively, the wearable device 10 may not calculate the distance between the wearable device 10 and the external device 30. In other words, if the wearable device 10 receives a notification about the storage of the content from the external device 30, the wearable device 10 can directly generate an encoding key and can transmit the encoding key to the external device 30.

As described above with reference to FIGS. 18 and 19, if the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value, the wearable device 10 may generate an encoding key, but one or more exemplary The embodiment is not limited thereto. That is, if the wearable device 10 and the external device 30 are connected to each other, the wearable device 10 can generate the encoding key without calculating the distance between the wearable device 10 and the external device 30.

Referring back to FIG. 4, in operation 490, the external device 30 encodes the content by using the encoding key. For example, the external device 30 may encode content by using a symmetric key algorithm or an asymmetric key algorithm. Furthermore, the external device 30 may store the encoded content.

Referring to the above description with reference to FIGS. 4 to 19, after the external device 30 stores the content, the wearable device 10 generates an encoding key and transmits the encoding key to the external device 30. However, one or more exemplary embodiments are not limited thereto. In other words, when the external device 30 executes a program for executing content, the wearable device 10 may generate an encoding key. Alternatively, when the external device 30 exits a program for executing content, the wearable device 10 may generate an encoding key.

Hereinafter, an example regarding the time when the wearable device 10 generates the encoding key is described with reference to FIGS. 20 to 23.

FIG. 20 is a flowchart illustrating an example in which the wearable device 10 generates an encoding key and the external device 30 encodes content according to another exemplary embodiment.

The exemplary embodiment of FIG. 20 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 20.

Comparing the flowchart of FIG. 20 with the flowchart of FIG. 4, the time when the wearable device 10 generates the encoding key is different. In other words, in the flowchart of FIG. 4, after the external device 30 stores the content, the wearable device 10 generates an encoding key. On the other hand, in the flowchart of FIG. 20, after the external device 30 executes a program, the wearable device 10 generates an encoding key. According to an exemplary embodiment, the program refers to a program used by the external device 30 to execute content.

In operation 2010, the wearable device 10 and the external device 30 are connected to each other. According to the exemplary embodiment, a connection indication data exchange is possible in between. For example, the wearable device 10 and the external device 30 may be connected to each other by using a wireless or wired communication method, and an example of the wireless and wired communication method is described above with reference to FIG. 1.

In operation 2020, the wearable device 10 obtains user information. For example, the user information may be biological information of the user 20 or account information of the user 20.

In operation 2030, the wearable device 10 authenticates the user 20 by using the user information. For example, the wearable device 10 may identify the user 20 by determining whether the obtained user information matches the pre-stored user information.

The wearable device 10 may authenticate the user 20 only before the wearable device 10 generates the encoding key, or may authenticate the user 20 regardless of the generation of the encoding key. That is, although the wearable device 10 generates an encoding key according to a result of user authentication, if the encoding key has not been generated, the wearable device 10 may perform user authentication without a time limit.

In operation 2040, the external device 30 executes a program to execute content. The time when the external device 30 executes the program does not depend on the wearable device 10 User 20 time. In other words, the external device 30 may execute the program after the wearable device 10 authenticates the user 20, or the wearable device 10 may authenticate the user 20 after the external device 30 executes the program.

In operation 2050, the external device 30 notifies the wearable device 10 that the program has been executed.

In operation 2060, the wearable device 10 generates an encoding key for encoding content. For example, the wearable device 10 may generate an encoding key for a symmetric key algorithm or may generate an encoding key for an asymmetric key algorithm. Referring to FIG. 20, when the wearable device 10 receives a notification about an executed program from the external device 30, the wearable device 10 automatically generates an encoding key without receiving input from the user 20, but a One or more exemplary embodiments are not limited thereto. That is, the wearable device 10 may generate an encoding key according to the selection of the user 20. According to an exemplary embodiment, the selection of the user 20 refers to whether the user 20 selects whether to encode the content (for example, whether to generate an encoding key).

In operation 2070, the wearable device 10 stores the encoding key. The wearable device 10 may not store independently but may directly delete the generated encoding key.

In operation 2080, the wearable device 10 transmits an encoding key to the external device 30.

In operation 2090, the external device 30 stores the content. That is, the external device 30 stores content executed by a program. The stored content can be unencoded.

In operation 2095, the external device 30 encodes the content by using an encoding key. For example, the external device 30 may encode content by using a symmetric key algorithm or an asymmetric key algorithm. Furthermore, the external device 30 may store the encoded content.

In operation 2090 to operation 2095, the external device 30 stores uncoded Original content and then encode the original content. The external device 30 may then store the encoded content. In other words, the unencoded original content and the encoded content may be stored in the external device 30.

Although not illustrated in FIG. 20, the external device 30 may encode the content and then may store the encoded content. In other words, operations 2090 and 2095 are interchangeable.

Hereinafter, an example in which the wearable device 10 generates an encoding key when the external device 30 executes a program is described in detail with reference to FIG. 21.

FIG. 21 illustrates an example in which the wearable device 10 generates an encoding key when the external device 30 executes a program according to an exemplary embodiment.

First, the external device 30 executes a program. For example, if the content is a document file, the external device 30 may execute the document file execution program. According to an exemplary embodiment, the document file execution program may indicate, but is not limited to, MS-Office word, Google DOCS, and the like.

When the user 20 selects the object 2110 to be output to the screen of the external device 30, the program can be executed. According to an exemplary embodiment, the object 2110 may include an icon, a pop-up window, and the like.

When the program is executed, the external device 30 notifies the wearable device 10 that the program has been executed in operation 2120.

When receiving the notification from the external device 30, the wearable device 10 may output a pop-up window 2130 to ask the user 20 whether to generate an encoding key. When the wearable device 10 receives a user input requesting to generate an encoding key via the user input unit 5310, the wearable device 10 generates an encoding key. Then, in operation 2140, the wearable device 10 transmits the generated encoding key to the external device 30.

Alternatively, the wearable device 10 may not ask the user 20 whether the product is produced. Health encoding key. In other words, if the wearable device 10 receives a notification about the execution of the program from the external device 30, the wearable device 10 can directly generate the encoding key and can transmit the generated encoding key to the external device 30.

FIG. 22A is a flowchart illustrating an example in which the wearable device 10 generates an encoding key and the external device 30 encodes content according to another exemplary embodiment.

The exemplary embodiment of FIG. 22A includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 22A.

Comparing the flowchart of FIG. 22A with the flowchart of FIG. 4, the time when the wearable device 10 generates the encoding key is different. In other words, in the flowchart of FIG. 22A, after the external device 30 executes a program, the wearable device 10 generates an encoding key. According to an exemplary embodiment, the program refers to a program used by the external device 30 to execute content.

In operation 2210, the wearable device 10 and the external device 30 are connected to each other. According to the exemplary embodiment, a connection indication data exchange is possible in between. For example, the wearable device 10 and the external device 30 may be connected to each other by using a wireless or wired communication method, and an example of the wireless and wired communication method is described above with reference to FIG. 1.

In operation 2220, the wearable device 10 obtains user information. For example, the user information may be biological information of the user 20 or account information of the user 20.

In operation 2230, the wearable device 10 authenticates the user 20 by using the user information. For example, the wearable device 10 may be obtained by determining The user 20 is identified by whether the user information matches the pre-stored user information.

The wearable device 10 may authenticate the user 20 only before the wearable device 10 generates the encoding key, or may authenticate the user 20 regardless of the generation of the encoding key. That is, although the wearable device 10 generates an encoding key according to a result of user authentication, if the encoding key has not been generated, the wearable device 10 may perform user authentication without a time limit.

In operation 2240, the external device 30 exits the program executing the content. The time when the external device 30 exits the program does not depend on the time when the wearable device 10 authenticates the user 20. In other words, the external device 30 may exit the program after the wearable device 10 authenticates the user 20, or the wearable device 10 may authenticate the user 20 after the external device 30 exits the program. Furthermore, the external device 30 may execute the program at any time before the external device 30 exits the program.

In operation 2250, the external device 30 notifies the wearable device 10 that the program has ended.

In operation 2260, the wearable device 10 generates an encoding key for encoding content. For example, the wearable device 10 may generate an encoding key for a symmetric key algorithm or may generate an encoding key for an asymmetric key algorithm. Referring to FIG. 22A, when the wearable device 10 receives a notification about the terminated program from the external device 30, the wearable device 10 automatically generates an encoding key without receiving input from the user 20, but a One or more exemplary embodiments are not limited thereto. That is, the wearable device 10 may generate an encoding key according to the selection of the user 20. According to an exemplary embodiment, the selection of the user 20 refers to whether the user 20 selects whether to encode the content (for example, whether to generate an encoding key).

In operation 2270, the wearable device 10 stores the encoding key. Wearable The wearable device 10 may not store independently but may directly delete the generated encoding key.

In operation 2280, the wearable device 10 transmits an encoding key to the external device 30.

In operation 2290, the external device 30 stores the content. That is, the external device 30 stores content executed by a program. The stored content can be unencoded.

In operation 2295, the external device 30 encodes the content by using an encoding key. For example, the external device 30 may encode content by using a symmetric key algorithm or an asymmetric key algorithm. Furthermore, the external device 30 may store the encoded content.

In operations 2290 to 2295, the external device 30 stores the unencoded original content and then encodes the original content. The external device 30 may then store the encoded content. In other words, the unencoded original content and the encoded content may be stored in the external device 30.

The external device 30 may encode the content and then may store the encoded content. In other words, operations 2290 and 2295 are interchangeable.

Hereinafter, an example in which the wearable device 10 generates an encoding key when the external device 30 exits the program is described in detail with reference to FIG. 22B.

FIG. 22B illustrates an example in which the wearable device 10 generates an encoding key when the external device 30 exits a program, according to an exemplary embodiment.

First, the external device 30 exits the program. For example, if the content is a document file, the external device 30 may exit the document file execution program. According to an exemplary embodiment, the document file execution program may indicate, but is not limited to, MS-Office word, Google DOCS, and the like.

When the user 20 selects an object 2320 displayed on the execution screen 2310 of the program, the program may end. According to an exemplary embodiment, the object 2320 may include a figure Display, pop-up windows, etc.

When the program ends, the external device 30 notifies the wearable device 10 that the program has ended in operation 2330.

When receiving the notification from the external device 30, the wearable device 10 may output a pop-up window 2340 to ask the user 20 whether to generate an encoding key. When the wearable device 10 receives a user input requesting to generate an encoding key via the user input unit 5310, the wearable device 10 generates an encoding key. Then, in operation 2350, the wearable device 10 transmits the generated encoding key to the external device 30.

Alternatively, the wearable device 10 may not ask the user 20 whether to generate an encoding key. In other words, if the wearable device 10 receives the notification of the end of the program from the external device 30, the wearable device 10 can directly generate the encoding key and can transmit the generated encoding key to the external device 30.

FIG. 23A is a flowchart illustrating an example in which the wearable device 10 generates an encoding key and the external device 30 encodes content according to another exemplary embodiment.

The exemplary embodiment of FIG. 23A includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 23A.

In operation 2211, the wearable device 10 and the external device 30 are connected to each other. An example of the connection between the wearable device 10 and the external device 30 is described above with reference to operation 2210 shown in FIG. 22A.

In operation 2221, the wearable device 10 obtains user information. For example, the user information may be biological information of the user 20 or account information of the user 20.

In operation 2231, the wearable device 10 authenticates the user 20 by using the user information. An example in which the wearable device 10 authenticates the user 20 is described above with reference to operation 2230 in FIG. 22A.

In operation 2241, the wearable device 10 generates an encoding key for encoding content. An example in which the wearable device 10 generates an encoding key is described above with reference to operation 2260 in FIG. 22A.

In operation 2251, the wearable device 10 transmits an encoding key to the external device 30.

In operation 2261, the external device 30 encodes the content by using an encoding key. In other words, after receiving the encoding key, the external device 30 may generate, execute, store, or to transmit the content to another external device by encoding using a previously transmitted encoding key. Hereinafter, an example in which the external device 30 encodes content is described with reference to FIG. 23B.

FIG. 23B illustrates an example in which the external device 30 encodes content by using a pre-received encoding key according to an exemplary embodiment.

Referring to FIG. 23B, after the user authentication is completed, the wearable device 10 may output a pop-up window 2341 to ask the user 20 whether to generate an encoding key. When the wearable device 10 receives a user input requesting to generate an encoding key via the user input unit 5310, the wearable device 10 generates an encoding key. Then, in operation 2351, the wearable device 10 transmits an encoding key to the external device 30.

Alternatively, the wearable device 10 may not ask the user 20 whether to generate an encoding key. In other words, if the wearable device 10 receives the notification of the end of the program from the external device 30, the wearable device 10 can directly generate the encoding key and can transmit the generated encoding key to the external device 30.

The external device 30 may store the encoding key received from the wearable device 10, and may store content generated, executed, stored, or to be transmitted to another external device using the stored encoding key after storing the encoding key.

For example, when the external device 30 stores the generated or executed content after the encoding key is transmitted to the external device 30 in operation 2361, the external device 30 may encode the content by using the encoding key received from the wearable device 10 . According to an exemplary embodiment, execution of the content includes reading or changing the content. As another example, when the external device 30 exits the executed program after the encoding key is transmitted to the external device 30 in operation 2321, the external device 30 may encode the content by using the encoding key received from the wearable device 10 .

When the external device 30 transmits content to another external device after the encoding key is transmitted to the external device 30, the external device 30 may encode the content by using the encoding key received from the wearable device 10.

In another exemplary embodiment, when the program is executed in the external device 30 and the wearable device 10 receives a notification about the execution of the program, the wearable device 10 may generate Encoding key. Then, when the external device 30 exits the program and transmits a notification about the end of the program to the wearable device 10, the wearable device 10 may transmit the generated encoding key to the external device 30. Thereby, the content executed in the program of the external device 30 can be encoded.

In another exemplary embodiment, the encoding key may be generated by the wearable device 10 at a random point in time. In the case where the encoding key has been generated by the wearable device 10, the wearable device 10 is wearable if it receives a prior notification from the external device 30 regarding the storage of content generated or edited by the external device 30 The portable device 10 may transmit the encoding key to the external device 30. Then, the external device 30 may The content can be encoded by using the received encoding key and the encoded content can be stored. Alternatively, in the case where the encoding key has been generated by the wearable device 10, if the wearable device 10 receives a pre-notification related to the transmission of content to the cloud server from the external device 30, the wearable device 10 can transmit the encoding key to the external device 30. Then, the external device 30 may encode the content by using the received encoding key and may transmit the encoded content to the cloud server.

Hereinafter, FIGS. 24 to 26 illustrate examples in which the external device 30 encodes content, which examples are described with reference to operation 490 of FIG. 4, operation 2095 of FIG. 20, operation 2295 of FIG. 22A, and operation 2261 of FIG. 23A.

FIG. 24 is a flowchart illustrating an example in which the external device 30 encodes content according to an exemplary embodiment.

The exemplary embodiment of FIG. 24 includes operations processed by the external device 30 shown in FIG. 1 in chronological order. Therefore, for the description related to the external device 30 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 24.

In operation 2410, the external device 30 encodes the content by using the received encoding key. For example, the external device 30 may encode content by using a symmetric key algorithm or an asymmetric key algorithm.

A symmetric key algorithm is an algorithm that performs encoding and decoding by using the same cryptographic key. Therefore, by using the encoding key received from the wearable device 10, the external device 30 can encode the content and can decode the encoded content.

The asymmetric key algorithm is an algorithm that performs encoding and decoding by using encoding keys and decoding keys different from each other. Therefore, the external device 30 may encode the content by using the encoding key received from the wearable device 10, and may decode the encoded internal content only after the external device 30 receives the independent decoding key from the wearable device 10. Content.

The details of the symmetric key algorithm and the asymmetric key algorithm are well known to those skilled in the art, and therefore detailed descriptions are omitted below.

In operation 2420, the external device 30 matches the encoding key with the wearable device 10 transmitting the encoding key, and stores the matching information. Hereinafter, an example in which the external device 30 matches the encoding key with the wearable device 10 and stores the matching information is described with reference to FIG. 25.

FIG. 25 illustrates an example in which an external device 30 matches an encoding key with a wearable device 10 and stores matching information according to an exemplary embodiment.

FIG. 25 illustrates an example of the external device 30 and the memory 5370 included in the external device 30.

The external device 30 can encode the content, can match the encoding key and the name of the wearable device 10, and can store the encoding key and the name. For example, if it is assumed that the external device 30 receives the encoding key 'En_Key 1' from the first wearable device, and the content 'abc.doc' is encoded by using the encoding key 'En_Key 1', the external device 30 can match The first wearable device and the encoding key 'En_Key 1' and the content 'abc.doc', and this information can be stored in the memory 31. Therefore, even if the external device 30 receives an encoding key from a different wearable device, or an encoding key from one wearable device, the external device 30 can still identify which one by using the encoding key received from the wearable device The content is encoded.

The external device 30 may transmit information to a server or a wearable device that transmits an encoding key, wherein the information (for example, the name of the wearable device, the title of the content, and the information in which the encoding key matches) are stored in the memory 31 in.

FIG. 26 illustrates an example in which the external device 30 transmits Examples of distributing information to the server 2610 or the wearable device 10.

Referring to FIG. 26, the external device 30 may transmit information including the title of the matched content, the encoding key, and the name of the wearable device 10 to the server 2610 or the wearable device 10. According to an exemplary embodiment, the wearable device 10 that receives information from the external device 30 is a body that transmits an encoding key to the external device 30.

The external device 30 may transmit the matching information to the server 2610, and the server 2610 may transmit the matching information back to the external device 30 according to a request from the external device 30.

FIG. 27 illustrates an example in which the wearable device outputs an alert when the external device 30 has finished encoding the content according to an exemplary embodiment.

FIG. 27 illustrates different cases in which an alarm is output according to the type of a wearable device. FIG. 27 illustrates the watch 2710, the glasses 2720, the wristband 2730, and the ring 2740 as the types of wearable devices, but the types of the wearable devices are not limited thereto. In other words, any type of wearable device that can be attached to the body of the user 20 may be used. Further, referring to FIG. 27, each of the wearable devices outputs one type of alarm, but one or more exemplary embodiments are not limited thereto. That is, a wearable device can output various types of alarms.

When the external device 30 has finished encoding the content, the external device 30 may notify the wearable devices 2710, 2720, 2730, and 2740 that the encoding of the content is completed. Then, the wearable devices 2710, 2720, 2730, and 2740 output an alarm so that the user 20 can be notified that the encoding of the content has been completed.

For example, the wearable device 2710 may output a pop-up window 2711 on the screen of the wearable device 2710 indicating that the encoding of the content is completed. As another example, the wearable device 2720 may be input through a speaker of the wearable device 2720. The audio indicating that the encoding of the content has been completed is output. As another example, the wearable device 2730 may generate vibration by using a vibration motor, and thus may notify the user 20 that the encoding of the content is completed. As another example, the wearable device 2740 may emit light, and thus may notify the user 20 that the encoding of the content is complete.

As described above with reference to FIG. 1, the wearable device 10 may generate not only an encoding key but also a decoding key. According to an exemplary embodiment, the decoding key is used for decoding of content encoded by using an encoding key generated by the wearable device 10.

Hereinafter, an example in which the wearable device 10 generates a decoding key and the external device 30 decodes content is described with reference to FIGS. 28 to 40.

FIG. 28 is a flowchart illustrating an example in which the wearable device 10 generates a decoding key and the external device 30 decodes content according to an exemplary embodiment.

The exemplary embodiment of FIG. 28 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 28.

In operation 2810, the wearable device 10 and the external device 30 are connected to each other. According to an exemplary embodiment, a connection refers to a connection by which data exchange can be performed. For example, the wearable device 10 and the external device 30 may be connected to each other by using a wireless or wired communication method, and an example of the wireless and wired communication method is described above with reference to FIG. 1.

If multiple devices can be connected to the wearable device 10, the wearable device 10 can select one of the multiple devices and can maintain a connection with the selected device. Examples in which the wearable device 10 and the external device 30 are connected to each other are described above with reference to FIGS. 4 to 7.

In operation 2820, the external device 30 selects the encoded content. In other words, the external device 30 selects encoding target content from among a plurality of encoded contents stored in the external device 30. For example, the external device 30 may receive a user input requesting execution of the encoded content, and may select the encoded content according to the user input.

In operation 2830, the external device 30 notifies the wearable device 10 that the encoded content has been selected.

In operation 2840, the wearable device 10 generates a decoding key by using the stored encoding key. For example, the wearable device 10 may generate an encoding key and may store the generated encoding key in the memory 5370. As another example, when the wearable device 10 receives the notification described in operation 2830, the wearable device 10 may also receive the encoding key from the external device 30.

In operation 2850, the wearable device 10 transmits a decoding key to the external device 30.

In operation 2860, the external device 30 decodes the encoded content by using a decoding key.

Referring to FIG. 28, the external device 30 decodes the encoded content by using a decoding key received from the wearable device 10, but the external device 30 may previously use the encoding key transmitted from the wearable device 10 to the external device 30 Decode the encoded content. For example, when the external device 30 decodes the content by using a symmetric key algorithm, the external device 30 can decode the content by using an encoding key received in advance from the wearable device 10. In this case, the wearable device 10 may not transmit a decoding key to the external device 30 but may transmit a signal to the external device 30 in order to allow decoding of the content.

Hereinafter, the flowchart of FIG. 28 will be described in detail with reference to FIGS. 29 and 30.

29 and 30 illustrate a wearable device therein according to an exemplary embodiment The device 10 generates an example of a decoding key and transmits the decoding key to the external device 30.

First, referring to FIG. 29, the external device 30 notifies the wearable device 10 that the encoded content has been selected. For example, when the user 20 requests the external device 30 to execute the content 'abc.doc' as the encoded content, the external device 30 notifies the wearable device 10 of the encoded content 'abc.doc' in operation 2910 select. According to the exemplary embodiment, execution of the content refers to a case where the user 20 executes the content in order to read, edit, or delete the content.

When receiving the notification from the external device 30, the wearable device 10 reads the encoding key En_Key 1 stored in the memory 11. In this example, the read encoding key En_Key 1 refers to an encoding key used to encode the content 'abc.doc'.

The wearable device 10 generates a decoding key De_Key 1 by using the read encoding key En_Key 1 in operation 2920. The method performed by the wearable device 10 to generate the decoding key De_Key 1 is well known to those skilled in the art, and therefore its detailed description is omitted below.

In operation 2930, the wearable device 10 transmits the decoding key De_Key 1 to the external device 30. The external device 30 decodes the encoded content 'abc.doc' by using the decoding key De_Key 1, and executes the decoded content 'abc.doc'.

If the user 20 is not wearing the wearable device 10, the wearable device 10 may use a preset password (for example, a password for user authentication). For example, based on user input for entering a preset password, the wearable device 10 can obtain a decoding key stored in the memory 5370 and can decode the content by using the obtained decoding key.

Referring to FIG. 30, as described above with reference to FIG. 29, in operation 3010, the external device 30 notifies the wearable device 10 that the encoded content has been selected and is operating. The wearable device 10 in operation 3030 generates a decoding key De_Key 1 by using the encoding key En_Key 1 read from the memory 11. Then, the wearable device 10 transmits the decoding key De_Key 1 to the external device 30 in operation 3040, and the external device 30 decodes the encoded content by using the decoding key De_Key 1.

However, the wearable device 10 shown in FIG. 30 can match the title of the content and the encoding key and can store the matched information in the memory 11. For example, when the encoding key En_Key 1 is assumed to be used to encode the content 'abc.doc', the wearable device 10 can match the encoding key En_Key 1 with the content 'abc.doc' and can store matching information. Therefore, the wearable device 10 can easily identify the content to be decoded, and an encoding key for encoding the content.

FIG. 31 is a flowchart illustrating an example in which the wearable device 10 generates a decoding key and transmits the decoding key to the external device 30 according to another exemplary embodiment.

The exemplary embodiment of FIG. 31 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 1 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 31.

Operations 3110 to 3130 and operations 3160 to 3180 in FIG. 31 are the same as operations 2810 to 2860 in FIG. 28, and therefore, detailed descriptions thereof are omitted here.

In operation 3140, the wearable device 10 obtains user information. Then, in operation 3150, the wearable device 10 authenticates the user 20 by using the user information.

For example, the user information may be biological information of the user 20 or account information of the user 20. Alternatively, the wearable device 10 may identify the user 20 by determining whether the obtained user information matches the pre-stored user information.

Hereinafter, an example in which the wearable device 10 obtains user information and authenticates the user is described with reference to FIGS. 32 to 37.

FIG. 32 illustrates an example in which the wearable device 10 obtains user information to generate a decoding key according to an exemplary embodiment.

First, the external device 30 selects the encoded content. In other words, the external device 30 selects a decoding target content from a plurality of encoded contents stored in the external device 30. For example, the external device 30 may receive user input to select the object 3210 indicating the encoded content, and may select the encoded content according to the user input. When the encoded content is selected, the external device 30 notifies the wearable device 10 that the encoded content has been selected in operation 3220.

When the wearable device 10 receives a notification from the external device 30, the wearable device 10 requests the user 20 to input user information. For example, the wearable device 10 may output a pop-up window 3230 to request the user 20 to input user information.

FIG. 33 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 to generate a decoding key according to an exemplary embodiment.

The exemplary embodiment of FIG. 33 includes operations processed by the wearable device 10 shown in FIG. 1 in chronological order. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 33.

In operation 3310, the wearable device 10 obtains biological information from the user 20.

In operation 3320, the wearable device 10 obtains an ID and a password from the user 20.

In operation 3330, the wearable device 10 performs user authentication based on the obtained biometric information and at least one of the obtained ID and password. That is, the wearable device 10 may perform user authentication by using biometric information or by using ID and password. Alternatively, the wearable device 10 may perform user authentication by using all biometric information and ID and password.

The wearable device 10 may authenticate the user 20 only before the wearable device 10 generates a decoding key, or may authenticate the user 20 regardless of the generation of the decoding key. In other words, although the wearable device 10 generates an encoding key according to a result of user authentication, if the encoding key has not been generated, the wearable device 10 may perform user authentication without a time limit.

For example, before the wearable device 10 generates and transmits a decoding key to the external device 30, the wearable device 10 can perform user authentication. Alternatively, when a program providing content is executed or ended in the external device 30, the wearable device 10 may automatically perform user authentication within a preset period of time. Alternatively, when the wearable device 10 is connected with the external device 30 for communication, the wearable device 10 may automatically perform user authentication within a preset period of time. Alternatively, when the wearable device 10 determines that the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined distance, the wearable device 10 may automatically perform user authentication within a preset period of time.

As described above, if the user authentication is performed before the decoding key is transmitted to the external device 30, the user 20 can feel that the content decoding time is reduced.

FIG. 34 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 to generate a decoding key by using the biometric information of the user 20 according to an exemplary embodiment.

In operation 3410, the wearable device 10 obtains biological information of the user 20. Here, the biological information may refer to information about at least one of a fingerprint, an iris, a retina, a vein, a skeletal part, and a face of the user 20. For example, the wearable device 10 may obtain information about the fingerprint, vein, or skeleton portion of the user 20 by using a sensor included in the sensing unit 5350, and may use the A / V input by using The camera in unit 5360 obtains information about the iris, retina, or face of the user 20.

In operation 3420, the wearable device 10 determines whether the biological information matches the pre-stored biological information. In other words, the wearable device 10 may store the biological information of the user 20 in the memory 5370, and then may determine whether the biological information obtained from the user 20 matches the biological information stored in the memory 5370.

When the wearable device 10 determines that the obtained biological information matches the pre-stored biological information, the wearable device 10 performs operation 3430, and if it does not match, the wearable device 10 ends the procedure.

In operation 3430, the wearable device 10 determines that the user 20 is authenticated.

FIG. 35 illustrates an example in which the wearable device 10 authenticates the user 20 by using the face information of the user 20 according to an exemplary embodiment.

The example in which the wearable device 10 identifies the user 20 by using the biometric information of the user 20 is not limited to the exemplary embodiment of FIG. 35. In other words, the wearable device 10 can authenticate the user 20 by using the method with respect to the examples of FIGS. 11 to 13. Furthermore, the wearable device 10 can obtain the fingerprint information of the user 20 by using a sensor, and can identify the user 20 by comparing the fingerprint information with the pre-stored fingerprint information of the user 20.

The wearable device 10 obtains face information of the user 20. For example, the wearable device 10 may obtain a face image 3510 of the user 20 by using a camera configured at the wearable device 10.

The wearable device 10 searches the user information in the memory 11 for an image 3520 corresponding to the face image 3510 of the user 20. According to an exemplary embodiment, the image 3520 contains information related to the position of the eyes, nose, and mouth, face contours, or other face information shown in the face image 3510.

The wearable device 10 extracts features from the face image 3510 and extracts features from the image 3520 stored in the memory 11. Then, the wearable device 10 searches for the image 3520 of the user 20 corresponding to the face image 3510 and among a plurality of information blocks stored in the memory 11, and the wearable device 10 compares the extracted features. Alternatively, the wearable device 10 may convert the face features of the user 20 into data in advance, may store the data, and may compare the stored data with features extracted from the face image 3510.

As a search result, if the image 3520 corresponding to the face image 3510 is stored in the memory 11 (or alternatively, if the data corresponding to the feature extracted from the face image 3510 is stored in the memory 11), the wearable device 10 determines that the user 20 is identified. In this case, the wearable device 10 may output a pop-up window 3530 indicating that the user authentication has been completed.

FIG. 36 is a flowchart illustrating an example in which the wearable device 10 authenticates the user 20 to generate a decoding key by using the account information of the user 20 according to an exemplary embodiment.

In operation 3610, the wearable device 10 obtains account information of the user 20. According to an exemplary embodiment, the account information may include the unique ID and password. For example, the wearable device 10 may obtain an ID and a password from the user 20 via the user input unit 5310.

In operation 3620, the wearable device 10 determines whether the obtained account information matches the pre-stored information. That is, the wearable device 10 may store the ID and password of the user 20 in the memory 5370, and may determine whether the ID and password obtained from the user 20 later match the ID and password stored in the memory 5370. .

If the wearable device 10 determines that the obtained account information matches the pre-stored information, the wearable device 10 performs operation 3630, and if it does not match, the wearable device 10 ends the procedure.

In operation 3630, the wearable device 10 determines that the user 20 is authenticated.

FIG. 37 illustrates an example in which the wearable device 10 authenticates the user 20 by using the ID and password of the user 20 according to an exemplary embodiment.

The wearable device 10 outputs a pop-up window 3710 to the user 20 so as to request the user 20 to input the ID and password, and the user 20 inputs the ID 'Samsung_1' and the password '1234' via the user input unit 5310.

The wearable device 10 compares the ID 'Samsung_1' and the password '1234' input by the user 20 with the ID and the password 3720 stored in the memory 11. If the wearable device 10 determines that the input ID and password match the stored ID and password 3720, the wearable device 10 determines that the user 20 is authenticated. In this case, the wearable device 10 may output a pop-up window 3730 indicating that the user authentication is completed.

FIG. 38 is a flowchart of an example in which the wearable device 10 generates a decoding key and transmits the generated decoding key to the external device 30 according to an exemplary embodiment.

In operation 3820, the wearable device 10 determines whether the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value. In other words, the wearable device 10 calculates the distance between the wearable device 10 and the external device 30 and determines whether the distance is equal to or smaller than a predetermined value.

When the user 20 executes content by using the external device 30, in general, the user 20 and the external device 30 are adjacent to each other by having a small distance therebetween. Therefore, the distance between the user 20 and the external device 30 may be a standard, and the user 20 determines whether to execute the content by using the external device 30 by using the standard.

Since the wearable device 10 according to an exemplary embodiment of the present invention can obtain biometric information to perform user authentication, it is assumed in this case that the user 20 is currently wearing the wearable device 10. Therefore, if the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value, the user 20 and the external device 30 can be positioned adjacent to each other.

Therefore, by determining whether the distance between the wearable device 10 and the external device 30 is equal to or less than a predetermined value, it is possible to prevent the decoding key from being generated by someone other than the user 20.

In operation 3820, the wearable device 10 generates a decoding key. Then, in operation 3830, the wearable device 10 transmits a decoding key to the external device 30.

Hereinafter, the exemplary embodiment of FIG. 38 is described in detail with reference to FIG. 39.

FIG. 39 illustrates an example of a condition under which the wearable device 10 generates a decoding key according to an exemplary embodiment.

First, the external device 30 selects the encoded content. In other words, the external device 30 selects a decoding target content from a plurality of encoded contents stored in the external device 30. For example, the external device 30 may receive an object indicating selection of encoded content 3210 user input, and coded content can be selected based on user input. When the encoded content is selected, the external device 30 notifies the wearable device 10 that the encoded content has been selected in operation 3920.

When the notification is received from the external device 30, the wearable device 10 calculates the distance between the wearable device 10 and the external device 30. For example, the wearable device 10 may output a specific signal, may receive a signal that is a signal reflected from the external device 30, and may calculate a distance between the wearable device 10 and the external device 30 by using the received signal. According to an exemplary embodiment, the description in which the wearable device 10 calculates the distance between the wearable device 10 and the external device 30 is described above with reference to FIG. 19.

Then, the wearable device 10 determines whether the calculated distance is equal to or smaller than a predetermined value. For example, when it is assumed that the distance between the wearable device 10 and the external device 30 is A cm, the wearable device 10 determines whether the A cm is equal to or less than a predetermined value.

If the wearable device 10 determines that A cm is equal to or less than a predetermined value, the wearable device 10 generates a decoding key and transmits the decoding key to the external device 30 in operation 3930.

Alternatively, the wearable device 10 may not calculate the distance between the wearable device 10 and the external device 30. In other words, if the wearable device 10 receives a notification about the selection of the encoded content from the external device 30, the wearable device 10 may directly generate a decoding key and may transmit the decoding key to the external device 30.

FIG. 40 illustrates an example in which the wearable device outputs an alarm when the external device 30 has completed decoding of the content according to an exemplary embodiment.

Figure 40 illustrates the difference in which an alarm is output depending on the type of wearable device Happening. FIG. 40 illustrates the watch 4010, the glasses 4020, the wristband 4030, and the ring 4040 as the types of wearable devices, but the types of the wearable devices are not limited thereto. In other words, any type of wearable device that can be attached to the body of the user 20 may be used. Also, referring to FIG. 40, each of the wearable devices outputs one type of alert, but one or more exemplary embodiments are not limited thereto. That is, a wearable device can output various types of alarms.

When the external device 30 has finished decoding the content, the external device 30 may notify the wearable devices 4010, 4020, 4030, and 4040 that the decoding of the content is completed. Then, the wearable devices 4010, 4020, 4030, and 4040 output alerts so that the user 20 can be notified that the decoding of the content has been completed.

For example, the wearable device 4010 may output a pop-up window 4011 on the screen of the wearable device 4010 indicating that the decoding of the content is completed. As another example, the wearable device 4020 may output an audio indicating that decoding of the content is completed via a speaker of the wearable device 4020. As another example, the wearable device 4030 may generate vibration by using a vibration motor, and thus may notify the user 20 that the decoding of the content is completed. As another example, the wearable device 4040 may emit light, and thus may notify the user 20 that decoding of the content is complete.

FIG. 41 illustrates an example in which the external device 30 generates an encoding key or a decoding key according to an exemplary embodiment.

Referring to FIGS. 1 to 40, the wearable device 10 authenticates the user 20 based on the user information, and generates an encoding key or a decoding key based on a result of the user authentication. Then, the external device 30 encodes or decodes the content. However, the wearable device 10 may perform only user authentication, and the external device 30 may generate an encoding key or a decoding key and may encode or decode the content based on a result of the user authentication.

Referring to FIG. 41, the wearable device 10 obtains user information from the user 20, and performs user authentication by using the user information. Then, the wearable device 10 transmits information about user authentication to the external device 30.

When receiving a notification about user authentication from the wearable device 10, the external device 30 generates an encoding key for encoding content, and encodes the content by using the encoding key. Hereinafter, an example in which the external device 30 generates an encoding key and encodes the content by using the encoding key is described with reference to FIGS. 42 to 45.

Furthermore, when receiving a notification about user authentication from the wearable device 10, the external device 30 generates a decoding key for decoding the content, and decodes the content by using the decoding key. Hereinafter, an example in which the external device 30 generates a decoding key and decodes the content by using the decoding key is described with reference to FIGS. 46 and 47.

FIG. 42 is a flowchart illustrating an example in which the wearable device 10 performs user authentication and transmits a result of the user authentication to the external device 10 according to an exemplary embodiment.

In operation 4210, the wearable device 10 obtains user information from the user 20.

The user information refers to information required by the wearable device 10 to identify the user 20 (eg, to identify the user 20). For example, the user information may be biological information of the user 20 or account information of the user 20. An example in which the wearable device 10 obtains user information is described above with reference to FIG. 1.

In operation 4220, the wearable device 10 identifies the user 20 based on the user information. For example, the wearable device 10 may identify the user 20 by comparing the input user information with pre-stored user information. The example in which the wearable device 10 authenticates the user 20 is described above with reference to FIG. 1.

In operation 4230, the wearable device 10 transmits user authentication information to the external device 30. According to an exemplary embodiment, the user authentication information refers to information indicating whether the user 20 has been authenticated.

FIG. 43 is a flowchart illustrating an example in which the external device 30 encodes content by using a user authentication result received from the wearable device 10 according to an exemplary embodiment.

The exemplary embodiment of FIG. 43 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 41 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 43.

Referring to FIG. 43, the external device 30 notifies the wearable device 10 that the content has been stored, and then, the wearable device 10 transmits user authentication information to the external device 30.

Operations 4310 to 4350 in FIG. 43 are the same as operations 410 to 450 in FIG. 4, and therefore, detailed descriptions of operations 4310 to 4350 are omitted here.

In operation 4360, the wearable device 10 transmits user authentication information to the external device 30. In other words, the wearable device 10 transmits information indicating whether the subject providing the user information is the user 20 to the external device 30.

In operations 4370 to 4390, the external device 30 generates an encoding key according to the result of user authentication, and encodes the content by using the encoding key. In operations 4370 and 4380, the method of generating and storing the encoding key (the method performed by the external device 30) and the method of generating and storing the encoding key (in the operations 460 and 470 of FIG. 4 by wearable The method performed by the device 10) is the same. Moreover, in FIG. 43 Operation 4390 is the same as operation 490 of FIG. 4. Therefore, detailed descriptions of operations 4370 to 4390 are omitted here.

FIG. 44 is a flowchart illustrating an example in which the external device 30 encodes content by using a user authentication result received from the wearable device 10 according to another exemplary embodiment.

The exemplary embodiment of FIG. 44 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 41 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 44.

Referring to FIG. 44, the external device 30 notifies the wearable device 10 that the program has been executed, and then, the wearable device 10 transmits user authentication information to the external device 30. According to an exemplary embodiment, the program refers to a program used by the external device 30 to execute content. For example, according to the type of content, the program may be a Microsoft word program, a Microsoft Excel program, a Microsoft PowerPoint program, a photo execution program, an image execution program, a video execution program, a music execution program, and the like.

Operations 4410 to 4450 in FIG. 44 are the same as operations 2010 to 2050 in FIG. 20, and therefore, detailed descriptions of operations 4410 to 4450 are omitted here.

In operation 4460, the wearable device 10 transmits user authentication information to the external device 30. In other words, the wearable device 10 transmits information indicating whether the subject providing the user information is the user 20 to the external device 30.

In operation 4470 to operation 4490, the external device 30 generates an encoding key according to the result of the user authentication, and encodes the content by using the encoding key. In operation In 4470 and operation 4480, the method of generating and storing the encoding key (the method performed by the external device 30) and the method of generating and storing the encoding key (in the operation 2060 and operation 2070 of FIG. 20 by the wearable device) 10 method of execution) is the same. Furthermore, operation 4490 of FIG. 44 is the same as operation 2095 of FIG. 20. Therefore, a detailed description about operations 4470 to 4490 is omitted here.

FIG. 45 is a flowchart illustrating an example in which the external device 30 encodes content by using a user authentication result received from the wearable device 10 according to another exemplary embodiment.

The exemplary embodiment of FIG. 45 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 41 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 45.

Referring to FIG. 45, the external device 30 notifies the wearable device 10 that the program has ended, and then, the wearable device 10 transmits user authentication information to the external device 30. According to an exemplary embodiment, the program refers to a program used by the external device 30 to execute content.

Operations 4510 to 4550 in FIG. 45 are the same as operations 2210 to 2250 in FIG. 22, and therefore, detailed descriptions of operations 4510 to 4550 are omitted here.

In operation 4560, the wearable device 10 transmits user authentication information to the external device 30. In other words, the wearable device 10 transmits information indicating whether the subject providing the user information is the user 20 to the external device 30.

In operations 4570 to 4590, the external device 30 generates an encoding key according to a result of user authentication, and encodes the content by using the encoding key. In operation In 4570 and operation 4580, the method of generating and storing the encoding key (the method performed by the external device 30) and the method of generating and storing the encoding key (in the operation 2260 and operation 2270 of FIG. 22 by the wearable device) 10 method of execution) is the same. Furthermore, operation 4590 of FIG. 45 is the same as operation 2295 of FIG. 22. Therefore, a detailed description about operations 4570 to 4590 is omitted here.

FIG. 46 is a flowchart illustrating an example in which the external device 30 generates a decoding key and decodes content according to an exemplary embodiment.

The exemplary embodiment of FIG. 46 includes operations processed by the wearable device 10 shown in FIG. 41 in chronological order. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 46.

Referring to FIG. 46, the external device 30 decodes the selected content without transmitting the notification to the wearable device 10 independently. That is, when content is selected by the user 20, the external device 30 generates a decoding key and decodes the selected content by using the decoding key. According to an exemplary embodiment, the selected content refers to encoded content.

Operations 4610 to 4630 in FIG. 46 are the same as operations 2820 to 2860 in FIG. 28, and therefore, detailed descriptions of operations 4610 to 4630 are omitted here.

In operation 4620, the external device 30 generates a decoding key by using the stored encoding key. For example, the external device 30 may generate a decoding key, and may store the decoding key in the memory 5370.

FIG. 47 is a flowchart illustrating an example in which the external device 30 generates a decoding key and decodes content according to another exemplary embodiment.

The exemplary embodiment of FIG. 47 includes The illustrated wearable device 10 handles the operations. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 41, the description is also applicable to the flowchart of FIG. 47.

Referring to FIG. 47, after the external device 30 receives user authentication information from the wearable device 20, the external device 30 generates a decoding key. As described above with reference to FIG. 46, the external device 30 decodes the selected content without transmitting the notification to the wearable device 10 independently. However, in the exemplary embodiment of the present invention of FIG. 47, when the external device 30 notifies the wearable device 10 that content has been selected and then receives user authentication information from the wearable device 20, the external device 30 decodes the content.

Operations 4710 to 4750 in FIG. 47 are the same as operations 3110 to 3150 in FIG. 31, and therefore, detailed descriptions of operations 4710 to 4750 are omitted here.

In operation 4760, the wearable device 10 transmits user authentication information to the external device 30. According to an exemplary embodiment, the user authentication information refers to information indicating whether the subject providing the user information is the user 20 or not.

In operation 4770, the external device 30 generates a decoding key by using the stored encoding key. In other words, if the subject providing the user information is the user 20, the external device 30 generates a decoding key.

Operation 4780 of FIG. 47 is the same as operation 3180 of FIG. 31. Therefore, a detailed description of the operation 4780 is omitted here.

FIG. 48 illustrates an example in which the wearable device 10 sets an access right to the external device 30 according to an exemplary embodiment.

As described above with reference to FIGS. 1 to 47, the wearable device 10 may determine whether to encode or decode content stored in the external device 30. In other words, only if Only when the wearable device 10 is currently worn by the user 20 can the wearable device 10 allow the content to be encoded or decoded. Therefore, the user 20 can execute the content only when the user 20 is currently wearing the wearable device 10.

Referring to FIG. 48, the wearable device 10 may assign the access right to the external device 30 to the user 20. In other words, the wearable device 10 can determine whether the user 20 is allowed to access the external device 30. For example, according to the result of user authentication, the wearable device 10 may activate the external device 30 so that the user 20 operates the external device 30. If the wearable device 10 determines that the access subject is not the user 20, the wearable device 10 may activate the external device 30. Therefore, the user 20 can use only the external device 30.

Hereinafter, an example in which the wearable device 10 assigns the access right to the external device 30 to the user 20 is described with reference to FIGS. 49 to 52.

FIG. 49 is a flowchart illustrating an example in which the wearable device 10 sets an access right to the external device 30.

The exemplary embodiment of FIG. 49 includes operations processed by the wearable device 10 shown in FIG. 48 in chronological order. Therefore, for a description related to the operation of the wearable device 10 shown in FIG. 1, the description can also be applied to the flowchart of FIG. 49.

Referring to operation 4910, the wearable device 10 performs user authentication by using the user information obtained from the user 20. The wearable device 10 may perform user authentication by comparing input user information with pre-stored user information. According to an exemplary embodiment, the user information may be biological information of the user 20 or account information of the user 20.

In operation 4920, the wearable device 10 is based on a user-identified result. As a result, information indicating the access right to the external device 30 is generated. The wearable device 10 then transmits the information to the external device 30.

Hereinafter, the exemplary embodiment of FIG. 49 is described in detail with reference to FIG. 50.

FIG. 50 is a flowchart illustrating an example in which the wearable device 10 sets an access right to the external device 30 based on a result of user authentication, according to an exemplary embodiment.

The exemplary embodiment of FIG. 50 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 48 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 50.

In operation 5010, the wearable device 10 and the external device 30 are connected to each other. According to an exemplary embodiment, a connection refers to a connection by which data exchange can be performed. For example, the wearable device 10 and the external device 30 may be connected to each other by using a wireless or wired communication method, and an example of the wireless and wired communication method is described above with reference to FIG. 1.

If multiple devices can be connected to the wearable device 10, the wearable device 10 can select one of the multiple devices and can maintain a connection with the selected device. An example in which the wearable device 10 maintains a connection with one of the plurality of devices is described with reference to FIGS. 5 to 7.

In operation 5020, the wearable device 10 obtains user information. According to an exemplary embodiment, the user information may be biological information of the user 20 or account information of the user 20.

In operation 5030, the wearable device 10 identifies the user 20 based on the user information. For example, the wearable device 10 may compare user information with Pre-register information to identify the user 20. Examples in which the wearable device 10 authenticates the user 20 are described above with reference to FIGS. 8 to 15.

In operation 5040, the wearable device 10 generates an indication that the access right is set to the access right information for the external device 30. According to an exemplary embodiment, the access right information activates the external device 30 in order to allow the user 20 to use the external device 30. In other words, when the user authentication fails, the right information is accessed to activate the external device.

For example, the access right information may be a key value for activating the external device 30. The format of the key value is not limited. The external device 30 can be activated only when the key value is transmitted from the wearable device 10.

In operation 5050, the wearable device 10 stores the access right information. Although not illustrated in FIG. 50, the wearable device 10 may not independently store the access right information but may directly delete the access right information.

In operation 5060, the wearable device 10 transmits the access right information to the external device 30.

In operation 5070, the external device 30 stores the access right information.

According to the exemplary embodiment of FIG. 50, the access right information is stored in the external device 30. Therefore, then, only the user 20 who has been authenticated by the user by the wearable device 10 can use the external device 30.

Hereinafter, referring to FIG. 51, an example in which the wearable device 10 determines whether to activate the external device 30 when a user 20 currently wearing the wearable device 10 attempts to use the external device 30.

FIG. 51 is a flowchart illustrating an example in which the wearable device 10 determines whether or not to activate the external device 30 for which the access right has been set, according to an exemplary embodiment.

The exemplary embodiment of FIG. 51 includes operations processed by the wearable device 10 and the external device 30 shown in FIG. 48 in chronological order. Therefore, for descriptions related to the operations of the wearable device 10 and the external device 30 shown in FIG. 1, the descriptions can also be applied to the flowchart of FIG. 51.

In operation 5110, the wearable device 10 and the external device 30 are connected to each other. An example in which the wearable device 10 and the external device 30 are connected to each other is described above with reference to operation 5010 of FIG. 50, and therefore, a detailed description thereof is omitted here.

In operation 5120, the external device 30 notifies the wearable device 10 that the external device 30 is a device storing the access right information. For example, when the user 20 attempts to use the external device 30, the external device 30 may notify the wearable device 10 that the external device 30 is a device that stores access rights information. According to an exemplary embodiment, the expression that the user 20 attempts to use the external device 30 may refer to a situation in which the user 20 inputs a command via the user input unit 5310 of the external device 30, and may refer to a situation in which the user 20 approaches the external device 30 so that the user The distance between 20 and the external device 30 is equal to or less than a predetermined distance, or may refer to many other types of situations in which the user 20 attempts to use the external device 30.

In operation 5130, the wearable device 10 reads the access right information. According to the above operation 5050 in FIG. 50, the wearable device 10 can generate and store access right information. Therefore, when transmitted from the external device 30 according to the notification of operation 5120, the wearable device 10 can read the stored access right information.

In operation 5140, the wearable device 10 transmits the access right information to the external device 30.

In operation 5150, the external device 30 matches the stored information with the received information. For example, when the access right information is assumed to be a key value, the external device 30 It can be determined whether the key value transmitted from the wearable device 10 matches the key value stored in the external device 30.

In operation 5160, the external device 30 is activated according to a result of the matching performed in operation 5150. For example, when the access right information is a key value, and if determined based on the result of the matching performed in operation 5150, the key value transmitted from the wearable device 10 and the key value stored in the external device 30 are If the key values match, the external device 30 is activated. Therefore, the user 20 can use the external device 30.

Before performing operation 5130, the wearable device 10 may perform user authentication. In other words, when receiving the notification according to operation 5120, the wearable device 10 may obtain user information from the user 20 and may perform user authentication based on the obtained user information. Then, the wearable device 10 can read the access right information according to the result of user authentication.

52 illustrates examples (a) and (b) in which whether the user 20 can use the external device 30 is determined according to whether the user 20 is currently wearing the wearable device 10 according to an exemplary embodiment.

Referring to example (a), the user 20 is currently wearing the wearable device 10. Therefore, the external device 30 can be activated and the user 20 can use the external device 30.

Referring to example (b), the user 20 is not currently wearing the wearable device 10. Therefore, the external device 30 can be deactivated, and the user 20 cannot use the external device 30.

One or more exemplary embodiments may be written as a computer program and may be implemented in a general-purpose digital computer that executes the program using a computer-readable recording medium.

The method can be executed by executing instructions contained in at least one of a plurality of programs recorded on a computer-readable recording medium. When instructions are executed in a computer At runtime, at least one program may perform a function corresponding to the instruction. Examples of instructions include not only machine code generated by a compiler but also code to be executed in a computer by using an interpreter. In one or more exemplary embodiments, the computer may include a processor, and the computer-readable recording medium may include a memory.

In addition, a data structure for one or more exemplary embodiments may be written in a computer-readable recording medium using various devices. Examples of the computer-readable recording medium include a magnetic storage medium (for example, ROM, RAM, USB, flexible disk, hard disk drive, etc.), an optical recording medium (for example, CD-ROM or DVD), and the like.

53 and 54 illustrate a structure of an example of a wearable device 10 or an external device 30 according to an exemplary embodiment.

The device 5300 shown in FIGS. 53 and 54 may correspond to the wearable device 10 or the external device 30 described above with reference to FIGS. 1 to 52.

Referring to FIG. 53, a device 5300 according to an exemplary embodiment of the present invention may include a user information obtainer 5380, an output unit 5320 (eg, an outputter), a controller 5330 (also referred to as a 'processor 5330'), and a communication unit 5340. (E.g. communicator). Furthermore, the user information obtainer 5380 shown in FIG. 53 may include a user input unit 5310 (for example, a user input device), a sensing unit 5350 (for example, a sensor), and an A / V input unit 5360 ( (For example, A / V input).

The user information obtainer 5380 obtains user information from the user 20. According to an exemplary embodiment, the user information may be biological information of the user 20 or account information of the user 20. The user information obtainer 5380 can obtain the account information of the user 20 through the user input unit 5310. Examples of the user input unit 5310 may include a keypad, a hemispherical switch, a touchpad, a jog wheel, an iog switch, and the like, and the user 20 can use the user input unit The ID and password entered by 5310 can be obtained as user information.

The user information obtainer 5380 can obtain the biological information of the user 20 by using the sensing unit 5350 or the A / V input unit 5360. For example, the wearable device 10 may obtain information about the fingerprint, vein, or skeleton portion of the user 20 by using a sensor included in the sensing unit 5350, and may use the A / V input by using The camera in unit 5360 obtains information about the iris, retina, or face of the user 20.

Referring to FIG. 53, the user information obtainer 5380 includes a user input unit 5310, a sensing unit 5350, and an A / V input unit 5360, but one or more exemplary embodiments are not limited thereto. For example, each of the user input unit 5310, the sensing unit 5350, and the A / V input unit 5360 of the user information obtainer 5380 shown in FIG. 53 may be independent elements in the device 5300. However, not all the elements shown in FIG. 53 are necessary elements of the wearable device 10 or the external device 30. That is, the wearable device 10 or the external device 30 may have more or fewer components than those shown in FIG. 53.

For example, referring to FIG. 54, the device 5300 according to the exemplary embodiment of the present invention may further include a memory 5370 and a user input unit 5310, an output unit 5320, a controller 5330, a communication unit 5340, a sensing unit 5350, and an A / V input unit 5360.

Further, referring to FIG. 53, the user information obtainer 5380 includes a user input unit 5310, a sensing unit 5350, and an A / V input unit 5360, but one or more exemplary embodiments are not limited thereto.

The user input unit 5310 may be a unit through which the user 20 inputs data in order to control the device 5300. For example, the user input unit 5310 Can include keypad, hemispherical switch, touchpad (capacitive touchpad, pressure resistive touchpad, infrared beam sensing touchpad, surface acoustic wave touchpad, integrated strain touch Board, piezoelectric effect touchpad, etc.), jog wheel, jog switch, etc., but one or more exemplary embodiments are not limited thereto.

For example, the user input unit 5310 may receive user information (for example, account information of the user 20). Furthermore, the user input unit 5310 may receive a user input for selecting one of a plurality of devices. Furthermore, the user input unit 5310 may receive a user input requesting the device 5300 to generate an encoding key or a decoding key.

Furthermore, the user input unit 5310 may receive a user input requesting the device 5300 to store content. Furthermore, the user input unit 5310 may receive a user input requesting the device 5300 to execute a program, may receive a user input requesting the device 5300 to exit the program, or may receive a user input selecting a coded content.

The output unit 5320 may output an audio signal, a video signal, or a vibration signal and may include a display unit 5321 (for example, a display), a sound output unit 5322 (for example, a sound output device), a vibration motor 5323, and the like.

The display unit 5321 displays and outputs information processed in the device 5300. For example, the display unit 5321 may display a user interface for the user 20 to select a virtual image, a user interface for the user 20 to set a virtual image, and a user interface for the user 20 to purchase items of the virtual image.

When the display unit 5321 and the touch pad form the same layer structure and then form a touch screen, the display unit 5321 can be used as both an output device and an input device. The display unit 5321 may include a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT-LCD), and an organic light-emitting diode (OLED). At least one of a display, a flexible display, a three-dimensional (3D) display, and an electrophoretic display. Furthermore, according to the type of the device 5300, the device 5300 may include at least two display units 5321. According to an exemplary embodiment, at least two display units 5321 may be disposed to face each other by using a hinge.

The sound output unit 5322 may output audio data received from the communication unit 5340 or stored in the memory 5370. The sound output unit 5322 may also output sound signals (for example, call signal reception sound, message reception sound, notification sound, etc.) related to the capabilities performed by the device 5300. The sound output unit 5322 may include a speaker, a buzzer, and the like.

The vibration motor 5323 can output a vibration signal. For example, the vibration motor 5323 may output a vibration signal corresponding to the output of audio data (for example, call signal reception sound, message reception sound, etc.) or video data. Furthermore, when touch is input to the touch screen, the vibration motor 5323 can output a vibration signal.

The controller 5330 may substantially control the entire operation of the device 5300. For example, the controller 5330 can control a user input unit 5310, an output unit 5320, a sensing unit 5350, a communication unit 5340, an A / V input unit 5360, and the like by executing a program stored in the memory 5370.

For example, the controller 5330 may identify the user 20 based on the user information, and when the user 20 is authenticated, the controller 5330 may generate an encoding key or a decoding key. Furthermore, the controller 5330 may calculate a distance between the wearable device 10 and the external device 30, and when the distance is equal to or less than a predetermined value, the controller 5330 may generate an encoding key or a decoding key.

After receiving the notification indicating the storage of the content from the external device 30, the controller 5330 may generate an encoding key. Furthermore, when an instruction is received from the external device 30 After the notification that the program for executing the content has been executed, the controller 5330 may generate an encoding key. Furthermore, after receiving a notification from the external device 30 indicating that the program for executing the content has ended, the controller 5330 may generate an encoding key. Further, after receiving a notification indicating the selection of the encoded content from the external device 30, the controller 5330 may generate a decoding key.

The controller 5330 may encode the content by using an encoding key or may decode the encoded content by using a decoding key.

When the user 20 is authenticated, the controller 5330 may determine whether the user 20 is allowed to access the external device 30. For example, the controller 5330 may generate access right information indicating that the user 20 has access rights to use the external device 30. Furthermore, the controller 5330 may activate the external device 30 based on the access right information.

The sensing unit 5350 can sense the status of the controller 5330 or the status of the device 5300 and can transfer sensing information to the controller 5330.

The sensing unit 5350 may include a sensor selected from a magnetic sensor 5351, an acceleration sensor 5352, a temperature / humidity sensor 5353, an infrared sensor 5354, a gyroscope sensor 5355, and a position sensor (e.g., GPS). 5356, at least one of an air pressure sensor 5357, a proximity sensor 5358, and an RGB sensor (ie, a brightness sensor) 5359, but one or more exemplary embodiments are not limited thereto. The function of the sensor can be inferred intuitively by those skilled in the art by being based on the sensor's name or other considerations, and therefore its detailed description is omitted here.

The communication unit 5340 may include one or more elements that allow the device 5300 to communicate with another device or server. For example, the communication unit 5340 may include a short-range communication unit 5341 (eg, a short-range communicator), a mobile communication unit 5342 (eg, a mobile communicator), and a broadcast receiving unit 5343 (eg, a broadcast receiver).

The short-range communication unit 5341 may include (but is not limited to) a Bluetooth communication unit, a Bluetooth Low Energy (BLE) communication unit, a near-field wireless communication unit, and a wireless local area network (WLAN) communication unit , Zigbee communication unit, infrared data association (IrDA) communication unit, Wi-Fi Direct (WFD) communication unit, UWB communication unit or Ant + communication unit.

The mobile communication unit 5342 exchanges wireless signals on the mobile communication network with at least one selected from the group consisting of a base station, an external terminal, and a server. The wireless signal may include various types of data about a voice call signal, a video call signal, or a text / multimedia message according to the communication.

The broadcast receiving unit 5343 receives a broadcast-related broadcast signal and / or information from the outside via a broadcast channel. The broadcasting channel may include a satellite channel and a ground wave channel. According to an exemplary embodiment, the device 5300 may not include the broadcast receiving unit 5343.

The A / V input unit 5360 can receive input of audio signals or video signals and can include a camera 5361 and a microphone 5362. The camera 5361 can obtain an image frame, such as a still image or a moving image, via an image sensor during a video call mode or a capture mode. The image captured by the image sensor can be processed by the controller 5330 or an independent image processing unit.

The image frames processed by the camera 5361 can be stored in the memory 5370 or transmitted to an external source via the communication unit 5340. Depending on the configuration of the device 5300, two or more cameras 5361 can be configured.

The microphone 5362 receives an external sound signal as an input and processes the received sound signal into electric voice data. For example, the microphone 5362 may receive a sound signal from an external device or a speaker. In order to eliminate the From time to time, the microphone 5362 can use various noise removal algorithms.

The memory 5370 can store programs for processing and controlling the controller 5330 and a plurality of data blocks input to or output from the device 5300.

The memory 5370 may include at least one type of storage medium selected from: flash memory, hard disk, multimedia card memory, card memory such as SD or XD card memory, random access memory Random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable and programmable read-only memory (electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, and optical discs.

The programs stored in the memory 5370 can be classified into multiple modules according to their functions, such as a user interface (UI) module 5371, a touch screen module 5372, an alarm module 5373, and the like.

The UI module 5371 can be combined with the device 5300 to provide a specific UI or a graphical user interface (GUI) for each application. The touch screen module 5372 can detect a user's touch gesture on the touch screen and transmit information related to the touch gesture to the controller 5330. In another exemplary embodiment, the touch screen module 5372 can recognize and analyze the touch code. The touch screen module 5372 can be configured by using additional hardware including a controller.

Various sensors can be arranged in the touch screen or near the touch screen so as to detect the touch on the touch sensor or the closest touch. Examples of the sensor to detect a touch on the touch screen may include a tactile sensor. The tactile sensor sensitively detects the contact of a specific object at least as sensitive as humans can detect. Tactile sensor It can detect various types of information, such as the roughness of the contact surface, the hardness of the contact object, and the temperature of the contact point.

Examples of sensors used to detect touches on a touch screen may include proximity sensors.

Proximity sensors detect the presence of objects near or to a predetermined detection surface by using electromagnetic field forces or infrared rays without mechanical contact. Examples of proximity sensors include transmission photo sensors, directional reflection photo sensors, specular reflection photo sensors, high-frequency vibration proximity sensors, capacitive proximity sensors, magnetic proximity sensors Sensors, infrared proximity sensors, etc. The user's touch gestures (e.g., input) may include touch gestures, touch and hold gestures, double touch gestures, drag gestures, horizontal movement gestures, toggle gestures, drag and land gesture Motion, sliding gestures, etc.

The alarm module 5373 may generate a signal for notifying the user 20 that an event has occurred in the device 5300. Examples of events occurring in the device 5300 may include call signal reception, message reception, key signal input, schedule notification, and the like. The alarm module 5373 may output a video format alarm signal via the display unit 5321, may output an audio format alarm signal via the sound output unit 5322, or output a vibration signal via a vibration motor 5323.

As described above, according to the exemplary embodiment, since the content is encoded or decoded according to the result of user authentication, the content can be prevented from being executed by another subject other than the user. Furthermore, since the user does not have to encode or decode each of the blocks of content, the user can easily manage the content.

Furthermore, since the determination as to whether or not to activate the external device is made based on the result of user authentication, it is possible to prevent the external device from using another device other than the user. One subject is used.

It should be understood that the exemplary embodiments described herein are to be regarded as descriptive only and not for purposes of limitation. Descriptions of features or aspects within each exemplary embodiment should typically be considered as being available for other similar features or aspects in other exemplary embodiments.

Although one or more exemplary embodiments have been described with reference to the drawings, those skilled in the art will generally understand that the form and details can be made therein without departing from the spirit and scope defined by the scope of the following patent applications. Changes.

Claims (15)

A wearable device includes: a memory configured to store instructions; a processor configured to execute the stored instructions to at least: obtain user information; and responding to a user based on the user The information is authenticated to selectively generate an encoding key for encoding the content of the external device; transmitting the encoding key to the external device; receiving a notification from the external device indicating that the encoded content has been selected; In response to the received notification, based on the identification of the user information, a decoding key for decoding the encoded content is generated; and the decoding key is transmitted to the external device. The wearable device of claim 1, wherein the processor is further configured to calculate a distance between the wearable device and the external device and respond to determining the distance Equal to or less than a predetermined distance, the encoding key is generated. The wearable device of claim 1, wherein the processor is further configured to: receive a notification from the external device indicating that the content is stored in the external device; and respond to the instruction The notification that the content is stored in the external device is received to generate the encoding key. The wearable device of claim 1, wherein the processor is further configured to: Receiving a notification from the external device indicating that a program for executing the content is executed in the external device; and in response to the notification indicating that a program for executing the content is executed in the external device Is received to generate the encoding key. The wearable device of claim 1, wherein in response to the user being authenticated, the processor is configured to determine whether the user is allowed to access the external device. The wearable device according to item 1 of the patent application scope, wherein the encoding key includes an encoding key for a symmetric key algorithm, or an encoding key for an asymmetric key algorithm. The wearable device according to item 1 of the scope of patent application, wherein the user information includes biological information of the user. A method for generating a coding key, the method is performed by a wearable device and includes: obtaining user information; identifying a user of the wearable device based on the user information; and responding to the user Selectively generating the encoding key for encoding content in an external device by the authentication being authenticated; transmitting the encoding key to the external device; receiving from the external device to indicate the encoding A notification that content has been selected; in response to receiving the notification, generating a decoding key for decoding the encoded content based on the identification of the user information; and transmitting the decoding key to the external Device. The method for generating an encoding key as described in item 8 of the scope of patent application, more Including: calculating a distance between the wearable device and the external device, wherein the generating is performed when the distance is equal to or less than a predetermined distance. The method for generating an encoding key according to item 8 of the scope of patent application, further comprising: receiving a notification from the external device indicating that the content is stored in the external device; and in response to receiving the instruction that the content is stored The generating is performed by the notification in the external device. The method for generating an encoding key according to item 8 of the scope of patent application, further comprising: receiving a notification from the external device indicating that a program for executing the content is executed in the external device; and in response to receiving The generation is performed to indicate that the program for executing the content is the notification executed in the external device. The method for generating a coding key as described in item 8 of the scope of patent application, further comprising determining whether to allow the user to access the external device in response to the user being authenticated by the authentication. The method for generating an encoding key according to item 8 of the scope of patent application, wherein the encoding key includes an encoding key for a symmetric key algorithm, or includes an encoding key for an asymmetric key algorithm . The method for generating a coding key according to item 8 of the scope of patent application, wherein the user information includes biological information of the user. A non-transitory computer-readable recording medium that has been recorded for borrowing A program that uses a computer to execute the method for generating an encoding key as described in item 8 of the scope of patent application.