CN116634211A

CN116634211A - Display device and content connection method

Info

Publication number: CN116634211A
Application number: CN202310537857.6A
Authority: CN
Inventors: 马晓燕; 庞秀娟; 贾亚洲; 宋子全; 马乐
Original assignee: Hisense Visual Technology Co Ltd
Current assignee: Hisense Visual Technology Co Ltd
Priority date: 2021-09-18
Filing date: 2021-09-29
Publication date: 2023-08-22
Also published as: CN113766301A; WO2023040419A1; CN113766292B; CN113766036A; CN113794918A; CN113766301B; CN113891130A; CN113891129A; CN113766036B; CN113766292A

Abstract

The application discloses a display device and a content connection method.A display device determines an application with highest matching degree with a pushing end application or an application designated by a user on the display device as a target application according to pushing end application information in a relay request after receiving the relay request sent by the pushing end device and used for requesting to continuously present target content provided by the pushing end application, and controls the target application to continuously present the target content according to playing information of the target content. Therefore, the success rate of continuing to present the target content is guaranteed to the greatest extent, and the conditions of continuous failure or continuous error are avoided.

Description

Display device and content connection method

The present application was filed in the division of China patent office, application No. CN202111151401.3, entitled "display device" at 29 of 9 months 2021, the entire contents of which are incorporated herein by reference.

Technical Field

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

Background

Display type devices, such as smart televisions, smart screens, etc., can provide users with play pictures, such as audio, video, pictures, etc., such as network video programs, live television programs, and can also provide users with various applications and service content, such as network games, AI fitness, online education, etc.

In some scenarios, for example, in a home, there are usually a plurality of terminal devices, such as smart televisions, refrigerator smart screens, smart speakers, etc., which can communicate with each other, and also can communicate with terminal devices outside the scenario based on a wide area network. Wherein each terminal device may present content to the user including, but not limited to, music, video, conversation, text, pictures, and the like. How to realize the sharing and continuous playing of the content between the devices so as to improve the user experience becomes a technical problem to be solved.

Disclosure of Invention

The application provides a display device and a content connection method.

In a first aspect, the present application provides a display apparatus comprising:

a display for presenting content;

a speaker for presenting the content in conjunction with the display;

a communicator for communicating with an external terminal device;

a controller configured to perform:

receiving a relay request sent by a pushing end device, wherein the relay request is used for requesting to continuously present target content provided by a pushing end application, and the relay request comprises pushing end application information and playing information of the target content;

determining a target application according to the pushing end application information, wherein the target application is an application with highest matching degree with the pushing end application or an application designated by a user on the display equipment;

And starting the target application, and controlling the target application to continuously present the target content according to the playing information of the target content.

In a second aspect, the present application further provides a content connection method, where the method includes:

According to the technical scheme, after receiving the relay request sent by the pushing end device and used for requesting to continue to present the target content provided by the pushing end application, the display device determines the application with the highest matching degree with the pushing end application or the application designated by the user on the display device as the target application according to the pushing end application information in the relay request, and controls the target application to continue to present the target content according to the playing information of the target content. Therefore, the success rate of continuing to present the target content is guaranteed to the greatest extent, and the conditions of continuous failure or continuous error are avoided.

Drawings

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

fig. 2 is a block diagram of the hardware configuration of the control apparatus 100 shown in some embodiments of the present application;

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

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

FIG. 5 illustrates a software configuration block diagram of a common relay assembly in accordance with an exemplary embodiment;

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

FIG. 7 illustrates a display device user interface;

FIG. 8 illustrates a display device user interface;

FIG. 9 illustrates a display device user interface;

FIG. 10 illustrates a display device user interface;

FIG. 11A illustrates a display device user interface;

FIG. 11B illustrates a display device user interface;

FIG. 11C illustrates a display device user interface;

FIG. 12 illustrates a display device user interface;

fig. 13 is a schematic diagram of a push scenario according to an exemplary embodiment of the present application;

FIG. 14 illustrates a display device user interface;

FIG. 15 illustrates a display device user interface;

FIG. 16 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 17 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 18 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 19 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 20 is a schematic view of another relay scenario illustrated in accordance with an exemplary embodiment of the present application;

FIG. 21 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 22 is a schematic view of another relay scenario illustrated in accordance with an exemplary embodiment of the present application;

FIG. 23 is a schematic view of another relay scenario illustrated in accordance with an exemplary embodiment of the present application;

FIG. 24 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 25 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 26 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 27 is a schematic illustration of a relay scenario in accordance with an exemplary embodiment of the present application;

FIGS. 28A and 28B are diagrams of a receiving-end device user interface according to an exemplary embodiment of the present application;

FIG. 29 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 30 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 31 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 32 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 33 is a schematic view of a relay scenario in accordance with an exemplary embodiment of the present application;

FIG. 34 is an interactive flow diagram according to an exemplary embodiment of the present application;

fig. 35 is an interactive flow diagram illustrating an exemplary embodiment of the present application.

Detailed Description

For the purposes of making the objects and embodiments of the present application more apparent, an exemplary embodiment of the present application will be described in detail below with reference to the accompanying drawings in which exemplary embodiments of the present application are illustrated, it being apparent that the exemplary embodiments described are only some, but not all, of the embodiments of the present application.

It should be noted that the brief description of the terminology in the present application is for the purpose of facilitating understanding of the embodiments described below only and is not intended to limit the embodiments of the present application. Unless otherwise indicated, these terms should be construed in their ordinary and customary meaning.

The terms first, second, third and the like in the description and in the claims and drawings are used for distinguishing between similar or similar objects or entities and not necessarily for describing a particular sequential or chronological order, unless otherwise indicated. It is to be understood that the terms so used are interchangeable under appropriate circumstances.

The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a product or apparatus that comprises a list of elements is not necessarily limited to all elements explicitly listed, but may include other elements not expressly listed or inherent to such product or apparatus.

The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware or/and software code that is capable of performing the function associated with that element.

Fig. 1 is a schematic diagram of an application scenario according to some embodiments of the present application, which is intended to show a scenario in which a plurality of terminal devices, including but not limited to devices having data transceiving and processing functions and image display functions and/or sound output functions, exist, and a server that can communicate with the terminal devices. In the scenario shown in fig. 1, the display device 200, the mobile terminal 300, the refrigerator smart screen 400, the smart box 500, the sound box device 600, and the server 700 are included.

Based on the everything interconnection technology, communication connection can be established among a plurality of terminal devices in the scene. Communication protocols that implement the above-described everything interconnection may include a local area network protocol, a wide area network protocol, and a short-range wireless communication protocol that is not limited by a network. The local area network protocol includes but is not limited to HSP communication protocol, the wide area network protocol includes but is not limited to AIOT protocol, and the short-range wireless communication protocol includes but is not limited to Bluetooth transmission protocol and infrared transmission protocol. Based on the difference of the types of the communication protocols, the communication protocol channels of the terminal device can be divided into a local area network protocol channel based on a local area network, a wide area network protocol channel based on a wide area network and other protocol channels. Other protocol channels include bluetooth protocol channels, infrared protocol channels, etc. Each protocol channel may support multiple communication protocols. The terminal devices in the above scenario may support one or more of the aforementioned protocol channels.

The terminal device may establish a communication connection with the server to interact with the server, for example to provide various content and interaction information to the terminal device. The terminal device may be permitted to make communication connections via a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. The server 700 may be a cluster or a plurality of clusters, and may include one or more types of servers.

It should be noted that, in the similar scenario shown in fig. 1, other terminal devices may also be included, including but not limited to, a touch integrated device, a projection device, a tablet computer, a notebook computer, an intelligent cooking device, and external devices of the foregoing various terminal devices, such as a keyboard, a mouse, a game handle, and the like. The number of similar terminal devices may be one or more. For example, multiple display devices 200 may be present simultaneously in a scene.

In some embodiments, different terminal devices may control each other, or may control a designated terminal device through the control apparatus 100. For example, the user may operate the display apparatus 200 by controlling the device 100 or the mobile terminal 300. As another example, a 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 through the display device 200 or the smart device 300, etc.

In some embodiments, the control device 100 may be a remote controller, and the communication between the remote controller and the terminal device includes infrared protocol communication or bluetooth protocol communication, and other short-range communication modes, and interact with the terminal device through a wireless or wired mode. The user can input user instructions through keys on a remote controller, voice input, control panel input and the like to control the terminal equipment.

In some embodiments, other terminal devices are controlled through the use of applications running on the mobile terminal 300.

In some embodiments, each terminal device may also perform control in a manner other than the control apparatus 100 or other terminal devices, for example, the voice command control of the user may be directly received through a module configured inside the device to obtain the voice command, or the voice command control of the user may be received through a voice control device set outside the device.

Fig. 2 exemplarily shows a block diagram of a configuration of the control apparatus 100 in accordance with an exemplary embodiment. As shown in fig. 2, the control device 100 includes, but is 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 may receive an input operation instruction from a user, and convert the operation instruction into an instruction recognizable and responsive to the terminal device, and may perform an interaction between the user and the terminal device.

In some embodiments, the terminal device includes a controller, a memory, a communicator, and a display. In some embodiments, the terminal device may further include at least one of a modem, a detector, an external device interface, an audio output interface, a power supply, a user interface. The controller comprises a processor, a video processor, an audio processor, a graphic processor, a RAM and a ROM, and is used for inputting/outputting from a first interface to an nth interface.

Taking the display device 200 as an example, fig. 3 shows a hardware configuration block diagram of the display device 200 in accordance with an exemplary embodiment. As depicted in fig. 3, the display apparatus 200 includes, but is not limited to, at least one of a modem 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 interface.

In some embodiments, the display may be a liquid crystal display, an OLED display, 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, or other network communication protocol chip or a near field communication protocol chip, and an infrared receiver. The terminal device can establish transmission and reception of control signals and data signals with other terminal devices, control devices or servers through the communicator.

A user interface operable to receive control signals from a control device, such as an infrared remote control.

The detector is used to collect signals of the external environment or interaction with the outside. For example, the detector includes a light receiver, a sensor for collecting the intensity of ambient light; alternatively, the detector may comprise an image collector, such as a camera, which may be used to collect external environmental scenes, user attributes or user interaction gestures, or alternatively, the detector 230 may comprise a sound collector, such as a microphone, for receiving external sounds.

In some embodiments, the image collector is a camera module including a camera for collecting images and a depth-sensing camera for collecting depth information of the images, such as an RGBD camera. Through the camera module, the image and the depth information of the image can be acquired.

The external device interface may include, but is 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, or the like. The input/output interface may be a composite input/output interface formed by a plurality of interfaces.

And a controller for controlling the operation of the terminal device and responding to the operation of the user by 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 to select to display a UI object on the display, the controller may perform an operation related to the object selected by the user command.

The object may be any one of selectable objects, such as a hyperlink, an icon, or other operable control. The operations related to the selected object are: displaying an operation of connecting to a hyperlink page, a document, an image, or the like, or executing an operation of a program corresponding to the icon.

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

In some embodiments, the system of terminal devices may include a Kernel (Kernel), a command parser (shell), a file system, and an application program. The kernel, shell, and file system together form the basic operating system architecture that allows users to manage files, run programs, and use the system. After power-up, the kernel is started, the kernel space is activated, hardware is abstracted, hardware parameters are initialized, virtual memory, a scheduler, signal and inter-process communication (IPC) are operated and maintained. After the kernel is started, shell and user application programs are loaded again. The application program is compiled into machine code after being started to form a process.

Referring to FIG. 4, in some embodiments, the system is divided into four layers, from top to bottom, an application layer (referred to as an "application layer"), an application framework layer (Application Framework layer) (referred to as a "framework layer"), a An Zhuoyun row (Android run) and a system library layer (referred to as a "system runtime layer"), and a kernel layer, respectively.

In some embodiments, at least one application program is running in the application program layer, and these application programs may be a Window (Window) program of an operating system, a system setting program, a clock program, or the like; or may be an application developed by a third party developer. In particular implementations, the application packages in the application layer are not limited to the above examples.

In some embodiments, the common relay component and the at least one content application are configured in an operating system of the terminal device. The content application refers to an application program that can provide content or present content, such as a camera application, a picture resource application, a picture viewing application, a video call application, a video play application, an audio call application, an audio resource application, a map application, a reading application, and the like. The content includes pictures, audio (including call audio, audio files, and live audio streams), video (including call video, video files, live video streams), text, geographic location information, navigation information, and the like. The content presentation includes displaying pictures, geographical location information or navigation information and text, playing video files, video call pictures and live broadcasting room pictures, playing audio files, call sounds and live broadcasting room sounds, etc. The public relay assembly is used for pushing the content presented by any one content application to the external terminal equipment so as to continuously broadcast on the external terminal equipment; and the content playing device is also used for receiving the content pushed by the public relay component on the external terminal equipment and the playing information thereof and continuously playing the content through the content with the capability of playing the content.

In some embodiments, any one of the content applications may push content to other terminal devices that may establish a communication connection through a common relay component, thereby eliminating the need to configure push content functionality on each of the content applications. Any content application can receive the pushing of other terminal equipment to certain content through the public relay assembly so as to connect the capabilities of the content, and therefore the function of receiving the pushing of the content does not need to be configured on each content application. In the content pushing, receiving and continuing process, the common relay component on the pushing end device (receiving end device) is responsible for communicating with the common relay component on the receiving end device (pushing end device) so as to complete the content pushing, receiving and continuing process.

For convenience of description, the procedure of pushing, receiving and capability connection of the content, which is cooperatively performed by the pushing end device and the receiving end device, will be referred to as a relay procedure. The pushing end device is the terminal device which initiates the content pushing, and the receiving end device is the terminal device which receives the content and relays the pushing end device to continue playing the content even though the content is pushed to the target. Based on the data flow direction, the relationship between the pushing end device and the receiving end device may be described as that the pushing end device pushes a certain content to the receiving end device, and the receiving end device plays the content pushed by the pushing end device in a relay manner. It should be understood that, the terminal device according to the present application may be at least used as a receiving end device to relay and play the content pushed by other terminal devices, such as the smart speaker device to relay and play the song pushed by the mobile phone. The terminal equipment can be used as receiving end equipment and pushing content outwards, for example, a mobile phone pushes current songs to an intelligent sound box for continuous playing, and the mobile phone receives video programs pushed by an intelligent television for continuous playing.

In some embodiments, the capability continuation includes, but is not limited to, at least one of an alarm setting, an image quality parameter setting, a file co-viewing, etc. of a continuation of the media asset (e.g., video continuation, audio continuation, etc.).

Fig. 5 illustrates a software configuration block diagram of a common relay assembly, according to an exemplary embodiment. As shown in fig. 5, the common relay assembly includes an interaction hub module, a status management module, an interface display module, a protocol processing module, and a logic control module.

The interaction center module is used for carrying out interaction on the content application on the local terminal equipment. The interaction center module is internally provided with an SDK (software development kit) for calling each application program, and each application program interacts with the interaction center module by calling the SDK. For example, when a user triggers an operation for transferring the current content to a designated terminal device for playback in the content application, the content application notifies the interactive hub module to send by calling the aforementioned SDK so that the public relay component responds to the operation of the user. For another example, the interaction center module feeds back various status information in the content pushing process to the corresponding content application program.

The state management module is used for managing various state information generated in the process of interacting with other terminal equipment, such as state information representing success or failure of pushing, state information representing abnormal conditions, various notification messages and the like. The management includes, but is not limited to, classification information, discrimination information to make a corresponding process according to the discrimination result, information forwarding, and the like.

And the interface display module is used for displaying interface elements related to the relay flow, such as window objects, tabs, state information prompt boxes and various operable buttons in the user interface.

And the protocol processing module is used for selecting a protocol channel through which the terminal equipment interacts with other terminal equipment according to a preset rule, for example, selecting one of a local area network protocol channel and a wide area network protocol channel, so that the terminal equipment interacts information with other terminal equipment through the channel selected by the protocol processing module.

And the logic processing module is used for executing various logic controls involved in the relay flow, such as logic control under a certain working mode and logic control under the condition of multi-equipment interaction.

In some embodiments, the individual functional modules of the common relay component are deployed at the application layer. In other embodiments, the various functional modules of the common relay component may be deployed across layers, e.g., the interactive hub module and the interface presentation module may be deployed at the application layer, while other modules are deployed at other layers. The present application is not limited thereto. It should be noted that, to implement the content relay function, the common relay component may include more or fewer modules, and is not limited to the software composition and architecture shown in fig. 5. Based on the functions of the public relay assembly according to the embodiment of the application, other components and architectures are designed to belong to the protection scope of the application.

Referring to fig. 4, the framework layer provides an application programming interface (application programming interface, API) and programming framework for the application programs of the application layer. The application framework layer includes a number of predefined functions. The application framework layer corresponds to a processing center that decides to let the applications in the application layer act. Through the API interface, the application program can access the resources in the system and acquire the services of the system in the execution.

As shown in fig. 4, the application framework layer in the embodiment of the present application includes a manager (manager), a Content Provider (Content Provider), and the like, where the manager includes at least one of the following modules: an Activity Manager (Activity Manager) is used to interact with all activities that are running in the system; a Location Manager (Location Manager) is used to provide system services or applications with access to system Location services; a Package Manager (Package Manager) for retrieving various information about an application Package currently installed on the device; a notification manager (Notification Manager) for controlling the display and clearing of notification messages; a Window Manager (Window Manager) is used to manage bracketing icons, windows, toolbars, wallpaper, and desktop components on the user interface.

In some embodiments, the activity manager is used to manage the lifecycle of the individual applications as well as the usual navigation rollback functions, such as controlling the exit, opening, fallback, etc. of the applications. The window manager is used for managing all window programs, such as obtaining the size of the display screen, judging whether a status bar exists or not, locking the screen, intercepting the screen, controlling the change of the display window (for example, reducing the display window to display, dithering display, distorting display, etc.), etc.

In some embodiments, the system runtime layer provides support for the upper layer, the framework layer, and when the framework layer is in use, the android operating system runs the C/C++ libraries contained in the system runtime layer to implement the functions to be implemented by the framework layer.

In some embodiments, the kernel layer is a layer between hardware and software. As shown in fig. 4, the kernel layer contains at least one of the following drivers: audio drive, display drive, bluetooth drive, camera drive, WIFI drive, USB drive, HDMI drive, sensor drive (e.g., fingerprint sensor, temperature sensor, pressure sensor, etc.), and power supply drive, etc.

In some embodiments, a user may input a user command through a Graphical User Interface (GUI) displayed on a display, and the user input interface receives the user input command through the Graphical User Interface (GUI). Alternatively, the user may input the user command by inputting a specific sound or gesture, and the user input interface recognizes the sound or gesture through the sensor to receive the user input command. A user interface is an interface (e.g., physical keys on a display device body, or the like) that may be used to receive control inputs.

In some embodiments, a "user interface" is a media interface for interaction and exchange of information between an application or operating system and a user that enables conversion between an internal form of information and a form acceptable to the user. A commonly used presentation form of the user interface is a graphical user interface (Graphic User Interface, GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It may be an interface element such as an icon, a window, a control, etc. displayed in a display screen of the electronic device, where the control may include a visual interface element such as an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc.

In some embodiments, when a terminal device presents a certain content, relevant information of the content can be pushed to the terminal device appointed by the user in response to the control of the user, so that the terminal device appointed by the user can continue playing the content according to the relevant information of the content. For convenience of explanation, in the following embodiments, a terminal device that initiates content pushing is referred to as a pushing end device, and a terminal device that accepts content pushing and relay continuation is referred to as a receiving end device. It should be noted that the pushing device and the receiving device may be display devices having both an image display function and an audio output function, such as a television, a smart phone, a tablet computer, a refrigerator smart screen, or devices having only an audio output function and not having an image display function, such as a speaker device, a radio, and the like.

For example, when a user watches a television episode on a living room television, he needs to go to a kitchen to cook, and the refrigerator in the kitchen has an intelligent screen, so that the user can push the television episode to the intelligent screen of the refrigerator for continuous playing through a series of operations on the living room television. Thus, the user can continue watching the television episode through the intelligent screen of the refrigerator while cooking. For another example, the user can listen to a song on the bedroom television, and the user needs to go to the living room, and the living room has a sound box, so that the user can push the song to the living room through a series of operations on the bedroom television to continue playing.

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

In some embodiments, after the display device is turned on and started, the public relay component is started, and then the call of any content application can be accepted.

In some embodiments, after a common relay component is started, the relay capabilities of all content applications in the system are scanned according to an operating system standard interface. Relay capability, as the name implies, refers to the ability of an application to continue rendering content, e.g., the type of content that can be rendered, the manner of rendering, etc. Taking a media application as an example, the content presentation capability may be the capability of playing a video file, including various parameters of a playable video file, and the like. When receiving the request of pushing content from the pushing end device, the receiving end device continues to play the content through the application program with the relay capability conforming to the content. For example, if the relay content is a video, the receiving end device needs to continue playing the video through the video playing application thereon; if the relay content is text, the receiving device may continue to display the text via a text application (e.g., notepad) thereon.

In some embodiments, the relay capability information of the device or other class of terminal devices, i.e., the relay capability information of each application on the device, is displayed. When an application on a device has a capability to support a certain relay capability, or when the relay capability of one or some of the applications on the device matches a certain relay capability, i.e. the device supports the relay capability, the device in turn has the capability to continue presenting a certain content.

In some embodiments, the same application may have different levels of relay capability, such as primary relay capability, secondary relay capability. In practice, the secondary relay capability is subordinate to the primary relay capability. Or, the secondary relay capability is a sub-capability of the primary relay capability. In another embodiment, the first level relay capability may be an upscaling capability of the plurality of second level relay capabilities, i.e., a generalization of the plurality of second level relay capabilities. In a further or alternative, the secondary relay capability of the application is the relay capability that the application has in different modes of operation.

From the practical functional considerations of the content application, the actual relay capability of the content application may be described by a single level of relay capability or a combination of levels of capabilities. It should be appreciated that the relay capabilities of each application may be customized according to its actual functionality.

Illustratively, taking a focused application as an example, a plurality of modules are embedded therein, including but not limited to modules for performing film, educational, gaming, K-song, fitness, shopping, etc. functions. In this example, the relay capabilities of the application may be described by a combination of multi-level capabilities. For example, a primary relay capability and a secondary relay capability affiliated with the primary relay capability. Each secondary relay capability corresponds to the aforementioned one functional module, and the plurality of secondary relay capabilities belong to sub-relay capabilities of the application, while the primary relay capability is the total capability of the application.

It should be noted, however, that in some implementations, if a first level of relay capability of an application matches a certain relay capability, a second level of relay capability of the application does not necessarily match the certain relay capability. Continuing with the example of the above-described focused application, even though focused primary relay capability supports video content-continuing presentation capability, its secondary relay capability of a module for implementing functions such as education, games, K songs, fitness, shopping, etc. does not necessarily support video content-continuing presentation capability. Thus, in some embodiments, for an application with multiple levels of capabilities, when each level of relay capability supports a certain relay capability, then the application is considered to support that relay capability, i.e., it may continue to present certain content. For example, for an application having a secondary relay capability, if the primary relay capability of the application and at least one secondary relay capability matches a target relay capability, then the application supports the target relay capability; for applications without secondary relay capability, if the primary relay capability of the application matches the target relay capability, the application supports the target relay capability.

It should be noted that, the data form and the data content of the capacity are not limited in the embodiment of the present application. However, it should be noted that the relay capability applied to the terminal device determines what content can be played by the terminal device in a relay manner. That is, the relay capability applied at the terminal device determines the capability of the terminal device to relay other device content. For example, when an application that plays a certain content in a relay manner is not available on a certain terminal device, the terminal device cannot play the content in a relay manner, and thus cannot become a 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 may be registered in a local area network protocol component of the terminal device, so that the local area network protocol component knows the relay capability of each content application program, where the local area network protocol component refers to a functional component for responding to the interaction information of an external device based on an instruction, a request, and the like sent by the local area network protocol channel. For example, when the first terminal device receives a capability query message sent by a second terminal device in the same local area network based on a local area network protocol channel, the relay capability of each application program pre-registered by the common relay component is fed back to the second terminal device, or a response is made to the capability query message, such as a response supporting a certain relay capability or not supporting a certain relay capability. Thus, the second terminal device can know the relay capability of the first terminal device and judge whether the first terminal device can be used as a receiving end device of a certain content according to the relay capability.

In some embodiments, the display device receives a capability query message sent by the push end device, the capability query message including a target relay capability; judging whether an application supporting the target relay capability exists on the display equipment, wherein for the application with the secondary relay capability, if the primary relay capability of the application is matched with at least one secondary relay capability, the application supporting the target relay capability; for applications without secondary relay capability, if the primary relay capability of the application matches the target relay capability, the application supports the target relay capability. And then returning a response message to the pushing end device according to the judging result, so that the pushing 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, the relay capability data may be uploaded to the cloud server, so that the cloud server may query the relay capability of each application on the specified terminal device. For example, when the cloud server receives a query request sent by the first terminal device and used for querying the relay capability of the second terminal device, the relay capability data uploaded in advance by the second terminal device can be returned to the first terminal device in response to the query request. Therefore, the first terminal device can know the relay capability of the second terminal device through the cloud server, and judge whether the second terminal device can be used as a receiving terminal device of certain content according to the relay capability.

In some specific implementations, the terminal device sends a device query request to the server, where the device query request includes a push end identifier and a target relay capability corresponding to the terminal device; receiving a request of a server responding to equipment inquiry, searching relay capability information corresponding to terminal equipment associated with the request according to a pushing end identifier, and judging whether application supporting target relay capability exists on the associated equipment, wherein for the application with secondary relay capability, if the primary relay capability of the application is matched with at least one secondary relay capability with the target relay capability, the application supporting target relay capability is applied; for applications without secondary relay capability, if the primary relay capability of the application matches the target relay capability, the application supports the target relay capability. And returning a device information set to the terminal device according to the query result, wherein the device information set comprises the device information of the terminal device which is related to the pushing end identifier and supports the target relay capability and queried by the server.

In other embodiments, after the common relay component scans the relay capability of each application, the relay capability data may be stored in a locally stored designated path, so that the local area network protocol component, the bluetooth protocol component, etc. may acquire the relay capability data in the designated path.

In some embodiments, the common relay component may select one or more of the foregoing manners according to a communication policy with other terminal devices to save the relay capability data of the local terminal device, where the communication policy refers to a communication channel, such as a lan protocol channel or a wan protocol channel, on which communication with other terminal devices is based. For example, if the terminal device is limited to communicating with other devices of the lan content based on the lan protocol channel, the common relay component may choose to register the relay capability data into the lan protocol component; if the terminal device can also communicate with a device outside the local area network based on the wide area network protocol channel, the public relay assembly can select to upload 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 the terminal device presents a certain content presented by a certain content application, the public relay component may search for a terminal device matching with the relay capability according to the relay capability of the content application, to obtain a device information list, where the device information list is the device information of the optional receiving end device. The user specifies the target pushing end device based on the device information list, and the public relay component can communicate with the target pushing end device based on a certain communication protocol channel to request the target pushing end device to relay and play the content. And the public relay component on the target pushing end equipment responds to the request, a content application with the relay capability is started, and the content is continuously played through the content application with the relay capability.

Notably, in a more specific implementation of the above embodiments, the content application on the push-end device needs to interact with the common relay component in response to user operations. The common relay component performs certain operations in response to the interaction information sent by the content application. In addition, since the common relay module has a function of presenting an interface object independent of the content application, a user can directly interact with the common relay module through the interface object provided by the common relay module to directly control the common relay module to perform certain operations. In other words, in a more specific implementation of the above-described embodiments, the common relay component on the push end device may perform certain operations in response to user input.

For convenience of explanation, in the following embodiments, content that a user desires to push is referred to as target content, a relay capability of an application that provides the target content on a pushing end device is referred to as target relay capability, and an application that supports the target relay capability on a target receiving end device is referred to as target application. In addition, the common relay assembly on the pushing end device may be simply referred to as a pushing termination force assembly, and the common relay assembly on the receiving end device may be simply referred to as a receiving termination force assembly. It is to be understood that the foregoing definitions are provided for convenience of description and for distinguishing between concepts. Not limited to the foregoing names, in some embodiments other names may be used to describe, and therefore, in determining the essence characterized by a certain name, the context of that name needs to be combined.

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

s601, the pushing end device presents the target content provided by a certain content application.

In fact, the target content may be any content that the content application presents. It should be appreciated that the types of target content provided by different content applications may be the same or different. The same content application may also provide different types of content. For example, for media applications, most of the content it presents is video content, picture content, or audio content. Corresponding to the reading application, the content presented is mostly text content.

Fig. 7 illustrates a display device user interface. As shown in fig. 7, the media application interface is displayed full screen on the display device, and the media application interface has a video playing window therein, in which a certain video content provided by the media application is being played.

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

The target relay capability, i.e., the relay capability of the content application providing the target content in S601.

In an alternative implementation, the content application transmits its own relay capability to the common relay component when the content application interface meets a preset condition. For example, when the target content is played full screen, the content application interface is considered to satisfy a preset condition. In other implementations, the content application may send its own relay capabilities to the common relay component when other conditions are met. For example, when a content application receives a particular user input, the content application sends its own relay capabilities to the public relay component. The present application is not limited to this.

S603, the public relay module on the pushing end device searches for terminal devices supporting target relay capability, and a device information list is obtained.

In some embodiments, after receiving a target relay capability sent by a content application, a public relay component on a pushing end device starts searching for a terminal device supporting the target relay capability, and obtains a device information list. The device information list is made up of device information of optional receiving-end devices. It should be appreciated that the common relay component search results may be divided into two cases, one in which at least one optional receiving end device is searched and one in which no optional receiving end device is searched. If the optional receiving terminal equipment is searched, the current scene is indicated to meet the preset content pushing condition, and if the optional receiving terminal equipment is not searched, the current scene is indicated to not meet the content pushing condition.

In some embodiments, the device search request is sent to the public relay component when the content application determines that the current scenario satisfies a preset content push condition. The public relay component responds to the device search request sent by the content application and searches for external terminal devices supporting the target relay capability according to the target relay capability in the device search request.

In other embodiments, the common relay component provides an interactive interface for a user to input a device search instruction, so that the common relay component can directly receive the device search instruction input by the user, and acquire the relay capability of the content application in response to the device search instruction to obtain the target relay capability; and searching for the external terminal equipment supporting the target relay capability according to the target relay capability. For example, in rendering target content, the common relay component controls the presentation of an interface object for triggering the rendering of device information, which can be manipulated by a user to input device search instructions.

In some alternative implementations, the public relay component on the pushing end device sends a device search request to the cloud end based on the wide area network communication protocol channel, wherein the device search request includes the pushing end information identifier and the target relay capability. The pushing end information identifier may be an account identifier logged in on the pushing end device, such as an account identifier of a logged-in content application. After the cloud receives the equipment searching request, searching terminal equipment associated with the pushing end equipment according to the pushing end information identification, for example, logging in the terminal equipment with the same account number with the pushing end equipment; after the cloud end searches the terminal equipment associated with the pushing terminal equipment, the terminal equipment matched with the target relay capability is determined according to the relay capability data uploaded by the terminal equipment. For example, when the relay capability of an application on a certain terminal device matches a target relay capability, the terminal device is determined as the terminal device matching the target relay capability. If the cloud end searches at least one terminal device matched with the target relay capability, a device information list containing the at least one terminal device is generated and fed back to the pushing end device. If the cloud end does not find the terminal equipment matched with the target relay capability, feeding back an equipment information list with empty content to the pushing end equipment, or returning a corresponding notification message to the pushing end equipment.

In some embodiments, a common relay component on the push end sends a capability query message to terminal devices in the local area network based on the local area network communication protocol channel; after receiving the capability query message, the terminal equipment in the local area network feeds back the relay capability of each application registered in the local area network component to the pushing end equipment through returning a response message; and the pushing end equipment determines optional pushing end equipment according to relay capability fed back by the terminal equipment in the local area network.

In some embodiments, a common relay component on the push end opens a close range communication protocol channel, receives relay capability data sent by nearby terminal devices based on the close range communication protocol channel, and thereby determines terminal devices supporting the target relay capability from the nearby terminal devices.

In some embodiments, the common relay component may select one or more of a local area network protocol channel, a wide area network protocol channel, and a near field communication protocol channel, and search for terminal devices supporting the target relay capability based on the selected communication protocol channel. By selecting proper protocol channel searching equipment, the searched equipment information can be ensured to be more comprehensive, so that more choices are provided for users, the communication resources of the equipment can be more reasonably utilized, the execution speed of the content relay process among the equipment is improved, and the user experience is improved.

In other embodiments, the user may preset a protocol channel for communicating with the receiving end device. And the public relay assembly searches for terminal equipment supporting the target relay capability based on a communication protocol channel preset by a user. It should be understood that if the communication protocol channel set by the user is a lan protocol channel, the terminal device searched by the public relay module is a device in the same lan as the pushing end device; if the communication protocol channel set by the user is a wide area network protocol channel, the terminal device searched by the public relay assembly can be a device outside the local area network; if the communication protocol channel set by the user is a near field communication protocol channel, the terminal device searched by the public relay assembly is the terminal device nearby the pushing terminal device.

In some embodiments, the push-side common relay component performs searching for external terminal devices supporting the target relay capability over the wide area network protocol channel, further configured to: sending a device query request to a server through a local area network protocol channel, wherein the device query request comprises a push end identifier and a target relay capability corresponding to the display device; and receiving a device information set returned by the server in response to the device query request, wherein the device information set comprises the device information of the terminal device which is related to the pushing end identifier and supports the target relay capability and queried by the server. In some embodiments, the device information includes a unique identification of the device and communication protocol information supported by the device. The communication protocols supported by some terminal devices can be categorized into one or more of a local area network protocol channel, a wide area network protocol channel and a near field communication protocol channel. For example, for some terminal devices, communication may be performed with the push end device through a lan protocol channel, or may be performed with the push end device through a close range communication protocol channel. For some terminal devices, communication with the push end device can be performed only through the wide area network protocol channel.

In some embodiments, the common relay component may 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, and avoid presenting repeated device information.

An exemplary integration result is as follows:

terminal equipment a: support AIOT/lan/bluetooth;

terminal equipment B: support local area network/bluetooth;

terminal equipment C: bluetooth is supported.

In some embodiments, when a common relay component on a push end device searches for a terminal device, the common relay component presents a prompt message on a current interface for prompting a user that the device is currently being searched. For example, as shown in fig. 8, a prompt message whose content is "seeking a device" is displayed on the playback screen.

S604, the common relay component on the push end device feeds back search results to the content application, the search results characterizing the existence of optional receiving end devices.

S605, after receiving the input relay operation, the content application on the pushing end device sends a device presentation request to the public relay assembly.

In some embodiments, when the content application presents certain content, the user may control call-out of the control region through a certain operation or a combination of operations. And the control area is used for intensively displaying the control which can be operated by the user, and the user triggers the terminal equipment to execute corresponding operation by operating a certain control.

In some implementations, if the common relay component on the push end device searches for at least one optional receiving end device, the first search result is fed back to the content application, the first search result characterizing the presence of the optional receiving end device. If the content application receives the first search result, when the user operates the call control area, an interface object for triggering the relay flow is displayed in the control area, and thus, 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 the call control area, an interface object for triggering the relay flow is not displayed in the control area.

In further implementations, a common relay component on the push end device feeds back search results to the content application, the search results characterizing whether an optional receiving end device is present. The content application decides whether to display an interface object for triggering the relay flow when the user brings up the control area according to the meaning characterized by the search result.

In some implementations, when the content application determines that the optional receiving end device exists according to the search result, an interface object for triggering the relay flow is directly displayed on the interface without displaying the interface object in the control area when the user operates to call out the control area.

As shown in fig. 9, the control section includes, but is not limited to, at least one of a "relay" control, a "playlist" control, a "sharpness" control, and a "recommended functions" control. The user can trigger the display device to execute corresponding operation by operating a control. For example, when a user selects the "playlist" control, the display device will display the selection list. Notably, the user can operate the "relay" control to input content relay operation, so as to trigger the display device to execute the operation of pushing the current program to other terminal devices to continue playing. When the media application receives user operation of the "relay" control, the media application sends a relay operation to the common relay component.

Of course, the user may input the content relay operation by other means, such as inputting the content relay operation by using a voice control function of the display device, inputting the content relay operation by using a voice password, or inputting the content relay operation by designating a key or a key combination on the control device.

S606, the common relay component on the push side device presents a device information list including at least one selectable receiving side device option.

In some embodiments, if at least one external terminal device supporting the target relay capability is searched, the public relay component controls to display an interface object for triggering presentation of device information, and at this time, the user can instruct presentation of the searched device information by operating the interface object; the public relay assembly responds to an input equipment presentation instruction to present an equipment information list, wherein the equipment information list comprises a plurality of equipment options, and the equipment options correspond to the searched equipment information; and when receiving the input selection operation of the target equipment options, determining that the content pushing instruction is received, wherein the target equipment options correspond to the equipment information of the target receiving end equipment.

As shown in fig. 10, the device information list includes a plurality of selectable device options named "second floor living room tv", "first floor kitchen refrigerator", "next lying sound box", "first floor living room tv", and the like. At this time, the user may designate the target receiving end device by inputting a selection operation of a certain option in the list. For example, when the user selects "second floor living room television", a device named "second floor living room television" is designated by the user as a target receiving end device.

S607, after receiving the input selection operation of the target receiving end device, the public relay component on the pushing end device requests the playing information of the target content from the content application.

And S608, the content application on the pushing end equipment returns the playing information of the target content to the public relay assembly.

The playing information of the target content is used for enabling an application on the receiving end equipment to continuously present the target content according to the playing information. For example, when the target content is multimedia content, the playing information thereof should include at least a playing source address, a playing progress, etc., and based on the playing information, the application on the receiving end device is sufficient to continue playing the multimedia content. For another example, when the target content is navigation information, the playing information thereof should include at least user location information and planned path information, and based on the playing information, the map application on the receiving end device is sufficient to continue to navigate the user. It should be understood that the parameters included in the corresponding play information may be the same or different depending on the content application. The playing information of a certain content application on the pushing end device should be parsed and identified by at least one content application on the receiving end device to continue presenting the target content.

In other embodiments, the user may instruct the public relay component to search for terminal devices supporting the target relay capability via the voice control function while the content application is rendering the target content. For example, referring to fig. 11A, after the user wakes up the voice application, speaks "search for relay device", and the voice application determines the user input device search instruction by parsing the semantics of the voice data. The device search command is sent to the public relay assembly and the user 'good' is replied to the interface to start the inquiry. And the public relay assembly responds to the equipment searching instruction sent by the voice application to search the terminal equipment supporting the target relay capability, so as to obtain an equipment information list.

Then, the public relay component sends the searched device information list to the voice application, and the voice application reads the specific content of the device information list, and simultaneously displays the device information list on an interface in a text mode, as shown in fig. 11B. After obtaining the device information list, the user can designate the target receiving end device through the voice control function and instruct the pushing end device to execute the relay flow. For example, the user speaks "relay to second floor living room tv", the voice application determines that the target receiving end device designated by the user is a terminal device named "second floor living room tv" by analyzing the semantics of the voice data, and the voice application transmits the device information of the target pushing end device to the public relay assembly while replying to the user "good, relaying", as shown in fig. 11C. After receiving the target receiving end information, the public relay assembly requests playing information of target content from the content application and executes subsequent steps.

In addition, the user may trigger some links in the relay flow through operation modes such as touch gesture and space gesture, which will not be described herein.

S609, the public relay module on the pushing end device sends a call request to the target receiving end device, wherein the call request comprises target relay capability and playing information of target content.

In some embodiments, the call request is also referred to as a relay request.

In some embodiments, after receiving a selection operation of a target push end device by a user, the public relay component on the push end device waits for a preset period of time and then calls the target receiving end device. The common relay component on the push end device displays a prompt message on the interface during the waiting period. During the display of the alert message or during the waiting period, the user may cancel the push by some action or may instruct the push immediately by some action. If the public relay component receives a cancel instruction input by a user during the display of the prompt message or during the waiting period, the step of canceling the push is executed. That is, the pushing end device responds to the input instruction of pushing the currently presented target content to the target receiving end device, and controls presentation of prompt information so as to prompt a user to input a pushing cancellation instruction or a pushing confirmation instruction within a preset time length through the prompt information; responding to the confirmation pushing instruction input by the user within a preset time length, and sending a relay request to target receiving end equipment so as to request the target receiving end equipment to continuously present target content; or, in response to the push cancellation instruction input by the user within a predetermined time period, canceling the transmission of the relay request to the target receiving end. If the input confirmed pushing instruction is not received or the pushing instruction is canceled within the preset time, a relay request is sent to the target receiving end equipment at the termination time of the preset time, and the display of the prompt information is canceled. In other embodiments, after receiving a user selection operation of a target push end device, the common relay component on the push end device displays a prompt message on the current interface while executing a call to the target receiving end device. During the display of the alert message or within a preset time, the user may cancel the push by some action. And if the pushing end equipment receives a cancel instruction input by a user in the display period of the prompt message or the preset time, executing the step of canceling the pushing. For example, if the target receiving end device is not called upon receiving an input cancel instruction, the call is blocked. If the target receiving end device has been called upon receiving the input cancellation instruction, a cancellation relay request is transmitted to the target receiving end device to cause the target receiving end device to interrupt the related operation.

That is, the pushing end device responds to the input instruction of pushing the currently presented target content to the target receiving end device, and sends a relay request to the target receiving end device so that the target receiving end device can continue to present the target content according to the relay request; and responding to the received push cancellation command input by the user within the preset time, and sending a relay cancellation request to the target receiving end equipment so as to cancel the presentation of the target content by the target receiving end equipment. Therefore, the user confirms the pushing operation input before a certain time, whether the pushing operation is withdrawn or not is considered, the target content is prevented from being pushed to the target receiving end equipment due to misoperation of the user, and user experience is improved.

The user may input the above-mentioned cancel push instruction by any key operation. The user can input the confirmation push instruction by designating a key.

In some embodiments, after receiving the selection operation of the user on the target push end device, the public relay component on the push end device performs countdown while displaying the prompt message, where the countdown duration may be a waiting duration before a call or a display duration of the prompt message. And displaying an interface element for showing the countdown progress on the interface to present a visual cue of the countdown progress to the user.

Fig. 12 is an application interface displayed on the push-end device after the user selects "second floor living room television" as the target receiving-end device in fig. 10. As shown in fig. 12, a prompt message with a content of "about to push to second floor living room television for playing," is displayed on the interface, the user stops pressing any key, presses the confirmation key to immediately relay, "and a visual prompt" 3 "of countdown progress is displayed on one side of the prompt message.

In some embodiments, after receiving a cancel push command input by a user, the public relay component on the push end device displays corresponding prompt information on an interface, and sends a cancel relay request to the target receiving end device. And after the public relay assembly on the target receiving end equipment receives the relay canceling request, displaying corresponding prompt information on an interface of the receiving end equipment.

Fig. 13 is a schematic diagram of a push scenario according to an exemplary embodiment of the present application. The interface of the pushing end device in fig. 13 is specifically an interface displayed after the pushing end force component receives a pushing cancellation instruction input by a user, and as shown in fig. 13, a prompt message with "pushing cancelled" is displayed on the interface of the pushing end device. The interface of the receiving end device in fig. 13 is specifically an interface displayed after the receiving end force receiving component receives the request for canceling the relay sent by the pushing end device, and as shown in fig. 13, the interface of the receiving end device displays a prompt message with the content of "bedroom television is canceled to be pushed".

It should be noted that, the public relay components on the pushing end device and the receiving end device may broadcast messages by calling the voice application, including but not limited to the above mentioned prompting information of "pushing has been canceled" and "pushing has been canceled by the bedroom television".

In some embodiments, after the pushing end device sends the relay request to the target receiving end device, the content application on the pushing end device may continue to present the target content, or may end to present the target content.

In some alternative implementations, the user may set the specified functions of the content application. After sending the relay request to the target receiving end equipment, the pushing end equipment decides whether to continue to present the target content according to the user setting. For example, in the case where the user turns on the function of "original device continue playing" of the content application, the pushing end device continues to present the target content after sending the relay request to the target receiving end device. Under the condition that the user closes the function of 'original equipment continuously playing' of the content application, the pushing end equipment continuously presents the target content after sending a relay request to the target receiving end equipment. Based on this, the push end device, after sending the relay request to the target receiving end device, is further configured to: acquiring a target setting parameter, wherein the target setting parameter is a first value or a second value; if the target setting parameter is the first value, controlling the content application to end playing the target content; and if the target setting parameter is the second value, controlling the content application to continuously play 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 shown in fig. 10, the user can operate "? The control triggers and enters a relay function introduction page which is at least used for displaying introduction information of a relay function, such as a relay operation mode. In addition, guide information whose content is "confirm key press force, adjust order by menu key" is displayed on the device information list page shown in fig. 10. The guidance information is used for reminding a user, the relay process can be triggered by operating a confirmation key on the remote controller under the condition that a certain equipment option is selected, and the display sequence of the equipment options in the equipment information list can be adjusted by operating a menu key on the remote controller.

In addition, on the device information list page shown in fig. 10, a switch button for "original device continue playing" is displayed, when the switch button is turned on by the user operation, that is, the function of "original device continue playing" of the content application is turned on, and then the content application will continue playing the content after pushing the content onto the receiving end device by the public relay component. When the user operates to turn off the switch button, i.e. the function of "original device continue playing" of the content application is turned off, the common relay component may exit to end playing of the content after pushing the content onto the receiving end device.

In other embodiments, after the push end device sends the relay request to the target receiving end device, the push end device is further configured to: receiving playing state information sent by target receiving end equipment, and acquiring target setting parameters, wherein the target setting parameters are first values or second values; if the playing state information represents that the target receiving end equipment responds to the relay request successfully and the target setting parameter is a first value, controlling the content application to end playing the target content; if the playing state information indicates that the target receiving end equipment fails to respond to the relay request or the target setting parameter is a second value, the content application is controlled to continuously play the target content.

And S610, the public relay component on the target receiving end equipment responds to the call request sent by the pushing end equipment, and starts a target application supporting the target relay capability.

In some embodiments, the push end device requests the target receiving end device to continue to present the target content provided by the push end application by sending a relay request to the target receiving end device. The relay request may include push side application information and play information of the target content. The pushing end application information at least comprises target relay capability and can also comprise application identification of the pushing end application. From the application identification it may be determined whether the two applications are the same application.

After receiving the relay request sent by the pushing end device, the receiving end public relay assembly determines a target application according to the pushing end application information, wherein the target application is the application with the highest matching degree with the pushing end application on the receiving end device or the application designated for the user. And then starting the target application, and controlling the target application to continuously present the target content according to the playing information of the target content. Therefore, the success rate of continuing to present the target content is guaranteed to the greatest extent, and the conditions of continuous failure or continuous error are avoided.

In some embodiments, the pusher application information includes a target relay capability and an application identification of the pusher application. After receiving a relay request sent by pushing end equipment, the receiving end public relay assembly determines a target application according to pushing end application information, and specifically comprises the following steps: the public relay assembly of the receiving end firstly screens out at least one candidate application supporting the target relay capability according to the relay capability of each application on the receiving end equipment. And judging whether the candidate application has the same application as the pushing end application or not according to the application identifier, wherein when the application identifier of a certain candidate application is matched with the application identifier of the pushing end application, the candidate application is determined to be the same application as the pushing end application. And if the candidate application has the same application as the pushing end application, determining the candidate application which is the same as the pushing end application as the target application. For example, when the push-side application is a media center application and the candidate applications on the receiving-side device also contain a media center application, then the media center application is determined to be the target application. If the candidate application does not have the same application as the pushing end application, determining a target application from the candidate application according to a preset rule.

In a more specific implementation, the receiving-end public relay component screens at least one candidate application supporting the target relay capability according to the relay capability of each application on the receiving-end equipment, and the method includes: judging whether the first-level relay capability applied on the display equipment is matched with the target relay capability; judging whether the applied secondary relay capacity is matched with the target relay capacity or not under the condition that the applied primary relay capacity is matched with the target relay capacity and the application has the secondary relay capacity; if at least one secondary relay capability of the application is matched with the target relay capability, determining the application as a candidate application; and determining the application as a candidate application under the condition that the primary relay capability of the application is matched with the target relay capability and the application does not have the secondary relay capability.

In some embodiments, the receiving-end public relay component first determines, according to an application identifier of the pushing-end application, whether an application identical to the pushing-end application exists on the receiving-end device, and if the application identical to the pushing-end application exists, determines a candidate application identical to the pushing-end application as a target application. If the application which is the same as the pushing end application does not exist, at least one candidate application supporting the target relay capability is screened out according to the relay capability of each application on the receiving end equipment. And determining the target application from the candidate applications according to a preset rule.

In some embodiments, the receiving-end public relay component determines the target application from candidate applications according to a preset rule, and specifically includes: according to a predefined ordering rule, ordering the candidate applications to determine the candidate application with the highest priority level; and determining the candidate application with the highest priority level as the target application. It should be noted that, in the embodiment of the present application, the manner of predefining the ordering rule is not limited, and the predefined ordering rule is not limited. Different ordering rules may be defined in connection with different scene needs. It should be understood that the ranking results are different according to the different ranking rules, and thus the ranking of the candidate applications is different, i.e. the priority levels thereof are different.

In some embodiments, relay scenarios may be categorized in advance. For example, relay scenes may be classified according to the type of target content. And predefining an ordering rule corresponding to the category of the relay scene. The public relay assembly of the receiving end obtains a corresponding predefined ordering rule according to the current relay scene category, and orders the candidate applications according to the obtained ordering rule.

In some embodiments, the content may be pre-categorized and each category of content is pre-configured with a default application. Illustratively, one of the plurality of video applications that can render video content is set as a default application for continuing to render video content. Based on the target application, the public relay assembly of the receiving end determines the target application from candidate applications according to a preset rule, and the method specifically comprises the following steps: determining a category of the target content; and determining the default application corresponding to the category of the target content in the candidate application as the target application according to the preset corresponding relation between the content category and the default application.

In some embodiments, after the receiving-end public relay component receives a relay request sent by the pushing-end device, determining a target application according to the pushing-end application information specifically includes: screening at least one candidate application supporting the target relay capability according to the relay capability of each application on the display equipment; presenting an application list including application options corresponding to each candidate application; and receiving the selection operation of the user on any application option, and determining 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, specifically, a user interface displayed after the display device is used as a receiving end device to receive a relay request sent by a pushing end device. As shown in fig. 14, an application list is presented on the user interface, the application list including application options corresponding to each candidate application, namely application 1, application 2 and application 3. At this time, the user may select a certain application option by moving the focus, and designate a corresponding candidate application as a target application by inputting an operation confirming that the certain application option is selected.

In some embodiments, the application options in the application list described above may be presented in a random order. In other embodiments, all candidate applications may be pre-ordered according to a predefined ordering rule to determine a priority level for each candidate application. The application list is then presented according to the ranking result such that the application options in the application list are arranged in a certain order, i.e. according to the priority level of each candidate application.

In some embodiments, after the receiving-end public relay component receives a relay request sent by the pushing-end device, determining a target application according to the pushing-end application information specifically includes: screening at least one candidate application supporting the target relay capability according to the relay capability of each application on the display equipment; acquiring the latest starting time corresponding to each candidate application; and determining the application with the latest starting time in the candidate applications as a target application.

In other embodiments, the target application may also be determined based on other user operation information for each candidate application. For example, the number of starts of each candidate application in the past certain period of time is acquired, and the application with the highest number of starts among the candidate applications is determined as the target application. For another example, the running time of each candidate application in the past certain time is obtained, and the application with the longest running time in the candidate applications is determined as the target application.

In some embodiments, if there is only one target application on the receiving end device that supports the target relay capability, the common relay component directly determines the application as the target application.

In some embodiments, after receiving a call request from a push end device, the common relay component on the receiving end device starts a support target application after waiting for a preset period of time. The common relay component on the receiving end device displays a hint message during the waiting period. During the display or waiting period of the prompt message, the user can cancel the relay by some operation or instruct the immediate relay by some operation. And if the receiving end equipment receives a relay cancellation instruction input by a user during the display period or the waiting time of the prompt message, executing the relay cancellation step. In other embodiments, a common relay component on the receiving end device displays a prompt message on the interface while locating the target application in response to a call request from the pushing end device. During the display of the alert message or within a preset time, the user may cancel the relay by some action. And if a cancel command input by a user is received during the display of the prompt message or in a preset time, executing the step of canceling the relay. For example, if the support target application is not started or the target application does not start presenting the target content upon receiving the input cancellation relay instruction, the start or stop of the play is prevented, and a cancellation message is sent to the push-end device. And if the target application starts playing the target content when receiving the input relay cancellation command, ending playing and sending a cancellation message to the pushing end equipment.

That is, the public relay module on the receiving end equipment responds to the received relay request sent by the pushing end equipment and controls to present certain prompt information so as to prompt the user to input a relay cancellation command or confirm the relay command within a preset time length through the prompt information; executing a relay request to continue presenting the target content in response to a confirmation relay command input by the user within a predetermined time period; or, in response to a cancellation relay command input by the user within a predetermined time period, ignoring the relay request to cancel the presentation target content, presenting corresponding prompt information, and sending a cancellation message to the pushing end device. And if the input confirmation relay command is not received or the relay command is cancelled within the preset time, executing the relay request at the termination time of the preset time to continue to present the target content. Thus, the user can respond to the received relay request sent by the pushing end device by the display device, and the display device is prevented from presenting the specified content in a relay way through the specified operation within a preset time before presenting the specified content in a relay way, or the display device is instructed to present the execution content immediately, so that the flexibility of the user operation is improved sufficiently.

In some embodiments, after receiving the relay request of the pushing end device, the public relay component on the receiving end device ignores the relay request to cancel the presentation target content and presents the corresponding prompt information if the relay canceling request sent by the pushing end device is received. In some embodiments, after the public relay component on the target receiving end device receives the call request sent by the pushing end device, the countdown is executed while the prompt message is displayed, and the countdown duration may be a waiting duration before the call or a display duration of the prompt message. And displaying an interface element for showing the countdown progress on the interface to present a visual cue of the countdown progress to the user.

Fig. 15 is a user interface displayed on the target receiving end device after the user selects "second floor living room television" as the target receiving end device in fig. 10. As shown in fig. 15, a prompt message with a content of "about to relay bedroom television content play, stop by pressing any key, relay immediately by pressing the confirm key" is displayed on the user interface, and a visual prompt "5" of countdown progress is displayed on one side of the prompt message.

In some embodiments, after receiving a cancel instruction input by a user, the common relay component on the receiving end device displays a corresponding cancel notification on an interface of the receiving end device, and synchronizes the relay state to the pushing end device. And after the public relay component on the pushing end equipment receives the relay state sent by the receiving end equipment, displaying a corresponding cancellation notice on an interface of the pushing end equipment.

Fig. 16 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. The interface of the receiving end device in fig. 16 is specifically an interface displayed after the receiving end force component receives the cancel command input by the user, and as shown in fig. 16, a notification message with the content of "relay has been cancelled" is displayed on the interface of the receiving end device. The interface of the push end device in fig. 16 is specifically an interface displayed after the push termination force assembly receives the relay state sent by the receiving end device, and as shown in fig. 16, a notification message with the content of "the opposite end has stopped relaying" is displayed on the interface of the push end device.

In some embodiments, the common relay component selects a target communication protocol channel based on the target receiver information, and calls the target receiver device based on the target communication protocol channel. The target communication protocol channel can be one or more of a local area network protocol channel, a wide area network protocol channel and a near field communication protocol channel.

Specifically, if the target receiving end device supports only one protocol channel, then the protocol channel is determined to be the target protocol channel. For example, for the terminal device C supporting only the bluetooth protocol in the above example, the bluetooth protocol channel is determined as the target communication protocol channel. For terminal equipment supporting multiple communication protocols, the common relay assembly determines one of the communication protocols supported by the target receiving end equipment according to preset rules and uses the determined one of the communication protocols as a target communication protocol channel.

In some embodiments, rules for determining the target communication protocol channel may be designed based on characteristics of various types of communication protocol channels. The local area network protocol channel and the wide area network protocol channel are known to have the characteristics of unlimited transmission distance, strong anti-interference capability, high transmission rate (the larger the bandwidth is, the faster the transmission rate) and the like; short-range communication transmission protocols, such as bluetooth protocol and infrared protocol, have short transmission distance, and for infrared protocol, directivity and no obstacle are required.

Based on this, in some exemplary embodiments, when the receiving end device supports both the lan protocol channel and the wan protocol channel, the lan protocol channel may be determined as the target communication protocol channel because the lan response time is superior to the wan. When the receiving end equipment supports a local area network protocol channel, a wide area network protocol channel and a Bluetooth protocol channel simultaneously, if the known transmission distance is far, if the transmission distance exceeds 10 meters, determining the local area network protocol channel or the wide area network protocol channel as a target communication protocol channel; if the transmission distance is known to be relatively close, e.g., not more than 2 meters, and the Bluetooth signal is relatively strong and the network signal is relatively weak, the Bluetooth protocol channel is determined to be the target communication protocol channel. When the receiving end equipment supports the Bluetooth protocol channel and the infrared protocol channel simultaneously, the infrared protocol is generally transmission with instructive property, and the supported data volume is smaller, and the anti-interference capability is weak, so that the Bluetooth protocol channel is preferentially determined as the target communication protocol channel.

In some embodiments, the push side common relay component obtains a preset priority of each protocol channel; and determining the protocol channel with the highest priority supported by the target receiving end equipment as a target protocol channel.

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

In some embodiments, the common relay component on the push end device calls the receive end device simultaneously according to each communication protocol channel supported by the receive end device. The receiving end device receives the call requests sent by the pushing end device based on different protocol channels successively. The receiving end device processes the call request received for the first time, and performs subsequent interaction with the pushing end device based on a communication protocol corresponding to the call request received for the first time. And when the receiving end equipment subsequently receives the same call requests sent by the same pushing end equipment based on other protocol channels, discarding the call requests.

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

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

S613, the target application on the receiving end equipment feeds back the playing state information to the public relay assembly.

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

In some embodiments, the play status indicates a success or failure of the play. If the target application on the receiving end equipment succeeds in continuing to play the target content, the target application feeds back playing state information indicating that the playing is successful to the receiving end force component. If the target application on the receiving end equipment fails to continue playing the target content, the target application feeds back playing state information indicating successful playing to the receiving end force component.

In some embodiments, the receiving-end relay component displays a corresponding prompt message on an interface of the receiving-end device according to the received play status information.

In some embodiments, the common relay component on the receiving end device returns a response message to the pushing end device after receiving the call request sent by the pushing end device. And the pushing end equipment judges success or failure of relay according to whether the response message is received. If the response message is received, the relay is considered to be successful, corresponding prompt information is displayed, if the content is the prompt information of 'pushed to xx equipment', if the response message is not received for a long time, the relay is considered to be failed, and if the content is the prompt information of 'relay failure'.

S615, the public relay component on the pushing terminal equipment receives the playing state information and presents corresponding prompt information according to the playing state information.

In some embodiments, after receiving the play status information sent by the push end device, the public relay component indicates the content application to end playing the target content or indicates the content application to continue playing the target content according to the play status information and the on-off status of the "continue playing by original device" button. For example, regardless of whether the play status information reveals that the receiving end device succeeds or fails to play the target content, the content application is instructed to continue playing the target content as long as the "original device continues playing" button is turned on. If the playing state information reveals that the receiving end equipment fails to play the target content, if the original equipment continuously plays the target content, the content application is instructed to continuously play the target content, and if the original equipment continuously plays the target content, the content application is instructed to finish playing the target content.

Fig. 17 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In fig. 17, the receiving-end device interface and the pushing-end device interface are specifically interfaces that are displayed after the target application succeeds in continuing to play the target content. In fig. 17, a prompt message with the content of "relayed bedroom television content play" is displayed on the receiving end device interface, and a prompt message with the content of "relayed to second floor living room television play" is displayed on the pushing end device interface.

Fig. 18 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. The receiving-end device interface and the pushing-end device interface in fig. 18 are specifically interfaces that are displayed after the target application fails to continue playing the target content. In fig. 18, a prompt message with the content of "relay failure" is displayed on the interface of the receiving end device, and a prompt message with the content of "relay failure" is displayed on the interface of the pushing end device.

In some embodiments, the push end device common relay component presents a hint message about the target receiving end device on the push end device interface when the target receiving end device and the push end device belong to different types of devices. For example, when the pushing end device is a display device, the target receiving end device is a speaker device, and the target content is an audio content, after the relay is successful, the pushing end device public relay component presents a prompt message with the content of "receiving end device no interface display" on the pushing end device interface. The specific content, display mode, display time and duration of the prompt message are not limited in the application. For example, after the user selects the target receiving end device, the push end device public relay component may display the prompt message when it is determined that the target receiving end device selected by the user is different from the push end device in type. And displaying the prompt message after successful relay.

It should be noted that, the relay flow related to the embodiment of the present application is not limited to the flow shown in fig. 6, and the UI interface style displayed in the process of executing the relay flow by the pushing end device and the receiving end device is not limited to the style shown in the foregoing embodiment. Based on the core thought of the technical scheme of the application, a person skilled in the art can obtain various different embodiments without creative labor, and the embodiments belong to the protection scope of the application.

In some embodiments, the common relay component may operate in two modes, one in an exclusive mode and one in a non-exclusive mode. When the public relay component is in the exclusive mode, the public relay component does not interact with the receiving end equipment or terminal equipment outside the pushing end equipment in the content pushing and content relay process when interacting with the receiving end equipment or the pushing end equipment. In other words, when the common relay module on the terminal device is in the exclusive mode, the common relay module cannot perform information interaction operation related to the content pushing and content relay process with two or more terminal devices at the same time. On the contrary, when the public relay component is in the non-exclusive mode, the public relay component can also perform interaction related to content pushing and content relay process with the receiving end device or terminal devices other than the pushing end device when performing information interaction in the content pushing process with a certain receiving end device and/or performing information interaction in the content relay process with a certain pushing end device.

In some possible implementations, the interactions described above in connection with the content push process include at least the step of pushing S609 to rendering play state performed by the termination force component of fig. 6. That is, if the push-end relay assembly is in exclusive mode, it does not interact with terminal devices other than the receiving-end device during execution S609 to rendering the play state.

In some possible implementations, the interactions described above in connection with content relay include at least S610 through S614 performed by the receive termination force assembly of fig. 6. That is, if the receiving-end relay component is in the exclusive mode, it does not interact with the terminal devices other than the pushing-end device during execution of S610 to S614.

In some embodiments, the interactions described above in connection with content pushing and content relay are referred to as relay interactions. Taking the display equipment as an example, in the process of relay interaction with the first terminal equipment, the display equipment responds to a relay request sent by the second terminal equipment to acquire a current working mode; and if the current working mode is the exclusive mode, ignoring the relay request sent by the second terminal equipment, and returning an exclusive message to the second terminal equipment. And if the current working mode is not the exclusive mode, displaying corresponding relay request prompt information according to the relay request sent by the second terminal equipment, so that a user can trigger to execute relay interaction with the second terminal equipment or trigger to abandon relay interaction with the second terminal equipment according to the relay request prompt information. The relay interaction with the first terminal device refers to an interaction process of executing a relay request sent by the first terminal device to continue presenting the content pushed by the first terminal device, and/or an interaction process of executing an input content pushing instruction to push the content currently presented to the first terminal device to continue presenting. 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, so that the content pushed by the first terminal device can be ensured to be smoothly relayed by the display device, or the content can be smoothly pushed to the first terminal device, and the user experience is ensured.

In some embodiments, if the current working mode is not the exclusive mode, displaying an interrupt operation prompt message, so that a user inputs an interrupt operation according to the interrupt operation prompt message, where the interrupt operation is used to control a display device to interrupt a relay interaction process with the first terminal device. And responding to the input interrupt operation, interrupting the relay interaction process with the first terminal equipment.

In some embodiments, the user may make settings related to content relay functionality on a UI interface provided by the common relay assembly, including setting an operational mode of the common relay assembly. For example, the operating mode of the common relay component is set to exclusive or non-exclusive mode by interacting with an interface object on a UI interface provided by the common relay component.

Based on this, in the above embodiment, the display device obtains the current working mode, which may specifically include obtaining a switch state of an exclusive function of the device; if the exclusive function of the device is in an on state, determining that the current working mode is an exclusive mode; and if the device exclusive function is in the off state, determining that the current working mode is not an exclusive mode.

In other embodiments, the user may turn on or off the device exclusive function of the common relay assembly on a UI interface provided by the common relay assembly. When the device exclusive function of the public relay module is started, the public relay module automatically enters an exclusive mode when the public relay module starts to execute content pushing or content relay interaction with a certain terminal device, and automatically exits the exclusive mode when the public relay module finishes the content relay interaction with the certain terminal device, and then enters a non-exclusive mode. In the case where the device exclusive function of the common relay assembly is turned off, the common relay assembly is always in a non-exclusive mode. That is, even if the common relay module starts to perform content push or content relay interaction with a certain terminal device, the terminal device does 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, judging whether the terminal device is in an exclusive mode currently; if the exclusive mode is not currently in, processing is performed for the call request, for example, S610 to S614 shown in fig. 6 are performed; if the call request is in the exclusive mode, the call request is not processed, corresponding relay request prompt information is displayed on an interface, and corresponding notification information is fed back to the terminal equipment sending the call request. For ease of illustration, the notification message may be referred to as an exclusive message. The terminal device sending the call request can display the corresponding prompt information on the interface according to the exclusive message. The relay request prompt information comprises equipment information of other terminal equipment and/or key information of the target content, such as equipment names of other terminal equipment and content names of the target content.

In some possible implementations, in a case where the common relay component is in the exclusive mode, it may determine whether the call request or other information data is a request or information data sent for the current interactive terminal or a request or information data sent for other terminal devices by determining a source of the call request or other information data. And if the request or the information data is sent by other terminal equipment, masking the request or the information data.

It will be appreciated that the terminal device in the exclusive mode may be acting as a push-end device, performing interactions with the receiving-end device related to the content push procedure, or may be acting as a receiving-end device, performing interactions with the push-end device related to the content relay procedure.

It should also be appreciated that the common relay component may receive call requests sent by multiple terminal devices at the same time, meaning at the same time or with a sufficiently short time difference in receiving the multiple call requests. In some embodiments, in the case where the common relay component on the terminal device is in a non-exclusive mode, if multiple call requests sent by multiple terminal devices are received, processing is performed for the first received call request, e.g., performing S610 through S614 shown in fig. 6, without processing the later received call requests. And feeding back a corresponding notification message to the terminal equipment sending the call request while deciding not to process the call request. For ease of illustration, this notification message may be referred to as a busy message. The terminal device sending the call request can display the corresponding prompt information on the interface according to the busy message.

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

Fig. 19 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, the a device sends a call request to the a device requesting that the C content be pushed to the a device to continue playing on the a device while interacting with the B device to push the a content to the B device. At this time, the C device presents a C content picture; the equipment A presents the picture of the content A and displays a prompt message with the content of 'to be pushed to the equipment B for playing'; the equipment B presents an equipment interface B, and a prompt message with the content of 'about to relay equipment A' is displayed on the equipment interface B. Notably, since the common relay component on the a device is in the exclusive mode, the a device does not process the call request of the C device after receiving the call request, but feeds back an exclusive message to the C device. And after receiving the exclusive message fed back by the A device, the C device presents a prompt message with the content of 'the A device is in relay' on the interface.

Fig. 20 is a schematic view of another relay scenario illustrating the present application according to an exemplary embodiment. This example differs from the example shown in fig. 19 in that when the a device interacts with the B device to push the a content to the B device, the C device, the D device, and the E device each send a call request to the a device requesting that the C content, the D content, and the E content be pushed to the a device, respectively, to continue playing on the a device. This example is the same as the example shown in fig. 18, in that the common relay component on the a device is in the exclusive mode, so that after receiving the call requests of the C device, the D device and the E device, the a device does not process the call requests, but feeds back an exclusive message to the C device, the D device and the E device, respectively. And after the C device, the D device and the E device receive busy information fed back by the A device, presenting prompt messages with the content of 'the A device is in relay' on respective interfaces.

Fig. 21 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, the a device sends a call request to the B device requesting that the C content be pushed to the B device to continue playing on the B device while interacting with the B device to push the a content to the B device. At this time, the C device presents a C content picture; the equipment A presents the picture of the content A and displays a prompt message with the content of 'to be pushed to the equipment B for playing'; the equipment B presents an equipment interface B, and a prompt message with the content of 'about to relay equipment A' is displayed on the equipment interface B. It is noted that, based on the same processing logic as the example shown in fig. 19, since the common relay component on the B device is in the exclusive mode, the B device does not process the call request of the C device after receiving the call request, but feeds back an exclusive message to the C device. And after the C equipment receives the exclusive message fed back by the B equipment, presenting a prompt message with the content of 'the B equipment is in a relay state' on the interface.

Fig. 22 is a schematic view of another relay scenario illustrating the present application according to an exemplary embodiment. This example differs from the example shown in fig. 19 in that when the a device interacts with the B device to push the a content to the B device, the C device, the D device, and the E device each send a call request to the B device requesting that the C content, the D content, and the E content be pushed to the B device, respectively, to continue playing on the B device. Because the public relay component on the B device is in the exclusive mode, after receiving the call requests of the C device, the D device and the E device, the B device does not process the call requests and feeds back an exclusive message to the C device, the D device and the E device respectively. After the C device, the D device and the E device receive the exclusive message fed back by the B device, the C device, the D device and the E device present prompt messages with the content of 'the B device is in relay' on respective interfaces.

Fig. 23 is a schematic view of another relay scenario illustrating the present application according to an exemplary embodiment. In this example, when the a device interacts with the B device to push the a content to the B device, the C device and the D device each send a call request to the a device requesting that the C content and the D content be pushed to the a device to continue playing on the a device, and the E device and the F device each send a call request 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. Because the A device and the B device are both in the exclusive mode, after receiving the call requests sent by the C device and the D device, the A device feeds back an exclusive message to the C device and the D device respectively, and the C device and the D device display prompt messages with the content of 'the A device is in a relay state' on respective interfaces; after receiving the call requests sent by the E device and the F device, the B device respectively sends an exclusive message to the E device and the F device, and the E device and the F device display prompt messages with the content of 'B device is in relay state' on respective interfaces.

In some embodiments, the working state of the common relay assembly is divided into two states, one being a busy state and the other being an idle state. The busy state is complementary to the idle state, i.e. the public relay component is in the idle state if not in the busy state. It should be noted that the busy state and the idle state may be defined according to different criteria. In other words, in different embodiments, the busy state of the common relay assembly may be different working states, and the corresponding idle states may also be different.

In some embodiments, the common relay component on a terminal device is in a busy state when the terminal device is acting as a push end device and interacting with another terminal device or devices to push content to the terminal device or devices. When a certain terminal device is used as a receiving end device and interacts with another one or more terminal devices to receive content pushed by the one or more terminal devices and relay play the content, a public relay assembly on the terminal device is in a busy state. In other words, the busy state refers to a state in which a certain terminal device performs relay interaction with other terminal devices.

In some alternative implementations, the common relay assembly is in a busy state during execution of S609 to S615 in fig. 6, otherwise in an idle state. More specifically, when the common relay module performs S609 of fig. 6, the common relay module enters a busy state, and when the common relay module performs S615, the common relay module shifts from the busy state to an idle state.

In other alternative implementations, the common relay assembly is in a busy state during execution of S607 through S615 in fig. 6, otherwise in an idle state. More specifically, when the common relay module performs S607, the common relay module enters a busy state, and when the common relay module performs S615, the common relay module shifts from the busy state to an idle state.

In some embodiments, a terminal device, while in an idle state, performs one or more relay requests in response to receiving the relay requests sent by another one or more terminal devices, and updates the current state from the idle state to a busy state.

In some embodiments, a terminal device, while in an idle state, sends a relay request to another terminal device or devices in response to an instruction entered by a user to push currently presented target content to the other terminal device or devices, and updates the current state from the idle state to a busy state.

For convenience of explanation, the following embodiments distinguish each terminal device in the interaction scenario by terms such as "first", "second", "third", etc. These terms, and in particular a certain terminal device, should be understood that the terms so used may be interchanged where appropriate.

In some embodiments, when the common relay module on the first terminal device is busy due to relay interaction with the second terminal device, if a call request sent by the third terminal device is received, a relay information option corresponding to the call request is displayed on the interface, so that the user knows the content of the call request. Alternatively, the relay information option may display the device information of the third terminal device and the key information of the specified content, for example, the device name of the third terminal device, and the content name of the specified content. At this time, the user may instruct the first terminal device to perform the call request by selecting the relay information option. The first terminal device responds to the user operation and executes the call request to present the appointed 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 common relay module on the first terminal device is busy due to relay interaction with the second terminal device, if a call request sent by the third terminal device is received, a relay information option corresponding to the call request is displayed on the interface, so that the user knows 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 module on the first terminal equipment receives the interrupt operation input by the user, the relay interaction with the second terminal equipment is interrupted, and the call request sent by the third terminal equipment is processed. If the public relay module on the first terminal equipment does not receive the interrupt operation input by the user, relay interaction with the second terminal equipment is continued, and the call request sent by the third terminal equipment is not processed.

Fig. 24 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, the a device sends a call request to the a device requesting that the C content be pushed to the a device to continue playing on the a device while interacting with the B device to push the a content to the B device. Because the public relay component on the a device is in a busy state, after receiving the call request of the C device, the public relay component on the a device performs an interactive flow with the B device, and simultaneously displays a content of "C device requests to push C content, is the current relay interrupted? Pressing the confirmation key interrupts. At this time, the user may input the interrupt operation by pressing the confirm key. If the public relay component on the A equipment receives the input interrupt operation, interrupting the interaction process with the B equipment, processing a call request sent by the C equipment, and finally continuing to play the C content on the A equipment. If the public relay component on the A equipment does not receive the input interrupt operation, the interaction process with the B equipment is continued without processing the call request sent by the C equipment, and a busy message is fed back to the C equipment.

Fig. 25 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, the a device sends a call request to the B device requesting that the C content be pushed to the B device to continue playing on the B device while interacting with the B device to push the a content to the B device. Because the public relay component on the B device is in a busy state, after receiving the call request of the C device, the B device executes the interaction procedure with the a device, and simultaneously displays the content on the B device interface as "C device requests to push the C content, is the current relay interrupted? Pressing the confirmation key interrupts. At this time, the user may input the interrupt operation by pressing the confirm key. If the public relay component on the B equipment receives the input interrupt operation, interrupting the interaction process with the A equipment, processing a call request sent by the C equipment, and finally continuing to play the C content on the B equipment. If the public relay component on the B device does not receive the input interrupt operation, the interaction process with the A device is continued without processing the call request sent by the C device, and a busy message is fed back to the C device.

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

It should be appreciated that if a certain terminal device receives a call request sent by another terminal device while in a busy state, it may prompt the user in various suitable manners, and is not limited to the content shown in the above example being "C device requests to push C content, is the current relay interrupted? Pressing the confirmation key interrupts. For example, relay information corresponding to the call request may be displayed on the device interface according to the received call request, where the relay information includes, but is not limited to, push-end device information and push content information. For example, in the example shown in fig. 26, if the public relay module on the a device receives the call request sent by the C device, the relay information option is displayed on the a device interface, and the C device information and the C content information are displayed on the relay information option.

In some embodiments, when the common relay module on the first terminal device is busy due to relay interaction with the second terminal device, if call requests sent by a plurality of third terminal devices are received, relay information options corresponding to each call request are displayed on the interface, so that the user knows the content of each call request. At this time, 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 equipment responds to an instruction of executing at least one target relay request by designating at least one target relay information option input by a user, and executes the at least one target relay request so as to present designated content corresponding to each target relay request, thereby avoiding the user from missing the content pushed by the third terminal equipment. And for the relay request corresponding to the relay information option which is not specified or selected by the user, returning a busy message to the terminal equipment which sends the relay request.

In addition, the user may interrupt interaction between the first terminal device and the second terminal device through a predetermined operation, and may select one or more relay information options to specify contents to be relayed. If the public relay module on the first terminal equipment receives the interrupt operation input by the user and the selection operation of one or more relay information options, the interaction with the second terminal equipment is interrupted, and the call request corresponding to the relay information option selected by the user is processed at the same time. If the public relay component on the first terminal equipment does not receive the interrupt operation input by the user, the interaction with the second terminal equipment is continued, and the call requests sent by other terminal equipment are not processed.

In some embodiments, if the user selects a plurality of relay information options to specify a plurality of contents to be relayed, the receiving-end relay component respectively starts a plurality of target applications supporting corresponding target relay capabilities, and respectively sends the playing information of each target content to the corresponding target application, so that each target application can continuously play the corresponding content according to the received playing information. Specifically, a plurality of content presentation windows are controlled to be displayed, each content presentation window is used for presenting specified content corresponding to each target relay request, the plurality of content presentation windows are tiled, or at least part of the plurality of content presentation windows are overlapped and displayed. Wherein the content presentation window may be an application interface of the target application.

Fig. 27 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, when the a device interacts with the B device to push the a content to the B device, the C device, the D device, and the E device each send a call request to the a device requesting that the C content, the D content, and the E content be pushed to the a device, respectively, to continue playing on the a device. Because the public relay component on the a device is in a busy state, after receiving the three call requests, the public relay component presents relay information options corresponding to each call request in an interface, namely, a content of "C device-C content", "D device-D content" and a content of "E device-E content", and the content of "whether to interrupt the current relay? Pressing the confirm key to interrupt the prompt message. At this time, the user can interrupt the interaction between the a device and the B device by the confirm key. And the content corresponding to the relay of the equipment A can be controlled by selecting a certain relay information option. For example, when a user selects "C device-C content," a common relay component on the A device processes a call request sent for the C device to continue playing the C content on the A device. It should be noted that the user may also select multiple relay information options simultaneously to control the content pushed by the a device to relay multiple devices simultaneously. For example, when a user selects "C device-C content", "D device-D content", the common relay component on the A device will process the call requests sent by both the C device and the D device to continue playing C content on the A device while continuing to play D content.

Fig. 28A and 28B are diagrams of a receiving-end device user interface according to an exemplary embodiment of the present application, specifically illustrating the user interface shown in fig. 27 after the user selects "C device-C content", "D device-D content", and "E device-E content" on the a device. In fig. 28A, the C content, the D content, and the E content are displayed in different windows, or, in other words, the C content, the D content, and the E content are displayed on the a device interface in a split screen manner. In fig. 28B, the C content is displayed full screen, and the D content and the E content are displayed superimposed on the C content. It should be understood that, when the user selects the plurality of relay information options to control the a device to relay the content pushed by the plurality of devices at the same time, the manner in which the receiving end device presents the plurality of content is not limited to the embodiment shown in the above example. The present application is not limited to the manner in which the receiving end device presents the plurality of contents.

Fig. 29 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. In this example, when the a device interacts with the B device to push the a content to the B device, the C device, the D device, and the E device each send a call request to the B device requesting that the C content, the D content, and the E content be pushed to the B device, respectively, to continue playing on the B device. Because the public relay component on the B device is busy, after receiving the three call requests, the public relay component presents relay information options corresponding to each call request in the interface, namely, "C device-C content", "D device-D content", and "E device-E content", and "whether to interrupt the current relay? Pressing the confirm key to interrupt the prompt message. At this time, the user can interrupt the relay flow between the B device and the a device through the confirm key. The B device can be controlled to receive the content pushed by the corresponding device by selecting a certain relay information option.

In some embodiments, when the common relay component on a certain terminal device is in an idle state, if call requests sent by a plurality of other terminal devices are received, relay information options corresponding to each call request are displayed on an interface, so that a user knows the content of each call request. At this time, the user may select one or more relay information options to specify the terminal device to interact with. If the public relay module on the first terminal equipment receives the selection operation of one or more relay information options, the call request corresponding to the relay information option selected by the user is processed at the same time.

Fig. 30 is a schematic view of a relay scenario according to an exemplary embodiment of the present application. This example differs from the example shown in fig. 27 in that the a device receives a call request sent by the C device, the D device, and the E device while its common relay assembly is in an idle state. Because the public relay component on the a device is in an idle state, after receiving the three call requests, only the relay information option corresponding to each call request needs to be presented in the interface for the user to select, and the display content is not required to be "whether to interrupt the current relay? Pressing the confirm key to interrupt the prompt message.

In some embodiments, the common relay component on the first terminal device may send a call request to the user specifying one or more other terminal devices in response to a user operation while in a busy state due to performing a relay procedure with the second terminal device. In an implementation case of simultaneously sending a call request to a plurality of other terminal devices, the first terminal device will receive feedback information of the plurality of other terminal devices, where the feedback information is any one of an exclusive message, a busy message, and play status information. And the first terminal equipment displays corresponding prompt information on the equipment interface according to the feedback information of each terminal equipment. For example, when receiving the play status information sent by a certain terminal device, corresponding prompt information including a play success status and a play failure status is presented in the interface according to the play status revealed by the play status information. When an exclusive message sent by a certain terminal device is received, a prompt message with the content of 'xx equipment in relay state' is presented in a user interface. When a busy message sent by a certain terminal device is received, a prompt message with the content of 'xx device refusal relay' is presented in an interface.

Fig. 31 is a schematic view of a relay scenario according to an exemplary embodiment of the present application, where the schematic view is specifically an interface state of each device after a user operation is responded to send a call request for requesting to push B content to a C1 device, a C2 device, and a C3 device when the a device interacts with the B device to push the a content to the B device, the B device presents the B content, and a device information list formed by optional receiving end device information. When the C1 device receives the call request, the C1 device is in an exclusive state, so that an exclusive message is returned to the B device, and the B device presents a prompt message with the content of 'the C1 device is in a relay state' on an interface. When the C2 device receives the call request, the C2 device is in a busy state, and the user does not have relay flows between the C2 device and other devices, so that the C2 device feeds back busy information to the B device, and the B device presents a prompt message of which the content is that the C2 device refuses relay on an interface. C3 equipment responds to the call request and starts the content application supporting the call request to successfully continue playing the B content, so that the C3 equipment returns playing state information indicating successful playing to the B equipment, and the B equipment presents a prompt message of which the content is 'successfully pushed to the C3 equipment' on an interface.

In some embodiments, if the first terminal device receives the call requests sent by the plurality of second terminal devices in the idle state, determining, according to the push end application identifier included in each call request, whether an application providing the target content on each second terminal device is the same as each application on the first terminal device; if some and only one application providing the target content on the second terminal device is the same as a certain application on the first terminal device, processing the call request sent by the second terminal device. For example, when a certain second terminal device requests that target content to be continuously presented is presented by a media center application on the second terminal device, and the first terminal device also has the media center application, a call request sent by the second terminal device is processed. If the application providing the target content on the plurality of second terminal devices is the same as one application on the first terminal device, the corresponding relay information options are displayed according to the call requests sent by the plurality of second terminal devices, so that the user can know the content of the call requests. At this time, 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 providing the target content on each second terminal device is different from the application on the first terminal device, displaying corresponding relay information options according to the call requests sent by each second terminal device, so that the user can know the content of the call requests. At this time, 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 common relay component on the first terminal device is busy due to executing a relay procedure with the second terminal device, the call request may be sent to one or more receiving end devices designated by the user in response to the user operation, and at the same time the call requests sent by the plurality of pushing end devices may be received.

Fig. 32 is a schematic view of a relay scenario according to an exemplary embodiment of the present application, where the schematic view specifically illustrates interface states of devices after an a device interacts with a B device to push a content to the B device, the B device presents the B content and a device information list formed by optional receiving end device information, and receives call requests sent by D1 devices, D2 devices, and D3 devices at the same time. The B device displays, in addition to the device information list formed by the "C1 device", "C2 device" and "C3 device", relay information options corresponding to the call requests sent by the D1 device, the D2 device and the D3 device, respectively, namely, the "D1 device-D1 content", "D2 device-D2 content" and "D3 device-D3 content", respectively. At this time, the user may designate the target receiving end device by selecting one or more receiving end device information options in the device information list, so that the B device may send a call request for pushing the B content to the receiving end device designated by the user, and may interrupt the relay flow between the B device and the a device by a predetermined operation, and select one or more relay information options, designate the target pushing end device, so as to relay the content pushed by the target pushing end device.

Referring to fig. 33, because the user selects "C1 device" and "C2 device" in the scenario shown in fig. 32, the common relay component on the B device sends a call request to the C1 device and the C2 device; because the user interrupts the relay flow between the B device and the A device and selects the D1 device-D1 content, the B device plays the D1 content in a relay way.

It should be noted that, the steps performed by the common relay assembly according to the above embodiment may be separately cooperated by the functional modules inside the common relay assembly.

Illustratively, FIG. 34 is an interactive flow diagram illustrating an exemplary embodiment of the present application. As shown in fig. 34, the common relay assembly includes an interaction hub module, a status management module, an interface presentation module, a protocol processing module, and a logic control module. On the pushing end equipment, after the content application presents the target content, communication connection is established with the interaction center module, and based on the communication connection, the self relay capability (namely the target relay capability) is sent to the interaction center module. The interactive 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, a target communication protocol channel is selected, and based on the target protocol channel, an external terminal device supporting the target relay capability is searched through a target communication protocol assembly corresponding to the target protocol channel, so that a device information list is obtained. And the protocol processing module sends the equipment information list to the interface display module, and feeds back equipment search results to the interaction center module. The interaction hub module sends the device search results to the content application. The content application displays an interface object for triggering relay operation on the interface according to the equipment search result, receives the relay operation input by the user through the interface object, and sends a relay instruction to the interaction center module. And after receiving the relay command, the interaction center module informs the interface display module to display the equipment information list. The interface display module receives the selection operation of the user on the target receiving end equipment, and the information of the target receiving end equipment is sent to the protocol processing module so as to instruct the protocol processing module to call the target receiving end equipment. After receiving the target receiving end equipment information, the protocol processing module instructs the interactive center module to request playing information of target content from the content application, and the interactive center module returns playing confidence of the requested target content to the protocol processing module. The protocol processing module selects a target communication protocol channel and instructs the logic control module to call the target receiving end device based on the target protocol channel. The logic control module judges whether the interface interaction module is in an exclusive mode currently, and if the interface interaction module is in the exclusive mode, the logic control module informs the interface interaction module to present a first prompting message so as to prompt a user. And if the device is not in the exclusive module, calling the target receiving end device based on the target protocol channel. And after the call is completed, receiving the play state information returned by the target receiving terminal equipment, and sending the play state information to the state management module. The state management module instructs the interface display module to display a second prompting message according to the playing state information so as to prompt the user.

Illustratively, FIG. 35 is an interactive flow diagram illustrating an exemplary embodiment of the present application. As shown in fig. 34, the common relay assembly includes an interaction hub module, a status management module, an interface presentation module, a protocol processing module, and a logic control module. And on the receiving end equipment, the target communication protocol component receives the call request sent by the pushing end equipment and sends the call request to the logic control module. The logic control module judges whether the current is in the exclusive mode or not, if the current is in the exclusive mode, the logic control module returns an exclusive message to the pushing end device through the target protocol component, and if the current is not in the exclusive mode, whether the current is in an idle state is continuously judged. And if the interaction center module is in the idle state currently, determining a target application indicating the target relay capability, and indicating the interaction center module to start the target application. The interactive center module starts the target application and sends the playing information of the target content to the target application. And the target application continues to present the target content according to the playing information of the target content and returns playing state information to the interaction center module. The interactive center module sends the playing state information to the state management module. The state management module instructs the logic control module to return the play state information to the pushing end device, and instructs the interface display module to display a prompt message according to the play state information. If the interface display module is in a busy state currently, the interface display module is instructed to display corresponding relay information according to the call request and display an interrupt operation reminding message. The interface display module displays corresponding relay information according to the call request and displays an interrupt operation reminding message, and when receiving the input interrupt operation, the interface display module instructs the logic control module to interrupt the current relay, and when receiving the selection operation of the input interface information, the interface display module instructs the logic control module to process the corresponding call request.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

The foregoing description, for purposes of explanation, has been presented in conjunction with specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the embodiments to the precise forms disclosed above. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles and the practical application, to thereby enable others skilled in the art to best utilize the embodiments and various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A display device, characterized by comprising:

a display for presenting content;

A communicator for communicating with an external terminal and a server;

a controller configured to perform:

when the audio and video are presented on the display, the background acquires the external equipment supporting the audio and video playing through the server, when the terminal equipment supporting the audio and video playing is searched, a device information list is obtained, the device information list is presented on the display to provide an entrance of relay service,

when the user designates the target pushing end device based on the device information list, the user communicates with the target pushing end device based on the communication protocol channel to request the target pushing end device to relay to play the audio and video.

2. The display device of claim 1, wherein the controller includes a common relay component that is activated from a start-up of the display device for obtaining relay capability information of an application running in a foreground on the display device, wherein the relay capability information is used for indicating whether the application supports transmission of related content to an external terminal, and the content includes at least one of video, audio, text, and audio-visual quality setting parameters.

3. The display device of claim 2, wherein the common relay component transmits a device search request for obtaining a device identification and supportable relay capability information.

4. A display device, characterized by comprising:

a display for presenting content;

a communicator for communicating with an external terminal device;

a controller configured to perform:

responding to the startup of the display equipment, traversing relay capability information of each application program on the display equipment, and sending the relay capability information to a server, wherein the relay capability information is used for indicating whether the application program supports continuous acquisition of related content sent by an external terminal, and the content comprises at least one of video, audio, characters and audio-video quality setting parameters;

receiving a capability query request related to an external device, and judging whether an application supporting target relay capability exists on the display device or not based on the relay capability information;

when an application supporting the target relay capability exists on the display equipment, receiving a relay request sent by external equipment, wherein the relay request is used for requesting to continuously present target content provided by a pushing end application, and the relay request comprises pushing end application information and playing information of the target content;

Determining a target application according to the external application information, wherein the target application is an application with highest matching degree with the pushing end application or an application designated by a user on the display equipment;

5. The display device of claim 4, wherein the capability query message includes the target relay capability; the controller determines whether an application supporting a target relay capability exists on the display device based on the relay capability information, and is further configured to:

for applications having secondary relay capabilities, if the primary relay capability of the application and at least one secondary relay capability matches the target relay capability, the application supports the target relay capability; for applications without secondary relay capability, if the primary relay capability of the application matches the target relay capability, the application supports the target relay capability;

and returning a response message to the pushing end equipment according to the judging result.

6. The display device of claim 4, wherein the controller determines a target application from the push side application information, further configured to:

Judging whether the first-level relay capability applied on the display equipment is matched with the target relay capability;

judging whether the applied secondary relay capacity is matched with the target relay capacity or not under the condition that the applied primary relay capacity is matched with the target relay capacity and the application has the secondary relay capacity; if at least one secondary relay capability of the application is matched with the target relay capability, determining the application as a candidate application;

and determining the application as a candidate application and determining a target application from the candidate applications in the case that the primary relay capability of the application is matched with the target relay capability and the application does not have the secondary relay capability.

7. A content relay method, which is applied to a display device, wherein the display device comprises a display, a communicator and a controller,

8. A content relay method, which is applied to a display device, wherein the display device comprises a display, a communicator and a controller,