Display device for performing authentication operation and operation method thereof

Abstract

A display device according to one embodiment disclosed herein may: enter an authentication mode on the basis of the occurrence of a device registration event associated with a mobile terminal; generate a pressing pattern on the basis of at least one of the number of times at least one first button included in the display device is pressed, the length of time the at least one first button is pressed, the time interval at which the at least one first button is pressed, the length of time during which the at least one first button is not pressed, or the time interval at which the at least one first button is not pressed during a period set in the authentication mode; and on the basis of the pressing pattern being generated, transmit information about the pressing pattern to the mobile terminal.

Description

Display device performing authentication operation and method of operation thereof

[0001] The present disclosure relates to a display device that performs an authentication operation and an operating method thereof.

[0002] In a network environment, a display device can be registered with an external electronic device, such as a mobile terminal or server, for control or interaction functions. The display device can be connected to the external electronic device via wireless communication, perform authentication operations, and register with the external electronic device based on the authentication results. If information associated with the authentication operation is shared or controlled by multiple nearby devices, serious privacy or security issues may arise. Therefore, various security measures can be employed to prevent this.

[0003] Typically, authentication can be performed based on information displayed on the display device's screen. However, display devices that cannot display information for user experience (UX) purposes or have slow screen transitions, making it difficult to immediately display information on the screen, can struggle to perform authentication and fail to register. Furthermore, even if the display device uses a different authentication method, the inability to utilize the information displayed on the screen increases the complexity of the registration process and can lead to frequent errors. Furthermore, when multiple display devices must be registered to a mobile terminal or server, the likelihood of these issues occurring is even higher.

[0004] One embodiment of the present disclosure can provide a display device that performs an authentication operation and an operating method thereof.

[0005] One embodiment of the present disclosure may provide a device and method for supporting authentication or registration operations for a display device that cannot display information on a screen or has slow screen transitions.

[0006] One embodiment of the present disclosure can provide a device and method that can easily perform authentication or registration operations for each display device even when there are multiple display devices that cannot immediately display information or settings on a screen.

[0007] According to one embodiment of the present disclosure, a display device includes a display, a transceiver, a user interface, a memory including at least one storage medium for storing commands, and at least one processor including a processing circuit, wherein the commands, when individually or collectively executed by the at least one processor, cause the display device to enter an authentication mode based on occurrence of a device registration event associated with a mobile terminal, generate a pressing pattern based on at least one of the number of times at least one first button included in the user interface is pressed, a time interval during which the at least one first button is pressed, a time length during which the at least one first button is not pressed, or a time interval during which the at least one first button is not pressed during a set time in the authentication mode, and transmit information about the pressing pattern to the mobile terminal through the transceiver based on the generation of the pressing pattern, wherein the information about the pressing pattern can cause the display device to determine whether to register with the mobile terminal. It can be used as authentication information to determine whether or not.

[0008] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to control the communication unit to broadcast a message including information of the display device, receive a registration start message from the mobile terminal through the communication unit in response to the broadcasted message, and identify that the device registration event has occurred based on the reception of the registration start message.

[0009] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to exit the authentication mode based on the pressing pattern not being generated for the set time in the authentication mode.

[0010] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to activate an LED (light emitting diode) included in the user interface for a set period of time or based on a set cycle, based on entering the authentication mode, and while the LED is activated, light of a single color or light of multiple colors may be sequentially emitted from the LED.

[0011] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to, in response to transmitting information about the pressing pattern to the mobile terminal, control the communication unit to receive network connection setting information from the mobile terminal through the communication unit, and transmit a registration request message to a server on the network based on the received network connection setting information, and in response to transmitting the registration request message, control the communication unit to receive from the server through the communication unit a registration completion message indicating that the display device has been registered as a device associated with the mobile terminal.

[0012] According to one embodiment, the registration completion message may be received based on the information of the display device included in the registration request message corresponding to the device information transmitted from the mobile terminal to the server.

[0013] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to cancel generation of the pressing pattern based on pressing of at least one first button and at least one second button different from those included in the user interface in the authentication mode.

[0014] According to one embodiment, the at least one first button may be used to generate the pressing pattern in the authentication mode, and may be used to perform a function corresponding to the at least one first button when the authentication mode is terminated, and the display device may include an electronic ink (E-ink) display device.

[0015] A display device according to one embodiment of the present disclosure comprises a display, a transceiver, a user interface, a memory including at least one storage medium for storing commands, and at least one processor including a processing circuit, wherein the commands, when individually or collectively executed by the at least one processor, cause the display device to enter an authentication mode based on the occurrence of a device registration event associated with a mobile terminal, activate a microphone included in the user interface for a set time in the authentication mode, receive a sound output from the mobile terminal or a user's speech through the activated microphone, generate pattern information based on the received sound output from the mobile terminal, and transmit the pattern information to the mobile terminal through the transceiver, wherein the pattern information is generated based on at least one of the number of times the sound is received, the length of time during which the sound is received, the time interval during which the sound is received, the length of time during which the sound is not received, or the time interval during which the sound is not received, and wherein the pattern information is generated based on the number of times the display device is connected to the mobile terminal. It can be used as authentication information to determine whether to register.

[0016] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the display device to generate an authentication code including the at least one number or letter based on the user's utterance, based on the user's utterance received, and to transmit the generated authentication code to the mobile terminal through the communication unit, wherein the generated authentication code may be used as the authentication information for determining whether the display device is to be registered with the mobile terminal.

[0017] A method for a display device to perform an authentication operation according to one embodiment of the present disclosure includes: entering an authentication mode based on occurrence of a device registration event associated with a mobile terminal; determining whether a pressing pattern is generated based on at least one of the number of times at least one first button included in the display device is pressed, a length of time during which the at least one first button is pressed, a time interval during which the at least one first button is pressed, a length of time during which the at least one first button is not pressed, or a time interval during which the at least one first button is not pressed during a time set in the authentication mode; and transmitting information about the pressing pattern to the mobile terminal based on the generation of the pressing pattern, wherein the information about the pressing pattern can be used as authentication information for determining whether the display device is to be registered with the mobile terminal.

[0018] According to one embodiment, the operation of entering the authentication mode may include an operation of broadcasting a message including information of the display device, an operation of receiving a registration start message from the mobile terminal in response to the broadcasted message, an operation of identifying that the device registration event has occurred based on the reception of the registration start message, and an operation of entering the authentication mode based on identifying that the device registration event has occurred.

[0019] According to one embodiment, the method may further include an operation of terminating the authentication mode based on the pressing pattern not being generated during the set time in the authentication mode.

[0020] According to one embodiment, the method further includes an operation of activating an LED (light emitting diode) included in the display device for a set period of time or based on a set cycle, based on entering the authentication mode, and while the LED is activated, light of a single color or light of multiple colors may be sequentially emitted from the LED.

[0021] According to one embodiment, the method may further include, in response to transmitting information about the pressing pattern to the mobile terminal, receiving network connection setting information from the mobile terminal, transmitting a registration request message to a server on the network based on the received network connection setting information, and in response to transmitting the registration request message, receiving a registration completion message from the server indicating that the display device has been registered as a device associated with the mobile terminal.

[0022] According to one embodiment, the registration completion message may be received based on the information of the display device included in the registration request message corresponding to the device information transmitted from the mobile terminal to the server.

[0023] According to one embodiment, the method may further include an operation of canceling generation of the pressing pattern based on pressing of at least one first button and at least one second button among buttons included in the display device in the authentication mode.

[0024] According to one embodiment, the at least one first button may be used to generate the pressing pattern in the authentication mode, and may be used to perform a function corresponding to the at least one first button when the authentication mode is terminated, and the display device may include an electronic ink (E-ink) display device.

[0025] A method for a display device to perform an authentication operation according to one embodiment of the present disclosure further includes an operation of entering an authentication mode based on occurrence of a device registration event associated with a mobile terminal, an operation of activating a microphone included in the user interface for a set time in the authentication mode, an operation of receiving a sound output from the mobile terminal or a user's speech through the activated microphone, an operation of generating pattern information based on the received sound output from the mobile terminal, and an operation of transmitting the pattern information to the mobile terminal, wherein the pattern information is generated based on at least one of a number of times the sound is received, a length of time during which the sound is received, a time interval during which the sound is received, a length of time during which the sound is not received, or a time interval during which the sound is not received, and the pattern information can be used as the authentication information for determining whether the display device is to be registered with the mobile terminal.

[0026] According to one embodiment, the method further includes: generating an authentication code including at least one number or letter based on the user's utterance; and transmitting the generated authentication code to the mobile terminal, wherein the generated authentication code can be used as the authentication information for determining whether the display device is to be registered to the mobile terminal.

[0027] FIG. 1 is a diagram schematically illustrating a device registration operation of a mobile terminal according to one embodiment.

[0028] FIG. 2 is a flowchart illustrating a device registration operation of a server according to one embodiment.

[0029] FIG. 3 is a diagram illustrating a device registration system according to one embodiment.

[0030] Figure 4 is a block diagram of a display device according to one embodiment.

[0031] FIG. 5 is a flowchart illustrating an operation of registering a display device to a mobile terminal based on a button input-based pressing pattern according to one embodiment.

[0032] FIG. 6 is a diagram schematically illustrating an operation of generating a press pattern in a display device based on press pattern information displayed on a mobile terminal according to one embodiment.

[0033] FIG. 7A is a diagram schematically illustrating an operation of receiving sound output from a mobile terminal to generate pattern information in a display device according to one embodiment.

[0034] FIG. 7b is a schematic diagram illustrating an operation of receiving a user's speech to generate an authentication code in a display device according to one embodiment.

[0035] FIG. 8A is a flowchart illustrating an operation of registering a display device to a mobile terminal based on sound-based pattern information according to one embodiment.

[0036] FIG. 8b is a flowchart illustrating an operation of registering a display device to a mobile terminal based on a user's speech-based authentication code according to one embodiment.

[0037] FIG. 9 is a flowchart illustrating an operation of registering a display device to a server via a mobile terminal according to one embodiment.

[0038] FIG. 10 is a flowchart illustrating an operation of a display device according to one embodiment of the present invention to generate a pressing pattern.

[0039] FIG. 11 is a flowchart illustrating an operation of a display device entering an authentication mode according to one embodiment.

[0040] FIG. 12 is a flowchart illustrating the operation of a display device based on input generated in an authentication mode according to one embodiment.

[0041] FIG. 13 is a flowchart illustrating an operation of a display device terminating an authentication mode according to one embodiment.

[0042] FIG. 14 is a flowchart illustrating an operation of registering a display device to a server according to one embodiment.

[0043] FIG. 15 is a flowchart illustrating an operation of a display device according to one embodiment of the present invention to generate pattern information based on sound.

[0044] FIG. 16 is a flowchart illustrating an operation of a display device according to one embodiment of the present invention to generate an authentication code based on a user's speech.

[0045] The following description refers to the attached drawings, and specific examples of implementations are illustrated within the drawings. Furthermore, other examples may be utilized and structural changes may be made without departing from the scope of the various examples.

[0046] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.

[0047] FIG. 1 is a diagram schematically illustrating a device registration operation of a mobile terminal according to one embodiment.

[0048] Referring to (a) of FIG. 1, the mobile terminal (110) can search for a connectable device via wireless communication (e.g., Bluetooth or Wi-Fi communication) and output the search result on the display. For example, the mobile terminal (110) can display a list of searched devices (112) on the display. The list of searched devices (112) can include information on one or more devices connectable to the mobile terminal (110). Information (114) corresponding to a specific device (e.g., TV (120)) from the list of searched devices (112) can be selected by the user. The mobile terminal (110) can select the TV (120) as a registration target device based on the selected information (114). Based on the selection of the TV (120) as a registration target device, the mobile terminal (110) can transmit a connection request message including identification information (e.g., name, model name, or unique number) of the mobile terminal (110) to the TV (120).

[0049] Referring to (b) of FIG. 1, the TV (120) can receive a connection request message and obtain identification information (e.g., Galaxy **) of the mobile terminal (110) from the received connection request message. Based on the identification information of the mobile terminal (110), the TV (120) can display a message (e.g., “Do you want to allow the connection between Galaxy ** and the TV?”) (122) for asking whether to approve the connection with the mobile terminal (110), and an “Allow” and a “Block” button for the user’s selection on the screen. When the “Allow” button is selected by the user, the TV (120) can identify that the connection with the mobile terminal (110) is approved and transmit a connection approval message to the mobile terminal (110). When the “Block” button is selected by the user, the TV (120) can identify that the connection with the mobile terminal (110) is not approved and transmit a connection rejection message to the mobile terminal (110).

[0050] Referring to (c) of FIG. 1, when the mobile terminal (110) receives a connection approval message from the TV (120), the mobile terminal (110) may perform a connection with the TV (120) and register the TV (120) as a device associated with the mobile terminal (110). Optionally, the mobile terminal (110) may display a message indicating that the registration of the TV (120) is complete (e.g., registration of the TV is complete) (132) on the display, or display registration information or identification information of the TV on the display. When the mobile terminal (110) receives a connection rejection message from the TV (120), the mobile terminal (110) may terminate the connection and registration operation for the TV (120).

[0051] Unlike the above, the mobile terminal (110) may also perform a password-based device registration operation. For example, the mobile terminal (110) may display a password on the display of the mobile terminal (110) and receive information about the password entered into the TV (120) from the TV (120), which is a device to be registered. The mobile terminal (110) may register the TV (120) if the password based on the received information corresponds to the password displayed on the display of the mobile terminal (110). The mobile terminal (110) may not register the TV (120) if the password based on the received information does not correspond to the password displayed on the display of the mobile terminal (110).

[0052] FIG. 2 is a flowchart illustrating a device registration operation of a server according to one embodiment.

[0053] Referring to FIG. 2, in operation 202, a display device (e.g., TV) (220) may execute an application. For example, the application may support a device registration operation with a server (230) and may be executed based on a selection by a user (240).

[0054] In operation 204, the display device (220) may transmit a registration request message requesting registration of the display device (220) to the server (230) based on which application is executed.

[0055] In operation 206, the server (230) may generate a pairing code for authentication based on the registration request message received. For example, the server (230) may generate the pairing code based on at least one number, at least one letter, or a combination thereof.

[0056] In operation 208, the server (230) may transmit the generated pairing code to the display device (220).

[0057] In operation 210, the display device (220) can display a pairing code received from the server (230) on the display. The display device (220) can display the pairing code for a set period of time.

[0058] In operation 212, the user (240) may input the pairing code displayed on the display device (220) into the server (230) using a mobile terminal or other electronic device.

[0059] In operation 214, the server (230) may register the display device (220) if the pairing code input by the user corresponds to the pairing code generated in operation 206. The server (230) may terminate the device registration operation if the pairing code input by the user does not correspond to the pairing code generated in operation 206 or if the pairing code is not input within a set time after generation of the pairing code.

[0060] The device registration operation of the server (230) may be performed based on a QR (quick response) code instead of a pairing code. The QR code may contain a specific link or encrypted information, and the display device (220) may access a specific link by scanning the QR code or decrypt the information to perform an authentication procedure for registration.

[0061] The device registration operation of the mobile terminal illustrated in FIG. 1 or the device registration operation of the server illustrated in FIG. 2 may be performed based on an authentication operation using information (e.g., a message, a pairing code, or a QR code) displayed on the screen of the registration target device (e.g., the TV (120) of FIG. 1 or the display device (220) of FIG. 2). If the registration target device cannot display information on the screen or cannot use the information displayed on the screen, the authentication operation cannot be performed, making it difficult to perform the device registration operation illustrated in FIG. 1 or FIG. 2.

[0062] For example, the device registration operation illustrated in FIG. 1 or FIG. 2 cannot be performed on a display device that cannot display information for UX (user experience) or has slow screen transitions, making it difficult to immediately use the information displayed on the screen. Taking this into account, the authentication and / or device registration operations presented below may be utilized.

[0063] FIG. 3 is a diagram illustrating a device registration system according to one embodiment.

[0064] Referring to FIG. 3, the device registration system (300) may include a mobile terminal (310), a display device (320), or a server (330).

[0065] According to one embodiment, the mobile terminal (310) may be a device capable of performing various computing functions, such as a communication function, a display function, or an output function (e.g., a voice, sound, or audio output function). For example, the mobile terminal (310) may be, but is not limited to, a portable communication device (e.g., a smartphone or tablet), a wearable device (e.g., a smart watch, smart glasses, or a head mounted display (HMD)), a computer device (e.g., a personal computer (PC), a desktop, or a laptop), a portable medical device, or a home appliance (e.g., a television (TV)), and may be various types of electronic devices.

[0066] According to one embodiment, the mobile terminal (310) may perform an operation of registering the display device (320) or an operation of registering the display device (320) with the server (330). To this end, the mobile terminal (310) may communicate with the display device (320) or the server (330). For example, the mobile terminal (310) may communicate with the display device (320) or the server (330) based on any of various wired or wireless communication protocols, such as Ethernet, GSM (global system for mobile communications), EDGE (enhanced data GSM environment), CDMA (code division multiple access), TDMA (time division multiplexing access), LTE (long term evolution), LTE-A (LTE advance), NR (new radio), Wi-Fi, or Bluetooth.

[0067] According to one embodiment, the display device (320) may be a display device that displays text and / or images. The display device (320) may be driven by low power and may include, but is not limited to, an E-ink display device that uses electronic ink (E-ink) technology. For example, the display device (320) may include a display device included in a home appliance such as a refrigerator or a washing machine, or another type of display device.

[0068] According to one embodiment, the display device (320) may be implemented in various forms, such as an e-book terminal or digital signage (e.g., an information display board in a public place such as an airport or bus stop, or a digital menu board in a store).

[0069] According to one embodiment, the display device (320) may include at least one first button (e.g., first button (321)) and at least one second button (e.g., second button (322)). The at least one first button and the at least one second button may each include a physical button that a user can directly press or operate using a hand or other body part.

[0070] According to one embodiment, the display device (320) can generate a press pattern based on a pattern in which at least one first button is pressed by a user in an authentication mode. The at least one first button may be predetermined for generating the press pattern. The generated press pattern can be used as authentication information for registering the display device (320) with the mobile terminal (310).

[0071] According to one embodiment, the display device (320) can cancel the generated press pattern if a button different from at least one first button (e.g., at least one second button) is pressed while the press pattern is generated in the authentication mode.

[0072] According to one embodiment, when the authentication mode is terminated (or released), the display device (320) may use at least one first button or at least one second button to perform an operation corresponding to the corresponding button, respectively. For example, in the normal mode entered by the termination of the authentication mode, the display device (320) may increase the screen brightness of the display device (320) when the user presses at least one first button, and may decrease the screen brightness of the display device (320) when the user presses at least one second button.

[0073] According to one embodiment, at least one first button and at least one second button may be included in a lower frame of the display device (320), as illustrated in FIG. 3, but is not limited thereto. The at least one first button and the at least one second button may be implemented in various locations on the display device (320).

[0074] According to one embodiment, the display device (320) may include a microphone (not shown). The microphone may be used to receive a user's speech or sound output from an external electronic device (e.g., a mobile terminal (310)).

[0075] According to one embodiment, the display device (320) may generate pattern information based on a sound received through a microphone in an authentication mode, or generate an authentication code including at least one number and / or at least one letter based on a sound received through a microphone or a user's speech in an authentication mode. The pattern information or authentication code may be used as authentication information for registering the display device (320) with the mobile terminal (310).

[0076] According to one embodiment, the display device (320) may include a light emitting diode (LED) (323) for status indication. For example, the display device (320) may activate the LED (323) to indicate an authentication mode, indicate that a button input is required, or indicate activation of a microphone. The LED (323) may be activated at a set time or at set cycles. While the LED (323) is activated, light of a single color may be emitted from the LED (323) or light of multiple colors may be emitted sequentially. The LED (323) may be configured in multiple numbers, and the LEDs configured in multiple numbers may be activated at the same or different times.

[0077] The server (330) can communicate with a mobile terminal (310) or a display device (320). For example, the server (330) can communicate with the mobile terminal (310) or the display device (320) based on any of a variety of wired or wireless communication protocols, such as Ethernet, GSM, EDGE, CDMA, TDMA, LTE, LTE-A, NR, Wi-Fi, or Bluetooth.

[0078] The server (330) may be a server on a network (e.g., a cloud server or an Internet of Things (IoT) server). The server (330) may register a device associated with the mobile terminal (310). For example, the server (330) may receive information about a device to be registered from the mobile terminal (310), and when a registration request is received from a device (e.g., a display device (320)) corresponding to the received information, the server (330) may register the device as a device associated with the mobile terminal (310).

[0079] Figure 4 is a block diagram of a display device according to one embodiment.

[0080] Referring to FIG. 4, the display device (320) may include a display (402), a transceiver (404), a user interface (406), a memory (408), or a processor (410).

[0081] The display (402) can visually present information (e.g., text and / or images) to the outside of the display device (320). The display (402) may also include, for example, control circuitry for controlling the display.

[0082] The communication unit (404) can support the establishment of a wireless communication channel or a wired communication channel between the display device (320) and an external electronic device (e.g., a mobile terminal (310) or a server (330)), and the performance of communication through the established communication channel.

[0083] The communication unit (404) may operate independently from the processor (e.g., application processor) (410) and may include one or more communication processors that support wireless communication or wired communication. According to one embodiment, the communication unit (404) may include a wireless communication module (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (e.g., a local area network (LAN) communication module, or a power line communication module). Any of these communication modules may communicate with an external electronic device via a first network (e.g., a short-range communication network such as Bluetooth, Bluetooth low energy (BLE), Wi-Fi, Wi-Fi direct (WFD), or infrared data association (IrDA)) or a second network (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These different types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips).

[0084] The user interface (406) may include an input interface and / or an output interface for interacting with a user. The input interface may receive commands or data to be used by a component of the display device (320) (e.g., a processor (410)) from an external source of the display device (320) (e.g., a user or a mobile terminal (310)).

[0085] According to one embodiment, the user interface (406) may include at least one button (or key) physically configured as an input interface. For example, the at least one button may include at least one first button for generating a press pattern (e.g., the first button (321) of FIG. 3 ). For example, the at least one button may include at least one second button for canceling a press pattern (e.g., the second button (322) of FIG. 3 ).

[0086] According to one embodiment, the user interface (406) may include a microphone as an input interface. The microphone may receive sound output from an external electronic device (e.g., a mobile terminal (310)) or a user's speech.

[0087] In one embodiment, the user interface (406) may include a speaker and / or an LED (e.g., LED (323) of FIG. 3) as an output interface. The LED may be activated, for example, to indicate an authentication mode, indicate that a button input is required, or indicate microphone activation. The LED may be activated at a set time or at set intervals to emit one or more lights. The LED may be composed of one or more LEDs and may be positioned at various locations on the display device (320). For example, the LED may be positioned at, but is not limited to, the upper portion of the display (402).

[0088] The memory (408) can store various data used by at least one component of the display device (320) (e.g., the display (402), the communication unit (404), the user interface (406), or the processor (410)). For example, the memory (408) can store at least one program for processing and controlling the processor (410), and can store input and / or output data. For example, the memory (408) can include at least one storage medium that stores instructions that, when individually or collectively executed by the processor (410), can cause the electronic device (420) to perform at least one operation. The memory (408) can also store at least one artificial intelligence (AI) model, and can include volatile memory or non-volatile memory.

[0089] The processor (410) can control the overall operation of the display device (320). The processor (410) can execute calculations or data processing related to control and / or communication of at least one other component of the display device (320). For example, the processor (410) can be electrically connected to the display (402), the communication unit (404), the user interface (406), and the memory (408), and can control the operations of the display device (320) by executing instructions of a program stored in the memory (408).

[0090] According to one embodiment, the processor (410) may correspond to a plurality of processors that perform a plurality of operations individually or collectively by dividing the operations among the processors.

[0091] According to one embodiment, the processor (410) may include processing circuitry that executes instructions of a program stored in the memory (408). The processor (410) may include at least one of a central processing unit (CPU), a neural processing unit (NPU), a graphics processing unit (GPU), a micro processing unit (MPU), a micro controller unit (MCU), an application processor (AP), a communication processor (CP), a system on chip (SoC), or an integrated circuit (IC), a sensor hub, a supplementary processor, a communication processor, an application processor, an application specific integrated circuit (ASIC), or a field programmable gate array (FPGA), and may have multiple cores.

[0092] The authentication or registration operation of the display device (320) configured as described above will be described below.

[0093] FIG. 5 is a flowchart illustrating an operation of registering a display device to a mobile terminal based on a button input-based pressing pattern according to one embodiment.

[0094] Referring to FIG. 5, in operation 502, the first display device (320-1) may broadcast a first message. According to one embodiment, the first display device (320-1) may have a configuration corresponding to the display device (320) of FIG. 3 or FIG. 4, and the first message may be a BLE advertising message. The first message may, for example, indicate that the first display device (320-1) is in a connection standby state or indicate that the first display device (320-1) is a connectable device. The first message may include, for example, identification information of the first display device (320-1) (e.g., the name, model name, unique number, or MAC (media access control) address of the first display device (320-1).

[0095] In operation 504, the second display device (320-2) may broadcast a second message. According to one embodiment, the second display device (320-2) may have a configuration corresponding to the display device (320) of FIG. 3 or FIG. 4, and the second message may include a BLE advertising message. The second message may, for example, indicate that the second display device (320-2) is in a connection standby state or indicate that the second display device (320-2) is a connectable device. The second message may include, for example, identification information of the second display device (320-2) (e.g., the name, model name, unique number, or MAC address of the second display device (320-2).

[0096] In one embodiment, operations 502 and 504 may be performed concurrently, or operation 504 may be performed prior to operation 502.

[0097] In operation 506, the mobile terminal (310) may initiate device registration. In one embodiment, the initiation of device registration may indicate that the mobile terminal (310) has entered device registration mode or that the mobile terminal (310) has initiated an operation for device registration. In one embodiment, the initiation of device registration may be performed based on the execution of an application for device registration on the mobile terminal (310).

[0098] In operation 508, the mobile terminal (310) may transmit a registration start message to the second display device (320-2) notifying the start of device registration.

[0099] In operation 510, the mobile terminal (310) may transmit a registration start message notifying the start of device registration to the first display device (320-1).

[0100] In one embodiment, operations 508 and 510 may be performed concurrently, or operation 510 may be performed prior to operation 508.

[0101] According to one embodiment, the first display device (320-1) and the second display device (320-2) may each receive a registration start message and enter an authentication mode for registration. The authentication mode may indicate a mode waiting for a button input or a mode in which a pressing pattern is input.

[0102] According to one embodiment, the first display device (320-1) and the second display device (320-2) may each activate an LED (e.g., LED (323) of FIG. 3) to indicate entry into an authentication mode. For example, the first display device (320-1) and the second display device (320-2) may each activate the LED to emit light of a single color or multiple colors, or may periodically activate the LED to provide a blinking effect. The LED may be activated for a set period of time during which the authentication mode is maintained.

[0103] In operation 512, the mobile terminal (310) may display press pattern information on the display of the mobile terminal (310). According to one embodiment, the press pattern information displayed on the display of the mobile terminal (310) may indicate a button input pattern or press pattern to be input on a registration target device (e.g., the first display device (320-1) or the second display device (320-2)).

[0104] In operation 514, the second display device (320-2) may be selected as a registration target device by the user (340) and may receive a pressing pattern input from the user (340). The pressing pattern input by the user (340) may be based on pressing pattern information displayed on the display of the mobile terminal (310), and may be, for example, an input for at least one first button included in the second display device (320-2). The second display device (320-2) may generate a pressing pattern based on the input of the user (340).

[0105] According to one embodiment, the second display device (320-2) can generate a pressing pattern based on at least one of the number of times at least one first button is pressed, the length of time at least one first button is pressed, the time interval at which at least one first button is pressed, the length of time at least one first button is not pressed, or the time interval at which at least one first button is not pressed. For example, the second display device (320-2) can generate a pressing pattern by distinguishing a first type signal (long signal) and a second type signal (short signal) based on the length of time at least one first button is pressed, and converting the first type signal and the second type signal into a first value (e.g., 0) and a second value (e.g., 1), respectively.

[0106] According to one embodiment, the second display device (320-2) can delete or cancel the generated press pattern when at least one second button included in the second display device (320-2), which is different from at least one first button, is pressed.

[0107] According to one embodiment, if there is no input of a pressing pattern within a set time from the time the authentication mode is entered, the device registration operation of the mobile terminal (310) may be terminated.

[0108] In operation 516, the second display device (320-2) can transmit information about the input pressing pattern to the mobile terminal (310) based on the input pressing pattern.

[0109] In operation 518, the mobile terminal (310) may perform a press pattern check operation based on the received information. For example, the mobile terminal (310) may check whether the press pattern based on the received information corresponds to the press pattern information displayed in operation 512.

[0110] In operation 520, the mobile terminal (310) may register the second display device (320-2) based on whether the pressing pattern based on the received information corresponds to the pressing pattern information displayed in operation 512. The mobile terminal (310) may not register the second display device (320-2) based on whether the pressing pattern based on the received information does not correspond to the pressing pattern information displayed in operation 512.

[0111] FIG. 6 is a diagram schematically illustrating an operation of generating a press pattern in a display device based on press pattern information displayed on a mobile terminal according to one embodiment.

[0112] Referring to FIG. 6, the mobile terminal (310) may display press pattern information (610) on the display of the mobile terminal (310) based on the start of device registration. According to one embodiment, the press pattern information (610) may include information (e.g., graphic information) indicating a press pattern to be input in a registration target device (e.g., display device (320)). According to one embodiment, the press pattern information (610) may optionally include a guidance message for inputting a press pattern (e.g., input a button in the following pattern).

[0113] According to one embodiment, the user (340) may perform a button input for generating a pressing pattern on the display device (320), which is a device to be registered, based on the pressing pattern information (610) displayed on the mobile terminal (310). When the user (340) identifies that the display device (320) has entered the authentication mode based on the LED (323) of the display device (320), the user (340) may perform a button input for generating the pressing pattern.

[0114] According to one embodiment, the display device (320) may receive a registration start message based on the mobile terminal (310) initiating device registration. The display device (320) may enter an authentication mode based on receiving the registration start message, and may indicate entry into an authentication mode requiring button input by activating an LED (323).

[0115] According to one embodiment, the display device (320) can generate a press pattern based on a button input of a user (340) while the LED (323) is activated. For example, when an input based on at least one first button (e.g., the first button (321)) is received, the display device (320) can generate a press pattern based on the received input. The at least one first button may be a button designated for generating a press pattern.

[0116] In one embodiment, when a user (340) presses at least one first button, the LED (323) may be activated for the same amount of time that the at least one first button is pressed, thereby indicating that a pressing pattern is being generated.

[0117] According to one embodiment, the color of the LED (323) indicating entry into authentication mode and the color of the LED (323) indicating generation of a pressing pattern may be different. For example, the color of the LED (323) indicating entry into authentication mode may be green, and the color of the LED (323) indicating generation of a pressing pattern may be red.

[0118] In one embodiment, the user (340) may cancel the generated press pattern using at least one second button (e.g., the second button (322)). The at least one second button may be a different button from the at least one first button and may not be a button designated for generating the press pattern. The at least one second button may be a button designated for canceling the generated press pattern.

[0119] According to one embodiment, if a pressing pattern is not input within a set time after entering the authentication mode, the display device (320) may exit the authentication mode and enter the general mode.

[0120] According to one embodiment, when a pressing pattern is input within a set time after entering the authentication mode, the display device (320) can transmit information about the input pressing pattern to the mobile terminal (310).

[0121] According to one embodiment, the mobile terminal (310) can receive information about a pressing pattern and determine whether the pressing pattern based on the received information corresponds to the pressing pattern information displayed by the mobile terminal (310). The mobile terminal (310) can register the display device (320) based on whether the pressing pattern based on the received information corresponds to the pressing pattern information displayed by the mobile terminal (310). The mobile terminal (310) can not register the display device (320) based on whether the pressing pattern based on the received information does not correspond to the pressing pattern information displayed by the mobile terminal (310).

[0122] FIG. 7A is a diagram schematically illustrating an operation of receiving a sound output from a mobile terminal to generate a pressing pattern in a display device according to one embodiment.

[0123] Referring to FIG. 7A, the mobile terminal (310) may provide press pattern information as sound. According to one embodiment, the mobile terminal (310) may display a screen such as (a) of FIG. 7A on the display based on the initiation of device registration.

[0124] Referring to (a) of FIG. 7A, the mobile terminal (310) may display an interface screen for sound output on the display. According to one embodiment, the interface screen for sound output may include a pattern output button (720) as a button that can be used for sound output. The pattern output button (720) may be, for example, a physical button included in the mobile terminal (310), or a button or icon in the form of a GUI (graphical user interface).

[0125] In one embodiment, the interface screen for sound output may include a guidance message (710) together with a pattern output button (720). The guidance message (710) may include information guiding the user to press the pattern output button (720) (e.g., “Please come close to the device you wish to register and press the button below.”).

[0126] According to one embodiment, the mobile terminal (310) may display an interface screen for sound output for a set period of time from the time device registration is initiated (e.g., the time device registration operation is initiated or device registration mode is entered).

[0127] Referring to (b) of FIG. 7a, a pattern output button (720) may be pressed by a user (340) on a mobile terminal (310). According to one embodiment, a sound may be output based on the pressing of the pattern output button (720), and an interface screen related to the sound output may be displayed. For example, the interface screen related to the sound output may include a message (730) indicating that a sound is being output and / or time information (740) related to the sound output. The time information (740) related to the sound output may include graphic information indicating an elapsed time from the time of sound output and / or a remaining time until the time of sound termination, but may also include text and / or image information.

[0128] According to one embodiment, the display device (320) may receive a registration start message based on the mobile terminal (310) starting device registration. The display device (320) may enter an authentication mode based on receiving the registration start message. The display device (320) may activate a microphone based on entering the authentication mode, or may activate the microphone when a specific button (e.g., a second button (322)) is pressed after entering the authentication mode. The display device (320) may activate an LED (323) to indicate entering the authentication mode or activating the microphone. The microphone may be activated for a set period of time from the time of entering the authentication mode, or may be activated until a specific button (e.g., a second button (322)) is pressed after activating the microphone.

[0129] According to one embodiment, the display device (320) can receive sound output from the mobile terminal (310) while the microphone is activated. The display device (320) can generate a sound pattern based on the received sound. According to one embodiment, the sound pattern can be generated based on at least one of the number of times the sound is received, the length of time during which the sound is received, the time interval during which the sound is received, the length of time during which the sound is not received, or the time interval during which the sound is not received.

[0130] In one embodiment, the display device (320) may change a sound pattern into a press pattern. For example, the display device (320) may consider the reception of a sound to correspond to a button input and change the sound pattern into a press pattern.

[0131] According to one embodiment, the display device (320) can transmit pattern information indicating a sound pattern or a pressing pattern to the mobile terminal (310). The mobile terminal (310) can receive the pattern information and determine whether the sound pattern or the pressing pattern indicated by the received pattern information corresponds to a pattern of sound output by the mobile terminal (310) (hereinafter referred to as an “output pattern”). The mobile terminal (310) can register the display device (320) based on whether the sound pattern or the pressing pattern corresponds to the output pattern. The mobile terminal (310) can not register the display device (320) based on whether the sound pattern or the pressing pattern does not correspond to the output pattern.

[0132] FIG. 7b is a schematic diagram illustrating an operation of receiving a user's speech to generate an authentication code in a display device according to one embodiment.

[0133] Referring to FIG. 7B, the mobile terminal (310) may display authentication code information on the display. According to one embodiment, the mobile terminal (310) may display a screen such as (a) of FIG. 7B on the display based on the initiation of device registration.

[0134] Referring to (a) of FIG. 7B, the mobile terminal (310) may display an authentication code (e.g., 7 A 4 1 B 5 3) (760) on the display. According to one embodiment, the authentication code (760) may be randomly generated by the mobile terminal (310). The authentication code (760) may include at least one number or at least one letter, or a combination of at least one number and at least one letter.

[0135] According to one embodiment, the mobile terminal (310) may display a guidance message (e.g., “Please enter the authentication code below into the device you wish to register”) (750) on the display guiding the user to enter an authentication code (760) into the device to be registered.

[0136] According to one embodiment, the mobile terminal (310) may display an authentication code (760) and a guidance message (750) for a set period of time from the time device registration begins.

[0137] Referring to (b) of FIG. 7B, the display device (320) may receive a registration start message based on the mobile terminal (310) starting device registration. The display device (320) may enter an authentication mode based on receiving the registration start message. The display device (320) may activate a microphone based on entering the authentication mode, or may activate the microphone when a specific button (e.g., the second button (322)) is pressed after entering the authentication mode. The display device (320) may activate an LED (323) to indicate entering the authentication mode or activating the microphone. The microphone may be activated for a set period of time from the time of entering the authentication mode, or may be activated until a specific button (e.g., the second button (322)) is pressed after activating the microphone.

[0138] In one embodiment, the display device (320) may receive a user's (340) speech while the microphone is activated. For example, the user's (340) speech may be based on an authentication code (760) displayed on the mobile terminal (310). The display device (320) may receive the user's (340) speech and generate an authentication code including at least one number or letter based on the received speech.

[0139] In one embodiment, instead of receiving speech from the user (340), the display device (320) may generate an authentication code by receiving an audio signal output from the mobile terminal (310). For example, the audio signal output from the mobile terminal (310) may be an audio signal indicating numbers and / or letters corresponding to number keys and / or letter keys selected by the user (340) on the mobile terminal (310). The display device (320) may generate an authentication code by receiving the audio signal output from the mobile terminal (310).

[0140] According to one embodiment, the display device (320) can transmit information about the generated authentication code to the mobile terminal (310).

[0141] According to one embodiment, the mobile terminal (310) may receive information about the generated authentication code and determine whether the authentication code based on the received information corresponds to the authentication code (760) displayed on the screen of the mobile terminal (310). The mobile terminal (310) may register the display device (320) based on whether the authentication code based on the received information corresponds to the authentication code (760) displayed on the screen of the mobile terminal (310). The mobile terminal (310) may not register the display device (320) based on whether the authentication code based on the received information does not correspond to the authentication code (760) displayed on the screen of the mobile terminal (310).

[0142] Detailed operations related to FIGS. 7a and 7b are described below with reference to FIGS. 8a and 8b.

[0143] FIG. 8A is a flowchart illustrating an operation of registering a display device to a mobile terminal based on sound-based pattern information according to one embodiment.

[0144] Referring to FIG. 8a, operations 802 to 810 correspond to operations 502 to 510 of FIG. 5, so a detailed description thereof is omitted.

[0145] In operation 812, the first display device (320-1) may activate the microphone in the authentication mode. In one embodiment, the first display device (320-1) may activate the microphone based on entering the authentication mode, or may activate the microphone based on an input to a specific button in the authentication mode. In one embodiment, the first display device (320-1) may activate the microphone for a set period of time from the time of entering the authentication mode, or may activate the microphone until a specific button is pressed.

[0146] In operation 814, the second display device (320-2) may activate the microphone in the authentication mode. In one embodiment, the second display device (320-2) may activate the microphone based on entering the authentication mode, or may activate the microphone based on a specific button input in the authentication mode. In one embodiment, the second display device (320-2) may activate the microphone for a set period of time from the time of entering the authentication mode, or may activate the microphone until a specific button is pressed.

[0147] In one embodiment, operations 812 and 814 may be performed concurrently, or operation 814 may be performed prior to operation 812.

[0148] In operation 816, the first display device (320-1) may terminate the authentication operation by terminating the authentication mode if no sound is received while the microphone is activated.

[0149] In operation 818, the second display device (320-2) may receive sound output from the mobile terminal (310) while the microphone is activated. According to one embodiment, the mobile terminal (310) may output an interface screen for sound output as illustrated in (a) of FIG. 7A. According to one embodiment, the mobile terminal (310) may output sound based on the user (720) pressing the pattern output button (720) on the mobile terminal (310), as illustrated in (b) of FIG. 7A. In one embodiment, the sound output from the mobile terminal (310) may form a randomly generated output pattern.

[0150] In operation 820, the second display device (320-2) may generate pattern information based on the received sound. According to one embodiment, the display device (320) may generate a sound pattern based on the received sound. According to one embodiment, the sound pattern may be generated based on at least one of the number of times the sound is received, the length of time during which the sound is received, the time interval during which the sound is received, the length of time during which the sound is not received, or the time interval during which the sound is not received. According to one embodiment, the display device (320) may also change the generated sound pattern into a pressing pattern. The display device (320) may generate pattern information indicating the sound pattern or the pressing pattern.

[0151] In operation 822, the second display device (320-2) can transmit the generated pattern information to the mobile terminal (310).

[0152] In operation 824, the mobile terminal (310) may receive pattern information from the second display device (320-2) and check the received pattern information. According to one embodiment, the mobile terminal (310) may determine whether the sound pattern or press pattern indicated by the received pattern information corresponds to the output pattern of the sound output in operation 818.

[0153] In operation 826, the mobile terminal (310) can register the second display device (320-2) based on whether the sound pattern or the pressing pattern corresponds to the output pattern.

[0154] The mobile terminal (310) may not register the second display device (320-2) based on the sound pattern or press pattern not corresponding to the output pattern.

[0155] FIG. 8b is a flowchart illustrating an operation of registering a display device to a mobile terminal based on a user's speech-based authentication code according to one embodiment.

[0156] Referring to FIG. 8b, operations 852 to 860 correspond to operations 502 to 510 of FIG. 5, so a detailed description thereof is omitted.

[0157] In operation 862, the first display device (320-1) may activate the microphone in the authentication mode. According to one embodiment, the first display device (320-1) may activate the microphone based on entering the authentication mode, or may activate the microphone based on a specific button input in the authentication mode. According to one embodiment, the first display device (320-1) may activate the microphone for a set period of time from the time of entering the authentication mode, or may activate the microphone until a specific button is pressed.

[0158] In operation 864, the second display device (320-2) may activate the microphone in the authentication mode. In one embodiment, the second display device (320-2) may activate the microphone based on entering the authentication mode, or may activate the microphone based on a specific button input in the authentication mode. In one embodiment, the second display device (320-2) may activate the microphone for a set period of time from the time of entering the authentication mode, or may activate the microphone until a specific button is pressed.

[0159] In one embodiment, operations 862 and 864 may be performed concurrently, or operation 864 may be performed prior to operation 862.

[0160] In operation 866, the mobile terminal (310) may display an authentication code on the display of the mobile terminal (310) based on the registration start message transmitted in each of operations 908 and 910. In one embodiment, the mobile terminal (310) may display a screen including an authentication code (760) as illustrated in (a) of FIG. 7B on the display.

[0161] In operation 868, the first display device (320-1) may not receive the user's (340) speech while the microphone is activated. The first display device (320-1) may terminate the authentication operation by terminating the authentication mode based on the fact that the user's (340) speech was not received.

[0162] In operation 870, the second display device (320-2) may receive speech from the user (340) while the microphone is activated. According to one embodiment, the second display device (320-2) may also receive an audio signal output from the mobile terminal (310) instead of the speech from the user (340). The audio signal output from the mobile terminal (310) may include, for example, an audio signal indicating numbers and / or letters corresponding to number keys and / or letter keys selected by the user (340).

[0163] In operation 872, the second display device (320-2) may generate an authentication code based on the user's (340) speech received.

[0164] In operation 874, the second display device (320-2) can transmit information about the generated authentication code to the mobile terminal (310).

[0165] In operation 876, the mobile terminal (310) may check an authentication code based on the received information. In one embodiment, the mobile terminal (310) may determine whether the authentication code based on the received information corresponds to the authentication code displayed on the screen of the mobile terminal (310).

[0166] In operation 878, the mobile terminal (310) can register the second display device (320-2) based on whether the authentication code based on the received information corresponds to the authentication code displayed on the screen of the mobile terminal (310).

[0167] The mobile terminal (310) may not register the second display device (320-2) based on the fact that the authentication code based on the received information does not correspond to the authentication code displayed on the screen of the mobile terminal (310).

[0168] FIG. 9 is a flowchart illustrating an operation of registering a display device to a server through a mobile terminal according to one embodiment.

[0169] According to one embodiment, the operations illustrated in FIG. 9 may be operations performed after the second display device (320-2) is registered with the mobile terminal (310) based on the operations of FIG. 5, FIG. 8a, or FIG. 8b.

[0170] Referring to FIG. 9, in operation 902, the mobile terminal (310) may transmit device information of a registration target device to be registered to the server (330) to the server (330). According to one embodiment, the registration target device may be a device registered to the mobile terminal (310) (e.g., a second display device (320-2)). The device information transmitted to the server (330) may include identification information of the registration target device (e.g., name, model name, unique number, or MAC address).

[0171] In operation 904, the server (330) may store the device information received from the mobile terminal (310). According to one embodiment, the server (330) may update the list of devices waiting for registration managed by the server (330) to include the device information of the device to be registered.

[0172] In operation 906, the second display device (320-2) may transmit a registration request message to the server (330). According to one embodiment, the second display device (320-2) may transmit the registration request message to the server (330) based on network connection setting information received from the mobile terminal (310). The network connection setting information may be received from the mobile terminal (310) based on the second display device (320-2) being registered with the mobile terminal (310). According to one embodiment, the network connection setting information may include at least one of information associated with the server (330), information for connecting to the server (330), or information for activating communication of the display device (320).

[0173] In operation 908, the server (330) may receive a registration request message and identify device information included in the received registration request message. If the device information included in the registration request message corresponds to the device information stored in operation 904, the server (330) may register the second display device (320-2). According to one embodiment, the server (330) may register the second display device (320-2) as a device associated with the mobile terminal (310).

[0174] In operation 910, the server (330) may transmit a registration completion message to the mobile terminal (310) indicating that the second display device (320-2) has been registered.

[0175] At operation 912, the server (330) may transmit a registration completion message to the second display device (320-2) indicating that the second display device (320-2) has been registered.

[0176] According to one embodiment, the server (330) may not register the second display device (320-2) if the device information included in the registration request message does not correspond to the device information stored in operation 904. Based on the fact that the second display device (320-2) has not been registered, the server (330) may transmit a registration rejection message to the second display device (320-2) and the mobile terminal (310).

[0177] Hereinafter, the operation of the display device (320) will be described in detail with reference to FIGS. 10 to 16. According to one embodiment, the operations illustrated in FIGS. 10 to 16 may be understood to be performed by a processor of the display device (320) (e.g., the processor 410 of FIG. 4). The operations illustrated in each of FIGS. 10 to 16 are not limited to the illustrated order and may be performed in various orders. According to one embodiment, at least some of the operations illustrated in each of FIGS. 10 to 16 may be omitted, or more operations may be performed than the operations illustrated in each of FIGS. 10 to 16.

[0178] FIG. 10 is a flowchart illustrating an operation of a display device (320) according to one embodiment of the present invention to generate a pressing pattern.

[0179] Referring to FIG. 10, in operation 1002, the display device (320) may enter an authentication mode based on the occurrence of a device registration event associated with the mobile terminal (310). According to one embodiment, the display device (320) may activate the LED (323) for a set period of time or based on a set cycle based on the entry into the authentication mode. According to one embodiment, while the LED (323) is activated, a single color of light may be emitted from the LED (323) or multiple colors of light may be sequentially emitted.

[0180] In operation 1004, the display device (320) may generate a pressing pattern based on at least one first button (e.g., the first button (321) of FIG. 3) for a set time in the authentication mode. According to one embodiment, the display device (320) may generate the pressing pattern based on at least one of the number of times the at least one first button is pressed, the length of time during which the at least one first button is pressed, the time interval during which the at least one first button is pressed, the length of time during which the at least one first button is not pressed, or the time interval during which the at least one first button is not pressed.

[0181] In operation 1006, the display device (320) may transmit information about the pressing pattern to the mobile terminal (310) based on the pressing pattern being generated for a set time in the authentication mode. According to one embodiment, the information about the pressing pattern may be used as authentication information for determining whether the display device (320) is to be registered with the mobile terminal (310).

[0182] FIG. 11 is a flowchart illustrating an operation of a display device (320) entering an authentication mode according to one embodiment.

[0183] According to one embodiment, the operations illustrated in FIG. 11 may be operations associated with operation 1002 of FIG. 10.

[0184] Referring to FIG. 11, in operation 1102, the display device (320) may broadcast a message including information about the display device (320). According to one embodiment, the broadcasted message may indicate that the display device (320) is in a connection standby state or may indicate that the display device (320) is a connectable device. According to one embodiment, the broadcasted message may include identification information such as the name, model name, unique number, or MAC address of the display device (320).

[0185] In operation 1104, the display device (320) may receive a registration start message from a mobile terminal (e.g., the mobile terminal (310) of FIG. 3). According to one embodiment, the registration start message may be a message indicating that the mobile terminal (310) begins an operation for device registration or enters a device registration mode.

[0186] In operation 1106, the display device (320) may identify that a device registration event associated with the mobile terminal (310) has occurred based on the receipt of a registration start message.

[0187] At operation 1108, the display device (320) may enter an authentication mode based on identifying that a device registration event has occurred.

[0188] FIG. 12 is a flowchart illustrating the operation of a display device (320) based on input generated in an authentication mode according to one embodiment.

[0189] Referring to FIG. 12, in operation 1202, the display device (320) can identify an input that occurred in the authentication mode.

[0190] In operation 1204, the display device (320) may determine whether the identified input is associated with at least one first button (e.g., the first button (321) of FIG. 3).

[0191] In operation 1206, the display device (320) may generate a press pattern based on the identified input, based on the identified input being associated with at least one first button.

[0192] In operation 1208, the display device (320) may cancel generation of the press pattern based on the button associated with the identified input not being associated with at least one first button. For example, the display device (320) may cancel generation of the press pattern based on the identified input being associated with at least one second button (e.g., the second button (322) of FIG. 3) that is different from the at least one first button.

[0193] FIG. 13 is a flowchart illustrating an operation of a display device (320) terminating an authentication mode according to one embodiment.

[0194] Referring to FIG. 13, in operation 1302, the display device (320) may enter an authentication mode based on the occurrence of a device registration event associated with the mobile terminal (310). According to one embodiment, the display device (320) may enter an authentication mode based on the operations illustrated in FIG. 11.

[0195] In operation 1304, the display device (320) can determine whether a pressing pattern based on at least one first button (e.g., the first button (321) of FIG. 3) is generated during a set time in the authentication mode.

[0196] In operation 1306, the display device (320) may terminate the authentication mode based on the fact that no pressing pattern has been generated for a set time in the authentication mode.

[0197] Fig. 14 is a flowchart illustrating an operation of registering a display device (320) to a server according to one embodiment.

[0198] Referring to FIG. 14, in operation 1402, the display device (320) may receive network connection setting information from a mobile terminal (e.g., the mobile terminal (310) of FIG. 3). According to one embodiment, the display device (320) may receive network connection setting information from the mobile terminal (310) based on what is registered in the mobile terminal (310).

[0199] In operation 1404, the display device (320) may transmit a registration request message to a server (e.g., a cloud server or an IoT server) (330) on the network based on network connection setting information. According to one embodiment, the network connection setting information may include at least one of information associated with the server (330), information for connecting to the server (330), or information for activating communication of the display device (320).

[0200] In operation 1406, the display device (320) may receive a registration completion message from the server (330) indicating that the display device (320) has been registered as a device associated with the mobile terminal (310). According to one embodiment, the registration completion message may be received based on the information of the display device (320) included in the registration request message corresponding to the device information transmitted from the mobile terminal (310) to the server (330).

[0201] FIG. 15 is a flowchart illustrating an operation of a display device (320) according to one embodiment of the present invention to generate pattern information based on sound.

[0202] Referring to FIG. 15, at operation 1502, the display device (320) may enter an authentication mode based on the occurrence of a device registration event associated with the mobile terminal (310). According to one embodiment, the display device (320) may enter an authentication mode based on the operations illustrated in FIG. 11.

[0203] In operation 1504, the display device (320) may activate a microphone (e.g., a microphone included in the user interface (406) of FIG. 4) for a set period of time in an authentication mode. In one embodiment, the display device (320) may activate an LED (323) for a set period of time or based on a set cycle based on the microphone being activated. In one embodiment, while the LED (323) is activated, a single color of light may be emitted from the LED (323) or multiple colors of light may be emitted sequentially.

[0204] In operation 1506, the display device (320) can receive sound output from the mobile terminal (310) through the activated microphone.

[0205] In operation 1508, the display device (320) can generate pattern information based on the received sound.

[0206] In operation 1510, the display device (320) can transmit pattern information to the mobile terminal (310).

[0207] FIG. 16 is a flowchart illustrating an operation of a display device (320) according to one embodiment of the present invention to generate an authentication code based on a user's speech.

[0208] Referring to FIG. 16, in operation 1602, the display device (320) may enter an authentication mode based on the occurrence of a device registration event associated with the mobile terminal (310).

[0209] In operation 1604, the display device (320) may activate a microphone (e.g., a microphone included in the user interface (406) of FIG. 4) for a set period of time in an authentication mode. In one embodiment, the display device (320) may activate an LED (323) for a set period of time or based on a set cycle based on the microphone being activated. In one embodiment, while the LED (323) is activated, a single color of light may be emitted from the LED (323) or multiple colors of light may be emitted sequentially.

[0210] In operation 1606, the display device (320) can receive the user's speech through the activated microphone.

[0211] In operation 1608, the display device (320) may generate an authentication code based on the user's speech.

[0212] In operation 1610, the display device (320) may transmit an authentication code to the mobile terminal (310).

[0213] According to one embodiment, authentication and registration operations for a display device that cannot display information on a screen or has slow screen transitions (e.g., display device (320) of FIG. 3) can be easily performed based on pattern input (e.g., a pressing pattern).

[0214] According to one embodiment, registration can be performed by entering a pattern on the target device, thereby providing convenience without having to individually identify and visit the target device to register.

[0215] According to one embodiment, even if there are multiple display devices that cannot immediately display information or settings through an on-screen display (OSD) on the screen, registration through pattern input is possible on any device, so that initial setup operations (e.g., device registration or network setup) of each display device can be easily performed.

[0216] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0217] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0218] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In the display device, display; transceiver; user interface; a memory comprising at least one storage medium for storing instructions; and comprising at least one processor comprising a processing circuit; The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: Enter authentication mode based on the occurrence of a device registration event associated with the mobile terminal, During a time set in the above authentication mode, a pressing pattern is generated based on at least one of the number of times at least one first button included in the user interface is pressed, the length of time during which the at least one first button is pressed, the time interval during which the at least one first button is pressed, the length of time during which the at least one first button is not pressed, or the time interval during which the at least one first button is not pressed. Based on the generation of the above pressing pattern, causing information about the pressing pattern to be transmitted to the mobile terminal through the communication unit, A display device, wherein information about the above pressing pattern is used as authentication information for determining whether the display device is to be registered with the mobile terminal.

2. In paragraph 1, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: Controlling the communication unit to broadcast a message containing information of the display device; In response to the above broadcasted message, a registration start message is received from the mobile terminal through the communication unit, A display device that causes the device registration event to be identified based on the receipt of the above registration start message.

3. In paragraph 1, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: A display device that causes the authentication mode to be terminated based on the pressing pattern not being generated for the set time in the authentication mode.

4. In any one of paragraphs 1 to 3, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: Based on entering the above authentication mode, causing the LED (light emitting diode) included in the user interface to be activated for the set time or based on the set cycle, A display device in which, while the LED is activated, light of a single color or light of multiple colors is emitted sequentially from the LED.

5. In any one of paragraphs 1 to 4, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: In response to transmitting information about the above pressing pattern to the mobile terminal, network connection setting information is received from the mobile terminal through the communication unit, Controlling the communication unit to transmit a registration request message to a server on the network based on the received network connection setting information; A display device, which, in response to transmitting the registration request message, causes the display device to receive a registration completion message from the server through the communication unit, indicating that the display device has been registered as a device associated with the mobile terminal.

6. In paragraph 5, A display device, wherein the registration completion message is received based on the information of the display device included in the registration request message corresponding to the device information transmitted from the mobile terminal to the server.

7. In paragraph 1, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: A display device that causes generation of the pressing pattern to be canceled based on pressing at least one first button and at least one second button among the buttons included in the user interface in the above authentication mode.

8. In paragraph 1, The at least one first button is used to generate the pressing pattern in the authentication mode, and is used to perform a function corresponding to the at least one first button when the authentication mode is terminated. The display device is a display device including an electronic ink (E-ink) display device.

9. In the display device, display; transceiver; user interface; a memory comprising at least one storage medium for storing instructions; and comprising at least one processor comprising a processing circuit; The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: Enter authentication mode based on the occurrence of a device registration event associated with the mobile terminal, Activate the microphone included in the user interface for the time set in the above authentication mode, Receive sound or user speech output from the mobile terminal through the activated microphone, Based on receiving the sound output from the mobile terminal, pattern information is generated based on the received sound, Causing the pattern information to be transmitted to the mobile terminal through the above communication unit, The pattern information is generated based on at least one of the number of times the sound is received, the length of time during which the sound is received, the time interval during which the sound is received, the length of time during which the sound is not received, or the time interval during which the sound is not received. A display device, wherein the above pattern information is used as authentication information for determining whether the display device is to be registered to the mobile terminal.

10. In paragraph 9, The above instructions, when individually or collectively executed by the at least one processor, cause the display device to: Based on receiving the user's speech, generating an authentication code including at least one number or letter based on the user's speech, Causing the generated authentication code to be transmitted to the mobile terminal through the above communication unit, A display device in which the above-mentioned generated authentication code is used as the authentication information for determining whether the display device is to be registered to the mobile terminal.

11. In a method for a display device to perform an authentication operation, An action to enter authentication mode based on the occurrence of a device registration event associated with a mobile terminal; An operation of generating a pressing pattern based on at least one of the number of times at least one first button included in the display device is pressed during a time set in the authentication mode, a length of time during which the at least one first button is pressed, a time interval during which the at least one first button is pressed, a length of time during which the at least one first button is not pressed, or a time interval during which the at least one first button is not pressed; and Based on the generation of the above pressing pattern, an operation of transmitting information about the pressing pattern to the mobile terminal is included. A method in which information about the above pressing pattern is used as authentication information for determining whether the display device is to be registered with the mobile terminal.

12. In paragraph 11, The action of entering the above authentication mode is: An action of broadcasting a message containing information of the display device; In response to the above broadcasted message, an action of receiving a registration start message from the mobile terminal; An action for identifying that the device registration event has occurred based on the reception of the above registration start message; and A method comprising an action of entering the authentication mode based on identifying that the above device registration event has occurred.

13. In paragraph 11, A method further comprising an operation of terminating the authentication mode based on the pressing pattern not being generated during the set time in the authentication mode.

14. In any one of paragraphs 11 to 13, Based on entering the above authentication mode, further including an action of activating an LED (light emitting diode) included in the display device for the set time or based on a set cycle, A method wherein, while the LED is activated, light of a single color or light of multiple colors is emitted sequentially from the LED.

15. In any one of paragraphs 11 to 14, An action of receiving network connection setting information from the mobile terminal in response to transmitting information about the pressing pattern to the mobile terminal; An operation of transmitting a registration request message to a server on the network based on the received network connection setting information; and A method further comprising, in response to transmitting the registration request message, receiving a registration completion message from the server indicating that the display device has been registered as a device associated with the mobile terminal.

Images