WO2010075692A1 - Identifying method and device for forwarding service - Google Patents

Abstract

An identifying method and device for forwarding service are provided. The method comprises the following steps: when the request universal resource identifier (Request-URI) in the received message is changed, judging whether the message meets the match conditions in one or more service point triggers (SPT) which are contained in an initial filter criteria (iFC). When the message meets the match conditions in one or more SPTs which are contained in the iFC, according to the forwarding service identifier which is contained in the iFC, identifying whether the service which corresponds to the message is the forwarding service.

Description

 Forwarding service identification method and equipment

 This application claims the priority of the Chinese application filed on December 31, 2008, with the application number 200810187970.1, and the invention name is "a method and device for identifying the forwarding business".

Technical field

 The present invention relates to the field of communication technologies, and in particular, to a method and device for identifying a forwarding service.

Background technique

 The IP Multimedia Subsystem (IMS) network is the IP Multimedia Subsystem Service Control defined by the 3GPP Funds (3GPP) in the 3rd Generation Partnership Project (3GPP). The interface (ISC) refers to the interface between the Call Session Control Function (CSCF) and the Application Server (AS). The Request-Universal Resource Identifier (Request-Universal Resource Identifier) in the message before and after the trigger is only used for the forward-recognition of the triggered AS in the called service-call session control function (S-CSCF). Request-URI) Make a simple comparison.

 The description of the S-CSCF identification forwarding in 3GPP 24.229 is not given a detailed description. The called S-CSCF identifies the forwarding service of the triggering AS only according to the Session Initiation Protocol (SIP). Whether the Request-URI in the message is changed for easy identification. For example: The Request-URI in the SIP message before the AS is triggered is "TEL: +8675528760001". After the AS is triggered, the AS modifies the Request-URI in the SIP message to "TEL:+8613911112222", then the S-CSCF judges before and after the trigger. The Request-URI has been changed, and it is identified as a forward-directed direct route to the forward-relay network without subsequent service triggering.

 In the prior art solution, the S-CSCF identifies the forward forwarding only according to whether the Request-URI in the SIP message before and after the trigger is changed. Due to the variety of services and scenarios, the AS sent by the S-CSCF contacts the Invite message. The Request-URI (a basic request message in SIP) is often modified into various service-related forms. When a simple judgment of the Request-URI change is applied to the IMS network, the forwarding service identification may be inaccurate. , or the problem of forwarding business is not recognized.

Summary of the invention The embodiment of the invention provides a method and a device for identifying a forwarding service, which are used for accurately identifying a forwarding service.

 An embodiment of the present invention provides a method for identifying a forwarding service, where the method includes: determining, when the request resource identifier Request-URI in the received message is changed, whether the message meets the initial filtering rule iFC One or more service trigger points in the SPT;

 When the message meets the matching condition in the one or more SPTs included in the iFC, the forward service identification identifier included in the iFC is used to identify whether the service corresponding to the message is a forwarding service.

 On the other hand, an embodiment of the present invention further provides an apparatus having a called service-call session control function, where the apparatus includes:

 a matching determining unit, configured to determine, when the Request-URI in the received message is changed, whether the message meets a matching condition in one or more SPTs included in the iFC;

 a forward identification unit, configured to identify the message according to the forwarding service identification identifier included in the iFC when the matching determination unit determines that the message meets a matching condition in one or more SPTs included in the iFC Whether the corresponding service is a forward business.

DRAWINGS

 The drawings described herein are provided to provide a further understanding of the invention and are in no way of limitation. In the drawing:

 1 is a schematic flowchart of a method for identifying a forwarding service according to Embodiment 1 of the present invention; FIG. 2 is a schematic structural diagram of an S-CSCF according to Embodiment 2 of the present invention;

 FIG. 3 is a schematic flowchart of a method for identifying a forwarding service according to Embodiment 3 of the present invention; FIG. 4 is a schematic flowchart of a method for acquiring original called information according to Embodiment 4 of the present invention; FIG. 6 is a schematic flowchart of obtaining the original called information according to the scenario 2 in the fourth embodiment of the present invention; FIG. 7 is a schematic diagram of obtaining the original called party in the third scenario according to the fourth embodiment of the present invention; Schematic diagram of the flow of information. detailed description

In order to make the objects, the technical solutions and the advantages of the embodiments of the present invention more clearly, the embodiments of the present invention will be described in detail below with reference to the embodiments and drawings. Here, the illustrative embodiment of the present invention The examples and the description thereof are intended to explain the present invention, but are not intended to limit the invention.

 A first embodiment of the present invention provides a method for identifying a forwarding service, and a schematic flowchart thereof is shown in FIG. 1 , and includes the following steps:

 Step S101: When the Request-URI in the received message is changed, determine whether the message meets one or more Service Point Trigger (SPT) included in the Initial Filter Criteria (iFC). Matching conditions in .

 When the message meets the matching condition in one or more SPTs included in the iFC, the process proceeds to step S102;

 When the message does not match the matching condition in one or more SPTs included in the iFC, the process proceeds to step S103.

 The received message may be a message returned by the application server AS after being triggered.

 The matching condition in one or more SPTs included in the iFC is specifically set by an exact value or a regular expression, and the specific content of the matching condition is:

 a Request-URI content set in a <Request-URI> field in the first SPT; and/or a History-info header field set in a <SIPHeader> field in the second SPT; and/or in the third SPT The Diversion header field is set in the <SIPHeader> field.

 Specifically, based on the foregoing matching condition setting, the judgment basis of the message conforming to the matching condition in one or more SPTs included in the iFC includes the following situations:

 When the Request-URI in the message returned by the received AS trigger matches the Request-URI content set in the <Request-URI> field in the first SPT, it is determined that the message meets the matching condition; or

 The Request-URI in the message returned after the received AS trigger matches the Request-URI content set in the <^^^81-111 1> field in the first SPT, and the message corresponds to the AS before the AS trigger When the message matches the information of the History-info header field set in the <SIPHeader> field in the second SPT, it is determined that the message meets the matching condition; or,

The difference between the Request-URI in the message returned after the received AS trigger and the message corresponding to the message before the AS triggers is the Request-set in the <Req _UeS t-URI> field in the first SPT. When the URI content matches the difference relationship corresponding to the <8 13⁄4&[161">History-info header field set in the second SPT, the message is judged to be in a matching condition; or, The Request-URI in the message returned after the received AS trigger matches the Request-URI content set in the <Request-URI> field in the first SPT, and is set with the Diversion set in the <SIPHeader> field in the third SPT. When the content set by the header field matches, it is judged that the message meets the matching condition.

 Step S102: Identify, according to the forwarding service identification identifier included in the iFC, whether the service corresponding to the message is a forwarding service.

 The forwarding service identification identifier includes a server identifier and a forwarding identifier.

 When the server identifier included in the iFC is the location identifier of the entire network, and the forwarding identifier is the forwarding confirmation character, the process proceeds to step S104;

 When the server identifier included in the iFC is not the entire network identification location character, or the forwarding identifier is not the forwarding confirmation character, the process proceeds to step S103.

 Specifically, the process of identifying, according to the forwarding service identification identifier included in the iFC, whether the service corresponding to the message is a forwarding service is:

 Determine whether the server identifier included in the iFC is a full network identification location character;

 When the server identifier included in the iFC is a location identifier of the entire network, it is determined whether the forwarding identifier is a forward confirmation character;

 When the forwarding identifier is a forwarding confirmation character, the service corresponding to the message is forwarded to the next step S103, and the service corresponding to the message is a non-forwarding service, and the subsequent service corresponding to the message is triggered.

 Step S104: Identify the service corresponding to the message as a forwarding service, and route the message to the forwarding network.

 It should be noted that, in the above method, when the iFC is configured for a single user, the iFC is configured on a Home Subscriber Server (HSS) to which the single user subscribes; when the iFC is The iFC is configured on the S-CSCF for the configuration of all users of the current network.

 Further, the method further includes: obtaining, according to the History-Info information carried in the message, a method for obtaining the original called information of the message corresponding to the message before the AS is triggered, and the specific process is as follows:

Obtaining the last index information in the message returned after the received AS trigger; According to the index information, the parent index information of the index information is obtained.

 The information corresponding to the parent index information is confirmed as the original called information of the message corresponding to the message before the AS is triggered.

 According to the actual situation, the corresponding changes or changes in the steps or processes in the embodiments of the present invention do not affect the scope of protection of the patent.

 The technical solution of the embodiment of the present invention has the following advantages, because the method for performing forwarding service identification according to the matching condition in one or more SPTs included in the iFC and the corresponding extended parameter is adopted, so that the forwarding can be accurately performed. The identification of services has improved the accuracy of business identification and avoids the waste of communication resources due to misidentification.

 Based on the method proposed in the foregoing embodiment, the second embodiment of the present invention provides a device, such as an S-CSCF, having a called service-call session control function. The structure of the device is as shown in FIG.

 The matching judging unit 1 is configured to determine, when the Request-URI in the received message is changed, whether the message meets the matching condition in one or more SPTs included in the iFC.

 The matching judging unit 1 is specifically configured to receive a message returned by the application server AS, and when the Request-URI in the received message is changed, determine whether the message meets a match in one or more SPTs included in the iFC. condition.

 The matching judging unit 1 specifically includes:

 The first determining module 11 is configured to determine whether the Request-URI in the message returned after the received AS is triggered is changed.

 The condition obtaining module 12 is configured to: when the first determining module 11 determines that the Request-URI in the message returned after the received AS trigger is changed, obtain the iFC corresponding to the message returned by the HSS or the local AS after the received AS trigger Matching conditions in one or more SPTs included;

 The second determining module 13 is configured to determine whether the message returned after the received AS trigger meets the matching condition acquired by the condition obtaining module 12.

The forwarding identification unit 2 is configured to: when the matching determining unit 1 determines that the message meets the matching condition in the one or more SPTs included in the iFC, whether the service corresponding to the message is identified according to the forwarding service identification identifier included in the iFC For the forwarding service, the forwarding service identification identifier includes a server identifier and a forwarding identifier, and the forwarding forwarding unit 2 specifically includes: The third determining module 21 is configured to determine, according to the matching condition, whether the server identifier is a full network identification location character;

 The fourth judging module 22 is configured to: when the third judging module 21 determines that the server identifier is a full-network identification location character, determine whether the forwarding identifier is a forwarding confirmation character, and when the current forwarding identifier is a forwarding confirmation character, the identification message corresponds to The business is a forward business.

 Further, the device further includes:

 The information obtaining unit 3 is configured to obtain the original called information of the message corresponding to the message before the AS triggers according to the parent index information of the last index index information in the returned message after the received AS trigger.

 The above units may be distributed in one device or distributed in multiple devices. The above units can be combined into one unit, or they can be split into multiple subunits.

 The technical solution of the embodiment of the present invention has the following advantages, because the called service-call session control function is adopted for performing forwarding service identification according to the matching condition in one or more SPTs included in the iFC and its corresponding extended parameter. Therefore, the device can accurately identify the forwarding service, thereby improving the accuracy of the service identification and avoiding the waste of communication resources caused by misidentification.

 In the existing technical scenario, combined with a specific example, the Request-UR form transformation application scenario mainly includes the following situations:

 Case 1: The Request-URI before the called party is "tel: +8675512345". The docked AS is transformed according to the business requirement or its own support capability, and the Request-URI after the trigger is changed in the form of "sip:+". 8675512345@huawei.com;user=phone,,.

 Case 2: The Request-URI before the trigger is "tel: 12345; phone-context=+86755,,, the docked AS performs the number analysis and regularization on the short form, and the triggered Request-URI is adjusted to "tel" :+8675512345", actually the same number.

 Case 3: The Request-URI before the trigger is "tel:+8675512345", and the AS is added to the docked AS (for example: cic). The Request-URI after the AS is triggered is modified to "tel:+8675512345;cic= +8001'O

Case 4: The Request-URI before the trigger is "tel: +8613911112222", and the connected AS performs special service processing, and the number is uniformly added to the operation pre-selection prefix (for example: 17951), which triggers The Request-URI after the AS is modified to "tel: 179586113911112222".

 It should be noted that the above four cases are merely examples of specific numbers or identifiers for convenience of description. In a specific application, the change of the specific number or the content of the identification does not affect the example range represented by the above cases.

 In the following, in order to clarify the technical solutions proposed by the embodiments of the present invention, the present invention will be specifically described in the following embodiments in combination with the above several cases.

 The existing forward recognition technology simply compares the Request-URI before and after the trigger. Such recognition does not accurately distinguish the forwarding service. Therefore, multiple non-forward scenarios are identified as forwarding situations. The call routing process is additionally performed once more, which in turn leads to service failure, which affects the efficiency of service response and wastes network resources.

 The technical solution proposed by the embodiment of the present invention is to flexibly utilize the existing user subscription data iFC and the extended part parameter to flexibly identify the forward rotation through the device with the called service-call session control function, and solve the various S-CSCF pairs. The effective identification of the forwarding after the AS is changed in the scenario, to avoid the change of the part that affects the route when the called party is triggered, and to additionally cause the service failure caused by the called routing process.

In the technical solution proposed by the embodiment of the present invention, the device having the called service-call session control function flexibly uses the <Request-URI> field and/or <80 ⁾ in the SPT of the existing user subscription data. (161) field and other fields to configure the matching condition, and determine whether the message after the AS is triggered satisfies the established SPT. When the result of the above determination is yes, the current message is triggered to the corresponding input of the SPT. 1 1101^61"\^>Server. For the forwarding service, the <ServerName> field in <ApplicationServer> is no longer configured with the address of the AS, but a location character recognized by the entire network is configured, that is, the entire network recognizes the location character. And configuring an extended parameter of the S-CSCF to perform service identification as a forwarding identifier. In the embodiment of the present invention, the forwarding identifier is named by "CF". In a specific application scenario, the change of the parameter name does not occur. It affects the scope of protection of the present invention.

 For example: The iFC signed by the user is:

 <InitialFilterCriteria>

 <Priority>0</Priority>

<TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <1^9\168 13⁄41>Proposed URI</Request-URI>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <861^6^&1^> The whole network recognizes the position character; CF= 1 </ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

</ApplicationServer>

 </InitialFilterCriteria>

 When the Request-URI in the SIP message after the AS is triggered changes, and the Request-URI in the message is modified by the AS to the defined URI, the device having the called service-call session control function determines the iFC. The message satisfies the matching condition of the trigger point, and thus triggers to <ServerName> in <ApplicationServer>. At this time, the device determines that <ServerName> is the location character recognized by the entire network, not the AS address, and will not perform the AS of the ISC interface. Trigger the route and make its own business logic judgment. For example: Obtain the extended forwarding identifier "CF" in <861"\^^ 1^>, and judge whether the service corresponding to the current message is the forwarding service according to this parameter. If CF=1, it is forward, if CF= 0 or non-existent, it is considered non-forward.

 Specifically, the technical solution proposed in the embodiment of the present invention solves the problem of forwarding identification in various scenarios by using the flexible configuration of the iFC data and the extended parameter "CF". The process is described. The schematic diagram of the process is shown in Figure 3. The following steps are included:

 Step S301: The device, such as the S-CSCF, determines whether the Request-URI in the message is changed after receiving the message triggered by the AS.

 If the Request-URI has not been changed, proceed to step S302;

If the Request-URI is changed, the process proceeds to step S303 to determine whether the service corresponding to the message is a forwarding service. Step S302: The device continues to perform a service trigger on the message without performing forwarding. Step S303: The device determines whether the Request-URI meets a matching condition in one or more SPTs included in the iFC.

 When the device determines that the Request-URI meets the matching condition, the process proceeds to step S304; when the device determines that the Request-URI does not meet the matching condition, the process proceeds to step S302. In this step, the device performs the next internal business logic identification (such as forwarding forwarding logic) of the iFC, using the SPT's <1^9 8 13⁄41> and/or <803⁄46&(161"> and other fields in the iFC. The set condition is used as a judgment drive for triggering the internal forward rotation recognition logic of the device, that is, by using the satisfaction condition of the iFC trigger condition, the forward forwarding service identification according to <ApplicationServer> is further triggered.

 Step S304: The device determines whether the < 1 &1101 861^61"> triggered by the STP trigger condition is a full network identification position character.

 When < 1 & 1101 861^61"> identifies the position character for the whole network, the process proceeds to step S305;

 When < 1 & 1101 861^61"> is not the whole network to identify the location character, the process proceeds to step S302. Step S305, the device determines whether the forwarding identifier in <ApplicationServer> triggered by the SPT trigger condition is before Confirm the character.

 Based on the foregoing scenario setting in the embodiment of the present invention, this step is equivalent to determining whether the identification value of "CF" is 1, and CF=1 means that the forwarding identifier is a forwarding confirmation character.

 When the device determines that the forwarding identifier is a forwarding confirmation character, that is, CF=1, the process proceeds to step S306; when the device determines that the forwarding identifier is not a forwarding confirmation character, or does not have a forwarding identifier, that is, CF= When 0 or no CF value, the process proceeds to step S302.

 Step S306: The device identifies that the service corresponding to the message is a forwarding service, and routes the message to the forwarding network.

 According to the actual situation, the corresponding changes or changes in the steps or processes in the embodiments of the present invention do not affect the scope of protection of the patent.

 In order to explain the above identification process more clearly, the embodiment of the present invention describes the above-described method implementation scenario according to a specific application example.

First, it should be noted that the matching condition in the above SPT can support precise configuration, and can also support regular expression configuration. The following description will be based on the specific implementation scenarios.

 Case 1: When the device only identifies the forwarding request for the Request-URI in the message triggered by the AS, it only needs to configure <1 ^^^-13⁄41> as the specified Request-URI in the SPT. , can be an exact value, or it can be a regular expression.

 Specific examples are as follows:

Example 1: When User B needs to be forwarded to C, the device can recognize the forward by the iFC configured as follows (for example: C number is "TEL: +867551234") _:

 <InitialFilterCriteria>

 <Priority>0</Priority>

 <TriggerPoint>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <Request-URI>TEL: +867551234</Request-URI>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <861^6^&1^> The whole network recognizes the position character; CF= 1 </ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria> Example 2: After the AS is triggered, the Request-URI is renamed to a regular matching URI with certain characteristics (for example, a number prefixed with +86755), which is recognized as a forward. The device can perform such identification by an iFC configured as follows.

 <InitialFilterCriteria>

 <Priority>0</Priority>

<TriggerPoint> <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <Request-URI>TEL: +86755(.*)</Request-URI>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <861^6^&1^> The whole network recognizes the position character; CF= 1 </ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria> Case 2: When the device needs to determine the Request-URI before and after the trigger to identify whether it is a forward, that is, the original called before the trigger needs to satisfy a certain condition, and needs to be changed after the AS is triggered. When the Request-URI also satisfies a certain condition, the SPT in the iFC needs to use <81?13⁄4&(161">Configure the History-Info header field, because the History-info header field can correctly represent the original called number before the change. Request-URI.

 Example 3: Set the original called URI before the trigger (for example: the number prefixed with 139) and the triggered Request-URI is a certain feature number (a number prefixed with 86755), then it is recognized as forwarding/ Non-forward, for example, in the same-vibration service, the number prefixed with 86755 is considered to be non-forward, and the other numbers are considered to be forwarded.

 <InitialFilterCriteria>

 <Priority>0</Priority>

 <TriggerPoint>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

<Group>0</Group> <Request-URI>TEL: +86755(.*)</Request-URI>

 </SPT>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <SIPHeader>

 <Header>History-Info</Header>

 <Content>TEL:+139(.*)</Content>

 </SIPHeader>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <ServerName> identifies the location character on the whole network; CF=0</ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria>

 The above matching conditions can only contain <81?13⁄4&(161"> without REQUEST-URI, and the principle is the same, and will not be described again.

 The SPT in iFC can also use the <803⁄46&(161">Configure Diversion header field, because the Diversion header field can also represent the original called Request-URI before the change.

 <InitialFilterCriteria>

 <Priority>0</Priority>

 <TriggerPoint>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <Request-URI>TEL: +86755(.*)</Request-URI>

</SPT> <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <SIPHeader>

 <Header>Diversion</Header>

 <Content>TEL:+139(.*)</Content>

 </SIPHeader>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <ServerName> identifies the location character on the whole network; CF=0</ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria>

 Case 3: When the device needs to determine the difference between the Request-URI before and after the trigger, it is necessary to control whether the difference is the basis for the forward rotation, and the difference is various, by flexibly configuring the History-Info header field. Differences between the original content and the new content The regular expression configures the difference to achieve the effect of control. The original content can be the original URI, and the new content can be a new URI.

 Example 4: After setting the triggering AS, the original Request-URI is changed to a Request-URI that carries certain key parameters (for example, Phone-context or Trunk Grou or cic or rn, etc.), and is recognized as forwarding. The device can perform such identification by an iFC configured as follows.

 <InitialFilterCriteria>

 <Priority>0</Priority>

 <TriggerPoint>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

<Group>0</Group> <Request-URI> (condition) [cic=develop cic](.*)</Request-URI>

 </SPT>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <SIPHeader>

 <Header>History-Info</Header>

 <Content>TEL:! Conditions! </Content>

 </SIPHeader>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <861^6^&1^> The whole network recognizes the position character; CF= 1 </ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria> Example 5: The Request-URI before the trigger is in the TEL format, and the Request-URI after the trigger is the SIP:user=phone format for this number, it is recognized as non-forward.

 <InitialFilterCriteria>

 <Priority>0</Priority>

 <TriggerPoint>

 <ConditionTypeCNF>0</ConditionTypeCNF>

 <SPT>

 <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <Request-URI>SIP: ! condition! @(.*);user=phone</Request-URI>

 </SPT>

<SPT> <ConditionNegated> 1 </ConditionNegated>

 <Group>0</Group>

 <SIPHeader>

 <Header>History-Info</Header>

 <Content>TEL:! Conditions! </Content>

 </SIPHeader>

 </SPT>

 </TriggerPoint>

 <ApplicationServer>

 <ServerName> identifies the location character on the whole network; CF=0</ServerName>

 <DefaultHandling index="0">0</DefaultHandling>

 </ApplicationServer>

 </InitialFilterCriteria> It is pointed out that in the specific application scenarios proposed in the first to the fifth cases corresponding to the above three cases, the AS can be triggered by the flexible adjustment of the forwarding identifier CF. Whether the returned message is accurately identified corresponding to the forwarding service, and the foregoing methods may be used separately or in combination, so that an accurate definition of the attribute of the message to be identified may be implemented, thereby flexibly determining the range of the message to be identified.

 The technical solution of the embodiment of the present invention has the following advantages, because the method for performing forwarding service identification according to the matching condition in one or more SPTs included in the iFC and the corresponding extended parameter is adopted, so that the forwarding can be accurately performed. The identification of services has improved the accuracy of business identification and avoids the waste of communication resources due to misidentification. Further, the fourth embodiment of the present invention also provides a method for acquiring the original called information, and according to the History-Info (history information header field) information carried in the message, the message corresponding to the message before the AS is triggered is obtained. The original called information, the specific flow chart is shown in Figure 4.

Because History-Info is a list list, to accurately obtain the current device, such as the original called information processed by the S-CSCF, can be achieved by the following steps: Step S401: The device acquires a last index (index) in the currently received AS-triggered Invite message (a basic request message in the SIP).

 Step S402: The device acquires, according to the index information, a parent index (index) where the index (the arch) 1 is located, and the information corresponding to the parent index (index) is the message in the AS. The original called information of the message corresponding to the trigger.

 Further, the following scenarios are specifically described. The following scenarios cover various forwarding service points, that is, the acquisition algorithm of History-Info (history information header field) can correctly obtain the original processing by the current device. The called information, wherein for convenience of description with reference to the accompanying drawings, the device is represented by S-CSCF+ uppercase letters, and the Invite message is represented by "request + letter", as the Invite message B is represented as a request: B.

 Scene 1, as shown in Figure 5, two forwards occur in this scenario, the first one is forward (SP, unconditional forward), and the second is late forward (SP, busy forward). Where <B;index=l> (<B; index=1> in the drawing) The following similar reference is expressed in the same figure in the drawing, so it is not explained.) It is the original called, <0^1(1 ^=1.1> is the first called after the unconditional forwarding of the AS triggered by the B user. <D;index=1.2> is the second called after the busy forwarding after the AS is triggered.

 Where <0;^(16 =1.1> and <0; (16 =1.2> is the same level index, and <8;^(16 =1> is <0;^(16 =1.1> and <0;^ (^ =1.2> parent index.

Then, for the S-CSCF2 where the original called B is located, in the first unconditional forward, the obtained original called information is the last 3⁄4<C; index= in the current History-Info of the message after the AS is triggered. Ll^ The URI of the previous index=l, ie <8; (^ =1>, and in the second busy forward, the information of the original called is the current History-Info of the message after the AS is triggered. The last hop of <D;index=1.2:^ The URI of the previous index=l, ie <B;index=l>. Scene 2, as shown in Figure 6, two unconditional forwards occurred in this scenario. In the first unconditional forward, <B;index=l> is the original called, after the B user's AS forwards to <C;index=ll:^ second original called, and in the second unconditional In the forward rotation, <C;index=ll> becomes the original called party, and then goes to the current called party of <D;index=lll> after passing the C user's forward AS. Where <8; (16 =1> is <0^1 (16 =1.1> parent index, and <0;^(16 =1.1> is <0; (^ =1.1.1> parent index) .

 Then S-CSCF2 corresponds to the first unconditional forward, and the original called is the last hop of the last hop <C;index=ll> of the history-Info after the current AS is triggered. URI, SP<B;index=l>; and S-CSCF3 corresponds to the second unconditional forward, and the original called is the last hop in the History-Info after the current trigger <D; index= Lll> The URI of index=ll above, ie <0;^ (^ =1.1>. Scene 3, as shown in Figure 7, three forwards occurred in this scenario, including two unconditional forwards and one encounter Busy forward, in the first unconditional forward, <B;index=l> is the original called, after the B user's AS unconditionally forwarded to C, the second original was added T<C; index=ll> Call, because the C user is busy, then the AS of B performs the second busy forward, forwards to the third original called <D;index=1.2>; the triggered AS of the D user makes the call the third unconditionally Forward, forward to current user E.

 Where <8;^(16 =1> is <0^1(16 =1.1> and <0; (16 =1.2> parent index, and <0; (^ =1.2> is <£; (16 The parent index of =1.2.1>.

， 第二次遇忙前转获取的原被叫就为触发后当前的 History-Info 中最后一跳的 <D;index=1.2:^ 上一级 index=l 的 URI, 即 <B;index=l>。 Then, for S-CSCF2, the original called for the first unconditional forward is the URI of the last index=l of the last hop <0;^ (^ =1.1> in the current History-Info after the trigger. which is

The original called called the second time to get forwarded is the URI of the last hop of the current hop in the current History-Info after the trigger, ie====<B;index= l>.

 For S-CSCF4, the original called is the URI of the previous index=1.2 of <E;index=1.2.1> of the last hop in the current History-Info after the trigger, ie <D;index =1.2>.

By applying the technical solution proposed by the embodiment of the present invention, the device with the called service-call session control function provided by the embodiment of the present invention can utilize the flexible use of the SPT in the iFC and the application of the extended parameter "CF". The S-CSCF can effectively identify the forwarding of the AS after the number is changed in various scenarios, and avoids the change of the part of the route that does not affect the routing when the called party is triggered. The called routing process is additionally performed once, causing the service to fail. The steps of a method or algorithm described in connection with the embodiments disclosed herein may be implemented directly in hardware, a software module executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

 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 identifying a forwarding service, the method comprising:  When the request resource identifier Request-URI in the received message is changed, it is determined whether the message meets the matching condition in one or more service trigger points SPT included in the initial filtering rule iFC;  When the message meets the matching condition in the one or more SPTs included in the iFC, the forward service identification identifier included in the iFC is used to identify whether the service corresponding to the message is a forwarding service.  2. The method according to claim 1, wherein the received message is a message returned by the application server AS after being triggered.  3. The method according to claim 1, wherein the forwarding service identification identifier comprises a server identifier and a forwarding identifier.  4. The method according to claim 1, wherein the matching condition in one or more SPTs included in the iFC is set by an exact value or a regular expression.  The method according to claim 4, wherein the matching condition in one or more SPTs included in the iFC is specifically:  Request-URI content set in the request resource identifier <Request-URI> field in the first SPT; and / or, In the second session of the SPT head Initiation Protocol <SIPHead _er> history information History-info header field set; and / or,  In the third SPT, the <803⁄46&(161"> field setting is transferred to the Diversion header field.  The method according to any one of claims 1 to 4 or 5, wherein the message meets a matching condition in one or more SPTs included in the iFC, and specifically includes:  Determining that the message meets the matching condition when the Request-URI in the message returned by the received AS trigger matches the Content of the Request-URI set in the <Request-URI> field in the first SPT; or , The Request-URI in the message returned after the received AS trigger matches the Request-URI content set in the <Request-URI> field in the first SPT, and the message corresponding to the message before the AS triggers And the <SIPHeader> field set in the second SPT When the information of the History-info header field matches, it is determined that the message meets the matching condition; or, the Request-URI in the message returned after the received AS is triggered and the message corresponding to the message before the AS triggers The difference between the difference relationship and the Request-URI content set in the <Request-URI> field in the first SPT and the difference corresponding to the History-info header field set in the <SIPHeader> field in the second SPT When the sexual relations match, it is judged that the message meets the matching condition; or,  The Request-URI in the message returned after the received AS trigger matches the Request-URI content set in the <Request-URI> field in the first SPT, and is <8 (in the third SPT) 161">When the content set in the Diversion header field of the field setting matches, it is judged that the message meets the matching condition.  The method according to claim 3, wherein the determining, according to the forward forwarding service identification identifier included in the iFC, whether the service corresponding to the message is a forwarding service, specifically: determining the server identifier Whether to identify the location character for the entire network;  When the result of the determination is that the server identifier is a full network identification location character, it is determined whether the forward forwarding identifier is a forward confirmation character;  When the forwarding identifier is a forwarding confirmation character, the service corresponding to the message is identified as a forwarding service.  8. The method of claim 1 further comprising the step of:  When the iFC is configured for a single user, the iFC is configured on a home subscriber server HSS that is subscribed by the single user;  When the iFC is configured for all users of the current network, the iFC is configured on the service-call session control function entity S-CSCF.  The method according to claim 1, further comprising: obtaining, according to the History-Info information carried in the message, the original called information of the message corresponding to the message before the AS is triggered, specifically For:  Obtaining the last index index information in the message returned by the received AS triggering; acquiring the parent index information of the index information according to the index information; The information corresponding to the parent index information is confirmed as the original called information of the message corresponding to the message before the AS is triggered. 10. A device having a service-call session control function, the device comprising:  a matching determining unit, configured to determine, when the Request-URI in the received message is changed, whether the message meets a matching condition in one or more SPTs included in the iFC;  a forward identification unit, configured to identify the message according to the forwarding service identification identifier included in the iFC when the matching determination unit determines that the message meets a matching condition in one or more SPTs included in the iFC Whether the corresponding service is a forward business.  The device according to claim 10, wherein the matching determining unit is specifically configured to receive a message returned by the application server AS, and when the Request-URI in the received message is changed, determine the location Whether the message meets the matching condition in one or more SPTs included in the iFC.  The apparatus according to claim 10, wherein the forwarding identification unit is configured to identify the message according to a type of a server identifier and a forwarding identifier included in the forwarding service identification identifier included in the iFC. Whether the corresponding service is a forward business.  The device according to claim 10, wherein the matching determining unit comprises:  a first determining module, configured to determine whether a Request-URI in the message returned after the received AS is triggered is changed;  a condition obtaining module, configured to: when the first determining module determines that the Request-URI in the message returned after the received AS trigger is changed, returns a message after the home subscription user server HSS or the local AS triggers the received AS trigger a matching condition in one or more SPTs included in the corresponding iFC;  The second determining module is configured to determine whether the message returned by the received AS trigger meets the matching condition acquired by the condition acquiring module.  The apparatus according to claim 12, wherein the forward rotation identification unit comprises:  a third determining module, configured to determine, according to the matching condition, whether the server identifier is a full network identification location character; a fourth determining module, configured to: when the third determining module determines, the server identifier included in the iFC When the location identifier is recognized by the entire network, it is determined whether the forward forwarding identifier is a forwarding confirmation character. When the forward forwarding identifier is a forwarding confirmation character, the service corresponding to the message is identified as a forwarding service.  The device according to claim 10, wherein the device further comprises: an information acquiring unit, configured to: according to the parent index information of the last index index information in the message returned after the received AS is triggered, Obtaining the original called message information of the message corresponding to the message before the AS triggers.