WO2017101409A1 - 不同客户端间的视频推送方法、系统及服务器 - Google Patents

不同客户端间的视频推送方法、系统及服务器 Download PDF

Info

Publication number
WO2017101409A1
WO2017101409A1 PCT/CN2016/089528 CN2016089528W WO2017101409A1 WO 2017101409 A1 WO2017101409 A1 WO 2017101409A1 CN 2016089528 W CN2016089528 W CN 2016089528W WO 2017101409 A1 WO2017101409 A1 WO 2017101409A1
Authority
WO
WIPO (PCT)
Prior art keywords
video
client
destination
pushed
identifier
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.)
Ceased
Application number
PCT/CN2016/089528
Other languages
English (en)
French (fr)
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.)
Le Holdings Beijing Co Ltd
LeTV Information Technology Beijing Co Ltd
Original Assignee
Le Holdings Beijing Co Ltd
LeTV Information Technology Beijing 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 Le Holdings Beijing Co Ltd, LeTV Information Technology Beijing Co Ltd filed Critical Le Holdings Beijing Co Ltd
Priority to US15/242,148 priority Critical patent/US20170171331A1/en
Publication of WO2017101409A1 publication Critical patent/WO2017101409A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
    • H04N21/2747—Remote storage of video programmes received via the downstream path, e.g. from the server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47214—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for content reservation or setting reminders; for requesting event notification, e.g. of sport results or stock market

Definitions

  • the present patent application relates to the field of video push, and in particular, to a video push method, system and server between different clients.
  • Push that is, the push mode is based on data transmission between users. According to this push method, once the push user is not connected to other users through the network, sharing information with other users or other clients cannot be realized.
  • the purpose of some embodiments of the present invention is to provide a video push method and a server between different clients.
  • the method does not depend on a network connection with a client, thereby improving the flexibility of video push and enhancing the user experience.
  • some embodiments of the present invention provide a video push method between different clients, where the video push method includes: receiving an identifier of a video to be pushed and a destination client to be pushed to and/or a push to be pushed. a destination account, wherein a source client providing the identification of the video is bound to the destination client, and/or a source account corresponding to the source client is bound to the destination account; The identifier of the video is pushed to the client corresponding to the destination client and/or the destination account.
  • the video push method further includes: receiving a request for the identity of the video from the destination client and/or a client corresponding to the destination account; and responding to the request, The video corresponding to the identifier of the video is sent to the client corresponding to the destination client and/or the destination account.
  • the video push method further includes: storing an identifier of the video to be pushed and a destination client to which the destination client and/or the destination account to be pushed are to be pushed.
  • the video push method further includes: pushing the identifier of the video to the destination client and/or the destination account when the destination client and/or the destination account is online Corresponding client.
  • the identification of the video includes a link to the video to be pushed.
  • some embodiments of the present invention further provide a server, where the server includes: a receiving module, receiving an identifier of a video to be pushed, and a destination client to be pushed to and/or a destination account to be pushed to, a source client that provides an identification of the video is bound to the destination client, and/or a source account corresponding to the source client is bound to the destination account; and a push module that identifies the video Push to the client corresponding to the destination client and/or destination account.
  • the receiving module is further configured to receive a request for the identifier of the video from the destination client and/or a client corresponding to the destination account; and in response to the request, the pushing Sending the video corresponding to the identifier of the video to the client corresponding to the destination client and/or the destination account.
  • the server further includes a storage module for storing the identity of the video to be pushed and the client to which the destination client is to be pushed and/or the destination account to which the user account is to be pushed.
  • the push module pushes the identifier of the video to the destination client and/or the client corresponding to the destination account.
  • the identification of the video includes a link to the video to be pushed.
  • some embodiments of the present invention further provide a video push system between different clients, where the video push system includes: a source client, a destination client, and the server; the source client is configured to Sending, by the server, an identifier of the video to be pushed and the destination client to which the destination client and/or the destination client to be pushed are to be pushed; the destination client is configured to receive the The identity of the video.
  • the video push system includes: a source client, a destination client, and the server; the source client is configured to Sending, by the server, an identifier of the video to be pushed and the destination client to which the destination client and/or the destination client to be pushed are to be pushed; the destination client is configured to receive the The identity of the video.
  • the destination client is further configured to send a request for the identifier of the video to the server; the destination client receives an identifier corresponding to the video that is sent by the server in response to the request The video.
  • the identifier of the received video and the destination client and/or the destination account are pushed, and the flag of the video is pushed to the client corresponding to the destination client and/or the destination account number, where the source client of the identifier of the video is provided.
  • a source account bound to the destination client and/or corresponding to the source client is bound to the destination account.
  • FIG. 1 is a flow chart of a video push method between different clients according to the present invention
  • FIG. 2 is a flowchart of a video push method between different clients according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of a video push system between different clients provided in accordance with the present invention.
  • FIG. 4 is a block diagram showing the structure of a server provided in accordance with the present invention.
  • the video push method between different clients may include: at step 11, receiving a push to be pushed The identification of the video and the client to which the destination client is to be pushed and/or the destination account to which the video is to be pushed, wherein the source client providing the identity of the video is bound to the destination client, and/or The source account corresponding to the source client is bound to the destination account; and at step 12, the identifier of the video is pushed to the client corresponding to the destination client and/or the destination account.
  • This enables video push without relying on the network connection with the client. Send, thus increasing the flexibility of video push and enhancing the user experience.
  • the daughter of the daughter can be bound to the client of the parent, for example, the two are bound to the same account (for example, a family account), of course, the account can also be bound to other clients, for example, a client, b client, etc., and all clients bound in the home account can be listed in the home account, and whenever a new client is bound to the home account, It can be listed in the home account and all clients bound can be displayed on the client logged into the home account.
  • the server When logging in to the home account through the client of the daughter, it is found that there are videos (such as historical videos) that the parents may be interested in, so that the historical video can be selected by the client of the daughter and the client of the parent is selected as the destination client of the push. And sending the identification of the historical video and the parent client to which the server is to be sent to the server, the server receiving the identifier of the historical video and the client as the parent of the destination client; that is, as described in FIG. 2, in the step At 21, the server receives the identification of the video to be pushed and the client to which the destination client is to be pushed and/or the destination account to which the advertisement is to be pushed.
  • videos such as historical videos
  • the server may store the identity of the video to be pushed and the destination client to which to push and/or the destination account to which to push, in this embodiment, the identity of the historical video and the client of the parent are stored. end.
  • the parent's client wishes to receive the historical video (for example, the parent's client's user clicks the confirmation button for receiving the historical video), it may send the server to the server.
  • Request for identification of the historical video (request to obtain the historical video), ie at Step 25:
  • the server receives a request for the identifier of the video from the destination client or a client corresponding to the destination account.
  • the server sends the video corresponding to the identifier of the video to the client corresponding to the destination client and/or the destination account, ie, in response to the identifier for the historical video.
  • Request to send the historical video to the parent's client This completes the push of the entire video, and in addition, if the server does not receive the request, the historical video will not be sent to the parent client.
  • the identifier of the video may include a link of the video to be pushed.
  • the identifier of the video may further include at least one of the following: a size of the video, a content introduction, or a viewing progress.
  • some embodiments of the present invention further provide a video push system between different clients.
  • the video push system provided by some embodiments of the present invention will be described in detail below with reference to FIG. 3 and FIG.
  • FIG. 3 is a structural block diagram of a video push system between different clients according to some embodiments of the present invention.
  • the video push system provided in this embodiment may include: a source client 10, a destination client 20, and a server 30; the source client 10 is configured to send the identifier of the video to be pushed to the server 30. And the destination client 20 to be pushed to and the destination account corresponding to the destination client 20 to be pushed to; the destination client 20 is configured to receive the identifier of the video pushed by the server 30.
  • video push can be implemented without relying on the network connection with the client, thereby improving the flexibility of video push and enhancing the user experience.
  • the destination client 20 is further configured to send a request for the identifier of the video to the server 30; the destination client 20 receives an identifier corresponding to the video that the server 30 sends in response to the request.
  • the video is further configured to send a request for the identifier of the video to the server 30; the destination client 20 receives an identifier corresponding to the video that the server 30 sends in response to the request. The video.
  • the server 30 provided in this embodiment may include: a receiving module 31, which receives the identifier of the video to be pushed and the destination client to be pushed to and/or the client corresponding to the destination account to be pushed to. End, wherein the source client providing the identifier of the video is bound to the destination client, and/or the source account corresponding to the source client is bound to the destination account; and the push module 32 The identifier of the video is pushed to the client corresponding to the destination client and/or the destination account.
  • the receiving module is further configured to receive a request for the identifier of the video from the destination client and/or the client corresponding to the destination account, in consideration of the intention of the user of the destination client and the destination account; In response to the request, the push sends the video corresponding to the identifier of the video to a client corresponding to the destination client and/or the destination account.
  • the server provided in this embodiment may further include a storage module for storing the identifier of the video to be pushed and the destination client to be pushed to and/or the destination account to be pushed to.
  • the push module pushes the identifier of the video to the destination client and/or the client corresponding to the destination account, for example, the stored video.
  • the identifier is pushed to the client corresponding to the stored destination client and/or destination account.
  • the identifier of the video may include a link of the video to be pushed.
  • the identifier of the video may further include a size, a content introduction, or a viewing progress of the video of at least one of the following.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本专利申请涉及视频推送领域，公开了一种不同客户端间的视频推送方法及服务器，所述视频推送方法包括：接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端，其中提供所述视频的标识的源客户端与所述目的客户端绑定和/或与所述源客户端对应的源账户与所述目的账户绑定；以及将所述视频的标识推送至所述目的客户端和/或目的账户。采用本发明实施例，能够不依赖与客户端之间的网络连接而进行视频推送，因而提高视频推送的灵活性，增强了用户的体验感。

Description

不同客户端间的视频推送方法、系统及服务器
本申请要求于2015年12月14日提交中国专利局、申请号为201510922943.4的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本专利申请涉及视频推送领域，具体地，涉及一种不同客户端间的视频推送方法、系统及服务器。
背景技术
随着电子产品的大力发展，用户间或用户不同客户端间的进行视频推送的需求也日益增强。目前，用户基本是通过网络直接向其他用户和/或其它客户端发送所要推荐的视频。例如，用户想要向另一用户推荐一视频时，需要将该视频通过连接在二者之间的网络发送至所述另一用户。
在现有技术中，用户想要推荐某一视频时，必须在其与其它用户之间建立网络连接，也就是说，用户需要通过建立在用户之间网络来与其他用户或其它客户端进行视频推送，即该推送方式是建立在用户之间的数据传输的基础上的。按照这种推送方式，一旦推送用户并未通过网络与其它用户连接，则无法实现与其他用户或其它客户端共享信息。
发明内容
本发明部分实施例的目的是提供一种不同客户端间的视频推送方法及服务器，该方法不依赖与客户端之间的网络连接，因而提高视频推送的灵活性，增强了用户的体验感。
为了实现上述目的，本发明部分实施例提供了一种不同客户端间的视频推送方法，所述视频推送方法包括：接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。
在一个实施例中，所述视频推送方法还包括：从所述目的客户端和/或所述目的账户对应的客户端接收针对所述视频的标识的请求；以及响应于所述请求，将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端。
在一个实施例中，所述视频推送方法还包括：存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端。
在一个实施例中，所述视频推送方法还包括：在所述目的客户端和/或所述目的账户在线时，将所述视频的标识推送至所述目的客户端和/或所述目的账户对应的客户端。
在一个实施例中，所述视频的标识包括所要推送的视频的链接。
相应地，本发明部分实施例还提供了一种服务器，所述服务器包括：接收模块，接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及推送模块，将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。
在一个实施例中，所述接收模块还用于从所述目的客户端和/或所述目的账户对应的客户端接收针对所述视频的标识的请求；以及响应于所述请求，所述推送将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端。
在一个实施例中，所述服务器还包括存储模块，用于存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端。
在一个实施例中，在所述目的客户端和/或所述目的账户在线时，所述推送模块将所述视频的标识推送至所述目的客户端和/或所述目的账对应的客户端。
在一个实施例中，所述视频的标识包括所要推送的视频的链接。
对应地，本发明部分实施例还提供了一种不同客户端间的视频推送系统，所述视频推送系统包括：源客户端、目的客户端及上述服务器；所述源客户端用于向所述服务器发送所要推送的视频的标识及所要推送至的所述目的客户端和/或所要推送至的所述目的客户端对应的目的账户；所述目的客户端用于接收所述服务器推送的所述视频的标识。
在一个实施例中，所述目的客户端还用于向所述服务器发送针对所述视频的标识的请求；所述目的客户端接收所述服务器响应于所述请求发送的所述视频的标识对应的所述视频。
通过上述技术方案，接收视频的标识及目的客户端和/或目的账户，将所述视频的标志推送至目的客户端和/或目的账户号对应的客户端，其中提供视频的标识的源客户端与所述目的客户端绑定和/或与所述源客户端对应的源账户与所述目的账户绑定。如此能够不依赖与客户端之间的网络连接而进行视频推送，因而提高视频推送的灵活性，增强了用户的体验感。
本发明部分实施例的其它特征和优点将在随后的具体实施方式部分予以详细说明。
附图说明
附图是用来提供对本发明部分实施例的进一步理解，并且构成说明书的 一部分，与下面的具体实施方式一起用于解释本发明部分实施例，但并不构成对本发明的限制。在附图中：
图1是根据本发明提供的不同客户端间的视频推送方法的流程图；
图2是根据本发明一种实施方式的不同客户端间的视频推送方法的流程图；
图3是根据本发明提供的不同客户端间的视频推送系统的结构框图；以及
图4是根据本发明提供的服务器的结构框图。
附图标记说明
10  源客户端  20目的客户端
30  服务器
31  接收模块  32推送模块
具体实施方式
以下结合附图对本发明的具体实施方式进行详细说明。应当理解的是，此处所描述的具体实施方式仅用于说明和解释本发明，并不用于限制本发明。
图1是根据本发明提供的不同客户端间的视频推送方法的流程图，如图1所示，本实施例提供的不同客户端间的视频推送方法可以包括：在步骤11处，接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及在步骤12处，将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。如此能够实现不依赖与客户端之间的网络连接而进行视频推 送，因而提高视频推送的灵活性，增强了用户的体验感。
以下将参照图2通过具体实施方式来详细描述本发明部分实施例所提供的不同客户端间的视频推送方法。应该理解的是，该实施方式仅是示例性的，并不用于限制本发明。
在该实施方式中，可以将女儿的客户端和父母的客户端进行绑定，例如将二者绑定至同一个账户(例如家庭账户)，当然该账户还可以绑定了其它客户端，例如a客户端、b客户端等等，并且可以在所述家庭账户中列出绑定在该家庭账户中的所有客户端，而且每当有新的客户端绑定至该家庭账户中时，还可以将其列出在该家庭账户中，并且可以在登录该家庭账户的客户端上显示绑定的所有客户端。
在通过女儿的客户端来登录家庭账户时，发现有父母可能感兴趣的视频(例如历史视频)，因而可以通过女儿的客户端来选择该历史视频并选中父母的客户端作为推送的目的客户端，以及将该历史视频的标识及所要推送至的父母客户端发送至服务器，服务器接收所述历史视频的标识及作为目的客户端的父母的客户端；也就是说，如图2所述，在步骤21处，服务器接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端。在步骤22处，服务器可以存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户，在该实施方式中，即存储所述历史视频的标识及父母的客户端。在步骤23处，判断目的客户端和/或目的账户是否在线，即判断父母的客户端是否在线。如果在线，则在步骤24处，服务器将所述视频的标识推送至所述目的客户端和/或所述目的账户对应的客户端，即将所述历史视频的标识推送至父母客户端。此时历史视频的标识会在父母的客户端上显示，如果父母的客户端希望接收该历史视频(例如父母的客户端的用户点击接收历史视频的确认键)，则其可以向服务器发送针对所述历史视频的标识的请求(请求获取所述历史视频)，即在 步骤25处，服务器从所述目的客户端或所述目的账户对应的客户端接收针对所述视频的标识的请求。在步骤26处，响应于所述请求，服务器将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端，即响应于针对所述历史视频的标识的请求，向父母的客户端发送所述历史视频。如此完成整个视频的推送，另外，如果服务器未接收到所述请求，则不会将历史视频发送至父母客户端。
其中，所述视频的标识可以包括所要推送的视频的链接。
在本实施例中，所述视频的标识还可以包括以下至少一者：所述视频的大小、内容简介或观看进度。
相应地，本发明部分实施例还提供一种不同客户端间的视频推送系统，以下将参考图3和图4来详细描述本发明部分实施例所提供的视频推送系统。
图3给出了本发明部分实施例提供的不同客户端间的视频推送系统的结构框图。如图3所示，本实施例提供的视频推送系统可以包括：源客户端10、目的客户端20及服务器30；所述源客户端10用于向所述服务器30发送所要推送的视频的标识及所要推送至的所述目的客户端20和/或所要推送至的所述目的客户端20对应的目的账户；所述目的客户端20用于接收所述服务器30推送的所述视频的标识。如此能够实现不依赖与客户端之间的网络连接而进行视频推送，因而提高视频推送的灵活性，增强了用户的体验感。
另外，所述目的客户端20还用于向所述服务器30发送针对所述视频的标识的请求；所述目的客户端20接收所述服务器30响应于所述请求发送的所述视频的标识对应的所述视频。
图3是根据本发明部分实施例提供的服务器的结构框图。如图3所示，本实施例所提供的服务器30可以包括：接收模块31，接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户 端，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及推送模块32，将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。
其中，考虑到目的客户端和目的账户的用户的意愿，所述接收模块还用于从所述目的客户端和/或所述目的账户对应的客户端接收针对所述视频的标识的请求；以及响应于所述请求，所述推送将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端。
另外，本实施例提供的服务器还可以包括存储模块，用于存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户。
在所述目的客户端或所述目的账户在线时，所述推送模块将所述视频的标识推送至所述目的客户端和/或所述目的账户对应的客户端，例如将所存储的视频的标识推送至所存储的目的客户端和/或目的账户对应的客户端。
其中，所述视频的标识可以包括所要推送的视频的链接。
在本实施例中，所述视频的标识还可以包括以下至少一者所述视频的大小、内容简介或观看进度。
以上结合附图详细描述了本发明的优选实施方式，但是，本发明并不限于上述实施方式中的具体细节，在本发明的技术构思范围内，可以对本发明的技术方案进行多种简单变型，这些简单变型均属于本发明的保护范围。
另外需要说明的是，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本发明对各种可能的组合方式不再另行说明。
此外，本发明的各种不同的实施方式之间也可以进行任意组合，只要其不违背本发明的思想，其同样应当视为本发明所公开的内容。

Claims (12)

  1. 一种不同客户端间的视频推送方法，所述视频推送方法包括：
    接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及
    将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。
  2. 根据权利要求1所述的视频推送方法，其中，所述视频推送方法还包括：
    从所述目的客户端和/或所述目的账户对应的客户端接收针对所述视频的标识的请求；以及
    响应于所述请求，将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端。
  3. 根据权利要求1或2所述的视频推送方法，其中，所述视频推送方法还包括：存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端。
  4. 根据权利要求1，2或3所述的视频推送方法，其中，所述视频推送方法还包括：在所述目的客户端和/或所述目的账户在线时，将所述视频的标识推送至所述目的客户端和/或所述目的账户对应的客户端。
  5. 根据权利要求1至4中任一项所述的视频推送方法，其中，所述视频的标识包括所要推送的视频的链接。
  6. 一种服务器，其中，所述服务器包括：
    接收模块，接收所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户，其中，提供所述视频的标识的源客户端与所述目的客户端绑定，和/或与所述源客户端对应的源账户与所述目的账户绑定；以及
    推送模块，将所述视频的标识推送至所述目的客户端和/或目的账户对应的客户端。
  7. 根据权利要求6所述的服务器，其中，所述接收模块还用于从所述目的客户端和/或所述目的账户对应的客户端接收针对所述视频的标识的请求；以及响应于所述请求，所述推送将所述视频的标识对应的所述视频发送至所述目的客户端和/或目的账户对应的客户端。
  8. 根据权利要求6或7所述的服务器，其中，所述服务器还包括存储模块，用于存储所要推送的视频的标识及所要推送至的目的客户端和/或所要推送至的目的账户对应的客户端。
  9. 根据权利要求6，7或8所述的服务器，其中，在所述目的客户端和/或所述目的账户在线时，所述推送模块将所述视频的标识推送至所述目的客户端和/或所述目的账户对应的客户端。
  10. 根据权利要求6至9中任一项所述的服务器，其中，所述视频的标识包括所要推送的视频的链接。
  11. 一种不同客户端间的视频推送系统，所述视频推送系统包括：源客户端、目的客户端及权利要求6至10中任一项所述的服务器；
    所述源客户端用于向所述服务器发送所要推送的视频的标识及所要推 送至的所述目的客户端和/或所要推送至的所述目的客户端对应的目的账户；
    所述目的客户端用于接收所述服务器推送的所述视频的标识。
  12. 根据权利要求11所述的视频推送系统，其中，
    所述目的客户端还用于向所述服务器发送针对所述视频的标识的请求；所述目的客户端接收所述服务器响应于所述请求发送的所述视频的标识对应的所述视频。
PCT/CN2016/089528 2015-12-14 2016-07-10 不同客户端间的视频推送方法、系统及服务器 Ceased WO2017101409A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/242,148 US20170171331A1 (en) 2015-12-14 2016-08-19 Method and electronic device for pushing videos between different clients

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510922943.4 2015-12-14
CN201510922943.4A CN105897842A (zh) 2015-12-14 2015-12-14 不同客户端间的视频推送方法、系统及服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/242,148 Continuation US20170171331A1 (en) 2015-12-14 2016-08-19 Method and electronic device for pushing videos between different clients

Publications (1)

Publication Number Publication Date
WO2017101409A1 true WO2017101409A1 (zh) 2017-06-22

Family

ID=57002965

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089528 Ceased WO2017101409A1 (zh) 2015-12-14 2016-07-10 不同客户端间的视频推送方法、系统及服务器

Country Status (2)

Country Link
CN (1) CN105897842A (zh)
WO (1) WO2017101409A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107231361A (zh) * 2017-06-12 2017-10-03 北京佰才邦技术有限公司 一种信息推送方法、系统、服务器及第一客户端
CN110996136B (zh) * 2019-12-04 2022-02-11 聚好看科技股份有限公司 视频资源的显示方法及装置
CN110958432B (zh) * 2019-12-13 2021-05-25 睿云联(厦门)网络通讯技术有限公司 基于rtsp协议的跨网络云端远程监控系统及监控方法
CN113438489B (zh) * 2021-08-26 2021-12-14 深圳市万佳安物联科技股份有限公司 云端视频的推送方法及推送系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103634363A (zh) * 2012-08-28 2014-03-12 杨念民 基于关系链的内容辅助定制互动方法及系统
CN103974137A (zh) * 2014-05-15 2014-08-06 北京奇艺世纪科技有限公司 一种跨设备推送视频资源的方法及装置
US20140324986A1 (en) * 2013-04-28 2014-10-30 Tencent Technology (Shenzhen) Company Limited Information collection, storage, and sharing platform
CN104639974A (zh) * 2015-02-27 2015-05-20 北京奇艺世纪科技有限公司 一种信息推送方法及装置
CN104683410A (zh) * 2013-12-02 2015-06-03 深圳市迅雷网络技术有限公司 一种资源共享方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2917554B1 (fr) * 2007-06-14 2010-01-01 Alcatel Lucent Dispositif de gestion de reception par des terminaux de contenus multimedia transmis par des infrastructures mettant en oeuvre des techniques de transmission differentes
CN104301758A (zh) * 2014-10-10 2015-01-21 安徽华米信息科技有限公司 一种推送视频的方法、装置及系统
CN104661057B (zh) * 2015-02-05 2018-06-19 深圳创维－Rgb电子有限公司 一种基于社交平台的视频分享方法及系统
CN104869439B (zh) * 2015-05-14 2018-03-09 无锡天脉聚源传媒科技有限公司 一种视频推送方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103634363A (zh) * 2012-08-28 2014-03-12 杨念民 基于关系链的内容辅助定制互动方法及系统
US20140324986A1 (en) * 2013-04-28 2014-10-30 Tencent Technology (Shenzhen) Company Limited Information collection, storage, and sharing platform
CN104683410A (zh) * 2013-12-02 2015-06-03 深圳市迅雷网络技术有限公司 一种资源共享方法及装置
CN103974137A (zh) * 2014-05-15 2014-08-06 北京奇艺世纪科技有限公司 一种跨设备推送视频资源的方法及装置
CN104639974A (zh) * 2015-02-27 2015-05-20 北京奇艺世纪科技有限公司 一种信息推送方法及装置

Also Published As

Publication number Publication date
CN105897842A (zh) 2016-08-24

Similar Documents

Publication Publication Date Title
CN107534672B (zh) 一种促进网络客户端提供网络服务的方法、设备与系统
US11716207B1 (en) System and method for a dynamic-PKI for a social certificate authority
CN102713951B (zh) 跨越多个社交网络站点自动同步新联络人
US8468587B2 (en) Binding activation of network-enabled devices to web-based services
US9774642B2 (en) Method and device for pushing multimedia resource and display terminal
US20130055323A1 (en) Method and system for connecting a companion device to a primary viewing device
CN107211029B (zh) 服务控制器设备以及对应的发现和连接的方法和系统
CN102904903B (zh) 通信系统和通信方法
CN109076007B (zh) 异步消息传递系统中单个账号的配置文件管理方法及系统
CN105451087A (zh) 弹幕信息的推送方法、终端、历史数据服务器及系统
CN105122931A (zh) 电子设备及在其用户门户服务器中注册个人云装置的方法
CN102763373B (zh) 基于远程访问使用本地网络装置的服务的方法和设备
KR20180022867A (ko) 근거리 통신을 통한 애플리케이션 버전 설치 방법 및 시스템
CN102685101A (zh) 社交网络上的代理通信
KR20130082588A (ko) Ｓｎｓ 그룹 초대 서비스 제공 방법 및 그를 위한 ｓｎｓ 서버
WO2017101409A1 (zh) 不同客户端间的视频推送方法、系统及服务器
CN103023907A (zh) 获取网站信息的方法，设备及系统
CN101854376A (zh) 点对点文件分享系统及方法
WO2018113693A1 (zh) 局域网设备通信管理方法、系统及网关设备
US9582561B2 (en) Size-based data synchronization
CN103986710B (zh) 一种消息传输的方法、装置及系统
CN105721274A (zh) 一种多种即时通讯的融合方法及装置
WO2023005199A1 (zh) 数据处理方法及装置
CN105681162A (zh) 一种信息同步的方法、装置和系统
US20070239827A1 (en) Global chat system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16874471

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16874471

Country of ref document: EP

Kind code of ref document: A1