JP6465324B2 - Method and device for transmitting content - Google Patents

Description

  The present disclosure relates to data processing, and more specifically to methods and devices for transmitting content.

  Over-the-top (OTT) content refers to the distribution of video, audio, and other media over the Internet where multiple system operators are not involved in the control and distribution of content. Internet service providers (ISPs) may know the content of Internet protocol packets, but are not involved in them and may control content viewing capabilities, copyrights, and other redistribution. Can not. This is in contrast to the purchase or rental of video or audio content from Internet service providers, such as, for example, AT & T U-Verse, on-demand pay TV broadcast service or IPTV video service. OTT refers specifically to content received from third parties, such as, for example, NowTV, Netflix, WhereverTV, NetD, Hulu, Crackle, WWE Network, RPI TV or myTV, and ISPs are only responsible for carrying IP packets. However, it is delivered to the end user. According to the versatility of OTT boxes and television receivers with embedded OTT box functionality, more and more people are using online OTT boxes / videos on their home TV via OTT boxes instead of PCs, tablets and smartphones. I want to see a movie. A user who dynamically switches playback or playback of content from one rendering device to another, for example, from a living room TV to a bedroom TV, or from a tablet / smartphone to a living room TV. A request exists.

There are several existing technologies that allow content playback to be switched between two devices, including AirPlay, Miracast, DLNA® (Digital Living Network Alliance), and the like. However, those Internet-based online media playback applications have some limitations:
1) AirPlay: When switching the content being played from the client to AirPlay (eg, AppleTV), the client sends the content URL and the current playback position on the playback axis of the content to AppleTV. In response, AppleTV sets up a new connection to the content server by submitting a request with the content URL and sending it to the content server, and then locates the specified playback location. Since the connection to the content server needs to be reestablished, the server considers the connection as a new client request. Thus, the server again performs some repetitive actions performed during the previous playback progress. For example, AppleTV plays the advertising video clip again. Other operations include an authentication process. It adversely affects the user experience.

  2) Miracast: The device that is playing the content acts as the source device. It encodes local videos and sends them over a WiFi-Direct connection to the selected target device. When the source device supplies the encoded video to the target device, the source device cannot leave or terminate its connection with the content server.

  3) DLNA: It requests the content server to host them for streaming content. In an online media playback scenario on the Internet, it is impossible for a content server in the Internet to be a DLNA DSM (Digital Media Server) compatible device.

  Accordingly, a method and apparatus for transmitting media content from a rendering device to other selected rendering devices during playback of the media content without degrading the user's viewing experience is desired.

  In accordance with an aspect of the present disclosure, it is a method of transmitting content at a content server and an intermediate device (eg, a gateway) that connects to at least two rendering devices, the content directed from the first rendering device to the content server A first connection between the first rendering device and the intermediate device, and a second connection between the intermediate device and the content server; and Sending data of the content received via the first rendering device via the first connection; receiving a request for the content directed to the content server from a second rendering device; The intermediate device and the second label Establishing a third connection with a dalling device; and receiving data of the content using the second connection and sending the data to the second rendering device via the third connection. Provide a method.

  In accordance with another aspect of the present disclosure, it is a device that connects a content server and at least two rendering devices and transmits content from the content server, the transceiver receiving and transmitting data, and the transceiver A request for content destined to the content server is received from one rendering device and a first connection between the first rendering device and the device and a second connection between the device and the content server are established And sending the content data received via the second connection by the transceiver to the first rendering device via the first connection, and from the second rendering device to the content server by the transceiver. Aiming Receiving the content request, establishing a third connection between the device and the second rendering device, receiving the content data using the second connection, and passing the data to the second rendering device. And a processor for sending via the third connection.

  It is to be understood that further aspects and advantages of the present disclosure can be found in the following detailed description of the present disclosure.

The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this application, and represent an embodiment of the invention described by the specification. used. The present invention is not limited to the embodiment.
1 is a block diagram illustrating a system for transmitting media or video content in accordance with an embodiment of the present disclosure. FIG. 5 is a flowchart illustrating a method for transmitting content according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating a TCP connection that carries content from a content server 101 to a rendering device A103 according to an embodiment of the present disclosure. FIG. 4 illustrates a portion of an on-screen menu according to an embodiment of the present disclosure. 5 is a flowchart illustrating an implementation of a method for transmitting content according to an embodiment of the present disclosure. FIG. 6 illustrates a connection according to an embodiment of the present disclosure.

  Embodiments of the invention will now be described in detail in conjunction with the drawings. In the following description, some detailed descriptions of known functions and configurations may be omitted for clarity and brevity.

  FIG. 1 is a block diagram illustrating a system for transmitting media or video content in accordance with an embodiment of the present disclosure. The system has a content server 101, a gateway 102, and two or more rendering devices 103 and 104 (the figure only shows two rendering devices).

  The content server 101 provides content (eg, video or audio) via a gateway 102 to one or more rendering devices in a data packet. In one example, the content server 101 is a server in the Internet.

  The gateway 102 is an intermediate device between the content server 101 and the rendering device. In one example, it is at the user end, eg, in the user's home and is a router. In order to achieve the objectives of this disclosure, proxy functions need to be supported or implemented at the gateway 102. The gateway 102 needs to be able to automatically recognize the transfer protocol or transfer message and then apply an application proxy for the protocol / message to establish a connection between the rendering device and the content server 101 There is. Since many content servers on the Internet typically use the HTTP protocol to transfer video / audio content to end users at home, the application proxy is an HTTP proxy in the context of the Internet.

  Rendering devices 103 and 104 are used to send requests for media content (eg, video or audio) to the content server 101, request transfer of data sessions, receive media content from the content server, and display it. . They take one of the forms including Internet, TV, TV with Internet set top box, tablet, PC and laptop, and so on.

  In the prior art, if a user wants to transfer a data session of media content between rendering devices, i.e., the user wants to view the content on rendering device B when the user is viewing the content on rendering device A, A new connection between the rendering device B and the content server is established, and the connection between the rendering device A is terminated. However, since the content server needs to assign a new network socket address that is a combination of the IP address and port number in the Internet protocol, the connection to the rendering device B is considered a new connection.

  However, in this embodiment, two TCP connections are established between the two endpoints of the rendering device and the content server 101. That is, one TCP connection is established between the rendering device and the gateway 102, and the other TCP connection is established between the gateway 102 and the content server 101. It should be noted here that we can also use a UDP connection. When transferring a data session of a media stream carrying media content from rendering device A 103 to rendering device B 104, the TCP connection between gateway 102 and server 101 remains unchanged, and the new connection between rendering device B 104 and gateway 102 The TCP connection is set up and the TCP connection between the rendering device A 103 and the gateway 102 is released. The gateway 102 automatically forwards the data packet of the data session for the requested media content to a rendering device B 104 other than device A. Here, “forward” corresponds to the IP address and port number of the source device and the connection between the gateway and the rendering device B without changing the payload data for the received data packet. This means changing the IP address and port number of the destination device. In addition, rendering device A 103 sends its currently playing context to rendering device B 104 so that rendering device B 104 has the same context for playing media content.

  FIG. 2 is a flowchart illustrating a method for transmitting content according to an embodiment of the present disclosure.

In step 201, the rendering device A 103 sends a request for the selected content to the content server 101. The request includes the URL of the selected content. When rendering device A sends a request for media content to content server 101 via gateway 102, two TCP connections are separate between content server 101 and gateway 102 and between gateway 102 and rendering device A. Established. FIG. 3 is a diagram showing a TCP connection for carrying content from the content server 101 to the rendering device A103. During connection establishment, the gateway 102 records proxy data locally (in memory or local storage), eg, data used to identify the two connections. In one example, it stores the following information:
A. IP address and port number of the rendering device: they combine to uniquely correspond to the media rendering / playback application running on the rendering device;
B. IP address and port number of the gateway for connecting with the rendering application in the rendering device;
C. D. IP address and port number of the gateway for connecting to the content server; URL (Uniform Resource Locator) of the requested media content. Those skilled in the art can use location indicators that uniquely identify the location of the requested media content, such as, for example, the absolute path (or relative path) and file name of the requested media content. You should notice a point.

  In step 202, the rendering device A 103 receives the requested content data stream in the form of data packets from the content server 101 via the gateway 102.

  If the user desires to transfer a data stream from rendering device A 103 to rendering device B 104 at step 203, the user can select rendering device B 104 as the destination device from an on-screen menu on rendering device A. Rendering device A initiates the process of transferring the data stream from rendering device A to rendering device B. FIG. 4 is a diagram illustrating a portion of an on-screen menu according to an embodiment of the present disclosure. As can be seen from FIG. 4, a submenu “rendering device B” exists under the menu “transfer to”. It should be noted that if there are additional rendering devices available for content transfer, those rendering devices will be listed under the menu “Destination”. It should also be noted that the submenu can be manually configured (including IP address) or automatically implemented. As for automatic implementation, it can be recognized by using UPnP (Universal Plug and Play). When rendering device B 104 is selected, rendering device A 103 sends instructions to gateway and rendering device B separately. FIG. 5 is a flowchart illustrating an implementation of a method for transmitting content in accordance with an embodiment of the present disclosure.

In step 501, rendering device A sends a message to the gateway to instruct the gateway to prepare for content transfer. The message is:
A. The IP address and port number of the current rendering device, ie, rendering device A;
B. The URL of the requested media content; It has the IP address of the target rendering device, ie, rendering device B.

  On the gateway side, it prepares to receive this switch message from rendering device A and wait to process a request for this URL from rendering device B. Specifically, the gateway generates one precheck item including the IP address and URL of the rendering device B. After the preparation is completed, the gateway sends a response message indicating that the preparation is completed to the rendering device A.

  In step 502, rendering device A receives a response message from the gateway indicating that it is ready.

In step 503, rendering device A sends a message to rendering device B to cause rendering device B to continue playing the requested content. The message is used to instruct rendering device B to transfer the data session to rendering device B. And the message has:
A. One or more rendering context parameters, eg playback progress (time), status (eg pause or play), volume, media format (eg FLV, MOV, HTML5, etc.), session information (eg current Cookies and session IDs of active HTTP media content transmission sessions, and related server and client side description information applied in the session, and media playback status (eg, location and volume), and authentication information, if any (Eg, passwords, tokens or certificates used to interact with the media server and decrypt the media content), etc. This information can cause rendering device B to initialize the context for the rendering application at rendering device B to continue playing the requested content from the location indicated by the playback progress parameter. In the example, the rendering context parameter includes only the playback progress that indicates the current playback position when rendering device A receives an instruction to transfer the data stream from rendering device A to rendering device B.

  B. URL. It tells the rendering device B to use it to retrieve media content for playback.

  In step 504, rendering device B receives a message from rendering device A. Upon receiving the message, the rendering device B sends a request including the URL to the content server.

  In step 505, the gateway receives the request from rendering device B and determines whether it matches the generated precheck item. Specifically, the gateway includes whether the packet is derived from the IP address included in the precheck item (that is, the IP address of the rendering device B), and the URL included in the request is included in the precheck item. Whether the URL is the same as the current URL. If the result is negative, the gateway establishes a new Internet side connection to the content server for the URL and sends a request to the content server over the connection. Here, the connection can be used later to carry the media content. In other examples, the gateway sends the request without establishing a connection. If the content server accepts the request, a connection is established to carry the media content. If the result is positive, the gateway terminates or abandons the request, applies the application proxy, and first sets up the rendering side connection to rendering device B. This connection is usually a TCP connection. Here, in other words, after rendering device B sends a request to the content server, rendering device B establishes a connection to the gateway. Meanwhile, the gateway application proxy sets up an Internet side connection for this URL request from rendering device B. Instead of configuring a new internet side connection between the gateway and the content server for this particular requested content, the gateway uses the existing internet side connection of the URL for rendering device A in the first place. . Specifically, after the connection between the rendering device B and the gateway is established, the rendering device B initializes the rendering context of the rendering device B. With regard to the initialization of the rendering context, it has the operations of adjusting the volume, searching for the playback position indicated by the playback progress parameter, and so on. Specifically, during initialization, rendering device B reuses the context parameters received from original rendering device A, eg, session information, security and authentication information, and these are established from rendering device B. Applies to “new” sessions to be used, reuses authentication information when interacting with content servers, and decrypts media data. When the rendering device B sends a request message to the content server to search for the playback position when the content playback is switched, the request message is sent between the rendering device B and the gateway and between the gateway and the content server. Sent to the content server via the connection. The content server receives the request message as if the request message came from the original rendering device A, and sends the requested content to the rendering device B from the playback point. Here, the data packet sent from the rendering device B to the content server is sent by the application proxy to the content server through this existing Internet side connection. The data packet of the requested content sent from the content server is sent to the rendering device B instead of the rendering device A. Further, after the connection between rendering device B and the gateway is established, the gateway uses the stored IP address and port number of rendering device A to render the previous rendering side to rendering device A, for example. Break or release the connection. FIG. 6 is a diagram illustrating a connection according to an embodiment of the present disclosure.

  For content servers on the Internet, the playback switching / transfer process is transparent to the content server. Since the connection socket for the requested content is still the same (IP address and port number) at the content server side and at the gateway side, the content server is unaware that the home side rendering device will change.

  In this way, Internet content playback can be switched smoothly from rendering device A to rendering device B without interruption.

  Those skilled in the art will know that content is not limited to media content. The content should include data such as online games.

  The following shows the application of the present invention.

  1. The user selects an Internet movie and clicks to play it on rendering device A. The first 30 seconds before the movie content has embedded non-skippable advertisements.

  2. After watching for a short time (eg, 20 minutes), the user decides to switch the playback progress to the rendering device B in the living room. Of course, the user does not want to wait again for the first embedded 30 second advertisement.

  3. The user selects the found rendering device B as a switching target with the rendering device A, and clicks the switching button.

  4). The Internet movie is played on the rendering device B continuously from the time when playback is switched, without taking in the playback of the advertisement embedded first.

  This embodiment proposes a new solution that supports the requirement to dynamically switch the playback progress of video based on the Internet between rendering devices. On the other hand, the solution not only allows the user to switch Internet content playback from one device to another, but also allows the user to review advertisements that are inserted before the movie starts, for example. Or the original playback device still needs to operate as an encoding and transfer source.

  The following introduces alternative embodiments of the present disclosure.

  It is a method for transmitting content, which is an intermediate device (eg, a gateway) connecting a content server and at least two rendering devices, from the first rendering device to the content server, including a location indicator for the content Receiving the requested request for the content; establishing a first connection between the first rendering device and the intermediate device; and a second connection between the intermediate device and the content server; Sending the content data received via a second connection to the first rendering device via the first connection; and including a location indicator for the content from the second rendering device. Receiving a request for the content directed to a server, establishing a third connection between the intermediate device and the second rendering device, receiving the content data using the second connection, Sending the data to the second rendering device via the third connection.

  In addition, as an improvement, prior to receiving the request from the second rendering device, the method further comprises receiving a message from the first rendering device including a location indicator and a target rendering device indicator, Prior to establishing a third connection, the method determines whether a request from the second rendering device matches a location indicator and an IP address of the target rendering device included in the message; If the determination result is affirmative, establishing the third connection; and receiving the data of the content using the second connection and passing the data to the second rendering device via the third connection. Step to proceed to send Further comprising a door.

  In addition, as an improvement, the method further comprises the step of sending a request from the second rendering device to the content server if the determination result is negative.

  In addition, as an improvement, the determining step determines whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and the location included in the request. The method further comprises determining whether an indicator is the same as the location indicator included in the message sent by the first rendering device.

  In addition, as an improvement, the method further comprises releasing the first connection between the first rendering device and the intermediate device after establishing the third connection.

  In addition, as an improvement, the message sent by the first rendering device further includes an IP address and port number of the first rendering device corresponding to the first connection, and the releasing step includes the first connection. Further using the IP address and port number of the first rendering device to release the

  It is also a computer program product recorded on a computer-readable medium downloadable from a communication network and / or executable by a processor, for carrying out the method steps described above. A computer program product having program code instructions is provided.

  It also provides a non-transitory computer readable medium having recorded thereon a computer program product that can be executed by a processor, including program code instructions for performing the method steps described above.

  It is also a device for transmitting content from a content server, the transceiver connecting the content server and at least two rendering devices, a transceiver for receiving and transmitting data, and by the transceiver, from the first rendering device, Receiving a request for the content directed to the content server, including a location indicator for the content; a first connection between the first rendering device and the device; and a first connection between the device and the content server. Two connections are established, and the transceiver transmits the content data received via the second connection to the first rendering device via the first connection, and the transceiver causes the second render A request for the content directed to the content server, including a location indicator for the content from a mobile device, establishing a third connection between the device and the second rendering device, and And a processor for receiving the content data and sending the data to the second rendering device via the third connection. Here, the transceiver is implemented in hardware (eg, a wired network interface (eg, RJ45) or a wireless network interface (eg, Wi-Fi)).

  In addition, as an improvement, prior to receiving a request from the second rendering device, the processor receives a message from the first rendering device via the transceiver that includes a location indicator and a target rendering device indicator, and the third connection. Is determined if the request from the second rendering device matches the location indicator included in the message and the IP address of the target rendering device, and if the determination is positive, It is further used to establish the third connection, receive data of the content using the second connection and proceed to send the data to the second rendering device via the third connection.

  In addition, as an improvement, the processor is further used to send a request from the second rendering device to the content server if the determination result is negative.

  In addition, as an improvement, the processor determines whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and the location indicator containing the request is It is further used to determine if it is the same as the location indicator included in the message sent by the first rendering device.

  In addition, as an improvement, the processor is further used to release the first connection between the first rendering device and the device after establishing the third connection.

  In addition, as an improvement, the message sent by the first rendering device further includes an IP address and port number of the first rendering device corresponding to the first connection, and the processor releases the first connection. Is further used to use the IP address and port number of the first rendering device.

A number of implementations have been described. It will nevertheless be understood that various changes may be made. For example, elements of different implementations may be combined, replaced, changed, or deleted to produce other implementations. In addition, those skilled in the art will appreciate that other structures and processes may be substituted for those disclosed, and that the resulting implementation will achieve at least substantially the same results as the disclosed implementation. It will be understood that at least substantially the same function is performed in the same way. However, these and other implementations are contemplated by this application and are within the scope of the invention as defined by the appended claims.
In addition to the above embodiment, the following supplementary notes are disclosed.
(Appendix 1)
A method for transmitting content at an intermediate device connected to a content server and at least two rendering devices, comprising:
Receiving a request for content directed to the content server from a first rendering device;
Establishing a first connection between the first rendering device and the intermediate device, and a second connection between the intermediate device and the content server;
Sending the content data received via the second connection to the first rendering device via the first connection;
Receiving a request for the content directed to the content server from a second rendering device;
Establishing a third connection between the intermediate device and the second rendering device;
Receiving data of the content using the second connection and sending the data to the second rendering device via the third connection;
Having a method.
(Appendix 2)
Prior to receiving a request from the second rendering device, the method receives a message from the first rendering device that includes a location indicator and a target rendering device indicator for the content that the first rendering device is receiving. Further comprising
Before the request from the second rendering device includes a location indicator for content and establishing the third connection, the method includes:
Determining whether a request from the second rendering device matches a location indicator and an IP address of a target rendering device included in the message;
If the determination result is positive, the third connection is established, the content data is received using the second connection, and the data is sent to the second rendering device via the third connection. To move on
The method according to appendix 1, further comprising:
(Appendix 3)
If the determination result is negative, the method further includes sending a request from the second rendering device to the content server.
The method according to appendix 2.
(Appendix 4)
The determining determines whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and a location indicator included in the request is sent by the first rendering device. Further comprising determining whether the location indicator included in the received message is the same.
The method according to appendix 2.
(Appendix 5)
After establishing the third connection, the method further comprises releasing the first connection between the first rendering device and the intermediate device.
The method according to appendix 2.
(Appendix 6)
The message sent by the first rendering device further comprises an IP address and port number of the first rendering device corresponding to the first connection;
Said releasing further comprises releasing said first connection using an IP address and port number of said first rendering device;
The method according to appendix 5.
(Appendix 7)
A device that connects to a content server and at least two rendering devices and transmits content from the content server,
A transceiver for receiving and transmitting data;
The transceiver receives a request for content destined for the content server from a first rendering device, a first connection between the first rendering device and the device, and between the device and the content server. Establishing a second connection, sending data of the content received via the second connection by the transceiver to the first rendering device via the first connection, and from the second rendering device by the transceiver Receiving a request for the content directed to the content server, establishing a third connection between the device and the second rendering device, receiving the content data using the second connection, To the second rendering device And a processor to send it via a connection
Having a device.
(Appendix 8)
The request from the second rendering device includes a location indicator for content;
The processor is
Prior to receiving a request from the second rendering device, the transceiver receives a message from the first rendering device that includes a location indicator and a target rendering device indicator for the content that the first rendering device is receiving,
Before establishing the third connection, it is determined whether the request from the second rendering device matches the location indicator included in the message and the IP address of the target rendering device, and the determination result is positive. If there is, proceed to establishing the third connection, receiving the data of the content using the second connection, and sending the data to the second rendering device via the third connection.
The device according to appendix 7, further used for:
(Appendix 9)
The processor is further used to send a request from the second rendering device to the content server if the determination result is negative.
The device according to appendix 8.
(Appendix 10)
The processor determines whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and a location indicator included in the request is sent by the first rendering device. Further used to determine if the location indicator contained in the message is the same.
The device according to appendix 8.
(Appendix 11)
The processor is further used to release the first connection between the first rendering device and the device after establishing the third connection.
The device according to appendix 8.
(Appendix 12)
The message sent by the first rendering device further comprises an IP address and port number of the first rendering device corresponding to the first connection;
The processor is further used to release the first connection using the IP address and port number of the first rendering device.
The device according to appendix 11.

Claims (14)

A method for transmitting content at an intermediate device connected to a content server and at least two rendering devices, comprising:
Receiving from the first rendering device a request for the content directed to the content server, including an identifier of the content;
Establishing a first connection between the first rendering device and the intermediate device, and a second connection between the intermediate device and the content server;
Sending the content data received via the second connection to the first rendering device via the first connection;
Receiving from the first rendering device a message including an identifier of the content and a target rendering device indicator indicating the target rendering device;
The second rendering device, and include an identifier, receiving a request directed to the content server,
The identifier included in the request from the second rendering device is the same as the identifier of the content in the message received from the first rendering device, and the second rendering device is the first rendering device Establishing a third connection between the intermediate device and the second rendering device upon determining that it is the same as the target rendering device in the message received from;
Receiving the data of the content using the second connection and sending the data to the second rendering device via the third connection. The content identifier is a location indicator for the content.
The method of claim 1. Determining that the identifier included in the request from the second rendering device and the second rendering device are not the same as the identifier of the content and the target rendering device in the message received from the first rendering device; The method of claim 1, further comprising sending a request from a second rendering device to the content server. Determining whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and a location indicator included in the request is sent to the message sent by the first rendering device; Further comprising determining if the location indicator is the same as included.
The method of claim 2. After establishing the third connection, the method further comprises releasing the first connection between the first rendering device and the intermediate device.
The method of claim 1. The message sent by the first rendering device further comprises an IP address and port number of the first rendering device corresponding to the first connection;
Said releasing further comprises releasing said first connection using an IP address and port number of said first rendering device;
The method of claim 5. A device that connects to a content server and at least two rendering devices and transmits content from the content server,
A transceiver for receiving and transmitting data;
The transceiver receives from the first rendering device a request for the content directed to the content server, including a content identifier, and a first connection between the first rendering device and the device, and the device Establishing a second connection with the content server and sending data of the content received via the second connection to the first rendering device via the first connection by the transceiver; Receiving from the first rendering device a message including an identifier of the content and a target rendering device indicator indicating the target rendering device and including the identifier from the second rendering device by the transceiver. Receives requests directed to Tsusaba, identifier included in the request from the second rendering device is the same as the identifier of the content in the said message first received from the rendering device, and the second Determining that the second rendering device is the same as the target rendering device in the message received from the first rendering device, establishing a third connection between the device and the second rendering device; A processor that receives data of the content using a second connection and sends the data to the second rendering device via the third connection. The content identifier is a location indicator for the content.
The device according to claim 7. The processor determines that the identifier included in the request from the second rendering device and the second rendering device are not the same as the identifier of the content and the target rendering device in the message received from the first rendering device. Once determined, it is further used to send a request from the second rendering device to the content server.
The device according to claim 7 . The processor determines whether the second rendering device sending the request is the same as indicated by the target rendering device indicator, and a location indicator included in the request is sent by the first rendering device. Further used to determine if the location indicator contained in the message is the same.
The device of claim 8. The processor is further used to release the first connection between the first rendering device and the device after establishing the third connection.
The device according to claim 7. The message sent by the first rendering device further comprises an IP address and port number of the first rendering device corresponding to the first connection;
The processor is further used to release the first connection using the IP address and port number of the first rendering device.
The device of claim 11.   A computer program having program code instructions executed by a processor to implement the method of any one of claims 1-5. Computer readable storage medium storing a computer program comprising program code instructions for execution by a processor to implement the method as claimed in any one of 請 Motomeko 1 to 5.

Images