KR102007841B1 - Media share control apparatus, media display apparatus, server for providing a media share application and media share method - Google Patents

Abstract

Disclosed are a media sharing controller, a media player, a media sharing application providing server, and a media sharing method. The network interface unit receives a search message for searching for a media service daemon from the media player. The control unit executes a receiver picker and a media service daemon. In response to receiving the search message, the executed media service daemon proceeds to pair with the media player, converts the media share message sent by the receiver picker according to the paired media player and the web-based protocol promised, The media sharing message may be transmitted to the paired media player.

Description

Media share control apparatus, media playback apparatus, server for providing media sharing application and media sharing method {media share control apparatus, media display apparatus, server for providing a media share application and media share method}

The present invention relates to a media sharing controller, a media player, a media sharing application providing server, and a media sharing method, and more particularly, to a sharing controller, a media sharing receiver, and a media sharing method capable of sharing media content in real time. It is about.

Electronic devices such as smart phones and smart TVs provide a function to automatically or additionally install a web app. A web app is an application that can be accessed over the Internet, written in a language supported by the browser, and refers to software that can run on a web browser. These web apps are installed in electronic devices such as smart phones and smart TVs, so that the smart phones and smart TVs can be utilized as general-purpose devices capable of performing various functions.

In addition, electronic devices such as smart phones and smart TVs may share media with each other in real time based on media sharing technologies such as AirPlay and Digital Living Network Alliance (DLNA).

DLNA (Digital Living Network Alliance) is an official partnership for the commercialization of home networks. It aims to build interoperable platforms based on open industry standards already in place and to achieve industry convergence. . Such DLNA is promoting the introduction of guidelines by companies based on Universal Plug and Play (UPnP), which is widely used by manufacturers of consumer electronics, personal computers (PCs), and wireless devices.

The guidelines currently introduced in DLNA provide design principles for sharing content between different brands and products through wired and wireless home networks between consumer electronics, PCs and wireless devices. Therefore, products designed according to the guidelines can share media contents such as music, photos, and videos through the home network, and are stored in the media server in real time through streaming to the media player. Play shared media content.

AirPlay is Apple's media sharing technology.

In order to implement a media receiver using a conventional media sharing technology, it is necessary to implement many components necessary for a media service using functions supported by a native platform. In particular, the media receiver cannot be implemented using only web standard technologies such as Javascript, HTML, and Hypertext Markup Language 5 (HTML 5), and thus the media receiver cannot be implemented using a web app type.

An object of the present invention is to provide a media sharing controller, a media player, a media sharing application providing server, and a media sharing method, which can be designed to implement a media receiver with standard web technologies.

Another object of the present invention is to provide a media sharing control device, a media player, a media sharing application providing server, and a media sharing method for enabling a media sharing application to be implemented in a thin client.

Another technical problem to be achieved by the present invention is to provide a media sharing controller, a media player, a media sharing application providing server, and a media sharing method for enabling a media sharing application that performs the functions of a media receiver to be implemented as a web app type. have.

Another technical problem to be achieved by the present invention is to provide a media sharing control device, a media playback device, and a user interface providing method for media sharing, which can provide a user with a media sharing service more conveniently.

In order to achieve the above technical problem, a media sharing controller according to the present invention includes a network interface unit for receiving a search message for searching for a media service daemon from a media player, and a receiver picker and a media service daemon. And a control unit configured to execute a media service daemon, wherein the executed media service daemon performs pairing with the media player in response to receiving the search message, and sends a media sharing message transmitted by the receiver picker. And converts the converted media sharing message to the paired media player according to a web-based protocol promised with the paired media player.

The media sharing message may include at least one of a play command, a playback command, and a stop command. The play command may include a Uniform Resource Locator (URL) of content that the receiver picker commands to play, and the media player may receive a media stream of the content based on the URL.

The media service daemon may control the receiver picker to transmit at least one of a service name of a media sharing service, its address, and a device name of the media player.

The media service daemon may include the paired media player in a media receiver list.

The media service daemon can run in the background.

The media service daemon may open and wait for a port for receiving a search message transmitted from the media player.

The media service daemon may be implemented in a plug-in manner.

Among the modules of the media service daemon, at least one of a module for communicating with the receiver picker through a media sharing protocol and a module for discovering the receiver picker may be plugged in.

In accordance with another aspect of the present invention, there is provided a media playback apparatus including a network interface unit for transmitting a search message for searching for a media service daemon to a media sharing controller, and a websocket-based service discovery and communication management module. And a controller for executing the search, wherein the executed websocket-based service discovery controls the search message to be transmitted according to a web-based protocol promised with the media sharing controller, and sends the search message to the media sharing controller. When receiving a response to the, and performs a pairing with the media sharing control device, the executed communication management module receives a media sharing message transmitted according to the web-based protocol from the paired media sharing control device In the received media sharing You can parse the message.

The media sharing message may include at least one of a play command, a playback command, and a stop command. The play command may include a uniform resource locator (URL) of content that the media control device plays command, and the controller may control to receive a media stream of the content based on the URL.

The websocket-based service discovery may control the search message to be transmitted to all Internet Protocol (IP) addresses in the subnetwork to which the media player belongs.

In accordance with another aspect of the present invention, there is provided a media sharing application providing server according to an embodiment of the present invention, a storage unit storing at least one of a media receiver application and a media service daemon application, a media receiver application or a media service daemon from an electronic device. The network interface unit may receive a message requesting the download of an application, and a control unit may be configured to control the stored media receiver application or the stored media service daemon application to be transmitted to the electronic device in response to receiving the message.

In accordance with another aspect of the present invention, there is provided a media sharing method according to the present invention, wherein a media service daemon receives a first search message for searching for a media service daemon from a media player, and receiving the first search message. In response, the media service daemon performing pairing with the media player, the media service daemon receiving a second search message from the receiver picker to confirm the existence of the media sharing service, 2 in response to receiving the search message, the media service daemon sending a response to the receiver picker for a second search message, the media service daemon receiving a media play request message from the receiver picker, the media The service daemon received the media play request message May be converted according to a web-based protocol promised with the paired media player, and controlling the media service daemon to transmit the converted media play request message to the paired media player. .

In accordance with another aspect of the present invention, there is provided a method for providing a user interface for media sharing according to the present invention. The method comprises: displaying a first graphical user interface (GUI) for selecting at least one media sharing control device; Detecting a user action of selecting a media sharing control device through the displayed first GUI; requesting a connection to the selected media sharing control device in response to detecting the user action; In response to receiving an authentication key transmission request from the media sharing control device, displaying a second GUI for receiving an authentication key, and if an authentication key is input, inputting the authentication to the media sharing control device. And transmitting the key.

The method for providing a user interface for media sharing may include transmitting a search message for searching for a media service daemon to a media sharing control device, receiving a response to the search message from the media sharing control device, and receiving the search message. The method may further include generating the first GUI based on the received response. The search message may be sent according to a web-based protocol promised with the media sharing control device. The search message may be sent to all IP (Internet Protocol) addresses in the subnetwork. The search message may be sent to a port agreed with the media sharing control device.

The method for providing a user interface for media sharing may include receiving a play command from the media sharing controller, and receiving a media stream based on a Uniform Resource Locator (URL) included in the received play command. And playing the received media stream. The playback command may be sent according to a web-based protocol promised with the media sharing control device.

In accordance with another aspect of the present invention, there is provided a method for providing a user interface for media sharing according to the present invention, the method comprising: displaying a graphical user interface (GUI) for executing a media service daemon, the media service Detecting a user action requesting the execution of a daemon; executing the media service daemon in response to detecting the user action; receiving a connection request from a media player; in response to receiving the connection request, authentication Requesting a key, receiving an authentication key from the media player, verifying the received authentication key, and transmitting the verification result to the media player. When the received authentication key and the authentication key displayed by the GUI are the same, a connection right may be given to the media player.

In accordance with another aspect of the present invention, there is provided a media playback apparatus comprising: a display for displaying a first graphical user interface (GUI) for selecting at least one media sharing control device; Detect a user action of selecting a media sharing control device through the displayed first GUI, request a connection to the selected media sharing control device in response to detecting the user action, and share the media in response to the connection request; When the authentication device is requested to transmit the authentication key, the second GUI for receiving the authentication key is displayed. When the authentication key is input, the input key is transmitted to the media sharing controller. It may include a control unit.

The media playback apparatus may further include a network interface unit configured to transmit a search message for searching for a media service daemon to a media sharing controller, and wherein the controller is configured to receive a response to the search message from the media sharing controller. The first GUI may be generated based on the received response. The search message may be sent according to a web-based protocol promised with the media sharing control device.

The media playback apparatus further includes a network interface unit configured to receive a playback command from the media sharing controller, wherein the controller is configured to generate a media stream based on a Uniform Resource Locator (URL) included in the received playback command. ), And the display may display the received media stream.

In order to achieve the above technical problem, a media sharing control apparatus according to the present invention includes a display for displaying a graphical user interface (GUI) for executing a media service daemon, and execution of the media service daemon. Detects a user action requesting a request, executes the media service daemon in response to the user action detection, and receives a connection request from a media player, in response to receiving the connection request, And requesting an authentication key, and receiving an authentication key from the media player, the controller may verify the received authentication key and control the verification result to be transmitted to the media renewing device. The controller may grant a connection right to the media player when the received authentication key is identical to the authentication key displayed by the GUI.

According to the media sharing control device, the media playback device, the media sharing application providing server, the media sharing method, and the user interface providing method for media sharing according to the present invention, the media sharing control device and the media playback device are provided for pairing and media sharing. The media service daemon that relays messages can be designed to implement the media receiver stage using standard web technologies, enable media sharing applications in thin clients, and perform media receiver functions. The shared application can be implemented as a web app type, and the user can use the media sharing service more conveniently.

1 is a block diagram showing the configuration of a preferred embodiment of a media sharing system according to the present invention,
2 shows a platform of a preferred embodiment of a media sharing system according to the present invention;
3 is a block diagram showing the structure of a preferred embodiment of a media service daemon;
4 is a flowchart illustrating a process of performing a preferred embodiment of a service discovery method according to the present invention;
5 is a flowchart illustrating a process of performing another preferred embodiment of a service discovery method according to the present invention;
6 is a flowchart illustrating a process of performing a preferred embodiment of the method for controlling media sharing according to the present invention;
7 is a flowchart illustrating a process of performing a preferred embodiment of a media sharing method according to the present invention;
8 illustrates one embodiment of a graphical user interface for an authentication procedure;
9 illustrates an embodiment of a graphical user interface for media service daemon setup;
10 illustrates one embodiment of a graphical user interface for connecting a media service daemon;
11 illustrates an embodiment of a graphical user interface for detailed setup of a media receiver;
12 is a diagram illustrating an embodiment of a screen on which a media service is executed on a media sharing controller and a media player;
FIG. 13 is a flowchart illustrating another preferred embodiment of a media sharing method according to the present invention; FIG.
14 is a view showing another embodiment of a screen on which a media service is executed on a media sharing controller and a media player;
15 is a block diagram showing a configuration of a preferred embodiment of an electronic device according to the present invention;
16 is a block diagram showing the configuration of a preferred embodiment of a media sharing application providing server according to the present invention.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

The suffix "module" for components used in the following description may refer to programs, software, plug-ins, libraries, drivers, and programs running on electronic devices.

On the other hand, the electronic device described herein is, for example, an intelligent electronic device that adds a computer support function to the broadcast reception function. The electronic device is faithful to the broadcast reception function and has an Internet function added thereto. It can have more convenient interface than pad or space remote controller. In addition, it is connected to the Internet and a computer with the support of a wired or wireless Internet function, and can perform functions such as e-mail, web browsing, banking or gaming. Standardized general-purpose operating systems can be used for these various functions.

Therefore, in the electronic device described in the present invention, various applications can be freely added or deleted, for example, on a general-purpose OS kernel, so that various user-friendly functions can be performed. More specifically, the electronic device may be, for example, a network TV, an HBBTV, a smart TV, an open hybrid TV (OHTV), or the like, and may be applied to a smartphone, a PC, and a home appliance in some cases. In addition, applications installed on the electronic device may include an app and a web app.

Furthermore, although an embodiment of the present invention will be described in detail with reference to the accompanying drawings and the contents described in the accompanying drawings, the present invention is not limited or restricted by the embodiments.

The terminology used herein is a general term that has been widely used as far as possible in consideration of functions in the present invention, but may vary according to the intention or custom of a person skilled in the art or the emergence of a new technology. In addition, in certain cases, there is a term arbitrarily selected by the applicant, and in this case, the meaning will be described in the corresponding description of the invention. Therefore, it is to be understood that the terminology used herein is to be interpreted based on the actual meaning of the term and the contents throughout the specification, rather than simply on the name of the term.

1 is a block diagram showing the configuration of a preferred embodiment of a media sharing system according to the present invention.

Referring to FIG. 1, the media sharing system 1 may include at least one of a media server 10, a media player 20, a media sharing controller 30, and a media sharing application providing server 40. . The media server 10, the media player 20, the media sharing controller 30, and the media sharing application providing server 40 may be connected to a network 2.

The network 2 may be composed of at least one of a backbone network and a subscriber network. The backbone network may consist of one or more integrated networks of an X.25 network, a Frame Relay network, an ATM network, a Multi Protocol Label Switching (MPLS) network, and a Generalized Multi Protocol Label Switching (GMPLS) network. Subscriber networks include Fiber To The Home (FTTH), Asymmetric Digital Subscriber Line (ADSL), cable network, Wireless LAN (IEEE 802.11b, IEEE 802.11a, IEEE802.11g, IEEE802.11n), WiBro (Wireless Broadband), Wimax, and It may be High Speed Downlink Packet Access (HSDPA). In some embodiments, network 2 may be an Internet network or may be a mobile communication network.

In some embodiments, the media server 10, the media playback device 20 and the media sharing control device 30 may be located in the same subscriber network, local network or sub-network, and the media sharing application providing server 40 may be It can be located on a backbone or internet network.

The media server 10 stores media data such as photos, music, and videos, and provides the stored media data to the media player 20. The media server 10 may provide media data to the media player 20 by streaming.

The media player 20 reproduces the media data. The media player 20 may receive and play media streaming from the media server 10 under the control of the media sharing controller 30.

The media sharing controller 30 controls the media player 20 to play the media data stored in the media player 20 and the media server 10.

The media sharing control device 30 searches for and connects to the media server 10 and the media playback device 20 existing in the same network by a predetermined protocol, and provides a GUI for media data existing in the media server 10. Can provide. The user can easily select the media data and the media player 20 to be played back through the GUI provided to the media sharing controller 30. In this case, the predetermined protocol may include at least one of a multicast protocol and a web-based protocol.

The media sharing control device 30 may be configured as a mobile device having a touch screen that provides a GUI by a user's touch gesture. In addition, the media sharing control device 30 according to an embodiment of the present invention may provide a user interface by other UI means such as a gesture, a voice, or the like.

In FIG. 1, the media server 10, the media playback device 20, and the media sharing control device 30 are shown in separate configurations, but for convenience of description, the present invention is limited thereto. However, one electronic device may perform a function corresponding to two or more of them. That is, the media server 10 and the media playback device 20 may be configured as one electronic device, and the media playback device 20 and the media sharing control device 30 may be configured as one electronic device. The media server 10 and the media sharing control device 30 may be configured as one electronic device.

Hereinafter, a service that the media player 20 controls the media data stored in the media server 10 under the control of the media sharing controller 30 is called a media sharing service or a media service. Technologies to provide media services include AirPlay and Digital Living Network Alliance (DNLA).

The media sharing application providing server 40 provides applications for enabling the electronic device to perform a function of the media sharing control device 30 or the media playback device 20. Here, the provided applications may include an app or a web app. The electronic device may download the application from the media sharing application providing server 40 and install and execute the downloaded application to perform the functions of the media playback device 20 and the media sharing control device 30. In some embodiments, the application may be installed on an electronic device during manufacture.

2 illustrates a platform of a preferred embodiment of a media sharing system according to the present invention.

Referring to FIG. 2, the media sharing system 200 may include a media sender 210, a media receiver 220, and a media controller 230. The media sharing system 200 may be an embodiment of a platform of the media sharing system 1 shown in FIG. 1. The media sender 210 is an embodiment of the platform of the media server 10 shown in FIG. 1, the media receiver 220 is an embodiment of the platform of the media player 20 shown in FIG. 1, and the media The controller 230 may be an embodiment of a platform of the media sharing control device 30 shown in FIG. 1.

The media sender 210 may include a streaming server 213. The streaming server 213 transmits data, information, or media to the media receiver 220 by using the Hyper Text Transfer Protocol (HTTP). The HTTP server 216 transmits HTTP live streaming to the media receiver 220. It may include at least one of an HTTP Live Streaming (HLS) server 217 to transmit and an RTSP server 218 to transmit a media stream to the media receiver 220 using a Real Time Streaming Protocol (RTSP). Here, the streaming server 213 may be a module.

The media sender 210 may provide the media controller 230 with a media list 203 including information on media stored or managed by the media sender 210. The media sender 210 may be connected to the media controller 230 without performing discovery and may provide the media list 203 to the media controller 230.

The media receiver 220 may play the media stream 201 transmitted by the media sender 210 under the control of the media controller 230. The media receiver 220 may communicate with the media controller 230 through a web-based protocol to stream and play media data such as video, audio, and photos transmitted by the media sender 210. In addition, the media receiver 220 may discover the media controller 230.

The media receiver 220 may include at least one of an HTML5 media player 221, a communication management module 223, and a websocket-based service discovery 229. Can be.

WebSocket-based service discovery 229 searches for media service daemons in the network (1). The websocket-based service discovery 229 may search for the presence of the media service daemon in the subnetwork.

In some embodiments, websocket-based service discovery 229 may send a discovery message to sequentially search for the media service daemon to the media service daemon port of IP addresses in the subnetwork. The search message may be transmitted in a unicast manner. At this time, the websocket-based service discovery 229 may transmit the search message to all IP addresses in the subnetwork. Since multicast is not supported on the web, the present invention can find a media service daemon using unicast.

The websocket-based service discovery 229 may generate a media controller list by collecting IP addresses that have been confirmed that the media service daemon is running, and store the media controller list. In addition, the websocket-based service discovery 229 may automatically pair to a media controller having an IP address included in the media controller list, and display a list of media controllers on a screen to allow a user to select a media controller to pair with. .

The websocket-based service discovery 229 performs an authentication procedure with the media service daemon 240. The websocket-based service discovery 229 receives an authentication key from the user, which is displayed on a graphical user interface (GUI) of the media service daemon 240. The websocket-based service discovery 229 controls the input authentication key to be transmitted to the media service daemon 240 through the network 1, and the media service daemon 240 transmits the websocket-based service discovery 229. The connection authority may be granted to the media receiver 220 by determining whether the key is equal to its own authentication key. The media receiver 220 authorized to connect may secure a network channel that can communicate with the daemon through a media sharing protocol.

After the media receiver 220 is connected to the media controller 230, the communication management module 223 may parse a media service message, which is a message related to a media service transmitted from the media service daemon 240. The communication management module 223 may deliver the parsed media service message to the HTML5 media player 221. Here, the media service message may include at least one of server information, receiver information, playback information, media information, a play command (or a play request), and a stop command (or a stop request), and may be called a media sharing message.

The communication management module 223 may include a web socket 224 and a protocol parser 225. The websocket 224 controls connection and data transmission and reception of the media service daemon 240. The protocol parser 225 parses the media service message and delivers the parsed media service message to the HTML5 media player 221.

The HTML5 media play 221 may play the media stream 201 based on the media service message parsed by the communication management module 223.

The media controller 230 searches for a user interface screen 231 for displaying a GUI, a controller 233 for detecting a user request for controlling the media controller 230, and a media receiver. The receiver may include a receiver picker 235 and a media service daemon 240 for transmitting a media service message to the media service daemon 240 or the media receiver 220.

The media service daemon 240 may communicate with the media controller to convert the existing media sharing protocol into a web-based protocol and communicate with the web-based media receiver 220 based on the converted protocol. The media service daemon 240 may include at least one of a communication management module 241 and a service discovery module 245. The media service daemon 240 may communicate with a media controller or another media controller that executes the media service daemon 240 to provide a media service. In addition, the media service daemon 240 may communicate with a plurality of media controllers to provide a media service.

The service discovery module 245 may perform service discovery. The service discovery module 245 may send a discovery message to the receiver picker 235 so that the receiver picker 235 can find a media receiver that can communicate with it. The service discovery module 245 may open and wait for a specific port so that the media receiver 220 can find the media service daemon 240.

The service discovery module 245 may perform paying between the media receiver 220 and the media controller 230 in response to the connection request of the media receiver 220. The service discovery module 245 may perform authentication based on the authentication key transmitted from the media receiver 220. The service discovery module 245 checks whether the authentication key input by the user and the authentication key transmitted by the media receiver 220 are the same, and processes the media receiver 220 as authenticated in the same case.

The service discovery module 245 may store information on the media receiver once authenticated in the media receiver list, and omit the authentication process at the next pairing of the media receiver stored in the media receiver list.

The communication management module 241 converts the actual media sharing protocol into a web-based protocol after the connection between the media controller 230, the media service daemon 240, and the media receiver 220 is completed, and converts the converted protocol. Send data based on this. The communication management module 241 may include an HTTP server 243 and a protocol parser 244.

The protocol parser 244 may receive a specific message coded according to an existing media sharing protocol from the controller module 233 and parse the received message. The protocol parser 244 converts the parsed message into a protocol that the media receiver 220 can decrypt. For example, the protocol parser 244 may convert the parsed message into a web-based protocol.

The HTTP server 243 transmits the message converted by the protocol parser 244 based on HTTP to the media receiver 220.

3 is a block diagram showing the structure of a preferred embodiment of a media service daemon (Media Service Daemon).

Referring to FIG. 3, the media service daemon 240 may be implemented in a plug-in manner. Accordingly, the media control device 30 of the present invention can process various media sharing protocols. In addition, since the media receiver 220 may be used in the same manner separately from the media controller 230 stage protocol, the media receiver 220 may process media services provided through various media sharing protocols.

In the media service core 310 of the media service daemon 240, a module capable of communicating with a web-based media receiver may exist. In some embodiments, the media service core 310 may include a web socket server 312 for pairing and communication with the media receiver 220 and a message generator module 314 for generating a web-based media sharing protocol. It may include.

Modules that communicate with existing media sharing protocols within the media service daemon 240 are plugged in. Accordingly, the media service daemon 240 may have high determinism.

In some embodiments, the media service daemon 240 uses the service discovery plug-in 320 that supports the corresponding discovery service (mDNS, SSDP) and the media service discovered after the media service (AirPlay, DLNA) discovery. It may include a communication management plug-in 330 that supports it.

4 is a flowchart illustrating a process of performing a preferred embodiment of a service discovery method according to the present invention.

Referring to FIG. 4, the websocket-based service discovery 229 performs a websocket search (S100). In some embodiments, the websocket-based service discovery 229 may sequentially access an IP address in its own subnet to find a media service daemon at the media controller side. In addition, the websocket-based service discovery 229 may sequentially send discovery messages to daemon ports of IP addresses in the subnet using unicast. The transmitted search message may include at least one of a service name and a device name.

The media service daemon 240 transmits a response message to the search message transmitted by the websocket-based service discovery 229 (S110). The media service daemon 240 may generate a user datagram protocol (UDP) discovery message to register the websocket-based service discovery 229 that transmitted the search message to the media receiver list.

When receiving a response message from the media service daemon 240, the websocket-based service discoverer 229 may add the IP address that transmitted the response message to the media controller list. In addition, the websocket-based service discovery 229 may automatically pair to a media controller having an IP address in the media controller list, and display the media controller list on a screen to allow a user to select a media controller to pair with.

The receiver picker 235 performs a service search based on UDP multicast (User Datagram Protocol Multicast) (S120). The UDP multicast based service discovery may be a simple service discovery protocol (SSDP) and a multicast DNS (mDNS).

The media service daemon 240 transmits a UDP-based response to the receiver picker 235 in response to the search of step S120 (S130).

5 is a flowchart illustrating a process of performing another preferred embodiment of the service discovery method according to the present invention.

Referring to FIG. 5, the websocket-based service discovery 229 performs a websocket search (S200). In some embodiments, the websocket-based service discovery 229 may sequentially access an IP address in its own subnet to find a media service daemon at the media controller side. In addition, the websocket-based service discovery 229 may sequentially send discovery messages to daemon ports of IP addresses in the subnet using unicast. The transmitted search message may include at least one of a service name and a device name.

The media service daemon 240 transmits a response message to the search message transmitted by the websocket-based service discovery 229 (S210). The media service daemon 240 may generate a user datagram protocol (UDP) discovery message to register the websocket-based service discovery 229 that transmitted the search message to the media receiver list.

When receiving a response message from the media service daemon 240, the websocket-based service discoverer 229 may add the IP address that transmitted the response message to the media controller list. In addition, the websocket-based service discovery 229 may automatically pair to a media controller having an IP address in the media controller list, and display the media controller list on a screen to allow a user to select a media controller to pair with.

The media service daemon 240 performs a UDP multicast based service search (S220). The UDP multicast based service discovery may be a simple service discovery protocol (SSDP) and a multicast DNS (mDNS).

The receiver picker 235 transmits a UDP-based response to the media service daemon 240 in response to the search of step S220 (S230).

6 is a flowchart illustrating a process of performing a preferred embodiment of the method for controlling media sharing according to the present invention.

Referring to FIG. 6, the controller 233 and the media service daemon 240 transmit and receive data or information based on a media sharing protocol. Here, the media sharing protocol may be a commercial media sharing protocol such as airplay or DLNA.

The media service daemon 240 requests server information (Server-infor) from the websocket-based service discovery 229 (S300).

The websocket-based service discovery 229 responds to the server information request of the media service daemon 240 (S310). Here, the websocket-based service discovery 229 may transmit information on the media that can be supported by the response to the media service daemon 240.

The media service daemon 240 requests the websocket-based service discovery 229 to play the media (S320). Here, the media service daemon 240 may transmit information about media to be played. The information may be a Uniform Resource Locator (URL) of the media to be played.

The websocket-based service discovery 229 responds to the play request (S330). Here, the websocket-based service discovery 229 may transmit, to the media service daemon 240, information indicating that it can be played back or not.

The websocket-based service discovery 229 transmits the playback information (Playback-info) to the media service daemon 240 (S340). The transmitted playback information may include information about a current playback time and a playback state.

The media service daemon 240 transmits a playback command to the websocket-based service discovery 229 (S350). The transmitted playback command may include at least one of pause, resume, and seek. When the websocket-based service discovery 229 receives the playback command, the websocket-based service discovery 229 performs the received playback command.

The transmitted playback command may be input from a user. That is, the controller 233 may detect a playback command input from the user and transmit the detected playback command to the media service daemon 240 according to the media sharing protocol 610. The media service daemon 240 may receive the playback command transmitted according to the media sharing protocol and parse the received playback command. The media service daemon 240 may transmit the parsed playback command to the web-based protocol.

The media service daemon 240 transmits a stop command to the websocket-based service discovery 229 (S360).

WebSocket-based service discovery 229 responds to the stop command (S370). WebSocket-based service discovery 229 also stops playing the media in response to the stop command.

7 is a flowchart illustrating a process of performing a preferred embodiment of the media sharing method according to the present invention.

Referring to FIG. 7, the media service daemon 240 is turned on (S400). As described above in FIG. 3, a module that communicates with a media sharing protocol, such as Airplay or DLNA, may be added to the media service daemon 240 as a plug-in. The media service daemon 240 may open a daemon port of the media controller 230.

WebSocket-based service discovery 229 performs a WebSocket Search (S402). In some embodiments, the websocket-based service discovery 229 may sequentially access an IP address in its own subnet to find a media service daemon at the media controller side. In addition, the websocket-based service discovery 229 may send search messages sequentially to daemon ports of IP addresses in the subnet using unicast. The transmitted search message may include at least one of a service name and a device name.

The media service daemon 240 transmits a response message to the search message transmitted by the websocket-based service discovery 229 (S404).

The websocket-based service discovery 229 transmits receiver information (Receiver Infor) to the media service daemon 240 (S406). The receiver information may include a service name and a device name. In some embodiments, "WebBasedMediaSharing" indicating a web-based media sharing service as a service name and "LGSmartTVXX" which is a device name of an electronic device performing a function of a media receiver as a device name may be transmitted.

In addition, when receiving a response message from the media service daemon 240, the websocket-based service discovery 229 may add the IP address that transmitted the response message to the media controller list. The websocket-based service discovery 229 may automatically pair to a media controller having an IP address in the media controller list, and display a list of media controllers on a screen to allow a user to select a media controller to pair with.

The media service daemon 240 transmits a response to the reception of the receiver information to the web socket-based service discovery 229 (S408).

The media service daemon 240 transmits a UDP multicast service advertisement to the receiver picker 235 (S410). The UDP multicast service advertisement may include at least one of a service name (ServiceName), an address (Address) and a device name (DeviceName). The service name may be a name of a media sharing protocol such as Airplay and DLNA, an address may be a local address, and the device name may be a device name included in the receiver information transmitted in step S406. The transmission of the UDP multicast service advertisement may be selectively performed according to the discovery protocol used and the execution time of the receiver picker 235.

The receiver picker 235 performs a service search based on UDP multicast (User Datagram Protocol Multicast) (S412). The UDP multicast based service discovery may be a simple service discovery protocol (SSDP) and a multicast DNS (mDNS). The receiver picker 235 checks whether there is a media sharing service, such as an AirPlay service or a DLNA service, through a UDP Multicast (User Datagram Protocol Multicast) based service search. Step S412 may be selectively executed according to the discovery protocol used and the execution time of the receiver picker 235.

The media service daemon 240 transmits a UDP-based response to the receiver picker 235 in response to the search in step S412 (S414). At least one of a service name, an address, and a device name may be transmitted in a UDP-based response. The service name may be a name of a media sharing protocol such as Airplay and DLNA, an address may be a local address, and the device name may be a device name included in the receiver information transmitted in step S404. Step S414 may be selectively executed according to the discovery protocol used and the execution time of the receiver picker 235.

The receiver picker 235 transmits a media playback request message requesting playback of media to the media service daemon 240 (S416). In this case, the media play request message may include information indicating a media to be played and a start time. The information indicating the media to be played may be a URL indicating the location of the media.

The media service daemon 240 requests server information (Server-infor) from the websocket-based service discovery 229 (S418).

The websocket-based service discovery 229 performs a response to the server information request of the media service daemon 240 (S420). Here, the websocket-based service discovery 229 may transmit information on the media that can be supported by the response to the media service daemon 240.

The media service daemon 240 requests play of media (S422). Here, the media service daemon 240 may transmit information about the media to be played and a start time. The information on the media to be played may be a Uniform Resource Locator (URL) of the media to be played. In addition, the information transmitted in step S422 may be the information transmitted in step S416, the media service daemon 240 changes the protocol of the information transmitted in step S416 to a web-based protocol to be transmitted to the websocket-based service discovery 229. Can be.

The websocket-based service discovery 229 transmits a response to the play request to the media service daemon 240 (S424).

When the media service daemon 240 receives the response transmitted in step S424, the media service daemon 240 transmits a response to the play request transmitted in step S416 to the receiver picker 235 (S426).

The websocket-based service discovery 229 requests media to be played (S428). The websocket based service discovery 229 may request media from the receiver picker 235 and may request the media sender 210 directly. Here, the websocket-based service discovery 229 may request media by using the media URL transmitted in step S422.

The websocket-based service discovery 229 receives media to be played (S430). The websocket-based service discovery 229 may receive media to play through the receiver picker 235. In addition, the websocket-based service discovery 229 may receive media directly from the media sender 210. The websocket-based service discovery 229 may receive the media to be played from the location indicated by the media URL transmitted in step S422.

The websocket-based service discovery 229 transmits the playback information (Playback-info) to the media service daemon 240 (S432). The transmitted playback information may include information about a current playback time and a playback state.

The media service daemon 240 transmits the playback information (Playback-info) transmitted in step S432 to the receiver picker 235 (S434). The playback information may be converted to a media sharing protocol currently used and transmitted to the receiver picker 235.

The receiver picker 235 transmits a playback command to the websocket-based service discovery 229 (S436). The transmitted playback command may include at least one of pause, resume, and seek. The transmitted playback command may be input from a user. That is, when the controller 233 detects a playback command input from the user, and outputs the detected playback command to the receiver picker 235, the receiver picker 235 is a media service daemon (according to the media sharing protocol currently used). 240).

The media service daemon 240 transmits a playback command to the websocket-based service discovery 229 (S438). The transmitted playback command may include at least one of pause, resume, and seek. The media service daemon 240 may change the playback command transmitted according to the media sharing protocol into a web-based protocol and transmit it to the websocket-based service discovery 229. The websocket-based service discovery 229 performs a playback command received from the media service daemon 240.

The receiver picker 235 transmits a stop command to the media service daemon 240 (S440). The stop command may be sent according to the media sharing protocol currently used.

The media service daemon 240 transmits the stop command transmitted in step S440 to the websocket-based service discovery 229 (S442). The media service daemon 240 may change the suspend command to a web-based protocol and transmit it to the websocket-based service discovery 229.

The websocket-based service discovery 229 transmits a response to the stop command to the media service daemon 240 (S444). Also, the websocket based service discovery 229 stops playing the media according to the stop command.

When the media service daemon 240 receives the response transmitted in step S444, the media service daemon 240 transmits a response to the stop command transmitted in step S440 to the receiver picker 235 (S446).

In some embodiments, operations S420, S424, S428, S432, and S444 may be performed by the communication management module 223, and the data, information, or message transmitted in steps S418, S422, S430, S438, and S442 may be performed by the communication management module. 223 may receive.

8 illustrates one embodiment of a graphical user interface for an authentication procedure.

Referring to FIG. 8, the screen 810 is a screen for executing the media service daemon 240 in the media sharing control device 30. The screen 810 includes an execution button 812 and a setting button 184. The user may execute the media service daemon 240 by performing a user action of touching the execution button 812. In addition, the user may perform a user action of touching the setting button 184 so that the GUI for setting the media service daemon is displayed.

The screen 810 displays an authentication key 816 for pairing with the media player 20. The authentication key 816 may be input from a user, and may be automatically generated by the media sharing control device 30. When the authentication key 816 is input to the media player 20 during initial pairing, the media player 20 stores the input authentication key 816, and when pairing, the playback device 20 stores the stored authentication. The key 816 can be automatically paired. The certified media players are managed as a media receiver list through the media service daemon 240, and then the media players in the media receiver list can be automatically paired.

The screen 830 is a screen on which the media service daemon 240 is executed in the media sharing controller 30. The user may stop the execution of the media service daemon 240 by performing a user action of touching the execution button 812 '. In some embodiments, media service daemon 240 may run in the background.

9 illustrates one embodiment of a graphical user interface for media service daemon configuration.

Referring to FIG. 9, the screen 900 displays a GUI for setting a media service daemon. The GUI 900 includes a name setting area 910, a daemon sharing setting area 920, an inter-daemon communication setting area 930, an automatic off time setting area 940, and a plug-in setting area 950.

The name setting area 910 is for setting a media service daemon name to be displayed on the media player 20. The user may set the media service daemon name (Phone XX) and change the set name (Phone XX) in the name setting area 910.

The daemon sharing setting area 920 is configured to support a plurality of media controllers executed in other media sharing controllers as one media service daemon. If daemon sharing is checked, the media service daemon of the media sharing controller 30 may provide the functions of the media service daemon to other media sharing controllers. That is, the other media sharing controller may control the media player 20 to play the media stream transmitted by the media server 10 using the media service daemon of the media sharing controller 30. In the following, this situation is referred to as daemon sharing situation.

The inter-daemon communication setting area 930 is for setting a specific media service daemon to communicate with the media playback device 20 as a representative when the media sharing daemon is performed for each media playback device instead of sharing a daemon. will be. When inter-daemon communication is checked, since one media service daemon communicates with the media player 20, delays due to discovery and pairing may be minimized. In some embodiments, the representative media service daemon may be determined as a media service daemon installed in the media sharing controller having the smallest IP address or a media service daemon set in the media sharing controller having the largest IP address.

The auto off time setting area 940 is for setting an auto off time to prevent a user from accidentally running the media service daemon without executing the media service. For example, if the automatic off time is set to 60 seconds, the media service daemon may be automatically terminated when there is no request for media service for 60 seconds, and the media service daemon may be reinitialized when there is a request for media service for 60 seconds.

The plug-in setting area 950 is for displaying a supported plug-in and allowing a user to select the displayed plug-in. The plug-in may include at least one of a service discovery plug-in supporting media service retrieval, and a communication management plug-in supporting reception and parsing of media sharing data. For example, the service discovery plug-in may be mDNS, SSDP, or the like, and the communication management plug-in may be airplay, DLNA, or the like.

Only the plug-in selected in the plug-in setting area 950 may be activated, and the remaining plug-ins may be deactivated.

10 is a diagram illustrating an embodiment of a graphical user interface for connecting a media service daemon.

Referring to FIG. 10, screen 1010 displays a GUI for connecting a media service daemon. The screen 1010 may be a screen displayed on the media player 20.

The GUI 1010 may include a daemon list 1011, a connection button 1021, a rescan button 1023, and a setting button 1024.

The daemon list 1011 displays a list of connectable media service daemons. The daemon list 1011 may list media service daemons included in the media controller list. The user may select the corresponding media service daemon by checking the check boxes 1012, 1013, and 1014. For example, the user may select check box 1012 to select a media service daemon named Phone_xx and check box 1013 to select a media service daemon named Endroid_xx.

If a user action of selecting the connect button 1021 is detected, pairing with the media service daemon selected in the daemon list 1011 is performed.

In the case of initial pairing with the selected media service daemon, a GUI for inputting an authentication key may be displayed. The GUI 1030 may be displayed by the GUI. The user may input an authentication key into the input area 1031 of the GUI 1030. The media player 20 may perform an authentication procedure with the media service daemon using the input authentication key.

When pairing with the selected media service daemon is completed, a GUI indicating that media service can be performed may be displayed. The GUI 1040 may be displayed by the GUI. The GUI 1040 displays Phone_xx and Endroid_xx, which are names of the connected media service daemon.

If a user action of selecting the rescan button 1023 is detected, a media service daemon search is performed. Here, the websocket-based service discovery 229 of FIG. 2 may perform a media service daemon search in the manner described above in FIG. 2. If the user does not have a media service daemon searched for in the daemon list 1011, the user may perform a user action of selecting the rescan button 1023 so that the media service daemon rescan is performed. As a result of the re-search, the found media service daemon may be included in the media controller list.

If a user action of selecting the setting button 1024 is detected, a GUI for detailed setting of the media receiver is displayed.

FIG. 11 illustrates an embodiment of a graphical user interface for detailed setup of a media receiver.

Referring to FIG. 11, the GUI 1100 is for detailed setting of a media receiver. The GUI 1100 may include an automatic connection setting area 1110, a simultaneous connection device setting area 1120, and a basic connection device setting area 1130.

The automatic connection setting area 1110 is configured to automatically attempt to pair with the media service daemon when only one media service daemon is searched or a media service daemon registered in the basic access device is found. When the automatic connection setting area 1110 is checked, the media player 20 may automatically perform pairing with the media service daemon without displaying a GUI for connecting the media service daemon.

The simultaneous access device setting area 1120 is for setting the number of media service daemons that can be simultaneously connected. For example, when 3 is set in the simultaneous connection device setting area 1120, the connection with three media service daemons is possible.

The default connected device setting area 1130 is for registering the media service daemon as a default connected device. The list 1131 lists the searched media service daemons, and the list 1135 lists the media service daemons registered as basic access devices. In FIG. 11, it can be seen that Phone_xx is registered as a basic access device.

12 is a diagram illustrating an embodiment of a screen on which a media service is executed on a media sharing control device and a media playback device.

Referring to FIG. 12, a media service daemon 240 may be installed in the electronic device 1210. When the installed media service daemon 240 is executed, the electronic device 1210 may perform a function of the media sharing control device 30. The user may execute the media service daemon installed in the electronic device 1210 through the GUI 810 illustrated in FIG. 8, and set the media service daemon installed through the GUI 900 illustrated in FIG. 9.

The media receiver web app may be installed on the electronic device 1250. Here, the media receiver web app may include at least one of the HTML5 media player module 221, the communication management module 223, and the websocket-based service discovery module 229 illustrated in FIG. 2. When the installed media receiver web app is executed, the electronic device 1250 may perform a function of the media player 20.

The media service daemon of the media sharing controller 1210 and the websocket based service discovery of the media player 1250 perform pairing between the media sharing controller 1210 and the media player 1250 in the manner described above in FIG. 2. do.

When the pairing is completed, a user may use a media service provided by the media sharing control device 1210 and the media player 1250 through an existing GUI or UX (User eXperience) for media service of the media sharing control device 120. Can be.

For example, if the electronic device 1210 is an iOS mobile device, the electronic device 1250 is LG's LG Smart TV, and the protocol for providing media services is AirPlay, then the user is an iOS mobile device. And a GUI or UX such as the GUI or UX provided by Apple's Apple TV.

When the user opens the content 1211 on the iOS mobile device 1210 and clicks the airplay icon, the screen 1210 is displayed. On the screen 1210, a window 1220 displaying a content 1211 and a list of equipment that can be used as a media player is displayed. When the user selects the LG Smart TV 1222 in the window 1220, the same content 1251 as the content 1211 is displayed on the LG Smart TV 1250.

FIG. 13 is a flowchart illustrating another preferred embodiment of a media sharing method according to the present invention.

Referring to FIG. 13, the media sharing control device 30 executes a media service daemon app (S500). The media sharing control device 30 may display the screen 810 illustrated in FIG. 8 as an execution screen of the media service daemon app.

The media sharing controller 30 sets up a media service daemon (S502). The media sharing controller 30 may set the media service daemon according to the items set in the GUI 900 illustrated in FIG. 9.

The media sharing control device 30 executes the media service daemon (S504). When the media sharing controller 30 detects a user action of selecting the execution button 812 included in the GUI 810 illustrated in FIG. 8, the media sharing controller 30 may execute a media service daemon web app in response to the user action detection. have.

The media player 20 executes a media receiver app (S506). The media player 20 may display the screen 1010 illustrated in FIG. 10 as an execution screen of the media receiver app.

The media player 20 discovers a media service daemon (S508). WebSocket-based service discovery 229 shown in FIG. 2 may perform a media service daemon search in the manner described above in FIG. The list of found media service daemons may be displayed on the screen 1010. Also, the discovered media service daemon may be included in the media controller list.

The media player 20 sets a media receiver (S510). The media player 20 may set a media receiver according to the items set in the GUI 1100 illustrated in FIG. 11.

The media player 20 selects a media service daemon (S512). The media player 20 may automatically select the media service daemon from among the media service daemons listed on the screen 1010 of FIG. 10 according to a user input.

The media player 20 requests a connection to the selected media service daemon (S514).

The media sharing control device 30 determines whether authentication is necessary (S516). The media sharing control device 30 may determine whether authentication is required by checking the media receiver list. If the media receiver executed in the media playback apparatus 20 requesting the connection is listed in the media receiver list, the media sharing control apparatus 30 may skip the authentication procedure and proceed to step S526.

If authentication is required, the media sharing control device 30 requests the media playback device 20 to transmit an authentication key (S518).

The media player 20 requests a user to input an authentication key (S520). Here, the media player 20 may display the GUI 1030 illustrated in FIG. 10, and receive an authentication key through the displayed GUI 1030.

The media player 20 transmits the authentication key to the media sharing controller 30 (S522). Herein, the transmitted authentication key may be an authentication key input in step S520 or a previously stored authentication key.

The media sharing controller 30 verifies the authentication key and registers the authenticated media receiver (S524). The media sharing controller 30 checks whether the authentication key transmitted in step S522 is the same as the authentication key set in step S522, and processes the media receiver as authenticated in the same case. The set authentication key may be an authentication key 816 displayed on the screen 810 of FIG. 8. The media sharing control device 30 may include the authenticated media receiver in the media receiver list.

The media sharing controller 30 transmits a message informing of the connection confirmation to the media player 20 (S526).

The media player 20 checks the connection result based on the message transmitted in step S526, and waits for media sharing (S528). In operation S528, the media player 20 may display the GUI 1040 illustrated in FIG. 10.

The media sharing control device 30 requests the media player 20 for the supported media type information of the media receiver (S530).

In response to the request for the support media type information of the media receiver, the media player 20 transmits the support media type information of the executed media receiver to the media sharing controller 30 (S532). The media player 20 waits for streaming playback. The media player 20 may display the GUI 1040 illustrated in FIG. 10 or the screen 1450 illustrated in FIG. 14 as a standby screen.

The media sharing controller 30 executes the media service daemon in the background (S534).

The media sharing control device 30 executes a media sharing service (S536). The media sharing service can be executed on user request or automatically. In some embodiments, in operation S536, the media sharing control device 30 may display the screen 1210 illustrated in FIG. 12 or the screen 1410 illustrated in FIG. 14.

The media sharing control device 30 selects a media receiver for sharing media (S538). Here, the media sharing control device 30 may select the media receiver automatically or according to user selection.

The media sharing controller 30 transmits a playback command to the media receiver selected in step S538 (S540). Here, the transmitted playback command may be transmitted according to the web-based protocol. The play command may include information indicating a media to play and a start time. The information on the media to be played may be a URL of media to be played.

The media player 20 plays the media commanded to play (S542). In this case, the played media may be a media stream transmitted by the media server 10. In some embodiments, the media player 20 may display the same content 1460 as the content 1410 displayed by the media sharing control device 30. In this case, the media server 10 may be a module executed in the media sharing controller.

The media player 20 transmits the playback information to the media sharing controller 30 (S544). The reproduction information may be transmitted periodically. Also, the playback information may be the same as the playback information described above with reference to FIG. 6 or 7.

The media sharing controller 30 transmits a playback command to the media player 20 (S546). Here, the transmitted playback command may be the same as the playback command described above with reference to FIG. 6 or 7.

The media sharing control device 30 transmits a stop command to the media player 20 (S548). Here, the transmitted stop command may be the same as the stop command described above with reference to FIG. 6 or 7.

When the stop command is received, the media player 20 stops playing the media. In addition, the media player 20 may display a standby screen. The standby screen may be the GUI 1040 shown in FIG. 10 or the screen 1450 shown in FIG. 14.

15 is a block diagram illustrating a configuration of a preferred embodiment of an electronic device according to the present invention.

Referring to FIG. 15, the electronic device 1500 may include a control unit 1510, a network interface unit 1520, a user interface unit 1530, an output unit 1540, an A / V input unit 1550, and a sensing unit 1560. The mobile communication unit 1570 and the location information unit 1580 are included. However, in connection with the present invention, the components shown in FIG. 20 are not essential, and the electronic device 1500 may not include some of the illustrated components or may be implemented in a form in which additional components are further included.

Hereinafter, each component of the electronic device 1500 will be described in detail.

The network interface unit 1520 accesses the media server 10 that stores the media data, and searches for the media player 20 or the media sharing controller 30 capable of playing the media data. The network interface unit 1520 may perform the same function as the wireless Internet unit 1522 and the short-range communication unit 1524.

The wireless internet unit 1522 refers to a module for wireless internet access, and may be embedded or external to the electronic device 1500. Wireless Internet technologies include Wireless LAN (Wi-Fi), Wireless Broadband (Wibro), World Interoperability for Microwave Access (Wimax), High Speed Downlink Packet Access (HSDPA), GSM, CDMA, WCDMA, Long Term Evolution), but is not limited to such.

In view of the fact that the wireless Internet access by Wibro, HSDPA, GSM, CDMA, WCDMA, LTE, etc. is made through the mobile communication network, the wireless Internet unit 1522 performing the wireless Internet access through the mobile communication network is the mobile communication unit 1570. It may be understood as a kind.

The short range communication unit 1524 refers to a module for short range communication. As a short range communication technology, Bluetooth, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee, and the like may be used.

The output unit 1540 is used to generate an output related to visual, auditory, or tactile senses. The output unit 1540 is configured to display the display unit 1542, the audio output unit 1544, the alarm unit 1546, and the haptic unit 1548. Include.

The display unit 1542 displays information processed by the electronic device 1500. For example, when the electronic device 1500 wants to play media data by controlling the media server 10 and the media player 20, the display unit 1542 may use a user interface (UI) or a graphical user (GUI) for this purpose. Interface). That is, the display unit 1542 may display a first GUI object that enables the user to select media data and a second GUI object that enables the user to select the found media player.

The display unit 1542 may be configured with a display panel such as a liquid crystal display (LCD) and an organic light-emitting diode (OLED), and a display device for providing a stereoscopic image as needed. It may be configured as.

There may be two or more display units 1542 according to the implementation form of the electronic device 1500. For example, the plurality of display units 1542 may be spaced apart from or integrally disposed on one surface of the electronic device 1500, or may be disposed on different surfaces.

The sound output unit 1544 may output audio data received from the network interface unit 1520 or stored in the memory 1592. The sound output unit 1544 may also output a sound signal related to a function performed by the electronic device 1500. The sound output unit 1544 may include a receiver, a speaker, a buzzer, and the like.

The alarm unit 1546 outputs a signal for notifying occurrence of an event of the electronic device 1500. Examples of events occurring in the electronic device 1500 include signal reception, message reception, key signal input, and touch input. The alarm unit 1546 may output a signal for notifying occurrence of an event in a form other than a video signal or an audio signal, for example, vibration. Since the video signal or the audio signal may also be output through the display unit 1542 or the audio output module 1552, in this case, the display unit 1542 and the audio output module 1552 may be classified as a kind of the alarm unit 1546. .

The haptic module 1548 generates various haptic effects that a user can feel. Vibration is a representative example of the haptic effect generated by the haptic unit 1548. The intensity and pattern of vibration generated by the haptic part 1548 can be controlled. For example, different vibrations may be synthesized and output or may be sequentially output.

The user interface 1530 generates input data for the user to control the operation of the terminal. For example, the user interface unit 1530 receives a first command of a user to select media data through a first GUI object, and receives a second command of a user to select a media player through a second GUI object. can do.

The user interface unit 1530 may be configured as a touch screen having a layer structure with the display unit 1542 by including a sensor for detecting a touch operation (hereinafter, referred to as a “touch sensor”). That is, the user interface unit 1530 may be integrally formed with the display unit 1542. The touch sensor may have, for example, a form of a touch film, a touch sheet, a touch pad, or the like.

In this case, the user interface 1530 may receive a first command and a second command through a user's touch gesture. In particular, the second command is received by a user's touch gesture of receiving a first command by a user's touch gesture of long pressing the first GUI object and dragging and dropping the first GUI object to the second GUI object. Can be received.

The touch sensor may be configured to convert a change in pressure applied to a specific portion of the display portion 1542 or capacitance generated at a specific portion of the display portion 1542 into an electrical input signal. The touch sensor may be configured to detect not only the position and area of the touch but also the pressure at the touch.

If there is a touch input to the touch sensor, the corresponding signal (s) is sent to a touch controller (not shown). The touch controller processes the signal (s) and then transmits the corresponding data to the controller 1510. As a result, the controller 1510 may determine which area of the display unit 1542 is touched.

The user interface unit 1530 may further include a key pad, a dome switch, a touch pad (static pressure / capacitance), a jog wheel, a jog switch, and the like.

The controller 1510 controls the overall operation of the electronic device 1500. The controller 1510 may play the media server 10 through the network interface 1520 to play the media data in the media playback apparatus 20 according to the first and second commands of the user received from the user interface 1530. And the media player 20.

The controller 1510 may perform a process of recognizing a user's touch gesture performed by the user interface unit 1530 configured as a touch screen. In addition, the controller 1510 may include a multimedia module 1512 for multimedia playback. The multimedia module 1512 may be implemented in the controller 1510 or may be implemented separately from the controller 1510.

As described above, when the user selects the electronic device 1500 as the media player 20, the media data is received from the media server 10 through the network interface unit 1520, and the multimedia module 1512 is transmitted to the multimedia module 1512. As a result, the media data may be reproduced and the media data reproduced through the display unit 1542 and the sound output unit may be output.

 The A / V input unit 1550 is for inputting an audio signal or a video signal, and the A / V input unit 1550 includes a camera 1552 and a microphone 1554. The camera 1552 processes image frames such as still images or moving images obtained by the image sensor in a video call mode or a photographing mode. The processed image frame can be displayed on the display portion 1542.

The image frame processed by the camera 1552 may be stored in the memory 1592 or transmitted to the outside through a network interface unit. Two or more cameras 1552 may be provided according to a usage environment. In addition, the camera 1552 may capture an image for recognition of the media playback apparatus and provide it to the controller 1510.

The microphone 1554 receives an external sound signal by a microphone and processes the external sound signal into electrical voice data. The processed voice data may be converted into a form transmittable to the mobile communication base station through the mobile communication unit 1570 and output in the call mode. The microphone 1554 may implement various noise removing algorithms for removing noise generated in the process of receiving an external sound signal.

The mobile communication unit 1570 may include at least one of a base station, an external terminal, and a server on a mobile communication network such as, but not limited to, Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA), and Wideband CDMA (WCDMA). Send and receive wireless signals. The wireless signal may include various types of data according to transmission and reception of a voice call signal, a video call call signal, or a text / multimedia message.

The location information unit 1580 is a module for obtaining a location of the electronic device 1500. The GPS (Global Position System) module may be used as the location information unit 1580. The GPS module calculates distance information and accurate time information away from three or more satellites, and then applies triangulation to the calculated information, thereby accurately calculating three-dimensional current position information according to latitude, longitude, and altitude. In this case, a method of calculating position and time information using three satellites and correcting an error of the position and time information calculated using another satellite may be used. In addition, the GPS module may calculate speed information by continuously calculating the current position in real time.

The sensing unit 1560 includes an electronic device 1500 such as an open / closed state of the electronic device 1500, a position of the electronic device 1500, a presence or absence of a user contact, an orientation of the electronic device 1500, an acceleration / deceleration of the electronic device 1500, and the like. Sensing a current state to generate a sensing signal for controlling the operation of the electronic device 1500. The sensing unit 1560 may include a gyroscope sensor, an acceleration sensor, a geomagnetic sensor, or the like.

The sensing unit 1560 may recognize a relative position of the electronic device 1500 with respect to the media player, and output the same to the controller 1510, and the controller 1510 may use the second GUI object representing the media player ( 14 can be displayed on the display portion 1542. In addition, the sensing unit 1560 may sense whether the power supply unit 1590 is supplied with power, whether the terminal interface unit 1570 is coupled to an external device, and the like. Meanwhile, the sensing unit 1560 may further include a proximity sensor 1562.

 The proximity sensor 1562 may be disposed near the touch screen or an inner area of the electronic device 1500 that is surrounded by the touch screen. The proximity sensor refers to a sensor that detects the presence or absence of an object approaching a predetermined detection surface or an object present in the vicinity without using a mechanical contact by using an electromagnetic force or infrared rays. Proximity sensors have a longer life and higher utilization than touch sensors.

Examples of the proximity sensor 1562 include a transmission photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillation proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor, an infrared proximity sensor, and the like. When the touch screen is capacitive, the touch screen is configured to detect the proximity of the pointer by the change of the electric field according to the proximity of the pointer. In this case, the touch screen (touch sensor) may be classified as a proximity sensor.

The proximity sensor 1562 detects a proximity touch and a proximity touch pattern (eg, a proximity touch distance, a proximity touch direction, a proximity touch speed, a proximity touch time, a proximity touch position, and a proximity touch movement state). Information corresponding to the sensed proximity touch operation and the proximity touch pattern may be output on the touch screen.

The memory 1592 may store a program for processing and controlling the controller 1510 and may perform a function for temporarily storing input / output data (for example, audio, still image, video, etc.). It may be. The memory 1592 may store a frequency of use of each of the data (eg, a frequency of use of each multimedia data). In addition, the memory 1592 may store information indicating a frequency of use of the media player, and the controller 1510 may control the display unit 1542 to display the second GUI object based on the preference. have.

In addition, the memory 1592 may store data about various patterns of vibration and sound output when a touch input on the touch screen is performed.

In addition, the memory 1592 may store a media controller list, a media receiver list, or an authentication key.

The memory 1592 may be a flash memory 1592 type, a hard disk type, a multimedia card micro type, a card type memory 1592 (e.g. SD or XD memory (1592), etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPEPROM), programmable read -Only Memory, a magnetic memory 1592, a magnetic disk, and an optical disk may include at least one type of storage medium. The electronic device 1500 may operate in association with a web storage that performs a storage function of the memory 1592 on the Internet.

 The power supply unit 1590 receives external power and internal power under the control of the controller 1510 to supply power for operation of each component.

Various embodiments described herein may be implemented in a recording medium readable by a computer or similar device using, for example, software, hardware or a combination thereof.

According to a hardware implementation, the embodiments described herein include application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), and the like. It may be implemented using at least one of processors, controllers, micro-controllers, microprocessors, and electrical units for performing other functions.

In some cases, the embodiments described herein may be implemented by the controller 1510 itself.

According to the software implementation, embodiments such as the procedures and functions described herein may be implemented as separate software modules. Each of the software modules may perform one or more functions and operations described herein.

Software code may be implemented in software applications written in a suitable programming language. The software code may be stored in the memory 1592 and executed by the controller 1510. For example, the streaming server 213, the media service daemon 240, the HTML5 media player 221, the communication management module 223, and the websocket-based service discovery 229 illustrated in FIG. 2 may be provided to the controller 1510. Can be executed by

16 is a block diagram showing the configuration of a preferred embodiment of a media sharing application providing server according to the present invention.

Referring to FIG. 16, the media sharing application providing server 200 may include a communication unit 1610, a controller 1620, and a storage 1630.

The communication unit 1610 receives the packets transmitted through the network 1, and transmits the packets to the media server 10, the media playback device 20, and the media sharing control device 30 through the network 2. Can transmit The packet may be transmitted in Session Initiation Protocol (SIP), User Datagram Protocol (UDP), and Transport Control Protocol (TCP).

The controller 1620 may control packet transmission of the communication unit 1610. The control unit 1620 includes a Session Initiation Protocol (SIP), Simple Mail Transfer Protocol (SMTP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Real-Time Streaming Protocol (RTSP), and Multi Media Streaming (MMS). The packet transmission of the communication unit 210 may be controlled based on at least one protocol.

The controller 1620 may transmit the media receiver application or the media service daemon application to the electronic device 1500 in response to a download request of the media receiver application or the media service daemon application from the electronic device 1500.

The storage unit 1630 may store a media receiver application or a media service daemon application.

The electronic device and its operation method according to the present invention can not be limitedly applied to the configuration and method of the embodiments described as described above, the embodiments are all or part of each embodiment so that various modifications can be made It may alternatively be configured in combination.

Meanwhile, the method of operating the electronic device of the present invention may be embodied as processor readable code on a processor readable recording medium included in the electronic device. The processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor. Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet. . The processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the specific embodiments described above, but the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims (15)

A network interface unit for receiving a search message for searching for a media service daemon from the media player; And
A control unit for executing a receiver picker and a media service daemon;
In response to receiving the search message, the executed media service daemon performs pairing with the media player, and sends a media sharing message sent by the receiver picker according to a web-based protocol promised with the paired media player. Convert, send the converted media sharing message to the paired media player,
The media service daemon includes a communication management module,
The communication management module converts the actual media sharing protocol into a web-based protocol after the connection between the media sharing control device, the media service daemon, and the media receiver is completed, and transmits data to the media receiver based on the converted protocol.
Media sharing control. The method of claim 1,
And the media sharing message comprises at least one of a play command, a playback command, and a stop command. The method of claim 2,
The playback command is
A URL (Uniform Resource Locator) of contents ordered to be played by the receiver picker,
And the media playback apparatus receives a media stream of the content based on the URL. The method of claim 1,
And the media service daemon controls the receiver picker to transmit at least one of a service name of a media sharing service, its address, and a device name of the media player. The method of claim 1,
And the media service daemon includes the paired media player in a media receiver list. The method of claim 1,
And the media service daemon is executed in the background. The method of claim 1,
And the media service daemon opens and waits for a port for receiving a search message transmitted from the media player. The method of claim 1,
And the media service daemon is implemented in a plug-in manner. The method of claim 8,
And at least one of a module for communicating with the receiver picker of the media service daemon through a media sharing protocol and a module for discovering the receiver picker are plugged in. A network interface unit which transmits a search message for searching for a media service daemon to a media sharing controller; And
A control unit for executing a web socket based service discovery and communication management module,
The executed websocket-based service discovery controls the search message to be transmitted according to the web-based protocol agreed with the media sharing controller, and receives a response to the transmitted search message from the media sharing controller. Pairing with the media sharing controller,
When the executed communication management module receives the media sharing message transmitted according to the web-based protocol from the paired media sharing control device, the received communication management module parses the received media sharing message,
After the connection between the media sharing control device, the media service daemon, and the media receiver is completed, the communication management module converts the actual media sharing protocol into a web-based protocol and converts data based on the converted protocol. Received from the media sharing control device,
Media player. delete delete delete delete delete

Images