CN101754162B - Method, system and device of controlling risk - Google Patents

Method, system and device of controlling risk Download PDF

Info

Publication number
CN101754162B
CN101754162B CN 200810226981 CN200810226981A CN101754162B CN 101754162 B CN101754162 B CN 101754162B CN 200810226981 CN200810226981 CN 200810226981 CN 200810226981 A CN200810226981 A CN 200810226981A CN 101754162 B CN101754162 B CN 101754162B
Authority
CN
China
Prior art keywords
user
ggsn
account balance
targeted customer
boss server
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
CN 200810226981
Other languages
Chinese (zh)
Other versions
CN101754162A (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.)
China Mobile Communications Group Co Ltd
Original Assignee
China Mobile Communications Group 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 China Mobile Communications Group Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN 200810226981 priority Critical patent/CN101754162B/en
Publication of CN101754162A publication Critical patent/CN101754162A/en
Application granted granted Critical
Publication of CN101754162B publication Critical patent/CN101754162B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method, a system and a device of controlling arrearage risk. The method comprises the following steps: after determining that a user is not an arrearage risk object user, a business operation support system (BOSS) server monitors the account balance of the user in real time and informs the GGSN when the account balance of the user is smaller than the preset threshold; and the GGSN executes the arrearage risk control procedure on the user. The method can realize arrearage risk control of all users in the PS domain, thereby avoiding great economic losses of the cable operators.

Description

A kind of controlling arrearage risk, system and device
Technical field
The present invention relates to moving communicating field, espespecially a kind of controlling arrearage risk for packet domain, system and device.
Background technology
Adopt the mode of offline charging in existing packet domain, off-line accounting system as shown in Figure 1.GPRS (General Packet Radio Service, GPRS) (the Service GPRS Supporting node of the Serving GPRS Support Node in system, SGSN) and Gateway GPRS Support Node (GatewayGPRS Support Node, GGSN) all can produce ticket.Wherein, the contextual charging data record of relevant packet data protocol (Packet Data Protocol, PDP)---the call detail record (CallDetail Record, CDR) that SGSN produces is called SGSN-CDR, is called for short S-CDR; GGSN produces the charging data record CDR of relevant PDP Context, is called for short G-CDR.S-CDR and G-CDR are transmitted to charging gateway (Charging Gateway, CG), then are sent to business operation support system (Business ﹠amp by CG; Operation Support System, BOSS) process;
After the CDR of gprs system receives in the BOSS system, carry out wholesale price in batches and charging and process, and at the corresponding business cost of use of user account deduction.After expense deduction, the BOSS system will judge also whether user's account balance can continue to use gprs service, if Sorry, your ticket has not enough value for the user to continue to use gprs service, the BOSS system can notify attaching position register (Home Location Register, HLR) change user's GPRS subscription data is down state, until the user is revised as upstate after supplementing with money again.
When whether monitor user ' is in the arrearage state, can there be following time delay in charging flow under existing offline charging pattern:
(1) original charging ticket lags behind and closes the time delay that causes.
(2) ticket is delivered to the time delay that CG causes.
(3) time delay of CG preliminary treatment ticket generation.
The time delay that produces when (4) ticket is delivered to the BOSS system.
(5) the BOSS system carries out wholesale price and processes the time delay that causes.
(6) time delay that the HLR subscription data produces is revised according to user balance by the BOSS system.
The time delay that produces when (7) HLR is synchronized to SGSN with subscription data.
At these time lapses, when Sorry, your ticket has not enough value, the user still can use business, causes arrearage when user account, and especially the user is online for a long time, caused Original CDR to lag behind when closing, and the amount owed that causes can be very large.When the user was in roaming state, time delay was larger, and amount owed just also may be larger.
Shortcoming for existing offline charging in packet domain, also considering to adopt the arrearage risk control scheme in packet domain in present gprs system, the technical scheme of existing arrearage risk control generally adopts expense sign (the Charging Characteristics that changes in user contracting data, CC) field, the BOSS system judges that regularly whether user balance is higher than the arrears risk threshold value of setting, if, do not belong to the arrears risk targeted customer, the CC field value in HLR in this user contracting data is empty; If not, notifying HLR to revise CC field in this user contracting data, to identify this user be the arrears risk user.
The user can obtain the subscription data that comprises the CC field from HLR in the process of carrying out PDP context activation to the GGSN request, when certain user carries out PDP context activation, if account balance is higher than arrears risk targeted customer's threshold value, be that the CC field value is for empty, GGSN is by this field of judgement, can not carry out arrearage risk control to this user, the user normally uses business, uses the offline charging mode; If account balance lower than arrears risk targeted customer's threshold value, carries out arrearage risk control to this user.
Because the CC field in user contracting data can only be carried by the establishment PDP Context request in activation (Create PDP Context Request) message, send GGSN to by SGSN, after in case the user activates the PDP Context success, this user is online for a long time, account balance constantly reduces, when account balance during lower than arrears risk targeted customer's threshold value, GGSN can not know that this user has belonged to the arrearage risk control targeted customer, also can not initiate the arrearage risk control flow process to BOSS; The offline charging mode that this moment, this user still used can cause huge time delay, and the user still can continue the use business in the situation that Sorry, your ticket has not enough value, causes arrearage to occur.
In view of being implemented real time billing, all users can have an immense impact on to the GGSN equipment performance, only consider in packet domain at present by GGSN to specific, the account balance that (carries out PDP context activation) when reaching the standard grade just fewer, targeted customer that arrears risk is higher take certain surveillance and control measure, most of user is still adopted the mode of above-mentioned offline charging, in case the user is online for a long time, when its account balance constantly reduces, can not in time include it in monitoring range, thereby cause still can normally using gprs service after its arrearage.As seen, existing packet domain can not effectively be carried out arrearage risk control, still can cause a large amount of arrearages to occur, and causes huge economic loss to operator.
In addition, 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) at Long Term Evolution/system architecture evolution (Long Term Evolution/System Architecture Evolution, LTE/SAE) concept of " always online " has been proposed in the System Dependent standard, be that user terminal is in case start, activate immediately PDP Context after adhering to, thereby the user who promotes data service experiences.According to above-mentioned analysis, the possibility of " always online " subscriber arrearage is very big, therefore such user's appearance can aggravate the problem of arrearage risk control system that most of user is included in that existing arrears risk scheme can't be real-time, if occurred a large amount of these type of users in gprs system, will cause huge economic loss to operator.
Summary of the invention
The embodiment of the present invention provides a kind of controlling arrearage risk, system and device, solved in the prior art can not be real-time all users are carried out the problem of arrearage risk control.
A kind of controlling arrearage risk comprises:
After business operation support system BOSS server determines that the user is not the arrears risk targeted customer, described user's account balance is carried out Real Time Monitoring;
During less than the threshold value set, notification gateway universal grouping wireless business supporting node GGSN carries out the arrearage risk control flow process to described user when described user's account balance.
According to said method of the present invention, described account balance to described user carries out Real Time Monitoring, specifically comprises:
Upgrade this user's account balance according to the ticket that receives;
Whether the account balance after judgement is upgraded is less than the threshold value of setting.
Said method of the present invention also comprises:
When described user's account balance during less than the threshold value set, described BOSS server notification attaching position register HLR revises the charging identifier information that comprises in this user's the subscription data of local storage, and to identify this user be the arrears risk targeted customer.
According to said method of the present invention, when described BOSS server receives user that described GGSN sends and activates first ticket that produces after the packet data protocol PDP Context, according to the charging identifier information that comprises in described first ticket, judge whether described user is the arrears risk targeted customer.
Said method of the present invention also comprises:
When described GGSN receives described user and asks to activate the request message of PDP Context, judge whether described user is the arrears risk targeted customer, if directly carry out the arrearage risk control flow process to described user; If not, allow this user normally to activate PDP Context.
According to said method of the present invention, the request message of described activation PDP Context generates according to the described user's who gets from described HLR subscription data; At least comprise charging identifier information in described subscription data;
Describedly judge that whether described user is the arrears risk targeted customer, specifically comprises:
According to described charging identifier information, judge whether described user is the arrears risk targeted customer.
According to said method of the present invention, the arrearage risk control flow process of described execution to described user specifically comprises:
Described GGSN sends the solicited message that starts arrearage risk control to described BOSS server;
Described BOSS server returns to spendable amount information according to described user's account balance;
Described GGSN controls described user's usage data business according to described amount information.
A kind of owing risk control system comprises: business operation support system BOSS server and ggsn GGSN;
Described GGSN is used for the notice according to described BOSS server, carries out the arrearage risk control flow process to described user;
Described BOSS server after be used for determining that the user is not the arrears risk targeted customer, carries out Real Time Monitoring to described user's account balance, and notifies described GGSN during less than the threshold value set at described user's account balance.
According to said system of the present invention, described GGSN also is used for sending described user and activates the ticket that produces after the packet data protocol PDP Context to described BOSS server;
Described BOSS server when also activating for the user who receives described GGSN transmission first ticket that produces after PDP Context, according to the charging identifier information that comprises in described first ticket, judges whether described user is the arrears risk targeted customer.
Said system of the present invention also comprises: attaching position register HLR;
Described BOSS server also is used for during less than the threshold value set, notifying attaching position register HLR when described user's account balance;
Described attaching position register HLR, being used for revising according to the notice of described BOSS server charging identifier information that this user's of local storage subscription data comprises, to identify this user be the arrears risk targeted customer.
According to said system of the present invention, described GGSN also is used for:
When receiving described user and asking to activate the request message of PDP Context, judge whether described user is the arrears risk targeted customer, if directly carry out the arrearage risk control flow process to described user; If not, allow this user normally to activate PDP Context.
Said system of the present invention also comprises: service universal grouping wireless business supporting node SGSN;
Described SGSN, the request message that the subscription data that is used for the described user that gets from described HLR generates described activation PDP Context sends to described GGSN.
According to said system of the present invention, described BOSS server also is used for: receive the solicited message of the startup arrearage risk control that described GGSN sends, and according to described user's account balance, return to spendable amount information;
Described GGSN specifically is used for: send the solicited message that starts arrearage risk control to described BOSS server; And according to the amount information that described BOSS server returns, control described user's usage data business; And after the available amount of authorizing in described amount information is finished, then to the available amount of described BOSS server application.
A kind of business operation support system BOSS server comprises:
Monitoring module is used for the account balance of determining the user who is not the arrears risk targeted customer is carried out Real Time Monitoring;
Notification module, notification gateway universal grouping wireless business supporting node GGSN when being used for account balance that described monitoring module monitors described user less than the threshold value set.
According to above-mentioned BOSS server of the present invention, described monitoring module comprises:
The balance updates unit is used for the account balance according to the described user of ticket renewal who receives;
Judging unit is used for judging that whether account balance after described balance updates unit upgrades is less than the threshold value of setting;
Control performance element, when being used for account balance after described judgment unit judges goes out to upgrade less than the threshold value set, controlling described notification module and notify described GGSN.
According to above-mentioned BOSS server of the present invention, described control performance element also is used for:
Account balance after described judgment unit judges go out to be upgraded is during less than the threshold value set, controls described notification module notice attaching position register HLR and revises the charging identifier information that comprises in local this user's who stores subscription data to identify this user be the arrears risk targeted customer.
Above-mentioned BOSS server of the present invention also comprises:
Judge module, when activating for the user who receives ggsn GGSN transmission first ticket that produces after the packet data protocol PDP Context, judge whether described user is the arrears risk targeted customer, and notify described monitoring module.
Description of drawings
Fig. 1 is the structural representation of off-line accounting system in prior art;
Fig. 2 is the flow chart of controlling arrearage risk in the embodiment of the present invention;
Fig. 3 starts the flow chart of arrearage risk control by GGSN in the embodiment of the present invention;
Fig. 4 is the structural representation of owing risk control system in the embodiment of the present invention;
Fig. 5 is the structural representation of BOSS server in the embodiment of the present invention;
Fig. 6 is a kind of concrete structure exemplary plot of owing risk control system in the embodiment of the present invention;
Fig. 7 is a kind of specific implementation flow chart of controlling arrearage risk in the embodiment of the present invention.
Embodiment
The controlling arrearage risk that the embodiment of the present invention provides, by GGSN, the arrears risk targeted customer is carried out on the arrearage risk control basis, after the user successfully activates PDP Context, by the BOSS server, other user who does not include the arrearage risk control scope in is carried out the remaining sum monitoring, thereby realize all users' arrears risk is controlled.Its flow chart as shown in Figure 2, execution in step is as follows:
Step S101: the user that business operation support system BOSS server receives the GGSN transmission activates first ticket that produces after PDP Context.
The user activates PDP Context, after bringing into use data service, the operating position that GGSN can counting user, and according to the regular transmit telephone bill of transmission cycle of setting to the BOSS server; Be specially:
GGSN is being sent to the BOSS server by charging gateway CG with ticket.
Step S102: judge whether this user is the arrears risk targeted customer.
The ticket that the user who receives produces is resolved, can obtain the charging identifier information of wherein carrying, judge according to charging identifier information whether described user is the arrears risk targeted customer.
If, execution in step S103; If not, execution in step S104.
Step S103: the account balance of not monitoring this user.
Annotate: because this user belongs to the arrears risk targeted customer, in pdp context activation, therefore GGSN needn't process these certain customers are included in the scope of risk control again.
Step S104: upgrade the present account balance of this user according to receiving ticket.Specifically comprise:
First ticket that receives according to step S101 upgrades the present account balance of this user; Or upgrade the present account balance of this user according to the ticket that step S106 receives.
Step S105: whether the account balance after judgement is upgraded is less than the threshold value of setting.
If not, execution in step S106; If, execution in step S107.
Step S106: next ticket that continues to receive this user.
And return to execution in step S104.
Step S107: this user of notice GGSN has become the arrears risk targeted customer.
Simultaneously, this user of BOSS server notification HLR has become the arrears risk targeted customer, HLR revises the charging identifier information that comprises in local this user's who stores subscription data, and for example: the CC field, this user belongs to the arrears risk targeted customer by the CC field identification.
Step S108:GGSN carries out the arrearage risk control flow process to this user.
Above-mentioned controlling arrearage risk also comprises: by GGSN, the arrears risk targeted customer is carried out arrearage risk control, its flow chart as shown in Figure 3, execution in step is as follows:
Step S201:GGSN receives the user by the request message of the activation PDP Context of affiliated user terminal transmission.
Wherein, carry subscription data in the request message of the activation PDP Context that receives, comprise at least charging identifier information in subscription data; And to be SGSN generate according to the described user's who gets from HLR subscription data the request message of this activation PDP Context, and send to GGSN's.
Step S202: judge whether this user is the arrears risk targeted customer.
GGSN resolves the request message of the activation PDP Context that receives, obtains the charging identifier information that comprises in its subscription data that carries, and judges according to the charging identifier information that gets whether described user is the arrears risk targeted customer.
If not, execution in step S203; If, execution in step S204.
Step S203: allow this user normally to activate PDP Context, namely this user normally accesses.
Step S204: this user is carried out the arrearage risk control flow process.
GGSN starts arrearage risk control mechanism, and allows this user to activate PDP Context under its arrearage risk control mechanism, realizes access.
Especially, the user all can report ticket to GGSN according to the report cycle of setting after normally activating PDP Context or GGSN startup arrearage risk control mechanism and activating PDP Context, then is sent to the BOSS server through charging gateway CG.
Above-mentionedly the user carried out the arrearage risk control flow process specifically comprise:
GGSN sends the solicited message that starts arrearage risk control to described BOSS server; After the solicited message of the startup arrearage risk control that BOSS server reception GGSN sends, according to user's account balance, return to spendable amount information; The amount information that GGSN returns according to the BOSS server is controlled the user and is activated PDP Context, the usage data business.
After the available amount of authorizing in amount information was finished, GGSN was again to the available amount of BOSS server application, when the account balance at family is zero or when receiving user's PDP deexcitation request, controlled the user and stopped using data service.
Above-mentioned controlling arrearage risk according to the embodiment of the present invention provides can build a kind of owing risk control system, and as shown in Figure 4, this system comprises: GGSN10 and BOSS server 20.
GGSN10 is used for the notice according to BOSS server 20, carries out the arrearage risk control flow process to this user.
GGSN10 also is used for sending described user and activates the ticket that produces after the packet data protocol PDP Context to BOSS server 20.
BOSS server 20 after be used for determining that the user is not the arrears risk targeted customer, carries out Real Time Monitoring to this user's account balance, and at this user's account balance notice GGSN10 during less than the threshold value set.
State BOSS server 20, when also activating for the user who receives the GGSN10 transmission first ticket that produces after PDP Context, according to the charging identifier information that comprises in first ticket, judge whether this user is the arrears risk targeted customer.
GGSN10 when also being used for receiving the user and asking to activate the request message of PDP Context, judges whether this user is the arrears risk targeted customer, if, the direct arrearage risk control flow process of execution to this user; If not, allow this user normally to activate PDP Context.
Above-mentioned owing risk control system also comprises: attaching position register HLR30.
BOSS server 20 also is used for during less than the threshold value set, notifying attaching position register HLR30 when user's account balance.
Attaching position register HLR30, being used for revising according to the notice of BOSS server 20 charging identifier information that this user's of local storage subscription data comprises, to identify this user be the arrears risk targeted customer.
BOSS server 20 as shown in Figure 5, comprising: monitoring module 202 and notification module 203.
Monitoring module 202 is used for carrying out Real Time Monitoring to determining the account balance that is not the arrears risk targeted customer.
Better, monitoring module 202 further can comprise: balance updates unit 2021, judging unit 2022 and control performance element 2023.
Balance updates unit 2021 is used for the account balance according to the ticket renewal user who receives.
Judging unit 2022 is used for judge that account balance after balance updates unit 2021 upgrades is whether less than the threshold value of setting.
Control performance element 2023, when being used for judging unit 2022 and judging account balance after renewal less than the threshold value set, controls described notification module and notify GGSN10.
Control performance element 2023, when also being used for judging unit 2022 and judging account balance after renewal and be not less than the threshold value of setting, control remains updating block 2021 continues to receive next ticket, and upgrades user's account balance according to the ticket that receives.
Control performance element 2023, also can be used for: the account balance after judging unit 201 is judged renewal is during less than the threshold value set, controls described notification module notice attaching position register HLR40 and revises the charging identifier information that comprises in local this user's who stores subscription data to identify this user be the arrears risk targeted customer.
Notification module 203, notice GGSN10 when being used for account balance that monitoring module 202 monitors the user less than the threshold value set.
BOSS server 20 also comprises: judge module 201 when activating for the user who receives the GGSN transmission first ticket that produces after the packet data protocol PDP Context, judges whether described user is the arrears risk targeted customer, and notifies described monitoring module.
BOSS server 20 also comprises: Quota distribution module 204, the request that is used for according to GGSN10 is that the arrears risk targeted customer distributes spendable amount, and returns to amount information to GGSN10.
Be described in detail below in conjunction with this concrete application scenarios of packet domain, be illustrated in figure 6 as a concrete example of owing risk control system.This system comprises: the HLR of user terminal and home network thereof, SGSN, GGSN, CG, BOSS server etc.
Wherein, the BOSS server can upgrade according to the account balance of the CDR information that has received to the user.When user's account balance satisfies the screening conditions of setting, the user contracting data of this user in HLR is modified.For example: if this user account remaining sum less than 0, i.e. shutdown operation is carried out in arrearage; If this user account remaining sum is greater than 0 and less than the threshold value of the arrearage risk control of setting, determine that this user belongs to potential arrears risk targeted customer, expense in this user contracting data in HLR sign CC field is modified, to identify this user as the arrears risk targeted customer.
SGSN, the subscription data that is used for the user that gets from HLR generates the request message that activates PDP Context and sends to GGSN.
When GGSN has become the arrears risk targeted customer according to the request message judgement user who activates PDP Context, before its usage data business, carry out authentication to the BOSS server, the amount that can be used by the BOSS authorized user, thus realize real-time control and charging to the targeted customer.Use detailed process that system shown in Figure 6 realizes all users are carried out arrearage risk control as shown in Figure 7, comprise the following steps:
Step S501: user terminal sends PDP activation request message to SGSN.
Step S502:SGSN obtains the user's who uses this user terminal subscription data from affiliated HLR.
After SGSN receives the PDP activation request message of user terminal transmission, the subscription data of asking this user to affiliated HLR, this user's of the local storage of HLR inquiry subscription data, and return to SGSN.Wherein, comprise at least charging identifier information in user's subscription data---the CC field.
Step S503:SGSN sends and creates the PDP Context request message to GGSN.
Wherein, create charging identifier information---the CC field that also comprises in the subscription data that the PDP Context request message carries, the CC field can be included in tunnel protocol (GPRS Tunnel Protocol, the GTP) packet header that creates the PDP Context request message.
Step S504:GGSN judges whether this user is the arrears risk targeted customer.
After GGSN receives and creates the PDP Context request message, the establishment PDP Context request message that receives is resolved, obtain the charging identifier information that comprises in its subscription data that carries---CC field, determine whether the arrears risk targeted customer according to the CC field.
If, execution in step S508; If not, execution in step S505.
Step S505:GGSN returns and creates the PDP Context response message to SGSN.
Step S506:SGSN returns to PDP to user terminal and activates response message.
SGSN receive GGSN return create the PDP Context response message after, return to PDP to user terminal and activate response message.At this moment, the user successfully activates PDP Context.
Because this user is not the arrears risk targeted customer, therefore can normally activate PDP Context.
Step S507: the user activates the rear normal usage data business of PDP Context success.
In the process of user's usage data business, GGSN can regularly produce ticket, and sends the BOSS server to by CG.
Step S508:GGSN is to the arrearage risk control flow process of BOSS server request startup to this user.Be specially: GGSN sends the solicited message that starts arrearage risk control to the BOSS server
Step S509:BOSS server authorizes can be used amount, and available amount information is returned to GGSN.
The BOSS server can be controlled the Signalling exchange of (Diameter Credit Contorl, DCC) Interface realization and GGSN by Diameter credit, complete potential arrears risk targeted customer's business is used and control.Be specially:
After the BOSS server receives the request of GGSN, and set up DCC between GGSN and be connected, check this user account remaining sum, and be the spendable amount of this user assignment according to account balance, return to the operable amount information of this user to GGSN.
Step S510:GGSN returns and creates the PDP Context response message to SGSN.
Step S511:SGSN returns to PDP to user terminal and activates response message.
At this moment, the user successfully activates PDP Context.
Step S512: the user is according to the amount information usage data business of distributing.
The operable amount information of this user that GGSN returns according to the BOSS server is controlled user's usage data business in available amount scope.
Step S513: after the available amount of distributing to the user was finished, GGSN can continue to the available amount of BOSS server application.
After the available amount of BOSS server-assignment uses, when GGSN is still online according to user profile judgement user, can be again to the available amount of BOSS server application, BOSS is according to the actual conditions of user account, if the user account remaining sum is non-vanishing, continue to distribute available amount, and allow the user to continue to use until user offline; If or the user account remaining sum is zero, forbid that the user uses business.
For example: user profile can be: IMSI International Mobile Subscriber Identity (International Mobile SubscriberIdentity, IMSI), Mobile Subscriber International ISDN number (Mobile Station International ISDNNumber, MSISDN) etc.; Wherein, ISDN is the abbreviation of integrated services digital network (Integrated Services DigitalNetwork).
First ticket that step S514:BOSS server produces when receiving this usage data business of user.Be that the user activates first ticket that produces after PDP Context.
Step S515: judge that this user is the arrears risk targeted customer.
After the BOSS server receives ticket, discovery is that this user activates first ticket that produces after PDP Context, the ticket that receives is resolved, obtain the charging identifier information that comprises in the subscription data that wherein carries---CC field, the CC field in ticket is judged.
If the CC field is not empty, illustrate that this user is the arrears risk targeted customer, execution in step S516; If the CC field is empty, illustrate that this user is not the arrears risk targeted customer, need to carry out Real Time Monitoring, execution in step S517 to user's account balance.
Step S516: the remaining sum of not monitoring this user.
Because this user has been the arrears risk targeted customer, GGSN has initiated and has carried out the arrearage risk control flow process to this user, therefore need to not monitor.
Step S517: the account balance that upgrades this user according to ticket.
The BOSS system realizes the Real Time Monitoring to account balance according to ticket real-time update user's account balance.
Whether step S518:BOSS server account balance is less than the threshold value of setting.
Wherein, threshold value can be set according to actual conditions, during lower than this threshold value, will be identified as the arrears risk targeted customer when the user account remaining sum.
If execution in step 520; If not, execution in step S519.
Step S519: next ticket that continues to receive this user.
Return to execution in step 517 when receiving next ticket.
Step S520: this user of notice GGSN has become the arrears risk targeted customer.
Especially, the BOSS server can be determined according to the GGSN address information in user's ticket the GGSN address of the current use of user.
The BOSS server informs that by the DCC interface message this user of GGSN has become the arrears risk targeted customer, need to carry out arrearage risk control to it.GGSN returns to acknowledge message after receiving the DCC interface message of BOSS transmission.
Simultaneously, BOSS notice HLR revises this user's subscription data, and this user has become the arrears risk targeted customer by the CC field identification.
Step S521:GGSN carries out arrearage risk control to this user.Be specially:
At first GGSN judges whether this user is online.Due to user profile such as the IMSI that includes the user in BOSS server and the mutual DCC interface message of GGSN and MSISDN, GGSN can find this user according to above-mentioned user profile, and judges whether this user is online.
If also online, just initiate the arrearage risk control flow process for this user, to the BOSS quota application, until this user offline or remaining sum are zero.If this user is not online, do not do subsequent operation.
The detailed process of this user being carried out arrearage risk control is the described process of step S508, S509, S512 and S513, repeats no more herein.
The user uses data service, sends PDP deexcitation request message, and GGSN receives PDP deexcitation request message, sends PDP deexcitation response message to SGSN, user's deexcitation success; And GGSN sends the message of termination credit control service to the BOSS server, and the BOSS server carries out associative operation to user account after receiving and stopping credit control service message, and to GGSN transmission acknowledge message.
Above-mentioned controlling arrearage risk, system and device that the embodiment of the present invention provides, the arrears risk targeted customer is carried out on the basis of arrearage risk control at GGSN, by the BOSS server, non-arrears risk targeted customer's remaining sum is monitored, thereby can be real-time bring all users in packet domain into the arrearage risk control system, the arrearage risk control of realization to all users, can effectively monitor the situation that long-time online user's account balance constantly reduces even to cause arrearage, avoid causing huge economic loss to operator.
Said method can well be supported the arrearage risk control to " always online " user, prevents the malicious overdraft phenomenon when this type of user uses business.
The above; only be the better embodiment of the present invention; but protection scope of the present invention is not limited to this; anyly be familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily, replace or be applied to other similar devices, within all protection scope of the present invention should being encompassed in.Therefore, protection scope of the present invention should be as the criterion with the protection range of claims.

Claims (10)

1. a controlling arrearage risk, is characterized in that, comprising:
After business operation support system BOSS server determines that the user is not the arrears risk targeted customer, account balance to described user carries out Real Time Monitoring, when wherein said BOSS server receives user that GGSN sends and activates first ticket that produces after the packet data protocol PDP Context, according to the charging identifier information that comprises in described first ticket, judge whether described user is the arrears risk targeted customer; And described GGSN judges whether described user is the arrears risk targeted customer, if directly carry out the arrearage risk control flow process to described user when receiving described user and asking to activate the request message of PDP Context; If not, allow this user normally to activate PDP Context;
During less than the threshold value set, notification gateway universal grouping wireless business supporting node GGSN carries out the arrearage risk control flow process to described user when described user's account balance;
Wherein, the arrearage risk control flow process of described execution to described user specifically comprises:
Described GGSN sends the solicited message that starts arrearage risk control to described BOSS server;
Described BOSS server returns to spendable amount information according to described user's account balance;
Described GGSN controls described user's usage data business according to described amount information.
2. the method for claim 1, is characterized in that, described account balance to described user carries out Real Time Monitoring, specifically comprises:
Upgrade this user's account balance according to the ticket that receives;
Whether the account balance after judgement is upgraded is less than the threshold value of setting.
3. method as claimed in claim 2, is characterized in that, also comprises:
When described user's account balance during less than the threshold value set, described BOSS server notification attaching position register HLR revises the charging identifier information that comprises in this user's the subscription data of local storage, and to identify this user be the arrears risk targeted customer.
4. the method for claim 1, is characterized in that, the request message of described activation PDP Context generates according to the described user's who gets from HLR subscription data; At least comprise charging identifier information in described subscription data;
Describedly judge that whether described user is the arrears risk targeted customer, specifically comprises:
According to described charging identifier information, judge whether described user is the arrears risk targeted customer.
5. an owing risk control system, is characterized in that, comprising: business operation support system BOSS server and ggsn GGSN;
Described GGSN is used for the notice according to described BOSS server, carries out the arrearage risk control flow process to described user;
Described BOSS server after be used for determining that the user is not the arrears risk targeted customer, carries out Real Time Monitoring to described user's account balance, and notifies described GGSN during less than the threshold value set at described user's account balance;
Wherein, described BOSS server also is used for: receive the solicited message of the startup arrearage risk control that described GGSN sends, and according to described user's account balance, return to spendable amount information;
Described GGSN specifically is used for: send the solicited message that starts arrearage risk control to described BOSS server; And according to the amount information that described BOSS server returns, control described user's usage data business; And after the available amount of authorizing in described amount information is finished, then to the available amount of described BOSS server application.
Described GGSN also is used for sending described user and activates the ticket that produces after the packet data protocol PDP Context to described BOSS server;
Described BOSS server when also activating for the user who receives described GGSN transmission first ticket that produces after PDP Context, according to the charging identifier information that comprises in described first ticket, judges whether described user is the arrears risk targeted customer;
Described GGSN also is used for: when receiving described user and asking to activate the request message of PDP Context, judge whether described user is the arrears risk targeted customer, if directly carry out the arrearage risk control flow process to described user; If not, allow this user normally to activate PDP Context.
6. system as claimed in claim 5, is characterized in that, also comprises: attaching position register HLR;
Described BOSS server also is used for during less than the threshold value set, notifying attaching position register HLR when described user's account balance;
Described attaching position register HLR, being used for revising according to the notice of described BOSS server charging identifier information that this user's of local storage subscription data comprises, to identify this user be the arrears risk targeted customer.
7. system as claimed in claim 5, is characterized in that, also comprises: service universal grouping wireless business supporting node SGSN;
Described SGSN, the request message that the subscription data that is used for the described user that gets from described HLR generates described activation PDP Context sends to described GGSN.
8. a business operation support system BOSS server, is characterized in that, comprising:
Monitoring module is used for the account balance of determining the user who is not the arrears risk targeted customer is carried out Real Time Monitoring;
Notification module, notification gateway universal grouping wireless business supporting node GGSN when being used for account balance that described monitoring module monitors described user less than the threshold value set;
Wherein, described monitoring module specifically is used for:
After receiving the solicited message of the startup arrearage risk control that described GGSN sends, according to described user's account balance, return to spendable amount information, according to described amount information, control described user's usage data business by described GGSN;
Described BOSS server also comprises:
Judge module, when activating for the user who receives ggsn GGSN transmission first ticket that produces after the packet data protocol PDP Context, judge whether described user is the arrears risk targeted customer, and notify described monitoring module.
9. BOSS server as claimed in claim 8, is characterized in that, described monitoring module comprises:
The balance updates unit is used for the account balance according to the described user of ticket renewal who receives;
Judging unit is used for judging that whether account balance after described balance updates unit upgrades is less than the threshold value of setting;
Control performance element, when being used for account balance after described judgment unit judges goes out to upgrade less than the threshold value set, controlling described notification module and notify described GGSN.
10. BOSS server as claimed in claim 9, is characterized in that, described control performance element also is used for:
Account balance after described judgment unit judges go out to be upgraded is during less than the threshold value set, controls described notification module notice attaching position register HLR and revises the charging identifier information that comprises in local this user's who stores subscription data to identify this user be the arrears risk targeted customer.
CN 200810226981 2008-11-28 2008-11-28 Method, system and device of controlling risk Active CN101754162B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN 200810226981 CN101754162B (en) 2008-11-28 2008-11-28 Method, system and device of controlling risk

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN 200810226981 CN101754162B (en) 2008-11-28 2008-11-28 Method, system and device of controlling risk

Publications (2)

Publication Number Publication Date
CN101754162A CN101754162A (en) 2010-06-23
CN101754162B true CN101754162B (en) 2013-05-15

Family

ID=42480390

Family Applications (1)

Application Number Title Priority Date Filing Date
CN 200810226981 Active CN101754162B (en) 2008-11-28 2008-11-28 Method, system and device of controlling risk

Country Status (1)

Country Link
CN (1) CN101754162B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006185A (en) * 2010-11-15 2011-04-06 中国联合网络通信集团有限公司 Internet of things terminal charging query method and internet of things terminal charging query system
CN102547641A (en) * 2010-12-23 2012-07-04 中兴通讯股份有限公司 Defaulting control method, gateway and system
CN102546219B (en) * 2010-12-31 2015-11-25 中国移动通信集团甘肃有限公司 Defaulting subscriber's method for supervising and system
CN102271321A (en) * 2011-07-20 2011-12-07 中兴通讯股份有限公司 prepayment request processing method and device
CN103634126B (en) * 2012-08-22 2017-12-22 华为技术有限公司 Multicast information transmission method and apparatus
CN102932940B (en) * 2012-10-17 2016-03-02 大唐移动通信设备有限公司 Communication resource adjustment method and device
CN108207006B (en) * 2016-12-20 2021-07-06 中国移动通信有限公司研究院 Data domain shutdown strategy control method and communication system
CN109120808A (en) * 2018-09-04 2019-01-01 湖北文理学院 A kind of shutdown fee payment method and device
CN109275115A (en) * 2018-10-15 2019-01-25 程桂平 It needs to adjust the processing method to new access request according to residual flow

Also Published As

Publication number Publication date
CN101754162A (en) 2010-06-23

Similar Documents

Publication Publication Date Title
CN101754162B (en) Method, system and device of controlling risk
CN102075897B (en) Method and system for charging mobile data service
RU2417536C2 (en) System and device for providing optional advice of charge service
US20030157925A1 (en) Communication unit and method for facilitating prepaid communication services
CN103477587A (en) Method and device for controlling QoS and/or policy and charging control of a guest user
CN101213863A (en) Online charging management server
JP2004248305A (en) Method for improving accounting efficiency
CN101208943A (en) Controlling provision of services in a communications network
MXPA06001678A (en) Subscriber management and accounting using event detection in a wireless device.
CN101217384B (en) Method, device and system to realize virtual private network charging
CN100561929C (en) The wide band post-paid service implementation method
CN102572768A (en) Charging method, authentication method, charging equipment and authentication equipment
CN103748921A (en) Capacity allocation in communications
CN102291704B (en) Charging method, charging device, exchange device and charging system
CN101959166B (en) Method and system for controlling online charging
CN100550960C (en) Avoid the method for the subscriber arrearage of account in business operation support system
CN109547956B (en) Multi-service concurrent processing method
WO2011140753A1 (en) Method, terminal and system for achieving difference charging of fixed wireless phone among cells
KR101006275B1 (en) Method and system for providing prepaid service using subdivision of prepaid account
CN102238508B (en) Online charging method, device and system
JP5749000B2 (en) Mobile communication terminal and terminal control method
CN102143466B (en) On-line charging method, access proxy equipment and system
CN101860634A (en) Method and system for implementing packet prepayment
CN103229576A (en) Connection establishment method and device
CN102056125B (en) Method, equipment and system for realizing service control during roaming

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