WO2023040419A1 - Display device and content continuing method - Google Patents

Abstract

A display device (200) and a content continuing method. The display device (200) comprises: a display (260), configured to present content; and a controller (250) configured to: receive a continuing request from a pushing device, wherein the continuing request comprises information related to an application of the pushing device and playback information provided by the application of the pushing device and related to target content to request to present the target content; determine a target application on the display device (200) according to the information related to the application of the pushing device, wherein the target application is an application having a highest degree of matching with the application of the pushing device or an application specified by a user; and start the target application, and control the target application to present the target content according to the playback information related to the target content.

Description

Display device and content connection method

Cross References to Related Applications

This application requires that the application number submitted on September 26, 2021 is 202111139380.3, the application number submitted on September 26, 2021 is 202111139401.1, the application number submitted on September 26, 2021 is 202111131349.5, and the application number submitted on September 26, 2021 is 202111131349.5. The priority of the Chinese patent application with the application number 202111097923.X filed on the 18th, the application number 202111128526.4 filed on September 26, 2021, and the Chinese patent application number 202111151401.3 filed on September 29, 2021, all of which are adopted References are incorporated in this application.

technical field

The present application relates to the technical field of display devices, and in particular to a display device and a content connection method.

Background technique

Display devices, such as smart TVs, smart screens, etc., can provide users with audio, video, and picture playback screens, such as online video programs and live TV programs. In addition, they can also provide users with information such as online games, AI fitness, Various applications and services such as online education.

In some scenarios, such as a home, there are usually multiple terminal devices, such as smart TVs, refrigerator smart screens, and smart speakers. These terminal devices can communicate with each other, and can also communicate with terminal devices outside the scene based on the WAN. Wherein, each terminal device can present content for the user, and the content includes but not limited to music, video, call, text, picture and so on. How to realize sharing and replaying of content between devices to improve user experience has become an urgent technical problem to be solved.

Contents of the invention

An embodiment of the present application provides a display device, including: a display for presenting content; and a controller configured to: receive a relay request from a push device, where the relay request includes a connection with the push device Application-related information and the playback information related to the target content provided by the application of the push-end device to request presentation of the target content; determine the target application on the display device according to the information related to the application of the push-end device , the target application is the application with the highest degree of matching with the application of the push terminal device or the application specified by the user; start the target application, and control the target application to play according to the playback information related to the target content The target content is rendered.

An embodiment of the present application provides a content connection method, including: receiving a relay request from a push-end device, where the relay request includes information related to the application of the push-end device and information provided by the application of the push-end device. play information related to the target content to request presentation of the target content on the display device; determine the target application on the display device according to the information related to the application of the push terminal, and the target application is an application with the push terminal The application with the highest matching degree or the application specified by the user; and starting the target application, and controlling the target application to present the target content according to the playing information related to the target content.

Description of drawings

FIG. 1 is a usage scenario of a display device in some embodiments of the present application;

FIG. 2 is a block diagram of the hardware configuration of the control device 100 in some embodiments of the present application;

FIG. 3 is a block diagram of a hardware configuration of a display device 200 in some embodiments of the present application;

FIG. 4 is a software configuration diagram of the display device 200 in some embodiments of the present application;

Fig. 5 is a software configuration block diagram of a public relay component according to an exemplary embodiment;

FIG. 6 is a schematic diagram of a relay process according to an exemplary embodiment of the present application;

FIG. 7 is a display device user interface;

FIG. 8 is a display device user interface;

Fig. 9 is a display device user interface;

FIG. 10 is a display device user interface;

FIG. 11A is a display device user interface;

FIG. 11B is a display device user interface;

FIG. 11C is a display device user interface;

Figure 12 is a display device user interface;

FIG. 13 is a schematic diagram of a push scenario in an embodiment of the present application;

Fig. 14 is a display device user interface;

Fig. 15 is a display device user interface;

FIG. 16 is a schematic diagram of a relay scenario according to an embodiment of the present application;

Fig. 17 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 18 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 19 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 20 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application;

Fig. 21 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 22 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application;

Fig. 23 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application;

Fig. 24 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 25 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 26 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 27 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

FIG. 28A and FIG. 28B are schematic diagrams of the user interface of the receiver device according to the present application;

Fig. 29 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 30 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 31 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 32 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 33 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application;

Fig. 34 is an interaction flowchart according to an exemplary embodiment of the present application;

Fig. 35 is an interaction flowchart according to an exemplary embodiment of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the application with reference to the drawings in the embodiments of the application. Apparently, the described embodiments are only some of the embodiments of the application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

It should be noted that the brief description of the terms in this application is only for the convenience of understanding the implementations described below, and is not intended to limit the implementations of this application. These terms are to be understood according to their ordinary and usual meaning unless otherwise stated.

FIG. 1 is a schematic diagram of an application scenario according to some embodiments of the present application. The schematic diagram is intended to illustrate a type of scenario in which there are multiple terminal devices and a server that can communicate with the terminal devices. These terminal devices include But it is not limited to devices with data sending and receiving and processing functions, image display functions and/or sound output functions. In the scenario shown in FIG. 1 , it includes a display device 200 , a mobile terminal 300 , a refrigerator smart screen 400 , a smart box 500 , a speaker device 600 and a server 700 .

Based on the Internet of Everything technology, communication connections can be established between multiple terminal devices in the above scenarios. The communication protocols for realizing the above-mentioned Internet of Everything may include local area network protocols, wide area network protocols, and short-distance wireless communication protocols that are not restricted by the network. Among them, the local area network protocol includes but not limited to the HSP communication protocol, the wide area network protocol includes but not limited to the AIOT protocol, and the short-range wireless communication protocol includes but not limited to the Bluetooth transmission protocol and the infrared transmission protocol. Based on the aforementioned different types of communication protocols, the communication protocol channels of the terminal equipment can be divided into LAN-based protocol channels, WAN-based WAN protocol channels, and other protocol channels. Other protocol channels include bluetooth protocol channel, infrared protocol channel and so on. Each protocol channel can support multiple communication protocols. The terminal device in the above scenario may support the aforementioned one or more protocol channels.

The terminal device can establish a communication connection with the server to perform information interaction with the server, such as providing various content and interactive information to the terminal device. Allows end devices to communicate via local area networks (LANs), wireless local area networks (WLANs), and other networks. The server 700 may be one cluster, or multiple clusters, and may include one or more types of servers.

It should be noted that other terminal devices may also be included in the same scene in Figure 1, including but not limited to touch-integrated devices, projection devices, tablet computers, computers, notebook computers, smart cooking devices, and various terminal devices mentioned above External devices such as keyboards, mice, game controllers, etc. There may be one or more terminal devices of the same type. For example, multiple display devices 200 may exist in the scene at the same time.

In some embodiments, different terminal devices can control each other, and can also control a specified terminal device through the control device 100 . For example, a user may operate the display device 200 through the control apparatus 100 or the mobile terminal 300 . For another example, the user may operate the smart box 500 or the refrigerator smart screen 400 through the smart device 300 , and/or operate the speaker device 600 and the like by operating the display device 200 or the smart device 300 .

In some embodiments, the control device 100 may be a remote control, and the communication between the remote control and the terminal device includes infrared protocol communication, bluetooth protocol communication, and other short-distance communication methods, and interacts with the terminal device in a wireless or wired manner. The user can control the terminal device by inputting user commands through buttons on the remote controller, voice input, control panel input, and the like.

In some embodiments, other terminal devices are controlled by using applications running on the mobile terminal 300 .

In some embodiments, each terminal device can also be controlled in a manner other than the control device 100 or other terminal devices. For example, the module for obtaining voice commands configured inside the device can directly receive the user's voice command control, or it can Receive the user's voice command control through the voice control device installed outside the device.

Fig. 2 is a configuration block diagram of the control device 100 according to some embodiments. As shown in FIG. 2 , the control device 100 includes but not limited to at least one of a controller 110 , a communication interface 130 , a user input/output interface 140 , a memory, and a power supply. The control device 100 can receive the user's input operation command, and convert the operation command into a command that the terminal device can recognize and respond to, so as to act as an interaction intermediary between the user and the terminal device.

In some embodiments, a terminal device includes a controller, memory, communicator and display. In some embodiments, the terminal device may further include at least one of a tuner and demodulator, a detector, an external device interface, an audio output interface, a power supply, and a user interface. Wherein, the controller includes a processor, a video processor, an audio processor, a graphics processor, a RAM, a ROM, and a first interface to an nth interface for input/output.

Taking the display device 200 as an example, FIG. 3 is a block diagram of a hardware configuration of the display device 200 according to an exemplary embodiment. As shown in Figure 3, the display device 200 includes but not limited to a tuner and demodulator 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, a user At least one of the interfaces.

In some embodiments, the display can be a liquid crystal display, an OLED display, and a projection display, and can also be a projection device and a projection screen.

A communicator is a component for communicating with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of a Wifi module, a Bluetooth module, a wired Ethernet module and other network communication protocol chips or near field communication protocol chips, and an infrared receiver. The terminal equipment can establish the transmission and reception of control signals and data signals with other terminal equipment, control devices or servers through the communicator.

The user input interface can be used to receive a control signal from a control device (such as an infrared remote controller, etc.).

The external device interface may include but not limited to the following: high-definition multimedia interface (HDMI), analog or data high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. any one or multiple interfaces. The controller controls the work of the terminal equipment and responds to user operations through various software control programs stored in the memory. The controller controls the overall operation of the terminal device. For example, in response to receiving a user command for selecting a UI object to be displayed on the display, the controller may perform an operation related to the object selected by the user command.

In some embodiments, the controller includes a central processing unit (Central Processing Unit, CPU), a video processor, an audio processor, a graphics processing unit (Graphics Processing Unit, GPU), RAM Random Access Memory, RAM), ROM (Read- Only Memory, ROM), at least one of the first interface to the nth interface for input/output, a communication bus (Bus), and the like.

Referring to Fig. 4, in some embodiments, the system is divided into four layers, from top to bottom are respectively the application (Applications) layer (abbreviated as "application layer"), application framework (Application Framework) layer (abbreviated as "framework layer") "), Android runtime (Android runtime) and system library layer (referred to as "system runtime layer"), and the kernel layer.

In some embodiments, there is at least one application program running in the application program layer, and these application programs can be window (Window) program, system setting program or clock program etc. that come with the operating system; they can also be developed by third-party developers. s application. During specific implementation, the application programs in the application program layer include but are not limited to the above examples.

In some embodiments, the operating system of the terminal device is configured with a public relay component and at least one content application program. Content applications refer to applications that can provide content or present content, such as camera applications, image resource applications, image viewing applications, video call applications, video playback applications, audio call applications, audio resource applications, map applications, and reading applications. The content includes pictures, audio (including call audio, audio files, and live audio streams), video (including call videos, video files, and live video streams), text, geographic location information, and navigation information. Presenting content includes displaying pictures, geographical location information or navigation information and text, playing video files, video call screens and live room screens, playing audio files, call sounds and live room sounds, etc. The public relay component is used to push the content presented by any content application to the external terminal device, so as to continue broadcasting on the external terminal device; it is also used to receive the content pushed by the public relay component on the external terminal device and its playback information, and The content continues to be played by the content having the capability to play the content.

In some embodiments, any content application can push content to other terminal devices that can establish a communication connection through the public relay component, so that there is no need to configure the function of pushing content on each content application. Any content application can receive a content push from other terminal devices through the public relay component, so as to carry out its capability connection, so that there is no need to configure the function of receiving content push on each content application. In the process of pushing, receiving and replaying the aforementioned content, the public relay component on the pusher device is responsible for communicating with the public relay component on the receiving device to complete the process of pushing, receiving and replaying the aforementioned content.

For ease of description, the above-mentioned process of content pushing, receiving, and capability connection performed by the pushing device and the receiving device in cooperation is called a relay process. The pusher device is the terminal device that initiates the content push, and the receiver device is the target device that receives the content push, or the terminal device that receives the content and relays the pusher device to continue playing the content. Based on the data flow direction, the relationship between the pusher device and the receiver device can be described as, the pusher device pushes a certain content to the receiver device, and the receiver device relays the content pushed by the pusher device. It should be understood that the terminal device involved in this application can at least serve as a receiving terminal device, relaying content pushed by other terminal devices, such as a smart speaker device relaying playing songs pushed by a mobile phone. The terminal device or display device involved in this application can not only be used as a receiving device, but also can be used as a push device to push content. For example, a mobile phone pushes the current song to a smart speaker for replay, and a mobile phone receives a video program pushed by a smart TV. and resume.

In some embodiments, capability continuation includes, but is not limited to, at least one of media resource continuation (such as video continuation, audio continuation, etc.) alarm setting, image quality and sound quality parameter setting, file overview, and the like.

Fig. 5 is a block diagram of a software configuration of a public relay component according to some embodiments. As shown in Figure 5, the public relay component includes an interaction center module, a state management module, an interface display module, a protocol processing module, and a logic control module.

Wherein, the interaction hub module is used for interacting with content applications on the local device. The interactive central module has a built-in SDK for calling by each application program, and each application program interacts with the interactive central module by calling the SDK. For example, when the user triggers an operation for transferring the current content to a designated terminal device for continued playback in the content application, the content application calls the aforementioned SDK to notify the interaction center module to send the public relay component for the user's operation respond. For another example, the interactive central module feeds back various status information during the content pushing process to the corresponding content application program.

The state management module is used to manage various state information generated during the interaction with other terminal devices, such as state information representing push success or failure, state information representing abnormal conditions, and various notification messages. The so-called management includes but is not limited to classifying information, judging information to make corresponding processing according to the judgment result, information forwarding, etc.

The interface display module is used to display interface elements related to the relay process in the user interface, such as window objects, tabs, status information prompt boxes and various operable buttons.

The protocol processing module is used to select the protocol channel through which it interacts with other terminal devices according to preset rules, for example, selecting one of the LAN protocol channel and the wide area network protocol channel, so that the terminal device communicates with other terminal devices through the channel selected by the protocol processing module. The terminal equipment performs information exchange.

The logic processing module is used to execute various logic controls involved in the relay process, such as logic control in a certain working mode and logic control in the case of multi-device interaction.

In some embodiments, each functional module of the public relay component is deployed at the application program layer. In other embodiments, each functional module of the public relay component can be deployed across layers, for example, the interaction hub module and the interface display module are deployed at the application layer, and other modules are deployed at other layers. This application is not limited to this. It should be noted that, in order to realize the above content relay function, the public relay component may include more or less modules, and is not limited to the software composition and architecture shown in FIG. 5 . Based on the functions of the public relay components involved in the embodiments of the present application, components with other components and structures designed belong to the protection scope of the present application.

Referring to FIG. 4 , the framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center, which decides to make the applications in the application layer take actions. Through the API interface, the application program can access the resources in the system and obtain the services of the system during execution.

As shown in Figure 4, in the embodiment of the present application, the application framework layer includes managers (Managers), content providers (Content Provider) etc., wherein the manager includes at least one of the following modules: activity manager (Activity Manager) Interact with all activities running in the system; the Location Manager is used to provide system services or applications with access to the system location service; the Package Manager is used to retrieve the information currently installed on the device Various information related to the application package; Notification Manager (Notification Manager) is used to control the display and clearing of notification messages; Window Manager (Window Manager) is used to manage icons, windows, toolbars, wallpapers on the user interface and desktop widgets.

In some embodiments, the activity manager is used to manage the life cycle of each application program and the general navigation back function, such as controlling the exit, opening, back, etc. of the application program. The window manager is used to manage all window programs, such as obtaining the size of the display screen, judging whether there is a status bar, locking the screen, capturing the screen, controlling the change of the display window (such as reducing the display window, shaking the display, distorting the display, etc.), etc.

In some embodiments, the system runtime layer provides support for the upper layer, that is, the framework layer. When the framework layer is used, the Android operating system will run the C/C++ library contained in the system runtime layer to realize the functions to be realized by the framework layer.

In some embodiments, the kernel layer is a layer between hardware and software. As shown in Figure 4, the kernel layer at least includes at least one of the following drivers: audio driver, display driver, bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensors, etc.), and power drives, etc.

In some embodiments, the user can input user commands through a graphical user interface (GUI) displayed on the display, and the user input interface receives user input commands through the graphical user interface (GUI). Alternatively, the user may input a user command by inputting a specific sound or gesture, and the user input interface recognizes the sound or gesture through a sensor to receive the user input command. The user interface is an interface that can be used to receive control input (such as: a physical button on the display device body, or others).

In some embodiments, "user interface" is a medium interface for interaction and information exchange between an application program or an operating system and a user, and it realizes the conversion between the internal form of information and the form acceptable to the user. The commonly used form of user interface is the graphical user interface (Graphic User Interface, GUI), which refers to the user interface related to computer operation displayed in a graphical way. It can be an icon, window, control and other interface elements displayed on the display screen of the electronic device, where the control can include icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. Visual interface elements.

In some embodiments, when a terminal device such as a display device presents a certain content, it may respond to user control and push relevant information about the content to the terminal device designated by the user, so that the terminal device designated by the user related information to continue playing the content. For ease of description, in the following embodiments, the terminal device that initiates the content push is called the pusher device, and the terminal device that accepts the content push and relays the broadcast is called the receiver device. It is worth noting that the push-end device and the receiver device can be display devices that have both image display and audio output functions, such as TVs, smartphones, tablets, refrigerator smart screens, etc., or they can only have audio output functions Devices that do not have image display functions, such as speaker equipment, radios, etc.

For example, when a user watches a TV series on the TV in the living room, he wants to cook in the kitchen, and the refrigerator in the kitchen has a smart screen, then the user can push the TV series to the smart screen of the refrigerator through a series of operations on the TV in the living room to continue play. In this way, the user can continue to watch the TV series through the smart screen of the refrigerator while cooking. For another example, the user listens to a song on the TV in the bedroom and wants to go to the living room, and the living room has speakers, then the user can push the song to the speakers in the living room to continue playing through a series of operations on the TV in the bedroom.

The terminal device can realize the above functions through the built-in public relay component. Various implementations of the technical solutions of the present application will be described in detail below by taking display devices and multimedia content as examples.

In some embodiments, after the display device is turned on and started, the public relay component starts to accept calls from any content application.

In some embodiments, after the public relay component is started, it scans the relay capabilities of all content applications in the system according to the standard interface of the operating system. Relay capability, as the name implies, refers to the ability of an application to continue presenting content, such as the type and presentation method of the content that can be presented. Taking a media application as an example, its content presentation capability may be its ability to play video files, including various parameters of playable video files. For the receiving end device, when it receives a request from the push end device to push the content, the application that matches the content through the relay capability continues to play the content. Exemplarily, if the relay content is a video, the receiving device needs to continue playing the video through its video playback application; if the relay content is text, the receiving device needs to continue playing the video through its text application (such as Notepad) Display the text.

In some embodiments, relay capability information of the device or other types of terminal devices is displayed, that is, relay capability information of each application on the device. When the device has an application that supports a certain relay capability, or in other words, when the relay capability of one or some applications on the device matches a certain relay capability, that is, the device supports this relay capability. The ability to present certain content.

In some embodiments, the same application may have different levels of relay capabilities, such as a first-level relay capability and a second-level relay capability. In fact, the second-level relay ability belongs to the first-level relay ability. In other words, the second-level relay ability is a sub-ability of the first-level relay ability. In other words, the first-level relay ability is an upper level ability for multiple second-level relay abilities, that is, a generalization of the multiple second-level relay abilities. In other words, the secondary relay capability of the application is the relay capability of the application in different working modes.

Considering the actual function of the content application, the actual relay capability of the content application can be described by one level of relay capability or a combination of multiple levels of capability. It should be understood that the relay capability of each application can be customized according to its actual function.

In the exemplary embodiment of the present application, taking the Jukanan application as an example, multiple modules are embedded in it, including but not limited to modules for realizing functions such as film and television, education, games, karaoke, fitness, and shopping. In this example, the relay capability of the application can be described by a combination of multi-level capabilities. For example, a level 1 relay capability and a level 2 relay capability subordinate to the level 1 relay capability. Wherein, each secondary relay capability corresponds to one of the aforementioned functional modules, the multiple secondary relay capabilities all belong to sub-relay capabilities of the application, and the primary relay capability is the total capability of the application.

However, it should be noted that in some implementation scenarios, if the first-level relay capability of an application matches a certain relay capability, the second-level relay capability of the application may not necessarily match the relay capability. Continuing to take the above-mentioned Jukanan application as an example, even though Jukankan’s first-level relay capability supports the ability to continue and present video content, the second-level relay capability of its modules for education, games, karaoke, fitness, shopping, etc. may not be Support video content continuous presentation capability. Therefore, in some embodiments, for an application with multi-level capabilities, when the relay capability of each level supports a certain relay capability, the application is considered to support this kind of relay capability, that is, it can continue to present certain content . For example, for an app with level 2 relay capability, if the app has level 1 relay capability and at least one level 2 relay capability matches the target relay capability, the app supports the target relay capability; for an app without level 2 relay capability, If the applied level one relay capability matches the target relay capability, then the application supports the target relay capability.

It should be noted that the embodiment of the present application does not limit the data form and data content of the relay capability. However, it should be noted that the relay capability of the application on the terminal device determines which content the terminal device can relay play. That is to say, the relay capability of the application on the terminal device determines the capability of the terminal device to relay content from other devices. For example, if there is no application for relay playing a certain content on a certain terminal device, then the terminal device cannot relay play the content, and thus cannot become the target receiving end device of the content.

In some embodiments, after the public relay component scans the relay capability of each application program, the relay capability data can be registered in the LAN protocol component of the terminal device, so that the LAN protocol component can understand the relay capability of each content application program, wherein the local area network The protocol component refers to the functional component used to respond to the command, request and other interactive information sent by the external device based on the LAN protocol channel. For example, when the first terminal device receives a capability inquiry message sent by the second terminal device in the same local area network based on the LAN protocol channel, the relay capability of each application program pre-registered by the public relay component is fed back to the second terminal device, Or make a response to the capability query message, such as a response that supports a certain relay capability or does not support a certain relay capability. In this way, the second terminal device can know the relay capability of the first terminal device, and use this as a basis to determine whether the first terminal device can serve as a receiving terminal device for a certain content.

In some specific implementation manners, the display device receives a capability query message sent by the push device, and the capability query message includes the target relay capability; it is judged whether there is an application supporting the target relay capability on the display device, wherein, for those with the second-level relay capability , if the application’s first-level relay ability and at least one second-level relay ability match the target relay ability, the application supports the target relay ability; for applications without second-level relay ability, if the application’s first-level relay ability If it matches the target relay capability, the supporting target relay capability shall be applied. Then return a response message to the push-end device according to the judgment result, so that the push-end device determines whether the display device supports the target relay capability according to the response message.

In other embodiments, after the public relay component scans the relay capability of each application, it can upload the relay capability data to the cloud server, so that the cloud server can query the relay capability of each application on the designated terminal device. For example, when the cloud server receives a query request sent by the first terminal device for querying the relay capability of the second terminal device, it may respond to the query request and return the relay capability data previously uploaded by the second terminal device to the first terminal device. Terminal Equipment. In this way, the first terminal device can know the relay capability of the second terminal device through the cloud server, and use this as a basis to determine whether the second terminal device can be used as a receiving terminal device for a certain content.

In some specific implementations, the terminal device sends a device query request to the server, and the device query request includes the push terminal identifier and target relay capability corresponding to the terminal device; the receiving server responds to the device query request, and searches for the terminal associated with it according to the push terminal identifier The relay capability information corresponding to the device, to determine whether there is an application supporting the target relay capability on these associated devices, wherein, for an application with a second-level relay capability, if the application has a first-level relay capability and at least one of the second-level relay capabilities is the same as the If the target relay capability matches, the application supports the target relay capability; for an application without secondary relay capability, if the application’s primary relay capability matches the target relay capability, the application supports the target relay capability. The device information set is returned to the terminal device according to the query result, and the device information set includes the device information of the terminal device that is associated with the push terminal identifier and supports the target relay capability and is queried by the server.

In other embodiments, after the public relay component scans the relay capability of each application program, it can save the relay capability data in the specified path of the local storage, so that the LAN protocol component, Bluetooth protocol component, etc. can be obtained under the specified path. The relay capacity data.

In some embodiments, the public relay component can select one or more of the above methods according to the communication strategy with other terminal devices to save the relay capability data of the local device. The communication strategy here refers to The communication channel on which it is based, such as a LAN protocol channel or a WAN protocol channel. Exemplarily, if the terminal device is limited to communicate with other devices in the LAN content based on the LAN protocol channel, the public relay component can choose to register the relay capability data in the LAN protocol component; if the terminal device can also communicate with the LAN content based on the WAN protocol channel When communicating with external devices, the public relay component can choose to upload the relay capability data to the cloud server, so that other devices can know the relay capability of the terminal device through the cloud server.

In some embodiments, when a terminal device presents a certain content presented by a certain content application, the public relay component can search for a terminal device that matches the relay capability according to the relay capability of the content application, and obtain a list of device information. The device information of the optional receiver device is in the information list. The user specifies the target push-end device based on the device information list, and the public relay component can communicate with the target push-end device based on a certain communication protocol channel, and request the target push-end device to play the content in relay. In response to the request, the public relay component on the target push device starts the content application with the relay capability, and continues to play the content through the content application with the relay capability.

It should be noted that, in a more specific implementation manner of the foregoing embodiments, the content application on the push terminal device needs to interact with the public relay component in response to user operations. The public relay component will perform some operations in response to the interaction information sent by the content application. In addition, since the public relay component has the function of presenting interface objects independent of content applications, users can directly interact with the public relay component through the interface objects provided by the public relay component to directly control the public relay component to perform certain operations. In other words, in a more specific implementation manner of the foregoing embodiments, the public relay component on the push end device may perform certain operations in response to user input.

For ease of description, in the following embodiments, the content that the user expects to push is called the target content, the relay capability of the application that provides the target content on the push device is called the target relay capability, and the target receiving device supports the target relay capability The application of is called the target application. In addition, the public relay component on the push-end device may also be referred to simply as the push-end relay component, and the public relay component on the receiver device may be simply referred to as the receive-end relay component. It should be understood that the aforementioned definitional names are all for convenience of description and distinction between concepts. It is not limited to the aforementioned names, and other names may also be used for description in some embodiments, so when clarifying the essence represented by a certain name, it is necessary to combine the context of the name. In the embodiment of the present application, the push end device can also be used to receive relay requests from other devices and perform relay play continuation, and the receiver device can also be used to push target content to other devices.

Fig. 6 is a schematic diagram of a relay process according to an exemplary embodiment of the present application. As shown in Figure 6, the process specifically includes the following steps:

S601. The push terminal device presents target content provided by a certain content application.

In fact, the target content can be any content presented by the content application. It should be understood that the types of target content provided by different content applications may be the same or different. The same content application can also provide different types of content. Exemplarily, for a media application, the presented content is mostly video content, picture content or audio content. Corresponding to the reading application, the content presented is mostly text content.

Fig. 7 is a display device user interface. As shown in FIG. 7 , the media application interface is displayed in full screen on the display device. There is a video playback window in the media application interface, and a certain video content provided by the media application is being played in the video playback window.

S602. The content application on the push device sends the target relay capability to the public relay component.

The target relay capability refers to the relay capability of the content application providing the target content in S601.

In an optional implementation manner, when the content application interface satisfies the preset condition, the content application sends its own relay capability to the public relay component. For example, when the target content is played in full screen, it is considered that the content application interface satisfies the preset condition. In another implementation manner, the content application may also send its own relay capability to the public relay component when other conditions are met. For example, when the content application receives a specific user input, the content application sends its own relay capability to the public relay component. In this regard, this application does not make a limitation.

S603, the public relay component on the push end device searches for a terminal device supporting the target relay capability, and obtains a list of device information.

In some embodiments, after receiving the target relay capability sent by the content application, the public relay component on the push terminal device starts to search for terminal devices supporting the target relay capability to obtain a device information list. The device information list is composed of optional device information of the receiver device. It should be understood that the search results of the public relay component can be divided into two cases, one is that at least one optional receiving end device is found, and the other is that no optional receiving end device is found. If an optional receiver device is found, it means that the current scene meets the preset content push conditions; if no optional receiver device is found, it means that the current scene does not meet the content push conditions.

In some embodiments, when the content application determines that the current scene satisfies the preset content push condition, it sends a device search request to the public relay component. In response to the device search request sent by the content application, the public relay component searches for an external terminal device (also referred to as a receiver device herein) that supports the target relay capability according to the target relay capability in the device search request.

In some other embodiments, the public relay component provides an interactive interface for the user to input a device search command, so that the public relay component can directly receive the device search command input by the user, and in response to the device search command, obtain the content application. The relay capability is obtained by obtaining the target relay capability; according to the target relay capability, an external terminal device supporting the target relay capability is searched. For example, when the target content is presented, the public relay component controls and displays an interface object for triggering presentation of device information, and the user can input a device search command by operating the interface object.

In some optional implementations, the public relay component on the pusher device sends a device search request to the cloud based on the WAN communication protocol channel, and the device search request includes the pusher information identifier and the target relay capability. Wherein, the pusher information identifier may be an account identifier logged on the pusher device, such as an account identifier logged into a content application. After the cloud receives the device search request, it searches for the terminal device associated with the push device according to the information identifier of the push device, such as a terminal device that is logged into the same account as the push device; after the cloud finds the terminal device associated with the push device , according to the relay capability data uploaded by these terminal devices, determine the terminal device that matches the target relay capability. For example, when the relay capability of the application on a certain terminal device matches the target relay capability, the terminal device is determined as the terminal device matching the target relay capability. If the cloud finds at least one terminal device that matches the target relay capability, it generates a device information list including the at least one terminal device and feeds it back to the push terminal device. If the cloud does not find a terminal device that matches the target relay capability, it will feed back an empty device information list to the push device, or return a corresponding notification message to the push device.

In some embodiments, the public relay component on the pushing end sends a capability inquiry message to the terminal device in the LAN based on the LAN communication protocol channel; after receiving the capability query message, the terminal device in the LAN returns the response message , and feed back the relay capability of each application registered in the LAN component to the push device; the push device determines an optional push device according to the relay capability fed back from the terminal device in the LAN.

In some embodiments, the public relay component on the push end opens a short-range communication protocol channel, and receives relay capability data sent by nearby terminal devices based on the short-range communication protocol channel, so as to determine from nearby terminal devices that support the target relay capability terminal equipment.

In some embodiments, the public relay component may select one or more of LAN protocol channels, wide area network protocol channels, and short-range communication protocol channels, and search for terminal devices that support the target relay capability based on the selected communication protocol channels. By selecting an appropriate protocol channel to search for devices, you can ensure that the searched device information is more comprehensive, provide users with more choices, and make more reasonable use of device communication resources, improve the execution speed of the content relay process between devices, and improve user experience. .

In some other embodiments, the user can pre-set the protocol channel used for communicating with the receiving end device. The public relay component searches for a terminal device that supports the target relay capability based on the communication protocol channel preset by the user. It should be understood that if the communication protocol channel set by the user is a LAN protocol channel, then the terminal device searched by the public relay component is a device in the same local area network as the push end device; if the communication protocol channel set by the user is a wide area network protocol channel , then the terminal device searched by the public relay component can be a device outside the local area network; if the communication protocol channel set by the user is a short-distance communication protocol channel, then the terminal device searched by the public relay component is the terminal device near the push end device .

In some embodiments, the public relay component at the push end performs a search for an external terminal device supporting the target relay capability through a WAN protocol channel, and is further configured to: send a device query request to the server through a LAN protocol channel, and the device query request includes displaying the corresponding The push terminal ID and target relay capability; receive the device information set returned by the server in response to the device query request, the device information set includes the device information of the terminal device that is associated with the push terminal ID and supports the target relay capability queried by the server. In some embodiments, the above-mentioned device information includes a unique identifier of the device and communication protocol information supported by the device. Among them, the communication protocols supported by some terminal devices can be attributed to one or more of LAN protocol channels, wide area network protocol channels, and short-distance communication protocol channels. For example, some terminal devices can communicate with the push-end device through a LAN protocol channel, or communicate with the push-end device through a short-distance communication protocol channel. For some terminal devices, it can only communicate with the push-end device through the WAN protocol channel.

In some embodiments, the public relay component can integrate the device information of the same terminal device scanned through different protocol channels according to the unique identifier in the device information, so as to present the integrated device information when the device information needs to be presented , to avoid presenting duplicate device information.

An exemplary integration result is as follows:

Terminal device A: support AIOT\LAN\Bluetooth;

Terminal device B: support LAN\Bluetooth;

Terminal device C: supports Bluetooth.

In some embodiments, when the public relay component on the push terminal device searches for the terminal device, the public relay component presents a prompt message on the current interface for prompting the user that the device is currently being searched. For example, as shown in FIG. 8 , a prompt message with the content "Looking for Device" is displayed on the playing screen.

S604, the public relay component on the push end device feeds back a search result to the content application, and the search result indicates that there is an optional receiving end device.

S605. After receiving the input relay operation (also referred to as "input command"), the content application on the push device sends a device presentation request to the public relay component.

In some embodiments, when the content application presents certain content, the user can control the control area to be called out through a certain operation or a combination of multiple operations. The user-operable controls are concentratedly displayed in the control area, and the user triggers the terminal device to perform corresponding operations by operating a certain control.

In some implementations, if the public relay component on the push end device searches for at least one optional receiving end device, it feeds back a first search result to the content application, where the first search result indicates that there is an optional receiving end device. If the content application receives the first search result, when the user operates the control area, an interface object for triggering the relay process is displayed in the control area, so that the user can input the relay operation by operating the interface object. If the content application does not receive the first search result, when the user operates to call out the control area, no interface object for triggering the relay process is displayed in the control area.

In another implementation manner, the public relay component on the push end device feeds back a search result to the content application, and the search result indicates whether there is an optional receiving end device. The content application determines whether to display the interface object used to trigger the relay process when the user calls out the control area according to the meaning represented by the search result.

In some implementations, when the content application determines that there is an optional receiving device based on the search result, the interface object used to trigger the relay process is directly displayed on the corresponding interface, without the need to display the interface object for triggering the relay process when the user operates the control area. The interface object is displayed in the control area.

As shown in FIG. 9 , the control area includes but is not limited to at least one of a "relay" control, a "playlist" control, a "sharpness" control, and a "recommended function" control. Wherein, the user can trigger the display device to perform a corresponding operation by operating a certain control. For example, when the user selects the Playlist control, the display device will display a list of collections. It is worth noting that the user can operate the "relay" control to input the content relay operation to trigger the display device to push the current program to other terminal devices to continue playing. When the media application receives the user's operation on the "relay" control, the media application sends the relay operation to the public relay component.

Of course, the user can also input content relay operations in other ways, such as using the voice control function of the display device to input content relay operations through voice passwords, or input content relay operations through designated buttons or button combinations on the control device.

S606. The public relay component on the push device presents a device information list, where the device information list includes at least one optional receiving device option.

In some embodiments, if at least one external terminal device supporting the target relay capability is found, the public relay component controls the display of an interface object used to trigger the display of device information. At this time, the user can indicate the presentation by operating the interface object The searched device information; the public relay component presents a device information list in response to the input device presentation command, and the device information list includes multiple device options, and the device options correspond to the searched device information; when receiving the input target device When the option is selected, it is determined that the content push command is received, and the target device option corresponds to the device information of the target receiving end device.

As shown in FIG. 10 , the device information list includes multiple optional device options named "living room TV on the second floor", "kitchen refrigerator on the first floor", "speaker in the second bedroom", and "TV in the living room on the first floor". At this point, the user can specify the target receiver device by inputting a selection operation on an option in the list. For example, when the user selects "TV in the living room on the second floor", a device named "TV in the living room on the second floor" is designated by the user as the target receiver device.

S607. After the public relay component on the push end device receives the input selection operation on the target receiving end device, request the content application for playing information of the target content.

S608, the content application on the push terminal device returns the play information related to the target content (also referred to as "play information of the target content" herein) to the public relay component.

Wherein, the playing information of the target content is used to enable the application on the receiving end device to continue presenting the target content according to the playing information. For example, when the target content is multimedia content, its playing information should at least include the playing source address, playing progress, etc. Based on the playing information, the application on the receiving device is sufficient to continue playing the multimedia content. For another example, when the target content is navigation information, its playback information should at least include user location information and planned route information. Based on the playback information, the map application on the receiving end device is sufficient to continue to navigate for the user. It should be understood that, according to different content applications, the parameters included in the corresponding playing information may be the same or different. The playback information of a content application on the push device should be parsed and recognized by at least one content application on the receiver device, so as to continue presenting the target content.

In some other embodiments, when the content application presents the target content, the user can use the voice control function to instruct the public relay component to search for a terminal device that supports the target relay capability. For example, referring to FIG. 11A , after the user wakes up the voice application, he says "check the relay device", and the voice application analyzes the semantics of the voice data to determine the device search command input by the user. Send the device search command to the public relay component, and reply to the user "OK, start querying" on the interface. The public relay component responds to the device search command sent by the voice application, searches for terminal devices that support the target relay capability, and obtains a list of device information.

Next, the public relay component sends the searched device information list to the voice application, reads the specific content of the device information list through the voice application, and displays the device information list on the interface in text, as shown in Figure 11B. After obtaining the device information list, the user can specify the target receiving device through the voice control function, and instruct the push device to perform the relay process. For example, when the user says "relay to the TV in the living room on the second floor", the voice application analyzes the semantics of the voice data to determine that the target receiving device specified by the user is a terminal device named "TV in the living room on the second floor", and the voice application pushes the target The device information of the end device is sent to the public relay component, and at the same time, it replies to the user "OK, relaying", as shown in Figure 11C. After the public relay component receives the target receiver information, it requests the content application for the playback information of the target content, and performs subsequent steps.

In addition, the user can also trigger some links in the above-mentioned relay process through touch gestures, air gestures and other operations, which will not be described here.

S609, the public relay component on the push end device sends a call request to the target receiver device, and the call request includes target relay capability and play information of the target content.

In some embodiments, a call request is also called a handover request.

In the embodiment of the present application, the receiver device may receive a relay request from the push device through its controller, and the relay request may include information related to the application of the push device and the push device's The provided playback information related to the target content is applied to request presentation of the target content.

In some embodiments, after receiving the user's selection operation on the target push-end device, the public relay component on the push-end device calls the target receiving-end device after waiting for a preset period of time. While the public relay component on the push device is waiting, a prompt message will be displayed on the interface. During the display or waiting period of the prompt message, the user can cancel the push by some operation, and can also instruct to push immediately by some operation. If the public relay component receives a cancel command input by the user during the display period of the prompt message or during the waiting period, the step of canceling the push is performed. That is to say, the push terminal device responds to an input command indicating to push the currently presented target content to the target receiving terminal device, and controls the presentation of prompt information, so as to prompt the user to input a cancel push command or confirmation within a predetermined time period through the prompt information. push command; in response to the confirmation push command input by the user within a predetermined period of time, a relay request is sent to the target receiving end device to request the target receiving end device to continue presenting the target content; or, in response to the input of the user within a predetermined period of time cancel the push command, and cancel sending the relay request to the target receiving end. If the input confirmation push command or cancel push command is not received within the predetermined time length, a relay request is sent to the target receiving end device at the end of the predetermined time length, and the display of the prompt information is cancelled. In some other embodiments, after receiving the user's selection operation on the target push-end device, the public relay component on the push-end device displays a prompt message on the current interface while calling the target receiver-end device. During the display of the prompt message or within the preset time, the user can cancel the push through some operation. If the push terminal device receives a cancel command input by the user during the display period of the prompt message or within a preset time, the step of canceling the push is performed. For example, if the target receiving end device is not called when an input cancel command is received, the call is blocked. If the target receiving end device has been called when the input cancel command is received, a cancel handover request is sent to the target receiving end device, so that the target receiving end device interrupts related operations.

That is to say, the push-end device sends a relay request to the target receiver-end device in response to an input instruction to push the currently presented target content to the target receiver-end device, so that the target receiver-end device continues to present the target content according to the relay request; In response to receiving a cancel push command input by the user within a preset time period, a cancel relay request is sent to the target receiving end device, so that the target receiving end device cancels presenting the target content. In this way, the user has a certain period of time to confirm the push operation input before, and consider whether to withdraw the push operation, so as to avoid pushing the target content to the target receiving end device due to user misoperation, and improve user experience.

Exemplarily, the user may operate any key to input the above-mentioned cancellation push command. The user may input the above confirmation push command through a designated key.

In some embodiments, after the public relay component on the push end device receives the user's selection operation on the target push end device, it performs a countdown while displaying a prompt message. The countdown time can be the waiting time before calling, or The display duration of the prompt message. And, an interface element for showing the progress of the countdown is displayed on the interface, so as to present a visual prompt of the progress of the countdown to the user.

Fig. 12 is the application interface displayed on the push end device after the user selects "the living room TV on the second floor" as the target receiving end device in Fig. 10 . As shown in Figure 12, the interface displays a prompt message with the content "It will be pushed to the TV in the living room on the second floor, press any key to stop, press the confirmation key to immediately relay", and the countdown progress is displayed on the side of the prompt message. Follow the prompt "3".

In some embodiments, after receiving the cancel push command input by the user, the public relay component on the push end device displays corresponding prompt information on the interface, and sends the relay cancel request to the target receiving end device. After receiving the relay cancellation request, the public relay component on the target receiver device displays corresponding prompt information on the interface of the receiver device.

Fig. 13 is a schematic diagram of a push scenario according to an exemplary embodiment of the present application. The interface of the push-end device in Figure 13 is specifically the interface displayed after the push-end relay component receives the cancel push command input by the user. As shown in Figure 13, the interface of the push-end device displays a prompt with the content "Push has been cancelled" information. The interface of the receiver device in Figure 13 is specifically the interface displayed by the receiver relay component after receiving the cancel relay request sent by the push device. As shown in Figure 13, the interface of the receiver device displays the content "The bedroom TV Push" message.

It should be noted that both the push-end device and the public relay component on the receiver-end device can broadcast messages by calling the voice application, including but not limited to the above-mentioned prompt information of "the push has been canceled" and "the bedroom TV has canceled the push".

In some embodiments, after the push-end device sends a relay request to the target receiving-end device, the content application on the push-end device may continue to present the target content, or may stop presenting the target content.

In some optional implementation manners, the user can set specified functions of the content application. After the push device sends a relay request to the target receiver device, the content application decides whether to continue presenting the target content according to the user settings. Exemplarily, in the case where the user enables the "original device to continue playing" function of the content application, after the push device sends a relay request to the target receiving device, the content application continues to present the target content. When the user disables the "original device continue playing" function of the content application, after the push device sends a relay request to the target receiving device, the content application continues to present the target content. Based on this, after the pusher device sends the relay request to the target receiving device, it is further configured to: obtain the target setting parameter, the target setting parameter is the first value or the second value; if the target setting parameter is the first value, control The content application finishes playing the target content; if the target setting parameter is the second value, the content application is controlled to continue playing the target content.

In some embodiments, the page displaying the device information list may also display some additional user guidance options and guidance information. For example, in the device information list page in FIG. 10 , the user can trigger to enter the relay function introduction page by operating the "?" control. The relay function introduction page is at least used to display the introduction information of the relay function, such as the relay operation mode. In addition, on the device information list page in FIG. 10 , there is displayed a guide message with the content of “press the confirmation key to relay, and press the menu key to adjust the order”. As the name suggests, this guide information is used to remind the user that when a device option is selected, the relay process can be triggered by operating the confirmation key on the remote control, and the device option in the device information list can be adjusted by operating the menu key on the remote control. display order.

In addition, on the device information list page in Figure 10, there is also a switch button of "continue to play on the original device". , after the public relay component pushes the content to the receiver device, the content application will continue to play the content. When the user operates the switch button to turn off the function of "continue playing on the original device" of the content application, then, after the public relay component pushes the content to the receiving end device, the content application can exit to end playing the content .

In some other embodiments, after the push device sends the relay request to the target receiving device, it is further configured to: receive the playback status information sent by the target receiving device, and acquire the target setting parameter, where the target setting parameter is the first value or The second value; if the playback status information indicates that the target receiver device responds successfully to the relay request, and the target setting parameter is the first value, then the control content application ends playing the target content; if the playback status information indicates that the target receiver device failed to respond to the relay request, Or if the target setting parameter is the second value, then the content application is controlled to continue playing the target content.

S610, the public relay component on the target receiving end device responds to the call request sent by the push end device, and starts the target application supporting the target relay capability.

In some embodiments, the push-end device sends a relay request to the target receiver-end device to request the target receiver-end device to continue presenting the target content provided by the push-end application. The relay request may include application information at the push end and play information of the target content. The pusher application information includes at least the target relay capability, and may also include the application identifier of the pusher application. Whether the two applications are the same application can be determined according to the application identification.

In an embodiment of the present application, the target application on the display device is determined according to the information related to the application of the push device, and the target application is the application with the highest degree of matching with the application of the push device or An application specified by a user; launching the target application, and controlling the target application to present the target content according to playback information related to the target content

In the embodiment of this application, after receiving the relay request sent by the push-end device, the receiving-end public relay component determines the target application according to the push-end application information. The application specified for the user. Then start the target application, and control the target application to continue presenting the target content according to the playing information of the target content. Therefore, the success rate of connecting and presenting the target content is ensured to the greatest extent, and the situation of connection failure or connection error is avoided.

In some embodiments, the pusher application information includes the target relay capability and application identifier of the pusher application. After receiving the relay request sent by the push device, the public relay component at the receiving end determines the target application according to the application information of the push end, specifically including: the public relay component at the receiving end first determines the target application based on the relay capability of each application on the receiving device. At least one candidate application of the relay capability. Then, according to the application identification, the target application is determined from the candidate applications. For example, it is determined whether there is an application identical to the pusher application among the candidate applications, wherein, when the application identifier of a candidate application matches the application identifier of the pusher application, it is determined that the candidate application is the same application as the pusher application. If there is an application identical to the push-end application among the candidate applications, the candidate application identical to the push-end application is determined as the target application. For example, when the pusher application is a media center application, and the candidate applications on the receiver device also include the media center application, the media center application is determined as the target application. If there is no application identical to the application at the pushing end among the candidate applications, the target application is determined from the candidate applications according to preset rules.

In a more specific implementation, the receiver public relay component determines at least one candidate application that supports the target relay capability according to the relay capability of each application on the receiver device, including: judging the first-level relay capability of the application on the display device Whether it matches the target relay capability; if the application’s first-level relay capability matches the target relay capability and the application has a second-level relay capability, determine whether the application’s second-level relay capability matches the target relay capability; if at least one of the application’s If the secondary relay capability matches the target relay capability, the application is determined to be a candidate application; if the application's primary relay capability matches the target relay capability and the application does not have the secondary relay capability, the application is determined to be a candidate application.

In some embodiments, the receiving end public relay component first judges whether there is an application identical to the push end application on the receiving end device according to the application identifier of the push end application, and if there is an application identical to the push end application, then the The same candidate application is determined as the target application. If there is no application identical to the pusher application, at least one candidate application that supports the target relay capability is determined according to the relay capability of each application on the receiving device. Then determine the target application from the candidate applications according to the preset rules.

In some embodiments, the public relay component at the receiving end determines the target application from the candidate applications according to preset rules, which specifically includes: sorting the candidate applications according to a predefined sorting rule, so as to determine the candidate application with the highest priority; The candidate application with the highest priority is determined as the target application. It should be noted that the embodiment of the present application does not limit the manner of the predefined sorting rules, nor does it limit the predefined sorting rules. According to the needs of different scenarios, different sorting rules can be defined. It should be understood that, according to different sorting rules, the sorting results are different, and thus the positions of the candidate applications are different, that is, their priority levels are different.

In some embodiments, relay scenarios may be pre-categorized. For example, relay scenarios may be classified according to the type of target content. And the sorting rules corresponding to the categories of relay scenarios are defined in advance. The public relay component at the receiving end acquires the corresponding predefined sorting rules according to the current relay scenario category, and sorts the candidate applications according to the acquired sorting rules.

In some embodiments, the content can be classified in advance, and a default application is preset for each type of content. Exemplarily, one of multiple video applications capable of presenting video content is set as a default application for continuing to present video content. Based on this, the public relay component at the receiving end determines the target application from the candidate applications according to preset rules, specifically including: determining the category of the target content; The default application corresponding to the category of is determined as the target application.

In some embodiments, after receiving the relay request sent by the push-end device, the public relay component at the receiving end determines the target application according to the push-end application information, specifically including: determining the supported target relay capability according to the relay capability of each application on the display device present at least one candidate application; present an application list, and the application list includes application options corresponding to each candidate application; receive a selection operation of any application option by the user, and determine the candidate application selected by the user as the target application.

Fig. 14 is a user interface of a display device according to an exemplary embodiment of the present application, which is specifically a user interface displayed after the display device, as a receiving device, receives a relay request sent by a push device. As shown in FIG. 14 , an application list is presented on the user interface, and the application list includes application options corresponding to each candidate application, namely application 1 , application 2 and application 3 . At this point, the user can select an application option by moving the focus, and confirm the selection of an application option by inputting an operation to designate the corresponding candidate application as the target application.

In some embodiments, the application options in the above application list may be presented in random order. In other embodiments, all candidate applications may be sorted in advance according to a predefined sorting rule, so as to determine the priority level of each candidate application. Then, an application list is presented according to the sorting result, so that the application options in the application list are arranged in a certain order, that is, arranged according to the priority level of each candidate application.

In some embodiments, after receiving the relay request sent by the push-end device, the public relay component at the receiving end determines the target application according to the push-end application information, specifically including: determining the supported target relay capability according to the relay capability of each application on the display device at least one candidate application; obtain the latest startup time corresponding to each candidate application; and determine the application with the latest startup time among the candidate applications as the target application.

In some other embodiments, the target application may also be determined according to other user operation information of each candidate application. For example, the startup times of each candidate application in the past certain period of time are obtained, and the application with the highest startup times among the candidate applications is determined as the target application. For another example, the running time of each candidate application within a certain period of time in the past is obtained, and the application with the longest running time among the candidate applications is determined as the target application.

In some embodiments, if there is only one target application supporting the target relay capability on the receiving device, the public relay component directly determines the application as the target application.

In some embodiments, after the public relay component on the receiving end device receives the call request from the push end device, it waits for a preset period of time, and then starts supporting the target application. While the public relay component on the receiver device is waiting, a prompt message will be displayed. During the display or waiting period of the prompt message, the user may cancel the relay through some operation, and may also instruct immediate relay through some operation. If the receiving end device receives a command to cancel the handover input by the user during the display period of the prompt message or within the waiting time, the step of canceling the handover is performed. In some other embodiments, the public relay component on the receiving end device responds to the call request of the push end device, and displays a prompt message on the interface while searching for the target application. During the display period of the prompt message or within a preset time, the user may cancel the relay through some operation. If a cancel command input by the user is received during the display period of the prompt message or within a preset time, the step of canceling the relay is performed. For example, if the supporting target application is not started or the target application does not start to present the target content when the input cancel relay command is received, the start or play is prevented, and a cancel message is sent to the push device. If the target application has started to play the target content when receiving the input cancel relay command, it will end the playback and send a cancel message to the push device.

That is to say, in response to receiving the relay request sent by the push device, the public relay component on the receiving end device controls to present some kind of prompt information, so as to prompt the user to input a cancel relay command or confirm the relay within a predetermined period of time through the prompt information. command; in response to a confirmation relay command input by the user within a predetermined duration, execute the relay request to continue presenting the target content; or, in response to a cancel relay command input by the user within a predetermined duration, ignore the relay request and cancel rendering of the target content, and present Corresponding prompt information, and sending a cancellation message to the push device. And when the input confirmation relay command or cancel relay command is not received within the predetermined time length, the relay request is executed at the end of the predetermined time length to continue presenting the target content. In this way, the user can prevent the display device from presenting the specified content through specified operations within a predetermined period of time before the display device receives the relay request sent by the push device, or instructs the display device to present the specified content immediately. content, fully improving the flexibility of user operations.

In some embodiments, after receiving the relay request from the push device, the public relay component on the receiving device ignores the relay request to cancel the presentation of the target content, and presents the corresponding Prompt information. In some embodiments, after receiving the call request sent by the push device, the public relay component on the target receiving device performs a countdown while displaying a prompt message. How long to display the message. And, an interface element for showing the progress of the countdown is displayed on the interface, so as to present a visual prompt of the progress of the countdown to the user.

FIG. 15 is a user interface displayed on the target receiving end device after the user selects “the TV in the living room on the second floor” as the target receiving end device in FIG. 10 . As shown in Figure 15, the user interface displays a prompt message with the content of "relaying the TV content in the bedroom, press any key to stop, press the confirmation key to relay immediately", and a visual display of the countdown progress is displayed on the side of the prompt message. Prompt "5".

In some embodiments, after receiving the cancellation command input by the user, the public relay component on the receiver device displays a corresponding cancellation notice on the interface of the receiver device, and synchronizes the relay status to the pusher device. After the public relay component on the push-end device receives the relay status sent by the receiver-end device, it displays a corresponding cancellation notice on the interface of the push-end device.

Fig. 16 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The interface of the receiving end device in Figure 16 is specifically the interface displayed after the receiving end relay component receives the cancel command input by the user. As shown in Figure 16, the interface of the receiving end device displays a notification message with the content "relay has been canceled" . The interface of the push-end device in Figure 16 is specifically the interface displayed after the push-end relay component receives the relay status sent by the receiving-end device. As shown in Figure 16, the interface of the push-end device displays the content "The peer has stopped " notification message.

In some embodiments, the public relay component selects the target communication protocol channel according to the information of the target receiving end, and calls the target receiving end device based on the target communication protocol channel. Wherein, the target communication protocol channel may be one or more of a local area network protocol channel, a wide area network protocol channel and a short distance communication protocol channel.

Specifically, if the target receiver device supports only one protocol channel, then the protocol channel is determined as the target protocol channel. For example, for the terminal device C that only supports the Bluetooth protocol in the above example, the Bluetooth protocol channel is determined to be the target communication protocol channel. For a terminal device supporting multiple communication protocols, the public relay component determines one of the communication protocols supported by the target receiver device according to preset rules as the target communication protocol channel.

In some embodiments, the rules for determining the target communication protocol channel can be designed according to the characteristics of various communication protocol channels. It is known that the LAN protocol channel and the WAN protocol channel have the characteristics of unlimited transmission distance, strong anti-interference ability, and fast transmission rate (the larger the bandwidth, the faster the transmission rate); and the short-distance communication transmission protocol, such as Bluetooth protocol, infrared protocol , the transmission distance is short, and for the infrared protocol, directionality and accessibility are also required.

Based on this, in some exemplary embodiments, when the receiver device supports both the LAN protocol channel and the WAN protocol channel, the LAN protocol channel can be determined as the target communication protocol channel because the response speed of the LAN is faster than that of the WAN. When the receiving device supports the LAN protocol channel, the WAN protocol channel and the Bluetooth protocol channel at the same time, if the transmission distance is known to be relatively long, such as exceeding 10 meters, then the LAN protocol channel or the WAN protocol channel is determined as the target communication protocol channel; If the transmission distance is relatively short, if it does not exceed 2 meters, and the Bluetooth signal is strong and the network signal is weak, then the Bluetooth protocol channel is determined as the target communication protocol channel. When the receiving device supports both the Bluetooth protocol channel and the infrared protocol channel, since the infrared protocol is generally an imperative transmission, and the amount of data supported is small, the anti-interference ability is weak, so the Bluetooth protocol channel is first determined as the target communication protocol channel .

In some embodiments, the public relay component at the push end obtains the preset priority of each protocol channel; and determines the protocol channel with the highest priority supported by the target receiver device as the target protocol channel.

It can be understood that by selecting an appropriate protocol channel to call the target receiving device, the communication resources of the device can be used more reasonably, the execution speed of the content relay process between devices can be improved, and the user experience can be improved.

In some embodiments, the public relay component on the push-end device simultaneously calls the receiving-end device according to each communication protocol channel supported by the receiving-end device. The receiving end device will successively receive the call requests sent by the push end device based on different protocol channels. The receiving end device processes the first received call request, and performs subsequent interaction with the push end device based on the communication protocol corresponding to the first received call request. When the receiving device subsequently receives the same call request sent by the same push device based on other protocol channels, it only needs to discard these call requests.

S611, the public relay component on the receiving end device sends the playing information of the target content to the target application.

S612, the target application on the receiving end device continues to play the target content according to the play information of the target content.

S613, the target application on the receiver device feeds back the playing status information to the public relay component.

S614, the public relay component on the receiving end device sends the playing state information to the push end device.

In some embodiments, the playback status indicates playback success or playback failure. If the target application on the receiving end device successfully resumes playing the target content, the target application feeds back playback status information indicating successful playback to the receiving end relay component. If the target application on the receiving end device fails to continue playing the target content, the target application feeds back playback status information indicating successful playback to the receiving end relay component.

In some embodiments, the relay component at the receiving end displays a corresponding prompt message on the interface of the receiving end device according to the received playing state information.

In some embodiments, after receiving the call request sent by the push-end device, the public relay component on the receiving-end device returns a response message to the push-end device. The push end device determines whether the relay is successful or failed according to whether the response message is received. If the response message is received, it is considered that the relay is successful, and the corresponding prompt information will be displayed, such as the prompt message "has been pushed to xx device", if the response message has not been received for a long time, it is considered that the relay has failed, then The corresponding prompt information is displayed, such as the prompt information with the content "relay failure".

S615. The public relay component on the push device receives the playing state information, and presents corresponding prompt information according to the playing state information.

In some embodiments, after receiving the playing state information sent by the push device, the public relay component instructs the content application to end playing the target content according to the playing state information and the switch state of the "original device continue playing" button, or instructs the The content application continues to play the target content. For example, no matter whether the playback status information reveals that the receiver device has successfully played the target content or failed, as long as the "Original Device Continue Playing" button is turned on, the content application is instructed to continue playing the target content. If the playback status information reveals that the receiving device failed to play the target content, if the "Original Device Continue Playing" button is on, it will instruct the content application to continue playing the target content; content playback.

Fig. 17 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The receiver device interface and the pusher device interface in FIG. 17 are specifically the interfaces displayed after the target application successfully resumes playing the target content. In FIG. 17 , the interface of the receiving device displays a prompt message with the content "relayed the TV content playback in the bedroom", and the push device interface displays a prompt message with the content "relayed the TV content playback in the living room on the second floor".

Fig. 18 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The receiver device interface and the pusher device interface in FIG. 18 are specifically the interfaces displayed after the target application fails to continue playing the target content. In FIG. 18 , the interface of the receiver device displays a prompt message with the content "relay failure", and the interface of the push device displays a prompt message with the content "relay failure".

In some embodiments, when the target receiving end device and the pushing end device are of different types of devices, the public relay component of the pushing end device presents a prompt message related to the target receiving end device on the interface of the pushing end device. For example, when the push device is a display device, the target receiver device is a speaker device, and the target content is audio content, after the relay is successful, the public relay component of the push device will display the content as "Receiver The device has no interface display" prompt message. It should be noted that this application does not limit the specific content, display method, display time and duration of such prompt messages. For example, after the user selects the target receiving end device, the push end device public relay component determines that the type of the target receiving end device selected by the user is different from that of the push end device, and displays a prompt message. You can display the prompt message after the relay is successful.

It should be noted that the relay process involved in the embodiment of the present application is not limited to the process in FIG. 6 , and the style of the UI interface displayed during the process of executing the relay process between the pusher device and the receiver device is not limited to the style of the above-mentioned embodiment. Based on the core idea of the technical solution of the present application, those skilled in the art can obtain many different implementation modes without creative work, and these implementation modes all belong to the protection scope of the application.

In some embodiments, during relay interaction with the push device, in response to receiving a relay request from an additional push device, the current working mode of the display device may be acquired. And it may be determined based on the current working mode whether the display device performs relay interaction with the additional push end device.

In some embodiments, the public relay component can work in two modes, one is an exclusive mode, and the other is a non-exclusive mode. Among them, when the public relay component is currently in the exclusive mode, when it interacts with a receiving end device, or when interacting with a certain push end device, it does not interact with the receiving end device or the push end device. The terminal device interacts with content push and content relay process. In other words, when the public relay component on the terminal device is currently in the exclusive mode, the public relay component cannot simultaneously perform information interaction operations related to content push and content relay process with two or more terminal devices. Conversely, when the public relay component is currently in the non-exclusive mode, it performs information interaction in the process of content push to a receiving end device, and/or performs information interaction in the process of content relay with a certain push end device , and interact with other terminal devices other than the receiving end device or the push end device about content push and content relay process.

In some possible implementations, the above-mentioned interaction related to the content pushing process includes at least the steps from S609 to presenting the playback state performed by the push end relay component in FIG. 6 . That is to say, if the push-end relay component is in the exclusive mode, it will not interact with terminal devices other than the receiving-end device during the period from executing S609 to presenting the playing state.

In some possible implementation manners, the above-mentioned interaction related to relaying content includes at least S610 to S614 performed by the relaying component at the receiving end in FIG. 6 . That is to say, if the relay component at the receiving end is in the exclusive mode, it will not interact with terminal devices other than the pushing end device during execution of S610 to S614.

In some embodiments, the above-mentioned interaction related to content push and content relay is called relay interaction. Taking the display device as an example, in the process of relay interaction with the first terminal device, the display device obtains the current working mode in response to receiving the relay request sent by the second terminal device; if the current working mode is exclusive mode, ignore the second The second terminal device sends a relay request, and returns an exclusive message to the second terminal device. If the current working mode is non-exclusive mode, display the corresponding relay request prompt information according to the relay request sent by the second terminal device, so that the user can trigger the relay interaction with the second terminal device according to the relay request prompt information or trigger Giving up the relay interaction with the second terminal device. Wherein, the relay interaction with the first terminal device refers to the interaction process of executing the relay request sent by the first terminal device to continue presenting the content pushed by the first terminal device, and/or, executing the input content push command to update the currently presented Push the content to the first terminal device to continue the interactive process of presentation. In this way, the relay request sent by the second terminal device can be prevented from interrupting the relay interaction process between the display device and the first terminal device, ensuring that the display device successfully relays the content pushed by the first terminal device, or pushes the content to the first terminal smoothly on the device to ensure user experience.

In some embodiments, if the current working mode is non-exclusive mode, an interrupt operation prompt message is displayed, so that the user can input an interrupt operation according to the interrupt operation prompt information, and the interrupt operation is used to control the display device to interrupt communication with the first terminal. Device relay interaction process. In response to the input interruption operation, the relay interaction process with the first terminal device is interrupted.

In some embodiments, the user can perform settings related to the content relay function on the UI interface provided by the public relay component, including setting the working mode of the public relay component. For example, by interacting with interface objects on the UI interface provided by the public relay component, the working mode of the public relay component is set to an exclusive mode or a non-exclusive mode.

Based on this, in the above embodiments, the display device acquires the current working mode, which may specifically include acquiring the on/off state of the device exclusive function; if the device exclusive function is on, then determine that the current working mode is the exclusive mode; if the device exclusive function is off state, then determine the current working mode non-exclusive mode.

In some other embodiments, the user can enable or disable the device-exclusive function of the public relay component on the UI interface provided by the public relay component. When the device exclusive function of the public relay component is turned on, when the public relay component starts to interact with a certain terminal device on content push or content relay, the public relay component automatically enters the exclusive mode, and when it finishes interacting with a certain During the aforementioned interaction of the terminal, it automatically exits the exclusive mode, and then enters the non-exclusive mode. When the device exclusive function of the public relay component is turned off, the public relay component is always in non-exclusive mode. That is, even if the public relay component starts to perform content push or content relay interaction with a certain terminal device, it will not automatically enter the exclusive mode.

In some embodiments, when the public relay component on the terminal device receives a call request sent by other terminal devices, it is judged whether it is currently in the exclusive mode; if it is not currently in the exclusive mode, the call request is processed, for example, execute FIG. 6 S610 to S614 in the above; if currently in the exclusive mode, the call request will not be processed, and the corresponding relay request prompt information will be displayed on the interface, and the corresponding notification message will be fed back to the terminal device that sent the call request. For ease of description, the notification message may be called an exclusive message. The terminal device sending the call request can display corresponding prompt information on its interface according to the exclusive message. Wherein, the relay request prompt information includes device information of other terminal devices and/or key information of the target content, such as device names of other terminal devices and content names of target content.

In some possible implementations, when the public relay component is in the exclusive mode, it can judge that the call request or other information data is a request or information sent by the current interactive terminal by judging the source of the call request or other information data Data, or request or information data sent by other terminal devices. If it is a request or information data sent by another terminal device, the request or information data is shielded.

It is understandable that the terminal device in the exclusive mode may be acting as a push device and interacting with the receiving device related to the content push process, or it may be a receiving device performing content relay with the push device Process-related interactions.

It should also be understood that the public relay component may receive call requests sent by multiple terminal devices at the same time, and the aforementioned simultaneous means that the multiple call requests are received at the same moment or the time difference between receiving the multiple call requests is short enough. In some embodiments, when the public relay component on the terminal device is in non-exclusive mode, if multiple call requests sent by multiple terminal devices are received, the first received call request is processed, for example S610 to S614 in FIG. 6 are executed without processing a call request received later. And, when deciding not to process a certain call request, feed back a corresponding notification message to the terminal device that sent the call request. For ease of description, the notification message may be called a busy message. The terminal device sending the call request can display corresponding prompt information on its interface according to the busy message.

In some embodiments, when the public relay component on the terminal device is in non-exclusive mode, if multiple call requests sent by multiple terminal devices are received, the relay corresponding to each call request is displayed on the interface Information, the relay information includes but not limited to the device information sent to the request, such as the device name, and may also include the content information of the request relay, such as the name of the target content. The user can specify the target relay information based on the relay information displayed in the interface, and the public relay component can process the corresponding call request and play the response content in relay. For the relay information not specified by the user, the public relay component may feed back a busy message to the terminal device sending the corresponding call request.

Fig. 19 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push the content of A to device B, device C sends a call request to device A, and the call request is used to request to push the content of C to device A for to continue playing. At this point, device C presents the content screen of C; device A presents the content screen of A, and displays a prompt message with the content "will be pushed to device B for playback"; device B presents the interface of device B, and the interface of device B displays the content " About to relay the content of device A" prompt message. It is worth noting that since the public relay component on device A is in exclusive mode, device A does not process the call request after receiving the call request from device C, but feeds back an exclusive message to device C. After receiving the exclusive message fed back by the A device, the C device presents a prompt message with the content "A device is relaying" on the interface.

Fig. 20 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application. The difference between this example and the example shown in Figure 19 is that when device A interacts with device B to push the content of A to device B, device C, device D, and device E all send call requests to device A, requesting that device C The content, D content and E content are pushed to the A device to continue playing on the A device. This example is the same as the example shown in Figure 18. Since the public relay component on the A device is in the exclusive mode, the A device does not make a call request after receiving the call request from the C device, D device, and E device. Instead, an exclusive message is fed back to the C device, the D device, and the E device respectively. After receiving the busy message fed back by the A device, the C device, the D device, and the E device present a prompt message with the content "A device is relaying" on their respective interfaces.

Fig. 21 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push the content of A to device B, device C sends a call request to device B, and the call request is used to request to push the content of C to device B for Continue playing. At this time, device C presents the content screen of C; device A presents the content screen of A, and displays a prompt message with the content "will be pushed to device B for playback"; device B presents the interface of device B, and the interface of device B displays the content " About to relay the content of device A" prompt message. It is worth noting that, based on the same processing logic as the example shown in Figure 19, since the public relay component on device B is in the exclusive mode, device B does not process the call request after receiving the call request from device C , but feeds back an exclusive message to the C device. After receiving the exclusive message fed back by the B-device, the C-device presents a prompt message with the content "B-device is in relay state" on the interface.

Fig. 22 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application. The difference between this example and the example shown in Figure 19 is that when device A interacts with device B to push content from A to device B, device C, device D, and device E all send call requests to device B, requesting that device C The content, the D content and the E content are pushed to the B device to continue playing on the B device. Since the public relay component on device B is in the exclusive mode, after receiving the call request from device C, device D, and device E, device B did not process the call request, but reported to device C, device D and device E respectively. The E-device returns an exclusive message. After receiving the exclusive message fed back by the B-device, the C-device, the D-device, and the E-device present a prompt message with the content "Device B is relaying" on their respective interfaces.

Fig. 23 is a schematic diagram of another relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push the content of A to device B, both device C and device D send call requests to device A, requesting to push content C and content D to device A respectively. The playback continues on the A device, and both the E device and the F device send call requests to the B device, requesting that the E content and the F content be pushed to the B device to continue playing on the B device. Since both device A and device B are in the exclusive mode, after receiving the call request sent by device C and device D, device A feeds back an exclusive message to device C and device D respectively. The displayed content is the prompt message "A device is in the relay state"; after receiving the call request sent by E device and F device, B device sends an exclusive message to E device and F device respectively, and E device and F device A prompt message with the content "Device B is in relay state" is displayed on the respective interface.

In some embodiments, the working state of the public relay component is divided into two types, one is a busy state, and the other is an idle state. Wherein, the busy state and the idle state are complementary, that is, the public relay component is in the idle state if it is not in the busy state. It should be noted that the busy state and the idle state may be defined according to different standards. In other words, in different embodiments, the busy state of the public relay component may be different working states, and the corresponding idle states may also be different.

In some embodiments, when a terminal device acts as a push terminal device and interacts with another or more terminal devices to push certain content to the one or more terminal devices, the public The relay component is busy. When a certain terminal device acts as a receiving terminal device and interacts with another or multiple terminal devices to receive the content pushed by the one or multiple terminal devices and relay play the content, the public relay component on the terminal device is in the busy state. In other words, the busy state refers to the state that a terminal device is in when it performs relay interaction with other terminal devices.

In some optional implementation manners, when the public relay component executes S609 to S615 in FIG. 6 , the public relay component is in a busy state, otherwise it is in an idle state. More specifically, when the public relay component executes S609 in FIG. 6 , the public relay component enters a busy state, and when the public relay component finishes executing S615 , the public relay component changes from a busy state to an idle state.

In other optional implementation manners, when the public relay component executes S607 to S615 in FIG. 6 , the public relay component is in a busy state, otherwise it is in an idle state. More specifically, when the public relay component executes S607, the public relay component enters a busy state, and when the public relay component executes S615, the public relay component changes from a busy state to an idle state.

In some embodiments, when a certain terminal device is in an idle state, in response to receiving a relay request sent by another or more terminal devices, execute the one or more relay requests, and update the current state from the idle state to busy state.

In some embodiments, when a certain terminal device is in an idle state, in response to a command input by the user indicating that the currently presented target content is pushed to another or more terminal devices, a relay is sent to the one or more terminal devices. Request, and update the current status from idle to busy.

For ease of description, terms such as "first", "second" and "third" are used in the following embodiments to distinguish each terminal device in an interaction scenario. These terms do not specifically refer to an end device, and it should be understood that the terms so used are interchangeable under appropriate circumstances.

In some embodiments, when the public relay component on the first terminal device is in a busy state due to the relay interaction with the second terminal device, if a call request sent by the third terminal device is received, it will be displayed on the interface. The relay information option corresponding to the call request, so that the user can understand the content of the call request. Optionally, the device information of the third terminal device and key information of the specified content can be displayed in the relay information option, such as the device name of the third terminal device and the content name of the specified content. At this point, the user may instruct the first terminal device to execute the call request by selecting the relay information option. In response to the user operation, the first terminal device executes the call request to present specified content corresponding to the call request. In this way, the user can be prevented from missing the content pushed by the third terminal device.

In some embodiments, when the public relay component on the first terminal device is in a busy state due to the relay interaction with the second terminal device, if a call request sent by the third terminal device is received, it will be displayed on the interface. The relay information option corresponding to the call request, so that the user can understand the content of the call request. At this time, the user may interrupt the interaction between the first terminal device and the second terminal device through a predetermined operation. If the public relay component on the first terminal device receives an interrupt operation input by the user, it interrupts the relay interaction with the second terminal device, and processes the call request sent by the third terminal device. If the public relay component on the first terminal device does not receive the interrupt operation input by the user, it will continue the relay interaction with the second terminal device without processing the call request sent by the third terminal device.

Fig. 24 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push the content of A to device B, device C sends a call request to device A, and the call request is used to request to push the content of C to device A for Continue playing. Since the public relay component on device A is busy, after receiving the call request from device C, the public relay component on device A will display the content on the interface of device A as " Device C requests to push C content, do you want to interrupt the current relay? Press the confirm button to interrupt". At this point, the user can input an interrupt operation by pressing the confirm key. If the public relay component on device A receives an input interrupt operation, it will interrupt the interaction process with device B, process the call request sent by device C, and finally continue to play C content on device A. If the public relay component on the A device does not receive the input interruption operation, it will continue the interaction process with the B device without processing the call request sent by the C device, and feed back a busy message to the C device.

Fig. 25 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push the content of A to device B, device C sends a call request to device B, and the call request is used to request to push the content of C to device B for Continue playing. Since the public relay component on device B is in a busy state, after receiving the call request from device C, device B executes the interaction process with device A, and displays the content on the interface of device B as "C device requests to push C Content, do you want to interrupt the current relay? Press the confirm key to interrupt". At this point, the user can input an interrupt operation by pressing the confirm key. If the public relay component on device B receives an input interrupt operation, it will interrupt the interaction process with device A, process the call request sent by device C, and finally continue to play C content on device B. If the public relay component on device B does not receive the input interruption operation, it continues the interaction process with device A without processing the call request sent by device C, and feeds back a busy message to device C.

In some embodiments, if the public relay component on the terminal device receives a busy message returned by the target receiving device after sending a call request to the target receiving device, corresponding user prompt information is displayed on the interface.

It should be understood that if a terminal device receives a call request sent by another terminal device when it is busy, it can prompt the user in various appropriate ways, not limited to the content of the above example as "C device requests push C content, do you want to interrupt the current relay? Press the confirm key to interrupt". For example, according to the received call request, the relay information corresponding to the call request may be displayed on the device interface, and the relay information includes but not limited to push terminal device information and push content information. For example, in the example shown in Figure 26, if the public relay component on device A receives the call request sent by device C, the relay information option will be displayed on the interface of device A, and the information of device C and C content information will be displayed on the relay information option .

In some embodiments, when the public relay component on the first terminal device is in a busy state due to the relay interaction with the second terminal device, if multiple call requests sent by the third terminal device are received, it will be displayed on the interface Relay information options corresponding to each call request to let the user know what each call request is about. At this point, the user may instruct the first terminal device to perform one or more call requests by selecting one or more relay information options. The first terminal device executes at least one target relay request in response to the instruction input by the user by specifying at least one target relay information option, and executes at least one target relay request to present the specified content corresponding to each target relay request, thereby preventing the user from missing Content pushed by the third terminal device. For a relay request corresponding to a relay information option not specified or selected by the user, a busy message is returned to the terminal device that sent the relay request.

In addition, the user can interrupt the interaction between the first terminal device and the second terminal device through a predetermined operation, and can select one or more relay information options to specify the content to be relayed. If the public relay component on the first terminal device receives an interruption operation input by the user and a selection operation on one or more relay information options, it will interrupt the interaction with the second terminal device, and simultaneously respond to the user-selected The call request corresponding to the relay information option is processed. If the public relay component on the first terminal device does not receive the interruption operation input by the user, it continues to interact with the second terminal device without processing call requests sent by other terminal devices.

In some embodiments, if the user selects multiple relay information options to designate multiple content to be relayed, the relay component at the receiving end starts multiple target applications that support the relay capability of the corresponding target, and transmits the playback information of each target content to Send to the corresponding target application, so that each target application continues to play the corresponding content according to the received playing information. Specifically, the display of multiple content presentation windows is controlled, and each of the content presentation windows is used to present the specified content corresponding to each target relay request. Window overlay display. Wherein, the content presentation window may be an application interface of the target application.

Fig. 27 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push content A to device B, device C, device D and device E all send call requests to device A, requesting to push content C, content D and content E respectively to the A-device to resume playback on the A-device. Since the public relay component on device A is in a busy state, after receiving these three call requests, it presents the relay information options corresponding to each call request in the interface, which are "C device-C content", "D device -D content" and "E equipment -E content", and the prompt message with the content "Do you want to interrupt the current relay? Press the confirm key to interrupt". At this time, the user may interrupt the interaction between the A device and the B device through the confirmation key. You can also control the content corresponding to the A device relay by selecting a relay information option. For example, when the user selects "C device-C content", the public relay component on A device will process the call request sent by C device to continue playing C content on A device. It is worth noting that the user can also select multiple relay information options at the same time to control device A to relay the content pushed by multiple devices at the same time. For example, when the user selects "C device-C content", "D device-D content", the public relay component on A device will simultaneously process the call requests sent by C device and D device to continue playing on A device C content while continuing to play D content.

Fig. 28A and Fig. 28B are schematic diagrams of user interfaces of exemplary receiver devices according to the present application. Specifically, in Fig. 27, the user selects "C device-C content", "D device-D content" and "E device -E Content" to display the user interface. In FIG. 28A , content C, content D, and content E are displayed in different windows, or in other words, content C, content D, and content E are displayed on the interface of device A in split screens. In FIG. 28B , content C is displayed in full screen, and content D and content E are displayed superimposed on content C. It should be understood that when the user selects multiple relay information options to control device A to simultaneously relay the content pushed by multiple devices, the way the receiver device presents the multiple content is not limited to the above example implementation. The present application does not limit the manner in which the receiver device presents multiple contents.

Fig. 29 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. In this example, when device A interacts with device B to push content A to device B, device C, device D and device E all send call requests to device B, requesting to push content C, content D and content E respectively to the B-device to resume playback on the B-device. Since the public relay component on device B is in a busy state, after receiving these three call requests, it presents the relay information options corresponding to each call request in the interface, which are "C device-C content", "D device -D content" and "E equipment -E content", and the prompt message with the content "Do you want to interrupt the current relay? Press the confirm key to interrupt". At this point, the user can interrupt the relay process between the B device and the A device through the confirmation key. You can also control the B device to receive the content pushed by the corresponding device by selecting a relay information option.

In some embodiments, when the public relay component on a certain terminal device is in an idle state, if multiple call requests sent by other terminal devices are received, the relay information option corresponding to each call request is displayed on the interface, so that the user understands the content of each call request. At this point, the user can select one or more relay information options to designate the terminal device to be interacted with. If the public relay component on the first terminal device receives a selection operation on one or more relay information options, it simultaneously processes the call request corresponding to the relay information option selected by the user.

Fig. 30 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The difference between this example and the example shown in FIG. 27 is that the A device receives the call request sent by the C device, the D device and the E device when its public relay component is in an idle state. Since the public relay component on device A is in an idle state, after receiving these three call requests, it only needs to present the relay information options corresponding to each call request in the interface for the user to choose, without displaying the content as " Do you want to interrupt the current relay? Press the confirm key to interrupt" prompt message.

In some embodiments, when the public relay component on the first terminal device is in a busy state due to the execution of the relay process with the second terminal device, one or more other terminal devices may be designated to the user in response to user operations Send a call request. In the implementation situation of sending a call request to multiple other terminal devices at the same time, the first terminal device will receive feedback information from the multiple other terminal devices, and the feedback information includes an exclusive message, a busy (busy) message, and playback status information any of the. The first terminal device displays corresponding prompt information on the device interface according to the feedback information of each terminal device. For example, when receiving the playback status information sent by a certain terminal device, according to the playback status revealed by the playback status information, corresponding prompt information will be presented on the interface, including playback success status and playback failure status. When receiving an exclusive message sent by a certain terminal device, a prompt message with the content "xx device is in relay state" is presented on the user interface. When receiving a busy message sent by a certain terminal device, a prompt message with the content "xx device refuses to relay" will be displayed on the interface.

Fig. 31 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The schematic diagram is specifically that device A is interacting with device B to push content A to device B, device B presents content B, and an optional receiving end When the device information list is composed of device information, the interface status of each device after sending a call request for pushing B content to C1 device, C2 device, and C3 device respectively in response to user operations. Wherein, since the C1 device is in the exclusive state when receiving the call request, it returns an exclusive message to the B device, and the B device presents a prompt message on the interface with the content "C1 device is in the relay state". Since the C2 device was busy when it received the call request, and the user did not terminate the relay process between the C2 device and other devices, the C2 device fed back a busy message to the B device, and the B device displayed the content on the interface as "C2 device Denied Relay" prompt message. The C3 device responds to the call request, and starts the content application that supports the call request, and successfully resumes playing the B content, so the C3 device returns to the B device the playback status information indicating that the playback is successful, and the B device presents the content on the interface as " Successfully pushed to the C3 device" prompt message.

In some embodiments, if the first terminal device receives call requests sent by multiple second terminal devices in the idle state, it can be judged according to the push-side application identifier contained in each call request that each second terminal device provides Whether the application of the target content is the same as every application on the first terminal device; The call request sent by the terminal equipment is processed. For example, when a second terminal device requests to continue presenting target content that is presented by a media center application on the second terminal device, and the first terminal device also has a media center application, then the The call request is processed. If there are multiple second terminal devices that provide the same application with the target content as an application on the first terminal device, the corresponding relay information options are displayed according to the call requests sent by the multiple second terminal devices, so that The user understands the content of these call requests. At this point, the user may instruct the first terminal device to perform one or more call requests by selecting one or more relay information options. If the application that provides the target content on each second terminal device is different from the application on the first terminal device, display the corresponding relay information option according to the call request sent by each second terminal device, so that the user can understand these call requests Content. At this point, the user may instruct the first terminal device to perform one or more call requests by selecting one or more relay information options. In some embodiments, when the public relay component on the first terminal device is in a busy state due to the execution of the relay process with the second terminal device, it may respond to the user operation and send a message to one or more receiving terminals designated by the user The device sends a call request, and can receive call requests sent by multiple push-end devices at the same time.

Fig. 32 is a schematic diagram of a relay scenario according to an exemplary embodiment of the present application. The schematic diagram is specifically that device A is interacting with device B to push content A to device B, device B presents content B, and an optional receiving end The device information list composed of device information, and the interface status of each device after receiving the call request sent by D1 device, D2 device and D3 device at the same time. Among them, in addition to displaying the device information list consisting of "C1 device", "C2 device" and "C3 device", device B also displays relay information options corresponding to the call requests sent by device D1, device D2 and device D3 respectively , which are "D1 device-D1 content", "D2 device-D2 content" and "D3 device-D3 content". At this time, on the one hand, the user can select one or more receiver device information options in the device information list to specify the target receiver device, so that the B device sends a call to push the B content to the user-specified receiver device Request, on the other hand, can interrupt the relay process between device B and device A through a predetermined operation, and select one or more relay information options to specify the target push device to relay the content pushed by the target push device.

Referring to Figure 33, since the user selects "C1 device" and "C2 device" in the scene shown in Figure 32, the public relay component on B device sends a call request to C1 device and C2 device; since the user interrupts B device and A device The relay process between them, and select "D1 device-D1 content", so B device plays D1 content in relay.

It should be noted that the steps performed by the public relay component involved in the above embodiments may be divided and coordinated by functional modules inside the public relay component.

Exemplarily, Fig. 34 is an interaction flowchart according to an exemplary embodiment of the present application. As shown in Figure 34, the public relay component includes an interaction center module, a state management module, an interface display module, a protocol processing module and a logic control module. On the push end device, after the content application presents the target content in step S3401, a communication connection is established with the interaction center module in step S3402, and based on the communication connection in step S3403, its own relay capability (i.e. target relay capability) is sent to the interaction center module. In step S3404, the interaction center module instructs the protocol processing module to search for external terminal devices supporting the target relay capability by sending the target relay capability to the protocol processing module. After the protocol processing module obtains the target relay capability in step S3405, select the target communication protocol channel, based on the target protocol channel, in step S3406, search for an external terminal device that supports the target relay capability through the target communication protocol component corresponding to the target protocol channel, and Step S3407 obtains the device information list. In step S3408, the protocol processing module sends the device information list to the interface display module, and at the same time, in step S3409, the device search result is fed back to the interaction center module. In step S3410, the interaction hub module sends the device search result to the content application. The content application displays the interface object for triggering the relay operation on the interface according to the device search result, receives the relay operation input by the user through the interface object in step S3411, and sends the relay command to the interaction central module in step S3412. After receiving the relay command in step S3413, the interaction hub module notifies the interface display module to present the device information list in step S3414. In step S3415, the interface presentation module receives the user's selection operation on the target receiver device, and in step S3416, sends the information of the target receiver device to the protocol processing module to instruct the protocol processing module to call the target receiver device. After steps S3417-3419 and S3421, the protocol processing module receives the target receiver device information, instructs the interaction center module to request the content application for the playback information of the target content, and the interaction center module returns the requested playback information of the target content to the protocol processing module . The protocol processing module selects the target communication protocol channel in step S3420, and instructs the logic control module to call the target receiving end device based on the target protocol channel in step S3422. The logic control module judges in step S3423 whether it is currently in the exclusive mode, and if it is in the exclusive mode, it notifies the interface interaction module in step S3424 to present a first prompt message in step S3426 to remind the user. If not in the exclusive module, call the target receiver device based on the target protocol channel in step S3425. After the call is completed, receive the playback status information returned by the target receiver device in step S3427, and send the playback status information to the status management module in step S3428. In steps S3429 and S3430, the state management module instructs the interface presentation module to present a second prompt message according to the playback state information to prompt the user.

Exemplarily, Fig. 35 is an interaction flowchart according to an exemplary embodiment of the present application. As shown in Figure 35, the public relay component includes an interaction center module, a state management module, an interface display module, a protocol processing module and a logic control module. On the receiving end device, in step S3501 the target communication protocol component receives the call request from the push end device, and in step S3502 sends the call request to the logic control module. In step S3503, the logic control module judges whether it is currently in the exclusive mode. If it is in the exclusive module, then in step S3504, the target protocol component returns an exclusive message to the push end device. If it is not in the exclusive mode, it continues to judge whether it is currently idle in step S3506. state. If it is currently in the idle state, determine the target application indicating the target relay capability in step S3507, and instruct the interaction center module to start the target application in step S3508. In step S3509, the interaction hub module starts the target application, and sends the playing information of the target content to the target application. The target application continues to present the target content according to the playing information of the target content, and returns the playing state information to the interaction hub module in step S3510. In step S3514, the interaction hub module sends the playback status information to the status management module. In steps S3515-S3517, the status management module instructs the logic control module to return the playback status information to the push device, and at the same time, in steps S3518-S3519, instructs the interface display module to present a prompt message according to the playback status information. If it is currently in a busy state, in step S3520, instruct the interface display module to display the corresponding relay information according to the call request, and display an interruption operation reminder message. In step S3521, the interface display module displays the corresponding relay information according to the call request, and displays an interruption operation reminder message. In step S3522, it is judged whether an interruption operation is received, and in step S3523, after receiving the input interruption operation, it instructs the logic control module to interrupt Current relay. In step S3524, when an input selection operation on relay information is received, in step S3525, the logic control module is instructed to process the corresponding call request.

For convenience of explanation, the above description has been made in conjunction with specific implementation manners. However, the above exemplary discussion is not intended to be exhaustive or to limit the implementations to the precise forms disclosed above. Many modifications and variations are possible in light of the above teachings. The selection and description of the above embodiments are to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various modified embodiments suitable for specific use considerations.

Claims (45)

1. A display device comprising:

   a display for presenting content; and

   Controller, configured to execute:

   receiving a relay request from the push-end device, the relay request including information related to the application of the push-end device and playback information related to the target content provided by the application of the push-end device to request presentation of the target content;

   determining a target application on the display device according to information related to the application of the push terminal device, the target application being an application with the highest degree of matching with the application of the push terminal device or an application specified by a user; and

   Starting the target application, and controlling the target application to present the target content according to the playing information related to the target content.
2. The display device according to claim 1, wherein the information related to the application of the push-end device includes a target relay capability and an application identifier of the application of the push-end device, and the controller is further configured to:

   determining at least one candidate application supporting the target relay capability according to the relay capability of each application on the display device;

   The target application is determined from the candidate applications according to the application identifier.
3. The display device according to claim 2, wherein the controller is further configured to:

   When there is an application with the same application identifier as the application of the push device in the candidate applications, determine the candidate application with the same application identifier as the target application; and

   If there is no application in the candidate applications having the same application identifier as the application of the pushing device, the target application is determined from the candidate applications according to a preset rule.
4. The display device according to claim 3, wherein the controller is further configured to:

   sorting the candidate applications according to a preset sorting rule to determine the candidate application with the highest priority;

   Determining the candidate application with the highest priority as the target application.
5. The display device according to claim 3, wherein the controller is further configured to:

   determine the category of said targeted content;

   According to a preset correspondence, a default application corresponding to the category of the target content among the candidate applications is determined as the target application.
6. The display device according to claim 1, wherein the information related to the application of the push-end device includes a target relay capability of the application of the push-end device, and the controller is further configured to:

   determining at least one candidate application supporting the target relay capability according to the relay capability of each application on the display device;

   presenting an application list including application options corresponding to each candidate application;

   A selection operation of any of the application options by the user is received, and the candidate application selected by the user is determined as the target application.
7. The display device according to claim 1, wherein the information related to the application at the push end includes a target relay capability of the application at the push end, and the controller is further configured to:

   determining at least one candidate application supporting the target relay capability according to the relay capability of each application on the display device;

   Obtain the latest startup time corresponding to each of the candidate applications;

   The application with the latest startup time among the candidate applications is determined as the target application.
8. The display device according to claim 1, wherein the controller is further configured to:

   Responsive to starting the display device, acquiring relay capability information of the display device, where the relay capability information includes the first-level relay capability of each application on the display device, and/or the second-level relay capability of some applications, the The secondary relay capability of the application belongs to the primary relay capability of the application, and the secondary relay capability of the application is the relay capability of the application in different working modes;

   Registering the relay capability information in a LAN protocol component, the LAN protocol component is used to communicate with an external terminal device through a LAN protocol channel; and/or

   Sending the relay capability information and the identification information of the display device to a server, so that the server stores the relay capability information of the display device and the identification information of the display device in correspondence.
9. The display device according to claim 8, wherein the controller is further configured to:

   receiving a capability query message from the push device, where the capability query message includes the target relay capability of the application of the push device;

   judging whether there is an application supporting the target relay capability on the display device,

   Wherein, for an application with a second-level relay capability, when the first-level relay capability and at least one second-level relay capability of the application match the target relay capability, the application supports the target relay capability; The application of the secondary relay capability, when the primary relay capability of the application matches the target relay capability, the application supports the target relay capability;

   Sending a response message to the push end according to the judgment result.
10. The display device according to claim 8, wherein the controller is further configured to:

    judging whether the first-level relay capability applied on the display device matches the target relay capability;

    If the first-level relay capability of the application matches the target relay capability and the application has a second-level relay capability, determine whether the second-level relay capability of the application matches the target relay capability; determining that the application is a candidate application when at least one secondary relay capability of the application matches the target relay capability;

    In a case where the first-level relay capability of the application matches the target relay capability and the application does not have the second-level relay capability, the application is determined to be a candidate application.
11. The display device according to claim 1, wherein the controller is further configured to:

    In the process of relay interaction with the push-end device, in response to receiving a relay request from an additional push-end device, acquire the current working mode of the display device;

    Determine whether the display device performs relay interaction with the additional push end device based on the current working mode.
12. The display device according to claim 11, wherein the controller is further configured to:

    When the current working mode is an exclusive mode, return an exclusive message to the additional push device;

    When the current working mode is the non-exclusive mode, according to the relay request from the additional push-end device, the corresponding relay request prompt information is displayed, so as to prompt the user to input trigger execution or give up the communication with the additional push-end device Commands for relay interactions.
13. The display device according to claim 12, wherein, when the current working mode is the non-exclusive mode, the controller is further configured to:

    The interrupt operation prompt information is displayed to prompt the user to input a command to trigger the interrupt operation, and the interrupt operation is used to control the display device to interrupt the relay interaction with the push terminal device.
14. The display device according to claim 12, wherein the relay request from the additional push device includes target relay capability and playback information related to the target content; when the current working mode is the non-exclusive mode, The controller is further configured to:

    launching a target application supporting the target relay capability in response to a user-input command triggering execution of the relay interaction;

    controlling the target application to continue presenting the target content according to the playing information.
15. The display device according to claim 12, wherein the controller is further configured to:

    Acquiring the switch state of the device exclusive function of the display device;

    If the device exclusive function is turned on, then determine that the current working mode is the exclusive mode;

    If the device exclusive function is off, it is determined that the current working mode is the non-exclusive mode.
16. The display device according to claim 11, wherein, when the current working mode is the non-exclusive mode, the controller is further configured to:

    Responsive to receiving a relay request from at least one push end device, presenting relay information options corresponding to each relay request;

    In response to a command input by the user through the relay information option to indicate at least one relay target request, the at least one relay target request is executed to present target content corresponding to each relay target request.
17. The display device according to claim 16, wherein the controller is further configured to:

    Responding to a command input by the user indicating that the currently presented target content is pushed to at least one receiving end device, sending a relay request to each of the receiving end devices respectively, so as to request each of the receiving end devices to present the target content .
18. The display device according to claim 17, wherein the controller is further configured to:

    Receive feedback information sent by the receiving end device, where the feedback information includes one of playback status information, an exclusive message, and a busy message;

    According to the feedback information, corresponding prompt information is displayed, wherein when the types of the feedback information are different, the corresponding prompt information is different.
19. The display device according to claim 16, wherein the controller is further configured to:

    Controlling the display of at least one content presentation window, each of the content presentation windows is used to present the target content corresponding to each of the target relay requests, wherein the at least one content presentation window is tiled, or multiple content presentation windows At least part of the content presentation window is superimposed and displayed.
20. The display device according to claim 16, wherein the controller is further configured to:

    For a relay request corresponding to a relay information option not selected by the user, a busy message is returned to the corresponding pusher.
21. The display device according to claim 1, wherein the controller is further configured to:

    In response to a command to relay the target content input by the user, control presents first prompt information to prompt the user to input a cancel or confirm command to relay the target content within a predetermined time period.
22. The display device according to claim 21, wherein the controller is further configured to:

    When a command input from the user is received within a predetermined time period, the transmission of the relay request is controlled based on the type of the command, wherein, in response to the confirmation command input by the user, the relay request is sent to the target receiving end device to request the The target receiver device presents the target content, or cancels sending the relay request to the target receiver in response to a cancel command input by the user; and

    When no command input from the user is received within the predetermined time period, the relay request is sent to the target receiving end device at the end of the predetermined time period, and the display of the first prompt information is ended.
23. The display device according to claim 22, wherein the controller is further configured to:

    In response to receiving the playing state information from the target receiving end device, control to display the second prompt information or the third prompting information, the playing state information indicating that the target receiving end device succeeds or fails in presenting the target content.
24. The display device according to claim 21, wherein the controller is further configured to:

    In response to the cancel command input by the user within a predetermined time period, displaying fourth prompt information is controlled.
25. The display device according to claim 21, wherein the controller is further configured to:

    In response to receiving a cancel message from the target receiver device, controlling display of fifth prompt information.
26. The display device according to claim 1, wherein the controller is further configured to:

    In response to a user-input command to relay the target content, sending the relay request to the target receiver device, so that the target receiver device presents the target content according to the relay request; and

    In response to receiving a relay cancel command input from a user within a preset time period, a relay cancel request is sent to the target receiver device, so that the target receiver device cancels presenting the target content.
27. The display device according to claim 1, wherein the controller is further configured to:

    In response to receiving the relay request from the push device, control presenting first prompt information to prompt the user to input a command to cancel or confirm relay within a predetermined time period.
28. The display device according to claim 27, wherein the controller is further configured to:

    When a command from a user input is received within a predetermined time period, the execution of the relay request is controlled based on the type of the command, wherein in response to the confirmation command input by the user, the relay request is executed to present the target content;

    When no command input from the user is received within a predetermined time period, the relay request is executed at the end of the predetermined time period to present the target content.
29. The display device according to claim 28, wherein the controller is further configured to:

    After the relay request is executed, play status information is sent to the push device, where the play status information indicates whether the display device succeeds or fails in presenting the target content.
30. The display device according to claim 28, wherein the controller is further configured to:

    In response to the cancel command input by the user within the predetermined time period, controlling the display of second prompt information;

    And, send a cancel message to the push device.
31. The display device according to claim 27, wherein the controller is further configured to:

    In response to receiving the relay cancellation request sent by the push device, third prompt information is presented.
32. The display device according to claim 28, wherein the controller is further configured to:

    If the presentation of the target content is successful, the display of the fourth prompt information is controlled.
33. The display device according to claim 1, wherein the controller is further configured to:

    When presenting the target content provided by the content application, searching for a receiver device that supports the target relay capability, where the target relay capability refers to the capability required by the receiver device to present the target content;

    Presenting the searched device information of the receiver device, so that the user specifies a target receiver device from the receiver devices;

    Responding to a push command input by the user, acquiring playback information related to the target content from the content application;

    Sending a relay request to the target receiver device according to the playing information, so that the target receiver device presents the target content.
34. The display device according to claim 33, wherein the controller is further configured to:

    Obtaining the relay capability of the content application in response to a device search command input by the user to determine the target relay capability; or

    In response to a device search request sent by the content application, the target relay capability is obtained from the device search request, wherein the content application sends the device search request when a preset condition is met.
35. The display device according to claim 33, wherein the controller is further configured to:

    When at least one receiving device supporting the target relay capability is found, displaying an interface object for triggering presentation of the device information;

    presenting a device information list in response to a device presentation command input by the user through the interface object, the device information list including a plurality of device options, the device options corresponding to the device information; and

    It is determined that the push command is received when a command input by the user to select a target device option is received, and the target device option corresponds to the device information of the target receiving end device.
36. The display device according to claim 33, wherein the controller is further configured to:

    controlling playback of the target content by the content application based on a target setting parameter,

    Wherein, when the target setting parameter is a first value, the content application is controlled to stop playing the target content, and when the target setting parameter is a second value, the content application is controlled to continue playing the target content .
37. The display device according to claim 36, wherein the controller is further configured to:

    The target setting parameters are acquired based on playback state information received from the target sink device.
38. The display device according to claim 33, wherein the controller is further configured to:

    Acquiring the relay capability of each application in response to the display device being turned on;

    registering the relay capability of the application in a LAN protocol component for communicating with an external terminal device through a LAN protocol channel; and/or

    Sending the relay capability of the application and the identification information of the display device to the server, so as to store the relay capability of the application on the display device and the identification information of the display device correspondingly.
39. A content continuation method comprising:

    receiving a relay request from the push end device, the relay request including information related to the application of the push end device and playback information related to the target content provided by the application of the push end device, so as to request to present the content on the display device stated target content;

    determining a target application on the display device according to information related to the application at the push end, the target application being an application with the highest degree of matching with the application at the push end or an application specified by a user; and

    Starting the target application, and controlling the target application to present the target content according to the playing information related to the target content.
40. The method of claim 39, wherein the method further comprises:

    In the process of relay interaction with the push-end device, in response to receiving a relay request from an additional push-end device, acquire the current working mode of the display device; and

    determining whether the display device performs relay interaction with the additional push end device based on the current working mode,

    Wherein, when the current working mode is the exclusive mode, an exclusive message is returned to the additional push device.
41. The method of claim 39, wherein the method further comprises:

    When presenting the target content, in response to a command input by the user to push the target content, send a relay request to the target receiver device, where the relay request is used to request the target receiver device to present the target content;

    When receiving the exclusive message sent by the target receiver device, presenting first prompt information to show that the target receiver device is in an interactive state,

    Wherein, the exclusive message is sent by the target receiving end device in response to receiving a relay request from other push end devices in exclusive mode.
42. The method according to claim 40, wherein said method further comprises:

    Responding to a command input by a user by specifying at least one relay target information option to execute at least one relay target request command, executing the at least one relay target request to present specified content corresponding to each relay target request.
43. The method of claim 39, wherein the method further comprises:

    In response to an input command indicating that the currently presented target content is pushed to the target receiving end device, controlling the presentation of first prompt information to prompt the user to input a command to cancel or confirm the relay within a predetermined period of time,

    Wherein, in response to the confirmation command input by the user within the predetermined time period, a relay request is sent to the target receiving end device to request the target receiving end device to present the target content; cancel the relay request sent to the target receiver.
44. The method of claim 39, wherein the method further comprises:

    In response to receiving the relay request from the push device, control presenting first prompt information to prompt the user to input a command to cancel or confirm the relay within a predetermined period of time;

    Wherein, in response to the confirmation command input by the user within the predetermined time period, the relay request is executed to present the target content.
45. The method of claim 39, wherein the method further comprises:

    When presenting the target content provided by the content application, searching for a receiver device that supports the target relay capability, where the target relay capability refers to the capability required by the receiver device to present the target content;

    Presenting the searched device information of the receiver device, so that the user specifies a target receiver device from the receiver devices;

    Responding to a push command input by the user, acquiring playback information related to the target content from the content application;

    Sending a relay request to the target receiver device according to the playing information, so that the target receiver device presents the target content.

Images