CN101207928B - System and method for triggering intelligence business - Google Patents

System and method for triggering intelligence business Download PDF

Info

Publication number
CN101207928B
CN101207928B CN2007101956258A CN200710195625A CN101207928B CN 101207928 B CN101207928 B CN 101207928B CN 2007101956258 A CN2007101956258 A CN 2007101956258A CN 200710195625 A CN200710195625 A CN 200710195625A CN 101207928 B CN101207928 B CN 101207928B
Authority
CN
China
Prior art keywords
service
intelligent
processing subsystem
trigger
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN2007101956258A
Other languages
Chinese (zh)
Other versions
CN101207928A (en
Inventor
冼旭和
杨青山
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2007101956258A priority Critical patent/CN101207928B/en
Publication of CN101207928A publication Critical patent/CN101207928A/en
Application granted granted Critical
Publication of CN101207928B publication Critical patent/CN101207928B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the invention discloses an intelligent triggering system, comprising a first intelligent service processing subsystem, a second intelligent service processing subsystem and a secondary triggering cascade subsystem, wherein, the first intelligent service processing subsystem is used for processing a first intelligent service signed by a user and for informing the secondary triggering cascade subsystem to process; the secondary triggering cascade subsystem is used for judging whether the user signs more than two intelligent services, if the user signs more than two intelligentservices, the secondary triggering cascade subsystem informs the second intelligent service processing subsystem to process and records that what the first intelligent service processing subsystem and the second intelligent service processing subsystem process are different intelligent services in the same call of the same user; the second intelligent service processing subsystem is used for processing the second intelligent service signed by the user. The intelligent triggering system can realize a plurality of intelligent services in the same call of the same user.

Description

A kind of IN service trigger method and system
Technical field
The present invention relates to the communications field, particularly relate to a kind of IN service trigger method and system.
Background technology
Along with developing rapidly of intelligent mobile network, many intelligent protocols based on intelligent mobile network have appearred.The appearance of intelligent protocol is in order to realize separating of business and exchange, picture PPS (Pre-aidService has appearred, prepayment service) and unusual typical application such as MVPN (Mobile Virtual Private Network, mobile virtual private network), for operator provides convenience.
CAMEL (Customized applications for Mobile Network Enhanced Logic, customization application based on mobile network's enhanced logic) appearance is can provide the business operation mechanism that is independent of service network for mobile network equally.CAMEL provides a kind of supplementary service, and provides a kind of network characterization.This feature reduction the control outside service network, business carried out of service operation person.Therefore, the CAMEL business can make the network operator that the network operator is provided self-determining business, even the user roams out HPLMN (Home Public and Mobile Network, home public land mobile network network), also can not impact for the operation of business.
Based on the IN service of CAMEL at existing network MSC/VLR (Mobile Switching Center/Visited Location Register, mobile switching center) goes up stack gsmSSF (GSM Service Switching Function, GSM Service Switch Function), gsmSSF is according to gsmSCF (GSM Service Control Function, GSM Service Control Function) requirement reports relevant information (as the positional information at active user place) or dependent event (as the called subscriber answer incident) to give gsmSCF, and gsmSCF is the business to realize being correlated with according to these information or incident control service logic.Support the networking of CAMEL system functional entity as shown in Figure 1, its networking function entity mainly comprises: HLR (Home Location Register, attaching position register), gsmSCF, gsmSSF, GMSC (Gateway MSC, mobile gateway switching center), VLR (Visited Location Register, VLR Visitor Location Register), MSC (Mobile Switching Center, mobile switching centre) and gsmSRF (GSM Specialized Resource Function, special resource function).Wherein the interface between HLR and gsmSCF, GMSC, VLR is MAP (Mobile application Part, a MAP); Interface between GMSC and MSC is MAP; Interface between gsmSCF and gsmSSF, gsmSRF is CAP (CAMEL Application Part, a CAMEL Application Part).
Present based on the CAMEL IN service in, in same user's a same calling procedure, can only trigger IN service one time in MO (Mobile Originating, mobile originating) or MT (Mobile Terminating, the mobile terminating) IN service.Such as: if user A is the intelligent subscriber that starts, dial user B, gsmSSF triggers the IN service that starts of user A, and only triggers once.The IN service more than two if user A has contracted, gsmSSF can discharge this to be called out, thereby can not realize the IN service that secondary is above.
Summary of the invention
Embodiments of the invention provide a kind of IN service trigger method and device, realize that same user is triggering twice above IN service in once calling out.
For achieving the above object, embodiments of the invention provide a kind of IN service trigger method, comprise step: after the receipt of call request, first IN service if the user has contracted, the intelligent trigger system sends the first IN service control request to first service control point (SCP); After receiving that a described SCP calls out the notice that continues, user's two above IN services of whether having contracted are judged by described intelligent trigger system, if then send the second IN service control request to the 2nd SCP of the second IN service correspondence, writing down described first IN service control request and the described second IN service control request is the different intelligent professional control request of same user in once calling out together, and continues to handle described calling according to the control of described the 2nd SCP.
For achieving the above object, embodiments of the invention also provide a kind of intelligent trigger system, comprise: the first IN service processing subsystem, the second IN service processing subsystem, secondary trigger the cascade subsystem, wherein: the described first IN service processing subsystem is used for the first signatory IN service of process user, and notifies described secondary to trigger the cascade subsystem and handle; Described secondary triggers the cascade subsystem and is used to judge user's two above IN services of whether having contracted, handle if then notify the described second IN service processing subsystem, and what write down that the described first IN service processing subsystem and the second IN service processing subsystem handle is same user with the different intelligent business in once calling out, otherwise continues to handle to the first IN service processing subsystem call handoff; The described second IN service processing subsystem is used for the second signatory IN service of process user.
After receiving that continuation that a SCP sends is handled after the notice of calling out or received second request response that HLR returns, judge user's two above IN services of whether having contracted again, trigger flow process if then carry out the secondary IN service, and to write down the first IN service control request and the described second IN service control request be same user with the professional control request of different intelligent in once calling out, what write down the processing of the described first IN service processing subsystem and the second IN service processing subsystem is the different intelligent business of same user in once calling out together, thereby has realized that same user is realizing repeatedly IN service in once calling out.
In addition, after detecting call event, earlier whether determine Event Report BCSM, and then whether determine Event Report BCSM, thereby whether can determine Event Report BCSM according to the control of corresponding SCP and do not interact according to the control of the 2nd SCP according to the control of a SCP.
Description of drawings
Fig. 1 is the functional entity networking schematic diagram based on the IN service of CAMEL;
Fig. 2 is the signaling process figure of the mobile originating MO IN service of the embodiment of the invention one;
Fig. 3 is the method flow diagram of the mobile originating MO IN service of the embodiment of the invention one;
Fig. 4 is the method flow diagram of the mobile terminating MT IN service of the embodiment of the invention two;
Fig. 5 is the signaling process figure of the mobile terminating MT IN service of the embodiment of the invention two;
Fig. 6 is the schematic diagram of the embodiment of the invention three.
Embodiment
Below in conjunction with drawings and Examples, the specific embodiment of the present invention is described in further detail:
See also Fig. 2, Fig. 3, the mobile originating MO IN service flow chart for the embodiment of the invention one specifically may further comprise the steps:
Step S301, the user dials called number, the intelligent trigger system is after for example switching equipment is received calling subscriber's call request, set up first Call Control Block, this first Call Control Block is used to control this to be called out, and carries out intelligent trigger for the first intelligent trigger module of intelligent trigger system call handoff and handle.
Step S302, the first intelligent trigger module is judged this calling subscriber first IN service of whether having contracted, as OCSI (Originating CAMEL Subscription Information, the mobile originating CAMEL Subscription Information), T-CSI (Terminating CAMEL Subscription Information, the mobile terminating CAMEL Subscription Information), if, execution in step S303 then, otherwise carry out rapid S304.
Step S303, the first intelligent trigger module sends the first IN service control request to first service control point (SCP), sends Initial Detection Point InitialDP message as the first intelligent trigger module to a SCP.
In addition, the first intelligent trigger module is set up the first intelligent event processing module, carries out rapid S305 then.
Step S304, the first intelligent trigger module notifies first Call Control Block to continue call treatment.
Step S305, a SCP sends the report solicited message to the intelligent trigger system.
For example a SCP sends report information to the first intelligent event processing module, this report solicited message comprises: request report BCSM event message RequestReportBCSM, be used to ask this first intelligent event processing module to report the incident that this event information is relevant with configuration, as caller abandon, called party answer, route selection failure, caller are taken out stitches, called information such as take out stitches; Charging solicitation message ApplyCharging is used to ask this first intelligent event processing module under satisfying condition the calling subscriber to be chargeed, and the report charging result.
Step S306, the first intelligent trigger module of notifying the one SCP continues to handle to call out, for example a SCP sends Continue or Connect message to the first intelligent trigger module, request continues to handle calls out, the first intelligent trigger module is with the control of call handoff first Call Control Block then, and first Call Control Block triggers cascade module control with call handoff to secondary.
Step S307, secondary triggers cascade module and judges user's two above IN services of whether having contracted, if set up second Call Control Block, give the control of second Call Control Block with call handoff, and the calling of writing down first Call Control Block and the processing of second Call Control Block is same user's same once calling, execution in step S308 then; Otherwise secondary triggers cascade module and notifies first Call Control Block to continue to handle calling, as the called or out processing of paging.
Step S308, second Call Control Block is given the second intelligent trigger module with call handoff, the second intelligent trigger module is judged user's second IN service of whether having contracted, as DCSI (Dialed ServiceCAMEL Subscription Information, Dialled Services CAMEL Subscription Information) or NCSI (Network Service CAMEL Subscription Information, Network CAMEL Subscription Information), if having, execution in step S309 then, otherwise execution in step S310.
Wherein the priority of first IN service is higher than the priority of second IN service.
Step S309, the second intelligent trigger module sends the second IN service control request to the 2nd SCP, send Initial Detection Point InitialDP message as the second intelligent trigger module to the 2nd SCP, and set up the second intelligent event processing module, execution in step S311 then, wherein said first IN service control request and the described second IN service control request are same user with the professional control request of different intelligent in once calling out.
Step S310, the second intelligent trigger module is notified first Call Control Block to continue to handle by second Call Control Block and is called out, as the called or out processing of paging.
Step S311, the 2nd SCP sends the report solicited message to the second intelligent event processing module.
For example this report solicited message comprises: request report BCSM event message RequestReportBCSMEvent, be used to ask this first intelligent event processing module to report the incident that this event information is relevant with configuration, as caller abandon, called party answer, route selection failure, caller are taken out stitches, called information such as take out stitches; Charging solicitation message ApplyCharging is used to ask this first intelligent event processing module under satisfying condition the calling subscriber to be chargeed, and the report charging result.
Step S312, the second intelligent trigger module of notifying the 2nd SCP continues to handle to call out, for example the 2nd SCP sends Continue or Connect message to the second intelligent trigger module, and request continues to handle calls out, and the second intelligent trigger module is controlled call handoff second Call Control Block then.
Step S313, if the user contracts is two IN services, and the called subscriber is when being the local subscriber, second Call Control Block carries out paging to be handled; If what the user contracted is two IN services, and the called subscriber is not when being not the local subscriber, and second Call Control Block carries out striking out to be handled; If the user contracts is IN service more than three, second Call Control Block triggers cascade module with call handoff to secondary and handles, secondary triggers cascade module and sets up the 3rd Call Control Block, and concrete process is identical with the flow process of second IN service, therefore repeats no more.
Step S314, whether the first intelligent event processing module reports response message to SCP transmission according to the control decision of a SCP after detecting call event, it is Event Report BCSM, trigger cascade module to secondary then and send call event, secondary triggers cascade module and sends call event to the second intelligent event processing module, receives whether the second intelligent event processing module behind the call event sends the report response message according to the control decision of the 2nd SCP.
After first Call Control Block of embodiment one receives that calling is handled in the continuation of SCP transmission, give two to trigger cascade module this call handoff, trigger cascade module by secondary and judge calling subscriber's two above IN services of whether having contracted, trigger flow process if then carry out the secondary IN service, and the calling of writing down first Call Control Block and the processing of second Call Control Block is that the same of same user once calls out, the first IN service control request and the described second IN service control request are recorded as the different intelligent professional control request of same user in once calling out together, thereby solved first Call Control Block and second Call Control Block same user's same once the calling regarded as independently two Call Collision problems that calling brings, and coordinate the operation of first Call Control Block and second Call Control Block, thereby realized that same user is realizing repeatedly IN service in once calling out.
In addition, when whether the first intelligent event processing module determines Event Report BCSM according to the control of a SCP after, secondary cascaded triggering module notifies the second intelligent event processing module whether to determine Event Report BCSM according to the control of the 2nd SCP, makes win intelligent event processing module and the second intelligent event processing module whether can determine Event Report BCSM according to the control of corresponding SCP and does not interact.
See also Fig. 4, Fig. 5, the mobile terminating MT IN service flow chart for the embodiment of the invention two specifically may further comprise the steps:
Step S401, the user dials called number, after the intelligent trigger system receives and sets up call request, sets up first Call Control Block, this first Call Control Block is used to control this calling, and carries out intelligent trigger for the first intelligent trigger module call handoff and handle.
Step S402, first Call Control Block sends the first roaming number request message to HLR, and for example first Call Control Block sends a SRI (Send Routing Information sends routing iinformation) message to HLR, to HLR request roaming number.
Step S403, HLR returns first request response to first Call Control Block, for example HLR returns SRI-ACK message to first Call Control Block, carries T-CSI (TerminatingCAMEL Subscription Information mobile terminating CAMEL Subscription Information) in the message.
Step S404, first Call Control Block is given the first intelligent trigger module with call handoff, the first intelligent trigger module is judged this called subscriber first IN service of whether having contracted, as T-CSI (Terminating CAMEL Subscription Information, the mobile terminating CAMEL Subscription Information), if, execution in step S405 then, otherwise execution in step S406.
Step S405, the first intelligent trigger module sends the first IN service control request to a SCP, sends Initial Detection Point InitialDP message as the first intelligent trigger module to a SCP, and sets up the first intelligent event processing module, carries out rapid S407 then.
Step S406, the first intelligent trigger module notifies first Call Control Block to continue call treatment, as the called or out processing of paging.
Step S407, a SCP sends the report solicited message to the intelligent trigger system.
For example a SCP sends the report solicited message to the first intelligent event processing module, this report solicited message comprises: request report BCSM event message RequestReportBCSMEvent, be used to ask this first intelligent event processing module to report the incident that this event information is relevant with configuration, as caller abandon, called party answer, route selection failure, caller are taken out stitches, called information such as take out stitches; Charging solicitation message ApplyCharging is used to ask this first intelligent event processing module under satisfying condition the calling subscriber to be chargeed, and the report charging result.
Step S408, the first intelligent trigger module of notifying the one SCP continues to handle to call out, for example a SCP sends Continue or Connect message to the first intelligent trigger module, and request continues to handle calls out, and the first intelligent trigger module is controlled call handoff first Call Control Block then.
Step S409, first Call Control Block sends the second roaming number request message to HLR, and for example first Call Control Block sends the 2nd SRI message to HLR.
Step S410, HLR returns second request response to first Call Control Block, and for example HLR returns SRI-ACK message to first Call Control Block, carries MSRN (MobileStation Roaming Number, mobile subscriber roam sign indicating number) in the message.
Step S411, first Call Control Block triggers cascade module control with call handoff to secondary.
Step S412, secondary triggers cascade module and judges user's two above IN services of whether having contracted, if set up second Call Control Block, give the control of second Call Control Block with call handoff, and the calling of writing down first Call Control Block and the processing of second Call Control Block is that the same of same user once calls out, execution in step 413 then, notify first Call Control Block to continue to handle calling otherwise secondary triggers cascade module, as the called or out processing of paging.
Step S413, second Call Control Block is given the second intelligent trigger module controls with call handoff, and the second intelligent trigger module is according to MSRN inquiring user second IN service of whether having contracted, as NCSI, if having, execution in step S414 then, if no, execution in step S415 then.
Wherein the priority of first IN service is higher than second IN service.
Step S414, the second intelligent trigger module sends the second IN service control request to the 2nd SCP, sends Initial Detection Point InitialDP message as the second intelligent trigger module to the 2nd SCP, and sets up the second intelligent event processing module, execution in step S416 then.
Wherein, the first IN service control request and the described second IN service control request are the different intelligent professional control request of same user in once calling out together.
Step S415, the second intelligent trigger module triggers cascade module control with call handoff to secondary by second Call Control Block, and secondary triggering cascade module is notified first Call Control Block to continue to handle and is called out, as the called or out processing of paging.
Step S416, the 2nd SCP sends the report solicited message to the second intelligent event processing module.
For example this report solicited message comprises: request report BCSM event message RequestReportBCSMEvent, be used to ask this first intelligent event processing module to report the incident that this event information is relevant with configuration, as caller abandon, called party answer, route selection failure, caller are taken out stitches, called information such as take out stitches; Charging solicitation message ApplyCharging is used to ask this first intelligent event processing module under satisfying condition the calling subscriber to be chargeed, and the report charging result.
Step S417, the second intelligent trigger module of notifying the 2nd SCP continues to handle to call out, for example the 2nd SCP sends Continue or Connect message to the second intelligent trigger module, and request continues to handle calls out, and the second intelligent trigger module is controlled call handoff second Call Control Block then.
Step S418, if the user contracts is twice IN service, and the called subscriber is when being the local subscriber, second Call Control Block carries out paging to be handled; If what the user contracted is twice IN service, and the called subscriber is not when being not the local subscriber, and second Call Control Block carries out striking out to be handled; If the user contracts is IN service more than three times, second Call Control Block triggers cascade module with call handoff to secondary and handles, secondary triggers cascade module and sets up the 3rd Call Control Block, and concrete process is identical with the flow process of the intelligent trigger second time, therefore repeats no more.
Step S419, whether the first intelligent event processing module reports response message to SCP transmission according to the control decision of a SCP after detecting call event, it is Event Report BCSM, trigger cascade module to secondary then and send call event, secondary triggers cascade module and sends call event to the second intelligent event processing module, receives whether the second intelligent event processing module behind the call event sends the report response message according to the control decision of the 2nd SCP.
After first Call Control Block of embodiment two is received second request response that HLR returns, this call handoff is triggered cascade module to secondary, trigger cascade module by secondary and judge calling subscriber's two above IN services of whether having contracted, trigger flow process if then carry out the secondary IN service, and the calling of writing down first Call Control Block and the processing of second Call Control Block is that the same of same user once calls out, the first IN service control request and the described second IN service control request are recorded as the different intelligent professional control request of same user in once calling out together, thereby solved first Call Control Block and second Call Control Block same user's same once the calling regarded as independently two Call Collision problems that calling brings, and coordinate the operation of first Call Control Block and second Call Control Block, thereby realized that same user is realizing repeatedly IN service in once calling out.
In addition, when whether the first intelligent event processing module determines Event Report BCSM according to the control of a SCP after, secondary cascaded triggering module notifies the second intelligent event processing module whether to determine Event Report BCSM according to the control of the 2nd SCP, makes win intelligent event processing module and the second intelligent event processing module whether can determine Event Report BCSM according to the control of corresponding SCP.
See also Fig. 6, be the schematic diagram of the embodiment of the invention three, this communication system comprises: IN service triggering system 61, the one SCP entity 62, the 2nd SCP entity 63 and HLR entity 64, wherein, intelligent trigger system 61 links to each other with HLR entity 64 with a SCP entity 62, the 2nd SCP entity 63 respectively.
IN service triggering system 61 further comprises: the first IN service processing subsystem 611, the second IN service processing subsystem 612, secondary trigger cascade subsystem 613, wherein:
The first IN service processing subsystem 611 is used for the first signatory IN service of process user, and notice secondary triggering cascade subsystem 613 is handled;
Secondary triggers cascade subsystem 613 and is used to judge user's two above IN services of whether having contracted, handle if then notify the second IN service processing subsystem 612, and to write down IN service that the first IN service processing subsystem 611 and the second IN service processing subsystem 612 handle be same user with the different intelligent business in once calling out, otherwise continue to handle to the first IN service processing subsystem 611 call handoff;
The second IN service processing subsystem 612 is used for the second signatory IN service of process user.
If what the user contracted is two IN services, and the called subscriber is the local subscriber, handles behind second IN service described second IN service processing subsystem 612 and also is used to carry out paging and handles.
If what the user contracted is two IN services, and the called subscriber is not the local subscriber, handles behind second IN service described second IN service processing subsystem 612 and also is used to carry out striking out and handles.
If what the user contracted is three above IN services, handles behind second IN service described second IN service processing subsystem 612 and also be used for triggering cascade subsystem 613 and send and call out the notice that continues to described secondary.After described secondary triggering cascade subsystem 613 receives that the calling of the second IN service processing subsystem 612 continues notice, set up the 3rd IN service processing subsystem and notify the 3rd IN service processing subsystem to handle, the 3rd IN service that the 3rd IN service processing subsystem process user is signatory.
Wherein, the priority of the described first intelligence business, second IN service, the 3rd IN service reduces successively.
After detecting call event, the described first IN service processing subsystem 611 also is used for decision and whether reports described call event, and described call event is triggered cascade subsystem 613 by described secondary send to the described second IN service processing subsystem 612, the described second IN service processing subsystem 612 receives described call event, and whether decision reports described call event.
If the mobile terminating IN service, the described first IN service processing subsystem 611 also was used for sending the first roaming number request to HLR before first IN service that process user is contracted, and received the first roaming number request response that described HLR returns; And also be used for sending the second roaming number request before handling notifying described secondary to trigger cascade subsystem 613, and receive the described second roaming number request response of returning with R to described HLR.
Wherein, the first IN service processing subsystem 611, the second IN service subsystem, the 3rd IN service subsystem also comprise respectively: Call Control Block, intelligent trigger module, intelligent event processing module.
This Call Control Block is used for calling out control;
This intelligent trigger module is used for triggering intelligence according to user's CAMEL-Subscription-Information;
Whether this intelligence event processing module is used to determine Event Report BCSM.
Through the above description of the embodiments, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium, comprise that some instructions are with so that a computer equipment (can be a personal computer, server, the perhaps network equipment etc.) carry out the method for each embodiment of the present invention.
Only be embodiments of the present invention below, should be pointed out that for those skilled in the art that under the prerequisite that does not break away from the principle of the invention, can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.

Claims (16)

1. an IN service trigger method is characterized in that, may further comprise the steps:
After the receipt of call request, first IN service if the user has contracted, the intelligent trigger system sends the first IN service control request to first service control point (SCP);
After receiving that a described SCP calls out the notice that continues, user's two above IN services of whether having contracted are judged by described intelligent trigger system, if then send the second IN service control request to the 2nd SCP of the second IN service correspondence, writing down described first IN service control request and the described second IN service control request is the different intelligent professional control request of same user in once calling out together, and continues to handle described calling according to the control of described the 2nd SCP.
2. IN service trigger method according to claim 1 is characterized in that, if the user contracts is two IN services, described intelligent trigger system continues to handle described calling according to the control of described the 2nd SCP and comprises:
If the called subscriber is the local subscriber, described intelligent trigger system carries out paging and handles;
If the called subscriber is not the local subscriber, described intelligent trigger system carries out striking out and handles.
3. IN service trigger method according to claim 1 is characterized in that, if the user contracts is three above IN services, described intelligent trigger system continues to handle described calling according to the control of described the 2nd SCP and comprises:
After receiving that described the 2nd SCP calls out the notice that continues, described intelligent trigger system sends the 3rd IN service control request to the Three S's CP of the 3rd IN service correspondence, and to write down the described first IN service control request, the described second IN service control request and described the 3rd IN service control request be same user with the professional control request of different intelligent in once calling out, and continue to handle described calling according to the control of described Three S's CP.
4. IN service trigger method according to claim 1, it is characterized in that, also comprise step: after detecting call event, whether the decision of described intelligent trigger system reports described call event to a described SCP, and whether decision reports described call event to described the 2nd SCP then.
5. IN service trigger method according to claim 1, it is characterized in that, for the mobile terminating IN service, after the receipt of call request of described intelligent trigger system and described intelligent trigger system before a SCP sends the first IN service control request, also comprise step:
Described intelligent trigger system sends the first roaming number request message to HLR, and receives the first roaming number request response that described HLR returns, and carries the mobile terminating CAMEL-Subscription-Information in the described response message.
6. IN service trigger method according to claim 5 is characterized in that, receive a described SCP call out the notice that continues after and described intelligent trigger system judge whether the user has contracted and also comprise step before two above IN services:
Described intelligent trigger system sends the second roaming number request message to described HLR, and receives the second roaming number request response that described HLR returns.
7. IN service trigger method according to claim 1 is characterized in that, the priority of first IN service that described user contracts is higher than the priority of described second IN service.
8. an intelligent trigger system is characterized in that, comprising: the first IN service processing subsystem, the second IN service processing subsystem, secondary trigger the cascade subsystem, wherein:
The described first IN service processing subsystem is used for the first signatory IN service of process user, and notifies described secondary to trigger the cascade subsystem and handle;
Described secondary triggers the cascade subsystem and is used to judge user's two above IN services of whether having contracted, handle if then notify the described second IN service processing subsystem, and what write down that the described first IN service processing subsystem and the second IN service processing subsystem handle is same user with the different intelligent business in once calling out, otherwise continues to handle to the first IN service processing subsystem call handoff;
The described second IN service processing subsystem is used for the second signatory IN service of process user.
9. intelligent trigger according to claim 8 system, it is characterized in that, if what the user contracted is two IN services, and the called subscriber is the local subscriber, handles behind second IN service described second IN service processing subsystem and also is used to carry out paging and handles; Or
If what the user contracted is two IN services, and the called subscriber is not the local subscriber, handles behind second IN service described second IN service processing subsystem and also is used to carry out striking out and handles.
10. intelligent trigger according to claim 8 system, it is characterized in that, if what the user contracted is three above IN services, handles behind second IN service described second IN service processing subsystem and also be used for triggering the cascade subsystem and send and call out the notice that continues to described secondary.
11. intelligent trigger according to claim 10 system is characterized in that, described intelligent trigger system also comprises the 3rd IN service processing subsystem, is used for the 3rd signatory IN service of process user; After described secondary triggering cascade subsystem receives that the calling of the described second IN service processing subsystem continues notice, notify described the 3rd IN service processing subsystem to handle.
12. intelligent trigger according to claim 8 system, it is characterized in that, if detect call event, the described first IN service processing subsystem also is used for decision and whether reports described call event, and described call event is triggered the cascade subsystem by described secondary send to the described second IN service processing subsystem, the described second IN service processing subsystem receives described call event, and whether decision reports described call event.
13. intelligent trigger according to claim 8 system, it is characterized in that, if mobile terminating IN service, the described first IN service processing subsystem also was used for sending the first roaming number request to HLR before first IN service that process user is contracted, and received the first roaming number request response that described HLR returns.
14. intelligent trigger according to claim 13 system, it is characterized in that, if mobile terminating IN service, notify described secondary trigger the cascade subsystem handle before the described first IN service processing subsystem also be used for sending the second roaming number request to described HLR, and receive the second roaming number request response that described HLR returns.
15. intelligent trigger according to claim 8 system is characterized in that the priority of described first IN service is higher than the priority of described second IN service.
16. to 15 each described intelligent trigger systems, it is characterized in that described IN service processing subsystem comprises Call Control Block, intelligent trigger module, intelligent event processing module according to Claim 8,
Described Call Control Block is used for calling out control;
Described intelligent trigger module is used for triggering intelligence according to user's CAMEL-Subscription-Information;
Whether described intelligent event processing module is used to determine Event Report BCSM.
CN2007101956258A 2007-12-04 2007-12-04 System and method for triggering intelligence business Active CN101207928B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2007101956258A CN101207928B (en) 2007-12-04 2007-12-04 System and method for triggering intelligence business

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2007101956258A CN101207928B (en) 2007-12-04 2007-12-04 System and method for triggering intelligence business

Publications (2)

Publication Number Publication Date
CN101207928A CN101207928A (en) 2008-06-25
CN101207928B true CN101207928B (en) 2010-09-29

Family

ID=39567712

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007101956258A Active CN101207928B (en) 2007-12-04 2007-12-04 System and method for triggering intelligence business

Country Status (1)

Country Link
CN (1) CN101207928B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111388B (en) * 2009-12-29 2014-06-25 华为技术有限公司 Service trigger method, service intermediate equipment and service trigger system
CN102196393B (en) * 2010-03-19 2013-12-04 华为技术有限公司 Intelligent network service triggering method and device
CN102547484A (en) * 2010-12-31 2012-07-04 ***通信集团浙江有限公司 Intelligent network service nesting method, system and service broker

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1240096A (en) * 1996-12-04 1999-12-29 英国电讯有限公司 Call set-up process
CN1318260A (en) * 1998-09-16 2001-10-17 诺基亚网络有限公司 Transmitting call-related data between switching centres
EP1206111A1 (en) * 2000-11-13 2002-05-15 Alcatel Charging arrangement for a multimedia communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1240096A (en) * 1996-12-04 1999-12-29 英国电讯有限公司 Call set-up process
CN1318260A (en) * 1998-09-16 2001-10-17 诺基亚网络有限公司 Transmitting call-related data between switching centres
EP1206111A1 (en) * 2000-11-13 2002-05-15 Alcatel Charging arrangement for a multimedia communication system

Also Published As

Publication number Publication date
CN101207928A (en) 2008-06-25

Similar Documents

Publication Publication Date Title
EP1991019B1 (en) A method, service control device and communication system for realizing the service of one card for multiple numbers
CN101180896B (en) Inbound roamer call control system
EP2510711B1 (en) Notifying roaming subscriber of missed call
US7349693B2 (en) Method for implementing a call connection between a non-local calling subscriber and a local called subscriber who is an intelligent network subscriber
US8060087B2 (en) CDMA intelligent network system and its method, device for realizing international roaming service
CN1285221C (en) Number portability and services utilizing number range owner information
CA2841196C (en) Method and system for implementing intelligent roaming service
CN101790157B (en) Realize the method and apparatus of one card multi-number business
CN100401848C (en) Method for solving calling/called impact in wireless network
CN101207928B (en) System and method for triggering intelligence business
CN101147413A (en) A method for realizing mobility limitation based on service in a mobile communication system
CN100550947C (en) Global call terminal fail call prompting method based on virtual terminal
CN101860589A (en) Method and system for realizing display of calling information at called terminal
US20120064888A1 (en) Method for implementing an intelligent service and communications system
CN101697639B (en) Method and system for complete smart bypass calling
CN101374345A (en) Method, apparatus and system for transferring wireless virtual private network VPN short number of calling subscriber
CN101110999A (en) Method for timely informing defaulting subscriber in mobile communication system
CN101835128B (en) Intelligent network call charging method and network
CN100442883C (en) System and method for providing telephone access service in wireless network
CN1512797A (en) Method for providing intelligent service in mobile virtual network
CN1988726B (en) Intelligent triggering and charging method, device and system in call re-orientation
CN101668278B (en) Method and related equipment for roaming service
CN101815271B (en) Method and system for realizing one-number double-machine service in prepayment service
CN101998373A (en) Method for processing multi-service nesting of intelligent network
CN101730003B (en) Method and system for avoiding endless loop in flexible ringing business

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant