CN102036246A - Call historical count (abbreviated as count) updating method and device - Google Patents
Call historical count (abbreviated as count) updating method and device Download PDFInfo
- Publication number
- CN102036246A CN102036246A CN2010105947546A CN201010594754A CN102036246A CN 102036246 A CN102036246 A CN 102036246A CN 2010105947546 A CN2010105947546 A CN 2010105947546A CN 201010594754 A CN201010594754 A CN 201010594754A CN 102036246 A CN102036246 A CN 102036246A
- Authority
- CN
- China
- Prior art keywords
- count
- upgrades
- system side
- indication parameter
- msc
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/12—Counting circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/14—Delay circuits; Timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
- H04M2203/551—Call history
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/60—Aspects of automatic or semi-automatic exchanges related to security aspects in telephonic communication systems
- H04M2203/6027—Fraud preventions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/60—Details of telephonic subscriber devices logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs
Abstract
The invention discloses a count updating method and a count updating device. The method comprises the following steps that: a system sets a count updating indication parameter; and when receiving a call request of a terminal, the system determines whether to perform the count updating or not according to the count updating indication parameter. In the method, the times of the count updating is set flexibly through the setting of the count updating indication parameter by the system, and the loads of system processing information is reduced greatly while cloning equipment is detected by the system.
Description
Technical field
The present invention relates to moving communicating field, especially a kind of method and apparatus of call history count update.
Background technology
For detect and prevent in the mobile communication free call on sb. else's expense through illegal means, various illegal use mobile communication resources and professional phenomenon such as usurp, guarantee network security and ensure telecommunication operator and user's just rights and interests that mobile phone user authentication is a kind of efficient ways.
Has the ability of the user being carried out authentication in the CDMA2000 system at present, in network, need to carry out three verifications: the one, the verification authentication is confirmed parameter (Authentication Confirmation Parameter, be called for short RANDC), the 2nd, verification Authentication Response parameter (Authentication Response Parameter, be called for short AUTHR), the 3rd, verification call history counting (Call History Count, be called for short COUNT), have only three verifications all to pass through, just allow the travelling carriage connecting system.The RANDC verification is in order to verify whether the used random number of travelling carriage authentication is that this switch (being the system that travelling carriage is prepared access) produces; The AUTHR verification then is that system side is according to Shared Secret Data (Shared Secret Data, be called for short SSD) use cellular authentication and voice encryption algorithm (Cellular authentication﹠amp with authentication random number (Authentication Challenge Parameter is called for short RANDU); Voice encryptionalgorithm is called for short the CAVE algorithm) result and the travelling carriage that calculate report whether consistent.Here will introduce the COUNT verification especially, whether it is to have imitated in the recognition network or puppet is emitted a kind of effective means of travelling carriage (promptly adopting illegal means to make " clone " travelling carriage), so the COUNT verification also claims " clone " detection.After carrying out the success of COUNT authentication when the process of COUNT authentication is Mobile Origination calling access in the CDMA2000 system, system side triggers COUNT and upgrades, (attaching position register (HLR) all has the COUNT value with mobile switching centre (MSC) for travelling carriage and system side, both keep identical) the COUNT value of preserving all adds one, and is consistent.As the travelling carriage with clone exists, and the COUNT value of preserving in the system is for legal mobile station and clone the summation of travelling carriage call event frequency.
If a terminal is by " clone ", so as long as legal terminal and " clone " terminal are all used on the net, two COUNT values that terminal provided after all have different with the COUNT value of system side record, and because the COUNT call event frequency of system side record is actually the summation of two terminal call incident frequencies, so any one one the COUNT value of terminal and the different situation of COUNT value of system side preservation must occur in two terminals when certain carries out system's access attempts, system side can be assert in view of the above has " clone " to exist, this moment, network side also can be taked related measure in addition again except refusal inserts, such as terminal is followed the tracks of or the like.
COUNT upgrades and is divided into the shared and shared dual mode of SSD of sharing users data (Shared Subscriber Data is called for short SSD), and when SSD shared, MSC carried out the COUNT authentication and triggers COUNT and upgrade; When SSD did not share, HLR carried out the COUNT authentication and triggers COUNT and upgrade.
COUNT upgrades when not sharing flow process that Fig. 1 shows SSD, the system side of this moment comprises base station controller (Base Station Controllor, be called for short BSC), (the MobileSwitching Station of mobile switching centre, be called for short MSC), VLR Visitor Location Register (Vistor Location Register is called for short VLR) and attaching position register (Home Location Register, be called for short HLR), specifically describe as follows:
101: Mobile Origination is called out, and BSC has sent to call for and asked message to MSC/VLR, and this is called for to ask and carries RANDC value, AUTHR value and the COUNT value that is used for authentication in the message;
102:SSD does not share, and MSC/VLR sends authentication request message to HLR, carries out authentication process by HLR, carries RANDC value, AUTHR value and COUNT value in the described authentication request message;
103:HLR carries out authentication process, comprises the COUNT authentication and triggers the COUNT renewal;
104:HLR returns authentication response message and gives MSC/VLR, carries and need carry out the sign that COUNT upgrades;
105:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues the assignment request earlier and gives BSC, and Traffic Channel is set up in request;
106:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
107:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the sign that COUNT upgrades according to the needs of preserving before, issues COUNT parameter updating request message;
108:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
109:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
110:MSC/VLR sends authentication status report request message to HLR, carries COUNT and upgrades the result;
111:HLR receives authentication status report request message, according to the result of the COUNT renewal of carrying in the message, as upgrades success, and the COUNT value that then travelling carriage is kept at HLR adds up 1;
After 112:HLR finishes the COUNT value and adds up, return authentication status report response message to MSC/VLR.
Fig. 2 shows SSD when sharing, the flow process that COUNT upgrades, and the system side of this moment comprises BSC, MSC and VLR, specifically describes as follows:
201: Mobile Origination is called out, and BSC has sent to call for and asked message to MSC/VLR, rises to call for to ask and carries RANDC value, AUTHR value and the COUNT value that is used for authentication in the message;
202:SSD shares, and MSC/VLR carries out authentication process, comprises the COUNT authentication and triggers the COUNT renewal;
203:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues the assignment request earlier and gives BSC, and Traffic Channel is set up in request;
204:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
205:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the sign that COUNT upgrades according to the needs of preserving before, issues COUNT parameter updating request message;
206:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
207:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
208:MSC/VLR receives the result that COUNT upgrades, as upgrades success, and the COUNT value that then travelling carriage is kept at MSC/VLR adds up 1.
When regulation does not trigger the COUNT renewal in the ANSI41-D agreement, mostly adopting per call all to trigger COUNT at present upgrades, like this in the per call with respect to not carrying out the flow process that COUNT upgrades, many two A interface messages, be that parameter updating request and parameter update are confirmed, owing to had 3 message on the A interface when travelling carriage carries out call, if carrying out COUNT, per call upgrades, then the message count that inserts for the A interface mobile station is increased to 5 by 3, can increase the signaling link burden on the A interface so greatly, BSC and MSC/VLR network element need higher message handling ability simultaneously.More newly arrive and reach anti-clone's purpose in order to carry out COUNT authentication and COUNT, and increase the load of signaling link and BSC on the A interface, MSC/VLR network element greatly, the mode that this COUNT upgrades is not suitable for carrying out extensive commercialization.
Summary of the invention
The technical problem to be solved in the present invention has provided a kind of method and apparatus of call history count update, reduces the number of times that COUNT upgrades, when reaching COUNT value cumulative effects, the system loading increase seldom, the present invention is suitable for extensive commercialization.
In order to solve the problems of the technologies described above, the invention provides a kind of method of call history count update, comprising:
System side is provided with call history counting (COUNT) and upgrades indication parameter;
System side is upgraded indication parameter decision whether carrying out COUNT according to described COUNT and is upgraded when the call request that receives terminal.
Further, described COUNT renewal indication parameter is a COUNT updating mark;
Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and is comprised:
System side is when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
Further, described system side is provided with COUNT and upgrades indication parameter and comprise;
Described system side is changed to described COUNT updating mark effectively when described terminal registration; And, when the call request that receives terminal, after described COUNT renewal indication parameter decision whether carrying out COUNT renewal, reset described COUNT updating mark according to preset rules and be changed to effective or invalid.
Further, described COUNT renewal indication parameter is that a COUNT upgrades timer;
Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and is comprised:
System side is when the call request that receives terminal, and is overtime if described COUNT upgrades timer, and described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
Further, described system side is provided with COUNT and upgrades indication parameter and comprise;
Described system side starts described COUNT and upgrades timer when described terminal registration; And,
Described system side is when the call request that receives described terminal, if described COUNT upgrades timer expiry, then carries out COUNT and upgrades, and after carrying out the COUNT renewal, restarts described COUNT and upgrades timer.
The present invention also provides a kind of device of call history count update, and wherein, described device comprises:
The unit is set, is used to be provided with call history counting (COUNT) and upgrades indication parameter;
Updating block is used for when the call request that receives terminal, upgrades indication parameter decision whether carrying out COUNT according to described COUNT and upgrades.
Further, described COUNT renewal indication parameter is a COUNT updating mark;
Described updating block is to be used for: when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and is upgraded; Otherwise, do not carry out COUNT and upgrade.
Further, the described unit that is provided with is to be used for: when terminal registration, described COUNT updating mark is changed to effectively, and,
Described updating block upgrades indication parameter decision whether carrying out COUNT renewal according to described COUNT after, reset described COUNT updating mark according to preset rules and be changed to effective or invalid.
Further, described COUNT renewal indication parameter is that a COUNT upgrades timer;
Described updating block is to be used for: overtime if described COUNT upgrades timer when the call request that receives terminal, and carry out COUNT and upgrade; Otherwise, do not carry out COUNT and upgrade.
Further, the described unit that is provided with is to be used for: start described COUNT and upgrade timer when described terminal registration; And, after described updating block carries out the COUNT renewal, restart described COUNT and upgrade timer.
The present invention is provided with the mode that COUNT upgrades indication parameter by system side the number of times that COUNT upgrades is set flexibly, carries out when cloned devices detects satisfying system side, has significantly reduced the load of system handles information.Compared with prior art, the present invention by mark will, mode such as clock is set, for a travelling carriage from start to the end between the shutdown, one or many COUNT only can take place to be upgraded, reaching the effect while that the COUNT value adds up, do not increase system loading, this mode can be used for extensive commercialization.
Description of drawings
Fig. 1 be SSD when not sharing COUNT upgrade flow chart;
COUNT upgraded flow chart when Fig. 2 shared for SSD;
Fig. 3 upgrades flow chart for adopting mark will mode COUNT when SSD does not share;
Fig. 4 upgrades flow chart for adopting mark will mode COUNT when SSD shares;
Fig. 5 upgrades flow chart for adopting timer mode COUNT when SSD does not share;
Fig. 6 upgrades flow chart for adopting timer mode COUNT when SSD shares.
Embodiment
The present invention will be further described in detail below in conjunction with accompanying drawing:
Basic thought of the present invention is in system side call history counting (COUNT) to be set to upgrade indication parameter; System side is upgraded indication parameter decision whether carrying out COUNT according to described COUNT and is upgraded when the call request that receives terminal.
Based on above-mentioned basic thought, the invention provides a kind of method of call history count update, wherein,
System side is provided with call history counting (COUNT) and upgrades indication parameter; System side is upgraded indication parameter decision whether carrying out COUNT according to described COUNT and is upgraded when the call request that receives terminal.
Wherein, described COUNT renewal indication parameter is a COUNT updating mark; Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and comprised: system side is when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
Wherein, described system side is provided with COUNT and upgrades indication parameter and comprise; Described system side is changed to described COUNT updating mark effectively when described terminal registration; And when the call request that receives terminal, whether decision is carried out resetting described COUNT updating mark according to preset rules and being changed to effective or invalid after COUNT upgrades according to described COUNT updating mark.
Described preset rules can for, between starting up of terminal and shutdown, only carry out COUNT and upgrade, such as, when terminal registration, the COUNT updating mark is changed to effectively, when terminal is called out first, carry out the COUNT renewal, it is invalid that the COUNT updating mark is changed to; Perhaps, between starting up of terminal and shutdown, carry out repeatedly COUNT and upgrade, COUNT updating mark value be not 0 o'clock then effective, initial value is N, whenever carries out a COUNT and upgrades, its value of COUNT updating mark subtracts 1.
Wherein, described COUNT renewal indication parameter is that a COUNT upgrades timer; Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and comprised: system side is when the call request that receives terminal, and overtime if described COUNT upgrades timer, described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
Wherein, described system side is provided with COUNT and upgrades indication parameter and comprise; Described system side starts described COUNT and upgrades timer when described terminal registration; And described system side is when the call request that receives described terminal, if described COUNT upgrades timer expiry, then carries out COUNT and upgrades, and after carrying out the COUNT renewal, restarts described COUNT and upgrades timer.
Wherein, it is a counter that COUNT upgrades indication parameter, described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and is comprised: when receiving the call request of terminal, if the value of counter is the multiple of M, then carrying out COUNT upgrades, otherwise, do not carry out COUNT and upgrade.Described system side is provided with COUNT renewal indication parameter and comprises; When initial counter being set is 0, when receiving the call request of terminal, Counter Value is added 1, wherein, can judge whether after carrying out COUNT upgrades counter to be added 1, perhaps, judges whether to carry out before COUNT upgrades counter to be added 1.
Fig. 3 shows mark will mode COUNT renewal flow chart when SSD does not share that the present invention adopts, COUNT upgrades indication parameter and is " call out next time and carry out the COUNT renewal " flag bit, the system side of this moment comprises BSC, MSC/VLR, and HLR, specifically describes as follows:
301: mobile platform started, BSC sends location update request message to MSC/VLR;
Do not have the record of this travelling carriage among the 302:MSC/VLR, send register request message to HLR;
303:HLR carries out the registration process of this travelling carriage, and " call out next time and the carry out the COUNT renewal " mark position with this travelling carriage is effectively simultaneously;
304: finish registration process, HLR returns enrollment response message and gives MSC/VLR;
305:MSC/VLR receives enrollment response message, upgrades to the BSC home position and accepts message, and notice BSC registration is finished;
306: initiate to call out for the first time after the travelling carriage registration is finished, BSC has sent to call for and has asked message to MSC/VLR, and this is called for to ask and carries RANDC value, AUTHR value and the COUNT value that is used for authentication in the message;
307:SSD does not share, and MSC/VLR sends authentication request message to HLR, carries the RANDC value, AUTHR value and the COUNT value that are used for authentication in this message;
308:HLR carries out authentication process, comprises the COUNT authentication, checks " call out next time carry out COUNT upgrade " flag bit, if this flag bit effectively then trigger COUNT and upgrade;
309:HLR returns authentication response message and gives MSC/VLR, carries and need carry out the sign that COUNT upgrades;
310:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues the assignment request and gives BSC, and Traffic Channel is set up in request;
311:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
312:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the sign that COUNT upgrades according to the needs of preserving before, issues COUNT parameter updating request message and gives BSC;
313:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
314:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
315:MSC/VLR sends authentication status report request message to HLR, carries COUNT in this message and upgrades the result;
316:HLR receives authentication status report request message, result according to the COUNT renewal of carrying in this message, as upgrade success, and the COUNT value that then travelling carriage is kept at HLR adds up 1, and " call out next time and the carry out the COUNT renewal " mark position with this travelling carriage is invalid simultaneously;
After 317:HLR finishes the COUNT value and adds up, return authentication status report response message to MSC/VLR.
Fig. 4 shows mark will mode COUNT renewal flow chart when SSD shares that the present invention adopts, and the system side of this moment comprises BSC, MSC and VLR, specifically describes as follows:
401: mobile platform started, BSC sends location update request message to MSC/VLR;
402:MSC/VLR carries out the registration process of this travelling carriage, and " call out next time and the carry out the COUNT renewal " mark position with this travelling carriage is effectively simultaneously;
The 403:MSC/VLR registration is finished, and upgrades to the BSC home position and accepts message, and notice BSC registration is finished;
404: initiate to call out for the first time after the travelling carriage registration is finished, BSC has sent to call for and has asked message to MSC/VLR, carries the RANDC value, AUTHR value and the COUNT value that are used for authentication in the message;
405:SSD shares, and MSC/VLR carries out authentication process, comprises the COUNT authentication, checks " call out next time carry out COUNT upgrade " flag bit, if this flag bit effectively then trigger COUNT and upgrade;
406:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues assignment request message earlier and gives BSC, and Traffic Channel is set up in request;
407:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
408:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the sign that COUNT upgrades according to the needs of preserving before, issues COUNT parameter updating request message and gives BSC;
409:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
410:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
411:MSC/VLR receives the result that COUNT upgrades, as upgrades success, and the COUNT value that then travelling carriage is kept at MSC/VLR adds up 1, and " call out next time and the carry out the COUNT renewal " mark position with this travelling carriage is invalid simultaneously.
Fig. 3, among the embodiment shown in Figure 4, all be to carry out after COUNT upgrades receiving call request first, it is invalid just the COUNT updating mark to be changed to, and between starting up of terminal and start, only carries out a COUNT and upgrades, in other embodiments of the invention, can the COUNT updating mark be set according to preset rules, be implemented between starting up of terminal and the shutdown and carry out upgrading more than COUNT, such as in the following way:
In HLR or MSC/VLR network element, increase COUNT update times information, the user starts shooting after the registration, COUNT update times assignment in HLR or MSC/VLR (this number of times value can be passed through the operating maintaining tool setting of HLR or MSC/VLR network element), whenever carrying out a COUNT behind the customer call upgrades, the COUNT update times is subtracted one, no longer carry out COUNT in after reducing to 0, calling out and upgrade.Operator can by the value of operating maintaining tool control COUNT update times, control the COUNT update times that the user starts shooting and carries out between the shutdown flexibly according to commercial result of use.
Fig. 5 shows timer mode COUNT renewal flow chart when SSD does not share that the present invention adopts, and the system side of this moment comprises BSC, MSC, VLR and HLR, specifically describes as follows:
501: mobile platform started, BSC sends location update request message to MSC/VLR;
Do not have the record of this travelling carriage among the 502:MSC/VLR, send register request message to HLR;
503:HLR carries out the registration process of this travelling carriage, and " COUNT renewal " timer is set simultaneously.
504: finish registration process, HLR returns enrollment response message and gives MSC/VLR;
505:MSC/VLR receives enrollment response message, upgrades to the BSC home position and accepts message, and notice BSC registration is finished;
506: after the travelling carriage registration was finished, every initiation call, BSC have sent to call for asked message to MSC/VLR, carries the RANDC value, AUTHR value and the COUNT value that are used for authentication in this message;
507:SSD does not share, and MSC/VLR sends authentication request message to HLR, carries the RANDC value, AUTHR value and the COUNT value that are used for authentication in this message;
508:HLR carries out authentication process, comprises the COUNT authentication, and is overtime as " COUNT renewal " timer, then triggers COUNT and upgrades;
509:HLR returns authentication response message and gives MSC/VLR, carries and need carry out the sign that COUNT upgrades;
510:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues the assignment request earlier and gives BSC, and Traffic Channel is set up in request;
511:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
512:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the sign that COUNT upgrades according to the needs of preserving before, issues COUNT parameter updating request message and gives BSC;
513:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
514:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
515:MSC/VLR sends authentication status report request message to HLR, carries COUNT in this message and upgrades the result;
516:HLR receives authentication status report request message, according to the result of the COUNT renewal of carrying in this message, as upgrades success, and the COUNT value that then travelling carriage is kept at HLR adds up 1, will start " COUNT renewal " timer simultaneously once more;
After 517:HLR finishes the COUNT value and adds up, return authentication status report response message to MSC/VLR.
Fig. 6 shows timer mode COUNT renewal flow chart when SSD shares that the present invention adopts, and the system side of this moment comprises BSC, MSC and VLR, specifically describes as follows:
601: mobile platform started, BSC sends location update request message to MSC/VLR;
602:MSC/VLR carries out the registration process of this travelling carriage, starts " COUNT renewal " timer simultaneously;
The 603:MSC/VLR registration is finished, and upgrades to the BSC home position and accepts message, and notice BSC registration is finished;
604: after the travelling carriage registration was finished, every initiation call, BSC have sent to call for asked message to MSC/VLR, carries the RANDC value, AUTHR value and the COUNT value that are used for authentication in the message;
605:SSD shares, and MSC/VLR carries out authentication process, comprises the COUNT authentication, checks " COUNT renewal " timer, if overtime, then trigger COUNT and upgrades;
606:MSC/VLR preserves and need carry out the sign that COUNT upgrades, and issues assignment request message earlier and gives BSC, and Traffic Channel is set up in request;
607:BSC finishes and sets up Traffic Channel, returns assignment and finishes message to MSC/VLR;
608:MSC/VLR judgement Traffic Channel is set up and is finished, and carries out the COUNT updating mark according to the needs of preserving before, issues COUNT parameter updating request message;
609:BSC notice travelling carriage carries out COUNT to be upgraded, and travelling carriage COUNT value adds up and returns response after 1;
610:BSC receives the response of travelling carriage, sends the parameter update acknowledge message to MSC/VLR;
611:MSC/VLR receives the result that COUNT upgrades, as upgrades success, and the COUNT value that then travelling carriage is kept at MSC/VLR adds up 1, starts " COUNT renewal " timer simultaneously once more.
Based on thought of the present invention, realize that the mode that COUNT upgrades also has a lot, such as:
Every interval specific call number of times carries out COUNT renewal mode once, particularly, after user's start, the HLR or the MSC/VLR recording user number of calls, start back initial value is 0, customer call number of times of every calling adds one, customer call, and the HLR or the MSC/VLR recording user number of calls add one, judge when the customer call number of times is the multiple of M, trigger more new technological process of COUNT, the value of M can be configured, and the operating maintaining tool by HLR or MSC/VLR network element is provided with.Such as, M can be 5,10.
The device that the present invention also provides the present invention that a kind of call history count update also is provided, wherein, described device comprises: the unit is set, is used to be provided with call history counting (COUNT) and upgrades indication parameter; Updating block is used for when the call request that receives terminal, upgrades indication parameter decision whether carrying out COUNT according to described COUNT and upgrades.
It is a COUNT updating mark that described COUNT upgrades indication parameter; Described updating block is to be used for: when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and is upgraded; Otherwise, do not carry out COUNT and upgrade.The described unit that is provided with is to be used for: when terminal registration described COUNT updating mark is changed to effectively, and, after whether described updating block carries out the COUNT renewal according to described COUNT updating mark decision, reset described COUNT updating mark according to preset rules and be changed to effective or invalid.It is that a COUNT upgrades timer that described COUNT upgrades indication parameter; Described updating block is to be used for: overtime if described COUNT upgrades timer when the call request that receives terminal, and carry out COUNT and upgrade; Otherwise, do not carry out COUNT and upgrade.The described unit that is provided with is to be used for: start described COUNT and upgrade timer when described terminal registration; And, after described updating block carries out the COUNT renewal, restart described COUNT and upgrade timer.
The present invention has introduced the method for avoiding the COUNT frequent updating in the CDMA2000 system, and the present invention is equally applicable in WCDMA and the TD-SCDMA system.By mark will mode, to the end between the shutdown, a COUNT only can take place upgrade from start for a travelling carriage.Actual in HLR or MSC/VLR, can be by the static mode that is provided with, set shutdown to the end after the mobile platform started, carry out several times that COUNT upgrades, do not upgrade and be not restricted to the COUNT that only carries out that Fig. 3, Fig. 4 describe.Adopting the timer mode, is 1 hour such as timer length, and then the user at most only carries out a COUNT renewal within an hour, and the effect that the COUNT value adds up in realizing travelling carriage and system does not increase system loading simultaneously like this.When extensive commercial COUNT update functions, the per call that prior art adopts all triggers COUNT and upgrades, can increase the load of the flow of A message link and BSC, MSC/VLR network element greatly, and the COUNT update strategy that the present invention proposes does not increase system loading when realizing the COUNT update functions.
It is pointed out that under the situation of not conflicting, the feature among embodiments of the invention and the embodiment can combination in any.In addition, the foregoing description only is an explanation of the invention and unrestricted, every based on inventive concept to any conversion that the present invention did, be equal to and replace or improve, all should be included within protection scope of the present invention.
Claims (10)
1. the method for a call history count update is characterized in that, comprising:
System side is provided with call history counting (COUNT) and upgrades indication parameter;
System side is upgraded indication parameter decision whether carrying out COUNT according to described COUNT and is upgraded when the call request that receives terminal.
2. the method for claim 1 is characterized in that, it is a COUNT updating mark that described COUNT upgrades indication parameter;
Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and is comprised:
System side is when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
3. method as claimed in claim 2 is characterized in that,
Described system side is provided with COUNT renewal indication parameter and comprises;
Described system side is changed to described COUNT updating mark effectively when described terminal registration; And when the call request that receives terminal, whether decision is carried out resetting described COUNT updating mark according to preset rules and being changed to effective or invalid after COUNT upgrades according to described COUNT updating mark.
4. the method for claim 1 is characterized in that,
It is that a COUNT upgrades timer that described COUNT upgrades indication parameter;
Described system side is upgraded indication parameter decision whether carrying out COUNT renewal according to described COUNT and is comprised:
System side is when the call request that receives terminal, and is overtime if described COUNT upgrades timer, and described system side is carried out COUNT and upgraded; Otherwise, do not carry out COUNT and upgrade.
5. method as claimed in claim 4 is characterized in that, described system side is provided with COUNT renewal indication parameter and comprises;
Described system side starts described COUNT and upgrades timer when described terminal registration; And,
Described system side is when the call request that receives described terminal, if described COUNT upgrades timer expiry, then carries out COUNT and upgrades, and after carrying out the COUNT renewal, restarts described COUNT and upgrades timer.
6. the device of a call history count update is characterized in that, described device comprises:
The unit is set, is used to be provided with call history counting (COUNT) and upgrades indication parameter;
Updating block is used for when the call request that receives terminal, upgrades indication parameter decision whether carrying out COUNT according to described COUNT and upgrades.
7. device as claimed in claim 6 is characterized in that,
It is a COUNT updating mark that described COUNT upgrades indication parameter;
Described updating block is to be used for: when the call request that receives terminal, if described COUNT updating mark is effective, described system side is carried out COUNT and is upgraded; Otherwise, do not carry out COUNT and upgrade.
8. device as claimed in claim 7 is characterized in that,
The described unit that is provided with is to be used for: when terminal registration, described COUNT updating mark is changed to effectively, and,
After whether described updating block carries out the COUNT renewal according to described COUNT updating mark decision, reset described COUNT updating mark according to preset rules and be changed to effective or invalid.
9. device as claimed in claim 6 is characterized in that,
It is that a COUNT upgrades timer that described COUNT upgrades indication parameter;
Described updating block is to be used for: overtime if described COUNT upgrades timer when the call request that receives terminal, and carry out COUNT and upgrade; Otherwise, do not carry out COUNT and upgrade.
10. device as claimed in claim 9 is characterized in that,
The described unit that is provided with is to be used for: start described COUNT and upgrade timer when described terminal registration; And, after described updating block carries out the COUNT renewal, restart described COUNT and upgrade timer.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010594754.6A CN102036246B (en) | 2010-12-17 | 2010-12-17 | Call historical count (abbreviated as count) updating method and device |
PCT/CN2011/082099 WO2012079438A1 (en) | 2010-12-17 | 2011-11-11 | Method and apparatus for updating call history count |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010594754.6A CN102036246B (en) | 2010-12-17 | 2010-12-17 | Call historical count (abbreviated as count) updating method and device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN102036246A true CN102036246A (en) | 2011-04-27 |
CN102036246B CN102036246B (en) | 2014-12-10 |
Family
ID=43888409
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201010594754.6A Active CN102036246B (en) | 2010-12-17 | 2010-12-17 | Call historical count (abbreviated as count) updating method and device |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102036246B (en) |
WO (1) | WO2012079438A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012079438A1 (en) * | 2010-12-17 | 2012-06-21 | 中兴通讯股份有限公司 | Method and apparatus for updating call history count |
WO2013007139A1 (en) * | 2011-07-13 | 2013-01-17 | 中兴通讯股份有限公司 | Authentication method and home location register |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6249572B1 (en) * | 1998-06-08 | 2001-06-19 | Inet Technologies, Inc. | Transaction control application part (TCAP) call detail record generation in a communications network |
CN1777322A (en) * | 2004-11-15 | 2006-05-24 | 华为技术有限公司 | Method for treating user of updating IP address at network side |
CN1953615A (en) * | 2006-09-22 | 2007-04-25 | 华为技术有限公司 | A method and device to perfect the terminal authentication |
CN101047904A (en) * | 2006-03-28 | 2007-10-03 | 中兴通讯股份有限公司 | Method for dispatching service zone optimization by trunking communication system |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102036246B (en) * | 2010-12-17 | 2014-12-10 | 中兴通讯股份有限公司 | Call historical count (abbreviated as count) updating method and device |
-
2010
- 2010-12-17 CN CN201010594754.6A patent/CN102036246B/en active Active
-
2011
- 2011-11-11 WO PCT/CN2011/082099 patent/WO2012079438A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6249572B1 (en) * | 1998-06-08 | 2001-06-19 | Inet Technologies, Inc. | Transaction control application part (TCAP) call detail record generation in a communications network |
CN1777322A (en) * | 2004-11-15 | 2006-05-24 | 华为技术有限公司 | Method for treating user of updating IP address at network side |
CN101047904A (en) * | 2006-03-28 | 2007-10-03 | 中兴通讯股份有限公司 | Method for dispatching service zone optimization by trunking communication system |
CN1953615A (en) * | 2006-09-22 | 2007-04-25 | 华为技术有限公司 | A method and device to perfect the terminal authentication |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012079438A1 (en) * | 2010-12-17 | 2012-06-21 | 中兴通讯股份有限公司 | Method and apparatus for updating call history count |
WO2013007139A1 (en) * | 2011-07-13 | 2013-01-17 | 中兴通讯股份有限公司 | Authentication method and home location register |
Also Published As
Publication number | Publication date |
---|---|
WO2012079438A1 (en) | 2012-06-21 |
CN102036246B (en) | 2014-12-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101189859B (en) | Wireless communication network security method and system | |
US6427073B1 (en) | Preventing misuse of a copied subscriber identity in a mobile communication system | |
US6236852B1 (en) | Authentication failure trigger method and apparatus | |
US5799084A (en) | System and method for authenticating cellular telephonic communication | |
US9015808B1 (en) | Restricting mobile device services between an occurrence of an account change and acquisition of a security code | |
CN101605323A (en) | Detection unusual by in the business of the portable terminal in cordless communication network emission | |
CN104717063B (en) | The software security means of defence of mobile terminal | |
CN102318386A (en) | Service-based authentication to a network | |
CN103686651B (en) | A kind of authentication method based on urgent call, equipment and system | |
CN101753725A (en) | System for blacklist processing, method and device therefor | |
CN101711023B (en) | Method and system for realizing interlocking of phone and card | |
US6618584B1 (en) | Terminal authentication procedure timing for data calls | |
US8804932B2 (en) | Protection of services in mobile network against CLI spoofing | |
KR100507394B1 (en) | A method for reducing fraudulent system access | |
CN100466806C (en) | Right discriminating method between mobile terminal and network equipment | |
CN101707771B (en) | Network authentication system and method for network side receiving terminal access | |
CN102036246B (en) | Call historical count (abbreviated as count) updating method and device | |
US7650139B2 (en) | Method for ensuring security of subscriber card | |
CN101330756B (en) | Intelligent network business implementing system and method for preventing user identification from being stolen | |
EP3045003B1 (en) | Paging procedure control | |
WO1998000956A3 (en) | System and method for preventing cellular fraud | |
CN101431754B (en) | Method for preventing clone terminal access | |
CN100558059C (en) | A kind of control method of customer service authority | |
GB2365687A (en) | Authentication process using sequence numbers | |
CN102238546A (en) | Authentication method and home location register |
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 |