WO2010037307A1

WO2010037307A1 - Method, network node and system for transmitting the content identifier

Info

Publication number: WO2010037307A1
Application number: PCT/CN2009/073849
Authority: WO
Inventors: 陈学梁; 漆宝剑
Original assignee: 华为技术有限公司
Priority date: 2008-09-24
Filing date: 2009-09-10
Publication date: 2010-04-08
Also published as: CN101686224A; CN101686224B

Abstract

A method, network node and system for transmitting the content identifier are provided by the embodiments of the present invention, wherein the method includes that of: obtaining the content identifier of the User Generated Content (UGC); encapsulating the content identifier of the UGC into the Session Initiation Protocol (SIP) message, and transmitting the content identifier of the UGC by the SIP message. Correspondingly, a network node and a network system are also provided by the embodiments of the present invention. By implementing the embodiments of the present invention, the content identifier of the UGC can be generated and transmitted to each network node in the network when the user is developing the UGC service, so that the UGC service can be developed conveniently and favorably.

Description

Method for transmitting content identification and network node and system The application is submitted to the Chinese Patent Office on September 24, 2008, and the application number is 200810198727.X, and the invention name is "a method for transmitting content identification and network node and system" The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference.

Technical field

The present invention relates to the field of communication applications, and in particular, to a method and network node and system for delivering content identification.

Background technique

The IP Multimedia Subsystem (IMS) is a subsystem superimposed on the existing packet domain in the WCDMA network. The packet domain is used as the bearer channel for the upper layer control signaling and media transmission, and the session initiation protocol (Session) is introduced. Description Protocol, SIP) As a service control protocol, SIP is simple, easy to expand, and easy to combine media. It provides rich multimedia services by separating service control from bearer control. The main functional entities in IMS include controlling user registration and session. Call Session Control Function (CSCF) for controlling functions, Application Server (AS) providing various business logic control functions, Home Subscriber Server for centrally managing user subscription data (Home Subscriber Server, HSS) and so on.

IMS based IPTV system, which provides Internet TV (IPTV) services under the overall architecture of IMS, by utilizing existing registration, authentication, routing, session control and establishment, service triggering, charging, and end-to-end QoS guarantee in the IMS network. And other mechanisms to provide users with streaming services and multimedia services that integrate streaming media and real-time session services. It not only provides basic live (BC) services, on-demand (VOD) services, recording (PVR) services, but also provides various enhanced services that reflect the advantages of IMS, including User Generated Content (UGC) services, PPV services. , referral business, advertising business, CallerlD business, Presence business, preview business, bookmark business, iTV business, parental control business, etc. In the existing IMS based IPTV system, it is possible to provide users with more convenient operations by applying content identification. For example, in the COD service, the user sends a request message through the user equipment (User Equipment, UE), and carries the requested uniform resource identifier (Requst URI) in the request message, and requests the corresponding content by using the content identifier of the COD contained in the request. COD service. In the COD service, the COD content source is already in the network, and the service provider determines a content identifier for the COD service, and the user can obtain the corresponding content identifier through the Electronic Program Guide (EPG). . For the UGC service, the existing mechanism does not implement the content identifier for the UGC content, which is not conducive to the development of the UGC service. Summary of the invention

The embodiment of the invention provides a method for transmitting a content identifier, a network node and a system, and the content of the UGC is transmitted to the relevant entity to ensure the normal development of the UGC service.

Correspondingly, an embodiment of the present invention provides a method for delivering a content identifier, including the following steps:

Get user generated content UGC content identification · '

The content identifier of the UGC is encapsulated in a SIP message and transmitted through the SIP message. Correspondingly, the embodiment of the present invention further provides a network node, where the network node includes: an obtaining unit, configured to acquire a content identifier of the UGC;

a packaging unit, configured to encapsulate the content identifier of the UGC obtained in the obtaining unit in a SIP message;

And a transmitting unit, configured to deliver the encapsulated SIP message to the other network node.

Correspondingly, the embodiment of the present invention further provides a network system, where the system includes: a content identifier generating unit, configured to generate a content identifier of the UGC;

a content identifier transmitting unit, configured to encapsulate the content identifier of the UGC generated by the content identifier generating unit in a SIP message for delivery;

a content identifier receiving unit, configured to receive a SIP message sent by the content identifier transmitting unit, and The content identifier of the UGC is obtained in the SIP message.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic diagram of a logical structure of a network system according to an embodiment of the present invention;

2 is a flowchart of a method for transmitting content identification according to an embodiment of the present invention;

3 is a first flowchart of uploading a UGC service according to an embodiment of the present invention;

4 is a second flowchart of uploading a UGC service according to an embodiment of the present invention;

FIG. 5 is a third flowchart of uploading a UGC service according to an embodiment of the present invention;

6 is a schematic structural diagram of a network node according to an embodiment of the present invention;

FIG. 7 is another schematic structural diagram of a network node according to an embodiment of the present invention.

detailed description

The embodiment of the invention provides a method for transmitting a content identifier, a network node and a system, and transmits the content identifier of the UGC to the relevant entity by using SIP signaling to ensure the normal development of the UGC service.

The embodiment of the invention provides a network system, which includes a user equipment (User Equipment, UE), a media function (Mddia Function, MF), a service control function (SCF), and a service selection function. Service Selection Function (SSF), Content Profile Service Function (CPSF), etc. FIG. 1 is a schematic diagram showing the logical structure of a network system in an embodiment of the present invention, including a content identifier generating unit 10, a content identifier transmitting unit 11 and a content identifier receiving unit 12, which may be located at the same time or separately in a network system. MF, SCF, CPSF, SSF, etc., wherein: the content identifier generating unit 10, whose main function is to generate the content identifier of the UGC, the content identifier of the UGC may be, but not limited to, the following forms: CRID, TV URI, CID, URL, etc. Shape The content identifier generating unit may be a single entity in the IMS Based IPTV system, or may be located in an entity such as a UE, an SCF, an MF, a CPSF (metadata storage unit), or a Service Selection Function (SSF). The generation of the content identifier may first generate a temporary logical identifier in the UE, or MF, or SCF, or CPSF or SSF, etc., and then generate a globally unique identifier in another entity (eg, may be generated by a metadata processing unit); The UGC content identifier can be generated before the UGC content upload starts, generated during the UGC content upload process, and generated after the UGC content upload is completed.

Specifically, before the UGC content is uploaded, an entity in the network entity (such as UE, SCF, SSF, CPSF, etc.) may return the generated UGC content identifier to one of the entities according to the UGC request, or the network entity (such as UE, SCF) , SSF, CPSF, etc.) directly generate the UGC content identifier; in the UGC content uploading process, one network element in the network generates the UGC content identifier; after the UGC content is uploaded, one network element in the network generates the UGC for the UGC content Content identification.

The content identifier of the UGC may be generated when the UE operates on the UE, when the UE senses that the user needs to perform the UGC service, or when the UE sends the UGC service request, other network entities (such as SCF, or CPSF, or MF, SSF, etc.) When the UGC service is required to be generated, the UE may be aware of the UGC service identifier. The UE may directly generate a UGC content identifier for the UGC service to other network entities (such as SCF, or CPSF, or MF, SSF, etc.). Similarly, each entity of the network system may generate a UGC content identifier after sensing the UGC service; or may request to return a UGC content identifier to other network entities after sensing the UGC service; or other network entities need to perform UGC The content identity passed by the network entity returns a UGC content identifier.

After the content identifier generating unit 10 generates the content identifier of the UGC, the content identifier is used to transmit the content identifier of the UGC, including encapsulating the content identifier of the UGC in the signaling, such as: encapsulating the content identifier of the UGC in the SIP signaling. The content identifier of the UGC may be located in a SIP request message or a response message, and the manner in which the content identifier of the UGC is carried in the SIP signaling includes, but is not limited to, In the following manner, the content identifier of the UGC is carried in the header field of the SIP signaling; the content identifier of the UGC is carried in the Session Description Protocol (SDP) of the SIP signaling; the extensible markup language in the SIP signaling (Extentsible Markup Language, XML) The content identifier that carries the UGC in the description. The specific carrying methods are detailed as follows:

The first one: extending the SIP protocol, defining a new header field to carry the UGC content identifier; or carrying the existing header field, for example: constructing a Requst URI in the TO header field of the INVITE message, The Requst URI is constructed by the user part and the SP domain name, and the user part part carries the UGC content identifier, ie: "user part@sp domain name" way.

For example: TO :<sip: contentid@ugc.com>

The second type: The content identifier of the UGC is implemented by extending the SDP, for example, by extending the new a line to carry the UGC content identifier, such as " a=ContentId: UGCContentldExample " , where UGCContentld is

<attribute field>, UGCContentId 3⁄4<attribute value>;

For example: a =contentid:<crid://ugc.com/example>

The third type: Carrying the UGC content identifier through XML, you can carry the UGC content identifier by defining a new XML type, such as defining a new Content-Type as application/vnd. etsi. iptvsad-UGC+XML, in XML Definition

<UGCContentId> UGCContentldExample </UGCContentId> to carry the UGC's content ID;

In addition, in the SIP request or the SIP response message, there may be both SDP and XML, and the content identifier of the UGC is carried in the XML or SDP or in the XML and SDP.

In the IMS Based IPTV system, the UE may send the SIP message of the encapsulated UGC content identifier as a content identifier transmission unit, or may be the SCF as the content identifier transmission unit, and identify the encapsulated UGC content. The SIP message is sent; the MF is used as the transmission unit of the content identifier, and the SIP message of the encapsulated UGC content identifier is sent; or the UE, the SCF, the MF, and the like are all used as the transmission unit of the content identifier. The content identifier receiving unit 12 is configured to receive the SIP message sent by the content identifier transmitting unit 11, and obtain the content identifier of the UGC from the SIP message, so that the network entity in the system performs related processing according to the content identifier of the UGC. Specifically, the content identifier of the received UGC may be associated with the received UGC media stream; the content identifier of the received UGC is associated with the UGC content metadata; and the obtained UGC content identifier is stored.

In the IMS Based IPTV system, the content identifier receiving unit 12 may be an entity such as an SCF, a CPSF, an MF, a UE, an SSF, etc., and these entities will receive a SIP signaling message, from a received SIP signaling message, or from a SIP message. The extended message header field, or the UGC content identifier is extracted from the SDP description of the SIP message body, or from the XML description carried by the SIP message. The network entity performs the UGC service behavior according to the content identifier of the UGC, for example, the UE initiates a viewing request according to the content identifier of the received UGC; the SCF selects an appropriate UGC MF according to the content identifier of the UGC; the MF locates the specific according to the content identifier of the UGC. The UGC content; SCF, or CPSF, or MF, or SSF associates the related description information of the content with the content according to the content identification, and the like. Each network entity performs related business activities according to the content identification of UGC, and can successfully carry out UGC services.

Through the UGC service process, the user can generate a UGC content identifier for the UGC service and transmit the UGC content identifier to each network element to better carry out the UGC service.

Correspondingly, FIG. 2 is a flowchart of a method for identifying a delivery content in an embodiment of the present invention, which specifically includes:

Step S20: Generate a content identifier of the corresponding UGC;

Specifically, the content identifier generating unit 10 is configured to generate a content identifier of the UGC. In the UGC service, the unit may be a separate functional entity located in the IMS Based IPTV system, and may also be located in: a UE that generates UGC content, and is UGC. Business services such as SCF, MF, SSF and other functional entities. The content identifier generating unit 10 of the UGC needs to generate a content identifier of the globally unique UGC based on the generating rule of the content identifier, and the generating rule may be: located in the content identifier In the generating unit 10, a set of generating logic is built in, for example, according to the sp domain name signed by the user, the identity of the user, and the serial code generated by the unit, to ensure the uniqueness of the generated UGC content identifier. The specific format of the UGC content identifier may be: a sequence code @user identifier.sp domain name; a user identifier + a sequence code @.sp domain name, and the like. After the network entity where the content identifier generating unit 10 is located determines that the user needs to perform the UGC service, the content identifier of the UGC may be generated for the UGC service.

UGC's content identifier can be generated before UGC content upload, or generated in UGC content upload, or generated after UGC content upload is completed. A network entity may generate a UGC service identifier for the UGC service after determining that the service is a UGC service according to the UGC request or the UGC service identifier.

Each entity of the network system may generate the UGC content identifier after sensing the UGC service; or may notify other network entities after the UGC service is perceived (the entity is mainly used to generate the UGC content identifier, or the UGC content identifier is The entity is uniformly generated by the entity to request to return a UGC content identifier; or the other network entity returns a UGC content identifier to the network entity that needs to perform the UGC content identifier delivery.

Step S21: Encapsulating the UGC content identifier in a SIP message for delivery;

Specifically, the content identifier of the UGC may be encapsulated in the SIP message by the content identifier transmitting unit 11, and the encapsulated SIP signaling message is transmitted to other network nodes.

The UGC's content identifier can be encapsulated in a variety of ways, encapsulated in a SIP request message, and encapsulated in a SIP response message. Specifically, it may be encapsulated in the header field of the request message (or the response message) (the header field may be a newly defined header field, or may be encapsulated in an existing header field), for example: in the INVITE request message, The Requst URI carried in the TO header field carries the content identifier of the UGC. The Requst URI is constructed in the following manner. The UE (which may also be an entity such as SCF or MF) constructs the requested URI based on a certain rule, SP: The domain name (eg: obtained from SSF), the user part (the content identifier of UGC is included in the user part) constitutes the request URI; In addition, the content identifier can be carried in the SDP a line of the request message (or response message): If the new SDP a line is defined, the content identifier is carried, ie: a=<attribute>[": "<attribute value>] , define a new <&3⁄4^^> to carry the content identifier, UGC's content identifier specific content is carried in <& 3⁄41^ ¥&1^>;

It can also be carried in the XML description of the request message (or response message).

In the IMS Based IPTV system, the content identifier transmission unit 11 may be located in the SCF, may be located in the SSF, may be located in the UE, or may be located in an entity such as an MF.

Step S22: Receive a SIP message, and extract a content identifier of the UGC from the SIP message.

Specifically, the content identifier may be received by the content identifier receiving unit 12, and the content identifier may be parsed from the SIP message. SP: The content identifier of the UGC may be parsed through the header field of the SIP signaling (when the header field carries the content identifier) The content identifier of the UGC may be parsed from the SDP information of the SIP signaling (when the SDP carries the content identifier), or the content identifier of the UGC may be parsed in the XML description of the SIP signaling (when the XML carries the content identifier) . The content identification receiving unit 12 performs related business activities according to the content identifier of the parsed UGC. In the IMS Based IPTV system, the content identifier receiving unit 12 may be an entity such as a UE, an SCF, a CPSF, an MF, or an SSF. After receiving the signaling of the content identifier carrying the UGC, the entity parses the UGC from the signaling. Content identification, related business processing according to the content identifier of UGC. For example, the UE may initiate a UGC content viewing request according to the content identifier of the UGC; the MF may find the corresponding UGC content according to the content identifier of the UGC or the MF establishes the association relationship between the UGC content identifier and the UGC content according to the UGC content identifier, and the like; the SCF is based on the UGC. The content identifier may select a corresponding MF; the SCF or MF or the SSF or the CPSF may associate the UGC content metadata with the UGC content identifier according to the UGC content identifier, and the UGC content metadata and the UGC content is related and so on.

In this way, during the UGC service process, the user can generate a UGC content identifier for the UGC service, and transmit the UGC content identifier to each network element, so that the UGC service can be better developed. The specific implementation process in the embodiment of the present invention is described in detail below with reference to FIG. 1 and FIG. 2, and FIG. 3 is a first flowchart of the UGC service uploading in the embodiment of the present invention. The content identifier of the UGC is generated by the UE, and the specific step is performed. as follows:

Step S301: The UE generates a UGC content identifier for the UGC.

When the user operates on the UE, the UE can generate a UGC service identifier for the UGC service when the UE senses that the user performs the UGC service.

Correspondingly, the UE can save the content identifier of the UGC in its own storage unit. Step S302: The UE initiates an INVITE request message.

The request message may carry the identity of the UGC UE, the content identifier of the UGC, and related SDP information.

The content identifier of the UGC can be carried in multiple ways: It can be carried in the user part of the request URI: The UE constructs the requested URI based on certain rules, SP: the domain name of the SP (obtained from the SSF), the user part (the content identifier contains The request part URI is formed in the user part (see example 1); it can be carried in the a line of the SDP (see example 2); it can be carried in the XML description (see example 3);

Example 1 (carrying the UGC's content ID in the SIP request URI):

INVITE UGCContentIdExample@iptvsp.com SIP/2.0

Example 2 (Loading the UGC's content ID in the SIP SDP a line):

a=UGCContantId: UGCContentldExample

Example 3 (carrying the UGC's content ID in the SIP XML):

<?xml version=" 1.0"encoding="UTF-8"?>

<UGCContentId> UGCContentldExample </UGCContentId>

Step S303: After receiving the INVITE request message, the Core (core) IMS forwards the INVITE request to the SCF.

Step S304: After receiving the INVITE request, the SCF extracts the content identifier of the UGC from the INVITE message. First, the SCF determines that the UGC service is the UGC service from the corresponding header field in the INVITE request, and extracts the user identity identifier. The content identifier of the UGC may be extracted, but is not limited to the following manner: or the content identifier of the UGC is extracted from the Request-URI (eg, Example 1 in S302: 'Or extracting the content identifier of the UGC from the corresponding SDP information (as in the example 2 in step S302) · ' · · or extracting the UGC from the XML description in the message body Content identification (such as example 3 in step S302);

Step S305: The SCF performs service authentication on the user request.

Step S306 to step S307: the SCF sends an INVITE request to the MF;

Step S308: MF saves the content identifier;

Thus, when a subsequent user initiates a viewing request, the MF can find the corresponding UGC content based on the content identification. It should be noted that this step is optional.

Step S309 to step S312: MF returns 200 OK message;

Step S313 to step S315 and step S318: the UE sends back an ACK message to the MF;

Step S316: The SCF stores the content identifier in the specified storage format to the CPSF by using a signaling;

In this way, the CPSF can publish the stored content identifier to the viewer through the SSF, and the viewer can initiate a viewing request according to the content identifier; the CPSF can also establish an association relationship between the content identifier and the user input UGC content description information (such as UGC). The content identifier and the association table of the UGC description information, etc., through which the UGC content description information and the UGC content can be associated.

Step S317: The CPSF returns a response message;

It should be noted that the step S316 and the step S317 may be performed after the SCF parses the content identifier of the UGC, that is, after receiving the INVITE message in step S303, the content identifier of the UGC is sent to the CPSF, and the entire implementation process is There may be no necessary sequential relationship between the sequence and the step after step S304.

Step S319 and step S320: establishing media transmission between the UE and the MF through SDP negotiation Channel, the UE sends the generated UGC content to the MF.

The address of the MF here is obtained based on the 200 OK message in steps S309 through S312. After the content is uploaded to the MF, the MF establishes an association relationship between the content identifier and the UGC content (eg, may be an association table, etc.), according to the content identifier of the UGC, when the subsequent user initiates the viewing request, the MF may be based on the user. In the initiated viewing request, the content identifier of the UGC carried is sent to the user.

In this way, when the UE senses that the user performs the UGC service, the UGC can generate a UGC content identifier for the UGC service, and the content identifier of the UGC is transmitted to each network element, so that the entire system can better carry out the UGC service.

FIG. 4 is a second flowchart of uploading a UGC service in an embodiment of the present invention, where the content identifier is determined by

SCF generation, the specific steps are as follows:

Step S401: The UE initiates an INVITE request.

The request message carries the identity of the UGC UE, the UGC service identifier, the address of the UGC, and the related SDP information.

Step S402: After receiving the INVITE request message, the Core IMS forwards the INVITE request to the SCF.

Step S403: After receiving the INVITE request, the SCF determines the UGC service from the corresponding header field in the INVITE request, and extracts the user identity identifier;

Step S404: The SCF performs service authentication according to the user request;

Step S405: The SCF generates a content identifier of the corresponding UGC according to the request of the user; Step S406 to Step S407: In the INVITE request, the content identifier of the UGC needs to be carried;

The UGC's content identifier can be carried in a variety of ways: If it is carried in the TO header field, the new TO header field consists of the user part part and the SP domain part, and the user part part contains the UGC content identifier (see Example 4); UGC The content identifier may also be carried in the SDP, and the content identifier of the UGC is carried in the form of a line by extending the SDP (see example 5); the content identifier of the UGC may also be carried in the message body of the INVITE request in the form of XML ( See example 6); Example 4 (carrying the content identifier of UGC in the SIP header field):

To: <sip: UGCContentIdExample@iptvsp.com >

Example 5 (Loading the UGC's content ID in the SIP SDP):

a=UGCContantId: UGCContentldExample

Example 6 (carrying the UGC's content ID in the SIP XML):

<?xml version=" 1.0"encoding="UTF-8"?>

<UGCContentId> UGCContentldExample </UGCContentId>

Step S408: The MF saves the content identifier of the UGC;

In this way, when the subsequent user initiates the viewing request, the MF can find the corresponding UGC content according to the content identifier of the UGC. The step may be selected, and the UGC may be determined as needed according to the need of step S409 to step S412: MF returns 200 OK message;

The 200 OK message carries the address information of the MF and the SDP information of the MF, and may also include the content identifier of the UGC.

Step S413 to step S415 and step S418: the UE sends back an ACK message to the MF;

Step S416: The SCF stores the content identifier in the specified storage format to the CPSF by using a signaling;

In this way, the CPSF can publish the stored content identifier to the viewer through the SSF, and the viewer can initiate a viewing request according to the content identifier; the CPSF can also establish an association relationship between the content identifier and the user input UGC content description information (such as UGC). The content identifier and the association table of the UGC description information, etc., through which the UGC content description information and the UGC content are associated.

Step S417: The CPSF returns a response message;

It should be noted that step S415 and step S416 are generally started after step S405, that is, after the content identifier of the UGC is generated in step S405, the content identifier is sent to the CPSF. Step S420: The UE saves the content identifier of the UGC and the MF address.

Step S419 and step S421: A media transmission channel is established between the UE and the MF through SDP negotiation, and the UE sends the generated UGC content to the MF.

The address of the MF and the content identifier of the UGC in step S420 can be obtained according to the 200 OK message in step S409 to step S412. The content identifier of the UGC may also be that after the SCF generates the content identifier of the UGC, the SCF transmits the content identifier of the UGC to the UE. Step S419 and step S420 do not have a strict sequence relationship, which may occur at the same time, and may exist in sequence.

After the UGC content is uploaded to the MF, the MF establishes an association relationship between the content identifier of the UGC and the UGC content (which may be an association table, etc.), according to the content identifier of the UGC, when the subsequent user initiates the viewing request, the MF may initiate according to the user. In the viewing request, the content identifier of the UGC carried, and the corresponding UGC content is sent to the user.

In this way, when the SCF knows that the UGC service is performed, the SGC can generate a UGC content identifier for the UGC service, and transmit the UGC content identifier to each network element. The entire system can better carry out the UGC service.

FIG. 5 is a third flowchart of the UGC service upload in the embodiment of the present invention. The content identifier of the UGC is generated by the MF, and the specific steps are as follows:

Step S501: The UGC UE sends an INVITE message to the CORE IMS, requesting to initiate a UGC upload, where the request message may carry the identity of the UGC UE, the UGC service identifier, the address of the UGC UE, and the related SDP information.

Step S502: After receiving the INVITE request message, the core IMS forwards the INVITE request to the SCF.

Step S503: After receiving the INVITE message, the SCF determines that the UGC service is from the corresponding header field in the INVITE request, and extracts the user identity identifier.

Step S504: The SCF performs service authentication according to the user request.

Step S505 and step S506: The SCF sends an INVITE request to the MF via the Core IMS to cancel the s, . Step S507: MF generates and saves a content identifier of the UGC;

Specifically, the MF may generate a content identifier of the UGC after determining that the service requested by the user is a UGC service.

After the MF saves the content identifier of the UGC, when the subsequent user initiates the viewing request, the MF can find the corresponding UGC content according to the content identifier of the UGC. The MF may decide whether to save the content identifier of the UGC according to actual needs.

Step S508 and step S509, step S512 to step S513: The MF sends back a 200 OK message to the UE, where the 200 OK message carries the content identifier of the UGC, the SDP information of the MF, and the address information of the MF, the UGC There are several ways to identify content: UGC's content identifier is carried in SDP (see Example 7); UGC's content identifier is carried in XML (see Example 8);

Example 7 (Loading the UGC's content ID in the SIP SDP):

a=UGCContantId: UGCContentldExample

Example 8 (carrying the UGC's content ID in the SIP XML):

<?xml version=" 1.0"encoding="UTF-8"?>

<UGCContentId> UGCContentldExample </UGCContentId>

Step S510: Step S511: The SCF stores the content identifier of the UGC in the specified storage format to the CPSF by using a signaling, and the CPSF returns a response message to the SCF.

In this way, the CPSF can publish the stored UGC content identifier to the viewer through the SSF, and the viewer can initiate a viewing request according to the content identifier of the UGC; the CPSF can also establish an association between the UGC content identifier and the user input UGC content description information. Relationships (such as the UGC content identifier and the association table of the UGC description information, etc.), through the UGC content identifier, the UGC content description information and the UGC content can be associated.

Step S514 to step S517: the UE returns an ACK message to the MF.

Step S518 and step S520: a media transmission channel is established between the UE and the MF through SDP negotiation, and the generated UGC content is sent to the MF. Step S519: The UE saves the content identifier of the UGC and the MF address.

It should be noted that the step is implemented after the UE receives the 200 OK message, that is, after the step S513.

After the UGC content is uploaded to the MF, the MF establishes an association relationship between the content identifier of the UGC and the UGC content (which may be an association table, etc.), according to the content identifier of the UGC, when the subsequent user initiates the viewing request, the MF may initiate according to the user. The content identifier of the UGC carried in the viewing request is sent to the user.

In this way, when the MF knows that the user is performing the UGC service, it can generate a UGC content identifier for the UGC service, and transmit the UGC content identifier to each network element, so that the entire system can better carry out the UGC service.

Correspondingly, FIG. 6 is a schematic structural diagram of a network node in the embodiment of the present invention, including: an obtaining unit 61, configured to acquire a content identifier of the generated UGC. The content identifier of the UGC may be generated in the network node or may be requested from other network nodes (such as obtained from SSF, SCF, MF, CPSF, etc.). Whether it is generated in the network node or requested by other network nodes, it may be generated by combining the UGC service identifiers generated by the user in the UGC operation, and if it is a UE, it may be generated directly when the user is aware of the UGC service.

The encapsulating unit 62 is configured to encapsulate the content identifier of the UGC obtained in the obtaining unit 61 in a SIP message. Specifically, the encapsulating unit 62 encapsulates the content identifier of the UGC in a header field of the SIP message; or the encapsulating unit 62 encapsulates the content identifier of the UGC in the SDP of the SIP message; or the encapsulating unit 62 sets the content of the UGC The identifier is encapsulated in the XML of the SIP message. Of course, the encapsulation process is not limited to the above, and may be various combinations of the above.

The transmitting unit 63 is configured to deliver the SIP message encapsulated by the encapsulating unit 62 to other network nodes.

It should be noted that the network node may be a UE, an MF, an SCF, a CPSF, an SSF, or the like. In this way, when the node knows that the user is performing UGC services, it can generate a UGC service.

The content identifier of the UGC, the content identifier of the UGC is transmitted to each network element, and the entire system can be To better carry out UGC business.

Specifically, FIG. 7 is another schematic structural diagram of a network node in the embodiment of the present invention, including:

The obtaining unit 72 is configured to obtain a content identifier of the generated UGC. The content identifier of the UGC may be generated in a network node or may be requested from other network nodes (e.g., obtained from SSF, SCF, MF, CPSF, etc.). Whether it is generated in the network node or requested by other network nodes, it may be generated by combining the UGC service identifiers generated by the user in the UGC operation, and if it is a UE, it may be generated directly when the user is aware of the UGC service. Specifically, if the obtaining unit 72 obtains the content identifier of the temporary UGC, the content identifier of the globally unique UGC needs to be generated according to the content identifier of the temporary UGC.

The encapsulating unit 73 is configured to encapsulate the content identifier of the UGC obtained in the obtaining unit 72 in a SIP message. Specifically, the encapsulating unit 73 encapsulates the content identifier of the UGC in a header field of the SIP message; or the encapsulating unit 73 encapsulates the content identifier of the UGC in the SDP of the SIP message; or the encapsulating unit 73 identifies the content of the UGC. Encapsulated in the XML of the SIP message. Of course, the encapsulation process is not limited to the above, and may be various combinations of the above.

The transmitting unit 74 is configured to deliver the SIP message encapsulated by the encapsulating unit 73 to other network nodes.

Correspondingly, when the content identifier of the UGC is generated by the network node, the network node is further provided with a generating unit 71, configured to generate a content identifier of the UGC according to the UGC service identifier, and the obtaining unit 72 obtains the UGC from the generating unit 71. Content identification. For the UE, when the UE can directly perceive the user to perform the UGC service, the UE can generate the content identifier of the UGC.

The network node may also receive the SIP message sent by the other network node, and obtain the content identifier of the UGC from the SIP message for related processing. The network node may further be provided with a receiving unit 76, configured to receive the SIP message sent by the other network node. The SIP message encapsulates the content identifier of the UGC; the corresponding parsing unit 77 and/or the processing unit 75 are disposed in the network node, where: the parsing unit 77 is configured to obtain the UGC from the SIP message received by the receiving unit. Content label The processing unit 75 is configured to perform association processing with the UGC content according to the content identifier of the UGC encapsulated in the SIP message received by the receiving unit 76, or associate the content identifier of the UGC with the metadata of the UGC content. Correspondingly, after the parsing unit 77 obtains the content identifier of the UGC, the content identifier of the UGC may be saved in the storage unit 78.

It should be noted that the network node may be a UE, an MF, an SCF, a CPSF, an SSF, or the like. In this way, when the node knows that the user is performing the UGC service, the UGC can generate a UGC content identifier for the UGC service, and the content identifier of the UGC is transmitted to each network element, so that the entire system can better carry out the UGC service. The node can also receive UGC content identifiers transmitted by other nodes in the system, and perform UGC services according to the content identifier of the UGC.

In summary, by assigning the UGC content identifier to the UGC service in the IMS Based IPTV system, and encapsulating the content identifier in the SIP protocol, the UGC content identifier can be transmitted to each required network element to facilitate the UGC service. Smooth development.

The above is only a preferred embodiment of the present invention, and the scope of the present invention is not limited thereto, and the equivalent changes made in the claims of the present invention are still within the scope of the present invention.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, can also be implemented entirely by hardware. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The specific embodiments of the present invention have been described in detail with reference to the preferred embodiments of the present invention. The scope of the invention, any modifications, equivalents, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Claim

A method for delivering a content identifier, the method comprising the steps of: acquiring a user generated content, a content identifier of the UGC,

The content identifier of the UGC is encapsulated in a Session Initiation Protocol SIP message and transmitted through the SIP message.

2. The method according to claim 1, wherein the content identifier of the UGC is encapsulated in a SIP message, specifically one or more of the following combinations:

Encapsulating the content identifier of the UGC in the header field of the SIP message.

Encapsulating the content identifier of the UGC in a session description protocol SDP description of the SIP message;

The content identifier of the UGC is encapsulated in an extensible markup language XML description of the SIP message.

The method of claim 1, wherein before the obtaining the content identifier of the UGC, the method further includes:

The content identifier of the UGC is generated according to the UGC service identifier when the user performs the UGC service operation; or

The UGC content identifier is generated when the user is perceived to perform UGC business operations.

4. The method according to claim 3, wherein the content identifier of the UGC is generated before the UGC content uploading is started, or generated during the UGC content uploading process, or after the UGC content uploading is completed.

The method of claim 1, wherein the acquiring the content identifier of the UGC specifically includes:

Obtain the content identifier of the temporary UGC;

A content identifier of the globally unique UGC is generated according to the content identifier of the temporary UGC.

6. The method according to claim 1, wherein the method further comprises: when the SIP message is transmitted to a network node, the network node obtains from the SIP message Take the content identifier of UGC.

The method according to claim 6, wherein after the network node obtains the content identifier of the UGC from the SIP message, the method further includes at least one of the following steps:

Storing the content identifier of the UGC; or

Associating the content identifier of the UGC with the UGC content; or

The content identifier of the UGC is associated with metadata of the UGC content.

8. A network node, wherein the network node comprises:

An obtaining unit, configured to acquire a content identifier of the user generated content UGC;

a transmitting unit, configured to transmit the SIP message after the encapsulation unit is encapsulated.

The network node according to claim 8, wherein the network node further comprises:

And a generating unit, configured to generate a content identifier of the UGC, where the obtaining unit is specifically configured to obtain a content identifier of the UGC from the generating unit.

The network node according to claim 8, wherein the obtaining unit is configured to acquire a content identifier of the temporary UGC, and generate a content identifier of the globally unique UGC according to the content identifier of the temporary UGC.

a receiving unit, configured to receive a SIP message, where the SIP message encapsulates a content identifier of the UGC;

And a parsing unit, configured to obtain a content identifier of the UGC from the SIP message received by the receiving unit.

The network node according to claim 11, wherein the network node further comprises: a storage unit, configured to store the content identifier of the UGC obtained in the parsing unit, or a processing unit, configured to associate the content identifier of the UGC acquired by the parsing unit with the UGC content, or use the UGC content identifier and the UGC The metadata of the content is associated.

The network node according to any one of claims 8 to 12, wherein the network node is a user equipment, or a service control function, or a media function, or a service selection function.

14. A network system, the system comprising:

a content identifier generating unit, configured to generate a content identifier of the user-generated content UGC, a content identifier transmitting unit, configured to encapsulate the content identifier of the UGC generated by the content identifier generating unit in a SIP message for delivery;

And a content identifier receiving unit, configured to receive a SIP message sent by the content identifier transmitting unit, and obtain a content identifier of the UGC from the SIP message.

The network system according to claim 14, wherein the system further comprises at least:

a content identification storage unit, configured to store a content identifier of the UGC obtained by the content identifier receiving unit; or

The content identifier association unit is configured to associate the content identifier of the UGC obtained by the content identifier receiving unit with the UGC content, or associate the content identifier of the UGC with the metadata of the UGC content.