Method and system for realizing anchor of media

An implementation method and anchoring technology, applied in the field of call technology, can solve the problems of signaling consumption and long call establishment time

Inactive Publication Date: 2012-02-01

ZTE CORP

6 Cites 2 Cited by

AI-Extracted Technical Summary

Problems solved by technology

Apparently, in the anchor media method implemented in the call initiation process in the...

Abstract

The invention discloses a method and system for realizing the anchor of a media. The method comprises the following steps of: after an application-level gateway (ALG) receives a session description protocol (SDP) request, carrying media resource information in the SDP request, which is received by the ALG, in the SDP request required to be forwarded and media resource information of a media processing entity, which is distributed by the ALG; forwarding the media resource information to the SDP request; after an application server (AS) receives the SDP request, determining whether the ALG is required for anchoring the media and transmitting a media anchor indication for expressing whether the ALG is required for anchoring the media as well as a session initial protocol (SIP) message responded by the SDP; and after the ALG receives the SIP message, determining whether the media is anchored. Whether the ALG is required for anchoring the media is realized by the AS by calling an existing signaling in the establishment process without an extra signaling, thereby the signaling consumption is saved and further the call establishment duration is shortened.

Application Domain

Connection managementTransmission

Technology Topic

Protocol for Carrying Authentication for Network AccessApplication server +5

Image

Examples

Experimental program(1)

Example Embodiment

[0047] figure 1 It is a flowchart of the method for realizing media anchoring in the present invention, such as figure 1 As shown, including the following steps:

[0048] Step 100: After the ALG receives the SDP request, it carries the media resource information in the SDP request and the media resource information of the media processing entity allocated by the ALG in the SDP request to be forwarded, and forwards the SDP request.

[0049] In this step, the SDP request received by ALG carries the media resource information of the initiator of the SDP request, and the ALG will allocate the media resource information of the media processing entity used to connect to the destination of the SDP request (that is, the media resource related to the ALG). information). The SDP request forwarded by the ALG is forwarded to the AS via the S-CSCF.

[0050] The SDP request can be carried by the SIP INVITE message.

[0051] Step 101: The AS receives the SDP request and determines whether the ALG anchor media is needed.

[0052] In this step, AS is based on the user subscription information of the SDP request or INVITE message initiator, the roaming information of the SDP request or INVITE message initiator, the home information of the SDP request or INVITE message destination, and the roaming information of the SDP request or INVITE message destination. , Whether the home network of the SDP request or INIVTE message initiator anchors one or any combination of media, and decides whether to forward the media resource information related to ALG to anchor or not anchor the media. such as:

[0053] If the SDP request or INIVTE message initiator’s subscription information indicates that anchoring is recommended, the AS further determines whether the home network of the SDP request or INIVTE message initiator anchors the media, and if it is not anchored, it further determines the SDP request or INVITE message initiator Whether roaming, if roaming, then decide to anchor; if not roaming, further according to the SDP request or INIVITE message destination's attribution information to determine whether the destination is a network user of this operator, if not, then decide to anchor; if so , Then further determine whether the destination party is roaming according to the SDP request or the attribution information of the destination party of the INIVITE message, if roaming, then decide to anchor; otherwise, decide not to anchor.

[0054] In this step, when the anchored media is determined, it also includes: the AS carries the ALG-related media resource information carried in the received SDP request into the SDP request forwarded to the SDP request or INVITE message destination and sends it ; When it is determined that the media is not anchored, the AS will carry the media resource information related to the initiator of the SDP request carried in the received SDP request to the SDP request forwarded to the destination of the SDP request or INVITE message and send it.

[0055] Step 102: The AS sends a SIP message carrying a media anchor indication indicating whether ALG anchor media is required and an SDP response.

[0056] In this step, the SIP message is forwarded to ALG via S-CSCF.

[0057] The media anchor indication used to indicate whether ALG anchored media is required can be implemented in two ways: one way is to use a special SIP message header field identifier to indicate whether ALG anchored media is required; the other way is, The media anchoring indication is included in the SDP response carried in the SIP message. At this time, the anchoring indication is realized by: using a special SDP attribute identifier to indicate whether ALG anchored media is required; or, selecting a specific media To indicate whether it is valid or invalid, specifically: when the media line corresponding to the media resource information related to ALG is valid (carried), it indicates that the media needs to be anchored; or, when it corresponds to the media resource information related to the SIP request initiator When the media line of is invalid, it indicates that the media needs to be anchored.

[0058] Step 103: The ALG determines whether to anchor the media according to the received SIP message. Including: ALG sends an SDP response to the SDP request or INVITE message initiator, and if it is determined by the media anchor indication in the SIP message that anchoring is required, the SDP sends the media resources of the media processing entity that should carry the ALG allocation Otherwise, the SDP response does not carry the media resource information of the media processing entity allocated by the ALG.

[0059] In this step, if the media anchor indication adopts a special mark, then when the mark shows that it needs to be anchored; or, if the media anchor indication adopts a media row, the media row corresponding to the media resource information related to ALG is valid When the media line corresponding to the media resource information related to the SDP request or INVITE message initiator is invalid: ALG carries the SDP response forwarded by the SDP request or INVITE message initiator to the SDP request or INVITE allocated by the ALG. Media resource information of the media processing entity of the message originator. So far, the initiator of the SDP request or INVITE message has negotiated media resources with the ALG, and the ALG has negotiated the media resources with the destination party of the SDP request or INVITE message; the ALG controls the media processing function entity to forward media data to realize the conversation between the two parties and realize the anchor Define the function of the media (that is, in the media path);

[0060] If the media anchor indication adopts a special mark, then when the mark shows that no anchor is needed; or, if the media anchor indication adopts a media line, the media line corresponding to the media resource information related to ALG is invalid, or When the media line corresponding to the media resource information related to the SDP request or INVITE message initiator is valid: ALG does not carry the SDP response forwarded to the SDP request or INVITE message initiator for connecting to the SDP request or INVITE initiator. Media resource information of the media processing entity. So far, the SDP request or INVITE message initiator and the SDP request or INVITE message destination have negotiated media resources, and the ALG is not included in the call media path of both parties, that is, the media is not anchored.

[0061] It can be seen from the method of the present invention that through the existing signaling in the call establishment process, the AS realizes whether the ALG is anchored to the media, no additional signaling is required, the signaling consumption is saved, and the call establishment time is shortened.

[0062] According to the method of the present invention, a system for realizing media anchoring is also provided, which includes at least ALG and AS, wherein:

[0063] ALG is used to forward a session description protocol SDP request, and the forwarded SDP request carries the received media resource information and the media resource information allocated by the ALG;

[0064] AS is used to receive SDP requests, decide whether ALG anchor media is required, and send SIP messages carrying SDP responses according to the result of the decision.

[0065] If the AS determines that ALG anchor media is required, the media line corresponding to the media resource information related to the ALG in the SDP response is valid, or the media resource information related to the initiator of the SDP request in the SDP response corresponds to The corresponding media line is invalid.

[0066] Those skilled in the art know that the information exchange between ALG and AS is forwarded through S-CSCF ( figure 2 Middle is shown).

[0067] The method of the present invention will be described in detail below in conjunction with embodiments.

[0068] image 3 It is a schematic flow chart of the first embodiment of the present invention for realizing media anchoring, such as image 3 As shown, in the first embodiment, UE-1 as the calling party initiates a call to the called party UE-2. When UE-1 establishes an IMS session with UE-2, the session signaling passes ALG and AS, and between AS and ALG The information exchanged between each other is forwarded via S-CSCF, which specifically includes the following steps:

[0069] Step 300: UE-1 sends a session description protocol SDP request (Offer): SDP1 to UE-2 to establish a media connection with UE-2, for example by sending an INVITE message of SIP SIP, SDP1 contains UE-1 Media resource information.

[0070] Step 301: The SDP request or the INVITE message carrying the SDP request passes through the ALG, and the ALG allocates media resources for connecting to the media processing entity at UE-2.

[0071] Step 302: ALG generates a new SDP request: SDP2, which includes the media resource information in the received SDP request, and also includes the media resource information of the media processing entity allocated by the ALG in step 301 ( image 3 It is represented by ALG1), and then forwards the INVITE message carrying SDP2.

[0072] There may be other processing entities between UE-1 and ALG. These processing entities may modify the received SDP request and then forward it, so that the SDP request received by ALG may not be SDP1, but the modified SDP request is still used Establish a media connection with UE-1, so the media resource information in it can still be regarded as related to UE-1.

[0073] ALG can be used to include ALG1 in SDP2. For example, if ALG1 contains voice media resource information, the voice media resource information related to UE-1 comes first, and the voice media resource information of ALG1 comes later or vice versa, or the voice media resource information of ALG1 The attribute is "inactive";

[0074] Step 303: The SDP request or the INVITE message carrying the SDP request arrives at the S-CSCF, and the S-CSCF forwards the SDP request or the INVITE message carrying the SDP request.

[0075] Step 304: The SDP request or the INVITE message carrying the SDP request arrives at the AS, and the AS follows the user subscription information of the SDP request or INVITE message initiator, the roaming information of the SDP request or INVITE message initiator, the SDP request or the home information of the INVITE message destination , The roaming information of the destination of the SDP request or INVITE message, whether the home network of the initiator of the SDP request or INVITE message anchors one or any combination of media, and decides whether ALG anchoring or not anchoring the media is required. such as:

[0076] If the SDP request or INIVTE message initiator’s subscription information indicates that anchoring is recommended, the AS further determines whether the home network of the SDP request or INIVTE message initiator anchors the media, and if it is not anchored, it further determines the SDP request or INVITE message initiator Whether roaming, if roaming, then decide to anchor; if not roaming, further according to the SDP request or INIVITE message destination's attribution information to determine whether the destination is a network user of this operator, if not, then decide to anchor; if so , Then further determine whether the destination party is roaming according to the SDP request or the attribution information of the destination party of the INIVITE message, if roaming, then decide to anchor; otherwise, decide not to anchor.

[0077] In the first embodiment, it is assumed that the judgment result of the AS is that anchoring is required. In this embodiment, it is assumed that the AS does not anchor the media, and the subsequent steps 305 to 306 are executed. If the AS anchors the media, the steps 305 to 306 are executed in the standard anchoring manner, which is irrelevant to the present invention and will not be repeated.

[0078] It should be noted that there may be other processing entities between ALG and AS. These processing entities may modify the received SDP request and then forward it, so that the SDP request received by the AS may not be SDP2, but the modified SDP The request is still used to establish a media connection with UE-1 and the ALG-controlled media processing entity, so the media resource information therein can still be regarded as related to UE-1 or ALG.

[0079] Step 305: The AS generates a new SDP request: SDP3, and SDP3 contains ALG-related media resource information ( image 3 Is represented by ALG1), and does not include UE-1 related media resource information with the same media type in the media resource information contained in ALG1. For example, if ALG1 contains voice media resource information, SDP3 does not include UE-1 related voice media Resource information.

[0080] Step 306: The SDP request or the INVITE message carrying the SDP request arrives at UE-2. UE-2 uses the media resource information in the received SDP request to negotiate the media, and sends a SIP message, which carries the SDP response (English translation: Answer) : SDP4, for example, the SIP message is a 200 OK message, and SDP4 carries UE-2's media resource information.

[0081] Step 307: The SIP message arrives at the AS, and the AS carries an anchor indication when forwarding the SIP message to instruct the ALG to anchor the media. The message body includes a new SDP response: SDP5, and SDP5 includes the received media resource information in SDP4 .

[0082] Specifically, for example, the header field of the SIP message is used to indicate whether ALG anchored media is required, or the anchoring indication is contained in SDP5, and the "a=" attribute line is used to indicate whether ALG anchored media is required; or the anchoring indication is contained in SDP5. SDP5 contains the same number and types of media rows as SDP2 and in the same order. The media row part of SDP5 corresponding to ALG1 in SDP2 contains the received media resource information in SDP4, that is, the media related to ALG in SDP5. The media row corresponding to the resource information is valid; the ports in the media row corresponding to the media resource information related to UE-1 in SDP2 in SDP5 are all set to 0, that is, the media resource information in SDP5 corresponding to UE-1 The media line is invalid.

[0083] Step 308: The SIP message arrives at the S-CSCF, and the S-CSCF forwards the SIP message.

[0084] Step 309: The ALG receives the SIP message and judges that the media anchoring indication carried in the SIP message indicates that anchoring is required; or, judges that the media line corresponding to the ALG-related media resource information in the SDP response in the SIP message is valid (or It is determined that the media line corresponding to the media resource information related to UE-1 is invalid), and then the media resource ( image 3 Expressed in ALG2).

[0085] Step 310: When ALG forwards the SIP message, it includes a new SDP response in the message body: SDP6, and SDP6 includes the media resource information allocated by the ALG in step 309 for connecting to the media processing entity at UE-1 ( image 3 Expressed in ALG2).

[0086] At this point, UE-1 and ALG negotiated media resources, ALG and UE-2 negotiated media resources, and ALG controls the media processing function entity to forward media data to realize the call between UE-1 and UE-2, and realize the function of anchoring media (Ie in the media path).

[0087] Figure 4 It is a schematic flowchart of the second embodiment of the present invention for realizing media anchoring, such as Figure 4 As shown, in the second embodiment, UE-1 as the calling party initiates a call to the called party UE-2. When UE-1 establishes an IMS session with UE-2, the session signaling passes ALG and AS, and between AS and ALG The information exchanged between each other is forwarded via S-CSCF, which specifically includes the following steps:

[0088] Step 400 to step 403 are completely consistent with the implementation of step 300 to step 303 in the first embodiment, and will not be repeated here.

[0089] Step 404: The SDP request or the INVITE message carrying the SDP request arrives at the AS, and the AS is based on the user subscription information of the SDP request or INVITE message initiator, the roaming information of the SDP request or INVITE message initiator, the SDP request or the home information of the INVITE message destination , Roaming information of the destination of the SDP request or INVITE message, whether the home network of the initiator of the SDP request (INVITE message) anchors one or a combination of media, and decides whether ALG anchoring or not anchoring the media is required. such as:

[0090] If the subscription information of the initiator of the SDP request (INVITE message) indicates that anchoring is recommended, the AS further judges whether the home network of the initiator of the SDP request (INVITE message) anchors the media, and if it is not anchored, it further judges the SDP request or INVITE message Whether the initiator is roaming or not, if it is roaming, then anchoring is determined; if it is not roaming, it further determines whether the destination is a user of the operator's network according to the SDP request or the attribution information of the INIVITE message destination, and if not, it decides to anchor; If it is, it is determined whether the destination party is roaming according to the SDP request or the attribution information of the destination party of the INIVITE message. If it is roaming, it is decided to anchor; otherwise, it is decided not to anchor.

[0091] In the second embodiment, it is assumed that the AS's judgment result is that anchoring is not required. In this embodiment, it is assumed that the AS does not anchor the media, and the subsequent steps 305 to 306 are executed. If the AS anchors the media, the steps 305 to 306 are executed in the standard anchoring manner, which is irrelevant to the present invention and will not be repeated.

[0092] It should be noted that there may be other processing entities between ALG and AS. These processing entities may modify the received SDP request and then forward it, so that the SDP request received by the AS may not be SDP2, but the modified SDP The request is still used to establish a media connection with UE-1 and the ALG-controlled media processing entity, so the media resource information therein can still be regarded as related to UE-1 or ALG.

[0093] Step 405: The AS generates a new SDP request: SDP3, in which only UE-1 related media resource information is included.

[0094] Step 406: The SDP request or the INVITE message carrying the SDP request arrives at UE-2, UE-2 uses the media resource information in the received SDP request to negotiate the media, and sends a SIP message. The message carries the SDP response: SDP4. For example, the SIP message is 200 OK message, SDP4 carries UE-2's media resource information.

[0095] Step 407: The SIP message arrives at the AS. The AS carries an anchor indication when forwarding the SIP message to indicate that the ALG does not anchor the media. The message body includes a new SDP response: SDP5, and SDP5 includes the received media resources in SDP4. information.

[0096] Specifically, for example, the header field of the SIP message is used to indicate whether ALG anchored media is required, or the anchoring indication is included in SDP5, and the "a=" attribute line is used to indicate whether ALG anchored media is required; or the anchoring indication is included in SDP5. In SDP5, SDP5 contains the same number and types of media rows as SDP2 and in the same order. The media row part of SDP5 corresponding to the media resource information related to UE-1 in SDP2 contains the received media resource information in SDP4, namely The media row corresponding to the media resource information related to UE-1 in SDP5 is valid, and the ports in the media row corresponding to ALG1 in SDP2 in SDP5 are all set to 0, that is, the media resource information related to ALG in SDP5 corresponds to The media line is invalid.

[0097] Step 408: The SIP message arrives at the S-CSCF, and the S-CSCF forwards the calling SIP message.

[0098] Step 409: ALG receives the SIP message and judges that the media anchor indication carried in the SIP message indicates that anchoring is not required; or judges that the media line corresponding to the ALG-related media resource information in the SDP response in the SIP message is invalid (Or it is determined that the media line corresponding to the media resource information related to UE-1 is valid), then the media resources allocated in step 401 for connecting to the media processing entity of the SDP request or INVITE message destination are released.

[0099] Step 410: When the ALG forwards the SIP message, it includes a new SDP response: SDP6 in the message body, and SDP6 includes the valid media resource information received in step 408 (media with a port number of 0 is indicated as invalid).

[0100] So far, UE-1 and UE-2 have negotiated media resources, and ALG is not included in the call media path between UE-1 and UE-2, that is, the media is not anchored.

[0101] The above are only preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modification, equivalent replacement and improvement made within the spirit and principle of the present invention shall be included in Within the protection scope of the present invention.

PUM

Description & Claims & Application Information

We can also present the details of the Description, Claims and Application information to help users get a comprehensive understanding of the technical details of the patent, such as background art, summary of invention, brief description of drawings, description of embodiments, and other original content. On the other hand, users can also determine the specific scope of protection of the technology through the list of claims; as well as understand the changes in the life cycle of the technology with the presentation of the patent timeline. Login to view more.