(51) Int Cl.: H04Q 3/00 ( )

Transkript

1 (19) TEPZZ_87684 B_T (11) EP B1 (12) EUROPEAN PATENT SPECIFICATION (4) Date of publication and mention of the grant of the patent: Bulletin 1/13 (21) Application number: (22) Date of filing: (1) Int Cl.: H04Q 3/00 (06.01) (86) International application number: PCT/CN0/ (87) International publication number: WO 06/113 ( Gazette 06/43) (4) Call processing in an intelligent network when the traffic between SSP and SCP is congested Verbindungsbearbeitung in einem intelligenten Netzwerk, wenn der Verkehr zwischen SSP und SCP überlastet ist Traitement d appels dans un réseau intelligent lorsque le trafic entre SSP et SCP est encombré (84) Designated Contracting States: AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR () Priority: CN (43) Date of publication of application: Bulletin 08/02 (73) Proprietor: Huawei Technologies Co., Ltd. Longgang District Shenzhen, Guangdong (CN) (72) Inventors: LI, Shiqian, Huawei Administration Building Guangdong (CN) YAN, Tianjun, Huawei Administration Building Guangdong (CN) (74) Representative: Thun, Clemens Mitscherlich PartmbB Patent- und Rechtsanwälte Sonnenstraße München (DE) (6) References cited: EP-A CN-A CN-A- 1 8 US-A US-A US-B EP B1 Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). Printed by Jouve, 7001 PARIS (FR)

2 1 EP B1 2 Description Field of the Invention [0001] The present invention relates to mobile communication technologies, and more particularly, to a method of ensuring a call for an intelligent user when traffic between a Service Switching Point (SSP) and a Service Control Point (SCP) is abnormal. Background of the Invention [0002] Along with the continuous development of intelligent services, the number of intelligent users rises continuously. To this end, how to ensure normal calls for intelligent users becomes a matter which may influence the quality of service. [0003] Figure 1 is a flowchart of originating a call from a prepaid user. As shown in Figure 1, suppose that the prepaid user is an intelligent user, the specific process of setting up a connection to ensure a call for the prepaid user in the prior art includes the following steps: Step 1: an originating SSP receives a call from a calling prepaid user, and detects an intelligent trigger named Origination_Attempt_Authorized. Step 2: the originating SSP sends an ORREQ message to a corresponding SCP according to the address identified in the trigger. Step 3: the SCP authenticates the calling prepaid user upon receiving the ORREQ message, and judges whether the user is legitimate; if the user is legitimate, proceed to Step ; otherwise, proceed to Step 4. Step 4: the SCP returns an orreq message, carrying in the message parameters ACCEDN and ANNLIST to notify the originating SSP that call processing shall be refused, and then terminates the process. Step : the SCP returns an orreq message, carrying in the message a parameter DMH_SVCIDLIST to notify the originating SSP that call processing shall continue. Step 6: the originating SSP detects an intelligent trigger named Calling_Routing_address_Available, and sends an ANLYZD message to a corresponding SCP according to the address identified in the trigger. Step 7: upon receiving the ANLYZD message, the SCP judges whether the account balance of the user is sufficient to initiate the call; if the account balance is sufficient, proceed to Step 8; otherwise, the SCP notifies the originating SSP to interrupt the call, and terminates the process. Step 8: the SCP notifies the originating SSP to continue the call, and the originating SSP establishes a connection from the calling user to the called user. Then, the calling user may communicate with the called user after receiving a response from the called user. [0004] It can be seen from the above process that the SCP is a core unit of the entire intelligent network for an intelligent service. When an intelligent call arrives, the SCP will send a series of operating instructions to the SSP, instructing the SSP to perform operations according to the established service logics, and the SSP can not independently implement the whole process of intelligent call by itself. [000] In practical implementation of intelligent services, however, abnormal situations may occur between the SSP and the SCP. For example, failures such as disconnection or congestion of a link between the SSP and the SCP may occur, which disables message interaction between the SSP and the SCP, For another example, the SCP, which is busy or in failure, can not send operation instructions to the SSP. Thus, when abnormal situations occur between the SSP and the SCP, the SSP can not acquire the operation instruction from the SCP, and therefore can not perform corresponding operation, which makes call proceeding of intelligent users impossible, and hinders normal operations of intelligent services. Summary [0006] An embodiment of the present invention is to provide a method of ensuring call for an intelligent user such that the SSP can implement the intelligent call in the case when the traffic between the SSP and the SCP becomes abnormal. [0007] The technical solution in accordance with the present invention is achieved as follows. [0008] A method of ensuring call processing for intelligent user, including: judging, by a Service Switching Point (SSP), whether traffic between the SSP and a Service Control Point (SCP) is abnormal; if the traffic is normal, performing an intelligent call connection; if the traffic is abnormal, turning off, by the SSP, intelligent triggers located in the SSP and related to the call, and performing an ordinary call connection. [0009] It can be seen that the method provided in embodiments of the present invention has the following ad- 2

3 3 EP B1 4 vantages: When an SSP detects, during the interaction with an SCP, that the traffic between the SSP and the SCP is abnormal, the SSP will turn off all intelligent triggers involved in the call, and take this call as an ordinary call rather than an intelligent call. Then, no more messages will be sent to the SCP, and the SSP will continue the call processing without instructions from the SCP. That is to say, even if the traffic between the SSP and the SCP is abnormal, normal communications can still be ensured between intelligent users in accordance with the embodiments of the present invention. Brief Description of the Drawings [00] Figure 1 is a flowchart of originating a call from a prepaid user in accordance with the prior art. Figure 2 is a flowchart of originating a call from a calling intelligent user in accordance with an embodiment of the present invention. 1 2 SCP is abnormal, the SSP may firstly acquire the intelligent user identity and the reason for abnormality, and judge whether the intelligent user is permitted to continue with the call connection procedure in this abnormal situation according to the corresponding relation set in advance; if yes, the SSP turns off all the intelligent triggers located in itself and performs the call connection; otherwise, the call connection procedure will no longer be continued, that is, the call is interrupted. [0013] Here, the intelligent user identity may be a number of the user, an addressor of the SCP to which the intelligent user belongs, etc. [0014] The invention is hereinafter described in detail with reference to the accompanying drawings as well as embodiments so as to make objectives, technical solutions and merits of the embodiment of the present invention more clear. [001] In an embodiment of the present invention, an intelligent user identity is a priority level of the intelligent user. [0016] Figure 2 is a flowchart of initiating a call from a calling intelligent user in accordance with the embodiment of the present invention. Referring to Figure 2, the process of initiating a call by an intelligent user includes the following steps: Figure 3 is a flowchart of implementing an inter-office call for the called user in accordance with an embodiment of the present invention. Embodiments of the Invention Step 1: an originating SSP receives a call from a calling intelligent user, and determines whether an abnormal traffic appears between the SSP and the SCP; if yes, proceed to Step 2; otherwise, perform the intelligent call connection according to prior art. [0011] In the prior art, an SSP has to implement call connection procedures for intelligent users following a series of instructions issued by an SCP. Therefore, if some abnormal situations occur between the SSP and the SCP, the call processing of the intelligent user can not be guaranteed. In view of the above, embodiments of the present invention provides a method of ensuring a call for an intelligent user. When the SSP detects that the traffic between the SSP and the SCP is abnormal, the SSP turns off all the intelligent triggers associated with the call, sends no more messages to the SCP, and continues with the call connection procedure without the instruction from the SCP, i.e., the call is handled as an ordinary call other than an intelligent call. Furthermore, if the call is associated with a plurality of SSPs, any one of the associated SSPs which has detected the abnormal situation will notify a subsequent associated SSP to handle the call as an ordinary call. [0012] In practical implementation of a service, if an SSP has to ensure call processing for all intelligent users, service load of the SSP will increase greatly. Therefore, in a preferred embodiment of the present invention, relations among intelligent user identities, reasons for abnormality and whether to perform call connection are set in advance. When the SSP attempts to communicate with the SCP but detects that traffic between the SSP and the [0017] Since the originating SSP has to communicate with the SCP, the originating SSP may firstly detect, when receiving a call from an intelligent user, whether the traffic between the SSP itself and the SCP is abnormal. The detecting process is known, and no more descriptions are given here. For example, an abnormal situation may be that the originating SSP has not received a response message from the SCP for a preset period of time. [0018] Step 2: the originating SSP acquires the priority level of the intelligent user and the reason for abnormality. [0019] The originating SSP acquires the priority level of the intelligent user from user information saved in itself, and determines the reason for abnormality according to the error reason value reported from the bottom layer or returned by the SCP. [00] Step 3: the originating SSP judges whether to continue the call connection; if yes, proceed to Step 4; otherwise, interrupt the call, and finish the process. [0021] Based on relations set in advance among priority levels of intelligent users, reasons for abnormality and whether to perform call connection, the originating SSP judges whether to continue the call connection for the intelligent user, i.e., whether to perform the intelligent call connection, according to the reason for abnormality of the call. For example, the relations set in advance in 3

4 EP B1 6 the originating SSP may include: as to a GSM (Global System for Mobile communication) user which is of higher priority, performing the call connection irrespective of any reason for abnormality between the originating SSP and the SCP; as to a prepaid user which is of lower priority, not performing the call connection in case that the reason for abnormality is that a link is disconnected, and performing the call connection in case that the reason for abnormality is that a link is congested or a signaling point is failed. Thus, if the intelligent user of the call is a GSM user and the reason for abnormality is that the link is disconnected, the originating SSP will perform the call connection; if the intelligent user of the call is a prepaid user and the reason for abnormality is that the link is disconnected, the originating SSP will not perform the call connection. [0022] Step 4: the originating SSP turns off all the intelligent triggers involved in the call. [0023] The originating SSP will not send any message related to the call to the SCP after all the intelligent triggers in the SSP, which are related to the call, are turned off. Moreover, the originating SSP may continue with the call connection procedure without instructions from the SCP, in other words, the originating SSP takes the call as an ordinary call other than an intelligent call. [0024] Step : the originating SSP sets up a connection from the calling user to the called user, and after the called user responds, the calling user may communicate with the called user. [002] Step 6: the originating SSP adds a charging identity into the CDR generated by the originating SSP itself after the call is finished. [0026] The added charging identity is used to indicate that the user of the call is an intelligent user, and the SCP has not charge the intelligent user for the call yet. [0027] Step 7: the originating SSP sends the CDR to a charging center. [0028] In an embodiment of the present invention, since the intelligent triggers located in the SSP are turned off, the SSP may not send messages related to the call to the SCP to which the intelligent user belongs, so that the SCP to which the intelligent user belongs does not charge the intelligent user for the call. Accordingly, in another embodiment of the present invention, a charging identity can be further added into the CDR generated by the SSP to indicate that the call of the intelligent user is normal but the SCP to which the intelligent user belongs does not charge the user, and then the charging center may perform charging according to the CDR, thereby not only ensuring the normal call but also ensuring the normal charging of the intelligent user. [0029] Figure 3 is a flowchart of implementing an interoffice call for the called user in an embodiment of the present invention. Referring to Figure 3, for the inter-office call of an intelligent user, the process of ensuring the call processing includes the following steps: Step 1: a user initiates a call, an originating SSP receives the called number and detects an intelligent trigger named Mobile_Termination. Then, the originating SSP sends a LOCREQ message to a Home Location Register (HLR) according to the address identified in the trigger. Step 2: the HLR returns a locreq message as a response to the originating SSP upon receiving the LOCREQ message. Step 3: the originating SSP determines, upon receiving a locreq message, whether the traffic between the SSP and an SCP is abnormal; if yes, proceed to Step 4; otherwise, perform the intelligent call connection and terminate the process. [00] After receiving the locreq message from the HLR, the originating SSP communicates with the SCP in order to detect whether there is an abnormal traffic between the SSP itself and the SCP. [0031] Step 4: the originating SSP acquires the priority level of the intelligent user and the reason for abnormality. [0032] The originating SSP acquires the priority level of the intelligent user from user information saved in itself, and acquires the reason for abnormality according to the error reason value reported from the bottom layer or returned by the SCP. [0033] Step : the originating SSP judges whether to continue with the call connection procedure; if yes, proceed to Step 6; otherwise, interrupt the call, and terminate the process. [0034] The originating SSP judges whether to continue with the call connection procedure, according to the corresponding relation set in advance in the SSP among the priority level of the intelligent user, the reason for abnormality and whether to perform the call connection. [003] Step 6: the originating SSP turns off all the intelligent triggers located in itself, which are related to the call. [0036] Since all the intelligent triggers related to the call are turned off in the SSP, the SSP will not send any message related to the call to the SCP, and the call connection procedure will be continued without instructions from the SCP. That is to say, the originating SSP can take the call as an ordinary call other than an intelligent call. [0037] Step 7: the originating SSP acquires the called Temporary Local Directory Number (TLDN) from the serving SSP of the called user via the HLR. [0038] Step 8: the originating SSP sends an IAM message containing a call connection service identity to the serving SSP. [0039] Since the originating SSP and the serving SSP are both associated SSPs of the call, the originating SSP shall notify subsequent serving SSPs to handle the call as an ordinary call. A call connection service identity is contained in an IAM message, and the IAM message is 4

5 7 EP B sent to the serving SSP by the originating SSP so as to notify the serving SSP to handle the call as an ordinary call. The call connection service identity may be a call connection prefix added before the called number or calling number or other cells of the IAM message. [00] In addition, the originating SSP uses the IAM message in the ISUP signaling to notify the serving SSP to handle the call as an ordinary call. Moreover, the originating SSP can use a message of other trunk signaling, such as an IAI message in the TUP signaling, or a SETUP message in the PRA signaling, to notify the serving SSP. [0041] Step 9: the serving SSP receives the IAM message, and if learning that the call needs to be handled as an ordinary call according to the call connection service identity in the IAM message, the serving SSP turns off all the triggers located in itself, which are related to the call, and performs the ordinary call connection. [0042] Step 3: the serving SSP adds a charging identity into the CDR generated by the SSP, and sends the CDR to a charging center. [0043] Here, the added charging identity is used for indicating that the call processing of the intelligent user is normal but the SCP to which the intelligent user belongs does not charge the user, and the charging center may charge the user according to the CDR. [0044] When the intelligent user initiates a three-party call or conference call or CALL HOLD or CALL WAIT, that is, when the SSP needs to perform a plurality of call connection procedures for one intelligent user, an embodiment of the present invention can be applied to each call independently. For example, an intelligent user A initiates a three-party call, i.e., simultaneously calls an intelligent user B and an intelligent user C. When the intelligent user A calls the intelligent user B, if the link between the SSP and the SCP is disconnected, the SSP will no longer communicate with the SCP for the call of the intelligent user A, but judge whether to perform the subsequent call connection for the intelligent user A to the intelligent user B according to the acquired priority level of the intelligent user A, the reason for abnormality, namely the link is failed, and the corresponding relation set in advance. Meanwhile, in the process that the intelligent user A calls the intelligent user C, if the link returns to normal when the SSP needs to communicate with the SCP, the SSP may perform the intelligent call connection for the intelligent user A to the intelligent user C according to the instruction from the SCP. After the three-party call ends, the SSP learns, from the generated CDR, that the link is failed in the process that the intelligent user A calls the intelligent user B and the SCP to which the intelligent user A belongs does not charge the user for the call. [004] In the above embodiments, the intelligent user identity is a priority level of the intelligent user. When the intelligent user identity is a number of the intelligent user, the SSP judges whether to perform the call connection for the intelligent user according to the acquired reason for abnormality, the number of the intelligent user, and the corresponding relation set in advance. When the intelligent user identity is an address of the SCP to which the intelligent user belongs, in accordance with the embodiment of the present invention, the SSP judges whether to perform the call connection for the intelligent user according to the acquired reason for abnormality, the address of the SCP namely the SCP to which the intelligent user belongs, and the corresponding relation set in advance. The principle of the specific implementation is the same as the principle of the above process. [0046] It is clear that, in an embodiment of the present invention, relations among intelligent user identities, reasons for abnormality and whether to perform call connection are set in advance. When the SSP attempts to communicate with the SCP but detects that the traffic between the SSP and the SCP is abnormal, the SSP may firstly judge whether to continue the call connection according to the corresponding relation set in advance instead of blindly performing call connections for all the intelligent users, thereby preventing excessive service load on the SSP. [0047] In an embodiment of the present invention, the SSP adds a charging identity into the Call Detail Record (CDR) generated by itself to indicate that the call of an intelligent user is normal, but the SCP to which the intelligent user belongs does not charge the user for the call, thereby not only ensuring normal calls, but further ensuring normal charging, which safeguards the interests of both intelligent users and operators. Claims 1. A method for performing a connection between a calling and a called intelligent user in an intelligent network, the method comprising: judging (1), by a Service Switching Point, SSP, whether traffic between the SSP and a Service Control Point, SCP, is abnormal due to congestion between the SSP and the SCP; if the traffic is normal, performing, by the SSP, an intelligent call connection between the calling and a called intelligent user; if the traffic is abnormal, acquiring (2), by the SSP, a priority level of the calling intelligent user and the reason for the current abnormality, and then judging (3), by the SSP, whether to continue the call connection, if yes, turning off (4), by the SSP, intelligent triggers located in the SSP and related to the call, performing () an ordinary call connection between the calling and the called intelligent user, adding (6), by the SSP, a charging identity into a Call Detail Record, CDR, generated at the SSP when the call is finished, wherein the charging identity indicates that the call of the intelligent user is normal but the SCP to which the intelligent user belongs has not charged the user and sending

6 9 EP B1 (7), by the SSP, the CDR to a charging center, otherwise, terminating the process, wherein the method further comprises: setting in advance, in the SSP, relations among priority levels of intelligent user, reasons for abnormality and whether to perform an ordinary call connection; and wherein the judging whether to continue the call connection is based on the relations set in advance in the SSP. 2. The method of claim 1, wherein the judging whether traffic between the SSP and the SCP is abnormal comprises: judging whether traffic between the SSP and the SCP is abnormal when the SSP conducts message interaction with the SCP. 3. The method of any one of claims 1 and 2, wherein the SSP is a first SSP and the call is associated with a plurality of SSPs, and the first SSP is not a last SSP associated with the call; and the method further comprises: notifying, by the first SSP, subsequent associated SSPs that the call is to be handled as an ordinary call; turning off, by each of the subsequent associated SSPs, the intelligent triggers located in the each of the subsequent associated SSPs itself and related to the call, and performing an ordinary call connection. 4. The method of claim 3, wherein the call is an interoffice call of the called user, and the first SSP is an originating SSP; and the notifying the subsequent associated SSPs by the first SSP, comprises: sending, by the first SSP, a message to a serving SSP, carrying in the message a call connection service identity indicating that the call is to be handled as an ordinary call.. The method of claim 4, wherein the message sent by the first SSP to a serving SSP is an initial address message (IAM) or an initial address message with additional information (IAI) or a call setup (SETUP) message. 6. The method of claim, wherein the carrying in the message the call connection service identity comprises: adding, into the message, a call connection service prefix before a called number or calling number or other cells of the message. 7. The method of any one of claims 1 and 2, wherein the intelligent user which has initiated the call initiates other calls at the same time; and the method further comprises: judging, by the SSP, whether the traffic between the SSP and the SCP is abnormal when setting up a call connection for another call initiated by the intelligent user which has initiated the call; if yes, turning off intelligent triggers located in the SSP and related to the another call, and performing an ordinary call connection; otherwise, performing an intelligent call connection. 8. The method of Claim 7, wherein the call is one of three-party calls or conference calls or CALL HOLD or CALL WAIT for intelligent services. 9. A Service Switching Point, SSP, configured to implement a method comprising: judging (1), by the Service Switching Point, SSP, whether traffic between the SSP and a Service Control Point, SCP, is abnormal due to congestion between the SSP and the SCP; if the traffic is normal, performing, by the SSP, an intelligent call connection between the calling and a called intelligent user; if the traffic is abnormal, acquiring (2), by the SSP, a priority level of the calling intelligent user and the reason for the current abnormality, and then judging (3), by the SSP, whether to continue the call connection, if yes, turning off (4), by the SSP, intelligent triggers located in the SSP and related to the call, performing () an ordinary call connection between the calling and the called intelligent user, adding (6), by the SSP, a charging identity into a Call Detail Record, CDR, generated at the SSP when the call is finished, wherein the charging identity indicates that the call of the intelligent user is normal but the SCP to which the intelligent user belongs has not charged the user and sending (7), by the SSP, the CDR to a charging center, otherwise, terminating the process; wherein, in the SSP, relations among priority levels of intelligent user, reasons for abnormality and whether to perform an ordinary call connection are set in advance; and wherein the SSP is configured to perform the judging whether to continue the call connection on the basis of the relations set in advance in the SSP.. The SSP of claim 9, wherein the SSP is a first SSP and the call is associated with a plurality of SSPs, and the first SSP is not a last SSP associated with the call; the first SSP is configured to notify subsequent as- 6

7 11 EP B1 12 sociated SSPs that the call is to be handled as an ordinary call so as to turn off the intelligent triggers located in the each of the subsequent associated SSPs itself and related to the call, and perform an ordinary call connection by each of the subsequent associated SSPs. 11. The first SSP of claim, wherein the call is an interoffice call of the called user, and the first SSP is an originating SSP; the first SSP is configured to send a message to a serving SSP, carrying in the message a call connection service identity indicating that the call is to be handled as an ordinary call. 12. The SSP of claim 9, wherein the intelligent user which has initiated the call initiates other calls at the same time; the SSP is configured to judge whether the traffic between the SSP and the SCP is abnormal when setting up a call connection for another call initiated by the intelligent user which has initiated the call; if yes, turn off intelligent triggers located in the SSP and related to the another call, and perform an ordinary call connection; otherwise, perform an intelligent call connection. Patentansprüche 1. Verfahren zum Durchführen einer Verbindung zwischen einem anrufenden und einem angerufenen intelligenten Benutzer in einem intelligenten Netzwerk, wobei das Verfahren die folgenden Schritte aufweist: Beurteilen (1) durch einen "Service Switching Point", SSP, ob der Verkehr zwischen dem SSP und einem "Service Control Point", SCP, infolge einer Überlastung zwischen dem SSP und dem SCP anormal ist; wenn der Verkehr normal ist, Durchführen durch den SSP einer intelligenten Rufverbindung zwischen dem anrufenden und einem angerufenen intelligenten Benutzer; wenn der Verkehr anormal ist, Erfassen (2) durch den SSP eines Prioritätsrangs des anrufenden intelligenten Benutzers und des Grunds für die gegenwärtige Anomalität, und dann Beurteilen (3) durch den SSP, ob die Rufverbindung fortgesetzt werden soll, falls ja, Abschalten (4) durch den SSP von intelligenten Triggern, die sich im SSP befinden und den Anruf betreffen, Durchführen () einer gewöhnlichen Rufverbindung zwischen dem anrufenden und dem angerufenen intelligenten Benutzer, Hinzufügen (6) durch den SSP einer Gebührenerfassungsidentität in eine "Call Detail Record", CDR, die am SSP erzeugt wird, wenn der Anruf beendet ist, wobei die Gebührenerfassungsidentität anzeigt, dass der Anruf des intelligenten Benutzers normal ist, jedoch der SCP, zu dem der intelligente Benutzer gehört, vom Benutzer keine Gebühren verlangt hat, und Senden (7) durch den SSP der CDR an ein Gebührenerfassungszentrum, andernfalls Beenden des Prozesses, wobei das Verfahren ferner aufweist: im Voraus Festlegen im SSP von Beziehungen zwischen Prioritätsrängen eines intelligenten Benutzers, Gründen für die Anomalität und ob eine gewöhnliche Rufverbindung durchgeführt werden soll; und wobei das Beurteilen, ob die Rufverbindung fortgesetzt werden soll, auf den im Voraus im SSP festgelegten Beziehungen beruht. 2. Verfahren nach Anspruch 1, wobei das Beurteilen, ob der Verkehr zwischen dem SSP und dem SCP anormal ist, aufweist: Beurteilen, ob der Verkehr zwischen dem SSP und dem SCP anormal ist, wenn der SSP einen Nachrichtenaustausch mit dem SCP durchführt. 3. Verfahren nach einem der Ansprüche 1 und 2, wobei der SSP ein erster SSP ist und der Anruf mit mehreren SSPs verknüpft ist, und der erste SSP nicht ein letzter SSP ist, der mit dem Anruf verknüpft ist; und das Verfahren ferner aufweist: Benachrichtigen durch den ersten SSP nachfolgender verknüpfter SSPs, dass der Anruf als ein gewöhnlicher Anruf behandelt werden soll; Abschalten durch jeden der nachfolgenden verknüpften SSPs der intelligenten Trigger, die sich in jedem der nachfolgenden verknüpften SSPs selbst befinden und den Anruf betreffen, und Durchführen einer gewöhnlichen Rufverbindung. 4. Verfahren nach Anspruch 3, wobei der Anruf ein innerbetrieblicher Anruf des angerufenen Benutzers ist, und der erste SSP ein Ursprungs-SSP ist; und das Benachrichtigen der nachfolgenden verknüpften SSPs durch den ersten SSP aufweist: Senden durch den ersten SSP einer Nachricht an einen bedienenden SSP, wobei in der Nachricht eine Rufverbindungsdienstkennung befördert wird, die anzeigt, dass der Anruf als ein gewöhnlicher Anruf behandelt werden soll.. Verfahren nach Anspruch 4, wobei die Nachricht, die durch den ersten SSP an einen bedienenden SSP gesendet wird, eine Anfangsadressierungsnachricht (initial address message, IAM) oder eine Anfangsa- 7

8 13 EP B1 14 dressierungsnachricht mit zusätzlichen Informationen (initial address message with additional information, IAI) oder eine Anrufaufbau- (call setup, SE- TUP) Nachricht ist. 6. Verfahren nach Anspruch, wobei das Befördern der Rufverbindungsdienstkennung in der Nachricht aufweist: Hinzufügen in die Nachricht eines Rufverbindungsdienstpräfix vor einer angerufenen Nummer oder anrufenden Nummer oder anderen Zellen der Nachricht. 7. Verfahren nach einem der Ansprüche 1 und 2, wobei der intelligente Benutzer, der den Anruf veranlasste, gleichzeitig andere Anrufe veranlasst; und das Verfahren ferner aufweist: Beurteilen durch den SSP, ob der Verkehr zwischen dem SSP und dem SCP anormal ist, wenn eine Rufverbindung für einen anderen Anruf aufgebaut wird, der durch den intelligenten Benutzer veranlasst wird, der den Anruf veranlasst hat; falls ja, Abschalten von intelligenten Triggern, die sich im SSP befinden und den anderen Anruf betreffen, und Durchführen einer gewöhnlichen Rufverbindung; andernfalls Durchführen einer intelligenten Rufverbindung. 8. Verfahren nach Anspruch 7, wobei der Anruf einer von Dreierkonferenzen oder Telefonkonferenzen oder CALL HOLD oder CALL WAIT für intelligente Dienste ist. 1 2 Beurteilen (1) durch den "Service Switching Point", SSP, ob der Verkehr zwischen dem SSP und einem "Service Control Point", SCP, infolge einer Überlastung zwischen dem SSP und dem SCP anormal ist; wenn der Verkehr normal ist, Durchführen durch den SSP einer intelligenten Rufverbindung zwischen dem anrufenden und einem angerufenen intelligenten Benutzer; wenn der Verkehr anormal ist, Erfassen (2) durch den SSP eines Prioritätsrangs des anrufenden intelligenten Benutzers und des Grunds für die gegenwärtige Anomalität, und dann Beurteilen (3) durch den SSP, ob die Rufverbindung fortgesetzt werden soll, falls ja, Abschalten (4) durch den SSP von intelligenten Triggern, die sich im SSP befinden und den Anruf betreffen, Durchführen () einer gewöhnlichen Rufverbindung zwischen dem anrufenden und dem angerufenen intelligenten Benutzer, Hinzufügen (6) durch den SSP einer Gebührenerfassungsidentität in eine "Call Detail Record", CDR, die am SSP erzeugt wird, wenn der Anruf beendet ist, wobei die Gebührenerfassungsidentität anzeigt, dass der Anruf des intelligenten Benutzers normal ist, jedoch der SCP, zu dem der intelligente Benutzer gehört, vom Benutzer keine Gebühren verlangt hat, und Senden (7) durch den SSP der CDR an ein Gebührenerfassungszentrum, andernfalls Beenden des Prozesses; wobei im SSP Beziehungen zwischen Prioritätsrängen eines intelligenten Benutzers, Gründe für die Anomalität und ob eine gewöhnliche Rufverbindung durchgeführt werden soll, im Voraus festgelegt werden; und wobei der SSP konfiguriert ist, das Beurteilen, ob die Rufverbindung fortgesetzt werden soll, auf der Grundlage der im SSP im Voraus festgelegten Beziehungen durchzuführen.. SSP nach Anspruch 9, wobei der SSP ein erster SSP ist und der Anruf mit mehreren SSPs verknüpft ist, und der erste SSP nicht ein letzter SSP ist, der mit dem Anruf verknüpft ist; der erste SSP konfiguriert ist, nachfolgende verknüpfte SSPs zu benachrichtigen, dass der Anruf als ein gewöhnlicher Anruf behandelt werden soll, um die intelligenten Trigger abzuschalten, die sich in jedem der nachfolgenden verknüpften SSPs selbst befinden und den Anruf betreffen, und eine gewöhnliche Rufverbindung durch jeden der nachfolgenden verknüpften SSPs durchzuführen. 9. "Service Switching Point" (SSP), der konfiguriert ist, ein Verfahren zu implementieren, das die folgenden Schritte aufweist: Erster SSP nach Anspruch, wobei der Anruf ein innerbetrieblicher Anruf des angerufenen Benutzers ist, und der erste SSP ein Ursprungs-SSP ist; der erste SSP konfiguriert ist, eine Nachricht an einen bedienenden SSP zu senden, wobei in der Nachricht eine Rufverbindungsdienstkennung befördert wird, die anzeigt, dass der Anruf als ein gewöhnlicher Anruf behandelt werden soll. 12. SSP nach Anspruch 9, wobei der intelligente Benutzer, der den Anruf veranlasst hat, gleichzeitig andere Anrufe veranlasst; der SSP konfiguriert ist zu beurteilen, ob der Verkehr zwischen dem SSP und dem SCP anormal ist, wenn eine Rufverbindung für einen anderen Anruf aufgebaut wird, der durch den intelligenten Benutzer veranlasst wird, der den Anruf veranlasst hat; falls ja, intelligente Trigger abzuschalten, die sich im SSP befinden und den anderen Anruf betreffen, und eine gewöhnliche Rufverbindung durchzuführen; andernfalls eine intelligente Rufverbindung durchzuführen. 8

9 1 EP B1 16 Revendications 1. Procédé pour établir une connexion entre un utilisateur intelligent appelant et un utilisateur intelligent appelé dans un réseau intelligent, le procédé comprenant les étapes suivantes : juger (1), par un point de commutation de services, SSP, si le trafic entre le SSP et un point de contrôle de services, SCP, est anormal du fait d une congestion entre le SSP et le SCP ; si le trafic est normal, établir, par le SSP, une connexion d appel intelligent entre l utilisateur intelligent appelant et un utilisateur intelligent appelé ; si le trafic est anormal, acquérir (2), par le SSP, un niveau de priorité de l utilisateur intelligent appelant et la raison de la présente anormalité, puis juger (3), par le SSP, si la connexion d appel doit être poursuivie ; dans l affirmative, éteindre (4), par le SSP, des déclencheurs intelligents situés dans le SSP et liés à l appel, établir () une connexion d appel ordinaire entre l utilisateur intelligent appelant et l utilisateur intelligent appelé, ajouter (6), par le SSP, une identité de taxation dans un enregistrement des détails des appels, CDR, généré au niveau du SSP lorsque l appel est terminé, où l identité de taxation indique que l appel de l utilisateur intelligent est normal, mais que le SCP auquel l utilisateur intelligent appartient n a pas taxé l utilisateur et envoyer (7), par le SSP, le CDR à un centre de taxation, sinon, mettre fin au processus, où le procédé comprend en outre de définir, à l avance, dans le SSP, des relations parmi les niveaux de priorité d utilisateurs intelligents, des raisons d anormalité et si une connexion d appel ordinaire doit être établie ; et où le jugement si la connexion d appel doit être poursuivie est basé sur les relations définies à l avance dans le SSP. 2. Procédé selon la revendication 1, dans lequel juger si le trafic entre le SSP et le SCP est anormal comprend : notifier, par le premier SSP, des SSP associés subséquents que l appel doit être traité comme un appel ordinaire ; éteindre, par chacun des SSP associés subséquents, les déclencheurs intelligents situés dans chacun des SSP associés subséquents eux-mêmes et liés à l appel, et établir une connexion d appel ordinaire. 4. Procédé selon la revendication 3, dans lequel l appel est un appel interne de l utilisateur appelé, et le premier SSP est un SSP d origine ; et la notification des SSP associés subséquents, par le premier SSP, comprend les étapes suivantes : envoyer, par le premier SSP, un message à un SSP de desserte, acheminer dans le message une identité de service de connexion d appel indiquant que l appel doit être traité comme un appel ordinaire.. Procédé selon la revendication 4, dans lequel le message envoyé par le premier SSP à un SSP de desserte est un message d adresse initiale (IAM) ou un message d adresse initiale avec informations additionnelles (IAI) ou un message d établissement d appel (SETUP). 6. Procédé selon la revendication, dans lequel l acheminement dans le message de l identité de service de connexion d appel comprend d ajouter, dans le message, un préfixe de service de connexion d appel avant un numéro appelé ou un numéro appelant ou d autres cellules du message. 7. Procédé selon l une quelconque des revendications 1 à 2, dans lequel l utilisateur intelligent qui a initié l appel initie d autres appels en même temps ; et le procédé comprend en outre les étapes suivantes : juger, par le SSP, si le trafic entre le SSP et le SCP est anormal lors de la configuration d une connexion d appel pour un autre appel initié par l utilisateur intelligent qui a initié l appel ; dans l affirmative, éteindre les déclencheurs intelligents situés dans le SSP et liés à l autre appel, et procéder à une connexion d appel ordinaire ; sinon, procéder à une connexion d appel intelligent. de juger si le trafic entre le SSP et le SCP est anormal lorsque le SSP conduit une interaction de message avec le SCP. 3. Procédé selon l une quelconque des revendications 1 et 2, dans lequel le SSP est un premier SSP et l appel est associé à une pluralité de SSP, et le premier SSP n est pas un dernier SSP associé à l appel ; et le procédé comprend en outre les étapes suivantes : 0 8. Procédé selon la revendication 7, dans lequel l appel est un appel parmi des appels à trois participants, ou des appels de conférence, ou une mise en attente (CALL HOLD) ou en instance (CALL WAIT) pour des services intelligents. 9. Point de commutation de services, SSP, configuré pour implémenter un procédé comprenant les étapes suivantes : 9

10 17 EP B1 18 juger (1), par le point de commutation de services, SSP, si le trafic entre le SSP et un point de contrôle de services, SCP, est anormal du fait d une congestion entre le SSP et le SCP ; si le trafic est normal, établir, par le SSP, une connexion d appel intelligent entre l utilisateur intelligent appelant et un utilisateur intelligent appelé ; si le trafic est anormal, acquérir (2), par le SSP, un niveau de priorité de l utilisateur intelligent appelant et la raison de la présente anormalité, puis juger (3), par le SSP, si la connexion d appel doit être poursuivie ; dans l affirmative, éteindre (4), par le SSP, des déclencheurs intelligents situés dans le SSP et liés à l appel, établir () une connexion d appel ordinaire entre l utilisateur intelligent appelant et l utilisateur intelligent appelé, ajouter (6), par le SSP, une identité de taxation dans un enregistrement des détails des appels, CDR, généré au niveau du SSP lorsque l appel est terminé, où l identité de taxation indique que l appel de l utilisateur intelligent est normal, mais que le SCP auquel l utilisateur intelligent appartient n a pas taxé l utilisateur et envoyer (7), par le SSP, le CDR à un centre de taxation, sinon, mettre fin au processus ; où, dans le SSP, des relations parmi les niveaux de priorité d utilisateurs intelligents, des raisons d anormalité et si une connexion d appel ordinaire doit être établie sont définies à l avance ; et où le SSP est configuré pour juger si la connexion d appel doit être poursuivie sur la base des relations définies à l avance dans le SSP SSP selon la revendication 9, dans lequel l utilisateur intelligent qui a initié l appel initie d autres appels en même temps ; le SSP est configuré pour juger si le trafic entre le SSP et le SCP est anormal lors de la configuration d une connexion d appel pour un autre appel initié par l utilisateur intelligent qui a initié l appel ; dans l affirmative, éteindre les déclencheurs intelligents situés dans le SSP et liés à l autre appel, et procéder à une connexion d appel ordinaire ; sinon, procéder à une connexion d appel intelligent.. Procédé selon la revendication 9, dans lequel le SSP est un premier SSP, et l appel est associé à une pluralité de SSP, et le premier SSP n est pas un dernier SSP associé à l appel ; le premier SSP est configuré pour notifier aux SSP associés subséquents que l appel doit être traité comme un appel ordinaire de manière à éteindre les déclencheurs intelligents situés dans chacun des SSP associés subséquents eux-mêmes et liés à l appel, et établir une connexion d appel ordinaire par chacun des SSP associés subséquents Premier SSP selon la revendication, dans lequel l appel est un appel interne de l utilisateur appelé, et le premier SSP est un SSP d origine ; le premier SSP est configuré pour envoyer un message à un SSP de desserte, acheminer dans le message une identité de service de connexion d appel indiquant que l appel doit être traité comme un appel ordinaire. 0

11 EP B1 11

12 EP B1 12

13 EP B1 13