WO2009056043A1 - Procédé, système et équipement pour obtenir des signets d'enregistrement dans un système de télévision sur ip - Google Patents

Procédé, système et équipement pour obtenir des signets d'enregistrement dans un système de télévision sur ip Download PDF

Info

Publication number
WO2009056043A1
WO2009056043A1 PCT/CN2008/072784 CN2008072784W WO2009056043A1 WO 2009056043 A1 WO2009056043 A1 WO 2009056043A1 CN 2008072784 W CN2008072784 W CN 2008072784W WO 2009056043 A1 WO2009056043 A1 WO 2009056043A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
recording
client
media
control function
Prior art date
Application number
PCT/CN2008/072784
Other languages
English (en)
Chinese (zh)
Inventor
Xiao Wang
Jun Yan
Original Assignee
Huawei Technologies 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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009056043A1 publication Critical patent/WO2009056043A1/fr

Links

Classifications

    • 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/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9562—Bookmark management
    • 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 embodiments of the present invention relate to communication technologies, and in particular, to a method, system, and device for acquiring a recording label in an IPTV system.
  • IPTV Internet Protocol Television
  • IMS IP Multimedia Subsystem
  • FIG. 1 is a schematic diagram of a draft general architecture of existing media control defined by the Internet Engineering Task Force (IETF).
  • the IETF defines three logical entities in the architecture, including: Control Server, Control Client, and Control Channel.
  • the session description protocol (SDP) of the session initiation protocol (SDP) is established between the control server and the control client, and a media control channel is established, and the control client sends the media to the control server through the media control channel. Control messages to implement media control processing.
  • FIG. 2 is an existing IMS-based implementation defined by the European Telecommunications Standards Institute (ETSI, Telecommunications and Internet converged Services and Protocols for Advanced Networking).
  • the IPTV media function (MF, Media Function) entity may include a Media Delivery Function (MDF) entity and a Media Control Function (MCF) entity from a functional point of view; the media delivery function entity is usually some
  • MDF Media Delivery Function
  • MCF Media Control Function
  • the media server under the control of the media control function entity, transmits the media stream required by the user to the user terminal.
  • the user terminal establishes a Real-Time Streaming Protocol (RTSP) control channel with the MCF through an IPTV Service Control Function (SCF) entity.
  • RTSP Real-Time Streaming Protocol
  • SCF IPTV Service Control Function
  • the SCF controls the MCF to implement related media functions through the y2 interface with the MCF.
  • a system selection function (SSF, Service Selection Function) may be further included in the system of the architecture for providing service information to the user, and the user selects the related service according to the service information.
  • NPVR Network Personal Video Record
  • the user can initiate a recording request to the network through the terminal, and record the specified channel program online; during the recording process, the user terminal can By interacting with the SCF, the recorded content is tagged (BookMark) to jump according to the tag during playback.
  • the recorded tag needs to be acquired first.
  • the user terminal cannot obtain the recording label. Therefore, according to the current prior art, some services of the IPTV (such as the NPVR service) cannot be successfully carried out if the recording label is required.
  • An embodiment of the present invention provides a method for acquiring a recording label in an IPTV system, which is used to solve the problem that a user terminal cannot obtain a recording label in the prior art.
  • the method includes:
  • the client sends a first message to the recording label providing entity, where the first message is used to request to acquire a recording label;
  • the client receives the second message sent by the recording label providing entity according to the first message, where the second message carries the recording label;
  • the client acquires the recording label from the second message.
  • the embodiment of the present invention further provides a client in an IPTV system, where the client includes: a sending module, where the sending module is configured to send a first message to a recording label providing entity, where the first message is used to request to obtain Recording a label;
  • the receiving module is configured to receive a second message that is sent by the recording label providing entity according to the first message, where the second message carries the recording label;
  • Recording a tag acquisition module where the recording tag acquisition module is configured to obtain from the second message The recording tag.
  • the embodiment of the present invention further provides a recording label providing entity in an IPTV system, where the recording label providing entity includes:
  • a receiving module configured to receive a first message sent by the client, where the first message is used to request to obtain a recording label
  • a sending module configured to send a second message to the client according to the first message, where the second message carries the recording label.
  • An embodiment of the present invention further provides a system for acquiring a recording label in an IPTV system, including: a client and a recording label providing entity;
  • the recording label providing entity is configured to receive a first message sent by the client, where the first message is used to request to acquire a recording label, and the client is configured to receive the recording label providing entity according to the first message.
  • the client and the recording tag provide entity interaction to obtain a recording label, so that
  • IPTV IPTV
  • NPVR services Some services in IPTV that require the use of recording tags (such as NPVR services) can be carried out smoothly.
  • Figure 1 is a schematic diagram of a draft general architecture of existing media control defined by the IETF;
  • FIG. 2 is a schematic diagram of a functional architecture of an existing IMS-based IPTV service defined by ETSI TISPAN;
  • Embodiment 1 of the present invention is a schematic flow chart of Embodiment 1 of the present invention.
  • Embodiment 2 of the present invention is a schematic flow chart of Embodiment 2 of the present invention.
  • Embodiment 3 of the present invention is a schematic flow chart of Embodiment 3 of the present invention.
  • Embodiment 4 of the present invention is a schematic flow chart of Embodiment 4 of the present invention.
  • Figure 8 is a schematic diagram of a system in accordance with an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a client according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a recording label providing entity according to an embodiment of the present invention.
  • the client obtains the recording label by interacting with the recording label providing entity, and the specific method is as follows:
  • the client sends the first message to the recording tag providing entity
  • the client obtains the recording label from the second message.
  • the client can be a user terminal (UE, User Equipment) or a network entity.
  • the recording function is combined with the service providing entity, the UE obtains the recording label by the method described in the embodiment of the present invention, and then plays the desired media content by interacting with the service providing entity according to the recording label; in another case, recording
  • the function is separated from the service providing entity, and the service providing entity, as the client, obtains the recording label from the entity having the recording function by using the method of the embodiment of the present invention, and then the service providing entity delivers the recording label to the UE.
  • the service providing entity obtains the recording label as a network entity, and there are other network entities (such as an application server (AS, Application Server), etc.) to obtain the recorded label, such as: having certain recording related services. (such as NPVR business), etc., not here - enumeration.
  • AS Application Server
  • NPVR business NPVR business
  • the client After the client obtains the recording label, the client can request the service providing entity to start playback of the recorded media content from the recording label designation.
  • the embodiment of the present invention takes the functional architecture of the existing IMS-based IPTV service defined by ETSI TISPAN as an example, and can also be applied to other similar IPTV functional architectures.
  • FIG. 3 The method flow of the first embodiment of the present invention is shown in FIG. 3.
  • the recording label providing entity is a service control function (SCF) entity; and the third party control (SIP REFER) method in the session initiation protocol is used to trigger the SCF to send a recording standard to the client.
  • the client sends a third party control (REFER) message to the SCF; after receiving the REFER message, the SCF sends a PUBLISH message or a MESSAGE message or session information (INFO) to the client.
  • REFER third party control
  • INFO session information
  • Steps 301 ⁇ 302 The client sends a REFER message, and the REFER message is routed to the SCF through the core IP multimedia subsystem (Core IMS);
  • the refer-to header field carries the address of the client and the playback recording medium identifier; the value of the method parameter is PUBLISH;
  • REFER message An example of a REFER message is given below, where only the key header fields are given, where the recordid parameter carries the playback recording media identifier:
  • Steps 305 to 306 The SCF sends a PUBLISH message to the client, and the PUBLISH message is routed to the client through the Core IMS; the recording label is carried in the PUBLISH message;
  • ⁇ /bookmark> In the above XML script, a ⁇ 111> item represents a tag, the tag is in an absolute timetable, and the relative time can also be used. Labels come in a variety of forms, and this is just an example.
  • Steps 307 ⁇ 308 The client receives the PUBLISH message and returns a 200 OK response message.
  • the method flow of the second embodiment of the present invention is shown in FIG.
  • the recording tag providing entity is a media control function (MCF) entity.
  • MCF media control function
  • the client sends a session message to the SCF, and establishes a media session and an RTSP control channel for playing back the recording medium through media negotiation; the SCF sends the label of the recording medium to the MCF; the client obtains the label through the RTSP command.
  • MCF media control function
  • Step 401 The client initiates an operation of playing back the recording medium, and performs media negotiation through the SCF and the MCF to establish a media session and an RTSP control channel.
  • Step 402 The SCF sends the label of the playback media to the MCF.
  • the specific form may be sent to the MCF by using the INVITE message in the media session, or sent to the MCF through the media control message.
  • Step 403 After the media session negotiation succeeds, the RTSP control channel is established between the client and the MCF; the client sends an RTSP control command acquisition parameter (GET_PARAMETER) to the MCF to obtain the label;
  • GET_PARAMETER an RTSP control command acquisition parameter
  • Step 404 The MCF returns an RTSP success response message (ie, a 200 OK response message), where the response message carries a recording label.
  • RTSP success response message ie, a 200 OK response message
  • Step 405 The client selects one of the recording tags obtained in step 404 as the starting tag of the starting position, and further selects one of the recording tags obtained in step 404 as the ending tag of the ending position ( In practical applications, the setting end position may not be selected; the client sends an RTSP control command setting parameter (SET_PARAMETER) or play (PLAY) to the MCF, which carries the preceding start tag or the media in the start tag.
  • the start location information may also carry the end tag or the end location information of the media play in the end tag.
  • the client sets the starting position of the media playback through the SET_PARAMETER command (you can further set the end position); then the client requests the MCF according to the starting position through the PLAY command (also It may further include an end position) to start playing the specified media.
  • the client can also pass directly
  • the PLAY command which carries the starting position of the playing media in the Range header field (you can further set the ending position), requests the MCF to start playing the specified media according to the starting position (which may further include the ending position).
  • ⁇ Start> indicates the position where playback starts
  • ⁇ End> indicates the position where playback stops
  • ⁇ End> can be omitted. Only ⁇ Start>, stop playback is controlled by the terminal in real time.
  • PLAY command where only the key header fields are given:
  • the carried recording label only includes the time information describing the location of the media (of course, the time information in the actual application may also be time offset information, file offset information, etc.); and the recording label may also include the label.
  • Other business related information such as: label identification, recording media content identification, media content brief description or label owner and other related business information, can not be one by one.
  • the label uses the XML description method.
  • other description methods can also be used.
  • the Content-type (text type) parameter description method of text/parameters (text format) is not repeated here. .
  • the method flow of the third embodiment of the present invention is shown in FIG. 5.
  • the recording label providing entity is a service control function (SCF) entity; and the recording label is obtained by using a SIP subscription method.
  • SCF service control function
  • the client subscribes to the SCF for an event package containing a recording tag.
  • Steps 501 ⁇ 502 The client sends a subscription (SUBSCRIBE) message to the SCF, and the SUBSCRIBE message is routed to the SCF through the Core IMS; in the SUBSCRIBE message, the value of the Request-URI is the playback recording media resource;
  • SUBSCRIBE subscription
  • the above subscription can use the Fetch method.
  • the value of the Expires header field is set to 0. In this way, the SCF can only send a recording label to the client, avoiding subsequent Repeated delivery.
  • Steps 503 ⁇ 504 The SCF receives the SUBSCRIBE message, returns a response message of 200 OK, and routes to the client through the Core IMS;
  • Steps 505 - 506 SCF sends a notification to the client (NOTIFY) message carries the subscription recording The recording label of the media; an example of a NOTIFY message is given below, where only the key header fields are given:
  • Steps 507 ⁇ 508 The client receives the NOTIFY message and returns a response message of 200 OK.
  • the method flow of the fourth embodiment of the present invention is shown in FIG. 6.
  • the recording label providing entity is a service selection function (SSF) entity.
  • the client obtains the recording label of the specified recording medium from the SSF through the Get (GET) method of the Hypertext Transfer Protocol (HTTP); the client obtains the file name of the label file on the SSF in advance.
  • the path, the recording file of the recording medium is saved in the label file (for example, the file name and path of the label file on the SSF can be obtained in the service discovery process or the file name and path of the label file on the SSF can be statically configured on the client. in).
  • the specific process description is as follows:
  • Step 601 The client obtains the configuration data of the user, where the configuration data includes the location where the recording label of the recording medium is saved (in this embodiment, the file name and path of the label file saved on the SSF, and of course other network element devices) );
  • Step 602 The client sends an HTTP GET message to the SSF to request to obtain the specified recording medium. Record the label; an example of a GET message is given below:
  • Step 603 The SSF returns a 200 OK response message to the client, where the response message carries the recording label of the recording medium;
  • An example of a 200 OK message is given below, where only the key header fields are given: HTTP/1.1 200 OK
  • the recording label providing entity is a service control function (SCF).
  • SCF service control function
  • the SCF sends the recording label of the recording media to the client through the 200 OK response message corresponding to the session establishment message (INVITE) of the SIP protocol in the process of the media session being established between the client and the SCF.
  • INVITE session establishment message
  • Step 701 - 702 The client sends an INVITE message to the SCF to establish a media session, and the INVITE message is routed to the SCF through the Core IMS.
  • the client and the SCF negotiate to establish a media session for playing back the recording medium.
  • the Request-URI value is the recording media resource address; and the Accept-Contact header field can carry the recording service identifier NPVR.
  • Steps 703 ⁇ 704 The SCF receives the INVITE request, and the recording medium is transmitted through the 200 OK response message. The label of the body is brought back to the client;
  • Steps 705 ⁇ 706 The client returns an ACK (acknowledgement message) to the SCF after receiving the 200 OK response message.
  • FIG. 8 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • the system includes: a client 801 and a recording tag providing entity 802;
  • the recording tag providing entity 802 is configured to receive the first message sent by the client 801;
  • the client 801 is configured to receive the second message carrying the recording label sent by the recording label providing entity 802, and obtain the recording label from the second message.
  • the recording tag providing entity 802 may be a Service Control Function (SCF) entity, the first message may be a SIP REFER message, and the second message may be a PUBLISH message or a MESSAGE message or an INFO message; in this case, the SIP REFER method may be used to trigger the SCF direction.
  • SCF Service Control Function
  • the client sends a recording label; the client sends a REFER message to the SCF; after receiving the REFER message, the SCF sends a PUBLISH message or a MESSAGE message or an INFO message to the client, and carries the recording label to the client through the message;
  • the recording tag providing entity 802 may be a media control function (MCF) entity, and the first message may be The GET_PARAMETER command, the second message may be an RTSP success response message; in this case, the client sends a session message to the SCF, and establishes a media session and an RTSP control channel for playing back the recording medium through media negotiation; the SCF will record the media.
  • MCF media control function
  • the label is sent to the MCF; the client obtains the label through the RTSP command; the client can also select the starting label from the recording label.
  • the client can send a SET_PARAMETER command to the MCF, the SET_PARAMETER command SET_PARAMETER command includes a start tag, the start tag is used to set the starting position of the media play; then the client sends a PLAY command to the MCF, The MCF is requested to play the media according to the starting position; or the client may also send a PLAY command to the MCF, where the PLAY command includes the starting position of the playing media in the starting tag, and requests the MCF to play the media according to the starting position.
  • the SET-PARAMETER or PLAY command may further include an end tag for determining the ending position of the playing media, and the specific carrying method is similar to that in the second embodiment.
  • the recording tag providing entity 802 may be a Service Control Function (SCF) entity, the first message may be a SUBSCRIBE message, and the second message may be a NOTIFY message; in this case, the SIP subscription is used to obtain the recording tag; the client subscribes to the SCF to include the tag. Event package (this subscription can use Fetch mode, the value of the Expires header field is set to 0);
  • SCF Service Control Function
  • the recording tag providing entity 802 may be a service selection function (SSF) entity, the first message may be an HTTP GET message, and the second message may be a success response message (eg, 200 OK); in this case, the client GET through the HTTP protocol
  • the method obtains the recording label of the specified recording medium from the SSF; the client obtains the location where the recording label of the recording medium on the SSF is saved in advance (for example, through the service discovery process or statically configured in the client), the label file name and the recorded media file.
  • the recording tag providing entity 802 may be a Service Control Function (SCF) entity, the first message may be an INVITE message, and the second message may be a success response message; in this case, the client establishes a media session with the SCF. During the process, the SCF sends the recording label of the recording media to the client through the 200 OK response message corresponding to the INVITE message.
  • SCF Service Control Function
  • the schematic diagram of a client structure according to an embodiment of the present invention includes:
  • the sending module 901 is configured to send the first message to the recording label providing entity;
  • the receiving module 902 is configured to receive a second message of the recording label providing entity, where the second message carries the recording label;
  • the recording label obtaining module 903 is configured to obtain a recording label from the second message.
  • the recording tag providing entity may be a Service Control Function (SCF) entity
  • the first message may be a SIP REFER message
  • the second message may be a PUBLISH message or a MESSAGE message or an INFO message
  • the SIP REFER method is used to trigger the SCF to the client.
  • Sending a recording label the client sends a REFER message to the SCF; after receiving the REFER message, the SCF sends a PUBLISH message or a MESSAGE message or an INFO message to the client, and carries the recording label to the client through the message;
  • the recording label providing entity may be a media control function (MCF) entity, the first message may be an RTSP command, and the second message may be an RTSP command response message; in this case, the client may further include a negotiation module for using the service
  • MCF media control function
  • the control function SCF media negotiation establishes an RTSP control channel for playing back the recording medium with the MCF; the SCF sends the label of the recording medium to the MCF; the client obtains the label through the RTSP command; the client may further include a start label selection module for Select the starting label from the above recording labels;
  • the client may further include a media play setting module, configured to send a SET_PARAMETER command to the MCF, the SET-PARAMETER includes a start tag, and the start tag is used to set a starting position of the media play, in which case
  • the client may further include a media play request module, configured to send a PLAY command to the MCF, requesting the MCF to play the media according to the starting position;
  • the client may further include a media playing module, configured to send a PLAY command to the MCF, where the PLAY command includes a starting position of the playing media in the starting tag, and the MCF is requested to play the media according to the starting position.
  • a media playing module configured to send a PLAY command to the MCF, where the PLAY command includes a starting position of the playing media in the starting tag, and the MCF is requested to play the media according to the starting position.
  • the SET-PARAMETER or PLAY command may further include an end tag, which is used to determine the end position of the playing media, and the specific carrying method and the specific embodiment 2 Like.
  • the recording label providing entity may be a Service Control Function (SCF) entity, the first message may be a SUBSCRIBE message, and the second message may be a NOTIFY message; in this case, the SIP subscription is used to obtain the recording label; the client subscribes to the SCF to include the label.
  • Event package (this subscription can use Fetch mode, the value of the Expires header field is set to 0);
  • the recording tag providing entity may be a service selection function (SSF) entity
  • the first message may be an HTTP GET message
  • the second message may be a success response message
  • the client may further include a configuration data acquiring module, configured to obtain a configuration module, configured to determine, according to the configuration data, that the recording label is saved in the service selection function SSF; the client obtains the recording label of the specified recording medium from the SSF by using the GET method of the HTTP protocol; the client obtains the recording medium on the SSF in advance Record the location where the tag is saved (for example, through the service discovery process or statically configured in the client);
  • the recording label providing entity may be a service control function (SCF) entity, the first message may be an INVITE message, and the second message may be a success response message; in this case, the client further includes an establishing module for the service control function SCF Negotiating to establish a media session for playing back the recording medium; in the process of the client establishing a media session with the SCF, the SCF sends the recording label of the recording media to the client through the 200 OK response message corresponding to the INVITE message;
  • SCF service control function
  • the above client may be a user terminal or a network entity.
  • FIG. 10 it is a schematic diagram of a physical structure of a recording label according to an embodiment of the present invention, including: a receiving module 1001, configured to receive a first message sent by a client;
  • the sending module 1002 is configured to send a second message to the client, where the second message carries the recording label.
  • the recording tag providing entity may be a Service Control Function (SCF) entity
  • the first message may be a SIP REFER message
  • the second message may be a PUBLISH message or a MESSAGE message or an INFO message; in this case, the SIP REFER method is used to trigger the SCF to the client.
  • Sending a recording label the client sends a REFER message to the SCF; after receiving the REFER message, the SCF sends a PUBLISH message or a MESSAGE message or an INFO message to the client, and carries the message through the foregoing message.
  • the recording label is returned to the client;
  • the recording label providing entity may be a media control function (MCF) entity, the first message may be an RTSP command, and the second message may be an RTSP command response message; in this case, the recording label providing entity may further include a recording label obtaining module, The recording label delivered by the SCF is received by the service control function; the client obtains the label by using the RTSP command.
  • MCF media control function
  • the recording label providing entity may be a Service Control Function (SCF) entity, the first message may be a SUBSCRIBE message, and the second message may be a NOTIFY message; in this case, the SIP subscription is used to obtain the recording label; the client subscribes to the SCF to include the label.
  • Event package (this subscription can use Fetch mode, the value of the Expires header field is set to 0);
  • the recording tag providing entity may be a service selection function (SSF) entity, the first message may be an HTTP GET message, and the second message may be a success response message; in this case, the client obtains the specified recording to the SSF through the GET method of the HTTP protocol. Recording label of the media; the client obtains in advance the location where the recording label of the recording medium on the SSF is saved (for example, through the service discovery process or statically configured in the client);
  • SSF service selection function
  • the recording label providing entity may be a service control function (SCF) entity, the first message may be an INVITE message, and the second message may be a success response message; in this case, the recording label providing entity may further include a negotiation module for using the client In the process of establishing a media session by the client and the SCF, the SCF sends the recording label of the recording media to the client through the 200 OK response message corresponding to the INVITE message.
  • SCF service control function

Abstract

L'invention a trait aux technologies de communication et concerne un procédé pour obtenir des signets d'enregistrement dans un système de télévision sur IP. Le procédé comporte les étapes suivantes: un client envoie un premier message pour demander d'obtenir un signet d'enregistrement à une entité fournissant des signets d'enregistrement; le client reçoit un second message portant le signet d'enregistrement envoyé par ladite entité, conformément au premier message; le client obtient le signet d'enregistrement contenu dans le second message. Ce procédé permet au client et à l'entité d'obtenir de manière interactive des signets d'enregistrement, et permet de mettre en œuvre avec succès certains services de télévision sur IP. L'invention concerne aussi un système pour obtenir des signets d'enregistrement, comprenant un client et une entité fournissant des signets d'enregistrement dans un système de télévision sur IP.
PCT/CN2008/072784 2007-10-26 2008-10-22 Procédé, système et équipement pour obtenir des signets d'enregistrement dans un système de télévision sur ip WO2009056043A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA2007101240924A CN101420588A (zh) 2007-10-26 2007-10-26 一种iptv系统中录制标签的获取方法、系统及设备
CN200710124092.4 2007-10-26

Publications (1)

Publication Number Publication Date
WO2009056043A1 true WO2009056043A1 (fr) 2009-05-07

Family

ID=40590551

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072784 WO2009056043A1 (fr) 2007-10-26 2008-10-22 Procédé, système et équipement pour obtenir des signets d'enregistrement dans un système de télévision sur ip

Country Status (2)

Country Link
CN (1) CN101420588A (fr)
WO (1) WO2009056043A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220103440A1 (en) * 2019-01-07 2022-03-31 China Mobile Communication Co., Ltd Research Institute Data processing method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1801929A (zh) * 2005-12-08 2006-07-12 复旦大学 一种网络互动电视系统实现时移功能的方法
CN1946162A (zh) * 2006-10-27 2007-04-11 华为技术有限公司 一种获取epg的方法及iptv业务系统
CN1968400A (zh) * 2006-01-05 2007-05-23 中兴通讯股份有限公司 一种iptv业务频道化方法
US20070244903A1 (en) * 2006-04-18 2007-10-18 Ratliff Emily J Collectively managing media bookmarks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1801929A (zh) * 2005-12-08 2006-07-12 复旦大学 一种网络互动电视系统实现时移功能的方法
CN1968400A (zh) * 2006-01-05 2007-05-23 中兴通讯股份有限公司 一种iptv业务频道化方法
US20070244903A1 (en) * 2006-04-18 2007-10-18 Ratliff Emily J Collectively managing media bookmarks
CN1946162A (zh) * 2006-10-27 2007-04-11 华为技术有限公司 一种获取epg的方法及iptv业务系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220103440A1 (en) * 2019-01-07 2022-03-31 China Mobile Communication Co., Ltd Research Institute Data processing method and device
US11924070B2 (en) * 2019-01-07 2024-03-05 China Mobile Communication Co., Ltd Research Institute Data processing method and device

Also Published As

Publication number Publication date
CN101420588A (zh) 2009-04-29

Similar Documents

Publication Publication Date Title
CN101573943B (zh) 媒体频道管理
JP4927879B2 (ja) Ｉｐｔｖのための、ｉｍｓ対応のコントロールチャネル
EP1988666B1 (fr) Système de réseau de transmission multimédia en continu, procédé de mise en oeuvre et entité d'activation de service de transmission multimédia en continu
CA2610515C (fr) Commande de sous-systeme multimedia pour protocole internet base sur des services de television
CN102415071B (zh) 会话推送传输
US20110138432A1 (en) Media Bookmarks
US8326942B2 (en) IP unicast streaming service delivery
US8307049B2 (en) Method and device for obtaining media description information of IPTV services
WO2008038200A2 (fr) Procédé et serveur pour le transfert d'une session multimédia d'un premier terminal à un second terminal
KR100891745B1 (ko) 주문형 비디오 서비스 제공을 위한 프로토콜 변환 방법 및 그 장치
US20100122281A1 (en) Method and system for controlling authorization of service resources
KR20090018673A (ko) Ｉｍｓ 아키텍쳐 네트워크에서 ｉｐ 텔레비젼 서비스에 액세스하기 위한 시스템
WO2007098682A1 (fr) Procédé permettant d'obtenir un guide de programmes électronique, système pour guide de programmes électronique et unité de mise en service
KR20090123781A (ko) 멀티캐스트 세션을 통해 수신한 어플리케이션에 기초한 ｉｐｔｖ 서비스 이용 방법 및 장치
US20080010380A1 (en) Re-directing video according to a standard protocol
WO2008098500A1 (fr) Procédé et appareil pour découvrir un service de flux de données multimédia et appareil pour découvrir un service
WO2009006814A1 (fr) Procédé d'établissement d'un service de télévision à décalage dans le temps et entité de fonction multimédia de télévision à décalage dans le temps
WO2009049509A1 (fr) Procédé et appareil de commande pour lire des données d'un flux multimédia
WO2011150705A1 (fr) Système et procédé de mise en œuvre d'une communication instantanée
WO2010028601A1 (fr) Procédé, système et équipement pour transmettre des contenus multimédia à l'aide de fichiers
WO2010028591A1 (fr) Procédé et système de réalisation d'enregistrement dans un terminal client et entité de contrôle d'enregistrement
US8671422B2 (en) Systems and methods for handling advertisements in conjunction with network-based bookmarking
WO2009056043A1 (fr) Procédé, système et équipement pour obtenir des signets d'enregistrement dans un système de télévision sur ip
WO2009024053A1 (fr) Procédé et système pour transférer un message de découverte d'opération et entité fonctionnelle pour une découverte d'opération
WO2009024077A1 (fr) Procédé et dispositif pour acquérir un paramètre de service iptv

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: 08845467

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: 08845467

Country of ref document: EP

Kind code of ref document: A1