WO2013168992A1

WO2013168992A1 - Method, apparatus and system for device discovery and content download in multi-network

Info

Publication number: WO2013168992A1
Application number: PCT/KR2013/004002
Authority: WO
Inventors: 이민수; 양승률
Original assignee: 엘지전자 주식회사
Priority date: 2012-05-09
Filing date: 2013-05-08
Publication date: 2013-11-14

Abstract

Disclosed are a method, an apparatus and a system for device discovery and content download in multi-network. The method for device discovery in multi-network may be performed by a first device connected to a first network, may discover a second device of a second network based on either multi-network probing or multi-network advertising, may join to the second network based on the discovery information about the second device, and may update a recently connected device list using the discovery information on the second device. Thus, device discovery can be performed in an automated and quick manner between devices belonging to different networks in a multi-network environment in which multiple different networks co-exist, and content download can be performed based on the thus-performed device discovery.

Description

Method, apparatus and system for device discovery and content download in multiple networks

The present invention relates to a device discovery and content download method, apparatus and system in a multi-network, and more particularly, to a technique for automatically performing rapid device discovery between devices in a multi-network, and based on this technology to perform content download It is about.

Recently, with the standardization of data communication standards and terminals and the intelligentization of devices, there is an increasing demand to build a more efficient and convenient system by interworking a plurality of devices and services. A typical example of this need is a home network. The home network interconnects devices and services distributed at various locations such as information appliances, wireless communication devices, and personal computer (PC) -related devices through wired or wireless communication.

The home network may provide a content sharing environment for sharing content between devices, or a reservation download environment for pre-downloading content to a device such as a NAS or a set-top box using a mobile device. Various basic technologies such as Universal Plug and Play (UPnP) and Universal Plug and Play (UPnP) may be used to implement a home network that provides a content sharing or reservation download environment.

In general, a plurality of different networks may coexist in a content sharing or reservation download environment. For example, in the above environment, a group owner such as a network that can be connected through an access point (AP) such as Ethernet or Wi-Fi Direct, or a group owner such as Wi-Fi Direct A plurality of networks, such as a network that can be connected through a network, can coexist.

In order to perform content sharing or scheduled download, the device must discover the target device. In general, device discovery is performed in a network to which the device belongs. Therefore, under a multi-network in which a plurality of different networks coexist, if a device is connected to a specific network, the device cannot discover and cooperate with a device connected to another network.

For example, assuming that under a multi-network, a first device connected to a particular network is to be used to send a content reservation request to a second device connected to another network, the first device is connected to the multiple networks. It is not possible to know which network the second device is connected to, nor the state of the second device.

In this case, the user must directly check the network to which the second device belongs through the second device and input the confirmed network information to the first device. However, it is true that the user wants the first device and the second device to connect with each other without having to check which network the first device or the second device is connected to.

Accordingly, there is an urgent need to develop a technology for automatically discovering devices among heterogeneous networks in a multi-network and performing content sharing or reservation download based on the discovery.

Disclosure of Invention The present invention has been made to solve such a problem, and an object thereof is to provide a device discovery method and apparatus in a multi-network capable of automatically performing rapid device discovery between devices in a multi-network.

In addition, another object of the present invention is to provide a content download method, apparatus and system capable of performing scheduled download of content based on such device discovery.

In order to achieve this object, the present invention provides a device discovery method in multiple networks in one aspect. The device discovery method in the multi-network is performed by a first device connected to the first network and discovers a second device of the second network based on one of multi-network probing and multi-network advertising. Making a step; Joining to the second network based on the discovery information of the second device; And updating the listened connected device list using the discovery information of the second device.

The second network may be, for example, a Wi-Fi direct network. The discovery information includes device identification information, a connection type, a basic service set identifier (BSSID), a service set identifier (SSID), a P2P group identifier, a security type, a security key, It may include at least one of an IP address and a port.

The multi-network probing may include sequentially probing a plurality of networks corresponding to a plurality of pieces of authentication information of the first device. The multi-network advertising may include receiving advertising messages from a plurality of devices connected to a plurality of networks, respectively.

Discovering the second device may comprise: acquiring a message sent from the second device by probing multiple networks; And extracting discovery information of the second device from the obtained message. Discovering the second device may include receiving an advertising message from the second device; And extracting discovery information of the second device from the received advertising message.

Joining to the second network may include detecting information of a second network to which the second device is connected from discovery information of the second device; And joining to the detected second network.

The device discovery method in the multi-network includes: disconnecting a connection with the second device; And connecting to the second device connected to the second network based on the updated listened connected device list.

On the other hand, in order to achieve the above object of the present invention the present invention provides a device discovery apparatus in a multi-network in another aspect. The device discovery apparatus in the multi-network includes: a memory; And discover a target device of a second network based on any one of multi-network probing and multi-network advertising and connect to the second network based on discovery information of the target device. And a device manager that joins and updates a list of listened connected devices stored in the memory using discovery information of the target device.

On the other hand, in order to achieve the above object of the present invention, the present invention provides a content download method in another aspect. The content download method may be performed by a first device connected to a first network, and discovering a second device of a second network based on one of multi-network probing and multi-network advertising; Joining to the second network based on the discovery information of the second device; And transmitting, via the second network, a queue request to the second device requesting to download content from a source to the second device.

The method of downloading a content may include: updating a listened connected device list using discovery information of the second device; Disconnecting from the second device; And connecting to the second device connected to the second network based on the updated listened connected device list.

On the other hand, in order to achieve the above object of the present invention, the present invention provides a content download device in another aspect. The content download apparatus is connected to a first network, discovers a second device of a second network based on one of multi-network probing and multi-network advertising, and based on discovery information of the second device. A device manager joining the second network; And a queue manager for transmitting a queue request to the second device requesting to download content from the source to the second device through the second network.

On the other hand, in order to achieve the above object of the present invention, the present invention provides a content download system in another aspect. The content download system includes a first device connected to a first network; And a second device connected to the second network. The first device discovers the second device based on one of multi-network probing and multi-network advertising, joins to the second network based on discovery information of the second device, The queue request for downloading the content may be transmitted to the second device. The second device may download the content from a source to the second device in response to the queue request.

As described above, according to the present invention, in a multi-network environment in which a plurality of different networks coexist, fast device discovery may be automatically performed between devices belonging to different networks, and content is downloaded based on such device discovery. can do.

1 is a block diagram illustrating a configuration of a content service system to which a device discovery and content download method in a multi-network according to an exemplary embodiment of the present invention can be applied.

2 is a block diagram illustrating a detailed structure and an associated interface of a client device of a content service system.

FIG. 3 shows a diagram for describing the interfaces shown in FIG. 2.

4 illustrates device discovery and content download in a multi-network in accordance with a preferred embodiment of the present invention.

5 illustrates device discovery and content download in a multi-network in accordance with another preferred embodiment of the present invention.

6 illustrates device discovery and content download in multiple networks according to another preferred embodiment of the present invention.

7 is a schema for describing items managed by a listened connected device list.

8 illustrates device discovery and content download in multiple networks according to another preferred embodiment of the present invention.

9 illustrates device discovery and content download in a multiple network according to another preferred embodiment of the present invention.

10 illustrates device discovery and content download in multiple networks according to another preferred embodiment of the present invention.

11 illustrates device discovery and content download in a multiple network according to another preferred embodiment of the present invention.

12 illustrates device discovery and content download in a multiple network according to another preferred embodiment of the present invention.

FIG. 13 exemplarily illustrates an embodiment of indicating a device of a multi-network at a client device.

14 exemplarily illustrates another embodiment of displaying a device of multiple networks at a client device.

FIG. 15 is a flowchart for explaining an embodiment of a multi-network probing procedure performed by a device. FIG.

16 is a flowchart illustrating an embodiment of a procedure of multi-network advertising.

17 illustrates a content download procedure using Wi-Fi Direct according to a preferred embodiment of the present invention.

As the present invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is said to be 'connected' or 'connected' to another component, it may be directly connected to or connected to that other component, but it may be understood that another component may exist in between Should be. On the other hand, when a component is said to be 'directly connected' or 'directly connected' to another component, it should be understood that no other component exists in the middle.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms 'comprise' or 'have' are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, with reference to the accompanying drawings, it will be described in detail a preferred embodiment of the present invention. In the following description of the present invention, the same reference numerals are used for the same elements in the drawings and redundant descriptions of the same elements will be omitted.

As shown in FIG. 1, a content service system may be divided into a server domain and a user domain.

The server domain may operate a service and a network policy for a content service and provide content to a user domain based on the policy. In other words, the server domain may mean a domain including servers for providing a content service. Such a server domain may perform content provision and operation of a service to a user domain such as content creation, sale, distribution, policy operation, and permission restriction.

The server domain may include a content server (CS) for providing content, a content policy server (CPS) for operating a policy for a content service, a content policy server (NPS) for operating a network policy, and the like. There may be multiple content servers. For example, the server domain may include a content download server for downloading content, a content streaming server for streaming content, and the like.

The user domain may include the devices 100 of the user. The device 100 may be, for example, a stationary device such as a PC, a set-top box, or a portable device such as a smartphone, a mobile phone, a mobile handset, a tablet, a personal digital assistant (PDA), a notebook computer, or the like. The devices 100 may access a local network based on UPnP, DLNA, and the like, and may interoperate with each other through wired or wireless communication.

The device 100 of the user may be a client device or an intermediate device.

The client device may mean a physical hardware device having at least one network interface and local storage. For example, the client device may be a mobile handset, tablet, smartphone, or the like, capable of consuming content. The client device CD may have modules for receiving a content service.

The intermediate device may be a dual role client / server device on the network that may be used to stage an asset for a client device row. The intermediary device may temporarily hold the asset until the asset is delivered to the client device. The intermediate device typically does not consume the content directly, but may consume the content directly. For example, the intermediate device may stage the content. That is, the intermediate device may download the content from the server, and store and play the content.

As shown in FIG. 2, the client device CD includes a local application / user agent 110, a player 130, a network policy client 140, A virtual storage device 150, a queue / policy engine (QPE) 120, and the like may be included.

The local application / user agent 110 may be software for a content service and may include a local application and a user agent. For example, the local application / user agent 110 may provide a user interface, a service menu, a service selection, a content selection, and the like for allowing a user to receive a content service.

The local application may communicate with the queue / policy engine 120 using a particular interface protocol, such as the Q2 interface protocol, as software resident on the client device. The user agent may refer to software that renders and executes a server-supplied application such as, for example, a web browser or middleware of a client device CS. The local application / user agent 100 may be activated when the download of content is started or completed.

The player 130 is for playing content provided through a content service. For example, the player 130 may be a media player capable of playing download content or streaming content. The network policy client 140 may acquire a network policy and control the client device CD according to the acquired network policy while communicating with the network policy server NPS.

The virtual storage device 150 is a representation of local storage that can be accessed through a cache object. For example, the virtual storage device 150 may be a general local storage such as a hard disk, a USB memory connected to the device, a flash memory, a virtual area such as a daemon, or the like.

The queue / policy engine 120 of the client device (CD) is configured to cache / download specific content (asset) of the content server when it satisfies the policy given by the Content Policy Server (CPS) or the Network Policy Server (NPS). A request for caching / downloading of content can be sent, which can be called a queue request. For example, the queue request may include a URI corresponding to content (asset). The queue request may include not only a codec type media profile, a container type, a multipurpose internet mail extension type, a store name, a total length of the queue request, content information, Policy information and the like. In addition, the queue request may include bandwidth information for each source URI estimated by the local application / user agent 110.

The queue / policy engine 120 is a module included in the client device CD and may communicate via P1, S, D1, D2, Q2, D3, and Q3 interface protocols. The queue / policy engine 120 may maintain a queue on behalf of each local application and content server, interface with storage, and synchronize queue requests with policies. You can take responsibility. Therefore, the queue / policy engine may be referred to as a service client for a content sharing service.

The queue / policy engine 120, that is, the queue / policy engine, may include a queue manager 122, a policy client 126, an intermediate device manager 124, and the like. Can be.

The queue manager 122 may operate a queue for downloading or streaming content. For example, the queue manager 122 may include a stream queue manager and a download manager.

The queue manager 122 may send a queue request to an intermediary device (IMD) or another client device and receive a response from the intermediary device (IMD) or another client device. Queue manager 122 may also receive a queue request from an intermediary device (IMD) or other client device, download content and transmit its response in accordance with the queue request.

For example, queue manager 122 sends a queue request requesting to download specific content from a content server (CS) or a local server, such as a digital media server (DMS), to an intermediate device (IMD) and receives the response. can do. The queue manager 122 may transmit a queue request to the intermediate device IMD to transmit the content downloaded from the content server CS or the local server to the client device CD.

In addition, the queue manager 122 may perform a write check for use of content. For example, the queue manager 122 may perform a write check for staging, for example, an asset from the content server CS, for staging an asset corresponding to the content selected by the local application 110 via the intermediate device IMD. A write check for downloading to the device IMD may be performed. The write check may include a digital right management (DRM) capability check and a license check.

The DRM capability check may verify whether the intermediary device (IMD) can support the DRM system protecting the asset, based on the DRM information of the asset and the DRM capability for the intermediary device (IMD). have. The license check can verify that the license mediated device (IMD) can obtain a license for use of the asset. For example, the license check may be to check a right defined in a right token.

Receipt of the requested asset managed by the queue can be accomplished using unicast download or multicast download, or a combination of both mechanisms. The queue / policy engine 120 must preserve a single queue even if the commands defined in the queue interface change their priority or order.

The policy client 126 maintains a policy object as a subsystem of the queue / policy engine 120. The policy client 126 may control the queue / policy engine 120 in accordance with policies from the content policy server (CPS). For example, the policy client 126 may retrieve policies from the content policy server (CPS) and adjust the queue request behavior.

The intermediary device manager 124 may manage intermediary devices (IMDs) or other client devices that cooperate with the client device (CD). For example, intermediary device manager 124 may discover intermediary devices (IMDs) or other client devices connected to the network and manage their status. The intermediary device manager 124 may send or receive necessary messages with the intermediary device or other client devices. The intermediate device manager 124 may perform device discovery in multiple networks.

Meanwhile, the client device may include a plurality of communication units for communicating with the outside. For example, the client device may be a 3G / 4G communication unit for connecting to a 3G or 4G / LTE (Long Term Evolution) mobile network, a WiFi direct communication unit for connecting to a Wi-Fi Direct network, a wireless LAN (WLAN) And a WLAN communication unit for connecting to a network, and a Wi-Fi communication unit for connecting to a general Wi-Fi network having an access point (AP). Further, the intermediate device may likewise be provided with the plurality of communication units. Thus, the client device and the intermediate device can be connected via, for example, a Wi-Fi Direct network.

FIG. 3 shows a diagram for describing the interfaces shown in FIG. 2.

As illustrated in FIG. 3, interfaces associated with a content service system may be divided into P, Q, S, and D interface groups. Each interface can work with a client-server architecture.

The P interface group may define a link and policy between the queue / policy engine 120 and the content policy server (CPS). This P interface group may include P1 and P2 interfaces. In the P1 interface, the server may be a content policy server (CPS) and the client may be a queue / policy engine 120. In the P2 interface, the server may be a network policy client 140 and the client may be a queue / policy engine 120. In the P4 interface, the server may be a content server (CS) and the client may be an intermediate device (IMD).

The Q interface group can define queue request handling. The Q interface group may be a primary command channel interworking between the content server CS, the intermediate devices IMD, and the queue / policy engine 120. The Q interface group can allow Caching Functionality to be called by the local application. In the Q2 interface, the server may be a queue / policy engine 120 and the client may be a local application.

Queue requests submitted via the Q2 interface protocol, i.e., the interface between the local agent and the queue / policy engine, may include a complete URL that may be called from the context of the user agent or the calling local application to download the asset. Alternatively, the queue request may include a local URL for calling a calling local application for pre-negotiate download.

In the Q3 interface, the server may be a queue / policy engine 120 and the client may be an intermediary device (IMD). In the Q4 interface, the server may be a content server (CS) and the client may be an intermediate device (IMD).

The S interface group can extract storage and cache capabilities to the queue / policy engine. In the S interface, the server may be a virtual storage device 150 and the client may be a queue / policy engine 120.

The D interface group may be used for data transmission. In the D1 interface, the server may be a content server (CS) and the client may be a queue / policy engine 120. In the D2 interface, the server may be a queue / policy engine 120 and the client may be a player 130. In the D3 interface, the server may be an intermediary device (IMD) and the client may be a queue / policy engine 120. In the D4 interface, the server may be a content server (CS) and the client may be an intermediate device (IMD).

Figure 4 illustrates device discovery and content download in a multi-network in accordance with a preferred embodiment of the present invention using such a content service system.

In the embodiment shown in FIG. 4, the client device CD is connected to the Internet, such as a first network, for example an Information System Network (ISN) network, and has a first intermediate device IMD1 and a second intermediate device IMD2. May be connected to a second network, such as a WiFi direct network. The client device CD causes a target device connected to the second network, for example, the first intermediate device IMD1, to send content from a local content server LCS connected to the second network, such as a digital media server (DMS). I want to request a download.

In this way, the target device is not connected to the first network to which the client device CD is connected. In general, the client device CD performs device discovery in the first network to which the client device CD is connected to discover the target device. However, since the first intermediate device IMD1 and the second intermediate device IMD2 are not connected to the first network, according to the conventional device discovery, the client device CD cannot discover the target device.

In contrast, the device discovery according to the preferred embodiment of the present invention can perform a sequential automatic device discovery for all the networks that the client device (CD) can legally access in an environment where multiple networks coexist.

That is, as shown in FIG. 4, in the device discovery according to the preferred embodiment of the present invention, the client device CD may discover the first intermediate device IMD1 based on performing multi-network probing. (Step: S1). The multi-network probing is to discover the device by automatically searching all networks corresponding to the authentication information that the device has, and obtaining discovery information of a device connected to each network. The authentication information may be, for example, a credential for accessing a network, a wired equivalent privacy (WEP), a Wi-Fi Protected Access (WPA) key, or the like.

For example, it is assumed that the client device CD stores authentication information for connecting to the second network, for example, WEP, WPA, credentials, and the like. The client device CD may use the authentication information to capture messages sent over the second network. Among the messages, there may be a message of the first intermediate device IMD1 or the second intermediate device IMD2. Accordingly, the client device CD may acquire the message of the first intermediate device IMD1 using the authentication information of the second network, and extract the discovery information of the first intermediate device IMD1 from the obtained message.

The discovery information may include, for example, device identification information, a connection type, a basic service set identifier (BSSID), a service set identifier (SSID), a P2P group identifier, a security type, and a security key. , Items such as an IP address, a port number, and the like.

It is not necessary to extract all of the items in step S1, but the discovery information extracted by the client device CD includes configuration information of a network to which the first intermediate device IMD1 is connected, such as a connection type and a basic service set identifier (and / Or service set identifier), P2P group identifier, etc. should be included.

In Wi-Fi, the basic subset identifier may be an ID for identifying a basic Wi-Fi access point (AP). When a plurality of Basic Service Sets (BSSs) are gathered to form one Extensive Service Set (ESS), an identifier assigned thereto is an SSID. Therefore, the network configuration information may include at least one of a basic service set identifier or a service set identifier.

On the other hand, if too many networks coexist in a multi-network environment, multi-network probing may take a long time. Therefore, the client device (CD) needs to be collected, which is the maximum time required for multi-network probing. The type of discovery information to be performed may be set in advance, and discovery based on multi-network probing may be performed according to the set information.

Next, the client device CD may join the second network to which the first intermediate device IMD1 is connected based on the extracted device discovery information (step S2). For example, the client device CD detects the information of the network to which the first intermediate device IMD1 is connected, that is, the information of the second network, from the extracted device discovery information and, based on the detected information, to the second network. Can join.

After joining to the second network, the client device CD may request the first intermediary device IMD1 to receive the remaining device discovery information if any of the device discovery information of the first intermediary device IMD1 is not received. . If all device discovery information is secured in the multi-network probing step (step S1), this process may be omitted.

The client device CD may update the Recently Connected Device List managed by the client device CD using the discovery information of the first intermediate device IMD1. The received connected device may mean a list including information on devices (eg, an intermediate device, another client device, etc.) that have been recently connected to the client device CD.

The list of connected devices may be stored in the storage of the client device CD, for example, the virtual storage device 150. For example, the client device (CD) generates a listened connected list using the information obtained through device discovery when first connected to the network, stores it in storage, and then acquires the device each time the device discovery is performed. Based on this information, you can constantly update the listened connected list.

On the other hand, if the client device CD does not have a listened connected device list, the client device CD may generate a listened connected device list using discovery information of devices collected through multi-network probing. . For example, the client device CD may generate a listened connected device list using the discovery information of the first intermediate device IMD1. The generated listened connected device list may be continuously updated and managed by the client device (CD).

It may be performed by the intermediate device manager 124 of the client device (CD) which is the device discovery related operation described above. Meanwhile, the client device CD may release the connection with the first network that was previously connected to join the second network. On the other hand, since the connection with the first network is disconnected when the second network is connected, the client may be designated to perform a request from a user (that is, a request that can be performed only when the first network is interworked). The device CD may wait for a preset waiting time before performing the multi-network probing and start the multi-network probing if there is no request from the user until the waiting time expires.

Next, the client device CD connected to the second network may obtain a content (or asset) list from the local content server LCS, for example, the DMS, belonging to the second network (step S3). The client device CD may then select the content to download from the content list (step: S4). Upon selection of content, the client device CD may interwork with a content policy server (CPS), a content server (CS), and the like in the server domain to confirm whether the corresponding content is usable content. Such requesting of the content list and content selection may be performed, for example, by the local application / user agent 110 of the client device (CD).

When content is selected, an operation related to content download may be performed by the queue manager 122 of the client device CD. The client device CD may transmit a device capability request message for requesting device capability of the first intermediate device IMD1 to the first intermediate device IMD1 (step S5). Upon receiving the device capability request message, the first intermediate device IMD1 may transmit a device capability response message including the requested device capability to the client device CD (step S6). The device capability may be information in the form of Extensible Markup Language (XML), and may include a plurality of capability items.

The device capability includes a device ID, a device name, a device friendly name, a user ID, a current power source, and a charging status. ), Power Level, Supporting Media Profiles, Supporting Codec Types, Storage Capacity, Storage Function Groups, Point Node , Storage Usage, Maximum Size of Queue Request, Maximum Number of Queue Request, Current Number of Queue Request, Entry of Network Interface Number of Entries, Network Access Type, Media Transport, Bandwidth Limit, etc. A capability item such as may be included.

The client device CD having obtained the device capability of the first intermediate device IMD1 may request a queue request to download the selected content from the local content server LCS to the intermediate device based on the device capability. It may transmit to the first intermediate device IMD1 (step S7). For example, the queue manager 122 of the client device CD may send a queue request to the first intermediate device IMD1 via the Q3 interface.

The queue request may include access information for allowing the first intermediate device IMD1 to download an asset suitable for the capability of the first intermediate device IMD1 among physical assets corresponding to the selected content. The queue request may include an identifier for identifying the selected content, access information for identifying and accessing a physical asset to be substantially downloaded corresponding to the content. For example, assuming that the identifier of the content is information for identifying a movie "Avatar", the access information may be information for identifying and accessing a physical "Avatar file" to be actually downloaded. For example, the access information may include information in the form of URL, URI, file name. That is, the client device CD delivers information for downloading an asset suitable for the capability of the first intermediate device IMD1 to the first intermediate device IMD1 through a queue request.

For example, the client device CD uses the device capability of the first intermediate device IMD1 received from the first intermediate device IMD1 to store storage capacity and storage retention of the first intermediate device IMD1, The media profile may be checked, and the first media device IMD1 may be transmitted to the first mediator device IMD1 through the queue request to download an asset corresponding to the downloadable size and the supportable media profile.

The first intermediate device IMD1 receiving the queue request may access the local content server LCS based on the information included in the queue request, and download content from the local content server LCS (step: S8). ). At this time, the first intermediate device IMD1 may download a physical asset, for example, a content file, suitable for the device capability of the first intermediate device IMD1 based on the queue request, from the local content server LCS. Can be.

In the embodiment shown in FIG. 5, the client device CD is connected to a first network, for example an ISN network, and the first intermediate device IMD1 and the second intermediate device IMD2 are connected to a second network, eg Wi-Fi Direct. It may be connected to the network. The client device CD wishes to request a target device connected to the second network, for example, the first intermediate device IMD1, to download content from a local content server LCS, eg, a DMS, connected to the second network. do.

As shown in FIG. 5, the client device CD may discover the first intermediary device IMD1 based on multi-network advertising in an environment where multi-networks coexist (step: S11). ).

In the multi-network advertising, a device belonging to a specific network transmits an advertising message to networks other than the network. For example, the first intermediate device IMD1 connected to the second network may transmit an advertising message to the devices of the first network. The client device (CD) has authentication information that can connect with the second network. The authentication information may be, for example, a credential for accessing a network, a wired equivalent privacy (WEP), a Wi-Fi Protected Access (WPA) key, or the like. Accordingly, the client device CD may receive an advertising message of the first intermediate device IMD1. The client device CD may extract discovery information of the first intermediate device IMD1 from the received advertising message.

The discovery information may include, for example, items such as device identification information, connection type, basic service set identifier (and / or service set identifier), P2P group identifier, security type, security key, IP address, port number, and the like. It is not necessary to extract all of the items in step S1, but the discovery information extracted by the client device CD includes configuration information of a network to which the first intermediate device IMD1 is connected, such as a connection type, a basic service set identifier, and a P2P. Group identifiers, etc. must be included.

Next, the client device CD may join the second network to which the first intermediate device IMD1 is connected based on the extracted device discovery information (step S12). For example, the client device CD detects the information of the network to which the first intermediate device IMD1 is connected, that is, the second network, from the extracted device discovery information, and joins to the second network using the detected information. can do.

After joining to the second network, the client device CD may request the first intermediary device IMD1 to receive the remaining device discovery information if any of the device discovery information of the first intermediary device IMD1 is not received. . If all of the device discovery information is secured in the multi-network advertising step (S11), this process may be omitted.

On the other hand, if too many networks coexist in a multi-network environment, multi-network advertising may take a long time. Therefore, the first intermediary device (IMD1) may be used for the maximum number of networks to be advertised and for multi-network advertising. The maximum time required, the type of discovery information to be transmitted, and the like, may be set in advance, and an advertising message may be transmitted to the multi-network according to the set information.

On the other hand, even in the client device (CD), the maximum number of networks to receive the advertising message, the maximum time for discovery based on the multi-network advertising, the kind of discovery information to be collected in advance, etc. in advance And device discovery based on multi-network advertising according to the set information.

The client device CD may update the list of connected connected devices managed by the client device CD using the device discovery information of the first intermediate device IMD1. As mentioned above, the listened connected device may mean a list including information of devices (eg, an intermediate device, another client device, etc.) that have recently been connected to the client device CD. If there is no list of listened connected devices, the client device CD may generate a new list of connected devices based on the device discovery information of the first intermediate device IMD1.

It may be performed by the intermediate device manager 124 of the client device (CD) which is the device discovery related operation described above. Meanwhile, the client device CD may release the connection with the first network that was previously connected to join the second network. Since a connection with the second network is disconnected from the first network, there may be a designation for performing a request from a user (that is, a request that can be performed only when the first network is connected). CD) may initiate multi-network discovery if it waits for a preset waiting time before performing multi-network probing and there is no request from the user until the waiting time expires.

Next, the client device CD connected to the second network may obtain a content (or asset) list from the local content server LCS, for example, the DMS, belonging to the second network (step S13). The client device CD may then select the content to download from the content list (step S14). Upon selection of content, the client device CD may interwork with a content policy server (CPS), a content server (CS), and the like in the server domain to confirm whether the corresponding content is usable content. Such requesting of the content list and content selection may be performed, for example, by the local application / user agent 110 of the client device (CD).

When content is selected, an operation related to content download may be performed by the queue manager 122 of the client device CD. The client device CD may transmit a device capability request message for requesting device capability of the first intermediate device IMD1 and IMD1 to the first intermediate device IMD1 and IMD1 (step S15). Upon receiving the device capability request message, the first intermediate device IMD1 may transmit a device capability response message including the requested device capability to the client device CD (step S16). The device capability may be information in the form of Extensible Markup Language (XML). As mentioned above, the device capability may include a plurality of capability items.

The client device CD having obtained the device capability of the first intermediate device IMD1 may request a queue request to download the selected content from the local content server LCS to the intermediate device based on the device capability. The first intermediate device IMD1 may be transmitted (step S17). For example, the queue manager 122 of the client device CD may send a queue request to the first intermediate device IMD1 via the Q3 interface.

The queue request may include access information for allowing the first intermediate device IMD1 to download an asset suitable for the capability of the first intermediate device IMD1. The queue request may include an identifier for identifying the selected content, access information for identifying and accessing a physical asset to be substantially downloaded corresponding to the content. The access information may be at least one of URL, URI, and file name. That is, the client device CD delivers information for downloading an asset suitable for the capability of the first intermediate device IMD1 to the first intermediate device IMD1 through a queue request.

The first intermediate device IMD1 receiving the queue request may access the local content server LCS based on the information included in the queue request, and download content from the local content server LCS (step: S18). ). At this time, the first intermediate device IMD1 may download a physical asset, for example, a content file, suitable for the device capability of the first intermediate device IMD1 based on the queue request, from the local content server LCS. Can be.

As shown in FIG. 6, the client device CD is connected to a first network, such as an information system network (ISN) network, and the intermediate device (IMD) and the local content server (LCS) are connected to a second network, such as Wi-Fi. It is connected to a direct network. Accordingly, the client device CD and the intermediate device IMD are not disconnected (step S21), and the intermediate device IMD and the local content server LCS are connected (step S22).

First, the client device CD may discover the intermediate device IMD based on multi-network probing (step S23). The multi-network probing is to discover the device by automatically searching all networks corresponding to the authentication information that the device has, and obtaining discovery information of a device connected to each network.

For example, it is assumed that the client device CD stores authentication information for connecting to the second network, for example, WEP, WPA, credentials, and the like. The client device CD may use the authentication information to capture messages sent over the second network. Among the messages may be a message of the intermediate device IMD or the second intermediate device IMD2. Accordingly, the client device CD obtains a message of the intermediate device IMD using the authentication information of the second network, and from the obtained message, discovery information of the intermediate device IMD, for example, a connection type, a basic service set identifier, and a P2P. The group identifier can be extracted.

Meanwhile, the client device (CD) may preset the maximum number of networks to be probed, the maximum time required for multi-network probing, the type of discovery information to be collected, and the like based on the set information. You can also do

Next, the client device CD may join the second network to which the intermediate device IMD is connected based on the extracted device discovery information (step: S24). For example, the client device CD detects and detects information of the Wi-Fi Direct network to which the intermediate device IMD is connected, such as a connection type, a basic service set identifier, a P2P group identifier, and the like, from the extracted connection device discovery information. This information can then be used to join a Wi-Fi Direct network.

The client device CD may update the Recently Connected Device List managed by the client device CD using the discovery information of the intermediate device IMD (step S25). As mentioned above, the listened connected device may refer to a list including information of devices (eg, an intermediate device, another client device, etc.) that have been recently connected to the client device CD.

7 is a schema for describing items managed by a listened connected device list.

As shown in FIG. 7, the listened connected device list includes a device friendly name, a connection type, a basic service set identifier (BSSID), and a P2P group identifier. P2P Group Identifier, Security Type, Security Key, IP Address, Port, Last Connected Time, Device Description, etc. can do. The received connected device list may further include a service set identifier (SSID), or may include a subset identifier instead of a basic service set identifier. That is, the listened connected device list may include at least one of a basic service set identifier or a service set identifier.

The device friendly name is an item representing the friendly name of the device and may be information in a string form. For example, the device friendly name of the intermediate device (IMD) connected to Wi-Fi network direct may be "My Phone".

The connection type may be an item representing a connection network of a device. The connection type may be string type information indicating at least one of Ethernet, 802.11, 802.11 Wi-Fi Direct, MoCA, Bluetooth, ZigBee, and the like. For example, the connection type of an intermediate device (IMD) connected to Wi-Fi Direct may be "802.11 WiFi Direct."

The basic subset identifier and the P2P group identifier may be an item for identifying the basic subset and the P2P group to which the device is connected. The basic subset identifier and the P2P group identifier of the intermediate device (IMD) may be, for example, "802.11 WiFi Direct BSSID" and "802.11 WiFi Direct GroupID".

The security type and the security key may represent a security type and a security key required for accessing a network, respectively. For example, the security type may be "WEP" and the security key may be "WEPKEY". The IP address and port may represent a connection address and a connection port, respectively, and may be numbers such as "192.168.11" and "11347", for example.

The last connected time may indicate the last time the device connected. For example, the last connected time of the intermediate device IMD may be "2011-02-22 T 12:00" 44 ".

The device description may include various information for describing the device. For example, the device description may include connection information, such as a URL, that can access device information, such as device capability of the intermediary device (IMD). In this case, the client device CD may obtain the capability information of the intermediate device IMD using the URL of the device description.

Such a listened connected device list may be stored in the storage of the client device (CD), for example, the virtual storage device 150. For example, the client device (CD) generates a listened connected list using the information obtained through device discovery when first connected to the network, stores it in storage, and then acquires the device each time the device discovery is performed. Based on this information, you can constantly update the listened connected list.

On the other hand, if the client device CD does not have a listened connected device list, the client device CD listens using discovery information of devices collected through multi-network probing, instead of performing step S25. You can create a list of incorrectly connected devices. For example, the client device CD may generate the listened connected device list using the discovery information of the intermediate device IMD. The generated listened connected device list may be continuously updated and managed by the client device (CD).

When the client device CD joins the second network, the client device CD is connected to the second network, and can interoperate with the intermediate device IMD through the second network (step S26).

The client device (CD) connected to the second network may then obtain a list of content (or assets) from a local content server (LCS) belonging to the second network, such as a DMS, and select content to download from the content list (step). : S27).

Once the content is selected, the queue manager 122 of the client device CD may send a queue request to the intermediary device IMD requesting to download the selected content from the local content server LCS to the intermediary device (step: S28). As mentioned above, the client device CD obtains the capability information of the intermediate device IMD from the intermediate device IMD, and downloads an asset suitable for the intermediate device IMD based on the capability information. The request may be made through the queue request.

The intermediate device IMD receiving the queue request may access the local content server LCS based on the information included in the queue request, and download content from the local content server LCS (step S29). The client device CD may release the connection to the second network, that is, the Wi-Fi Direct network, connected to the queue request (step S30).

On the other hand, after disconnecting from the Wi-Fi Direct network, the client device CD may wish to reconnect to the intermediate device IMD. In this case, the client device (CD) can quickly connect with the intermediate device (IMD) using the listened connected device list.

For example, the client device CD may query a list of listened connected devices to detect connection information of each device IMD, such as a connection type, a basic service set identifier, and a P2P group ID. The client device CD may join the second network using the detected connection information, then unicast the discovery request to the intermediary device IMD, and receive a discovery response from the intermediary device IMD. Thus, the client device CD can quickly discover the intermediate device IMD using the listened connected device list without performing multi-network discovery. If there is a change in the connection information of the intermediate device IMD, the client device CD may update the listened connected device list according to the changed information.

As shown in FIG. 8, the client device CD is connected to a first network, such as an information system network (ISN) network, and the intermediate device (IMD) and the local content server (LCS) are connected to a second network, such as Wi-Fi. It is connected to a direct network. Accordingly, the client device CD and the intermediate device IMD are not disconnected (step S31), and the intermediate device IMD and the local content server LCS are connected (step S32).

First, the client device CD may discover the intermediate device IMD based on the multi-network advertising of the intermediate device (step S33). In the multi-network advertising, a device belonging to a specific network transmits an advertising message to networks other than the network.

For example, an intermediate device (IMD) connected to the second network may send an advertising message to the devices of the first network. The client device (CD) has authentication information that can connect with the second network. The authentication information may be, for example, a credential for accessing a network, a wired equivalent privacy (WEP), a Wi-Fi Protected Access (WPA) key, or the like. Accordingly, the client device CD may receive an advertising message of the intermediate device IMD. The advertising message may include configuration information of Wi-Fi Direct, which is the second network. The client device CD may extract discovery information of the intermediate device IMD from the received advertising message. The extracted discovery information may include configuration information of Wi-Fi Direct.

Next, the client device CD may join the second network to which the intermediate device IMD is connected based on the extracted device discovery information (step S34). For example, the client device CD detects and detects information of the Wi-Fi Direct network to which the intermediate device IMD is connected, such as a connection type, a basic service set identifier, a P2P group identifier, and the like, from the extracted connection device discovery information. This information can then be used to join a Wi-Fi Direct network.

The client device CD may update the Recently Connected Device List managed by the client device CD using the discovery information of the intermediate device IMD (step S35). If there is no list of listened connected devices on the client device CD, the client device CD uses the discovery information of the devices collected through the multi-network advertising, instead of performing step S35. You can create a list of connected devices. For example, the client device CD may generate the listened connected device list using the discovery information of the intermediate device IMD.

When the client device CD joins the second network, the client device CD is connected to the second network, and can interoperate with the intermediate device IMD through the second network (step S36). The client device CD connected to the second network may obtain a list of content (or assets) from a local content server (LCS), for example, a DMS, belonging to the second network, and select content to download from the content list (step S37). ).

Once the content is selected, the queue manager 122 of the client device CD may send a queue request to the intermediary device IMD requesting to download the selected content from the local content server LCS to the intermediary device (step: S38). As mentioned above, the client device CD obtains the capability information of the intermediate device IMD from the intermediate device IMD, and downloads an asset suitable for the intermediate device IMD based on the capability information. The request may be made through the queue request.

Upon receiving the queue request, the intermediate device IMD may access the local content server LCS based on the information included in the queue request, and download content from the local content server LCS (step S39). The client device CD may release the connection to the second network, that is, the Wi-Fi Direct network, connected to the queue request (S40).

Meanwhile, as mentioned above, after disconnecting from the Wi-Fi Direct network, the client device CD may attempt to reconnect to the intermediary device IMD. In this case, the client device (CD) can quickly connect with the intermediate device (IMD) using the listened connected device list. For example, the client device CD may query a list of listened connected devices to detect connection information of each device IMD, such as a connection type, a basic service set identifier, and a P2P group ID. The client device CD may join the second network using the detected connection information, then unicast the discovery request to the intermediary device IMD, and receive a discovery response from the intermediary device IMD. Thus, the client device CD can quickly discover the intermediate device IMD using the listened connected device list without performing multi-network discovery. If there is a change in the connection information of the intermediate device IMD, the client device CD may update the listened connected device list according to the changed information.

As shown in FIG. 9, the client device CD and the local content server LCS are connected to a first network such as an ISN network, and the intermediate device IMD is connected to a second network such as a Wi-Fi direct network. have. Accordingly, the client device CD and the intermediate device IMD are not disconnected (step S42), and the client device CD and the local content server LCS are connected (step S41). The local content server LCS may be a DMS. According to another embodiment of the present invention, the local content server LCS may be replaced with the content server CS of the server domain.

The client device CD is provided with an AV service from the local content server LCS (step S43). The client device (CD) selects specific content while receiving an AV service and attempts to download the selected content to the intermediate device (IMD). By the way, the intermediate device IMD is connected to the Wi-Fi Direct network to which the client device CD is not connected. From the standpoint of the client device CD, it is unknown to which network the intermediate device IMD is connected.

Accordingly, the client device CD may discover the intermediate device IMD based on multi-network probing (step S44). For example, the client device CD may acquire messages transmitted through each network using its own authentication information such as WEP, WPA, credentials, etc., and then obtain the message of the intermediary device IMD. It is possible to extract the discovery information of the intermediate device (IMD) from the acquired message.

Next, the client device CD may join the second network to which the intermediate device IMD is connected based on the extracted device discovery information (step S45). For example, the client device CD detects and detects information of the Wi-Fi Direct network to which the intermediate device IMD is connected, such as a connection type, a basic service set identifier, a P2P group identifier, and the like, from the extracted connection device discovery information. Information can be used to join a second network, the Wi-Fi Direct network.

The client device CD may update the Recently Connected Device List managed by the client device CD using the discovery information of the intermediate device IMD (step S46). If there is no list of listened connected devices on the client device CD, the client device CD uses the discovery information of devices collected through multi-network probing, instead of performing step S46. You can create a device list. For example, the client device CD may generate the listened connected device list using the discovery information of the intermediate device IMD. The generated listened connected device list may be continuously updated and managed by the client device (CD).

When the client device CD joins the second network, the client device CD is connected to the second network, and can interoperate with the intermediate device IMD through the second network (step S48). On the other hand, the client device CD releases the connection with the ISN. Therefore, the connection between the client device CD and the local content server LCS is released (step S47).

Subsequently, the queue manager 122 of the client device (CD) connected to the second network may send a queue request to the intermediate device (IMD) requesting to download preselected content from the local content server (LCS) to the intermediate device. (Step S49). The client device (CD) obtains the capability information of the intermediate device (IMD) from the intermediate device (IMD), and through the queue request to download an asset suitable for the intermediate device (IMD) based on the capability information. You can request If the queue request is transmitted normally, the client device (CD) releases the connection with the second network, the Wi-Fi network. Therefore, the client device CD and the intermediate device IMD are disconnected (S50).

The intermediate device (IMD) receiving the queue request connects to the local content server (LCS) of the first network based on the information included in the queue request (step S51), and downloads content from the local content server (LCS). Can be done (step: S52).

Meanwhile, as mentioned above, after disconnecting from the Wi-Fi Direct network, the client device CD may attempt to reconnect to the intermediary device IMD. In this case, the client device (CD) can quickly connect with the intermediate device (IMD) using the listened connected device list.

As shown in FIG. 10, the client device CD and the local content server LCS are connected to a first network, such as an ISN network, and the intermediate device IMD is connected to a second network, such as a Wi-Fi Direct network. have. Accordingly, the client device CD and the intermediate device IMD are not disconnected (step S62), and the client device CD and the local content server LCS are connected (step S61). The local content server LCS may be a DMS. According to another embodiment of the present invention, the local content server LCS may be replaced with the content server CS of the server domain.

The client device CD is provided with an AV service from the local content server LCS (step S63). The client device (CD) selects specific content while receiving an AV service and attempts to download the selected content to the intermediate device (IMD). By the way, the intermediate device IMD is connected to the Wi-Fi Direct network to which the client device CD is not connected. From the standpoint of the client device CD, it is unknown to which network the intermediate device IMD is connected.

Accordingly, the client device CD may discover the intermediate device IMD based on the multi-network advertising of the intermediate device (step S64). In the multi-network advertising, a device belonging to a specific network transmits an advertising message to networks other than the network.

For example, an intermediate device (IMD) connected to the second network may send an advertising message to the devices of the first network. The client device CD may receive an advertising message of the intermediary device IMD. The advertising message may include configuration information of Wi-Fi Direct, which is the second network. The client device CD extracts discovery information of the intermediate device IMD from the received advertising message, and the extracted discovery information may include configuration information of Wi-Fi Direct.

Next, the client device CD may join the second network to which the intermediate device IMD is connected based on the extracted device discovery information (step S65). For example, the client device CD detects the information of the Wi-Fi Direct to which the intermediate device IMD is connected, for example, a connection type, a basic service set identifier, a P2P group identifier, and the like, from the extracted connection device discovery information. The information can be used to join a Wi-Fi Direct network.

The client device CD may update the list of connected connected devices managed by the client device CD using the discovery information of the intermediate device IMD (step: S66). If there is no list of listened connected devices on the client device (CD), instead of performing step S66, the client device (CD) listens using discovery information of devices collected through multi-network advertising. You can create a list of connected devices. For example, the client device CD may generate the listened connected device list using the discovery information of the intermediate device IMD.

When the client device CD joins the second network, the client device CD is connected to the second network, and interoperable with the intermediary device IMD through the second network (step S68). On the other hand, the client device CD releases the connection with the ISN. Therefore, the connection between the client device CD and the local content server LCS is released (step S67).

Subsequently, the queue manager 122 of the client device (CD) connected to the second network may send a queue request to the intermediate device (IMD) requesting to download preselected content from the local content server (LCS) to the intermediate device. (Step S69). The client device (CD) obtains the capability information of the intermediate device (IMD) from the intermediate device (IMD), and through the queue request to download an asset suitable for the intermediate device (IMD) based on the capability information. You can request If the queue request is transmitted normally, the client device (CD) releases the connection with the second network, the Wi-Fi network. Accordingly, the client device CD and the intermediate device IMD are disconnected (step S70).

The intermediate device (IMD) receiving the queue request connects to the local content server (LCS) of the first network based on the information included in the queue request (step S71), and downloads content from the local content server (LCS). Can be done (step S72).

As shown in FIG. 11, the client device CD and the intermediate device IMD are connected to a first network, such as an ISN network, and the local content server LCS is connected to a second network, such as a Wi-Fi direct network. Assume that there is. Accordingly, the client device CD and the intermediate device IMD are connected (step S82), and the client device CD and the local content server LCS are not connected (step S81). The local content server LCS may be a DMS.

The client device CD is provided with an AV service from each device (step: S83). The client device (CD) attempts to connect to a local content server (LCS) while receiving an AV service. The local content server LCS is connected to a Wi-Fi Direct network to which the client device CD is not connected. The position of the client device CD does not know which network the local content server LCS is connected to.

Accordingly, the client device CD may discover the local content server LCS based on multi-network probing (step S84). For example, the client device CD acquires messages transmitted through each network using its own authentication information such as WEP, WPA, credentials, etc., and then obtains a message of the local content server LCS. The discovery information of the local content server (LCS) may be extracted from the acquired message.

Next, the client device CD may join the second network to which the local content server LCS is connected based on the extracted device discovery information (step S85). For example, the client device CD detects the information of the Wi-Fi Direct network to which the local content is connected, for example, the connection type, the basic service set identifier, the P2P group identifier, and the like from the extracted connection device discovery information, and detects the detected information. To join to a Wi-Fi Direct network. On the other hand, the client device CD may release the connection with the intermediate device (step: S86). In other words, the client device CD releases the connection with the ISN.

The client device CD may update the Recently Connected Device List managed by the client device CD using the discovery information of the local content server LCS (step S87). If there is no list of listened connected devices on the client device CD, the client device CD uses the discovery information of the devices collected through multi-network probing, instead of performing step S87. You can create a device list. For example, the client device CD may generate a listened connected device list using discovery information of the local content server LCS. The generated listened connected device list may be continuously updated and managed by the client device (CD).

When the client device CD joins the second network, the client device CD is connected to the second network, and interoperable with the intermediate device IMD through the second network (step S90).

Subsequently, the client device CD connected to the second network may perform multi-network advertising of each device (step S88). For example, a client device (CD) connected to the second network may send an advertising message to the devices of the first network. The advertising message includes discovery information of the client device (CD). The discovery information includes configuration information of the second network. Accordingly, the intermediate device receiving the advertising message may join the second network. Therefore, the client device CD and the intermediate device are in a state capable of interworking through the second network (step S89).

With the client device (CD), content server and intermediate device connected to the second network, the client device (CD) obtains a list of content (or assets) from the local content server (LCS), e. The content may be selected (step S91).

Subsequently, the queue manager 122 of the client device CD may transmit a queue request to the intermediary device IMD requesting to download the selected content from the local content server LCS to the intermediary device (step S92). . The client device (CD) obtains the capability information of the intermediate device (IMD) from the intermediate device (IMD), and through the queue request to download an asset suitable for the intermediate device (IMD) based on the capability information. You can request After receiving the queue request, the intermediate device IMD may download the content from the local content server LCS based on the information included in the queue request (step S93).

As shown in FIG. 12, the client device CD and the local content server LCS are connected to a first network such as an ISN network, and the intermediate device IMD is connected to a second network such as a Wi-Fi direct network. have. Therefore, the client device CD and the intermediate device IMD are not disconnected (step S102), and the client device CD and the local content server LCS are connected through the first network ISN. (Step S101). The local content server LCS may be a DMS. The client device CD is provided with an AV service from the local content server LCS (step S103).

The client device CD may discover the intermediate device IMD based on the multi-network advertising of the intermediate device (step S104). In the multi-network advertising, a device belonging to a specific network transmits an advertising message to networks other than the network.

For example, an intermediate device (IMD) connected to the second network may send an advertising message to the devices of the first network. The client device CD may receive an advertising message of the intermediary device IMD. The advertising message may include configuration information of the Wi-Fi Direct network, which is the second network. The client device CD extracts discovery information of the intermediate device IMD from the received advertising message, and the extracted discovery information may include configuration information of Wi-Fi Direct.

Next, the client device CD may join the second network to which the intermediate device IMD is connected based on the extracted device discovery information (step S105). For example, the client device CD detects the information of the Wi-Fi Direct to which the intermediate device IMD is connected, for example, a connection type, a basic service set identifier, a P2P group identifier, and the like, from the extracted connection device discovery information. The information can be used to join a Wi-Fi Direct network.

The client device CD may update the list of connected devices managed by the client device CD using the discovery information of the intermediate device IMD (step S106). If there is no list of listened connected devices on the client device (CD), instead of performing step S106, the client device (CD) listens using discovery information of devices collected through multi-network advertising. You can create a list of connected devices. For example, the client device CD may generate the listened connected device list using the discovery information of the intermediate device IMD.

When the client device CD joins the second network, the client device CD is connected to the second network, and can interoperate with the intermediate device IMD through the second network (step S109). On the other hand, however, the client device CD is disconnected from the ISN and thus cannot interwork. The client device CD therefore wants to connect the local content server LCS to the second network.

The client device CD may perform multi-network advertising (step S107). For example, a client device (CD) connected to the second network may send an advertising message to the devices of the first network. The advertising message includes discovery information of the client device (CD). The discovery information includes configuration information of the second network. Accordingly, the local content server LCS that receives the advertising message may join the second network. Accordingly, the client device CD and the local content server LCS are in a state capable of interworking through the second network (step S108).

With the client device (CD), content server and intermediate device connected to the second network, the client device (CD) obtains a list of content (or assets) from the local content server (LCS), e. The content may be selected (step S110).

Subsequently, the queue manager 122 of the client device CD may transmit a queue request to the intermediate device IMD requesting to download the selected content from the local content server LCS to the intermediate device (step S111). . The client device (CD) obtains the capability information of the intermediate device (IMD) from the intermediate device (IMD), and through the queue request to download an asset suitable for the intermediate device (IMD) based on the capability information. You can request After receiving the queue request, the intermediate device IMD may download the content from the local content server LCS based on the information included in the queue request (step S112).

Meanwhile, as mentioned above, after disconnecting from the Wi-Fi Direct network, the client device CD may wish to reconnect to the intermediary device IMD or the local content server LCS. In this case, the client device (CD) can quickly connect with the intermediate device or the local content server (LCS) using the listened connected device list.

As described above, the client device CD may automatically perform multi-network discovery for actively or passively discovering devices in the multi-network based on multi-network probing or multi-network advertising. Therefore, it is possible to interwork with devices that are not connected to the client device CD, and based on this, it is possible to easily perform a download request and download of content between devices belonging to heterogeneous networks.

FIG. 13 exemplarily illustrates an embodiment of displaying a device of multiple networks in a client device (CD).

Referring to FIG. 13, as illustrated in FIG. 13A, TV1, TV2, Server 1, and Server 2 exist in a multi-network environment. Further, as shown in 13B, TV1 and Server 2 are connected to a Wi-Fi Direct network having SSIDs of "My2ndNet" and "My3rdNet", respectively. The client device CD is connected to the same network as the TV2 and Server 1 (the Wi-Fi network whose SSID is "My1stNet"), but not to the TV1 and Server 2.

As shown in 13C, conventionally, only the TV2 and Server 1 connected to the same network are displayed in the device list displayed on the client device CD, but the TV1 and Server 2 connected to the other network are not displayed.

In contrast, as shown in 13D, the client device (CD) performing multi-network discovery can display all of TV1, TV2, Server 1, and Server 2 through the device list, and TV1 and Server 2 are connected to any network. It can also indicate whether it is connected.

14 exemplarily illustrates another embodiment of displaying a device of multiple networks in a client device (CD).

Referring to Fig. 14, as shown in 14A, in the device list indicating the devices of the multi-network, the user is connected to TV1 (SSID = "My2ndNet") connected to a network different from the network to which the client device CD is connected. Connected).

Then, as shown in 14B, a window may be displayed asking whether the client device CD connects the client device CD to the network (SSID = "My2ndNet") to which TV1 is connected.

When the user selects "OK" in the window, the client device CD connects to the Wi-Fi Direct network connected to TV1, and disconnects from the Wi-Fi Direct network whose SSID is "My1stNet". Thus, as shown in 14C, TV1 is displayed as the same network, and TV2, Server 1, and Server 2 indicate that SSIDs are connected to "My1stNet", "My1stNet", and "My3rdNet", respectively.

As shown in FIG. 15, a device for performing multi-network probing is connected to network A (step S121). If there is no request from the user for the preset period T, the device stores the access and authentication information of network A (step S122). Subsequently, the device determines whether there is other available access and authentication information (step S123), if any, creates a listened connected device list of accessible networks (step S124), and disconnects from network A. (Step S125).

Subsequently, the device may connect with one network in the listened connected device list (step S126), and perform discovery of a device of the connected network (step S127). If the network is not available (Not available), the device deletes the network from the listened connected device list (step: S12), and disconnects from the network (step: S129). .

Subsequently, the device determines whether another network remains in the listened-to-connected device list (step S130), and if another network remains, the device transitions to step S126, and if not, the network A and After connection (step: S131), device discovery in network A may be performed (step: S132).

As shown in FIG. 16, a device to perform multi-network advertising is connected to a specific network (step S130). When the procedure starts, the device may multicast the Bye-bye message to all connected networks (step S131). Subsequently, the device determines whether there is other available access and authentication information (step S132), and if so, creates a listened connected device list of accessible networks (step S124).

The device connects to one of the networks in the listened-to-connected device list (step S134) and multicasts the by-by message to a device in the network (step S135). The device deletes the network from the listened connected device list (step S136) and releases the connection with the network (step S137). Subsequently, the device may determine whether another network remains in the listened-to-connected device list (step S138), and if another network remains, proceed to step S134, and if not, end the operation ( Step: S139).

As illustrated in FIG. 17, the client device CD may transmit a content download request to the cloud service server CSS (S141). The content download request may be a request for downloading content from a source to the first intermediate device IMD1 and transmitting the downloaded content to the client device CD.

The content download request may include, for example, a source URI and download / wake up time information. Here, the download time may be a downloadable time set by a user or an application, and the wake up time information may be a time for waking up the first intermediate device IMD1 in the sleep mode to perform a download.

Upon receiving the content download request, the cloud service server CSS may transmit a confirmation message in response to the content download request to the client device CD (S142). The client device CD receiving the confirmation message may enter a sleep mode to reduce power consumption. The cloud service server (CSS) may pre-download an asset of the content to be downloaded from the source URI based on the content download request.

The cloud service server CSS may transmit a wake-up request to the first intermediate device IMD1 (S143). Upon receiving the wake-up request, the intermediate device IMD1 may perform a wake-up in response to the wake-up request to switch from the sleep mode to the active mode. In operation S144, the first intermediate device IMD1 may transmit a confirmation message in response to the wakeup request to the cloud service.

The cloud service server CSS receiving the confirmation message may transmit the requested content to the first intermediate device IMD1 (S145). For example, the cloud service server CSS may push the content to the first intermediate device IMD1. Accordingly, the first intermediate device IMD1 may download the content and may enter the sleep state when the download is completed.

The client device CD wakes up to an active state to perform Wi-Fi Direct, and transmits a content download request to the first intermediate device IMD1 through Wi-Fi Direct (S146). The first intermediate device IMD1 receiving the download request may download the content downloaded from the cloud service server CSS to the client device CD.

Hereinafter, the aforementioned items of device capability will be described in detail. Device Capability includes Device ID, Device Name, Device Friendly Name, User Identifier, Current Power Source, Charging Status , Power Level, Supporting Media Profiles, Supporting Codec Types, Storage Capacity, Storage Function Groups, Point Nodes, Storage Usage, Maximum Size of Queue Request, Maximum Number of Queue Request, Current Number of Queue Request, Network of Entries Such as Network Interface Number of Entries, Network Access Type, Media Transport, Bandwidth Limit, etc. May include a capability item (Item).

The device identifier may mean an identifier that uniquely identifies the device globally. The value of the device identifier may be string type information. The device name may mean a universally-unique identifier for a device. The value of the device name may be, for example, information in the form of a string. The device friendly name is a short description for an end user, and the value may be string type information. The user identifier is an identifier for identifying the end user, and the value of the user identifier may be string type information.

The current power source is a description of the current power source of the device, the value of which may be a string. The value of the current power source may be set to, for example, "AC Power" which means that the device is supplied with AC power, "batter" which means that the device is powered from the battery. Assuming the device is powered from an AC source, the value of the current power source can be set to 'AC Power.' If the device is powered from a battery, the value of the current power source is 'battery' Can be set to '.

The charging status is a capability item indicating the current state of charge of the battery, the value of which may be string information. The value of the charging status is 'Available' which means that the battery is installed in the device and the installed battery is currently working, and 'Charging' which means that the battery is installed and charging in the device. It may be set to 'Unavailable' which means that the battery is not installed, or 'Error' which indicates that the battery is installed in the device but fails to function correctly.

The power level may represent the current power level of the battery. For example, the value of the power level may be a percentage value. For example, '0' may mean that the battery is completely discharged or no battery is installed. '100' may mean that the battery is fully charged.

The supporting media profile may indicate a supportable media profile type. The value of the supporting media profile is string type information such as 'HD' for high definition (HD), 'SD' for standard definition (SD), and portable definition (PD). It may be set to 'PD' which means.

The supporting codec type is a list of supported codec types, and a value thereof may be string type information. The storage capacity may represent an available amount of storage.

The storage functional group represents a function group associated with storage of a device, for example, a virtual storage device, and a value thereof may be string type information. The value of the functional group may be 'Access Control', 'Capacity Management', 'Expiration', 'Transformation', 'Playlist' and the like.

The 'access control' represents an access control functional group that mediates between different applications using the virtual storage device. The access control functional group may, for example, block a particular application from accessing content associated with another application.

The 'capacity management' may refer to a capacity management function group that allows a virtual storage device to manage its storage space based on priority. The capacity management group may discard the lower priority asset, for example, if an asset with a higher priority is downloaded, to make room for the higher priority asset.

The 'expiration' may indicate an expiration function group for allowing the virtual storage device to store content based on a specific date range. The 'Transformation' may refer to a transform function group that allows a transform operation while reading or writing content from the virtual storage device.

The 'Playlist' may represent a playlist functional group that enables the virtual storage device to process the playlist. If there is a playlist function group, the playlist can be used for group objects.

The storage usage may indicate the total amount of storage currently available. The value of the storage notice may be a percentage value. For example, if the value of the storage notice is '0', it means that the storage is completely empty (Completely Unoccupied), '100' may mean that the storage is completely occupied (Fully Occupied).

Maximum Size of Queue Request, Maximum Number of Queue Request, Current Number of Queue Request, and Network Interface Number of Entries Entries may indicate the maximum size of the queue request, the total number of queue requests that can be submitted during a given time, the number of current queue requests other than the complete state, and the number of network interfaces.

The network access type may indicate an available network access interface type. The value of the network access type may be string information. The value of the network access type may be, for example, 'Ethernet', '801.11', 'Bluetooth', '3G' or 'WiMAX'.

The media transport may indicate a supported transport protocol type for D3, D4, and D1 interfaces. The value of the media transport may be, for example, 'HTTP', 'RTP', and the like. The bandwidth limit may represent the available bandwidth of the network interface.

Although the present invention has been described above by way of example, those skilled in the art will variously modify and change the present invention without departing from the technical matters and scope of the present invention as set forth in the claims below. It will be understood that it can be done. Accordingly, modifications to future embodiments of the present invention will not depart from the technology of the present invention.

Claims

Performed by a first device connected to the first network,

Discovering a second device of a second network based on one of multi-network probing and multi-network advertising;

Joining to the second network based on the discovery information of the second device; And

Updating a listened connected device list using the discovery information of the second device.
The method of claim 1, wherein the second network is a Wi-Fi direct network.
The method of claim 1, wherein the discovery information includes device identification information, a connection type, a basic service set identifier (BSSID), a service set identifier (SSID), a P2P group identifier (P2P group identifier), Device discovery method in a multiple network, characterized in that it comprises at least one of a security type, security key, IP address, port.
The method of claim 1, wherein the multi-network probing,

Sequentially probing a plurality of networks corresponding to a plurality of pieces of authentication information of the first device;

The multi-network advertising includes receiving advertising messages from a plurality of devices connected to a plurality of networks, respectively.
The method of claim 1, wherein the discovering of the second device comprises:

Acquiring a message sent from the second device by probing multiple networks; And

Extracting discovery information of the second device from the obtained message.
The method of claim 1, wherein the discovering of the second device comprises:

Receiving an advertising message from the second device; And

Extracting discovery information of the second device from the received advertising message.
The method of claim 1, wherein joining to the second network comprises:

Detecting information of a second network to which the second device is connected from discovery information of the second device; And

Joining to the detected second network.
The method of claim 1, further comprising: disconnecting from the second device; And

Connecting to the second device connected to the second network based on the updated listened connected device list.
storage; And

Connected to a first network, discovering a target device of a second network based on one of multi-network probing and multi-network advertising, and joining to the second network based on discovery information of the target device And a device manager for updating a list of listened connected devices stored in the storage by using the discovery information of the target device.
10. The device discovery apparatus of claim 9, wherein the second network is a Wi-Fi direct network.
The method of claim 9, wherein the discovery information includes device identification information, connection type, basic service set identifier (BSSID), service set identifier (SSID), P2P group identifier (P2P group identifier), Device discovery apparatus in a multi-network comprising at least one of a security type, security key, IP address, port.
Performed by a first device connected to the first network,

Discovering a second device of a second network based on one of multi-network probing and multi-network advertising;

Joining to the second network based on the discovery information of the second device; And

And transmitting, via the second network, a queue request to the second device requesting the download of content from a source to the second device.
The method of claim 12, wherein the second network is a Wi-Fi direct network.
The method of claim 12, wherein the discovery information includes device identification information, connection type, basic service set identifier (BSSID), service set identifier (SSID), P2P group identifier (P2P group identifier), And at least one of a security type, a security key, an IP address, and a port.
The method of claim 12, wherein the multi-network probing,

Sequentially probing a plurality of networks corresponding to a plurality of pieces of authentication information of the first device;

The multi-network advertising includes receiving an advertising message from a plurality of devices connected to a plurality of networks, respectively.
The method of claim 12, wherein the discovering of the second device comprises:

Acquiring a message sent from the second device by probing multiple networks; And

Extracting discovery information of the second device from the obtained message.
The method of claim 12, wherein the discovering of the second device comprises:

Receiving an advertising message from the second device; And

Extracting discovery information of the second device from the received advertising message.
13. The method of claim 12, further comprising: updating a listened connected device list using discovery information of the second device;

Disconnecting from the second device; And

Connecting to the second device connected to the second network based on the updated listened connected device list.
Connected to a first network, discovering a second device of a second network based on one of multi-network probing and multi-network advertising, and based on discovery information of the second device, the second network A device manager for joining; And

And a queue manager for transmitting a queue request to the second device requesting to download content from a source to the second device via the second network.
A first device connected to the first network; And

A second device connected to a second network,

The first device,

Discovering the second device based on one of multi-network probing and multi-network advertising, joining to the second network based on discovery information of the second device, and content to the second device Send a queue request to request the download of,

The second device,

In response to the queue request, download the content from a source to the second device.