CN101420588A

CN101420588A - Recorded label obtaining method, system and equipment in IPTV system

Info

Publication number: CN101420588A
Application number: CNA2007101240924A
Authority: CN
Inventors: 王啸; 严军
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-10-26
Filing date: 2007-10-26
Publication date: 2009-04-29
Also published as: WO2009056043A1

Abstract

The embodiment of the invention relates to a communication technology and discloses a method for obtaining a recording tag from an IPTV system, the method comprises: a client sends a first message to a recording tag providing entity, the first message is used for requesting the obtainment of the recording tag; the client receives a second message which is sent by the recording tag providing entity according to the first message, the second message carries the recording tag; and the client obtains the recording tag from the second message. The application of the method can lead the client and the recording tag providing entity to interactively obtain the recording tag, thereby leading certain businesses of IPTV to be developed smoothly. The embodiment of the invention also provides a system for obtaining the recording tag form the IPTV system, the client and the recording tag providing entity.

Description

Acquisition methods, system and the equipment of recorded label in a kind of IPTV system

Technical field

The embodiment of the invention relates to the communication technology, acquisition methods, system and the equipment of recorded label in the particularly a kind of IPTV system.

Background technology

Internet protocol TV (IPTV, IP Television) technology is to utilize technology such as broadband cabled TV network, computer interconnected network and communication network.The IPTV business is usually based on IP Multimedia System (IMS; IP Multimedia Subsystem) realizes; to make full use of mechanism such as existing session control and foundation in the IMS network, provide the technology of the interactive multimedia business such as business of streaming media service, fusion Streaming Media and real-time session business for the user.

Referring to Fig. 1, Fig. 1 is the generic structure draft schematic diagram of the existing medium control of ietf definition.Ietf definition three logic entities in this framework, comprising: Control Server (Control Server), control client (Control Client) and media control channel (Control Channel).Wherein, dialogue-based initiation protocol (SIP between Control Server and the control client, Session Initial Protocol) Session Description Protocol (SDP, Session Description Protocol), set up media control channel, the control client sends the medium control messages by media control channel, realizes the medium control and treatment.

Referring to Fig. 2, be the function structure schematic diagram that has the IPTV business that realizes based on IMS now of ETSI TISPAN definition.Wherein, IPTV media function (MF, Media Function) entity can comprise media delivery function (MDF, Media Delivery Function) entity and media control function (MCF, Media Control Function) from functional perspective; The media delivery functional entity is some media servers normally, under the control of media control function entity, transmit the Media Stream that the user needs to user terminal.In Streaming Media was used, user terminal was set up RTSP control channel by IPTV service control function (SCF, Service ControlFunction) entity with MCF.SCF by and MCF between the y2 interface, control MCF realizes the related media function.

Can also comprise that in the system of this framework service selection capability (SSF, Service SelectionFunction) is used for providing information on services to the user, the user selects related service according to information on services.

In some business of IPTV, (by the NPVR business, the user can initiate recording request to network by terminal, the online channel program of recording appointment such as the professional NPVR of network REC (Network Personal videoRecord) business; In recording process, user terminal can stamp label (BookMark) for the content of recording, so that carry out redirect according to label when playback by mutual with SCF), when user's playback recorded content, need obtain the label of recording earlier.In present prior art, user terminal can't obtain recorded label, therefore according to present prior art, in some business of IPTV (as the NPVR business), uses recorded label then can not carry out smoothly as needs.

Summary of the invention

The embodiment of the invention provides the acquisition methods of recorded label in a kind of IPTV system, is used for solving the problem that the prior art user terminal can't obtain recorded label.This method comprises: client sends first message to recorded label entity is provided, and described first message is used for the acquisition request recorded label;

Described client receives described recorded label second message of entity according to described first message sends is provided, and carries described recorded label in described second message;

Described client is obtained described recorded label from described second message.

The embodiment of the invention also provides the client in a kind of IPTV system, and described client comprises sending module, and described sending module is used to send first message to recorded label provides entity, and described first message is used for the acquisition request recorded label;

Receiver module, described receiver module are used to receive described recorded label provides second message of entity according to described first message sends, and carries described recorded label in described second message;

Recorded label acquisition module, described recorded label acquisition module are used for obtaining described recorded label from described second message.

The embodiment of the invention also provides the recorded label in a kind of IPTV system that entity is provided, and comprises receiver module, is used to receive first message that client sends, and described first message is used for the acquisition request recorded label; Sending module is used for sending second message to described client according to described first message, carries described recorded label in described second message.

The embodiment of the invention also provides the system that obtains of recorded label in a kind of IPTV system, and comprising: client and recorded label provide entity;

Described recorded label provides entity to be used to receive first message that described client sends, and described first message is used for the acquisition request recorded label; Described client is used to receive described recorded label provides entity to send second message according to described first message, and described second message is carried described recorded label; Described client also is used for obtaining described recorded label from described second message.

The embodiment of the invention provides entity interaction to obtain recorded label by client and recorded label, makes that some need use the business (as the NPVR business) of recorded label to carry out smoothly among the IPTV.

Description of drawings

Fig. 1 is the generic structure draft schematic diagram of the existing medium control of ietf definition;

Fig. 2 is the function structure schematic diagram that has the IPTV business that realizes based on IMS now of ETSI TISPAN definition;

Fig. 3 is the schematic flow sheet of the embodiment of the invention one;

Fig. 4 is the schematic flow sheet of the embodiment of the invention two;

Fig. 5 is the schematic flow sheet of the embodiment of the invention three;

Fig. 6 is the schematic flow sheet of the embodiment of the invention four;

Fig. 7 is the schematic flow sheet of the embodiment of the invention five;

Fig. 8 is the system schematic of the embodiment of the invention;

Fig. 9 is the client terminal structure schematic diagram of the embodiment of the invention;

Figure 10 is that the recorded label of the embodiment of the invention provides the entity structure schematic diagram.

Embodiment

In the embodiment of the invention, client is by providing entity interaction to obtain recorded label with recorded label, and concrete grammar is as follows:

Client sends first message to recorded label entity is provided;

Client receives recorded label second message of entity according to this first message sends is provided, and carries recorded label in this second message;

Client is obtained recorded label from this second message.

Wherein, client can be user terminal (User Equipment:UE), also can be network entity.Under recording function and the professional situation that provides entity to close to establish, UE obtains recorded label by the method that the embodiment of the invention is described, and plays the media content of wanting according to recorded label and the professional entity interaction that provides then; In another case, recording function and business provide entity separation, business provides entity to adopt the method for the embodiment of the invention to obtain recorded label to the entity with recording function as client representative of consumer terminal, and business provides entity that recorded label is passed to UE then.And this just professionally provides entity to obtain a kind of situation of recorded label as a network entity, also can exist other network entity (as application server (AS:Application Server) etc.) to obtain the situation of recorded label, as: have some and record related service (as the NPVR business) etc., do not enumerate one by one at this.

After client was obtained recorded label, client can provide entity to begin the media content that playback is recorded from the recorded label appointment by requested service.

The embodiment of the invention is an example with the function structure that has the IPTV business that realizes based on IMS now of ETSI TISPAN definition, can also be applied under other similar IPTV function structures.

For the purpose, technical scheme and the advantage that make the embodiment of the invention is clearer, the embodiment of the invention is described in further detail below in conjunction with accompanying drawing.

The method flow of the specific embodiment of the invention one as shown in Figure 3.

In the present embodiment, it is Service Control Function that recorded label provides entity; Use SIP REFER method to trigger SCF and send recorded label to client.In the method for present embodiment, client sends REFER message to SCF; After SCF receives this REFER message, send PUBLISH or MESSAGE message or INFO, carry recorded label by above-mentioned message and return to client to client.Idiographic flow is described below:

Step 301～302: client sends REFER message, and this REFER message is routed to SCF through Core IMS;

In this REFER message, carried the address and the playback recording medium sign of client in the refer-to header field; The value of method parameter is PUBLISH;

Provide the example of REFER message below, only provide crucial header field here, recordid parameter is wherein carried playback recording medium sign:

REFER?sip:scf@example.com?SIP/2.0

Refer-to:

<sip:ue@example.com>；recordid＝fejiw12d@scf.example.com；method＝PUBLISH

Refer-Sub:false

Step 303～304:SCF returns the 200OK response message, is routed to client through Core IMS;

Step 305～306:SCF sends PUBLISH to client, and this PUBLISH is routed to client through Core IMS; In this PUBLISH, carry recorded label;

Provide the PUBLISH example of carrying recorded label below, only provide crucial header field here:

PUBLISH?sip:ue@example.com?SIP/2.0

Event:bookmark

Content-type:application/bookmark+xml

Content-Length:...

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<bookmark?xmlns＝＂urn:ietf:params:xml:ns:bookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<item>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</item>

<item>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</item>

</bookmark>

In above-mentioned XML script, one＜item〉represent a label, label to represent also available relative time with absolute time.The form of expression of label is varied, only is an example herein.

Step 307～308: client receives PUBLISH, returns the 200OK response message.

The method flow of the specific embodiment of the invention two as shown in Figure 4.

In the present embodiment, it is media control function (MCF) that recorded label provides entity.In the method for present embodiment, client is sent conversation message to SCF, by media negotiation, sets up the media session and the RTSP control channel of playback recording medium; SCF is handed down to MCF with the label of recording medium; Client is obtained label by the RTSP order.Idiographic flow is described below:

Step 401: client is initiated the operation of playback recording medium, carries out media negotiation by SCF and MCF, set up media session with RTSP control channel;

Step 402:SCF is handed down to MCF with the label of playback media; Concrete form, can by with the label band in setting up the INVITE of media session, be handed down to MCF, perhaps be handed down to MCF by the medium control messages;

Step 403: after media session is consulted successfully, set up RTSP control channel between client and MCF; Client sends RTSP control command GET_PARAMETER to MCF, to obtain label;

Provide the example of GET_PARAMETER order below, only provide crucial header field here:

GET_PARAMETER?rtsp://example.com/record/foo?RTSP/1.0

CSeq:11

Content-Type:application/bookmark+xml

Session:12345678

Step 404:MCF returns RTSP success response message (being the 200OK response message), carries recorded label in this response message;

Provide the example of response message below, only provide crucial header field here:

RTSP/1.0200?OK

CSeq:11

Content-Type:application/bookmark+xml

Session:12345678

Content-Length:...

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<bookmark?xmlns＝＂urn:ietf:params:xml:ns:bookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<item>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</item>

<item>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</item>

<item>

2005-08-15T10:23:30.000-05:00 /*bookmark3*/

</item>

</bookmark>

Step 405: client is selected the start-tag of one of them recorded label as original position from the recorded label that step 404 obtains, can also further from the recorded label that step 404 obtains, select the end-tag (in actual applications, can not select set end position) of one of them recorded label as end position; Client sends RTSP control command SET_PARAMETER or PLAY to MCF, wherein carry the start position information of media play in the start-tag of front or the start-tag, can also carry the end position information of media play in end-tag or the end-tag.Client is ordered by SET_PARAMETER, and the original position (end position can also further be set) of media play is set; Client begins to play the medium of appointment by PLAY command request MCF according to original position (can further include end position) then.Client also can be directly by the PLAY order, the original position (end position can also further be set) of in the Range header field, carrying playing media, and request MCF begins to play the medium of appointment according to original position (can further include end position).

Provide the example of SET_PARAMETER order below, only provide crucial header field here:

SET_PARAMETER?rtsp://example.com/record/foo?RTSP/1.0

CSeq:12

Content-Type:application/setbookmark+xml

Session:12345678

Content-Length:...

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<setbookmark?xmlns＝＂urn:ietf:params:xml:ns:setbookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<Start>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</Start>

<End>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</End>

</setbookmark>

Annotate: among the SET_PARAMETER,＜Start the expression position that begins to play,＜End〉the expression position that stops to play, and＜End〉can omit, have only＜Start, stop to play and control in real time by terminal.

Given below is the example of PLAY order, only provides crucial header field here:

GET_PARAMETER?rtsp://example.com/record/foo?RTSP/1.0

CSeq:12

Session:12345678

Range:10:22:20-/* begins to play from the time location of bookmark1, do not specify stop play position */

Step 406:MCF begins playing media, returns the 200OK response message to client.

Above example, simple in order to describe, the recorded label that carries has only comprised the temporal information (temporal information also may be a time migration information in the practical application certainly, document misregistration information etc.) of describing medium position; And recorded label other service related information that can also comprise label as: the sign of the sign of label, recording medium content, media content are simply described or related service information such as label owner, and be can not one complete at one stroke.And label adopts in this example is the describing mode of XML, can certainly adopt other describing mode, is the parametric description mode of text/parameters as Content-type, just be not repeated in this description at this.

The method flow of the specific embodiment of the invention three as shown in Figure 5.

In the present embodiment, it is Service Control Function that recorded label provides entity; Use the sip subscribe mode to obtain recorded label.In the method for present embodiment, client is subscribed to the incident bag that comprises recorded label to SCF.Idiographic flow is described below:

Step 501～502: client is sent SUBSCRIBE message to SCF, and this SUBSCRIBE message is routed to SCF through Core IMS; In this SUBSCRIBE message, the value of Request-URI is a playback recording medium resource;

Provide the example of SUBSCRIBE message below, only provide crucial header field here:

SUBSCRIBE?sip:fejiw12d@scf.example.com?SIP/2.0

Expires:0

Event:bookmark

Contact:sip:user@ue.example.com

Above-mentioned subscription can be adopted the Fetch mode, and the value that is about to the Expires header field is made as 0, uses this kind mode, and SCF can only send a recorded label to client, avoids follow-up repeating to send.

Step 503～504:SCF receives SUBSCRIBE message, returns the response message of 200OK, is routed to client through Core IMS;

Step 505～506:SCF sends NOTIFY to client and carries the recorded label of subscribing to recording medium; Provide the example of NOTIFY below, only provide crucial header field here:

NOTIFY?sip:user@ue.example.com?SIP/2.0

Event:bookmark

Subscription-State:terminated

Content-Type:application/bookmark+xml

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<bookmark?xmlns＝＂urn:ietf:params:xml:ns:bookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<item>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</item>

<item>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</item>

</bookmark>

Step 507～508: client receives NOTIFY, returns the response message of 200OK;

The method flow of the specific embodiment of the invention four as shown in Figure 6.

In the present embodiment, it is service selection capability (SSF) that recorded label provides entity.In the method for present embodiment, client is obtained the recorded label of specifying recording medium by the GET method of http protocol to SSF; Client obtains the filename and the path of label file on SSF in advance, preserved in this label file recording medium recorded label (such as can by in the service discovering process, obtain in the filename of label file on the SSF and path or on SSF the filename of label file and path static configuration in client).Idiographic flow is described below:

Step 601: client is obtained user's configuration data, and this configuration data comprises the position (can be to be kept at filename and the path that SSF goes up label file in this embodiment, also be on other network element device certainly) that the recorded label of recording medium is preserved;

Step 602: client sends HTTP GET message to SSF, and acquisition request is specified the recorded label of recording medium; Provide the example of GET message below:

GET?http://ssf.example.com/record/fejiw12d@scf.example.com.xml?http/1.1

Step 603:SSF returns the response message of 200OK to client, carries the recorded label of recording medium in this response message; Provide the example of 200OK message below, only provide crucial header field here:

HTTP/1.1?200OK

Content-Type:application/bookmark+xml

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<bookmark?xmlns＝＂urn:ietf:params:xml:ns:bookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<item>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</item>

<item>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</item>

</bookmark>

The method flow of the specific embodiment of the invention five as shown in Figure 7.

In the present embodiment, it is Service Control Function that recorded label provides entity.In the method for present embodiment, to set up alternately in the process of media session in client and SCF, the 200OK response message of SCF by the INVITE correspondence sends to client with the recorded label of recording medium.Idiographic flow is described below:

Step 701～702: client sends INVITE to SCF and is used to set up media session, and this INVITE is routed to SCF through Core IMS;

Client and SCF consult to set up the media session of playback recording medium, and in this INVITE, the value of Request-URI is the recording medium resource address; The Accept-Contact header field then can carry recoding service sign npvr;

Step 703～704:SCF receives the INVITE request, by the 200OK response message label of recording medium is taken back to client;

Provide the example of 200OK message below, only provide crucial header field here:

SIP/2.0200?OK

Content-Type:application/bookmark+xml

<？xml?version＝＂1.0＂encoding＝＂UTF-8＂？>

<bookmark?xmlns＝＂urn:ietf:params:xml:ns:bookmark＂

xmlns:xsi＝＂http://www.w3.org/2001/XMLSchema-instance＂>

<item>

2005-08-15T10:22:00.000-05:00 /*bookmark1*/

</item>

<item>

2005-08-15T10:22:20.000-05:00 /*bookmark2*/

</item>

</bookmark>

Step 705～706: return ACK behind the client reception 200OK response message and confirm message to SCF;

Show as Fig. 8, be the system configuration schematic diagram of the embodiment of the invention.Comprise in this system: client 801 and recorded label provide entity 802;

Recorded label provides entity 802 to be used to receive first message that client 801 sends;

Client 801 is used to receive second message of carrying recorded label that recorded label provides entity 802 to send, and obtains recorded label from second message.

It can be Service Control Function that recorded label provides entity 802, and first message can be SIP REFER message, and second message can be PUBLISH or MESSAGE message or INFO; Can use SIP REFER method to trigger SCF under this kind situation and send recorded label to client; Client sends REFER message to SCF; After SCF receives this REFER message, send PUBLISH or MESSAGE message or INFO, carry recorded label by above-mentioned message and return to client to client;

It can be media control function (MCF) that recorded label provides entity 802, and first message can be the GET_PARAMETER order, and second message can be RTSP success response message; Under this kind situation, client is sent conversation message to SCF, by media negotiation, sets up the media session and the RTSP control channel of playback recording medium; SCF is handed down to MCF with the label of recording medium; Client is obtained label by the RTSP order; Client can also be selected start-tag from recorded label.Further, client can send SET_PARAMETER and order to MCF, and this SET_PARAMETER order SET_PARAMETER order comprises start-tag, and this start-tag is used to be provided with the original position of media play; Client transmission PLAY orders to MCF then, and MCF is according to the original position playing media in request; Perhaps client can also send PLAY and orders to MCF, comprises the original position of the playing media in the start-tag in the PLAY order, and MCF is according to the original position playing media in request.Need to prove, in SET_PARAMETER or PLAY order, can also comprise end-tag, be used for determining the end position of playing media, similar in concrete method of carrying and the specific embodiment two.

It can be Service Control Function that recorded label provides entity 802, and first message can be SUBSCRIBE message, and second message can be NOTIFY; Use the sip subscribe mode to obtain recorded label under this kind situation; Client is subscribed to the incident bag (this subscription can be adopted the Fetch mode, and the value that is about to the Expires header field is made as 0) that comprises label to SCF;

It can be service selection capability (SSF) that recorded label provides entity 802, and first message can be HTTP GET message, and second message can be success response message (as 200OK); Under this kind situation, client is obtained the recorded label of specifying recording medium by the GET method of http protocol to SSF; Client obtained in advance the position that recorded label that SSF goes up recording medium preserves (such as by in the service discovering process or static configuration in client), the label file name is identical with the media file name of recording;

It can be Service Control Function that recorded label provides entity 802, and first message can be INVITE, and second message can be success response message; Under this kind situation, set up alternately in the process of media session in client and SCF, the 200OK response message of SCF by the INVITE correspondence sends to client with the recorded label of recording medium.

As shown in Figure 9, the client terminal structure schematic diagram for the embodiment of the invention comprises:

Sending module 901, being used to send first message to recorded label provides entity;

Receiver module 902 is used to receive second message that recorded label provides entity, carries recorded label in second message;

Recorded label acquisition module 903, recorded label acquisition module are used for obtaining recorded label from second message.

It can be Service Control Function that recorded label provides entity, and first message can be SIPREFER message, and second message can be PUBLISH or MESSAGE message or INFO; Use SIP REFER method to trigger SCF under this kind situation and send recorded label to client; Client sends REFER message to SCF; After SCF receives this REFER message, send PUBLISH or MESSAGE message or INFO, carry recorded label by above-mentioned message and return to client to client;

It can be media control function (MCF) that recorded label provides entity, and first message can be the RTSP order, and second message can be RTSP command response message; Under this kind situation, client can also comprise negotiation module, be used for by with service control function SCF media negotiation, set up the RTSP control channel of playback recording medium with MCF; SCF is handed down to MCF with the label of recording medium; Client is obtained label by the RTSP order; Client can also comprise start-tag selection module, is used for selecting start-tag from above-mentioned recorded label;

Further, client can also comprise that media play is provided with module, being used to send SET_PARAMETER orders to MCF, this SET_PARAMETER comprises start-tag, this start-tag is used to be provided with the original position of media play, client can also comprise the media play request module under this kind situation, is used to send PLAY and orders to MCF, and MCF is according to the original position playing media in request;

Perhaps client can also comprise the media play module, is used to send PLAY and orders to MCF, comprises the original position of the playing media in the start-tag in the PLAY order, and MCF is according to the original position playing media in request.

Need to prove, in SET_PARAMETER or PLAY order, can also comprise end-tag, be used for determining the end position of playing media, similar in concrete method of carrying and the specific embodiment two.

It can be Service Control Function that recorded label provides entity, and first message can be SUBSCRIBE message, and second message can be NOTIFY; Use the sip subscribe mode to obtain recorded label under this kind situation; Client is subscribed to the incident bag (this subscription can be adopted the Fetch mode, and the value that is about to the Expires header field is made as 0) that comprises label to SCF;

It can be service selection capability (SSF) that recorded label provides entity, and first message can be HTTPGET message, and second message can be success response message; Under this kind situation, client can also comprise the configuration data acquisition module, is used to obtain configuration data; Determination module is used for determining that according to configuration data recorded label is kept at service selection capability SSF; Client is obtained the recorded label of specifying recording medium by the GET method of http protocol to SSF; Client obtained in advance the position that recorded label that SSF goes up recording medium preserves (such as by in the service discovering process or static configuration in client);

It can be Service Control Function that recorded label provides entity, and first message can be INVITE, and second message can be success response message; Under this kind situation, client also comprises sets up module, is used for consulting to set up with service control function SCF the media session of playback recording medium; Set up alternately in the process of media session in client and SCF, the 200OK response message of SCF by the INVITE correspondence sends to client with the recorded label of recording medium;

Above-mentioned client can be user terminal or network entity.

As shown in figure 10, for the recorded label of the embodiment of the invention provides the entity structure schematic diagram, comprising:

Receiver module 1001 is used to receive first message that client sends;

Sending module 1002 is used to send second message to client, carries recorded label in second message.

It can be Service Control Function that recorded label provides entity 802, and first message can be SIP REFER message, and second message can be PUBLISH or MESSAGE message or INFO; Use SIP REFER method to trigger SCF under this kind situation and send recorded label to client; Client sends REFER message to SCF; After SCF receives this REFER message, send PUBLISH or MESSAGE message or INFO, carry recorded label by above-mentioned message and return to client to client;

It can be media control function (MCF) that recorded label provides entity, and first message can be the RTSP order, and second message can be RTSP command response message; Under this kind situation, recorded label provides entity can also comprise the recorded label acquisition module, is used to receive the recorded label that service control function SCF issues; Client is obtained label by the RTSP order.

It can be service selection capability (SSF) that recorded label provides entity 802, and first message can be HTTP GET message, and second message can be success response message; Under this kind situation, client is obtained the recorded label of specifying recording medium by the GET method of http protocol to SSF; Client obtained in advance the position that recorded label that SSF goes up recording medium preserves (such as by in the service discovering process or static configuration in client);

It can be Service Control Function that recorded label provides entity 802, and first message can be INVITE, and second message can be success response message; Under this kind situation, recorded label provides entity can also comprise negotiation module, is used for setting up with the client negotiation media session of playback recording medium; Set up alternately in the process of media session in client and SCF, the 200OK response message of SCF by the INVITE correspondence sends to client with the recorded label of recording medium;

Though pass through with reference to some of the preferred embodiment of the invention, the present invention is illustrated and describes, but those of ordinary skill in the art should be understood that and can do various changes to it in the form and details, and without departing from the spirit and scope of the present invention.

Claims

1. the acquisition methods of recorded label in the IPTV system is characterized in that described method comprises:

Client sends first message to recorded label entity is provided, and described first message is used for the acquisition request recorded label;

2. the method for claim 1 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SIP REFER message, and described second message is PUBLISH or MESSAGE message or INFO.

3. the method for claim 1 is characterized in that, it is media control function MCF that described recorded label provides entity, and described first message is RTSP GET_PARAMETER order, and described second message is RTSP success response message, and described method also comprises:

Described client by with service control function SCF media negotiation, set up the RTSP control channel of playback recording medium with described MCF.

4. method as claimed in claim 3 is characterized in that described recorded label is issued to described MCF by described SCF.

5. method as claimed in claim 3 is characterized in that, described method also comprises:

Described client is selected start-tag from described recorded label;

Described client sends RTSP SET_PARAMETER order to described MCF, and described RTSPSET_PARAMETER order comprises described start-tag, and described start-tag is used to be provided with the original position of media play;

Described client sends RTSP PLAY order to described MCF, asks described MCF according to described original position playing media.

6. method as claimed in claim 3 is characterized in that, described method also comprises:

Described client is selected start-tag from described recorded label;

Described client sends RTSP PLAY order to described MCF, comprises the original position of the playing media in the described start-tag in the described RTSP PLAY order, and described RTSP PLAY order is used to ask described MCF according to described original position playing media.

7. the method for claim 1 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SUBSCRIBE message, is used to subscribe to the incident bag that comprises recorded label; Described second message is NOTIFY.

8. method as claimed in claim 7 is characterized in that, the value of Expires header field is made as 0 in the described SUBSCRIBE message.

9. the method for claim 1 is characterized in that, it is service selection capability SSF that described recorded label provides entity; Described first message is HTTP GET message, and described second message is success response message.

10. method as claimed in claim 9 is characterized in that, described method also comprises:

Described client is obtained configuration data;

Described client determines that according to described configuration data described recorded label is kept among the described SSF.

11. method as claimed in claim 10 is characterized in that, described configuration data be that client obtains in the service discovering process or static configuration in client.

12. the method for claim 1 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is INVITE, and described second message is success response message.

13. method as claimed in claim 12 is characterized in that, described INVITE is used for the media session that described client and SCF consult to set up the playback recording medium.

14. the client in the IPTV system, it is characterized in that: described client comprises:

Sending module, described sending module is used to send first message to recorded label provides entity, and described first message is used for the acquisition request recorded label;

15. client as claimed in claim 14 is characterized in that, described client also comprises:

Negotiation module, described negotiation module be used for by with service control function SCF media negotiation, set up the RTSP control channel of playback recording medium with described MCF.

16. client as claimed in claim 15 is characterized in that, described client also comprises:

Start-tag is selected module, and described start-tag selects module to be used for selecting start-tag from described recorded label;

Media play is provided with module, and described media play is provided with module and is used to send the RTSPSET_PARAMETER order to described MCF, and described RTSP SET_PARAMETER order comprises described start-tag, and described start-tag is used to be provided with the original position of media play;

Media play request module, described media play request module are used to send RTSP PLAY order to described MCF, ask described MCF according to described original position playing media;

17. client as claimed in claim 15 is characterized in that, described client also comprises:

The media play module, described media play module is used to send RTSP PLAY order to described MCF, the original position that comprises the playing media in the described start-tag in the described RTSP PLAY order, described RTSP PLAY order is used to ask described MCF according to described original position playing media.

18. client as claimed in claim 14 is characterized in that, described client also comprises:

The configuration data acquisition module, described configuration data acquisition module is used to obtain configuration data;

Determination module, described determination module are used for determining that according to described configuration data recorded label is kept at service selection capability SSF.

19. client as claimed in claim 14 is characterized in that, described client also comprises:

Set up module, describedly set up the media session that module is used for consulting to set up with service control function SCF the playback recording medium.

20., it is characterized in that described client is user terminal or network entity as each described client of claim 14 to 19.

21. the recorded label in the IPTV system provides entity, it is characterized in that described recorded label provides entity to comprise:

Receiver module is used to receive first message that client sends, and described first message is used for the acquisition request recorded label;

Sending module is used for sending second message to described client according to described first message, carries described recorded label in described second message.

22. recorded label as claimed in claim 21 provides entity, it is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SIP REFER message, and described second message is PUBLISH or MESSAGE message or INFO.

23. recorded label as claimed in claim 21 provides entity, it is characterized in that, it is media control function MCF that described recorded label provides entity, and described recorded label provides entity also to comprise:

The recorded label acquisition module, described recorded label acquisition module is used to receive the recorded label that service control function SCF issues.

24. recorded label as claimed in claim 21 provides entity, it is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SUBSCRIBE message, is used to subscribe to the incident bag that comprises recorded label; Described second message is NOTIFY.

25. recorded label as claimed in claim 21 provides entity, it is characterized in that, it is service selection capability SSF that described recorded label provides entity; Described first message is HTTP GET message, and second message is success response message.

26. recorded label as claimed in claim 21 provides entity, it is characterized in that, it is service control function SCF that described recorded label provides entity, and described recorded label provides entity also to comprise:

Negotiation module, described negotiation module are used for setting up with described client negotiation the media session of playback recording medium.

27. the system that obtains of recorded label in the IPTV system, it is characterized in that described system comprises: client and recorded label provide entity;

Described recorded label provides entity to be used to receive first message that described client sends, and described first message is used for the acquisition request recorded label;

Described client is used to receive described recorded label provides entity to send second message according to described first message, and described second message is carried described recorded label; Described client also is used for obtaining described recorded label from described second message.

28. system as claimed in claim 27 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SIP REFER message, and described second message is PUBLISH or MESSAGE message or INFO.

29. system as claimed in claim 27, it is characterized in that, it is media control function MCF that described recorded label provides entity, described client also be used for by with service control function SCF media negotiation, set up the RTSP control channel of playback recording medium with described MCF.

30. system as claimed in claim 27 is characterized in that, described system also comprises SCF, and described SCF is used to issue recorded label to described MCF.

31. system as claimed in claim 29 is characterized in that,

Described client also is used for selecting start-tag from described recorded label, and send the RTSPSET_PARAMETER order to described MCF, described RTSP SET_PARAMETER order comprises described start-tag, and described start-tag is used to be provided with the original position of media play;

Described client also is used to send RTSP PLAY order to described MCF, asks described MCF according to described original position playing media;

32. method as claimed in claim 29 is characterized in that, described method also comprises:

Described client also is used for selecting start-tag from described recorded label, and send the RTSPPLAY order to described MCF, the original position that comprises the playing media in the described start-tag in the described RTSP PLAY order, described RTSP PLAY order is used to ask described MCF according to described original position playing media.

33. system as claimed in claim 27 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is SUBSCRIBE message, is used to subscribe to the incident bag that comprises recorded label; Described second message is NOTIFY.

34. system as claimed in claim 27 is characterized in that, it is service selection capability SSF that described recorded label provides entity, and described client also is used to obtain configuration data, and determines that according to described configuration data described recorded label is kept among the described SSF.

35 systems as claimed in claim 27 is characterized in that, it is service control function SCF that described recorded label provides entity; Described first message is INVITE, and second message is success response message.