Patent Description:
A sound mirroring or screen mirroring technology is a technology of transmitting audio or image content output via a source device to a sync device. Mirroring technology has been used primarily to output content of a device having a relatively smaller screen size, such as a smartphone, to a device having a relatively larger screen size, such as a television (TV), and has been used for various purposes such as meetings and for everyday use.

With existing screen mirroring technology, however, users might need to perform a process of executing a screen mirroring application of a source device, and selecting a sync device that is to output content of the source device. That is, the users might need to perform multiple processes to implement the screen mirroring technology, which might prove tedious, error-prone, impractical, or the like.

Further, with existing mirroring technology, an approval process between the source device and the sync device might be required each time that mirroring is requested in order to establish a connection between the sync device and the source device to permit mirroring between the devices. Further, there is a limitation that in a case where different transmission schemes are used according to the particular content to be output, a user might be required to directly select a particular transmission scheme, or the sync device may output content having a predetermined and limited function, because the sync device may not be capable of outputting the content based on a context of the content that is being output via the source device.

<CIT> discloses a system in which content from a server is controllably displayed on a display device, activated by NFC handshaking between a mobile phone and a remote control device. <CIT> discloses a method for controlling data of a mirror link system, and more particularly, to a method for controlling flow of data in a mirror link system capable of mirroring data between a wireless terminal and a vehicle's audio/video and navigation (AVN) system depending on whether the vehicle is driven or a position of a display.

Terms used in the disclosure may be used to describe specific embodiments rather than limiting the scope of the disclosure. Singular forms of terms may include the plural forms of the terms unless the context clearly indicates otherwise.

In the disclosure, expressions such as "have," "may have," "include," "may include," or the like, may indicate the existence of a corresponding feature (e.g., a numerical value, a function, an operation, or a component such as a part), and might not exclude the existence of an additional feature.

In the disclosure, expressions such as "A or B," "at least one of A and/or B," "one or more of A and/or B," or the like, may include all possible combinations of items enumerated together. For example, "A or B," "at least one of A and B," or "at least one of A or B," may include all of: <NUM>) a case in which at least one A is included, <NUM>) a case in which at least one B is included, or <NUM>) a case in which both of at least one A and at least one B are included.

Expressions such as "first," "second," or the like, used in the disclosure may indicate various components regardless of a sequence and/or importance of the components, and may be used in order to distinguish one component from the other components, and might not limit the corresponding components.

When it is mentioned that a component (e.g., a first component) is (operatively or communicatively) coupled with/to or is connected to another component (e.g., a second component), the component may be directly coupled to another component or may be coupled to another component via the other component (e.g., a third component). Moreover, when it is mentioned that any component (e.g., a first component) is "directly coupled" or "directly connected" to another component (e.g., a second component), an intermediate component (e.g., a third component) might not be present between the component and the other component.

Expressions such as "configured (or set) to" used in the disclosure may be interchangeable with expressions such as "suitable for," "having the capacity to," "designed to," "adapted to," "made to," or "capable of" depending on the context. The expression "configured (or set) to" may not necessarily mean "specifically designed to" in hardware.

Instead, the expression "a device configured to" may indicate that the device may "perform" an operation together with other devices or components. For example, a "processor configured (or set) to perform A, B, and C" may indicate a dedicated processor (e.g., an embedded processor) for performing the corresponding operations or a generic-purpose processor (e.g., a central processing unit (CPU) or an application processor) that may perform the corresponding operations by executing one or more software programs stored in a memory device.

The terms "module" or a "[function]er/or" may be configured to perform at least one function or operation, and may be implemented in hardware or software or be implemented in a combination of hardware and software. In addition, a plurality of "modules" or a plurality of "[function]ers/ors" may be integrated in at least one module and be implemented by at least one processor (not illustrated) except for a "module" or a "[function]er/or" that is implemented by specific hardware.

<FIG> are views for describing a method for controlling a display device <NUM> and a method for controlling a user terminal device <NUM> according to an embodiment.

The user terminal device <NUM> according to an embodiment may include at least one of, for example, a smartphone, a tablet personal computer (PC), a video phone, a desktop PC, a laptop PC, a netbook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), an MP3 player, a mobile medical device, a wearable device, or the like.

The wearable device may include at least one of an accessory type wearable device (e.g., a watch, a ring, a bracelet, an anklet, a necklace, glasses, a contact lens, or a head-mounted-device (HMD)), a textile or clothing integral type wearable device (e.g., an electronic clothing), a body attachment type wearable device (e.g., a skin pad or a tattoo), or a living body implantation type wearable device (e.g., an implantable circuit).

Although <FIG> illustrate a smartphone as an example of the user terminal device <NUM>, the disclosure is not limited thereto.

As shown in <FIG>, based on detecting a content request event associated with a request for the display device <NUM> to output information associated with content that is being output via the user terminal device <NUM>, the display device <NUM> may output the content based on the information associated with the content that is received from the user terminal device <NUM>.

Specifically, the display device <NUM> may detect the content request event. According to an embodiment of the disclosure, the content request event may be an event in which the user terminal device <NUM> is brought within communicative proximity of a near field communication (NFC) tag including information associated with the display device <NUM>. NFC is a short-range wireless communication protocol that may use a frequency range of <NUM>. NFC permits information to be transmitted and received based on terminal devices being brought within communicative proximity (e.g., <NUM> centimeters). Therefore, based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag of the display device <NUM>, the display device <NUM> may transmit, to the user terminal device <NUM>, information (e.g., a media access control (MAC) address of the display device <NUM>) associated with the display device <NUM>, and connection information. The connection information may include information associated with a communication method for receiving the information associated with content that is being output via the user terminal device <NUM>. Specifically, the connection information may include information associated with a communication method by which the display device <NUM> may receive the information associated with content that is being output via the user terminal device <NUM>, such as a Bluetooth MAC address or a peer-to-peer (P2P) device address. Therefore, the user terminal device <NUM> may connect to the display device <NUM> to transmit information associated with content, based on the received connection information.

According to an embodiment, the content request event may be an event in which the user terminal device <NUM> transmits, to the display device <NUM>, a signal indicating that the information associated with content that is being output via the user terminal device <NUM> is to be transmitted. In other words, the content request event may be an event in which the user terminal device <NUM> transmits a signal indicating that the information associated with content that is currently being output via the user terminal device <NUM> is to be transmitted to the display device <NUM> to permit the display device to output the content while the connection is established.

According to an embodiment, the content request event may be an event in which an external device connected to the display device <NUM> transmits, to the user terminal device <NUM> that may be connected to the display device <NUM>, a signal for requesting transmission of the information associated with content that is currently being output via the user terminal device <NUM>. Therefore, based on receiving the signal that requests the transmission of the information associated with content from the external device, the display device <NUM> may transmit, to the user terminal device <NUM> that may be connected to the display device <NUM>, a signal that requests the information associated with content that is currently being output via the user terminal device <NUM>.

Further, based on detecting the content request event, the display device <NUM> may transmit, to the user terminal device <NUM>, a signal that requests the information associated with content that is being o the user terminal device <NUM>.

According to an embodiment, the user terminal device <NUM> may receive the signal that requests the information associated with content that is being output via the user terminal device <NUM> from the display device <NUM>, while outputting the content, and the user terminal device <NUM> may identify a type of content that is currently being output. Further, the user terminal device <NUM> may transmit the information associated with content that is being output via the user terminal device <NUM> to the display device <NUM> by using various and/or different communication methods according to the identified type of content. The user terminal device <NUM> may utilize connection information received from the display device <NUM> when transmitting information associated with the identified type of content by using various and/or different communication methods. According to an embodiment, in a case where it is identified that video content is being output by the user terminal device <NUM>, the user terminal device <NUM> may transmit information associated with the video content to the display device <NUM> by using P2P communication (e.g., Wireless Fidelity (Wi-Fi) Direct communication) by utilizing the connection information such as a P2P device MAC address. According to another embodiment, in a case where it is identified that audio content is being output via the user terminal device <NUM>, the user terminal device <NUM> may transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication and utilizing the connection information such as a Bluetooth MAC address. In a case where the user terminal device <NUM> is brought within communicative proximity of the display device <NUM> when the display device <NUM> is in a powered-off state, the display device <NUM> may receive a wake-up signal from the user terminal device <NUM> and enter a standby mode in which a predetermined standby screen <NUM> is provided. According to an embodiment, the display device <NUM> may display an indicator indicating that the user terminal device <NUM> is within communicative proximity of the display device <NUM> on a region of the standby screen <NUM>, and the region may correspond to a position where the user terminal device <NUM> is within communicative proximity. A detailed description thereof will be provided below in more detail with reference to <FIG>.

Further, as shown in <FIG>, in a case where content that is being output via the user terminal device <NUM> is video content, the display device <NUM> may be switched from the standby mode to a normal mode, and display the video content and an indicator <NUM> indicating that information associated with video content is received, based on the information (e.g., orientation information of the video content, a title of the video content, information associated with a current playback point of the video content that is being output via the user terminal device, and a connection method for receiving the video content) associated with the video content. The indicator <NUM> indicating that information associated with video content is received is shown as a play button in <FIG>. However, the indicator <NUM> may be variously implemented in a form such as a thumbnail icon of the video content, or the like.

Further, as shown in <FIG>, in a case where content that is being output via the user terminal device <NUM> is audio content, the display device <NUM> may display audio user interfaces (Uls) <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> that are different than a UI that is concurrently being displayed via the user terminal device <NUM>, while outputting the received audio content. According to an embodiment, the display device <NUM> may receive information (e.g., an audio data packet, a title of the audio content, a playlist, a playback point, and the like) associated with audio content from the user terminal device <NUM>. The display device <NUM> may output the audio content based on the received audio data packet. Further, the display device <NUM> may display the audio UI <NUM>-<NUM>, the audio UI <NUM>-<NUM>, and the audio UI <NUM>-<NUM> on the standby screen <NUM>. The audio UI <NUM>-<NUM> may be generated based on the title of the audio content, the playback point, and the like, the audio UI <NUM>-<NUM> may be generated based on an image (e.g., an album image of audio data) relevant to the audio content that is being played, the playback point, and the like, and the audio UI <NUM>-<NUM> may be generated based on a play history of recently played audio content. As such, the display device <NUM> may output the audio content while displaying, on the standby screen <NUM>, the audio Uls <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> that are different than the UI that is concurrently displayed on the user terminal device <NUM>.

The content request event may be an event in which the user terminal device <NUM> is brought within communicative proximity of an external device connected to the display device <NUM>. That is, the display device <NUM> may output content that is being output via the user terminal device <NUM> based on the user terminal device <NUM> being brought within communicative proximity of the external device (e.g., a remote controller controlling the display device <NUM>, and an artificial intelligence (AI) speaker connected to the display device <NUM>) connected to the display device <NUM>, rather than being directly brought within communicative proximity of the NFC tag of the display device <NUM>. A detailed description thereof will be provided below in more detail with reference to <FIG>, and <FIG>.

<FIG> is a block diagram schematically illustrating a configuration of the display device <NUM> according to an embodiment.

As illustrated in <FIG>, the display device <NUM> may include a communication interface <NUM>, a display <NUM>, a memory <NUM>, and a processor <NUM>.

The communication interface <NUM> may be configured to communicate with the user terminal device <NUM> by various methods. The communication between the communication interface <NUM> and the user terminal device <NUM> may be facilitated via a connection via a third device (e.g., a relay, a hub, an access point, a server, a gateway, or the like).

The communication interface <NUM> may include various communication modules to connect to the user terminal device <NUM>. A detailed description of the various communication modules is provided below with reference to <FIG>.

The display <NUM> may display various information based on a control by the processor <NUM>. Specifically, based on a wake-up signal being received via the communication interface <NUM>, the display <NUM> may display a predetermined standby screen based on the control by the processor <NUM>. Further, the display <NUM> may display, on a region of the standby screen, an indicator indicating that the user terminal device <NUM> is within communicative proximity of the display device <NUM>, and the region may correspond to a position where the user terminal device <NUM> is within communicative proximity, according to a control by the processor <NUM>.

According to an embodiment, the display <NUM> may display video content received from the user terminal device <NUM> based on a control by the processor <NUM>. Further, the display <NUM> may display an audio UI that is different than a UI that is concurrently being displayed via the user terminal device <NUM> based on a control by the processor <NUM>.

Further, the display <NUM> may be implemented by a touch screen in combination with a touch panel, or may be implemented in various forms.

Further, a panel of the display <NUM> may be implemented by various display technologies such as a liquid crystal display (LCD) technology, an organic light emitting diode (OLED) technology, an active-matrix organic light emitting diode (AM-OLED) technology, a liquid crystal on silicon (LcoS) technology, a quantum dot light emitting diode (QLED) technology, and a digital light processing (DLP) technology. Further, the display <NUM> may be in a form of a flexible display and may be connected in at least one of a front surface region, a side surface region, or a back surface region of the display device <NUM>.

The memory <NUM> may store instructions or data that may be utilized by at least another component of the display device <NUM>. In particular, the memory <NUM> may be implemented by a nonvolatile memory, a volatile memory, a flash memory, a hard disk drive (HDD), a solid state drive (SDD), or the like. The memory <NUM> is accessed by the processor <NUM>, and various operations such as readout, recording, correction, deletion, update, and the like, of data in the memory <NUM> may be performed by the processor <NUM>. In the disclosure, the term "memory" includes the memory <NUM>, a read only memory (ROM) (not illustrated) in the processor <NUM>, a random access memory (RAM) (not illustrated), or a memory card (not illustrated) (e.g., a micro secure digital (SD) card or a memory stick) mounted in the display device <NUM>. Further, the memory <NUM> may store a program, data, or the like, for configuring various screens to be displayed on a display region of the display <NUM>.

Further, the memory <NUM> may store information associated with the user terminal device <NUM>, and information associated with content that is received from the user terminal device <NUM>. For example, the memory <NUM> may store information associated with the user terminal device <NUM>, such as an Internet protocol (IP) address of the user terminal device <NUM>, a network environment, security settings, and connection history. Further, the memory <NUM> may store a title, a type, a history, and the like, of the content received form the user terminal device <NUM>.

The processor <NUM> may be electrically connected to the memory <NUM> to control the overall operation and function of the display device <NUM>. In particular, based on detecting the content request event, the processor <NUM> may control the communication interface <NUM> to transmit, to the user terminal device <NUM>, a signal that requests the information associated with content that is being output via the user terminal device <NUM>. According to an embodiment, and in a case where the content request event is an event in which the user terminal device <NUM> is brought within communicative proximity of the NFC tag of the display device <NUM>, the processor <NUM> may receive the wake-up signal via an NFC communication interface <NUM> and enter the standby mode in which the predetermined standby screen is provided. After entering the standby mode, the processor <NUM> may control the display <NUM> to display, on the region corresponding to a position where the user terminal device <NUM> is within communicative proximity, the indicator indicating that the user terminal device <NUM> is within communicative proximity. According to an embodiment, and in a case where the user terminal device <NUM> is brought within communicative proximity of the right side of the display device <NUM>, the processor <NUM> may control the display <NUM> to display the indicator indicating that the user terminal device <NUM> is within communicative proximity, on a right side region of the display <NUM>.

In a case where information associated with video content is received from the user terminal device <NUM>, the processor <NUM> may switch a mode of the display device <NUM> from the standby mode to the normal mode. Then, the processor <NUM> may control the display <NUM> to display the video content and the indicator indicating that the information associated with the video content was received, based on the information associated with the video content that is received from the user terminal device <NUM>, in the normal mode. The indicator indicating that the information regarding the video content was received may be an indicator having a play button shape as shown in <FIG>. Alternatively, the indicator indicating that the information regarding the video content was received may also be a thumbnail icon of the received video content.

Further, in a case where information associated with audio content is received from the user terminal device <NUM>, the processor <NUM> may control an audio output component <NUM> to output the audio content based on the information associated with the audio content, and may control the display <NUM> to display, on the standby screen, an audio UI that is different from a UI that is concurrently being displayed on the user terminal device <NUM>. Specifically, the processor <NUM> may identify an audio UI based on information (e.g., a title of the audio content, a playback point, a playlist, or the like) associated with audio content that is received from the user terminal device <NUM>, and control the display <NUM> to display the identified audio UI.

Meanwhile, in a case where the content that is being output via the user terminal device <NUM> is video content received from an external server <NUM>, the processor <NUM> may receive information associated with the video content from the user terminal device <NUM> via the communication interface <NUM>. The information associated with the video content may include a title of the video content that is being output via the user terminal device <NUM>, and a current playback point of the video content that is being output via the user terminal device <NUM>. Then, the processor <NUM> may receive, from the external server <NUM> via the communication interface <NUM>, video content that corresponds to a timeframe after the playback point of the video content that is being output via the user terminal device <NUM>, based on the information associated with the video content.

The processor <NUM> may store information (e.g., an IP address of the user terminal device <NUM>, a network environment, security settings, and user information of the user terminal device <NUM>) associated with the user terminal device <NUM> that is received from the user terminal device <NUM>, a type and a history of content received from the user terminal device <NUM>, in the memory <NUM>. Further, the processor <NUM> may control the display <NUM> to display the indicator indicating that the user terminal device <NUM> is within communicative proximity, based on the stored information associated with the user terminal device <NUM>. Further, the processor <NUM> may control the display <NUM> to display a UI including the stored type and history of content received from the user terminal device <NUM> on the standby screen or a screen in the normal mode.

<FIG> is a block diagram illustrating a configuration of the display device <NUM> according to an embodiment. As illustrated in <FIG>, the display device <NUM> may include ta communication interface <NUM>, a display <NUM>, a memory <NUM>, a processor <NUM>, an NFC communication interface <NUM>, an input component <NUM>, and an audio output component <NUM>. The communication interface <NUM>, the display <NUM>, the memory <NUM>, and the processor <NUM> shown in <FIG> may be substantially similar to the communication interface <NUM>, the display <NUM>, the memory <NUM>, and the processor <NUM> as described above with reference to <FIG>.

The communication interface <NUM> may include various modules configured to connect to the user terminal device <NUM> or the external server <NUM>. For example, the communication interface <NUM> may include a Bluetooth module <NUM>, a P2P module <NUM>, a wireless communication module <NUM>, and a broadcast receiving module <NUM>.

The Bluetooth module <NUM> may be a module that is configured to connect to the user terminal device <NUM> using a Bluetooth low energy (BLE) protocol. Bluetooth is a wireless communication method using an industrial, scientific, and medical (ISM) frequency range (e.g., <NUM> to <NUM>). According to an embodiment, the Bluetooth module <NUM> may receive, from the user terminal device <NUM>, information associated with audio content output via the user terminal device <NUM> by using Bluetooth communication.

The P2P module <NUM> may be a module that is configured to connect to the user terminal device <NUM> by using P2P communication. According to an embodiment, the P2P module <NUM> may connect to the user terminal device <NUM> by utilizing Wi-Fi Direct, which is a Wi-Fi-based P2P standard, without requiring access to separate equipment such as an access point (AP) or a router. Further, the P2P module <NUM> may receive, form the user terminal device <NUM>, information associated with video content that is being output via the user terminal device <NUM>.

The wireless communication module <NUM> may include a cellular communication module using at least one of long-term evolution (LTE), LTE Advanced (LTE-A), code division multiple access (CDMA), wideband CDMA (WCDMA), universal mobile telecommunications system (UMTS), Wireless Broadband (WiBro), or Global System for Mobile Communications (GSM). As another example, the wireless communication module may include, for example, at least one of Zigbee, magnetic secure transmission, radio frequency (RF), or a body area network (BAN).

The broadcasting receiving module <NUM> may include a terrestrial broadcasting receiving module (not illustrated) including an antenna, a demodulator, an equalizer, and the like, for receiving a terrestrial broadcasting signal, a digital multimedia broadcasting (DMB) module for receiving and processing a DMB broadcasting signal, or the like.

The NFC communication interface <NUM> may include an NFC tag in which information (e.g., a MAC address of the display device <NUM>) associated with the display device <NUM>, and connection information (e.g., a Bluetooth MAC address, a P2P device MAC address, and the like) are stored. The NFC tag may include an integrated circuit (IC) and an antenna coil. When the user terminal device <NUM> including an NFC reader is brought within communicative proximity of the NFC tag to perform short distance access, the NFC tag is driven by an electromagnetic wave emitted from the NFC reader, and may transmit, to the user terminal device <NUM>, an RF signal including information associated with the display device <NUM> and connection information that is stored in the NFC tag.

Specifically, in the antenna coil in the NFC tag, a current may be induced based on the electromagnetic wave emitted from the NFC reader. The induced current may be charged to a capacitor included in the NFC tag. Further, the antenna coil in the NFC tag may be formed by a conductor wound multiple times in a rectangular or circular form. The IC may be driven by the current charged to the capacitor to modulate and encode information recorded in a memory in the IC to generate the RF signal.

Further, the NFC communication interface <NUM> may receive the wake-up signal from the user terminal device <NUM>. The wake-up signal may be a signal for inducing the display device <NUM> to enter the standby mode in which the predetermined standby screen is provided, even in a state in which the display device <NUM> is powered off.

The input component <NUM> may receive a user input for controlling the display device <NUM>. Particularly, the input component <NUM> may include, for example, a touch panel for receiving a touch gesture, a stylus pen, or the like, and a button for receiving a manipulation by the user. In addition, the input component <NUM> may be implemented by another input device (e.g., a remote controller <NUM>, a virtual keyboard, a mouse, a motion input component, or the like).

The audio output component <NUM> may be a component configured to output various alarms or audio messages as well as various audio data on which various processes such as decoding, amplification, noise filtering, and the like, are performed by an audio processor (not illustrated). Particularly, the audio output component <NUM> may output a response to user speech as an audio message in a form of a natural language. The audio output component <NUM> may be implemented by a speaker, or by an output terminal that may output audio data.

Particularly, according to an embodiment, the audio output component <NUM> may output audio content received from the user terminal device <NUM> based on a control by the processor <NUM>.

The processor <NUM> may include one or more of a central processing unit (CPU) configured to process a digital signal, a microcontroller unit (MCU), a micro processing unit (MPU), a controller, an application processor (AP), a communication processor (CP), an ARM processor, or the like. In addition, the processor <NUM> may be implemented by a system-on-chip (SoC) or a large scale integration (LSI) in which a processing algorithm is embedded, or may be implemented in a field programmable gate array (FPGA) form. The processor <NUM> may perform various functions by executing computer executable instructions stored in the memory <NUM>. In addition, the processor <NUM> may include at least one of a graphics processing unit (GPU), a neural processing unit (NPU), or a visual processing unit (VPU) as a separate artificial intelligence (AI) dedicated processor configured to perform an Al function.

<FIG> is a block diagram schematically illustrating a configuration of the user terminal device <NUM> according to an embodiment of the disclosure.

As shown in <FIG>, the user terminal device <NUM> according to an embodiment may include a communication interface <NUM>, a display <NUM>, a memory <NUM>, and a processor <NUM>.

The communication interface <NUM> may be configured to communicate with the display device <NUM>, and the external device <NUM> connected with the display device <NUM>. Specifically, the communication interface <NUM> may include an NFC module, and the NFC module may be implemented by an NFC reader. When the user terminal device <NUM> including the NFC reader is brought within communicative proximity of the NFC tag in which information regarding the display device <NUM> is stored to perform short distance access, an electromagnetic wave may be emitted from the NFC reader. Further, the NFC tag of the display device <NUM> is driven by the emitted electromagnetic wave and may transmit an RF signal including the information regarding the display device <NUM> to the NFC reader. In this way, the communication interface <NUM> may receive the information associated with the display device <NUM> and connection information from the display device <NUM>. The connection information may include information associated with a communication method by which the display device <NUM> may receive the information associated with the content that is being output via the user terminal device <NUM>, such as a Bluetooth MAC address or a peer-to-peer (P2P) device address.

Further, the communication interface <NUM> may include at least one of a Wi-Fi chip, a Bluetooth chip, a P2P chip, or a wireless communication chip. Specifically, the Wi-Fi chip, the Bluetooth chip, and the P2P chip may perform Wi-Fi communication, Bluetooth communication, and P2P communication, respectively. Further, the wireless communication chip may be a chip configured to perform communication according to various communication protocols such as Institute of Electrical and Electronics Engineers (IEEE), Zigbee, 3rd generation (<NUM>), 3rd generation partnership project (3GPP), long term evolution (LTE), 5th generation (<NUM>), and the like. Particularly, the communication interface <NUM> may transmit information associated with audio content to the display device <NUM> by using Bluetooth communication, and transmit information associated with video content to the display device <NUM> by using P2P communication. Alternatively, the communication interface <NUM> may transmit content by using various communication methods.

The display <NUM> may display various information based on a control by the processor <NUM>. Specifically, based on receiving a signal for requesting information associated with content that is currently being output via the user terminal device <NUM> from the display device <NUM>, the display <NUM> may display a UI for selecting information associated with content to be transmitted to the display device <NUM> according to a control by the processor <NUM>.

Further, the display <NUM> may be implemented by a touch screen in combination with a touch panel. Further, a panel of the display <NUM> may be implemented by various display technologies such as a liquid crystal display (LCD) technology, an organic light emitting diode (OLED) technology, an active-matrix organic light emitting diode (AM-OLED) technology, a liquid crystal on silicon (LcoS) technology, a quantum dot light emitting diode (QLED) technology, and a digital light processing (DLP) technology. Further, the display <NUM> may be in a form of a flexible display and may be connected in at least one of a front surface region, a side surface region, or a back surface region of the user terminal device <NUM>.

The memory <NUM> may include at least one instruction related to the user terminal device <NUM>. The memory <NUM> may include a semiconductor memory such as a flash memory, or a magnetic storage medium such as a hard disk, or the like. Further, the memory <NUM> may store various kinds of information such as various kinds of data input, set, or generated during execution of the programs or the applications therein.

In addition, the memory <NUM> may include various software modules for operating the user terminal device <NUM> according to various embodiments, and the processor <NUM> may execute the various software modules stored in the memory <NUM> to perform an operation of the user terminal device <NUM> according to various embodiments.

Further, the memory <NUM> may store the information associated with the display device <NUM> and connection information.

The processor <NUM> may be electrically connected to the memory <NUM> to control overall operation and function of the user terminal device <NUM>. The processor <NUM> may be implemented in various forms. For example, the processor <NUM> may be implemented by at least one of an application specific integrated circuit (ASIC), an embedded processor, a microprocessor, a hardware control logic, a hardware finite state machine (FSM), or a digital signal processor (DSP).

In particular, according to an embodiment, based on receiving the content request signal from the display device <NUM>, the processor <NUM> may identify a type of the content that is currently being output via the user terminal device <NUM>. Specifically, the processor <NUM> may analyze metadata of content that is being output, or the like to identify the type of content. Further, the processor <NUM> may control the communication interface <NUM> to transmit information associated with the content that is being output via the user terminal device <NUM> to the display device <NUM> by using different communication methods according to the identified type of content.

According to an embodiment, in a case where the content that is being currently output is identified as audio content, the processor <NUM> may control the communication interface <NUM> to transmit, to the display device <NUM>, information associated with the audio content that is being output by using Bluetooth communication. Further, in a case where the content that is being currently output is identified as video content, the processor <NUM> may control the communication interface <NUM> to transmit, to the display device <NUM>, information associated with the video content that is being output by using P2P communication.

Meanwhile, based on receiving the content request signal f from the display device <NUM>, the processor <NUM> may control the display <NUM> to display the UI for selecting information associated with the content to be transmitted to the display device <NUM>. Further, based on receiving a selection of information associated with the content via the UI for selecting the information associated with the content to be transmitted to the display device <NUM>, the processor <NUM> may control the communication interface <NUM> to transmit information associated with the selected content to the display device <NUM>. According to an embodiment, and in a case where information associated with audio data is selected for transmission, the processor <NUM> may control the communication interface <NUM> to transmit the information associated with the audio data to the display device <NUM> by using Bluetooth communication. In a case where information regarding video data is selected for transmission, the processor <NUM> may control the communication interface <NUM> to transmit the information associated with the video data to the display device <NUM> by using P2P communication.

<FIG> is a sequence diagram illustrating a process in which the display device outputs content that is being output via the user terminal device, according to an embodiment.

First, the display device <NUM> may detect a content request event associated with a request for the display device <NUM> to output information associated with content that is being output via the user terminal device <NUM> (S410). According to an embodiment, the content request event may be an event in which the user terminal device <NUM> is brought within communicative proximity of the NFC tag including information (e.g., a MAC address of the display device) and connection information. Based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag, the user terminal device <NUM> may receive the information associated with the display device <NUM> that is stored in the NFC tag, and transmit the wake-up signal to the display device <NUM> (S420). Based on receiving the wake-up signal, the display device <NUM> may enter the standby mode in which the predetermined standby screen is provided, even when the display device <NUM> is powered off (S430). Specifically, based on entering the standby mode, the display device <NUM> may display, on a region corresponding to a position where the user terminal device <NUM> is within communicative proximity, the indicator indicating that the user terminal device is within communicative proximity.

The display device <NUM> may transmit, to the user terminal device <NUM>, the signal for requesting information associated with content that is being output via the user terminal device <NUM> (S440). Based on receiving the signal for requesting information associated with content that is being output via the user terminal device <NUM>, the user terminal device <NUM> may identify a type of the content that is being output (S450). Specifically, the user terminal device <NUM> may analyze metadata of the content that is being output to identify whether the type of content is audio data or video data.

Further, the user terminal device <NUM> may transmit the information associated with the content by using different communication methods based on the identified type of content (S460). Specifically, the user terminal device <NUM> may utilize connection information received from the display device <NUM> when transmitting the information associated with the content by using the different communication methods. According to an embodiment, and in a case where the content is identified as audio content, the user terminal device <NUM> may transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication. Further, and in a case where the content is identified as video content, the user terminal device <NUM> may transmit information regarding the video content to the display device <NUM> by using P2P communication.

The display device <NUM> may output the content in a manner according to the type of content, based on the received information regarding the content (S470). Specifically, in a case where the content that is being output via the user terminal device <NUM> is audio content, the display device <NUM> may display an audio UI that is different than a UI that is concurrently being displayed on the user terminal device <NUM> while outputting the audio content, based on received information associated with the audio content. alternatively, and in a case where the content that is being output via the user terminal device <NUM> is video content, the display device <NUM> may be switched from the standby mode to the normal mode, and display the video content and the indicator indicating that information associated with the video content is received, based on the received information associated with the video content.

<FIG> are views for describing a process in which the display device <NUM> receives information associated with video content from the user terminal device <NUM>, and outputs content based on the received information according to an embodiment.

As shown in <FIG>, the display device <NUM> may be in a powered-off state. A function to be described later may be performed even in a state in which the display device <NUM> is powered off.

As shown in <FIG>, based on the user terminal device <NUM> being brought within communicative proximity of the powered-off display device <NUM>, the display device <NUM> may receive the wake-up signal from the user terminal device <NUM> and enter the standby mode in which the predetermined standby screen <NUM> is provided.

Specifically, the display device <NUM> may display, on a region of the standby screen <NUM>, indicators <NUM> and <NUM> indicating that the user terminal device <NUM> is within communicative proximity of the display device <NUM>. The region may correspond to a position where the user terminal device <NUM> is within communicative proximity. According to an embodiment, and as shown in <FIG>, in a case where the user terminal device <NUM> is within communicative proximity of the display device <NUM> at the right-upper side of the display device <NUM>, the display device <NUM> may display the indicator <NUM> indicating that the user terminal device <NUM> is within communicative proximity, on a right-upper side region of the display <NUM>. In <FIG>, the indicator <NUM> indicating that the user terminal device <NUM> is within communicative proximity on the right-upper side region of the display <NUM> is implemented in a form in which water spreads, but this is merely an embodiment, and the indicator <NUM> may be implemented in various forms. As video content is being output via the user terminal device <NUM>, the display device <NUM> may display the indicator <NUM> indicating video content on the right-upper region of the display <NUM>. Although the indicator <NUM> indicating video content is implemented by a play button in <FIG>, the indicator <NUM> may be a thumbnail icon of video content to be received from the user terminal device <NUM>, or may be a title of the received image content. That is, the indicators <NUM> and <NUM> illustrated in <FIG>, which indicate that the user terminal device <NUM> is within communicative proximity, are merely an embodiment, and the indicators <NUM> and <NUM> indicating that the user terminal device <NUM> is within communicative proximity may be implemented in various forms.

Further, base on the user terminal device <NUM> being brought within communicative proximity of the display device <NUM>, the display device <NUM> may receive information (e.g., an IP address, received content history, user information, security settings, a network environment, and the like, of the user terminal device <NUM>) associated with the user terminal device <NUM>. Therefore, the display device <NUM> may display, on the standby screen <NUM>, a UI <NUM>-<NUM> indicating that the user terminal device <NUM> is within communicative proximity, based on the received information. For example, in a case where information indicating that a name of a user of the user terminal device <NUM> is "Chulsoo" is received from the user terminal device <NUM>, the display device <NUM> may display, on the standby screen <NUM>, the UI <NUM>-<NUM> that displays a phrase "Hello, Chulsoo. " Further, the display device <NUM> may display, on the standby screen <NUM>, a UI <NUM>-<NUM> that displays weather and calendar information or a UI <NUM>-<NUM> that displays latest content information, but this is merely an embodiment, and the display device <NUM> may display a UI displaying various types of information.

Based on the user terminal device <NUM> being brought within communicative proximity of the display device <NUM>, the display device <NUM> may transmit, to the user terminal device <NUM>, a signal that requests the user terminal device <NUM> for information associated with content. As shown in <FIG>, based on receiving the signal that requests information associated with content from the display device <NUM>, the user terminal device <NUM> may identify that video content is being output, and transmit information associated with the video content to the display device <NUM> by using P2P communication.

Further, as shown in <FIG>, in a case where content that is being output via the user terminal device <NUM> is video content, the display device <NUM> may be switched from the standby mode to the normal mode, and display video content <NUM>, and the indicator <NUM> indicating that video content is received, based on the information associated with the video content that is received from the user terminal device <NUM>. According to an embodiment, the display device <NUM> may display the indicator <NUM> indicating that video content is received for a predetermined time frame and then remove the indicator <NUM>.

<FIG> and <FIG> are views for describing a process in which the display device <NUM> receives information associated with audio content from the user terminal device <NUM>, and outputs the audio content based on the received information associated with the audio content, according to an embodiment.

<FIG> and <FIG> illustrate a similar situation as that shown in <FIG> except that audio content is output instead of video content.

As illustrated in <FIG>, the display device <NUM> may display indicators <NUM> and <NUM> indicating that the user terminal device <NUM> is within communicative proximity, on a region of the standby screen <NUM>. The region may correspond to a position where the user terminal device <NUM> is within communicative proximity. In contrast to <FIG>, the user terminal device <NUM> outputs audio content, and thus the indicator <NUM> indicating that the user terminal device <NUM> is within communicative proximity may have a musical note shape corresponding to audio content. It should be understood that this is merely an embodiment, and the indicator <NUM> indicating that the user terminal device <NUM> is within communicative proximity may be implemented in various forms. Further, as shown in <FIG>, based on receiving the signal that requests information associated with content that is being output via the user terminal device <NUM> from the display device <NUM>, the user terminal device <NUM> may identify that audio content is being output, and transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication.

As shown in <FIG>, based on receiving the information associated with the audio content from the user terminal device <NUM>, the display device <NUM> may display, on the standby screen <NUM>, the audio Uls <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> that are different than a UI that is being concurrently displayed via the user terminal device <NUM>, and output the audio content based on the received information associated with the audio content. Further, the display device <NUM> may display, on the standby screen <NUM>, the audio Uls <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> that are generated based on the received information (e.g., a title of the audio content, image information related to the audio content, a play history, a playback point, and a playlist) associated with the audio content that is received from the user terminal device <NUM>. Specifically, the display device <NUM> may display the audio UI <NUM>-<NUM>, the audio UI <NUM>-<NUM>, and the audio UI <NUM>-<NUM> on the standby screen <NUM>. The audio UI <NUM>-<NUM> may be generated based on information associated with the title of the audio content and the playback point, the audio UI <NUM>-<NUM> may be generated based on information regarding an image relevant to the received audio content, and the playback point, and the audio UI <NUM>-<NUM> may be generated based on received information associated with the play history. However, this is merely an embodiment, and the display device <NUM> may display, on the standby screen <NUM>, various Uls generated based on information regarding an audio content.

<FIG> is a view for describing a process in which the display device <NUM> receives information associated with content from the external server <NUM> and the user terminal device <NUM> according to an embodiment.

As shown in <FIG>, and in a case where video content that is being output via the user terminal device <NUM> is video content received from the external server <NUM>, the display device <NUM> may receive information associated with the video content from the user terminal device <NUM>. The information may include a title and a current playback point of the video content that is currently being output via the user terminal device <NUM>. According to an embodiment, and as shown in <FIG>, the display device <NUM> may receive, from the user terminal device <NUM>, information indicating that a title of the video content that is being output via the user terminal device <NUM> is "hiking," and information identifying that a current playback point of the video content is <NUM> minutes. Then, the display device <NUM> may receive, from the external server <NUM> from which the user terminal device <NUM> also receives the video content, a portion of the video content that corresponds to the current playback point of the video content that is being output via the user terminal device <NUM>, based on the received information. According to an embodiment, the display device <NUM> may receive, from the external server <NUM>, video content titled "hiking" after the playback point of <NUM> minutes. Therefore, the display device <NUM> may receive and display the video content that corresponds to the current playback point of the video content that is received from the external server <NUM> and is being output via the user terminal device <NUM>.

<FIG> and <FIG> are views for describing a process in which the user terminal device <NUM> is brought within communicative proximity of the external device <NUM> connected to the display device <NUM>, according to an embodiment. In <FIG>, the external device <NUM> is implemented by a remote controller, but this is merely an embodiment, and the external device <NUM> may be implemented by various devices such as an Al speaker. According to an embodiment, the external device <NUM> may include an NFC tag in which information (e.g., a MAC address of the display device <NUM>) associated with the display device <NUM> and connection information are stored.

According to an embodiment, based on the display device <NUM> being in a powered-off state, and based on the user terminal device <NUM> being brought within communicative proximity of the external device <NUM> connected to the display device <NUM>, the user terminal device <NUM> or the external device <NUM> may transmit the wake-up signal to the display device <NUM>. Based on the wake-up signal being received, the display device <NUM> may enter the standby mode in which the predetermined standby screen <NUM> is provided. Specifically, the display device <NUM> may display, on the standby screen <NUM>, the indicator <NUM> indicating that the user terminal device <NUM> is within communicative proximity of the external device <NUM>, the UI <NUM>-<NUM> including information associated with the user terminal device <NUM> that is received from the user terminal device <NUM>, and the Uls <NUM>-<NUM> and <NUM>-<NUM> indicating weather and calendar information and latest content, respectively. However, this is merely an embodiment, and the display device <NUM> may display a UI including various types of information, on the standby screen <NUM>.

Further, the display device <NUM> may transmit, to the user terminal device <NUM>, the signal that requests information associated with content that is being output via the user terminal device <NUM>. That is, as similar to the case where the user terminal device <NUM> is directly brought within communicative proximity of the display device <NUM>, the display device <NUM> may transmit the signal that requests information associated with content that is being output via the user terminal device <NUM> even in a case where the user terminal device <NUM> is within communicative proximity of the external device <NUM> connected to the display device <NUM>.

In <FIG>, the user terminal device <NUM> outputs audio content, and thus the user terminal device <NUM> may transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication. A subsequent process has been described above with reference to <FIG>, and thus a redundant description may be omitted.

<FIG> are views for describing a process in which the user terminal device <NUM> is brought within communicative proximity of an NFC tag external to the display device <NUM>, according to an embodiment. Specifically, the NFC tag including information (e.g., a MAC address of the display device <NUM>) associated with the display device <NUM>, and connection information (e.g., a Bluetooth MAC address and a P2P device MAC address) may be external to the display device <NUM>. That is, the NFC tag may be disposed externally to the display device <NUM>, and the embodiments shown in <FIG> are merely embodiments.

According to an embodiment, an NFC tag <NUM> may be disposed on a table <NUM> as shown in <FIG>. Based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag <NUM>, the user terminal device <NUM> may receive, from the NFC tag <NUM>, information associated with the display device <NUM> and connection information via NFC with the NFC tag <NUM>. Further, the user terminal device <NUM> may connect to the display device <NUM> based on the received information.

The display device <NUM> may transmit, to the user terminal device <NUM>, the signal that requests information associated with content that is currently being output via the user terminal device <NUM>. Based on receiving the signal that requests the information associated with content, the user terminal device <NUM> may identify a type of the content that is currently being output, and transmit, to the display device <NUM>, information associated with the content that is being output by using different communication methods according to the identified type of content. Referring to <FIG>, based on video content being output via the user terminal device <NUM>, the user terminal device <NUM> may transmit, to the display device <NUM>, information associated with the video content by using P2P communication. Further, the display device <NUM> may display the video content and the indicator indicating that the video content is received, based on the received information associated with the video content. A detailed description of the screen on which the video content is output has been provided above with reference to <FIG> and <FIG>, and thus redundant description may be omitted.

According to an embodiment, an NFC tag <NUM> may be disposed on a vehicle handle <NUM> as shown in <FIG>.

Specifically, based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag <NUM>, the user terminal device <NUM> may receive, from the NFC tag <NUM>, information associated with the display device <NUM> and connection information via NFC with the NFC tag <NUM>. Further, the user terminal device <NUM> may connect to the display device <NUM> based on the received information. The display device <NUM> may transmit, to the user terminal device <NUM>, the signal that requests transmission of information associated with content that is being output via the user terminal device <NUM>. Based on receiving the signal that requests the transmission of information associated with content, the user terminal device <NUM> may identify a type of the content that is currently being output, and transmit, to the display device <NUM>, information associated with the content that is being output by using different communication methods according to the identified type of content. Referring to <FIG>, based on audio content being output via the user terminal device <NUM>, the user terminal device <NUM> may transmit, to the display device <NUM>, information associated with the audio content by using Bluetooth communication. Then, the display device <NUM> may output the audio content based on the received information associated with the audio content and display, on the standby screen <NUM>, the audio Uls <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> that are different than the UI that is concurrently displayed via the user terminal device <NUM>. A detailed description of the standby screen <NUM> and the audio Uls <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> has been provided above with reference to <FIG> and <FIG>, and thus redundant description may be omitted.

According to an embodiment, an NFC tag <NUM> may be disposed on a bed <NUM> as shown in <FIG>. According to an embodiment, the NFC tag <NUM> may include a control instruction for executing a specific application, in addition to information associated with the display device <NUM> and connection information. Specifically, based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag <NUM>, the user terminal device <NUM> may receive, from the NFC tag <NUM>, information associated with the display device <NUM>, connection information, and a control instruction for executing an alarm application. The user terminal device <NUM> may connect to the display device <NUM> based on the information received from the NFC tag <NUM> via NFC, and execute an alarm application <NUM>.

Further, according to an embodiment, based on a user instruction (e.g., an instruction to set an alarm for <NUM>:<NUM> as shown in <FIG>) being input to the application <NUM> executed by the user terminal device <NUM>, the user terminal device <NUM> may transmit a signal including the input instruction to the display device <NUM>. Further, the display device <NUM> may display a notification UI <NUM> that is generated based on the received signal and set alarm.

<FIG> illustrates a case where the NFC tag <NUM> includes the control instruction for executing the alarm application, but this is merely an embodiment, and the NFC tag <NUM> may include various control instructions.

<FIG> is a view for describing a case where the display device <NUM> is implemented by an Al speaker <NUM>, according to an embodiment. An NFC tag <NUM> illustrated in <FIG> may include information (e.g., a MAC address of the Al speaker) associated with the Al speaker <NUM>, and connection information (e.g., a Bluetooth MAC address and a P2P device MAC address). In addition, the NFC tag <NUM> may be embedded in the Al speaker <NUM> or disposed on an outer portion of the Al speaker <NUM>.

Based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag <NUM>, the user terminal device <NUM> may receive, from the NFC tag <NUM>, information associated with the Al speaker <NUM> and connection information via NFC. The Al speaker <NUM> may transmit, to the user terminal device <NUM>, the signal that requests information associated with content that is currently being output via the user terminal device <NUM>. Based on receiving the signal that requests information associated with content, the user terminal device <NUM> may identify a type of the content that is being output, and transmit, to the Al speaker <NUM>, information associated with the content by using different communication methods according to the identified type of content. In <FIG>, based on audio content being output, the user terminal device <NUM> may transmit information associated with the audio content to the AI speaker <NUM> by using Bluetooth communication. Further, the Al speaker <NUM> may output the audio content based on the received information associated with the audio content.

In addition, based on the Al speaker <NUM> being in a powered-off state, and based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag <NUM>, the user terminal device <NUM> may transmit the wake-up signal to the Al speaker <NUM>. Based on receiving the wake-up signal, the Al speaker <NUM> may be powered on to output the received content.

According to an embodiment, the Al speaker <NUM> may not include the NFC tag <NUM>. In this case, based on detecting a content request event, the Al speaker <NUM> may transmit, to the user terminal device <NUM>, the signal that requests transmission of information associated with content that is currently being output via the user terminal device <NUM>. The content request event may be an event in which the user terminal device <NUM> transmits, to the Al speaker <NUM>, a signal that induces transmission of the signal that requests information associated with content that is currently being output.

<FIG> illustrates a case where the display device <NUM> is implemented by an Al speaker <NUM>, but this is merely an embodiment, and the display device <NUM> may be implemented by various electronic devices such as a PC.

<FIG> are views for describing processes in which a connection between the display device <NUM> and the user terminal device <NUM> is terminated according to an embodiment.

According to the claimed embodiment, and as shown in <FIG>, based on the user terminal device <NUM> being brought within communicative proximity the display device <NUM> after a connection is established, the connection between the display device <NUM> and the user terminal device <NUM> may be ended. That is, based on the user terminal device <NUM> being brought within communicative proximity of the NFC tag of the display device <NUM> in a state in which the connection between the display device <NUM> and the user terminal device <NUM> is established, the connection may be ended. Put another way, the user of the user terminal device <NUM> may perform a first NFC tap to establish the connection, and perform a second NFC tap to end the connection. The display device <NUM> may display a UI <NUM> indicating that the connection is ended. The UI <NUM> indicating that communicative connection is ended may be a UI including a message "connection with Chulsoo has been ended" as shown in <FIG>, but this is merely an embodiment, and the UI <NUM> may be implemented in various forms.

Alternatively, and according to an embodiment, based on the user terminal device <NUM> being moved away from the display device <NUM> by a distance exceeding a threshold distance <NUM> in a state in which a connection between the display device <NUM> and the user terminal device <NUM> is established, the connection may be ended. Specifically, based on a distance between the user terminal device <NUM> and the display device <NUM> exceeding the threshold distance, the user terminal device <NUM> may transmit, to the display device <NUM>, a signal that ends the connection. Based on receiving the signal that ends the connection, the display device <NUM> may end the connection with the user terminal device <NUM>, and display the UI <NUM> indicating that connection is ended.

According to an embodiment, based on another user terminal device <NUM>-<NUM> being brought within communicative proximity of the display device <NUM> in a state in which a connection between the display device <NUM> and the user terminal device <NUM> is established, the established connection may be ended. That is, based on another user terminal device <NUM>-<NUM> being brought within communicative proximity of the display device <NUM>, the display device <NUM> may end the established connection with the user terminal device <NUM>, and display the UI <NUM> indicating that connection is ended. Further, the display device <NUM> may transmit, to the terminal device <NUM>-<NUM> that is more recently brought within communicative proximity, the signal that requests information associated with content that is currently being output.

<FIG> is a view for describing a UI <NUM> for selecting information associated with content to be transmitted from the user terminal device <NUM> to the display device <NUM> according to an embodiment.

Based on receiving the signal that requests information associated with content that is currently being output from the display device <NUM>, the user terminal device <NUM> may display the UI <NUM> for selecting information associated with content to be transmitted to the display device <NUM>. Specifically, the UI <NUM> for selecting information associated with content may include Uls <NUM>, <NUM>, and <NUM> indicating content to be transmitted. The UI <NUM> corresponding to audio content may have a musical note shape as shown in <FIG>, but this is merely an embodiment, and the UI <NUM> may be a UI including metadata of audio content. The UI <NUM> corresponding to video content may have a play button shape as shown in <FIG>, but this is merely an embodiment, and the UI <NUM> may be a thumbnail icon of the video content or a UI including a title of the content, or the like. The UI <NUM> corresponding to a uniform resource locator (URL) may be a UI in which a word "URL" is written as shown in <FIG>, or may be a UI including a name of a website accessible via the URL, or control information for installing an application.

Based on information associated with content being selected via the UI <NUM>, the user terminal device <NUM> may transmit the selected information associated with content to the display device <NUM>. Particularly, the user terminal device <NUM> may transmit the information associated with content to the display device <NUM> by using different communication methods according to a type of selected information associated with content. Further, the user terminal device <NUM> may utilize connection information (e.g., a Bluetooth MAC address and a P2P device MAC address) received from the display device <NUM> to transmit the information associated with content to the display device <NUM> by using different communication methods according to the type of selected content. According to an embodiment, based on the selected content being audio content, the user terminal device <NUM> may transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication. Further, based on the selected content being video content, the user terminal device <NUM> may transmit information associated with the video content to the display device <NUM> by using P2P communication.

<FIG> are views for describing a process in which the display device <NUM> determines whether to rotate the display <NUM> according to an embodiment.

First, as shown in <FIG>, based on the user terminal device <NUM> being brought within communicative proximity of the powered-off display device <NUM>, the display device <NUM> may receive the wake-up signal from the user terminal device <NUM>, and enter the standby mode in which the predetermined standby screen <NUM> is provided. A description of entering the standby mode has been provided above with reference to <FIG>, and thus a redundant description may be omitted.

Further, the display device <NUM> may determine whether to rotate the display <NUM> based on information associated with video content that includes information identifying orientation information of the video content received from the user terminal device <NUM>. Specifically, the display device <NUM> may identify whether an orientation of the display <NUM> and an orientation of the video content are different from each other based on the information received from the user terminal device <NUM>. Based on identifying that the orientation of the display <NUM> and the orientation of the video content are different from each other, the display device <NUM> may determine to rotate the display <NUM>. According to an embodiment, and as shown in <FIG>, based on the information indicating that the orientation of the video content is a portrait orientation being received from the user terminal device <NUM> based on the orientation of the display <NUM> being a landscape orientation, the display device <NUM> may identify that the orientation of the display <NUM> and the orientation of the video content are different from each other. Further, the display device <NUM> may determine to rotate the display <NUM> into the portrait orientation, and rotate the display <NUM> into the determined orientation.

According to an embodiment, based on the information indicating that the orientation of the video content is the landscape orientation being received from the user terminal device <NUM> and based on the orientation of the display <NUM> being the portrait orientation, the display device <NUM> may identify that the orientation of the display <NUM> and the orientation of the video content are different from each other. Further, the display device <NUM> may determine to rotate the display <NUM> into the landscape orientation, and rotate the display <NUM> into the determined orientation.

According to an embodiment, based on the information indicating that orientation information of video content is changed being received from the user terminal device <NUM>, the display device <NUM> may rotate the display <NUM> based on the information indicating that orientation information is changed. According to an embodiment, based on both of the orientation of the video content and the orientation of the display <NUM> being the landscape orientation, and based on information indicating that the orientation of the video content received from the user terminal device <NUM> is changed from the landscape orientation to the portrait orientation being received, the display device <NUM> may rotate the display <NUM> into the portrait orientation from the landscape orientation.

<FIG> is a flowchart for describing a method for controlling the display device <NUM> according to an embodiment. First, based on detecting a content request event associated with a request for the display device <NUM> to output information associated with content that is being output via the user terminal device <NUM>, the display device <NUM> may request the user terminal device <NUM> for information associated with content that is being output via the user terminal device <NUM> (S1610). According to an embodiment, the content request event may be an event in which the user terminal device <NUM> is brought within communicative proximity of an NFC tag in which information associated with the display device <NUM> is stored. That is, a user of the user terminal device <NUM> may perform an NFC tap using the user terminal device <NUM>. Put another way, the user may "tag" the user terminal device <NUM> to the NFC tag. Further, based on the user terminal device <NUM> being brought within communicative proximity of the display device <NUM> when the display device <NUM> is in a powered-off state, the display device <NUM> may receive the wake-up signal from the user terminal device <NUM>. Based on receiving the wake-up signal, the display device <NUM> may enter the standby mode in which the predetermined standby screen is provided. Further, the display device <NUM> may display the indicator indicating that the user terminal device <NUM> is within communicative proximity (e.g., that an NFC tap or tag has been performed), on a region of the standby screen that corresponds to a position where the user terminal device <NUM> is within communicative proximity (e.g., where the NFC tap or tag was performed).

The display device <NUM> may identify a type of the received content (S1620). According to an embodiment, based on determining that the received content is video content, the display device <NUM> may display the video content based on the received information associated with the video content (S1630). Specifically, in a case where information associated with video content is received, the display device <NUM> may be switched from the standby mode to the normal mode, and display the video content and the indicator indicating that the video content is received based on the information associated with the video content.

According to an embodiment, in a case where information associated with audio content is received from the user terminal device <NUM>, the display device <NUM> may display an audio UI that is different from a UI that is concurrently being displayed via the user terminal device <NUM>, and output the audio content based on the received information associated with the audio content (S1640). Specifically, the display device <NUM> may generate the audio UI based on the received information associated with the audio content. Further, the display device <NUM> may output the audio content based on the information associated with the audio content, and display the audio UI on the standby screen.

<FIG> is a flowchart for describing a method for controlling the user terminal device <NUM> according to an embodiment. First, based on receiving the signal that requests information associated with content that is currently being output via the user terminal device <NUM> from the display device <NUM> while the content is output, the user terminal device <NUM> may identify a type of the content that is currently being output via the user terminal device <NUM>. Specifically, the user terminal device <NUM> may analyze metadata of the content that is currently being output to identify whether the content is audio content or video content (S1710).

Further, the user terminal device <NUM> may transmit information associated with content that is being output via the user terminal device <NUM> to the display device <NUM> by using different communication methods based on the identified type of content (S1720). Specifically, in a case where the content that is being output is identified as audio content, the user terminal device <NUM> may transmit information associated with the audio content to the display device <NUM> by using Bluetooth communication. In a case where the content that is being played is identified as video content, the user terminal device <NUM> may transmit information associated with the video content to the display device <NUM> by using P2P communication.

As used herein, the terms "module" or a "[function]er/or" may denote a unit implemented in hardware, software, or firmware, and may be used interchangeably with a term such as logic, a logic block, a part, or a circuit. The terms "[function]er/or" or "module" may indicate an integrated part, or a minimum unit for performing one or more functions, or part thereof. For example, a module may be implemented by an ASIC.

Various embodiments of the disclosure may be implemented by software including instructions stored in a machine-readable storage medium (e.g., a non-transitory computer-readable medium). A machine may be a device that invokes the stored instruction from the storage medium and may be operated depending on the invoked instruction, and may include an electronic device (e.g., the display device <NUM>) according to the disclosed embodiments. In the case where an instruction is executed by the processor, the processor may directly perform a function corresponding to the instruction or other components may perform the function corresponding to the instruction under a control of the processor. The instruction may include code created or executed by a compiler or an interpreter. The machine-readable storage medium may be provided in a form of a non-transitory storage medium. Here, the term "non-transitory" may mean that the storage medium is tangible, and might not distinguish whether data is semi-permanently or temporarily stored on the storage medium.

According to an embodiment, the methods according to the embodiments may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a purchaser. The computer program product may be distributed in a form of a storage medium (e.g., a compact disc read only memory (CD-ROM)) that may be read by the machine or online through an application store (e.g., PlayStoreTM). In the case of the online distribution, at least portions of the computer program product may be at least temporarily stored in a storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server or be temporarily created.

Claim 1:
A display device (<NUM>) comprising:
a communication interface (<NUM>) configured to communicate with a user terminal device (<NUM>);
a display (<NUM>);
a memory (<NUM>) configured to store at least one instruction; and
a processor (<NUM>) configured to execute the at least one instruction to:
in response to detecting of a content request event associated with a request for the display device to output information associated with content that is being output via the user terminal device, receive the information associated with the content from the user terminal device via the communication interface;
based on the type of content that is being output via the user terminal device being video content, control the display to display the video content based on information associated with the video content that is received from the user terminal device; and
based on the type of content that is being output via the user terminal device being audio content, control the display to display an audio user interface (UI) that is different than a UI that is concurrently being displayed via the user terminal device, and control the display device to output the audio content, based on information associated with the audio content that is received from the user terminal device;
wherein the processor is further configured to execute the at least on instruction to:
based on the user terminal device being moved within communicative proximity of a NFC tag of the display device in a state in which a connection between the display device and the user terminal device is established, the connection between the display device and the user terminal device is ended.