CN113794918A - Display device and content push method - Google Patents

Display device and content push method Download PDF

Info

Publication number
CN113794918A
CN113794918A CN202111130805.4A CN202111130805A CN113794918A CN 113794918 A CN113794918 A CN 113794918A CN 202111130805 A CN202111130805 A CN 202111130805A CN 113794918 A CN113794918 A CN 113794918A
Authority
CN
China
Prior art keywords
target
relay
content
protocol channel
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111130805.4A
Other languages
Chinese (zh)
Inventor
马晓燕
张娜
刘美玉
贾亚洲
庞秀娟
宋子全
马乐
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hisense Visual Technology Co Ltd
Original Assignee
Hisense Visual Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hisense Visual Technology Co Ltd filed Critical Hisense Visual Technology Co Ltd
Publication of CN113794918A publication Critical patent/CN113794918A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/4302Content synchronisation processes, e.g. decoder synchronisation
    • H04N21/4307Synchronising the rendering of multiple content streams or additional data on devices, e.g. synchronisation of audio on a mobile phone with the video output on the TV screen
    • H04N21/43078Synchronising the rendering of multiple content streams or additional data on devices, e.g. synchronisation of audio on a mobile phone with the video output on the TV screen for seamlessly watching content streams when changing device, e.g. when watching the same program sequentially on a TV and then on a tablet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

The application discloses a display device and a content pushing method, when target content is presented, external terminal equipment supporting target relay capacity is searched through one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels; responding to an instruction of pushing target content to target receiving end equipment in response to an instruction input by a user, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment; and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content. By selecting the appropriate protocol channel searching equipment and calling the target receiving terminal equipment, the searched equipment information can be ensured to be more comprehensive, 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 between the equipment is improved, and the user experience is improved.

Description

Display device and content push method
The present application claims priority from chinese patent application entitled "display device" filed by chinese patent office on 18/9/2021 with application number 202111097923.X, the entire contents of which are incorporated herein by reference.
Technical Field
The present application relates to the technical field of display devices, and in particular, to a display device and a content push method.
Background
Display devices such as smart televisions, smart screens and the like can provide playing pictures such as audio, video, pictures and the like for users, such as network video programs and live television programs, and can also provide various application and service contents such as network games, AI fitness, online education and the like for users.
In some scenes, for example, in a home, a plurality of terminal devices, such as a smart television, a smart screen of a refrigerator, a smart speaker, and the like, are generally present, and these terminal devices may communicate with each other and may communicate with terminal devices outside the scene based on a wide area network. Each terminal device may present content to the user including, but not limited to, music, video, speech, text, pictures, and the like. How to realize the sharing and continuous playing of contents between devices to improve user experience becomes a technical problem to be solved urgently.
Disclosure of Invention
The application provides a display device and a content pushing method.
In a first aspect, the present application provides a display device comprising:
a display for presenting content;
a speaker for presenting the content in conjunction with the display;
a communicator configured to communicate with an external terminal device through a local area network protocol channel, a wide area network protocol channel, and other protocol channels;
a controller configured to:
when presenting the target content, searching for an external terminal device supporting target relay capability through one or more of the local area network protocol channel, the wide area network protocol channel and other protocol channels, wherein the target relay capability refers to the capability required for presenting the target content;
presenting the searched device information of the external terminal device for the user to specify a target receiving terminal device from the external terminal device supporting the target relay capability;
responding to an instruction input by a user and indicating to push the target content to target receiving end equipment, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment, wherein the target protocol channel is one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels;
and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content.
In a second aspect, the present application further provides a content pushing method, where the method includes:
when presenting the target content, searching for an external terminal device supporting target relay capability through one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels, wherein the target relay capability refers to the capability required for presenting the target content;
presenting the searched device information of the external terminal device for the user to specify a target receiving terminal device from the external terminal device supporting the target relay capability;
responding to an instruction input by a user and indicating to push the target content to target receiving end equipment, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment, wherein the target protocol channel is one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels;
and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content.
According to the technical scheme, based on the display device and the content pushing method provided by the embodiment of the application, when the target content is presented, the external terminal device supporting the target relay capability is searched through one or more of the local area network protocol channel, the wide area network protocol channel and other protocol channels; responding to an instruction of pushing target content to target receiving end equipment by an instruction input by a user, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment, wherein the target protocol channel is one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels; and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content. By selecting the appropriate protocol channel searching equipment and calling the target receiving terminal equipment, the searched equipment information can be ensured to be more comprehensive, 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 between the equipment is improved, and the user experience is improved.
Drawings
FIG. 1 is a usage scenario of a display device shown in some embodiments of the present application;
fig. 2 is a block diagram of a hardware configuration of the control apparatus 100 shown in some embodiments of the present application;
fig. 3 is a block diagram of a hardware configuration of a display device 200 shown in some embodiments of the present application;
FIG. 4 is a diagram of the software configuration in a display device 200 shown in some embodiments of the present application;
FIG. 5 illustrates a block diagram of a software configuration of a common relay component in accordance with an exemplary embodiment;
fig. 6 is a relay flow diagram shown in accordance with 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 illustrated in accordance with an exemplary embodiment of the present application;
FIG. 14 illustrates a display device user interface;
FIG. 15 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 16 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 17 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 18 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 19 is a schematic diagram of another relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 20 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
fig. 21 is a schematic diagram of another relay scenario illustrated by the present application in accordance with an exemplary embodiment;
fig. 22 is a schematic diagram of another relay scenario illustrated by the present application in accordance with an exemplary embodiment;
FIG. 23 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 24 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 25 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 26 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
27A and 27B are schematic diagrams of a user interface of a receiving end device according to an exemplary embodiment of the present application;
FIG. 28 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 29 is a relay scenario diagram illustrating an exemplary embodiment of the present application;
FIG. 30 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 31 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 32 is a schematic diagram of a relay scenario illustrated in accordance with an exemplary embodiment of the present application;
FIG. 33 is an interaction flow diagram, shown herein in accordance with an illustrative embodiment;
FIG. 34 is an interaction flow diagram illustrated by the present application in accordance with an exemplary embodiment.
Detailed Description
To make the purpose and embodiments of the present application clearer, the following will clearly and completely describe the exemplary embodiments of the present application with reference to the attached drawings in the exemplary embodiments of the present application, and it is obvious that the described exemplary embodiments are only a part of the embodiments of the present application, and not all of the embodiments.
It should be noted that the brief descriptions of the terms in the present application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of the present application. These terms should be understood in their ordinary and customary meaning unless otherwise indicated.
The terms "first," "second," "third," and the like in the description and claims of this application and in the drawings are used for distinguishing between similar or analogous objects or entities and not necessarily for limiting a particular order or sequence unless otherwise indicated. It is to be understood that the terms so used are interchangeable under appropriate circumstances.
The terms "comprises" and "comprising," 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 expressly 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 and/or software code that is capable of performing the functionality 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 illustrate 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 capable of communicating with the terminal devices. In the scenario shown in fig. 1, the mobile terminal includes a display device 200, a mobile terminal 300, a refrigerator smart screen 400, a smart box 500, a speaker device 600, and a server 700.
Based on the internet of everything technology, communication connection can be established among a plurality of terminal devices in the above scenario. The communication protocols for realizing the above-mentioned everything interconnection can include a local area network protocol, a wide area network protocol and a short-range wireless communication protocol which 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, infrared transmission protocol. Based on the difference of the foregoing communication protocol types, the communication protocol channel of the terminal device may 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 device in the above scenario may support one or more of the aforementioned protocol channels.
The terminal device can establish a communication connection with the server to perform information interaction with the server, for example, various contents and interaction information are provided for the terminal device. The terminal device may be allowed to make communication connections via a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. 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-control integrated device, a projection device, a tablet computer, a notebook computer, an intelligent cooking device, and the aforementioned external devices related to various terminal devices, such as a keyboard, a mouse, and a game pad. The number of the same kind of terminal devices may be one or more. For example, multiple display devices 200 may be present in a scene at the same time.
In some embodiments, different terminal devices may be controlled with each other, or may be controlled by the control apparatus 100 for a specific terminal device. For example, the user may operate the display apparatus 200 through the control device 100 or the mobile terminal 300. As another example, the user may operate the smart box 500 or the smart screen 400 of the refrigerator through the smart device 300, and/or operate the sound box device 600 or the like through the operation of the display device 200 or the smart device 300.
In some embodiments, the control apparatus 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-distance communication methods, and interacts with the terminal device through a wireless or wired method. The user can input user instructions through keys on the 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 be controlled by a manner other than controlling apparatus 100 or other terminal devices, for example, the voice instruction control of the user may be directly received by a module configured inside the device for acquiring a voice instruction, or may be received by a voice control device provided outside the device.
Fig. 2 exemplarily shows a block diagram of a configuration of the control apparatus 100 according to 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 can receive an input operation instruction of a user, and convert the operation instruction into an instruction which can be recognized and responded by the terminal equipment, and plays a role in interaction mediation between the user and the terminal equipment.
In some embodiments, a 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 tuner demodulator, a detector, an external device interface, an audio output interface, a power supply, and a user interface. The controller includes a processor, a video processor, an audio processor, a graphic processor, a RAM, a ROM, and first to nth interfaces for input/output.
Taking the display apparatus 200 as an example, fig. 3 shows a hardware configuration block diagram of the display apparatus 200 according to an exemplary embodiment. As shown in fig. 3, the display apparatus 200 includes, but is not limited to, at least one of a tuner demodulator 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.
In some embodiments, the display may be a liquid crystal display, an OLED display, and a projection display, and may also be a projection device and a projection screen.
The communicator is a component for communicating with an external device or a server according to various communication protocol types. For example: the communicator may include at least one of a Wifi module, a bluetooth module, a wired ethernet module, and other network communication protocol chips or near field communication protocol chips, and an infrared receiver. The terminal device can establish transmission and reception of the control signal and the data signal with other terminal devices, the control apparatus, or the server through the communicator.
The user interface can be used for receiving control signals of a control device (such as an infrared remote controller and the like).
The detector is used for acquiring signals of 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 includes an image collector, such as a camera, which may be used to collect external environment scenes, attributes of the user, or user interaction gestures, or the detector 230 includes a sound collector, such as a microphone, which is used to receive external sounds.
In some embodiments, the image collector is a camera module, and the camera module includes a camera for collecting an image and a depth-sensing camera for depth information of the collected image, such as an RGBD camera. Through the camera module, can gather the depth information of image and image.
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, and the like. The interface may be a composite input/output interface formed by the plurality of interfaces.
And a controller for controlling the operation of the terminal device and responding to the user's operation 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 for selecting a UI object to be displayed on the display, the controller may perform an operation related to the object selected by the user command.
The object may be any of a number of selectable objects, such as a hyperlink, an icon, or other operable control. The operations related to the selected object are: displaying an operation connected to a hyperlink page, document, image, or the like, or performing an operation of a program corresponding to the icon.
In some embodiments the controller comprises at least one of a Central Processing Unit (CPU), a video processor, an audio processor, a Graphics Processing Unit (GPU), a RAM Random Access Memory (RAM), a ROM (Read-Only Memory), a first to nth interface for input/output, a communication Bus (Bus), and the like.
In some embodiments, the system of the terminal device may include a Kernel (Kernel), a command parser (shell), a file system, and an application program. The kernel, shell, and file system together make up the basic operating system structure that allows users to manage files, run programs, and use the system. After power-on, the kernel is started, kernel space is activated, hardware is abstracted, hardware parameters are initialized, and virtual memory, a scheduler, signals and interprocess communication (IPC) are operated and maintained. And after the kernel is started, loading the Shell and the user application program. The application program is compiled into machine code after being started, and a process is formed.
Referring to fig. 4, in some embodiments, the system is divided into four layers, which are an Application (Applications) layer (abbreviated as "Application layer"), an Application Framework (Application Framework) layer (abbreviated as "Framework layer"), an Android runtime (Android runtime) and system library layer (abbreviated as "system runtime library layer"), and a kernel layer from top to bottom.
In some embodiments, at least one application program runs in the application program layer, and the application programs may be windows (windows) programs carried by an operating system, system setting programs, clock programs or the like; or 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, a common relay component and at least one content application are configured in an operating system of the terminal device. A content application refers to an application that can provide content or render content, such as a camera application, a picture resource application, a picture viewing application, a video call application, a video playing application, an audio call application, an audio resource application, a mapping application, a reading application, and so forth. The content includes pictures, audio (including call audio, audio files, and live audio streams), video (including call video, video files, and live video streams), text, geographical location information, navigation information, and the like. Presenting content includes displaying pictures, geographical location information or navigation information and text, playing video files, video call pictures and live room pictures, playing audio files, call sounds and live room sounds, etc. The public relay component is used for pushing the content presented by any one content application to the external terminal equipment so as to continue playing on the external terminal equipment; and the server is also used for receiving the content and the playing information thereof pushed by the public relay assembly on the external terminal equipment and continuing playing the content through the content with the capability of playing the content.
In some embodiments, any one content application can push content to other terminal devices capable of establishing communication connection through the common relay component, so that the function of pushing content does not need to be configured on each content application. Any content application can receive the push of other terminal equipment to a certain content through the public relay component so as to carry out capacity continuation on the content, so that the function of receiving the push of the content does not need to be configured on each content application. In the foregoing content pushing, receiving and resuming process, the public relay component on the pushing end device (receiving end device) is responsible for communicating with the public relay component on the receiving end device (pushing end device) to complete the foregoing content pushing, receiving and resuming process.
For convenience of description, the above-mentioned processes of content pushing, receiving and capability continuing executed by the pushing end device and the receiving end device are referred to as a relay process. The push end device is a terminal device initiating content push, and the receiving end device is a content push target, or a terminal device receiving the content and connecting the push end device to continue playing the content. Based on the data flow direction, the relationship between the push end device and the receiving end device may be described as that the push end device pushes a certain content to the receiving end device, and the receiving end device performs relay playing on the content pushed by the push end device. It should be understood that the terminal device related to the present application may at least serve as a receiving terminal device, and relay play content pushed by other terminal devices, such as a song pushed by a mobile phone via an intelligent sound box device. The terminal equipment related to the application can be used as receiving end equipment, and meanwhile can also be used as pushing end equipment to push contents outwards, if the mobile phone pushes the current song to the intelligent sound box for continuous playing, the mobile phone receives the video program pushed by the intelligent television for continuous playing.
In some embodiments, the capability continuation includes, but is not limited to, at least one of an alarm setting, a picture quality sound quality parameter setting, a file review, etc., of a resume (e.g., a video resume, an audio resume, etc.) of the media asset.
FIG. 5 illustrates a block diagram of a software configuration of a common relay component according to an exemplary embodiment. As shown in fig. 5, the common relay component 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 interacting content application on the home terminal equipment. And the interaction center module is internally provided with an SDK for each application program to call, and each application program interacts with the interaction center module by calling the SDK. For example, when the user triggers an operation for transferring the current content to a specified terminal device for continuous playing in the content application, the content application notifies the interaction hub module to send by calling the SDK, so that the common relay component responds to the operation of the user. For another example, the interaction center module feeds back various types of state information in the content pushing process to the corresponding content application program.
And the state management module is used for managing various types of state information generated in the interaction process with other terminal equipment, such as state information representing the success or failure of pushing, state information representing abnormal conditions, various types of notification messages and the like. Management includes, but is not limited to, classification information, discrimination information to perform corresponding processing 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 in the user interface, such as window objects, tabs, status information prompt boxes and various operable buttons.
The protocol processing module is used for selecting a protocol channel through which interaction with other terminal equipment is carried out 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 carries out information interaction 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 in a certain working mode and logic control in the case of multi-device interaction.
In some embodiments, the functional modules of the common relay component are deployed at the application layer. In other embodiments, the functional modules of the common relay component may be deployed across layers, for example, the interaction hub module and the interface presentation module are deployed at an application layer, and the other modules are deployed at other layers. This is not a limitation of the present application. It should be noted that, in order 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 common relay component related to the embodiment of the present application, components of other compositions and architectures are all within the protection scope of the present application.
Referring to fig. 4, the framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions. The application framework layer acts as a processing center that decides to let the applications in the application layer act. The application program can access the resources in the system and obtain the services of the system in execution through the API interface.
As shown in fig. 4, in the embodiment of the present application, the application framework layer includes a manager (Managers), 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 for interacting with all activities running in the system; the Location Manager (Location Manager) is used for providing the system service or application with the access of the system Location service; a Package Manager (Package Manager) for retrieving various information related to an application Package currently installed on the device; a Notification Manager (Notification Manager) for controlling display and clearing of Notification messages; a Window Manager (Window Manager) is used to manage the icons, windows, toolbars, wallpapers, and desktop components on a user interface.
In some embodiments, the activity manager is used to manage the lifecycle of the various applications as well as general navigational fallback functions, such as controlling exit, opening, fallback, etc. of the applications. The window manager is used for managing all window programs, such as obtaining the size of a display screen, judging whether a status bar exists, locking the screen, intercepting the screen, controlling the change of the display window (for example, reducing the display window, displaying a shake, displaying a distortion deformation, and the like), and the like.
In some embodiments, the system runtime layer provides support for the upper layer, i.e., the framework layer, and when the framework layer is used, the android operating system runs the C/C + + library included 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 core layer includes at least one of the following drivers: audio drive, display driver, bluetooth drive, camera drive, WIFI drive, USB drive, HDMI drive, sensor drive (like fingerprint sensor, temperature sensor, pressure sensor etc.) and power drive etc..
In some embodiments, a user may enter a user command on a Graphical User Interface (GUI) displayed on the 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 receives the user input command by recognizing the sound or gesture through the sensor. The user interface is an interface (such as physical keys on the display device body or the like) which can be used for receiving control input.
In some embodiments, a "user interface" is a media interface for interaction and information exchange between an application or operating system and a user that enables conversion between an internal form of information and a form that is acceptable to the user. A commonly used presentation form of the User Interface is a Graphical User Interface (GUI), which refers to a User Interface related to computer operations and displayed in a graphical manner. It may be an interface element such as an icon, a window, a control, etc. displayed in the 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, the relevant information of the content can be pushed to a terminal device designated by a user in response to a user control, so that the terminal device designated by the user continues to play the content according to the relevant information of the content. For convenience of description, in the following embodiments, a terminal device that initiates content push is referred to as a push-end device, and a terminal device that accepts content push and resumes playing is referred to as a receive-end device. It should be noted that the push end device and the receiving end 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 smart screen of a refrigerator, or devices having only an audio output function but no image display function, such as a sound box device and a radio.
For example, when a user watches a certain television episode on a television in a living room, the user wants to go to a kitchen for cooking, and a 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 serial operations on the television in the living room. Therefore, the user can cook and continue to watch the television episode through the intelligent screen of the refrigerator. For another example, if the user listens to a certain song on the bedroom television and wants to go to the living room, and the living room has a sound box, the user can push the song to the sound box in the living room to continue playing through series of operations on the bedroom television.
The terminal equipment can realize the functions through the built-in public relay assembly. Various implementation modes 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 started, the common relay component is started, and the call of any content application can be received.
In some embodiments, after the common relay component is started, the relay capabilities of all content applications in the system are scanned according to the standard interface of the operating system. The relay capability, as the name implies, refers to the capability of an application program to continuously present content, such as the type and presentation manner of the content that can be presented. Taking a media application as an example, the content presentation capability may be the capability of playing a video file, including parameters of the playable video file. For the receiving end device, when it receives the request of the pushing end device to push the content, the application program conforming to the content through the relay capability continues to play the content. Exemplarily, if the relay content is a video, the receiving end device needs to continue playing the video through a video playing application thereon; if the relay content is a text, the receiving device needs to continue to display the text through a text application (such as a notepad) on the receiving device.
In some embodiments, the relay capabilities may have different levels, such as primary capabilities, secondary capabilities. In view of the actual functionality of the content application, the true relay capability of the content application may be described by one level of relay capability or a combination of multiple levels of capability. It should be understood that the relay capabilities of each application may be customized according to its actual functionality. The embodiment of the present application does not limit the data form of the relay capability and the data content thereof. It should be noted that the relay capability applied to the terminal device determines what contents can be relayed by the terminal device. That is, the relay capability applied on a terminal device determines the ability of the terminal device to relay other device content. For example, when a certain terminal device does not have an application for playing a certain content in a relay manner, the terminal device cannot play the content in the relay manner, and thus cannot become a target receiving device of the content.
In some embodiments, after the common relay component scans the relay capabilities of the respective applications, 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, where the local area network protocol component refers to a functional component for responding to an instruction, a request, and other interactive information sent by an external device based on a 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 lan based on the lan protocol channel, the relay capabilities of the application programs registered in advance by the common relay component are fed back to the second terminal device, or a response is made to the capability query message, such as a response that a certain relay capability is supported or a certain relay capability is not supported. Therefore, the second terminal device can know the relay capability of the first terminal device, and determine whether the first terminal device can be used as a receiving terminal device of certain content according to the relay capability.
In other embodiments, after the public relay component scans the relay capabilities of each application program, the relay capability data may be uploaded to the cloud server, so that the cloud server may query the relay capabilities of each application program on the designated terminal device. For example, when the cloud server receives an inquiry request sent by the first terminal device for inquiring the relay capability of the second terminal device, relay capability data uploaded in advance by the second terminal device may be returned to the first terminal device in response to the inquiry request. Therefore, the first terminal device can know the relay capability of the second terminal device through the cloud server, and whether the second terminal device can be used as a receiving terminal device of a certain content or not is judged according to the relay capability.
In other embodiments, after the common relay component scans the relay capabilities of each application program, 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, and the like may obtain the relay capability data in the designated path.
In some embodiments, the common relay component may select one or more of the above manners according to a communication policy with other terminal devices to store 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 the communication with other terminal devices is based. For example, if the terminal device is limited to communicate 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 in the lan protocol component; if the terminal equipment can also communicate with equipment outside the local area network based on the WAN protocol channel, the public relay assembly can select to upload the relay capacity data to the cloud server so that other equipment can know the relay capacity of the terminal equipment through the cloud server.
In some embodiments, when the terminal device presents a certain content presented by a certain content application, the common relay component may search, according to the relay capability of the content application, the terminal device matching the relay capability to obtain a device information list, where the device information list is device information of the optional receiving end device. The user specifies the target push terminal device based on the device information list, and the public relay component can communicate with the target push terminal device based on a certain communication protocol channel to request the target push terminal device to relay and play the content. And the public relay component on the target push terminal equipment responds to the request, starts the content application with the relay capability and continues to play the content through the content application with the relay capability.
It is noted that in a more specific implementation of the above embodiment, the content application on the push-side device needs to interact with the common relay component in response to a user operation. The common relay component may perform certain operations in response to the interaction information from the content application. In addition, because the common relay component has a function of presenting an interface object independent of the content application, the user can directly interact with the common relay component through the interface object provided by the common relay component to directly control the common relay component to perform certain operations. In other words, in a more specific implementation of the above-described embodiments, the common relay component on the push-side device may perform certain operations in response to user input.
For convenience of description, in the following embodiments, a content that a user desires to push is referred to as a target content, a relay capability of an application that provides the target content on a push end device is referred to as a target relay capability, and an application that supports the target relay capability on a target receiving end device is referred to as a target application. In addition, the public relay assembly on the push terminal equipment can be referred to as the push terminal relay assembly for short, and the public relay assembly on the receiving terminal equipment can be referred to as the receiving terminal relay assembly for short. It is to be understood that the foregoing definitional designations are provided to facilitate explanation and distinction between concepts. In some embodiments, the description may use other names, so that the context of a name is used to determine the substance of the name.
Fig. 6 is a relay flow diagram according to an exemplary embodiment of the present application. As shown in fig. 6, the process specifically includes the following steps:
s601, the push terminal device presents the target content provided by a certain content application.
In fact, the target content may be any content presented by the content application. It should be understood that the types of targeted content provided by different content applications may or may not be the same. The same content application may also provide different types of content. For example, for a media application, the content presented by the media application is mostly video content, picture content or audio content. For reading applications, the content presented by the reading applications is mostly text content.
FIG. 7 illustrates a display device user interface. As shown in fig. 7, the media application interface is displayed on the display device in a full screen, and the media application interface has a video playing window in which a certain video content provided by the media application is being played.
S602, the content application on the push terminal equipment sends the target relay capacity to the public relay component.
The target relay capability is a relay capability of the content application providing the target content in S601.
In an alternative implementation, when the content application interface meets a preset condition, the content application sends its own relay capability to the common relay component. For example, when the target content is played in a full screen, the content application interface is considered to satisfy the preset condition. In another implementation, the content application may send its own relay capability to the common relay component when other conditions are met. For example, when the content application receives a particular user input, the content application sends its own relay capabilities to the common relay component. The present application is not limited thereto.
S603, the public relay assembly on the pushing end device searches for the terminal device supporting the target relay capability to obtain a device information list.
In some embodiments, after receiving the target relay capability sent by the content application, the common relay component on the push-end device starts to search for the terminal device supporting the target relay capability, so as to obtain the device information list. The device information list is composed of device information of selectable sink devices. It should be understood that the common relay component search result can be divided into two cases, one is that at least one optional receiving end device is searched, and the other is that the optional receiving end device is not searched. If the optional receiving end equipment is searched, the current scene meets the preset content pushing condition, and if the optional receiving end equipment is not searched, the current scene does not meet the content pushing condition.
In some embodiments, the device search request is sent to the common relay component when the content application determines that the current scene satisfies a preset content push condition. The public relay component responds to a device search request sent by the content application, and searches the external terminal device supporting the target relay capacity according to the target relay capacity in the device search request.
In other embodiments, the public relay component provides an interactive interface for a user to input a device search instruction, so that the public relay component can directly receive the device search instruction input by the user, and respond to the device search instruction to acquire the relay capability of the content application to obtain the target relay capability; and searching the external terminal equipment supporting the target relay capability according to the target relay capability. For example, when the target content is presented, the common relay component controls to present an interface object for triggering presentation of the device information, and the user can input a device search instruction by operating the interface object.
In some optional implementation manners, the public relay component on the push terminal device sends a device search request to the cloud based on a wide area network communication protocol channel, where the device search request includes a push terminal information identifier and a target relay capability. The push terminal information identifier may be an account identifier logged in on the push terminal device, such as an account identifier of a login content application. After receiving the device search request, the cloud searches for terminal devices associated with the push-end device according to the push-end information identifier, for example, terminal devices which log in the same account with the push-end device; after the cloud finds the terminal devices associated with the pushing terminal devices, the terminal devices matched with the target relay capacity are determined according to the relay capacity data uploaded by the terminal devices. For example, when the relay capability of the application on a certain terminal device matches the target relay capability, the terminal device is determined as the terminal device matching the target relay capability. And if the cloud finds at least one terminal device matched with the target relay capacity, generating a device information list containing the at least one terminal device, and feeding back the device information list to the pushing terminal device. And if the cloud end does not find the terminal equipment matched with the target relay capacity, 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 public relay component on the push end sends a capability query message to a terminal device in a local area network based on a local area network communication protocol channel; after receiving the capability inquiry message, the terminal device in the local area network feeds back the relay capability of each application registered in the local area network component to the pushing terminal device by returning a response message; and the push terminal equipment determines optional push terminal equipment according to the relay capability fed back by the terminal equipment in the local area network.
In some embodiments, the common relay component on the push end starts a near field communication protocol channel, and receives relay capability data sent by nearby terminal devices based on the near field communication protocol channel, so as to determine the terminal device 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 that support the target relay capability based on the selected communication protocol channel. By selecting the appropriate protocol channel to search the equipment, the searched equipment information can be ensured to be more comprehensive, 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 between the equipment is increased, and the user experience is improved.
In other embodiments, the user may preset a protocol channel for communicating with the sink device. And the public relay component searches the terminal equipment supporting the target relay capability based on a communication protocol channel preset by the user. It should be understood that, if the communication protocol channel set by the user is a local area network protocol channel, the terminal device searched by the common relay component is a device in the same local area network as the push terminal device; if the communication protocol channel set by the user is a wide area network protocol channel, the terminal equipment searched by the public relay component can be equipment 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 common relay component is a terminal device near the push terminal device.
In some embodiments, the push-side common relay component performs a search for external terminal devices supporting the target relay capability over a wide area network protocol tunnel, further configured to: sending an equipment query request to a server through a local area network protocol channel, wherein the equipment query request comprises a push terminal identifier and target relay capacity corresponding to display equipment; 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 queried by the server, is associated with the push terminal identification and supports the target relay capability. In some embodiments, the device information includes a unique identification of the device and communication protocol information supported by the device. Some of the communication protocols supported by the terminal devices may be categorized into one or more of a local area network protocol channel, a wide area network protocol channel, and a short-range communication protocol channel. For example, some terminal devices may communicate with the push-end device through a local area network protocol channel, and may also communicate with the push-end device through a near field communication protocol channel. And for some terminal devices, the terminal devices can only communicate with the push terminal device 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 that when the device information needs to be presented, the integrated device information is presented, and repeated device information is prevented from being presented.
An exemplary integration result is as follows:
the terminal device A: supporting AIOT \ LAN \ Bluetooth;
and a terminal device B: local area network/Bluetooth is supported;
and a terminal device C: bluetooth is supported.
In some embodiments, when the common relay component on the push end device searches for the terminal device, the common relay component presents a prompt message on the current interface for prompting the user that the device is currently being searched. For example, as shown in fig. 8, a prompt message with "device being sought" content is displayed on the play screen.
S604, the public relay assembly on the pushing end device feeds back a search result to the content application, and the search result represents that the optional receiving end device exists.
And S605, after the content application on the push terminal equipment receives the input relay operation, sending an equipment presentation request to the public relay component.
In some embodiments, when the content application presents certain content, the user may control the control area to be called out through a certain operation or a combination of operations. The control area is centrally provided with user operable controls, and the user triggers the terminal equipment to execute corresponding operations 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, and the first search result indicates that the optional receiving end device exists. If the content application receives the first search result, when the user operates the call-out control area, an interface object for triggering the relay flow is displayed in the control area, so that the user can input the relay operation by operating the interface object. And if the content application does not receive the first search result, not displaying the interface object for triggering the relay flow in the control area when the user operates the call-out control area.
In another implementation, a common relay component on the push end device feeds back search results to the content application, where the search results characterize whether an optional receiving end device exists. And the content application determines whether to display an interface object for triggering the relay flow when the user calls out the control area according to the meaning represented by the search result.
In some implementation manners, when the content application determines that the optional receiving terminal device exists according to the search result, the interface object for triggering the relay flow is directly displayed on the interface, and the interface object is displayed in the control area without calling out the control area by the user operation.
As shown in fig. 9, the control area includes, but is not limited to, at least one of a "relay" control, a "playlist" control, a "definition" control, and a "recommended function" control. The user can trigger the display device to execute corresponding operation by operating a certain control. For example, when the user selects the "playlist" control, the display device will display a list of albums. It is worth noting that the user can input the content relay operation by operating the relay control 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 an operation of the user on the relay control, the media application sends the relay operation to the common relay component.
Of course, the user may also input the content relay operation in other manners, such as using a voice control function of the display device, inputting the content relay operation through a voice password, or inputting the content relay operation through a designated key or a combination of keys on the control device.
S606, the public relay assembly on the push terminal device presents a device information list, and the device information list comprises at least one optional receiving terminal device option.
In some embodiments, if at least one external terminal device supporting the target relay capability is searched, the common relay component controls to display an interface object for triggering presentation of device information, and at this time, a user may instruct presentation of the searched device information by operating the interface object; the public relay component responds to an input equipment presentation instruction and presents 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 option, determining that a content push instruction is received, wherein the target equipment option corresponds 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, such as "second floor living room tv", "first floor kitchen refrigerator", "second floor sound box", "first floor living room tv", and the like. At this time, the user may specify the target sink device by inputting a selection operation for a certain option in the list. For example, when the user selects "second floor living room television," the device named "second floor living room television" is designated by the user as the target sink device.
S607, when the public relay component on the push end device receives the input selection operation on the target receiving end device, it requests the content application for the playing information of the target content.
And S608, the content application on the pushing end device returns the playing information of the target content to the public relay component.
The playing information of the target content is used for enabling an application on the receiving terminal device to continue to 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, and the like, 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 at least include user position 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 for the user. It should be understood that, depending on the content application, the parameters included in the corresponding playing information may be the same or different. The playing information of a certain content application on the push end device should be able to be parsed and identified by at least one content application on the receiving end device to continue to present the target content.
In other embodiments, the user may instruct the common relay component to search for terminal devices that support the target relay capability through a voice control function while the content application presents the target content. For example, referring to fig. 11A, after waking up the voice application, the user speaks "find relay device", and the voice application determines the user input device search instruction by parsing the semantics of the voice data. And sending the device searching instruction to the public relay component, and replying the user 'good, starting to inquire' on the interface. And the public relay component responds to a device search instruction sent by the voice application, searches the terminal device supporting the target relay capability and obtains a device information list.
Next, the common relay component sends the searched device information list to the voice application, reads the specific content of the device information list through the voice application, and displays the device information list on the interface in text, as shown in fig. 11B. After obtaining the device information list, the user can designate a target receiving end device through a voice control function and instruct the pushing end device to execute a relay flow. For example, the user speaks "relay to second floor living room television", the voice application determines that the target receiving end device designated by the user is the terminal device named "second floor living room television" by analyzing the semantic meaning of the voice data, and the voice application sends the device information of the target sending end device to the public relay component and replies "good, relaying" to the user, as shown in fig. 11C. And after receiving the target receiving end information, the public relay assembly requests the content application for the playing information of the target content and executes the subsequent steps.
In addition, the user may also trigger some links in the relay flow through operation modes such as a touch gesture, an air gesture, and the like, which is not described herein again.
And S609, the public relay assembly on the pushing end equipment sends a call request to the target receiving end equipment, wherein the call request comprises the target relay capability and the playing information of the target content.
In some embodiments, the call request is also referred to as a baton request.
In some embodiments, after receiving a selection operation of a target push end device by a user, a common relay component on the push end device calls the target receiving end device after waiting for a preset duration. And the public relay component on the pushing end device displays a prompt message on the interface during waiting. During the display period or the waiting period of the prompting message, the user can cancel the pushing through some operation, or can instruct the pushing immediately through some operation. And if the public relay component receives a cancel instruction input by a user during the display period or the waiting period of the prompt message, executing the step of canceling the push. That is, the push end device responds to the input instruction of pushing the currently presented target content to the target receiving end device, and controls the presentation of the prompt information, so that the user is prompted by the prompt information to input a push cancel instruction or a push confirm instruction within a preset time; responding to the push confirmation instruction input by the user within a preset time length, and sending a relay request to the target receiving terminal equipment to request the target receiving terminal equipment to continuously present the target content; or, in response to the push cancel instruction input by the user within the preset time, canceling the sending of the relay request to the target receiving end. And if the input push confirmation instruction or the push cancellation instruction is not received within the preset time, sending a relay request to the target receiving terminal equipment at the termination moment of the preset time, and canceling the display of the prompt message. In other embodiments, after receiving a selection operation of a target push end device by a user, a common relay component on the push end device displays a prompt message on a current interface while executing a call to the target receiving end device. During the display of the prompting message or within a preset time, the user can cancel the pushing through some operation. And if the push terminal equipment receives a cancel instruction input by a user during the display period of the prompt message or within the preset time, executing a step of canceling the push. For example, if the target receiving-end device is not called upon receipt of the input cancel instruction, the call is blocked. If the target receiving end equipment is called when the input cancelling instruction is received, a cancelling relay request is sent to the target receiving end equipment, so that the target receiving end equipment interrupts the relevant operation.
That is, the push 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 continues to present the target content according to the relay request; and responding to a push canceling instruction input by a user and received within a preset time length, and sending a relay canceling request to the target receiving terminal equipment so as to enable the target receiving terminal equipment to cancel the presentation of the target content. Therefore, the user has a certain time to confirm the push operation input before, and whether the push operation is withdrawn or not is considered, so that the target content is prevented from being pushed to the target receiving terminal equipment due to misoperation of the user, and the user experience is improved.
Illustratively, the user can input the above-mentioned push cancel instruction by operating any key. The user can input the push confirmation instruction through the appointed key.
In some embodiments, after the public relay component on the push end device receives a selection operation of a user on a target push end device, a countdown is performed while a prompt message is displayed, 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 on the interface showing the countdown progress to expose a visual cue of the countdown progress to the user.
Fig. 12 is an application interface displayed on the push-side device after the user selects "second floor living room tv" as the target receiving-side device in fig. 10. As shown in fig. 12, a prompt message indicating that "tv is to be pushed to the second floor living room for playing, stop by pressing any key, and relay immediately by pressing the enter key" is displayed on the interface, and a visual prompt "3" indicating a countdown progress is displayed on one side of the prompt message.
In some embodiments, after receiving a push cancellation instruction input by a user, a common relay component on the push end device displays corresponding prompt information on an interface, and sends a relay cancellation request to the target receiving end device. And after the public relay assembly on the target receiving terminal equipment receives the relay cancellation request, displaying corresponding prompt information on an interface of the receiving terminal equipment.
Fig. 13 is a schematic diagram of a push scenario illustrated in accordance with an exemplary embodiment of the present application. The interface of the push-end device in fig. 13 is specifically an interface displayed after the push-end force assembly receives a push cancel instruction input by a user, and as shown in fig. 13, a prompt message with a content of "push cancelled" is displayed on the interface of the push-end device. The interface of the receiving end device in fig. 13 is specifically an interface displayed after the receiving end relay assembly receives the relay cancellation request sent by the push end device, and as shown in fig. 13, a prompt message indicating that "the bedroom television cancels push" is displayed on the interface of the receiving end device.
It should be noted that, the public relay components on the push end device and the receiving end device may broadcast the message by invoking the voice application, including but not limited to the above-mentioned prompt information of "push has been cancelled" and "push has been cancelled for the bedroom tv".
In some embodiments, after the push end device sends the relay request to the target receiving end device, the content application on the push end device may continue to present the target content, or may end presenting the target content.
In some alternative implementations, the user may set a specified function of the content application. After the push terminal equipment sends the relay request to the target receiving terminal equipment, the content application determines whether to continue to present the target content according to the user setting. For example, when the user starts the function of "original device continues playing" of the content application, the content application continues to present the target content after the push end device sends the relay request to the target receiving end device. Under the condition that the user closes the function of 'original equipment continues playing' of the content application, the content application continues to present the target content after the push end equipment sends the relay request to the target receiving end equipment. Based on this, after sending the relay request to the target receiving end device, the push 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 a 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, a user can operate "? The control is triggered to enter a relay function introduction page, and the relay function introduction page is at least used for displaying introduction information of the relay function, such as a relay operation mode. In the device information list page shown in fig. 10, guidance information indicating "order adjustment by pressing the confirmation key and pressing the menu key" is displayed. The guide information is used for reminding a user, and under the condition of selecting a certain equipment option, the relay process can be triggered by operating a confirmation key on the remote controller, 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, a switch button for "original device continues playing" is also displayed on the device information list page shown in fig. 10, and when the user operates the switch button to turn on, that is, the function of "original device continues playing" of the content application is turned on, then the content application continues playing the content after the public relay component pushes the content to the receiving end device. When the user operates to turn off the switch button, that is, the function of "original device continues playing" of the content application is turned off, then, after the public relay assembly pushes the content to the receiving end device, the content application can exit to finish playing the content.
In some embodiments, after the push-end device sends the relay request to the target receiving-end device, the method further includes: receiving play state information sent by target receiving end equipment, and acquiring a target setting parameter, wherein the target setting parameter is a first value or a second value; if the playing state information represents that the target receiving terminal equipment successfully responds to the relay request and the target setting parameter is a first value, controlling the content application to end playing the target content; and if the playing state information represents that the target receiving terminal equipment fails to respond to the relay request or the target setting parameter is a second value, controlling the content application to continue playing the target content.
S610, the public relay assembly on the target receiving end equipment responds to the call request sent by the pushing end equipment, and starts the target application supporting the target relay capability.
In some embodiments, when only one target application supporting the target relay capability is available on the target receiving end device, then the common relay component directly launches the application. When the target receiving terminal equipment has a plurality of target applications supporting the target relay capability, the public relay component starts a preset default application, or starts a target application with the highest priority level according to the preset priority level of each target application, or displays an application list consisting of the plurality of target applications in an interface to prompt a user to designate a certain target application, so as to start the target application designated by the user.
In some embodiments, after the public relay component on the receiving end device receives the call request of the pushing end device, the public relay component starts the supporting target application after waiting for a preset time. And the public relay assembly on the receiving terminal equipment displays a prompt message during waiting. During the display period or the waiting period of the prompting message, the user can cancel the relay through some operation, or can instruct the relay immediately through some operation. If the receiving end equipment receives a relay cancellation instruction input by a user in the display period or the waiting time of the prompt message, the step of cancelling the relay is executed. In other embodiments, the common relay component on the receiving end device responds to the call request of the pushing end device, and displays the prompt message on the interface while searching the target application. During the display period of the prompting message or within the preset time, the user can cancel the relay through some operation. And if a cancel instruction input by a user is received during the display period of the prompt message or within a preset time, executing a step of canceling the relay. For example, if the supporting target application is not started or the target application does not start to present the target content when the input cancel relay instruction is received, starting or stopping playing is prevented, and a cancel message is sent to the push-end device. And if the target application starts playing the target content when receiving the input relay cancellation instruction, ending the playing and sending a cancellation message to the pushing end equipment.
That is to say, the public relay assembly on the receiving end device controls to present some prompt information in response to receiving the relay request sent by the pushing end device, so as to prompt the user to input a relay cancellation instruction or a relay confirmation instruction within a preset time through the prompt information; responding to a relay confirmation instruction input by a user within a preset time length, and executing a relay request to continue presenting the target content; or, in response to a relay cancellation instruction input by the user within a preset time, ignoring the relay request to cancel the presentation of the target content, presenting corresponding prompt information, and sending a cancellation message to the push terminal device. And if the relay confirmation instruction or the relay cancellation instruction which is input is not received within the preset time length, the relay request is executed at the termination moment of the preset time length to continue presenting the target content. In this way, the user can stop the display device from presenting the designated content in a predetermined time before the display device presents the designated content in a relay manner in response to receiving the relay request sent by the push terminal device, or instruct the display device to present the execution content immediately, thereby fully improving the flexibility of user operation.
In some embodiments, after the public relay component on the receiving end device receives the relay request of the push end device, if a request for cancelling the relay sent by the push end device is received, the relay request is ignored to cancel the presentation of the target content, and corresponding prompt information is presented. In some embodiments, after the public relay component on the target receiving end device receives the call request sent by the push 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 on the interface showing the countdown progress to expose a visual cue of the countdown progress to the user.
Fig. 14 is a user interface displayed on the destination sink device after the user selects "second floor living room tv" as the destination sink device in fig. 10. As shown in fig. 14, a prompt message indicating that "the bedroom television content is about to be relayed, stop by pressing any key, and immediately relay by pressing the confirmation key" is displayed on the user interface, and a visual prompt "5" of the countdown progress is displayed on one side of the prompt message.
In some embodiments, after receiving a cancellation instruction input by a user, a common relay component on the receiving end device displays a corresponding cancellation notification on an interface of the receiving end device, and synchronizes a relay state to the pushing end device. And after the public relay assembly 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. 15 is a relay scenario diagram according to an exemplary embodiment of the present application. The interface of the receiving end device in fig. 15 is specifically an interface displayed after the receiving end relay assembly receives the cancel instruction input by the user, and as shown in fig. 15, a notification message with a content of "having cancelled relay" is displayed on the interface of the receiving end device. The interface of the push end device in fig. 15 is specifically an interface displayed after the push end power assembly receives the relay state sent by the receiving end device, and as shown in fig. 15, a notification message with content "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 according to the target receiving end information, and calls the target receiving end device based on the target communication protocol channel. The target communication protocol channel may be one or more of a local area network protocol channel, a wide area network protocol channel, and a near field communication protocol channel.
Specifically, if the target receiving end device only supports one protocol channel, the protocol channel is determined as the target protocol channel. For example, for the terminal device C that supports only the bluetooth protocol in the above example, the bluetooth protocol channel is determined as the target communication protocol channel. And for terminal equipment supporting multiple communication protocols, the common relay assembly determines one communication protocol supported by the target receiving terminal equipment according to a preset rule to serve as a target communication protocol channel.
In some embodiments, the rules for determining the target communication protocol channel may be designed based on characteristics of various types of communication protocol channels. As is known, the local area network protocol channel and the wide area network protocol channel have the characteristics of unlimited transmission distance, strong anti-interference capability, fast transmission rate (the larger the bandwidth is, the faster the transmission rate is), and the like; short-distance communication transmission protocols, such as bluetooth protocol and infrared protocol, have short transmission distance, and for infrared protocol, directionality and no obstacle are also required.
Based on this, in some example embodiments, when the receiving end device supports both the local area network protocol channel and the wide area network protocol channel, the local area network protocol channel may be determined as the target communication protocol channel because the local area network response speed per hour is better than that of the wide area network. When the receiving end equipment simultaneously supports a local area network protocol channel, a wide area network protocol channel and a Bluetooth protocol channel, if the known transmission distance is longer, such as more than 10 meters, the local area network protocol channel or the wide area network protocol channel is determined as a target communication protocol channel; and if the known transmission distance is short, such as not exceeding 2 meters, the Bluetooth signal is strong, and the network signal is weak, determining the Bluetooth protocol channel as the target communication protocol channel. When the receiving end equipment supports the Bluetooth protocol channel and the infrared protocol channel at the same time, the Bluetooth protocol channel is preferentially determined as the target communication protocol channel because the infrared protocol is generally transmission with an instructional property, the supported data volume is small, and the anti-interference capability is weak.
In some embodiments, the push-end public relay component acquires a preset priority of each protocol channel; and determining the protocol channel with the highest priority supported by the target receiving end equipment as the 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 devices can be more reasonably utilized, the execution speed of the content relay process between the devices is increased, and the user experience is improved.
In some embodiments, the common relay component on the push end device calls the receiving end device simultaneously according to each communication protocol channel supported by the receiving end device. The receiving end device will successively receive the call requests sent by the pushing end device based on different protocol channels. The receiving terminal equipment processes the call request received for the first time and carries out subsequent interaction with the pushing terminal equipment based on a communication protocol corresponding to the call request received for the first time. When receiving end equipment receives the same call request sent by the same pushing end equipment based on other protocol channels in the follow-up process, the call request can be discarded.
S611, the public relay component on the receiving end device sends the playing information of the target content to the target application.
And S612, the target application on the receiving terminal equipment continues to play the target content according to the playing information of the target content.
S613, the target application on the receiving end device feeds back the playing status information to the public relay component.
And S614, the public relay assembly on the receiving terminal equipment sends the playing state information to the pushing terminal equipment.
In some embodiments, the play status indicates a success or failure of the play. If the target application on the receiving terminal device succeeds in playing the target content, the target application feeds back playing state information indicating that the playing is successful to the receiving terminal relay assembly. If the target application on the receiving terminal equipment fails to continue playing the target content, the target application feeds back playing state information indicating successful playing to the receiving terminal relay assembly.
In some embodiments, the receiving-end relay assembly 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 push end device after receiving the call request sent by the push end device. And the pushing terminal equipment judges that the relay is successful or failed according to whether the response message is received or not. 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 the corresponding prompt information is displayed, if the content is the prompt information of 'relay failure'.
And S615, the public relay assembly on the pushing end equipment receives the playing state information and presents corresponding prompt information according to the playing state information.
In some embodiments, after receiving the play state information sent by the push end device, the common relay component instructs the content application to end playing the target content or instructs the content application to continue playing the target content according to the play state information and the on-off state of the "original device continue playing" button. For example, no matter the playing status information reveals that the receiving end device succeeds or fails in playing the target content, as long as the "original device continues to play" button is turned on, the content application is instructed to continue playing the target content. If the playing state information reveals that the target content playing of the receiving end equipment fails, if the button of 'original equipment continues playing' is turned on, the content application is instructed to continue playing the target content, and if the button of 'original equipment continues playing' is turned off, the content application is instructed to finish playing the target content.
Fig. 16 is a relay scenario diagram according to an exemplary embodiment of the present application. In fig. 16, the receiving-end device interface and the pushing-end device interface are specifically interfaces displayed after the target application continues to play the target content successfully. In fig. 16, a prompt message with "relayed bedroom tv content playing" content is displayed on the interface of the receiving-end device, and a prompt message with "relayed second-floor living room tv playing" content is displayed on the interface of the pushing-end device.
Fig. 17 is a relay scenario diagram 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 displayed after the target application fails to continue playing the target content. In fig. 17, a prompt message with the content "relay failure" is displayed on the interface of the receiving-end device, and a prompt message with the content "relay failure" is displayed on the interface of the pushing-end device.
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 the push end device and the receiving end device executing the relay flow is not limited to the style shown in the above embodiment. Based on the core idea of the technical solution of the present application, those skilled in the art can obtain various embodiments without creative work, and these embodiments all belong to the protection scope of the present application.
In some embodiments, the common relay assembly may operate in two modes, one being an exclusive mode and the other being a non-exclusive mode. When the public relay assembly is in the exclusive mode, the public relay assembly does not perform interaction related to content pushing and content relay processes with a certain receiving end device or terminal devices except the certain pushing end device when interacting with the certain receiving end device or the certain pushing end device. In other words, when the common relay component on the terminal device is in the exclusive mode, the common relay component cannot perform information interaction operations related to the content push and content relay processes with two or more terminal devices at the same time. On the contrary, when the public relay component is in the non-exclusive mode, when the public relay component performs information interaction in the process of content pushing to a certain receiving end device and/or performs information interaction in the process of content relay with a certain pushing end device, the public relay component can also perform interaction related to the content pushing and the content relay process with the receiving end device or a terminal device except the pushing end device.
In some possible implementations, the above-mentioned interaction related to the content push process includes at least the steps performed by the push terminal power component in fig. 6 from S609 to the presentation of the play state. That is, if the push terminal power assembly is in the exclusive mode, it does not interact with the terminal device other than the receiving terminal device during the execution of S609 to the presentation play state.
In some possible implementations, the interaction related to the content relay at least includes S610 to S614 performed by the receiving end relay component in fig. 6. That is, if the receiving-end relay device is in the exclusive mode, it will not interact with the terminal devices other than the push-end device during the execution of S610 to S614.
In some embodiments, the interactions described above in connection with content push and content relay are referred to as relay interactions. Taking the display device as an example, in the process of performing relay interaction with the first terminal device, the display device responds to the received relay request sent by the second terminal device to acquire the 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 a non-exclusive mode, displaying corresponding relay request prompt information according to the relay request sent by the second terminal equipment so that the user triggers to execute relay interaction with the second terminal equipment or to abandon the 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 currently presented content to the first terminal device to continue presenting. Therefore, the relay request sent by the second terminal equipment can be prevented from interrupting the relay interaction process between the display equipment and the first terminal equipment, the display equipment can be ensured to smoothly relay the content pushed by the first terminal equipment, or the content can be smoothly pushed to the first terminal equipment, and therefore the user experience is ensured.
In some embodiments, if the current working mode is not the independent mode, displaying an interruption operation prompt message to enable a user to input an interruption operation according to the interruption operation prompt message, where the interruption operation is used to control the display device to interrupt the relay interaction process with the first terminal device. And in response to the input interrupt operation, interrupting the relay interaction process with the first terminal equipment.
In some embodiments, the user can make settings related to the content relay function on the UI interface provided by the common relay component, including setting an operating mode of the common relay component. For example, the working mode of the common relay component is set to the exclusive mode or the non-exclusive mode by interacting with an interface object on the UI interface provided by the common relay component.
Based on this, in the above embodiment, the obtaining, by the display device, the current working mode may specifically include obtaining an on-off state of an exclusive function of the device; if the exclusive function of the equipment is in an opening state, determining that the current working mode is the exclusive mode; and if the exclusive function of the equipment is in a closed state, determining that the current working mode is a non-exclusive mode.
In other embodiments, the user may turn on or off the device-exclusive function of the common relay component on a UI interface provided by the common relay component. Under the condition that the device exclusive function of the public relay assembly is started, when the public relay assembly starts to execute related content pushing or content relay interaction with a certain terminal device, the public relay assembly automatically enters an exclusive mode, and when the public relay assembly finishes the interaction with the certain terminal device, the public relay assembly automatically exits the exclusive mode and further enters a non-exclusive mode. Under the condition that the device exclusive function of the public relay assembly is closed, the public relay assembly is always in a non-exclusive mode. That is, even if the common relay component starts to perform an interaction related to content push or content relay with a certain terminal device, it does not automatically enter the exclusive mode.
In some embodiments, when a public relay component on a terminal device receives a call request sent by other terminal devices, whether the public relay component is currently in an exclusive mode is judged; if the call request is not currently in the exclusive mode, processing is performed for the call request, for example, executing S610 to S614 shown in fig. 6; if the current mode is exclusive, the call request is not processed, corresponding relay request prompt information is displayed on an interface, and a corresponding notification message 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 corresponding prompt information on the interface thereof according to the exclusive message. The relay request prompt information includes device information of other terminal devices and/or key information of the target content, such as device names of other terminal devices and content names of the target content.
In some possible implementations, in the case that the common relay component is in the exclusive mode, it may determine whether the call request or other information data is the request or information data sent for the current interactive terminal or the request or information data sent for other terminal devices by determining the source of the call request or other information data. And if the request or the information data are transmitted by other terminal equipment, shielding the request or the information data.
It is understood that the terminal device in the exclusive mode may be a push-end device and is performing an interaction related to a content push flow with the receiving-end device, and may also be a receiving-end device and is performing an interaction related to a content relay flow with the push-end device.
It should also be appreciated that the common relay assembly may receive call requests sent by multiple terminal devices simultaneously, i.e., at the same time or with sufficiently short time differences between receipt of the multiple call requests. In some embodiments, in the case where the common relay component on the terminal device is in the non-exclusive mode, if a plurality of call requests transmitted by a plurality of terminal devices are received, processing is performed with respect to the first received call request, for example, performing S610 to S614 shown in fig. 6, without processing the later received call request. And feeding back a corresponding notification message to the terminal equipment which sends the call request while deciding not to process the certain call request. For convenience of explanation, the notification message may be referred to as a busy message. The terminal equipment sending the call request can display corresponding prompt information on the interface thereof according to the busy message.
In some embodiments, in the case that 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 component can process the corresponding call request so as to relay and play the responded content. For the relay information which is not specified by the user, the public relay component can feed back a busy message to the terminal equipment which sends the corresponding call request.
Fig. 18 is a relay scenario diagram according to an exemplary embodiment of the present application. In this example, the a device, while interacting with the B device to push the a content to the B device, the C 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. At this time, the C device presents a C content screen; the device A presents a content picture A and displays a prompt message with the content of 'pushing to the device B to play'; the B device presents a B device interface, and a prompt message with the content of 'the relay A device content is about to be received' is displayed on the B device interface. It should be noted that, since the common relay component on the a device is in the exclusive mode, after receiving the call request of the C device, the a device does not process the call request, but feeds back an exclusive message to the C device. And after the C device receives the exclusive message fed back by the A device, presenting a prompt message with the content of 'the A device is in relay' on the interface.
Fig. 19 is a schematic diagram of another relay scenario illustrated by the present application according to an exemplary embodiment. This example differs from the example shown in fig. 18 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 all send call requests to the a device to respectively request to push the C content, the D content, and the E content to the a device to continue playing on the a device. The example is the same as the example shown in fig. 18, because the common relay component on the a device is in the exclusive mode, 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 device C, the device D and the device E receive the busy message fed back by the device A, presenting a prompt message with the content of 'the device A is in relay' on respective interfaces.
Fig. 20 is a relay scenario diagram 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 sends a call request to the B device, the call request requesting that the C content be pushed to the B device to continue playing on the B device. At this time, the C device presents a C content screen; the device A presents a content picture A and displays a prompt message with the content of 'pushing to the device B to play'; the B device presents a B device interface, and a prompt message with the content of 'the relay A device content is about to be received' is displayed on the B device interface. It is to be noted that, based on the same processing logic as the example shown in fig. 18, 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 the relay state' on the interface.
Fig. 21 is a schematic diagram of another relay scenario illustrated by the present application according to an exemplary embodiment. The difference between this example and the example shown in fig. 18 is 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 all send call requests to the B device to respectively request to push the C content, the D content, and the E content to the B device to continue playing on the B device. Since the common 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, 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 the exclusive message fed back by the B device, presenting a prompt message with the content of 'the B device is in relay' on respective interfaces.
Fig. 22 is a schematic diagram of another relay scenario illustrated by the present application according to an exemplary embodiment. In this example, when the device a interacts with the device B to push the content a to the device B, the device C and the device D both send a call request to the device a to respectively request to push the content C and the content D to the device a to continue playing on the device a, and the device E and the device F both send a call request to the device B to request to push the content E and the content F to the device B to continue playing on the device B. Because the device A and the device B are both in an exclusive mode, the device A feeds back an exclusive message to the device C and the device D respectively after receiving call requests sent by the device C and the device D, and the device C and the device D display a prompt message with the content of 'the device A 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 sends an exclusive message to the E device and the F device respectively, and the E device and the F device display a prompt message with the content of 'the B device is in a relay state' on respective interfaces.
In some embodiments, the operating states of the common relay components are divided into two types, one being a busy state and the other being an idle state. The busy state is complementary to the idle state, i.e., the common relay component is in the idle state if the common relay component is 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 component may be a different operational state, and the corresponding idle state may also be different.
In some embodiments, when a terminal device acts as a push terminal device, and interacts with one or more other terminal devices to push a content to the one or more terminal devices, the common relay component on the terminal device is in a busy state. When a certain terminal device is used as a receiving terminal device, and interacts with another terminal device or a plurality of terminal devices to receive the content pushed by the terminal device or the plurality of terminal devices and relay the playing of the content, the common relay component on the terminal device is in a busy state. In other words, the busy state refers to a state in which a terminal device performs relay interaction with other terminal devices.
In some alternative implementations, the common relay component is in a busy state when the common relay component performs the period from S609 to S615 in fig. 6, and is in an idle state otherwise. More specifically, when the common relay component performs S609 in fig. 6, the common relay component enters a busy state, and when the common relay component performs S615, the common relay component transitions from the busy state to an idle state.
In other alternative implementations, the common relay component is in a busy state when the common relay component performs the period from S607 to S615 in fig. 6, and is in an idle state otherwise. 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 transitions from the busy state to an idle state.
In some embodiments, when a terminal device is in an idle state, in response to receiving a baton request sent by another terminal device or terminal devices, the one or more baton requests are executed, and the current state is updated from the idle state to a busy state.
In some embodiments, when a terminal device is in an idle state, a relay request is sent to one or more terminal devices in response to a user input instruction indicating to push currently presented target content to another or more terminal devices, and the current state is updated from the idle state to a busy state.
For convenience of description, in the following embodiments, terms such as "first", "second", "third", and the like are used to distinguish the terminal devices in the interaction scenario. These terms are not intended to be limiting, and it is to be understood that the terms so used are interchangeable under appropriate circumstances.
In some embodiments, when the common relay component on the first terminal device is in a busy state due to relay interaction with the second terminal device, if a call request sent by a third terminal device is received, a relay information option corresponding to the call request is displayed on an interface so that a user can know the content of the call request. Optionally, the relay information option may show device information of the third terminal device and key information of the specified content, for example, a device name of the third terminal device and a 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 equipment responds to the user operation and executes the call request so as to present the specified content corresponding to the call request. In this way, the user can be prevented from missing the content pushed by the third terminal device.
In some embodiments, when the common relay component on the first terminal device is in a busy state due to relay interaction with the second terminal device, if a call request sent by a third terminal device is received, a relay information option corresponding to the call request is displayed on an interface so that a user can know 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 assembly on the first terminal equipment receives the interrupt operation input by the user, the relay interaction between the first terminal equipment and the second terminal equipment is interrupted, and the call request sent by the third terminal equipment is processed. If the common relay assembly on the first terminal equipment does not receive the interrupt operation input by the user, the relay interaction with the second terminal equipment is continued, and the call request sent by the third terminal equipment is not processed. Fig. 23 is a relay scenario diagram 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 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. Because the common relay component on the device a is in a busy state, after receiving the call request of the device C, the common relay component on the device a performs an interactive procedure with the device B, and displays on the interface of the device a content "is the device C requesting to push the content C, whether to interrupt the current relay? Press enter interrupt ". At this time, the user can input the interrupt operation by pressing the confirmation key. If the public relay assembly on the device A receives the input interrupt operation, the interaction process between the public relay assembly and the device B is interrupted, the call request sent by the device C is processed, and finally the content C is continuously played on the device A. And if the common relay component on the device A does not receive the input interrupt operation, continuing the interactive process with the device B without processing the call request sent by the device C and feeding back a busy message to the device C.
Fig. 24 is a relay scenario diagram 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 sends a call request to the B device, the call request requesting that the C content be pushed to the B device to continue playing on the B device. Since the common relay component on the B device is in a busy state, after the B device receives the call request of the C device, the B device executes an interactive procedure with the a device and displays a content on the B device interface as "does the C device request to push the C content and whether to interrupt the current relay? Press enter interrupt ". At this time, the user can input the interrupt operation by pressing the confirmation key. And if the public relay assembly on the B equipment receives the input interrupt operation, interrupting the interaction process with the A equipment, processing the call request sent by the C equipment, and finally continuing to play the C content on the B equipment. And if the common relay component on the B equipment does not receive the input interrupt operation, continuing the interactive process with the A equipment without processing the call request sent by the C equipment and feeding back a busy message to the C equipment.
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 understood that if a terminal device receives a call request sent by another terminal device while in a busy state, it may prompt the user in various suitable ways, without being limited to the example shown above, which is "C device requests to push C content, whether to interrupt the current relay? Press enter interrupt ". 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-side device information and push content information. For example, in the example shown in fig. 25, when the common relay component 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 component on the first terminal device is in a busy state due to relay interaction with the second terminal device, if call requests sent by a plurality of third terminal devices are received, a relay information option corresponding to each call request is displayed on the interface so that a user can know 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 device responds to an instruction which is input by a user through the appointed at least one target relay information option and indicates to execute at least one target relay request, and executes the at least one target relay request to present appointed content corresponding to each target relay request, so that the situation that the user misses the content pushed by the third terminal device is avoided. And returning a busy message to the terminal equipment which sends the relay request for the relay request corresponding to the relay information option which is not specified or selected by the user.
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 content to be relayed. If the public relay assembly 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 between the public relay assembly and the second terminal equipment is interrupted, and meanwhile, the public relay assembly processes the call request corresponding to the relay information option selected by the user. And if the common relay assembly on the first terminal equipment does not receive the interrupt operation input by the user, continuing the interaction with the second terminal equipment without processing the call request sent by other terminal equipment.
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 assembly 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 applications, so that each target application continues to 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 the designated content corresponding to each target relay request, the plurality of content presentation windows are displayed in a tiled mode, or at least part of the plurality of content presentation windows are displayed in a superposed mode. Wherein the content presentation window may be an application interface of the target application. Fig. 26 is a relay scenario diagram according to an exemplary embodiment of the present application. In this example, when the device a interacts with the device B to push the content a to the device B, the device C, the device D, and the device E all send call requests to the device a to respectively request to push the content C, the content D, and the content E to the device a, so as to continue playing on the device a. Since the common relay component on the device a is in a busy state, after receiving the three call requests, the relay information options corresponding to each call request are presented in the interface, which are "C device-C content", "D device-D content", and "E device-E content", respectively, and "is the content" is the current relay interrupted? Press enter interrupt' prompt message. At this time, the user can interrupt the interaction between the a device and the B device through the confirmation key. And the relay corresponding content of the equipment A can be controlled by selecting a certain relay information option. For example, when the user selects "C device-C content," the common relay component on the a device will process the 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 at the same time, so as to control the a device to relay the content pushed by multiple devices at the same time. For example, when the user selects "C device-C content" or "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 the C content on the a device while continuing playing the D content. Fig. 27A and 27B are schematic diagrams of a user interface of a receiving end device according to an exemplary illustration of the present application, which specifically illustrate a user interface displayed after a user selects "C device-C content", "D device-D content", and "E device-E content" on a device in fig. 26. In fig. 27A, the C content, the D content, and the E content are displayed in different windows, or the C content, the D content, and the E content are displayed in a split screen on the a device interface. In fig. 27B, 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 a plurality of relay information options to control the a device to relay the content pushed by a plurality of devices at the same time, the presentation manner of the plurality of content by the receiving end device is not limited to the embodiment shown in the above example. The present application does not limit the manner in which the receiving end device presents the plurality of contents.
Fig. 28 is a relay scenario diagram according to an exemplary embodiment of the present application. In this example, when the device a interacts with the device B to push the content a to the device B, the device C, the device D, and the device E all send call requests to the device B to respectively request to push the content C, the content D, and the content E to the device B, so as to continue playing on the device B. Since the common relay component on the B device is in a busy state, after receiving the three call requests, the relay information options corresponding to each call request are presented in the interface, which are "C device-C content", "D device-D content", and "E device-E content", respectively, and the content is "whether to interrupt the current relay? Press enter interrupt' prompt message. At this time, the user may interrupt the relay flow between the B device and the a device through the confirmation key. And the B equipment can be controlled to receive the content pushed by the corresponding equipment 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, a relay information option corresponding to each call request is displayed on an interface, so that a user can know the content of each call request. At this point, the user may select one or more relay information options to specify the terminal device to interact with. If the public relay assembly 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. 29 is a relay scenario diagram according to an exemplary embodiment of the present application. This example is different from the example shown in fig. 26 in that the a device receives the call requests sent by the C device, the D device, and the E device when its common relay component is in an idle state. Since the common relay component on the device a is in an idle state, after receiving the three call requests, it only needs to present the relay information option corresponding to each call request in the interface for the user to select, without displaying the content "whether to interrupt the current relay? Press enter interrupt' prompt message.
In some embodiments, the common relay component on the first terminal device may designate one or more other terminal devices to send call requests to the user in response to user actions while in a busy state due to performing the relay procedure with the second terminal device. In an implementation case of sending a call request to a plurality of other terminal devices at the same time, the first terminal device receives 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 an 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, the 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. And when an exclusive message sent by a certain terminal device is received, presenting a prompt message with the content of 'xx device is in a relay state' in a user interface. And when a busy message sent by a certain terminal device is received, presenting a prompt message with the content of 'xx device refusing relay' in the interface.
Fig. 30 is a schematic diagram of a relay scenario shown in the present application according to an exemplary embodiment, specifically, when an a device interacts with a B device to push an a content to the B device, the B device presents the B content, and a device information list composed of optional receiving end device information, interface states of the devices after a call request for requesting to push the B content is sent to a C1 device, a C2 device, and a C3 device, respectively, in response to a user operation. When receiving the call request, the C1 device is in the exclusive state, so that an exclusive message is returned to the B device, and the B device presents a prompt message with the content "the C1 device is in the relay state" on the interface. Since the C2 device is in busy state when receiving the call request, and the user does not end the relay flow between the C2 device and other devices, the C2 device feeds back busy message to the B device, and the B device presents a prompt message with content "C2 device refuses relay" on the interface. The C3 device responds to the call request and launches the content application supporting the call request, the B content is successfully resumed, so the C3 device returns playback status information indicating that the playback was successful to the B device, which then presents a prompt message on the interface that the content is "successfully pushed to the C3 device".
In some embodiments, when the common relay component on the first terminal device is in a busy state due to the execution of the relay procedure with the second terminal device, the common relay component may send a call request to one or more receiving end devices specified by the user in response to a user operation, and may receive the call requests sent by the plurality of pushing end devices.
Fig. 31 is a schematic diagram of a relay scenario shown in the present application according to an exemplary embodiment, specifically, an interface state of each device after the device a interacts with the device B to push the content a to the device B, the device B presents the content B and a device information list composed of optional receiving end device information, and simultaneously receives call requests sent by the device D1, the device D2, and the device D3. The B device displays, in addition to the device information list including "C1 device", "C2 device", and "C3 device", relay information items corresponding to the call requests transmitted from the D1 device, the D2 device, and the D3 device, which are "D1 device-D1 content", "D2 device-D2 content", and "D3 device-D3 content", respectively. At this time, on one hand, 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 sends a call request for pushing the B content to the receiving end device designated by the user, on the other hand, the user 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. 32, since the user selects "C1 device" or "C2 device" in the scenario shown in fig. 31, the common relay component on the B device sends a call request to the C1 device or the C2 device; since the user interrupts the relay flow between the B device and the a device and selects "D1 device-D1 content", the B device relays to play the D1 content.
It should be noted that, the steps executed by the common relay assembly according to the above embodiments may be respectively divided and cooperated by the functional modules inside the common relay assembly.
Illustratively, fig. 33 is an interaction flow diagram illustrated herein in accordance with an exemplary embodiment. As shown in fig. 33, the common relay component includes an interaction hub module, a status management module, an interface display module, a protocol processing module, and a logic control module. After the content application presents the target content, the push end device establishes communication connection with the interactive center module, and sends the relay capacity (namely the target relay capacity) of the push end device to the interactive center module based on the communication connection. The interaction center module sends the target relay capacity to the protocol processing module so as to instruct the protocol processing module to search the external terminal equipment supporting the target relay capacity. And after the protocol processing module obtains the target relay capability, selecting a target communication protocol channel, searching for external terminal equipment supporting the target relay capability through a target communication protocol component corresponding to the target protocol channel based on the target protocol channel, and obtaining an equipment information list. The protocol processing module sends the equipment information list to the interface display module, and simultaneously feeds back an equipment search result to the interactive 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 a user through the interface object, and sends a relay instruction to the interactive center module. And after the interactive center module receives the relay instruction, the interface display module is informed to present the equipment information list. The interface display module receives the selection operation of the target receiving terminal equipment by the user, and the information of the target receiving terminal equipment is sent to the protocol processing module so as to instruct the protocol processing module to call the target receiving terminal equipment. After receiving the information of the target receiving terminal equipment, the protocol processing module indicates the interaction center module to request the playing information of the target content from the content application, and the interaction center module returns the 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 current mode is exclusive or not, and if the current mode is exclusive, the logic control module informs the interface interaction module to present a first prompt message to prompt a user. If the target receiving end equipment is not in the exclusive module, calling the target receiving end equipment based on the target protocol channel. And after the call is finished, receiving the playing state information returned by the target receiving terminal equipment, and sending the playing state information to the state management module. And the state management module instructs the interface display module to present a second prompt message according to the playing state information so as to prompt the user.
Illustratively, fig. 34 is an interaction flow diagram illustrating a method according to an exemplary embodiment of the present application. As shown in fig. 34, the common relay component includes an interaction hub module, a status management module, an interface display module, a protocol processing module, and a logic control module. On the receiving end device, the target communication protocol assembly receives the call request sent by the pushing end device and sends the call request to the logic control module. And the logic control module judges whether the current state is in an exclusive mode, if so, an exclusive message is returned to the push terminal equipment through the target protocol component, and if not, the logic control module continues to judge whether the current state is in an idle state. And if the current state is in an idle state, determining a target application indicating the target relay capacity, and indicating the interactive center module to start the target application. And 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 the playing state information to the interactive center module. And the interactive center module sends the playing state information to the state management module. The state management module indicates the logic control module to return the playing state information to the pushing end device, and simultaneously indicates the interface display module to present a prompt message according to the playing state information. And if the current state is busy, indicating the interface display module to display corresponding relay information according to the call request and display an interruption operation reminding message. The interface display module displays corresponding relay information and an interruption operation reminding message according to the call request, instructs the logic control module to interrupt the current relay after receiving input interruption operation, and instructs the logic control module to process the corresponding call request when receiving the selection operation of the input connection force information.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present 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 (9)

1. A display device, comprising:
a display for presenting content;
a speaker for presenting the content in conjunction with the display;
a communicator configured to communicate with an external terminal device through a local area network protocol channel, a wide area network protocol channel, and other protocol channels;
a controller configured to:
when presenting the target content, searching for an external terminal device supporting target relay capability through one or more of the local area network protocol channel, the wide area network protocol channel and other protocol channels, wherein the target relay capability refers to the capability required for presenting the target content;
presenting the searched device information of the external terminal device for the user to specify a target receiving terminal device from the external terminal device supporting the target relay capability;
responding to an instruction input by a user and indicating to push the target content to target receiving end equipment, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment, wherein the target protocol channel is one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels;
and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content.
2. The display device of claim 1, wherein the communicator comprises a local area network protocol component for communicating with an external terminal device over a local area network protocol channel, the controller further configured to:
responding to the starting of the display equipment, and acquiring the relay capability parameter of each application;
registering the relay capacity parameters of each application in the local area network protocol assembly so that the local area network protocol assembly returns a response message to the external terminal equipment according to the relay capacity parameters of each application when receiving a capacity inquiry message of the external terminal equipment;
and/or sending the relay capability parameters of each application and the identification information of the display device to a server, so that the server queries the terminal device which is associated with the terminal device and supports the designated relay capability according to the pre-stored identification information of the device and the corresponding relay capability parameters when receiving a device query request sent by the terminal device.
3. The display device of claim 1, wherein the controller performs a search for external terminal devices supporting a target relay capability over the local area network protocol channel, further configured to:
sending a capability inquiry message to terminal equipment in the same local area network as the display equipment through the local area network protocol channel;
receiving a response message to the capability inquiry message, which is sent by the terminal equipment;
and determining whether the terminal equipment supports the target relay capability or not according to the response message.
4. The display device of claim 1, wherein the controller performs a search for external terminal devices supporting a target relay capability over the wide area network protocol tunnel, further configured to:
sending an equipment query request to a server through the local area network protocol channel, wherein the equipment query request comprises a push terminal identifier corresponding to the display equipment and the target relay capacity;
and receiving a device information set returned by the server in response to the device query request, wherein the device information set comprises device information of terminal devices which are queried by the server, are associated with the push terminal identification and support the target relay capability.
5. The display device of claim 1, wherein the controller performs determining a target protocol channel according to a protocol channel supported by the target sink device, and is further configured to:
if the target receiving end equipment supports a protocol channel, determining the protocol channel supported by the target receiving end equipment as a target protocol channel for communicating with the target receiving end equipment;
and if the target receiving end equipment supports multiple protocol channels, determining a target protocol channel for communicating with the target receiving end equipment according to a preset rule.
6. The display device according to claim 5, wherein the other protocol channels include a bluetooth protocol channel and an infrared protocol channel, and the controller executes the determining of the target protocol channel for communicating with the target receiving end device according to the preset rule, and is further configured to:
if the target receiving end equipment supports a local area network protocol channel and a wide area network protocol channel at the same time, determining the local area network protocol channel as a target protocol channel;
if the target receiving end equipment simultaneously supports a local area network protocol channel, a wide area network protocol channel and a Bluetooth protocol channel and the transmission distance exceeds a preset value, determining the local area network protocol channel or the wide area network protocol channel as a target protocol channel;
and if the target receiving end equipment supports the Bluetooth protocol channel and the infrared protocol channel at the same time, determining the Bluetooth protocol channel as a target protocol channel.
7. The display device according to claim 5, wherein the controller executes the determining of the target protocol channel for communication with the target sink device according to a preset rule, and is further configured to:
acquiring a preset priority of each protocol channel;
and determining the protocol channel with the highest priority supported by the target receiving end equipment as the target protocol channel.
8. The display device according to claim 1, wherein the device information includes a unique identifier, wherein the controller performs presenting the searched device information of the external terminal device, and is further configured to:
according to the unique identification, integrating the equipment information of the same terminal equipment searched by different protocol channels;
presenting the integrated device information.
9. A method for pushing content, the method comprising:
when presenting the target content, searching for an external terminal device supporting target relay capability through one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels, wherein the target relay capability refers to the capability required for presenting the target content;
presenting the searched device information of the external terminal device for the user to specify a target receiving terminal device from the external terminal device supporting the target relay capability;
responding to an instruction input by a user and indicating to push the target content to target receiving end equipment, and determining a target protocol channel according to a protocol channel supported by the target receiving end equipment, wherein the target protocol channel is one or more of a local area network protocol channel, a wide area network protocol channel and other protocol channels;
and sending a relay request to the target receiving terminal equipment based on the target protocol channel so as to request the target receiving terminal equipment to continuously present the target content.
CN202111130805.4A 2021-09-18 2021-09-26 Display device and content push method Pending CN113794918A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111097923X 2021-09-18
CN202111097923 2021-09-18

Publications (1)

Publication Number Publication Date
CN113794918A true CN113794918A (en) 2021-12-14

Family

ID=78797483

Family Applications (7)

Application Number Title Priority Date Filing Date
CN202111139380.3A Pending CN113891129A (en) 2021-09-18 2021-09-26 Display device, content pushing and relay method
CN202111139401.1A Pending CN113891130A (en) 2021-09-18 2021-09-26 Display device and request processing method
CN202111131349.5A Active CN113766036B (en) 2021-09-18 2021-09-26 Display equipment and information interaction method
CN202111130805.4A Pending CN113794918A (en) 2021-09-18 2021-09-26 Display device and content push method
CN202111128526.4A Active CN113766301B (en) 2021-09-18 2021-09-26 Display device and interaction control method
CN202111151401.3A Active CN113766292B (en) 2021-09-18 2021-09-29 Display device
CN202310537857.6A Pending CN116634211A (en) 2021-09-18 2021-09-29 Display device and content connection method

Family Applications Before (3)

Application Number Title Priority Date Filing Date
CN202111139380.3A Pending CN113891129A (en) 2021-09-18 2021-09-26 Display device, content pushing and relay method
CN202111139401.1A Pending CN113891130A (en) 2021-09-18 2021-09-26 Display device and request processing method
CN202111131349.5A Active CN113766036B (en) 2021-09-18 2021-09-26 Display equipment and information interaction method

Family Applications After (3)

Application Number Title Priority Date Filing Date
CN202111128526.4A Active CN113766301B (en) 2021-09-18 2021-09-26 Display device and interaction control method
CN202111151401.3A Active CN113766292B (en) 2021-09-18 2021-09-29 Display device
CN202310537857.6A Pending CN116634211A (en) 2021-09-18 2021-09-29 Display device and content connection method

Country Status (2)

Country Link
CN (7) CN113891129A (en)
WO (1) WO2023040419A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115022688A (en) * 2022-05-26 2022-09-06 海信视像科技股份有限公司 Display device and media data relay method
WO2023216684A1 (en) * 2022-05-09 2023-11-16 海信视像科技股份有限公司 Terminal device and data relay method

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113891129A (en) * 2021-09-18 2022-01-04 海信视像科技股份有限公司 Display device, content pushing and relay method
CN114553952B (en) * 2022-02-22 2024-05-03 Oppo广东移动通信有限公司 Device management method and device, electronic device and storage medium
CN114710694B (en) * 2022-04-12 2023-05-30 深圳市瑞云科技有限公司 Distributed plug flow method in cloud game scene
CN114900386B (en) * 2022-05-09 2023-10-31 海信视像科技股份有限公司 Terminal equipment and data relay method
WO2023220853A1 (en) * 2022-05-16 2023-11-23 Oppo广东移动通信有限公司 Service operation method and apparatus, and chip, storage medium and computer program
CN114979169B (en) * 2022-05-27 2024-03-29 山东派盟网络科技有限公司 Network resource pushing method and device, storage medium and electronic equipment
CN115297352B (en) * 2022-06-27 2024-03-22 青岛海尔科技有限公司 Video continuous playing method and device, storage medium and electronic device
CN115223521B (en) * 2022-07-12 2024-04-30 海信视像科技股份有限公司 Display equipment and relay equipment display method
CN117834568A (en) * 2022-09-27 2024-04-05 比亚迪股份有限公司 Data relay method, device, system, storage medium, equipment and vehicle

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103856993A (en) * 2012-12-06 2014-06-11 腾讯科技(深圳)有限公司 Method and device for wireless communication
CN105872953A (en) * 2016-03-29 2016-08-17 乐视控股(北京)有限公司 Communication method between user devices and user devices
CN110958475A (en) * 2019-10-30 2020-04-03 华为终端有限公司 Cross-device content projection method and electronic device
CN112258086A (en) * 2020-11-13 2021-01-22 Oppo广东移动通信有限公司 Cross-device task relay method and device, cloud platform and storage medium

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974137A (en) * 2014-05-15 2014-08-06 北京奇艺世纪科技有限公司 Cross-equipment video resource pushing method and device
CN104270668B (en) * 2014-09-26 2018-03-20 广州创维平面显示科技有限公司 A kind of video content continuous playing method and system
JP2017069932A (en) * 2015-10-02 2017-04-06 株式会社リコー Transmission management system, relay device selection method, and program
CN105898544A (en) * 2016-05-23 2016-08-24 乐视控股(北京)有限公司 Video playing method and device
CN109525862A (en) * 2018-11-07 2019-03-26 苏宁体育文化传媒(北京)有限公司 A kind of multiple terminals live streaming exchange method and system
CN109725863B (en) * 2018-11-14 2022-04-19 北京风行在线技术有限公司 Method, device, equipment and system for screen projection
CN111726661B (en) * 2019-03-21 2021-10-08 海信视像科技股份有限公司 Program push playing method, display equipment, mobile terminal and system
CN110248224A (en) * 2019-05-24 2019-09-17 南京苏宁软件技术有限公司 Throw screen connection method for building up, device, computer equipment and storage medium
CN112153442A (en) * 2019-06-28 2020-12-29 Oppo广东移动通信有限公司 Playing method, device, terminal, television equipment, storage medium and electronic equipment
CN110381345B (en) * 2019-07-05 2020-12-15 华为技术有限公司 Screen projection display method and electronic equipment
CN112714214B (en) * 2019-10-24 2022-05-10 华为终端有限公司 Content connection method, equipment, system, GUI and computer readable storage medium
CN113037929B (en) * 2019-12-24 2022-04-15 腾讯科技(深圳)有限公司 Information relay output method and device, electronic equipment and storage medium
CN113784220B (en) * 2020-02-17 2023-08-08 聚好看科技股份有限公司 Method for playing media resources, display device and mobile device
CN113311975A (en) * 2020-02-27 2021-08-27 华为技术有限公司 Application interaction method among multiple devices and related devices
CN113438354B (en) * 2020-03-06 2022-09-02 华为技术有限公司 Data transmission method and device, electronic equipment and storage medium
CN115278377A (en) * 2020-03-26 2022-11-01 华为技术有限公司 Method for continuously playing multimedia content between devices
CN111526416A (en) * 2020-04-17 2020-08-11 腾讯科技(深圳)有限公司 Video playing method, device, equipment and storage medium
CN111464844A (en) * 2020-04-22 2020-07-28 海信视像科技股份有限公司 Screen projection display method and display equipment
CN111741372B (en) * 2020-07-08 2022-02-25 聚好看科技股份有限公司 Screen projection method for video call, display device and terminal device
CN111897507B (en) * 2020-07-30 2023-03-24 茂佳科技(广东)有限公司 Screen projection method and device, second terminal and storage medium
CN112114761A (en) * 2020-08-14 2020-12-22 深圳市飞图视讯有限公司 Wireless screen projection control method and device, terminal equipment and readable storage medium
CN113207018A (en) * 2021-04-23 2021-08-03 西安万像电子科技有限公司 Remote screen projection method, system, equipment and storage medium
CN112988102B (en) * 2021-05-11 2021-09-14 荣耀终端有限公司 Screen projection method and device
CN113891129A (en) * 2021-09-18 2022-01-04 海信视像科技股份有限公司 Display device, content pushing and relay method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103856993A (en) * 2012-12-06 2014-06-11 腾讯科技(深圳)有限公司 Method and device for wireless communication
CN105872953A (en) * 2016-03-29 2016-08-17 乐视控股(北京)有限公司 Communication method between user devices and user devices
CN110958475A (en) * 2019-10-30 2020-04-03 华为终端有限公司 Cross-device content projection method and electronic device
CN112258086A (en) * 2020-11-13 2021-01-22 Oppo广东移动通信有限公司 Cross-device task relay method and device, cloud platform and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023216684A1 (en) * 2022-05-09 2023-11-16 海信视像科技股份有限公司 Terminal device and data relay method
CN115022688A (en) * 2022-05-26 2022-09-06 海信视像科技股份有限公司 Display device and media data relay method

Also Published As

Publication number Publication date
CN113766036A (en) 2021-12-07
CN113766301A (en) 2021-12-07
CN113766301B (en) 2023-11-28
CN113766292B (en) 2023-03-31
CN113891130A (en) 2022-01-04
WO2023040419A1 (en) 2023-03-23
CN116634211A (en) 2023-08-22
CN113766036B (en) 2024-04-09
CN113891129A (en) 2022-01-04
CN113766292A (en) 2021-12-07

Similar Documents

Publication Publication Date Title
CN113766292B (en) Display device
CN111277884B (en) Video playing method and device
CN112911380B (en) Display device and connection method with Bluetooth device
WO2020248627A1 (en) Video call method and display device
CN113590059A (en) Screen projection method and mobile terminal
CN113489700A (en) Method, server and terminal equipment for acquiring media asset data
CN112632160A (en) Intelligent device and intelligent device login method
CN115454367A (en) Display device and display device control method
CN113784186B (en) Terminal device, server, and communication control method
CN114928760B (en) Key setting method of control device and display equipment
CN115022688A (en) Display device and media data relay method
CN114968031A (en) Task management method and display device
CN111953838B (en) Call dialing method, display device and mobile terminal
CN114900386A (en) Terminal equipment and data relay method
CN116614659A (en) Screen projection method, display device and intelligent device
CN116795466A (en) Display device and method for displaying content of external device
CN115705222A (en) Terminal device and content reverse relay method
CN118120242A (en) Display device and content connection method
CN113473230B (en) Method for realizing channel switching by using third-party application and display equipment
CN115514998B (en) Display equipment and network media resource switching method
CN115705220A (en) Content service relay method of terminal equipment and terminal equipment
CN117707363A (en) Display device and application window display method
CN114860370A (en) Display device, server and software development kit switching method
CN115904290A (en) Display device, communication terminal and screen projection control method
CN116320564A (en) Display device, terminal device, and device control method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination