CN101378546A

CN101378546A - Method, entity and system for implementing medium consignation control

Info

Publication number: CN101378546A
Application number: CN 200710148416
Authority: CN
Inventors: 严军; 漆宝剑; 王随海; 王鹏; 吴向阳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-08-28
Filing date: 2007-08-28
Publication date: 2009-03-04
Also published as: WO2009026810A1

Abstract

The invention discloses a media delivery controlling method, and an entity and a system thereof. The proposal of the media delivery controlling method chooses a media-delivery functional entity capable of providing media stream for a user by obtaining and according to the media resource information of the media-delivery functional entity; and by the RTSP (real time streaming protocol) conversation with the media-delivery functional entity, the media-delivery functional entity is controlled to conduct media delivery, and a specific way for an MCF (media control functional) entity to control media delivery of an MDF (media delivery functional) entity is provided, thereby meeting the needs of an interface between the MCF entity and the MDF entity for supporting media resource management function and media stream control function.

Description

Method, entity and system for realizing media delivery control

Technical Field

The present invention relates to the field of communications, and in particular, to techniques for implementing media delivery control.

Background

The streaming media service or IPTV (IP TeleVision) service is a new service rapidly developed in recent years, and the streaming media service uses a streaming transmission technology to transmit multimedia files, including file contents such as video and audio, over a packet-switched network. These contents can be played immediately upon access without a full download. The key technology for realizing the streaming media service is streaming transmission technology, and the streaming transmission technology is network transmission technology which processes continuous video and audio information and then puts the processed continuous video and audio information on a website server, so that a user can download and listen to the processed continuous video and audio information at the same time without waiting for the whole file to be downloaded to a machine of the user to watch the processed continuous video and audio information.

IMS (IP Multimedia Subsystem) is a Subsystem for providing Multimedia services proposed by 3GPP R5, belonging to an upper control Subsystem, independent of the specific access technology. The system comprises a SCF (Session Control Function), an MGCF (Media gateway Control Function), an MRFP (Media Resource Function processor) and other functional entities, and mainly adopts SIP (Session initiation protocol) and Diameter protocol to realize registration, authentication, routing, Session Control and establishment, Service triggering, charging, end-to-end QoS (Quality of Service) guarantee and other Session mechanisms.

The IMS based IPTV system provides IPTV service based on IMS structure, and provides multimedia service of streaming media service, merging streaming media and real-time session service for users by fully utilizing the existing session control mechanism in IMS network. That is, the multimedia session from the user to the content is completed through the existing session control mechanism of the IMS, and during the session establishment, bearer resources need to be reserved for the transmission of the media stream.

The functional architecture of the IMS based IPTV system is shown in fig. 1, and includes a terminal device (UE), an IPTV media function (IPTV media functions) module, and the like, in addition to the IMS system.

The terminal device is used for receiving the media stream and performing remote play control on the media stream, such as requesting play/pause, fast forward and fast backward.

The IPTV media function module is responsible for controlling and delivering (Delivery) a media stream to the terminal device. At present, from a functional perspective, the IPTV Media Function module is decomposed into an MCF (Media control Function) entity and an MDF (Media Delivery Function) entity, where the MCF entity is defined to be responsible for functions such as session control, Media play control, Media resource management, and charging; and defining the functions of the MDF entity in charge of the transmission of the media stream, the report of the media resources and the like.

As can be seen from the functions of the MCF entity and the MDF entity defined in the prior art, an interface reference point between the MCF entity and the MDF entity, denoted as Xp, needs to support controlling establishment of a media delivery session and instructing one or more MDF to deliver content to a terminal, which requires that an Xp interface has a media resource management function and a media flow control function. However, the prior art does not provide a specific way for the MCF entity to control the media delivery of the MDF entity, and cannot meet the requirement that the interface between the MCF entity and the MDF entity supports the media resource management function and the media flow control function.

Disclosure of Invention

The invention provides a method, an entity and a system for realizing media delivery control, and the method provides a specific implementation scheme that an MCF entity controls media delivery of an MDF entity.

The invention is realized by the technical scheme provided by the following embodiment:

the embodiment of the invention provides a method for realizing media delivery control, which comprises the following steps:

acquiring media resource information of a media delivery functional entity;

selecting a media delivery functional entity capable of providing media contents required by a user according to the media resource information of the media delivery functional entity;

and controlling the media delivery behavior of the media delivery functional entity through a real-time streaming protocol (RTSP) session with the media delivery functional entity.

An embodiment of the present invention further provides a media control function entity, which includes:

the resource management unit is used for acquiring the media resource information of the media delivery functional entity;

a session initiation protocol SIP session control function unit used for selecting a media delivery function entity capable of providing the media content required by the user according to the media resource information of the media delivery function entity;

and the real-time streaming protocol RTSP session control function unit is used for controlling the media delivery behavior of the media delivery function entity through the RTSP session between the RTSP session control function unit and the media delivery function entity selected by the SIP session control function unit.

The embodiment of the invention also provides a method for realizing media delivery control, which comprises the following steps:

receiving a media control request of a media control function entity through a real-time streaming protocol (RTSP) session between the media control function entity and the RTSP; and controlling media delivery behavior according to the media control request.

The embodiment of the present invention further provides a media delivery function entity, which includes:

a real-time streaming protocol RTSP session control function unit, which is used for receiving the media control request of the media control function entity through the RTSP session with the media control function entity; controlling the media delivery behavior of a media delivery unit according to the media control request;

and the media delivery unit selects corresponding media contents to deliver to the user according to the control of the RTSP conversation control function unit.

An embodiment of the present invention further provides a media delivery control system, where the media delivery control system includes:

the media control function entity is used for acquiring the media resource information of the media delivery function entity; selecting a media delivery functional entity capable of providing media contents required by a user according to the media resource information of the media delivery functional entity; sending a media control request through a real-time streaming protocol (RTSP) session between the media delivery function entity and the media delivery function entity;

the media delivery function entity is used for receiving the media control request of the media control function entity through the RTSP conversation with the media control function entity; and controlling media delivery behavior according to the media control request.

As can be seen from the specific implementation of the embodiment of the present invention, in the scheme, by acquiring the media resource information of the MDF entity, the MDF entity capable of providing the media content to the user is selected according to the media resource information of the MDF entity; the media delivery behavior of the MDF entity is controlled through the RTSP conversation with the MDF entity, and a specific way for the MCF entity to control the media delivery of the MDF entity is provided, so that the requirements of an interface between the MCF entity and the MDF entity for supporting a media resource management function and a media flow control function are met.

Drawings

Fig. 1 is a functional architecture of an IMS based IPTV system provided in the prior art;

fig. 2 is a block diagram of a media delivery control system according to a first embodiment of the present invention;

fig. 3 is a block diagram of a media control function entity in a first embodiment of the present invention;

fig. 4 is a block diagram of a media delivery function according to a first embodiment of the present invention;

FIG. 5 is a general flow chart of a business process according to a second embodiment of the present invention;

fig. 6 is a flowchart of a session initiation procedure of an IPTV service in a second embodiment of the present invention;

fig. 7 is a flowchart of a terminal triggered session modification procedure in a second embodiment of the present invention;

fig. 8 is a flowchart illustrating an implementation of a session modification process triggered by an MDF on a network side according to service requirements in a second embodiment of the present invention;

fig. 9 is a flowchart of a process of notifying the UE to initiate session modification to the network side after media modification is performed through MCF decision when the MDF on the network side needs to perform media modification in the second embodiment of the present invention;

fig. 10 is a flowchart of a terminal triggered session release procedure in a second embodiment of the present invention;

fig. 11 is a flowchart of a network-side SCF triggered session release procedure in a second embodiment of the present invention;

fig. 12 is a flowchart of a session release triggering process of a network-side MCF in the second embodiment of the present invention;

fig. 13 is a flowchart of establishing and terminating an RTSP session by using SDP offer/Answer in the h.248 protocol in the second embodiment of the present invention;

fig. 14 is a flow chart of the implementation of the fourth embodiment of the present invention.

Detailed Description

A first embodiment of the present invention provides a media delivery control system, as shown in fig. 2, comprising a CoreIMS (IP multimedia subsystem center), an MCF entity and an MDF entity.

The Core IMS, the function of which is similar to the existing 3GPP technology, is used for providing authentication, authorization and session control functions for the UE according to the IPTV service request of the UE, routing the service request to the SCF entity in the Core IMS according to the user subscription information, and triggering the corresponding service processing logic by the SCF entity.

The MCF entity is used for acquiring media content required by a user from a service request according to the triggered service processing logic, and selecting the MDF with the media content required by the user according to the media content and media resource information of the MDF entity acquired based on an H.248 media gateway control protocol; informing the selected MDF of the address of the UE and informing the UE of the address of the selected MDF; and controlling the media delivery behavior of the MDF entity through the RTSP session from the MCF entity to the MDF entity.

Under the condition that the RTSP session between the MCF entity and the MDF entity does not exist, the MCF entity is also used for issuing a message carrying the description information of the real-time streaming session required for establishing the RTSP stream; and obtaining the ID (identification) of the RTSP session according to the response message returned by the media delivery functional entity, and establishing the RTSP session corresponding to the ID between the RTSP session and the media delivery functional entity.

The MDF entity is used for delivering the media stream to the corresponding UE based on the RTSP; based on H.248 protocol, reporting media resource information to MCF, and receiving media resource management of MCF; receiving a media control request of a media control function entity through an RTSP session with the media control function entity; and controls media delivery behavior and the like according to the media control request.

Under the condition that the RTSP session between the MCF entity and the MDF entity does not exist, the MDF entity is also used for returning the ID of the RTSP session between the MDF entity and the media control function entity based on the H.248 protocol or the SIP protocol after obtaining the description information of the real-time streaming session sent by the media control function entity, and the RTSP session corresponding to the ID is established between the MDF entity and the media control function entity.

The structure of the MCF entity is shown in fig. 3, and includes an SIP session control function unit, an RTSP session control function unit, a resource management function unit, and a media resource information storage unit.

The SIP session control function unit is used for completing the SIP service request (SIP INVITE) of the received SCF, establishing the SIP session and carrying out the media negotiation according to the request, and selecting a media delivery function entity capable of providing media content for a user according to the media resource information of the MDF; and informs the RTSP session control function unit of the selected media delivery function entity.

The RTSP conversation control function unit is used for controlling and managing the RTSP conversation, and comprises the steps of establishing the RTSP conversation between the MDF and the UE and controlling the media stream between the MDF and the UE; and controlling the media delivery behavior of the MDF according to the request of the user through the RTSP session between the MDF and the MCF.

Under the condition that the RTSP session between the MDF and the MCF does not exist, the RTSP session control function unit is also used for converting the obtained media description information into real-time streaming session description information based on an RTSP protocol; based on SIP protocol, sending the message carrying the description information of the real-time streaming session to a media delivery function entity; and according to the response fed back by the media delivery functional entity, obtaining the ID of the RTSP session between the media delivery functional entity and the RTSP session corresponding to the ID between the media delivery functional entity and the RTSP session. Or,

under the condition that the RTSP session between the MDF and the MCF does not exist, the RTSP session control function unit is further configured to send, to the media delivery function entity, the real-time streaming session description information required for establishing the RTSP streaming session through an SDP (Service Discovery Protocol) offer carried by an h.248 Protocol; and according to the feedback response message of the media delivery functional entity, obtaining the ID of the RTSP conversation between the media delivery functional entity and establishing the RTSP conversation corresponding to the ID between the media control functional entity and the media delivery functional entity.

And the resource management functional unit is responsible for acquiring the MDF media resource information based on the H.248 protocol. The media resource information includes media processing capability of the MDF (e.g., codec conversion capability), available media resource information (e.g., stored streaming media content information), load information of the MDF (e.g., MDF load percentage and storage space information), delivery status of the media content (e.g., play, pause and fast forward, etc.), and media usage information (e.g., traffic statistics), etc.

And the media resource information storage unit is responsible for storing media resource information, providing information storage, modification and deletion functions for the resource management function unit, providing an information inquiry function for the SIP session control function, the RTSP session control function and the resource management function, and receiving information update from the resource management function.

The structure of the MDF entity is shown in fig. 4, and includes a media resource information storage unit, a resource management function unit, a media delivery unit, and an RTSP session control function unit.

And the media resource information storage unit is responsible for storing the media resource information.

And the resource management functional unit is used for obtaining the media resource information from the resource information storage unit. And is also used for providing the media resource information of the media delivery function entity to the media delivery unit.

Media delivery unit, which is used to select the corresponding media content requested by UE according to the control of RTSP conversation control function unit, and deliver the media content to the user through Xc interface; and sending the media resource information such as the delivery state of the media content, the media processing capability, the media delivery address and the port to the media resource information storage unit.

The RTSP conversation control function unit is used for receiving a media control request of the MCF entity through an RTSP conversation with the MCF entity; controlling the media delivery behavior of a media delivery unit according to the media control request; the resource information storage unit is also used for inquiring media resource information such as media processing capacity, media delivery address and port and the like;

under the condition that the RTSP conversation between the MDF entity and the MCF entity does not exist, the RTSP conversation control function unit is also used for returning the identification of the RTSP conversation between the RTSP conversation control function unit and the media control function entity based on the H.248 protocol or the SIP protocol after obtaining the description information of the real-time streaming conversation sent by the MDF entity, and establishing the RTSP conversation corresponding to the identification between the MDF entity and the MCF entity.

The resource management functional unit may be further configured to provide media resource information of the media delivery functional entity to the media control functional entity based on the h.248 protocol.

A second embodiment of the present invention provides a method for controlling media delivery, which can be implemented based on the media delivery control system provided in the first embodiment, and the service process includes a media resource information reporting process, a MCF media resource information saving process, a session initiation process, a session modification process, a session release process, and a media delivery state reporting process. The specific flow is shown in fig. 5:

1. the media resource information reporting process:

after the MDF is started, the resource information is registered to the MCF, and the MCF adopts an H.248 protocol to complete the management of the media resources. This process is prior art and is not described further herein.

2. The MCF stores the media resource information, which belongs to the prior art and is not described in detail herein.

3. Session initiation process of IPTV service:

when a user requests a service (such as a COD service), the UE starts a session initiation process, establishes a session between the terminal and the network side, performs media negotiation to establish a content channel and/or a content control channel, and the MCF obtains media resource information of the MDF, where the media resource information includes media processing capability of the MDF (such as codec conversion capability), available resource information (such as stored streaming media content information), load information of the MDF (such as MDF load percentage and storage space information), delivery status of the media content (such as play, pause, fast forward, etc.), and media usage information (such as traffic statistics information), etc. The MCF selects the MDF providing the media resources according to the media resource information of each MDF, and carries out media negotiation of the control channel and/or the content channel according to the information. After the session is successfully established, the user views the program and controls the delivery of media content during the viewing process, such as pause, fast forward, fast rewind, and skip. When the delivered media content of the MDF has a state change, the MDF reports the media content state information to the MCF based on the H.248 protocol.

In the service process, the MDF needs to report media resource information such as a media content delivery state and media traffic to the MCF. The process may be implemented using the h.248 protocol.

4. Session modification process of IPTV service:

the session modification process is initiated by a terminal or a network (SCF/MCF), and includes adding new media content, modifying media parameter description (such as codec, media sending address and port information), deleting original media content, and the process is an optional process.

5. The session release process of the IPTV service is initiated by a terminal or a network (SCF/MCF) based on an SIP/RTSP protocol, and the MCF and the MDF complete the session release based on the RTSP protocol. In the service process, the MDF needs to report media resource information such as a media content delivery state and media traffic to the MCF based on the h.248 protocol.

In the following, an implementation flow of the session initiation procedure of the IPTV Service is illustrated, in this example, the UE has already obtained network parameters (media description information including COD content, RTSP Request-URI information, and the like) of the COD Service from an SSF (Service selection function) through an EPG (Electronic Program Guide ), and at this time, the session initiation procedure of the corresponding IPTV Service, as shown in fig. 6, includes:

step F1-F3, UE sends session initial request (SIP INVITE) to request COD service, wherein RTSP URI information of media content requested by UE is carried; the Core IMS routes the session initiation request to the SCF providing the COD services according to the specifications defined in the existing 3GPP IMS R7 version. The SCF selects an MCF capable of providing the media content, and then sends a session initial request to the selected MCF, wherein the selected MCF carries RTSP URI information of the media content requested by the UE.

Step F4, after receiving the session initiation request, the MCF selects the MDF providing the media resource according to the resource status information of each MDF. Based on SIP protocol, MCF sends description acquisition request (RTSP DESCRIBE) message to selected MDF, wherein RTSP URI information of media content requested by UE is carried in message.

Step F5, after receiving the description acquisition request (RTSP DESCRIBE) message from the MCF, the MDF returns the media description information of the media content corresponding to the RTSP URI based on the SIP protocol.

After the steps F4 to F5, the MCF may obtain the media description information. Besides, the MCF may also obtain the media description information from the Web Server that centrally stores the media description information, or the MCF itself may already store the relevant information such as the media description information, in which case steps F4 to F5 are optional.

Step F6, the MCF converts the acquired media description information into streaming media SETUP request information according to the acquired media description information and the conversion relationship between the SDP offer information of the session initial request and the RTSP SETUP information shown in table 1; based on the RTSP protocol, a streaming media establishment Request (RTSPSETUP) is sent to the MDF, and a Transport header field of a request message carries the transmission information of the UE. The transmission information comprises coding format, delivery mode, receiving address of UE and port information.

The conversion relationship between the SDP offer information and RTSP SETUP information of the session initiation request is shown in table 1:

TABLE 1

Serial number	SDP Offer of session initiation request	RTSP SETUP information
Serial number	SDP Offer of session initiation request	RTSP SETUP information	1	Media reception address (row C) and port (port information of row m) of the UE C-IN IP4126.16.64.4/127	Destination and Client _ Port parameters converted to Transport header fields, such as Transport.

	m＝audio 8000RTP/AVP 0	Destination＝126.16.64.4；client_port＝8000-8001
	m＝audio 8000RTP/AVP 0	Destination＝126.16.64.4；client_port＝8000-8001	2	Media description information, M line segment, M audio 8000RTP/AVP 0a recurvon ly	And converting into RTP/AVP parameters of a Transport header field. Such as Transport RTP/AVP; ...
3	RTSP content object information a fmtp rtsprequest-uri RTSP:// mcf/example	Converted into content identification information on the MDF. For example, SETUP RTSP:// mdf1/example/audio RTSP/1.0	2

For example:

SETUP rtsp://mdf1/example/audio RTSP/1.0

CSeq:2

Transport:RTP/AVP；unicast；destination＝126.16.64.4；client_port＝8000-8001

in step F7, the MDF returns a response message (RTSP200OK) to the MCF to establish the streaming media session, where the response message includes the media sending address and port information of the MDF and the SessionID information of the RTSP session. For example:

RTSP/1.0 200 OK

CSeq:2

Transport:RTP/AVP；unicast；source＝126.16.64.5；destination＝126.16.64.4；

client_port＝8000-8001；Server_port＝9000-9001；mode＝＂PLAY|PAUSE”

Session:10000000/*Session ID 1 is between MCF and MDF*/

step F8-F10, after receiving the response message, the MCF stores the RTSP Session information (Session ID), and then carries out Media negotiation according to the content of the response message to determine the final Media response (Media SDPANser). The MCF returns a session initial response message (183 or 200OK) to the SCF, the message containing media response information of the media negotiation, and bearer information of the control channel providing the content (i.e. the IP address and port of the MCF). The session initial response message is routed to the UE through the Core IMS; the UE saves the media negotiation information. And establishes a corresponding channel (e.g., TCP connection) to the MCF according to the control channel negotiation information. The Media SDP answer example is as follows:

v＝0

o＝mhandley 2890844526 2890842807 IN IP4 126.16.64.5

s＝SDP Seminar

i＝A Seminar on the session description protocol

u＝-

e＝-

c＝IN IP4 126.16.64.5/127

t＝2873397496 2873404696

m＝application 9 TCP/RTSP rtsp

a＝connection:new

a＝setup:passive

a＝rtspid m-stream:10

a＝control:rtsp://mcf/example

a＝control:rtsp://mcf/example/audio

a＝fmtp:rtsp version:1.0

a＝fmtp:rtsp h-accept-ranges:NPT

a＝fmtp:h-session:20000000 /*There are two separately RTSP sessions.SessionId 2 is notsame.Session2 is between UE and MCF*/

m＝audio 9000RTP/AVP 0

a＝Sendonly

a＝lable:10

step F11, the UE sends a request for playing streaming media to the MCF through the established content control channel, where the request for playing includes the session ID between the UE and the MCF and the position of starting playing, such as the following examples:

PLAY rtsp://mcf/example/audio RTSP/1.0

CSeq:2

Session:20000000 /*Session2 is between UE and MCF*/

Range:smpte＝0:10:00-

the play request may not include the Range parameter, and the network side (SCF/MGCF) determines the play start position. For example, the Session Initiation Request message sent by the SCF to the MGCF contains Range information.

Step F12, after receiving the play request of the UE, the MCF sends a play request of the streaming media to the MDF according to the request of the UE. The message includes the session ID and the media start playing position between the MCF and the MDF. Examples of messages are as follows:

PLAY rtsp://mdf1/example/audio RTSP/1.0

CSeq:2

Session:10000000/*Session ID 1 is between MCF and MDF*/

Range:smpte＝0:10:00-

step F13, after receiving the play request from the MCF, the MDF sends the media stream according to the request, and then returns a play response message to the MCF, where the message includes the session ID between the MCF and the MDF and the start play position of the media. Examples of messages are as follows:

RTSP/1.0 200 OK

CSeq:2

Session:10000000/*Session ID 1 is between MCF and MDF*/

Range:smpte＝0:10:00-

RTP-Info:url＝rtsp://mdf1/example/audio；seq＝876655；rtptime＝1032181

step F14, the MCF returns a play response message to the UE, where the message includes the session ID and the media start play position between the UE and the MCF. Examples of messages are as follows:

RTSP/1.0 200 OK

CSeq:2

Session:20000000 /*Session2 is between UE and MCF*/

Range:smpte＝0:10:00-

RTP-Info:url＝rtsp://mcf/example/audio；seq＝876655；rtptime＝1032181

step F15, the MDF sends the media stream according to the request.

Step F16, the MDF saves the delivery status of the streaming media and sends an h.248 NOTIFY message to the MCF, where the message contains the delivery status information of the current media (Playing in Playing).

The above-mentioned RTSP session establishment procedure of the Xp interface is also suitable for other unicast service flows, such as the TsTV service.

The session modification process of the IPTV service is described in several cases according to different entities triggering the session modification process:

in the first case, the terminal triggers the session modification procedure. The implementation flow is shown in fig. 7, and includes:

steps F1 to F3, the UE initiates a session change procedure, including adding media content, deleting media content and modifying media content (e.g. modifying media format or receiving address and port of the terminal) and holding (Hold) unicast media content, and the session change request includes a new media SDP Offer, compliant with the media modification mechanism defined by the RFC3264 protocol.

Step F4, after receiving the session change request, when the media content is to be added, the MCF sends a request for establishing streaming media (RTSP SETUP) to the MDF, where the message includes the session id (session identifier) of the original RTSP session. When the media content is requested to be deleted, the MCF sends a release request (RTSP teraflow) for specifying the media stream to the MDF, and the message includes the SessionID of the original RTSP session. If the media content is modified, the MCF sends a media stream establishment request (RTSP SETUP) to the MDF to modify the media transmission parameters, and the message contains the Session ID of the original RTSP session. But to maintain (Hold) the unicast media content, the MCF sends a PAUSE request (RTSP PAUSE) specifying the media stream to the MDF. Fig. 7 is an example of adding media content.

Step F5, taking the newly added media content as an example, after receiving the request for establishing the newly added media content, the MDF adds and sends the new media content to the UE according to the request.

The subsequent process is basically consistent with the session initial establishment process, and is not described herein again.

In the second case, the MDF on the network side triggers the session modification procedure according to the service requirements. Taking the example of adding a new media content, the implementation flow is shown in fig. 8, and includes:

step F1, the MDF providing the media content triggers the media modification process due to the service requirement, and the MDF sends an RTSP ANNOUNCE message to the MCF, where the message includes the new complete media description information.

Step F2, after receiving the MDF description notification message, the MCF compares the new complete media description information with the original media description information, and finds that media modification is needed, which is new media content in this example.

In step F3, the MCF sends an RTSP SETUP (real-time streaming protocol SETUP request) for the new media content to the MDF to request to SETUP a new media stream, where the message includes the transmission parameters of the existing UE side and the session ID of the original RTSP.

Step F4, after receiving the request for establishing the new media content, the MDF establishes the new media content, and then returns a setup response message (RTSP200OK) to the MCF.

Steps F5 to F10, the MCF initiates a session change procedure to the UE, and the procedure complies with the existing specification and is not described herein again.

Step F11, when the transmission parameter of the UE side changes, the MCF sends an RTSP SETUP message to the MDF to modify the transmission parameter of the UE side in the original session, where the message includes the session ID of the original RTSP and the new transmission parameter.

Step F12, the MDF modifies the saved UE side transmission parameters and returns a setup response message (RTSP200OK) to the MCF.

In steps F13-F14, the MCF sends a PLAY request (RTSP PLAY) of the new media content to the MDF. And after receiving the request, the MDF sends new media content to the UE according to the request.

In the third situation, when the MDF on the network side modifies the media according to the service requirement, the MCF sends an RTSP ANNOUNCE message to the UE through the media control channel after determining that the media modification is required according to the description notification sent by the MDF, and the UE initiates a session modification process to the network side after receiving the message. Taking the newly added media content as an example, the implementation flow is shown in fig. 9, and includes:

step F1, the MDF providing the media content triggers the media modification procedure due to the service requirement, and the MDF sends a description notification (RTSP ANNOUNCE) message to the MCF, where the message includes the new complete media description information.

Step F2, after receiving the MDF description notification message, the MCF compares the new complete media description information with the original media description information, and finds that media modification is needed, such as adding a new media stream. The MCF returns a description notification response (RTSP200OK) to the MDF.

And F3-F4, the MCF sends a description notification request (RTSP ANNOUNCE) to the UE, and the UE returns a description notification response message (RTSP200OK) to the MCF after receiving the message.

The subsequent processing is consistent with the session modification process started by the terminal, and is not described in detail herein.

The following describes the session release process of the IPTV service according to different entities triggering the session release process in several cases:

in the first case, the terminal triggers the session release procedure, as shown in fig. 10, which includes:

steps F1-F8, the UE initiates SIP BYE (session termination request) routing to MCF via Core IMS/SCF. After receiving the request, the MCF releases the SIP session and RTSP session with the UE, and then sends RTSP TEARDOWN (termination request) to the MDF, stopping the sending of the MDF media content.

In step F9, the MDF reports media delivery information to the MCF via h.248 NOTIFY, where the media delivery information includes delivery status (e.g., Stopped delivery) and media usage information (e.g., media traffic statistics) of the media content.

In the second case, the SCF at the network side triggers the session release procedure, as shown in fig. 11, which includes:

SCF sends session termination request, the session termination request reaches MCF entity, or reaches UE side through IMS Core;

the MCF entity sends a session termination request to the MDF entity; the transmission of the MDF media content is stopped. And returns a session termination response. In particular, similar to the above-mentioned description, it is not described in detail here.

And the UE side releases the corresponding session and feeds back a session termination response.

In the third case, the MCF on the network side triggers the session release process, as shown in fig. 12, including:

steps F1 to F2, after the MDF1 finishes playing the media Stream, the method described by draft-zeng-mm RTSP (draft-zeng-mm-00) may be used, but not limited to, to send an END _ Of _ Stream message to the MCF to notify the MCF that the media Stream is completely played.

Step F3-F10, after receiving the notice, the MCF starts the session release process, sends the session release request to the UE and sends the RTSP TEARDOWN (termination request) message to the MDF. The message carries a session ID, already transmitted media stream information, already transmitted number of RTP packets, and the like. Examples of messages are:

END_OF_STREAM rtsp://foo.com/bar.avi/streamid＝0RTSP/1.0

CSeq:123

session:12345678 (Session ID)

Range, npt ═ 0-200; bytes is 0-200000 (the server informs the client of the media stream information that has been sent)

RTP-Info, url// mdf/foo/streamid 0; 45102 (client knows the number of RTP packets the server has sent)

Reason:End of range reached

RTSP/1.0 200 OK

CSeq:123

Session:12345678

The above description is based on the SETUP and release RTSP session defined by RTSP protocol and the TEARDOWN message, and the control and release of real-time media stream are completed based on the RTSP session, but the embodiment of the present invention is not limited to this, and can also be implemented by the following method:

the method realizes the establishment of the RTSP conversation by adopting the way that the SDP offer/Answer of the H.248 protocol carries media parameters, and then carries out streaming media control based on the RTSP protocol. The sending port of the media stream is set to be 0 through SDP Offer or the sub-track defined by H.248 protocol to realize the termination of RTSP session. The basic implementation process is shown in fig. 13, and includes:

step F1, the MCF sends an h.248 ADD request to the MDF, where the request includes SDP offer, and the SDPoffer includes information needed to establish an RTSP stream, and the information includes information such as RTSP URI information of the media content, RTSP version information, and an association relationship between an RTSP session and the media stream.

Step F2, after receiving the request message, the MDF acquires the information needed to establish the RTSP stream, establishes an RTSP Session with the MCF according to the information, and returns an h.248reply response message, where the response message includes an SDP Answer that includes RTSP Session establishment response content, such as Session ID of the RTSP Session and RTP information of the media stream.

Step F3, after receiving the response message, the MCF sends an RTSP PLAY (real-time streaming PLAY) request to the MCF.

Step F4-F5, after receiving the request message, MDF returns RTSP200OK (response message), then sends media stream to UE.

In step F6, the MCF sends h.248sutract (terminate flow request) to the MDF.

Step F7, after the MDF receives the request, it releases the RTSP session and stops sending the media content.

A third embodiment of the present invention provides a media control function entity, and the structure, the units included in the structure, and the functions of each unit are the same as the MCF entity in the first embodiment, and will not be described in detail here.

In accordance with the third embodiment of the present invention, a fourth embodiment of the present invention provides a method for media delivery control, which is implemented as shown in fig. 14, and includes:

step 101, acquiring media resource information of an MDF entity;

the media resource information of the MDF entity may be acquired based on the h.248 media gateway control protocol.

102, selecting an MDF entity capable of providing media content for a user according to media resource information of the MDF entity;

and 103, controlling the media delivery behavior of the MDF through the real-time streaming protocol RTSP session with the MDF entity. Specifically, there may be the following three processing cases:

in the first case, the MDF entity is controlled to deliver the media contents requested by the user to the user through an RTSP session with the MDF entity.

In the second case, the MDF entity is controlled to perform media modification:

controlling the media delivery functional entity to modify the media through the RTSP session with the media delivery functional entity according to the session modification request of the user; or,

determining media modification according to a media description notification message sent by a media delivery function entity; indicating the media delivery functional entity to modify the media according to the determined media modification through the RTSP conversation with the media delivery functional entity; or,

determining that media modification is needed according to a media description notification message sent by a media delivery functional entity, and controlling the media delivery functional entity to modify media according to a session modification request initiated by description information corresponding to the determined media modification by a user side.

And in the third case, the MDF entity is controlled to release the media. The method comprises the following specific steps:

acquiring a media stream playing completion notification sent by a media delivery functional entity; informing the user side and the media delivery function entity to end the session according to the notification; or,

the method comprises the steps of obtaining a session termination request sent by a session control function SCF entity at a network side or a session termination request of a user forwarded by the SCF entity at the network side, and informing a media delivery function entity to end a session according to the session termination request.

The method also comprises the process of establishing the RTSP session between the MDF and the MCF under the condition that the RTSP session does not exist between the MDF and the MCF, and the method is concretely realized as follows:

issuing real-time streaming session description information required for establishing RTSP streaming; and obtaining the identification of the RTSP conversation according to the response message returned by the media delivery functional entity, and establishing the RTSP conversation corresponding to the ID between the media control functional entity and the media delivery functional entity.

The process of issuing the real-time streaming session description information required for establishing the RTSP stream can be implemented by the following two methods:

firstly, converting the obtained media description information into real-time streaming session description information based on RTSP; and sending the real-time streaming session description information to a media delivery function entity based on a Session Initiation Protocol (SIP).

And secondly, sending the real-time streaming session description information required by the RTSP stream establishment to the media delivery function entity through the H.248 protocol.

A fifth embodiment of the present invention provides a media delivery function entity, the structure, the units included in the structure, and the functions of each unit are the same as the MDF entity in the first embodiment described above, and will not be described in detail here.

Corresponding to the fifth embodiment of the present invention, the sixth embodiment of the present invention provides a method for implementing media delivery control, which receives a media control request of an MCF entity through an RTSP session with the MCF entity; and controlling media delivery behavior according to the media control request.

The sixth embodiment further includes a process of establishing an RTSP session between the MDF and the MCF, when the RTSP session does not exist between the MDF and the MCF, which is specifically implemented as follows:

after the real-time streaming session description information sent by the media control function entity is obtained, the identifier of the RTSP session between the media control function entity and the media delivery function entity is returned based on the H.248 protocol or the SIP protocol, and the RTSP session corresponding to the identifier is established between the media delivery function entity and the media control function entity.

In the sixth embodiment, the media resource information of the MDF entity may also be provided to the MCF entity. The media resource information of the media delivery function entity can be provided to the media control function entity based on the h.248 protocol.

It can be seen from the specific implementation of the embodiment of the present invention that, in the scheme, the media delivery functional entity capable of providing the media stream to the user is selected by acquiring the media resource information of the media delivery functional entity and according to the media resource information of the media delivery functional entity; the media delivery behavior of the media delivery functional entity is controlled through the RTSP conversation with the media delivery functional entity, and a specific way for the MCF entity to control the media delivery of the MDF entity is provided, so that the requirements of an interface between the MCF entity and the MDF entity for supporting a media resource management function and a media flow control function are met.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for implementing media delivery control, the method comprising:

acquiring media resource information of a media delivery functional entity;

and controlling the media delivery functional entity to carry out media delivery behavior through a real-time streaming protocol (RTSP) session between the media delivery functional entity and the media delivery functional entity.

2. The method of claim 1, wherein the media resource information of the media delivery function entity is obtained based on h.248 media gateway control protocol.

3. The method of claim 1 or 2, further comprising:

issuing real-time streaming session description information required for establishing RTSP streaming; and obtaining the identifier of the RTSP session according to the response message returned by the media delivery functional entity, and establishing the RTSP session corresponding to the identifier between the media control functional entity and the media delivery functional entity.

4. The method of claim 3, wherein said issuing RTSP-based real-time streaming session description information comprises:

acquiring media description information; converting the obtained media description information into real-time streaming session description information based on an RTSP (real time streaming protocol); sending the real-time streaming session description information to a media delivery function entity based on a Session Initiation Protocol (SIP); or,

and sending the real-time streaming session description information required by the RTSP to the media delivery function entity through the H.248 protocol.

5. The method of claim 1, wherein controlling the media delivery behavior of the media delivery function through the RTSP session with the media delivery function comprises:

and controlling the media delivery function entity to deliver the media content requested by the user to the user through the RTSP session with the media delivery function entity.

6. The method of claim 1, wherein controlling the media delivery behavior of the media delivery function through the RTSP session with the media delivery function comprises:

determining that media modification is needed according to a media description notification message sent by a media delivery functional entity, sending a description notification request to a user side according to the determined media modification, and controlling the media delivery functional entity to modify media according to a session modification request initiated by the user side according to the description notification request.

7. The method of claim 1, wherein controlling the media delivery behavior of the media delivery function through the RTSP session with the media delivery function comprises:

8. A media control function entity, comprising:

and the real-time streaming protocol RTSP session control function unit is used for controlling the media delivery function entity to carry out media delivery behavior through the RTSP session between the RTSP session control function unit and the media delivery function entity selected by the SIP session control function unit.

9. The media control function entity of claim 8, wherein the RTSP session control function unit is further configured to obtain media description information; converting the obtained media description information into real-time streaming session description information based on an RTSP (real time streaming protocol); sending the message carrying the real-time streaming session description information to a media delivery function entity based on an SIP protocol; and according to the response fed back by the media delivery functional entity, acquiring an identifier of the RTSP session between the media delivery functional entity and establishing the RTSP session corresponding to the identifier between the media delivery functional entity and the RTSP session.

10. The media control function entity of claim 8, wherein the RTSP session control function unit is further configured to send real-time streaming session description information required for establishing the RTSP streaming session to the media delivery function entity through the h.248 protocol; and according to the response message fed back by the media delivery functional entity, acquiring an identifier of the RTSP session between the media delivery functional entity and establishing the RTSP session corresponding to the identifier between the media delivery functional entity and the RTSP session.

11. The media control function entity of claim 8, wherein the resource management unit is further configured to obtain media resource information of the media delivery function entity based on H.248 protocol.

12. A method for implementing media delivery control, the method comprising:

receiving a media control request of a media control function entity through a real-time streaming protocol (RTSP) session between the media control function entity and the RTSP; and performing media delivery behavior according to the media control request.

13. The method of claim 12, further comprising:

the method comprises the steps of acquiring real-time streaming session description information sent by a media control function entity, returning an identifier of an RTSP session between the media control function entity and the media control function entity based on an H.248 protocol or a session initiation protocol SIP, and establishing the RTSP session corresponding to the identifier between a media delivery function entity and the media control function entity.

14. The method of claim 12, further comprising:

media asset information is provided to a media control function entity.

15. The method of claim 14, further comprising:

and providing the media resource information of the media delivery function entity to the media control function entity based on the H.248 protocol.

16. A media delivery function, comprising:

17. The media delivery function entity of claim 16, wherein the RTSP session control function unit is further configured to, after obtaining the description information of the real-time streaming session sent by the media control function entity, return an identifier of the RTSP session with the media control function entity based on an h.248 protocol or a session initiation protocol SIP protocol, and establish the RTSP session corresponding to the identifier between the media delivery function entity and the media control function entity.

18. The media delivery function of claim 16 or 17, further comprising:

and the resource management functional unit is used for providing the media resource information to the media delivery unit.

19. The media delivery function of claim 18, wherein the resource management function is further configured to provide media resource information of the media delivery function to the media control function.

20. A media delivery control system, characterized in that the media delivery control system comprises: