CN102387260A - Method and system for determining dropped call rate - Google Patents

Method and system for determining dropped call rate Download PDF

Info

Publication number
CN102387260A
CN102387260A CN2011103210506A CN201110321050A CN102387260A CN 102387260 A CN102387260 A CN 102387260A CN 2011103210506 A CN2011103210506 A CN 2011103210506A CN 201110321050 A CN201110321050 A CN 201110321050A CN 102387260 A CN102387260 A CN 102387260A
Authority
CN
China
Prior art keywords
users
counter
active user
report cycle
sampling period
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
Application number
CN2011103210506A
Other languages
Chinese (zh)
Other versions
CN102387260B (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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201110321050.6A priority Critical patent/CN102387260B/en
Publication of CN102387260A publication Critical patent/CN102387260A/en
Priority to PCT/CN2012/072848 priority patent/WO2013056530A1/en
Application granted granted Critical
Publication of CN102387260B publication Critical patent/CN102387260B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/22Arrangements for supervision, monitoring or testing
    • H04M3/36Statistical metering, e.g. recording occasions when traffic exceeds capacity of trunks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/08Indicating faults in circuits or apparatus
    • H04M3/10Providing fault- or trouble-signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method and system for determining a dropped call rate. The method comprises the following steps of: recording a user number which is abnormally released in a sampling period and a user number which is successfully established in the sampling period by adopting a summation and accumulation way through a foreground according to the increased user number and the decreased user number, and calculating a current user number in the sampling period; after the sampling period is reached, respectively writing the user number which is abnormally released in the sampling period and the user number which is successfully established in the sampling period into an abnormally-released user counter and a successfully-established user counter by adopting the summation and accumulation way through the foreground; writing the current user number of the sampling period into a current user counter by adopting a way of covering previous data; after a reporting period is reached, synchronizing the data on the abnormally-released user counter, the successfully-established user counter and the current user counter to a webmaster through the foreground; and determining the dropped call rate of the reporting period by the webmaster according to the user number which is abnormally released in the reporting period, the user number which is successfully established in the reporting period and the current user number of the last reporting period.

Description

Cutting off rate is confirmed method and system
Technical field
The present invention relates to field of mobile communication, particularly relate to a kind of cutting off rate and confirm method and system.
Background technology
In the prior art, cutting off rate is the index of an important measurement systematic function of mobile communications network.As the 4th generation technique Long Term Evolution (Long Term Evolution the abbreviates LTE as) system of mobile network's evolution, the cutting off rate index is more important.
At present, the definition of cutting off rate index comprises two kinds of computational methods: method one, confirm cutting off rate according to the number of users of unusual release divided by the total number of users that discharges; Method two is confirmed cutting off rate according to the number of users that the number of users of unusual release is set up divided by success.In the LTE system, mainly confirm the cutting off rate index according to method two.
In method two, confirm that the molecule (the unusual number of users that discharges) and the denominator (number of users that success is set up) of cutting off rate index do not have interdependence, the promptly unusual number of users that discharges does not have interdependence with the number of users that success is set up in a granularity.Under above-mentioned situation, can cause the index of cutting off rate abnormal conditions to occur greater than 100%.Densely distributed at number of users; Add up under the bigger situation of fineness ratio, so unusual difficult exposure, but sparse in user distribution; The statistics fineness ratio is less; And successfully set up with unusual release and stride under the situation of granularity, the unusual occurrence probability of this statistics is very high, thereby has had a strong impact on the accuracy of index.
Summary of the invention
The present invention provides a kind of cutting off rate to confirm method and system, to solve in the prior art problem that cutting off rate accuracy that cutting off rate under special circumstances causes greater than 100% reduces.
The present invention provides a kind of cutting off rate to confirm method, comprising:
The number of users of the increase that the foreground of base station reports according to the chain of command of base station and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the sampling period;
The sampling period then after; The number of users that the foreground adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that active user's number in this sampling period is write active user's counter;
Report cycle then after, the data sync that the foreground will discharge subscriber's meter unusually, be created as on function family counter and the active user's counter is given webmaster;
Webmaster is confirmed the cutting off rate of this report cycle according to active user's number of the number of users of the unusual release of this report cycle, the successful number of users of setting up and a last report cycle.
The present invention also provides a kind of cutting off rate to confirm system, comprises base station foreground and webmaster, and wherein, base station foreground comprises:
Sampling module; Be used for the number of users of the increase that the chain of command according to the base station reports and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the sampling period;
Processing module; Be used for the sampling period then after; The number of users that adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that active user's number in this sampling period is write active user's counter;
Reporting module, be used for report cycle then after, give webmaster with the data sync that discharges subscriber's meter unusually, be created as on function family counter and the active user's counter;
Webmaster, the active user's number that is used for the number of users according to the unusual release of this report cycle, the successful number of users of setting up and a last report cycle is confirmed the cutting off rate of this report cycle.
Beneficial effect of the present invention is following:
Cutting off rate index through online active user's number at last granularity end being introduced next granularity is calculated; Solve in the prior art problem that cutting off rate accuracy that cutting off rate under special circumstances causes greater than 100% reduces, can under any circumstance guarantee the accuracy of cutting off rate.
Description of drawings
Fig. 1 is the flow chart that the cutting off rate of the embodiment of the invention is confirmed method;
Fig. 2 is the sketch map that the eNB of the embodiment of the invention handles;
Fig. 3 is the process chart of the ENB performance sampling MOD of the embodiment of the invention;
Fig. 4 is the process chart that the oldest value of OMC performance of the embodiment of the invention gathers;
Fig. 5 is the structural representation that the cutting off rate of the embodiment of the invention is confirmed system.
Embodiment
In order to solve in the prior art problem that cutting off rate accuracy that cutting off rate under special circumstances causes greater than 100% reduces; The invention provides a kind of cutting off rate and confirm method and system; Particularly; At first introduce a kind of new mode that gathers, be called the oldest value and gather mode at operation maintenance center's (Operations & Maintenance Center abbreviates OMC as) webmaster.This mode is supported the user data at last granularity end is introduced in this granularity.In addition, the foreground in the base station increases a kind of data processing method, is called sampling and revises (Modify abbreviates MOD as) mode, accomplishes the sampling of active user's number, and the up-to-date sampled value with not zero clearing replaces original sampled value all the time.Combine final accurately definite cutting off rate through AM/BAM.Below in conjunction with accompanying drawing and embodiment, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, does not limit the present invention.
Method embodiment
According to embodiments of the invention, provide a kind of cutting off rate to confirm method, Fig. 1 is the flow chart that the cutting off rate of the embodiment of the invention is confirmed method, before carrying out flow process as shown in Figure 1, the foreground of base station need be handled as follows:
Number of users for unusual release: all modes of gathering that need to discharge subscriber's meter unusually are set to summing mode, and wherein, all modes of gathering comprise: the foreground account form, and the webmaster time is gathered mode, and mode is gathered in the webmaster space;
Number of users for success foundation: all modes of gathering that need be created as function family counter are set to summing mode, and wherein, all modes of gathering comprise: the foreground account form, and the webmaster time is gathered mode, and mode is gathered in the webmaster space;
For current number of users: foreground account form that need the active user's counter MOD mode that is set to sample, the webmaster time mode of gathering is set to ask the oldest value mode, and the webmaster space mode of gathering is set to summing mode.
Wherein, sampling MOD mode is specially: statistical phenomeon is periodically counted according to chain of command (business module) report of user of base station in the foreground (platform property statistical module) that is meant the base station of sampling, and adds and subtracts calculating, obtains the value in sampling period.MOD is meant that after each sample clock generator is overtime the value that this cycle is calculated writes in the counter, as the value of this counter, covers original value with up-to-date value all the time.
Ask the oldest value mode to be: OMC gathers with the granularity to be unit, 15 minutes granularities are arranged, 30 minutes granularities, 1 hour granularity, 1 day granularity, 1 all granularities, January granularity etc.When the oldest value defined was this Granular Computing index, the mode that gathers was got the value that last granularity is preserved for the counter of old value.As: calculate 2011-09-0711 point 15 minutes to 11: 30 cutting off rates during this period of time of 2011-09-07, the value of then current number of users is got the counter that to be 2011-09-07 11: 00 reported to 2011-09-07 in 15 minutes during this period of time at 11 o'clock.
Based on above-mentioned description and processing, as shown in Figure 1, confirm that according to the cutting off rate of the embodiment of the invention method comprises following processing:
Step 101; The number of users of the increase that the foreground of base station reports according to the chain of command of base station and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the sampling period;
That is to say, in step 101, need be accumulated in the sum of the unusual number of users that discharges in this sampling period and the sum of the successful number of users of setting up; For example; UE1 discharges after successful connection unusually, and UE1 is not only after the successful connection but also unusual release, at this moment subsequently; The unusual number of users that discharges is 2, and the number of users that success is set up also is 2; And, need active user's number of real-time online in the calculating sampling cycle for active user's number, for example; In a sampling period, there are UE1, UE2, UE3, UE4, these 5 user's successful connections of UE5 to be in line states, then active user's number is 5; If in this sampling period, there are 2 user UE2, UE3 to discharge unusually again, there is user UE6 successful connection to be in line states; Then active user's number is 5-2+1=4, in the next sampling period, if there is 1 user UE5 to discharge unusually; Have 2 user UE7, UE8 successful connection to be in line states, then active user's number is 4-1+2=5.
Step 102; The sampling period then after; The number of users that the foreground adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that active user's number in this sampling period is write active user's counter;
For example; Before the number of users of the number of users and the success of the unusual release in this sampling period being set up on the foreground writes unusual release subscriber's meter respectively and is created as function family counter; The unusual subscriber's meter that discharges is respectively 4 and 5 with the counting that is created as function family counter; The number of users of the unusual release in this sampling period is respectively 2 and 1 with the number of users that success is set up; After then the foreground number of users that adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter; The unusual value that discharges subscriber's meter is 4+2=6, and the value that is created as function family counter is 5+1=6.
For active user's counter; Before the active user's number with this sampling period write, the value of active user's counter was 5, and active user's number in this sampling period is 8; Then when the active user's number with this sampling period writes active user's counter; Use 8 replacements 5, after the active user's number with this sampling period write active user's counter, the value of active user's counter was 8.
Step 103, report cycle then after, the data sync that the foreground will discharge subscriber's meter unusually, be created as on function family counter and the active user's counter is given webmaster;
In step 103, the foreground can be unit with the measuring object, gives webmaster with the data sync that discharges subscriber's meter unusually, be created as on function family counter and the active user's counter.Wherein, measurement unit comprises: sub-district, network element etc.
The number of users that step 104, webmaster are set up according to the number of users of the unusual release of this report cycle and success and active user's number of a last report cycle are confirmed the cutting off rate of this report cycle.
Particularly, in step 104, the number of users of the unusual release of cutting off rate=this report cycle of this report cycle/(number of users of the successful foundation of active user's number+this report cycle of a last report cycle).
That is to say that if the number of users that the number of users of the unusual release of this report cycle that the foreground reports is 3, success is set up is 5, active user's number is 6, active user's number of a last report cycle is 4, then the cutting off rate of this report cycle=3/ (4+5).When calculating the cutting off rate of next report cycle, need call the active user several 6 of this report cycle.
Preferably, in embodiments of the present invention, the base station is the evolved base station (evolved Node B abbreviates eNB as) in the LET system.
Fig. 2 is the sketch map that the eNB of the embodiment of the invention handles, and is as shown in Figure 2, platform property module and the OMC of the chain of command of eNB, eNB.
Be example below with eNB, the technique scheme of the embodiment of the invention is described.Fig. 3 is the process chart of the ENB performance sampling MOD of the embodiment of the invention, and is as shown in Figure 3:
Step 1, the chain of command of eNB report to add 1 foreground (platform property module) to eNB when having number of users to increase, and when having number of users to reduce, report to subtract the 1 platform property module to eNB.
Step 2, the platform property module of eNB is responsible for the periodic sampling of number of users.Chain of command reports the added-time, and the data in this sampling period are added 1, reports when subtracting, to the data minus 1 in sampling period.After sample clock generator is overtime, the value in this sampling period is write in active user's counter.
Step 3, when reporting the moment to arrive, the foreground of eNB is that unit reports OMC with the measuring object with performance collection data, if report no show constantly, then execution in step 2.
Fig. 4 is the process chart that the oldest value of OMC performance of the embodiment of the invention gathers; As shown in Figure 4; On the foreground of eNB is that OMC put performance collection data in storage, and according to granularity the performance collection data in the storehouse is gathered after unit reported OMC with the measuring object with performance collection data; If the mode that gathers is the oldest value mode, gets the last value of granularity that reports of this granularity and gather value at last as this counter.
Embodiment 1
Below with under the object of sub-district, the realization flow situation of radio resource control (Radio Resource Control abbreviates RRC as) cutting off rate is an example, and technique scheme of the present invention is illustrated.Suppose that the sampling MOD cycle is 30S.Report cycle is 15 minutes between OMC and the foreground.The practical implementation step is following:
Step 1 has 5 user UE1 to UE5 to connect (Attach) success at certain day 11 o'clock to 11: 15.
Wherein, UE1 is the Attach success between 11 o'clock to 11: 30 seconds, and chain of command reports the report of user number to add 1 incident for the platform property module.The platform property module is 1 in the sampled value of this sampling granularity.Sample clock generator is overtime, and sampled value 1 is write in active user's counter, and Counter Value is 1.
Family of no use is inserted between 11: 30 seconds to 11: 10, and then sampling is always 1, and Counter Value is 1.
11: 10 assign between 11: 10: 30, UE2 to UE4 Attach success.Chain of command has reported 4 numbers of users to add 1 incident for the platform property module.The platform property module adds 4 times in this sampling granularity, so sampled value is 5.Sample clock generator is overtime, and sampled value is write in active user's counter, and Counter Value is 5.
Before 11: 15, do not have the user to insert again, then the Counter Value of active user's number is always 5.
Step 2,11: 15, report constantly and arrive, the foreground synchrodata is given the OMC webmaster.Wherein the current RRC number of users counters count value of this granularity is 5, and the unusual release times statistical value of this granularity is 0, and it is 5 that this granularity is successfully set up the number statistical value.
According to cutting off rate index formula=unusual number of users that discharges/(number of users that current number of users+success is set up); Then the cutting off rate index of this granularity is 0/ (0+5)=0.(current RRC number of users is 0, is because this Granular Computing value is got the value of last granularity).
Step 3,11: 15 to 11: 30: UE1 and UE2 caused having gone offline unusually owing to RLC ERROR IND.
Wherein, because RLC ERROR IND causes having gone offline unusually, chain of command reports the report of user number to subtract 1 incident for the platform property module to UE1 between 11: 15 to 11: 15: 30.The platform property module subtracts 1 in this sampling granularity, so sampled value is 4.Sample clock generator is overtime, and sampled value is write in active user's counter, and Counter Value is 4.
Family of no use changes between 11: 15 minutes 30 seconds 1, and then sampling is always 4, and Counter Value is 4.
11: 20 assign between 11: 20: 30, and UE2 causes having gone offline unusually owing to RLC ERROR IND.Chain of command reports the report of user number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 3.Sample clock generator is overtime, and sampled value is write in active user's counter.Counter Value is 3.
Before 11: 30, do not have the user to insert again, then the Counter Value of active user's number is always 3.
Step 4,11: 30, report constantly and arrive, the foreground synchrodata is given the OMC webmaster.Wherein the current RRC number of users counters count value of this granularity is 3, and the unusual release times statistical value of this granularity is 2, and it is 0 that this granularity is successfully set up the number statistical value.
According to cutting off rate index formula=unusual number of users that discharges/(number of users that current number of users+success is set up); Then the cutting off rate index of this granularity is 2/ (5+0)=40%.(current RRC number of users is 5, is because this Granular Computing value is got the value of last granularity).
Embodiment 2
Below with under the object of sub-district; The general continental rise wireless access network RAB of evolution (Evolved Universal Terrestrial Radio Access Network Radio Access Bear; Abbreviating ERAB as) the realization flow situation of cutting off rate is example, and the technical scheme of the embodiment of the invention is elaborated, and supposes that the sampling MOD cycle is 30S; Report cycle is 15 minutes between OMC and the foreground, and the practical implementation step is following:
Step 1 has 5 user UE1 to UE5 successful at certain day 11 o'clock to 11: 15 Attach, and each user sets up a default bearing.
Wherein, UE1 is the Attach success between 11 and 11: 30 seconds, and chain of command reports the ERAB number to add 1 incident for the platform property module.The platform property module is 1 in the sampled value of this sampling granularity.Sample clock generator is overtime, and sampled value 1 is write in the current ERAB counter, and Counter Value is 1.
Family of no use is inserted between 11: 30 seconds to 11: 10, and then sampling is always 1, and Counter Value is 1.
11: 10 assign between 11: 10: 30, UE2 to UE4 Attach success.Chain of command has reported 4 ERAB numbers to add 1 incident for the platform property module.The platform property module adds 4 times in this sampling granularity, so sampled value is 5.Sample clock generator is overtime, and sampled value is write in the current ERAB counter, and Counter Value is 5.
Before 11: 15, do not have the user to insert again, the Counter Value of then current ERAB number is always 5.
Step 2,11: 15, report constantly and arrive, the foreground synchrodata is given the OMC webmaster.Wherein the current ERAB number counters count value of this granularity is 5, and it is 0 that this granularity discharges ERAB several statistical values unusually, and this granularity is successfully set up ERAB, and to count statistical value be 5.
According to cutting off rate index formula=unusual ERAB number that discharges/(the ERAB number that current ERAB number+success is set up); Then the ERAB cutting off rate index of this granularity is 0/ (0+5)=0.(current ERAB number of users is 0, is because this Granular Computing value is got the value of last granularity).
Step 3,11: 15 to 11: 30: UE1 and UE2 caused having gone offline unusually owing to RLC ERROR IND.
Wherein, UE1 11: 15 and 11: 15: 30 between because RLC ERROR IND causes having gone offline unusually, chain of command reports the ERAB number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 4.Sample clock generator is overtime, and sampled value is write in the current ERAB counter.Counter Value is 4.
Family of no use changes between 11: 15 minutes 30 seconds 1, and then sampling is always 4.Counter Value is 4.
11: 20 assign between 11: 20: 30, and UE2 causes having gone offline unusually owing to RLC ERROR IND.Chain of command reports the ERAB number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 3.Sample clock generator is overtime, and sampled value is write in the current ERAB counter, and Counter Value is 3.
Before 11: 30, do not have ERAB to insert again, the Counter Value of then current ERAB number is always 3.
Step 4,11: 30, report constantly and arrive, the foreground synchrodata is given the OMC webmaster.Wherein the current ERAB counter statistical value of this granularity is 3, and the unusual release times statistical value of this granularity is 2, and it is 0 that this granularity is successfully set up ERAB number statistical value.
According to cutting off rate index formula=unusual ERAB number that discharges/(the ERAB number that current ERAB number+success is set up); Then the cutting off rate index of this granularity is 2/ (5+0)=40% (current ERAB number is 5, is because this Granular Computing value is got the value of last granularity).
In sum; Technical scheme by means of the embodiment of the invention; Cutting off rate index through online active user's number at last granularity end being introduced next granularity is calculated; Solve in the prior art problem that cutting off rate accuracy that cutting off rate under special circumstances causes greater than 100% reduces, can under any circumstance guarantee the accuracy of cutting off rate.
Device embodiment
According to embodiments of the invention; Provide a kind of cutting off rate to confirm system, Fig. 5 is the structural representation that the cutting off rate of the embodiment of the invention is confirmed system, and is as shown in Figure 5; Confirm that according to the cutting off rate of the embodiment of the invention system comprises base station foreground 50 and webmaster 52; Wherein, base station foreground 50 comprises: sampling module 502, processing module 504, reporting module 506, below each module of the embodiment of the invention is carried out detailed explanation.
At first, the foreground 50 of base station need be handled as follows:
Number of users for unusual release: all modes of gathering that need to discharge subscriber's meter unusually are set to summing mode, and wherein, all modes of gathering comprise: foreground 50 account forms, and 52 times of webmaster are gathered mode, and mode is gathered in webmaster 52 spaces;
Number of users for success foundation: all modes of gathering that need be created as function family counter are set to summing mode, and wherein, all modes of gathering comprise: foreground 50 account forms, and 52 times of webmaster are gathered mode, and mode is gathered in webmaster 52 spaces;
For current number of users: foreground 50 account forms that need the active user's counter MOD mode that is set to sample, 52 time of the webmaster mode of gathering is set to ask the oldest value mode, and the webmaster 52 space modes of gathering are set to summing mode.
Wherein, sampling MOD mode is specially: statistical phenomeon is periodically counted according to chain of command (business module) report of user of base station in the foreground 50 (platform property statistical module) that is meant the base station of sampling, and adds and subtracts calculating, obtains the value in sampling period.MOD is meant that after each sample clock generator is overtime the value that this cycle is calculated writes in the counter, as the value of this counter, covers original value with up-to-date value all the time.
Ask the oldest value mode to be: OMC gathers with the granularity to be unit, 15 minutes granularities are arranged, 30 minutes granularities, 1 hour granularity, 1 day granularity, 1 all granularities, January granularity etc.When the oldest value defined was this Granular Computing index, the mode that gathers was got the value that last granularity is preserved for the counter of old value.As: calculate 2011-09-07 11: 15 to 11: 30 cutting off rates during this period of time of 2011-09-07, the value of then current number of users is got the counter that to be 2011-09-07 11: 00 reported to 2011-09-07 in 15 minutes during this period of time at 11 o'clock.
Sampling module 502; Be used for the number of users of the increase that the chain of command according to the base station reports and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the sampling period;
That is to say; Sampling module 502 need be accumulated in the sum of the unusual number of users that discharges in this sampling period and the sum of the successful number of users of setting up, and for example, UE1 discharges after successful connection unusually; UE1 is not only after the successful connection but also unusual release subsequently; At this moment, the unusual number of users that discharges is 2, and the number of users that success is set up also is 2; And, need active user's number of real-time online in the calculating sampling cycle for active user's number, for example; In a sampling period, there are UE1, UE2, UE3, UE4, these 5 user's successful connections of UE5 to be in line states, then active user's number is 5; If in this sampling period, there are 2 user UE2, UE3 to discharge unusually again, there is user UE6 successful connection to be in line states; Then active user's number is 5-2+1=4, in the next sampling period, if there is 1 user UE5 to discharge unusually; Have 2 user UE7, UE8 successful connection to be in line states, then active user's number is 4-1+2=5.
Processing module 504; Be used for the sampling period then after; The number of users that adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that active user's number in this sampling period is write active user's counter;
For example; Before the number of users that processing module 504 is set up the number of users and the success of the unusual release in this sampling period writes unusual release subscriber's meter respectively and is created as function family counter; The unusual subscriber's meter that discharges is respectively 4 and 5 with the counting that is created as function family counter; The number of users of the unusual release in this sampling period is respectively 2 and 1 with the number of users that success is set up; After then foreground 50 number of users that adopts mode that summation adds up that the number of users of the unusual release in this sampling period and success are set up writes unusual release subscriber's meter respectively and is created as function family counter; The unusual value that discharges subscriber's meter is 4+2=6, and the value that is created as function family counter is 5+1=6.
For active user's counter; Before the active user's number with this sampling period write, the value of active user's counter was 5, and active user's number in this sampling period is 8; Then when the active user's number with this sampling period writes active user's counter; Use 8 replacements 5, after the active user's number with this sampling period write active user's counter, the value of active user's counter was 8.
Reporting module 506, be used for report cycle then after, give webmaster 52 with the data sync that discharges subscriber's meter unusually, be created as on function family counter and the active user's counter;
Reporting module 506 can be unit with the measuring object, gives webmaster 52 with the data sync that discharges subscriber's meter unusually, be created as on function family counter and the active user's counter.Wherein, measurement unit comprises: sub-district, network element etc.
Webmaster 52, the number of users that is used for setting up according to the number of users and the success of the unusual release of this report cycle and active user's number of a last report cycle are confirmed the cutting off rate of this report cycle.
Particularly, the number of users of the unusual release of cutting off rate=this report cycle of this report cycle/(number of users of the successful foundation of active user's number+this report cycle of a last report cycle).
That is to say that if the number of users that the number of users of the unusual release of this report cycle that foreground 50 reports is 3, success is set up is 5, active user's number is 6, active user's number of a last report cycle is 4, then the cutting off rate of this report cycle=3/ (4+5).When calculating the cutting off rate of next report cycle, need call the active user several 6 of this report cycle.
Preferably, in embodiments of the present invention, the base station is the eNB in the LET system.
Fig. 2 is the sketch map that the eNB of the embodiment of the invention handles, and is as shown in Figure 2, platform property module and the OMC of the chain of command of eNB, eNB.
Be example below with eNB, the technique scheme of the embodiment of the invention is described.Fig. 3 is the process chart of the ENB performance sampling MOD of the embodiment of the invention, and is as shown in Figure 3:
Step 1, the chain of command of eNB report to add 1 foreground (platform property module) to eNB when having number of users to increase, and when having number of users to reduce, report to subtract the 1 platform property module to eNB.
Step 2, the platform property module of eNB is responsible for the periodic sampling of number of users.Chain of command reports the added-time, and the data in this sampling period are added 1, reports when subtracting, to the data minus 1 in sampling period.After sample clock generator is overtime, the value in this sampling period is write in active user's counter.
Step 3, when reporting the moment to arrive, the foreground of eNB is that unit reports OMC with the measuring object with performance collection data, if report no show constantly, then execution in step 2.
Fig. 4 is the process chart that the oldest value of OMC performance of the embodiment of the invention gathers; As shown in Figure 4; On the foreground of eNB is that OMC put performance collection data in storage, and according to granularity the performance collection data in the storehouse is gathered after unit reported OMC with the measuring object with performance collection data; If the mode that gathers is the oldest value mode, gets the last value of granularity that reports of this granularity and gather value at last as this counter.
Embodiment 1
Below with under the object of sub-district, the realization flow situation of radio resource control (Radio Resource Control abbreviates RRC as) cutting off rate is an example, and technique scheme of the present invention is illustrated.Suppose that the sampling MOD cycle is 30S.Report cycle is 15 minutes between OMC and the foreground 50.The practical implementation step is following:
Step 1 has 5 user UE1 to UE5 to connect (Attach) success at certain day 11 o'clock to 11: 15.
Wherein, UE1 is the Attach success between 11 o'clock to 11: 30 seconds, and chain of command reports the report of user number to add 1 incident for the platform property module.The platform property module is 1 in the sampled value of this sampling granularity.Sample clock generator is overtime, and sampled value 1 is write in active user's counter, and Counter Value is 1.
Family of no use is inserted between 11: 30 seconds to 11: 10, and then sampling is always 1, and Counter Value is 1.
11: 10 assign between 11: 10: 30, UE2 to UE4 Attach success.Chain of command has reported 4 numbers of users to add 1 incident for the platform property module.The platform property module adds 4 times in this sampling granularity, so sampled value is 5.Sample clock generator is overtime, and sampled value is write in active user's counter, and Counter Value is 5.
Before 11: 15, do not have the user to insert again, then the Counter Value of active user's number is always 5.
Step 2,11: 15, report constantly and arrive, foreground 50 synchrodatas are given OMC webmaster 52.Wherein the current RRC number of users counters count value of this granularity is 5, and the unusual release times statistical value of this granularity is 0, and it is 5 that this granularity is successfully set up the number statistical value.
According to cutting off rate index formula=unusual number of users that discharges/(number of users that current number of users+success is set up); Then the cutting off rate index of this granularity is 0/ (0+5)=0.(current RRC number of users is 0, is because this Granular Computing value is got the value of last granularity).
Step 3,11: 15 to 11: 30: UE1 and UE2 caused having gone offline unusually owing to RLC ERROR IND.
Wherein, because RLC ERROR IND causes having gone offline unusually, chain of command reports the report of user number to subtract 1 incident for the platform property module to UE1 between 11: 15 to 11: 15: 30.The platform property module subtracts 1 in this sampling granularity, so sampled value is 4.Sample clock generator is overtime, and sampled value is write in active user's counter, and Counter Value is 4.
Family of no use changes between 11: 15 minutes 30 seconds 1, and then sampling is always 4, and Counter Value is 4.
11: 20 assign between 11: 20: 30, and UE2 causes having gone offline unusually owing to RLC ERROR IND.Chain of command reports the report of user number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 3.Sample clock generator is overtime, and sampled value is write in active user's counter.Counter Value is 3.
Before 11: 30, do not have the user to insert again, then the Counter Value of active user's number is always 3.
Step 4,11: 30, report constantly and arrive, foreground 50 synchrodatas are given OMC webmaster 52.Wherein the current RRC number of users counters count value of this granularity is 3, and the unusual release times statistical value of this granularity is 2, and it is 0 that this granularity is successfully set up the number statistical value.
According to cutting off rate index formula=unusual number of users that discharges/(number of users that current number of users+success is set up); Then the cutting off rate index of this granularity is 2/ (5+0)=40%.(current RRC number of users is 5, is because this Granular Computing value is got the value of last granularity).
Embodiment 2
Below with under the object of sub-district, the realization flow situation of ERAB cutting off rate is an example, and the technical scheme of the embodiment of the invention is elaborated, and supposes that the sampling MOD cycle is 30S, report cycle is 15 minutes between OMC and the foreground 50, the practical implementation step is following:
Step 1 has 5 user UE1 to UE5 successful at certain day 11 o'clock to 11: 15 Attach, and each user sets up a default bearing.
Wherein, UE1 is the Attach success between 11 and 11: 30 seconds, and chain of command reports the ERAB number to add 1 incident for the platform property module.The platform property module is 1 in the sampled value of this sampling granularity.Sample clock generator is overtime, and sampled value 1 is write in the current ERAB counter, and Counter Value is 1.
Family of no use is inserted between 11: 30 seconds to 11: 10, and then sampling is always 1, and Counter Value is 1.
11: 10 assign between 11: 10: 30, UE2 to UE4 Attach success.Chain of command has reported 4 ERAB numbers to add 1 incident for the platform property module.The platform property module adds 4 times in this sampling granularity, so sampled value is 5.Sample clock generator is overtime, and sampled value is write in the current ERAB counter, and Counter Value is 5.
Before 11: 15, do not have the user to insert again, the Counter Value of then current ERAB number is always 5.
Step 2,11: 15, report constantly and arrive, foreground 50 synchrodatas are given OMC webmaster 52.Wherein the current ERAB number counters count value of this granularity is 5, and it is 0 that this granularity discharges ERAB several statistical values unusually, and this granularity is successfully set up ERAB, and to count statistical value be 5.
According to cutting off rate index formula=unusual ERAB number that discharges/(the ERAB number that current ERAB number+success is set up); Then the ERAB cutting off rate index of this granularity is 0/ (0+5)=0.(current ERAB number of users is 0, is because this Granular Computing value is got the value of last granularity).
Step 3,11: 15 to 11: 30: UE1 and UE2 caused having gone offline unusually owing to RLC ERROR IND.
Wherein, UE1 11: 15 and 11: 15: 30 between because RLC ERROR IND causes having gone offline unusually, chain of command reports the ERAB number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 4.Sample clock generator is overtime, and sampled value is write in the current ERAB counter.Counter Value is 4.
Family of no use changes between 11: 15 minutes 30 seconds 1, and then sampling is always 4.Counter Value is 4.
11: 20 assign between 11: 20: 30, and UE2 causes having gone offline unusually owing to RLC ERROR IND.Chain of command reports the ERAB number to subtract 1 incident for the platform property module.The platform property module subtracts 1 in this sampling granularity, so sampled value is 3.Sample clock generator is overtime, and sampled value is write in the current ERAB counter, and Counter Value is 3.
Before 11: 30, do not have ERAB to insert again, the Counter Value of then current ERAB number is always 3.
Step 4,11: 30, report constantly and arrive, foreground 50 synchrodatas are given OMC webmaster 52.Wherein the current ERAB counter statistical value of this granularity is 3, and the unusual release times statistical value of this granularity is 2, and it is 0 that this granularity is successfully set up ERAB number statistical value.
According to cutting off rate index formula=unusual ERAB number that discharges/(the ERAB number that current ERAB number+success is set up); Then the cutting off rate index of this granularity is 2/ (5+0)=40% (current ERAB number is 5, is because this Granular Computing value is got the value of last granularity).
In sum; Technical scheme by means of the embodiment of the invention; Cutting off rate index through online active user's number at last granularity end being introduced next granularity is calculated; Solve in the prior art problem that cutting off rate accuracy that cutting off rate under special circumstances causes greater than 100% reduces, can under any circumstance guarantee the accuracy of cutting off rate.
Although be the example purpose, the preferred embodiments of the present invention are disclosed, it also is possible those skilled in the art will recognize various improvement, increase and replacement, therefore, scope of the present invention should be not limited to the foregoing description.

Claims (10)

1. a cutting off rate is confirmed method, it is characterized in that, comprising:
The number of users of the increase that the foreground of base station reports according to the chain of command of said base station and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the said sampling period;
The said sampling period then after; The number of users that the mode that said foreground adopts summation to add up is set up the number of users and the said success of the said unusual release in this sampling period writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that said active user's number in this sampling period is write active user's counter;
Report cycle then after, webmaster is given with said unusual release subscriber's meter, the said data sync that is created as on function family counter and the said active user's counter in said foreground;
Said webmaster is confirmed the cutting off rate of this report cycle according to active user's number of the number of users of the unusual release of this report cycle, the successful number of users of setting up and a last report cycle.
2. the method for claim 1 is characterized in that, the number of users that said webmaster is set up according to the number of users of the unusual release of this report cycle and success and active user's number of a last report cycle confirm that the cutting off rate of this report cycle is specially:
The number of users of the unusual release of cutting off rate=this report cycle of this report cycle/(number of users of the successful foundation of active user's number+this report cycle of a last report cycle).
3. the method for claim 1 is characterized in that, said foreground specifically comprises said unusual release subscriber's meter, the said data sync that is created as on function family counter and the said active user's counter to webmaster:
Said foreground is unit with the measuring object, gives webmaster with said unusual release subscriber's meter, the said data sync that is created as on function family counter and the said active user's counter.
4. method as claimed in claim 3 is characterized in that, said measurement unit comprises: sub-district, network element.
5. the method for claim 1 is characterized in that, said base station is the evolved base station in the long evolving system.
6. a cutting off rate is confirmed system, it is characterized in that, comprises base station foreground and webmaster, and wherein, base station foreground comprises:
Sampling module; Be used for the number of users of the increase that the chain of command according to said base station reports and the number of users of minimizing; The mode that adopts summation to add up is recorded in the number of users of interior unusual number of users that discharges of sampling period and success foundation, and calculates active user's number of real-time online in the said sampling period;
Processing module; Be used for the said sampling period then after; The number of users that the mode that adopts summation to add up is set up the number of users and the said success of the said unusual release in this sampling period writes unusual release subscriber's meter respectively and is created as function family counter, and adopts the mode that covers former data that said active user's number in this sampling period is write active user's counter;
Reporting module, be used for report cycle then after, give webmaster with said unusual release subscriber's meter, the said data sync that is created as on function family counter and the said active user's counter;
Said webmaster, the active user's number that is used for the number of users according to the unusual release of this report cycle, the successful number of users of setting up and a last report cycle is confirmed the cutting off rate of this report cycle.
7. device as claimed in claim 6 is characterized in that, said webmaster specifically is used for: the cutting off rate of confirming this report cycle by following formula:
The number of users of the unusual release of cutting off rate=this report cycle of this report cycle/(number of users of the successful foundation of active user's number+this report cycle of a last report cycle).
8. device as claimed in claim 6 is characterized in that reporting module specifically is used for:
With the measuring object is unit, gives webmaster with said unusual release subscriber's meter, the said data sync that is created as on function family counter and the said active user's counter.
9. device as claimed in claim 8 is characterized in that, said measurement unit comprises: sub-district, network element.
10. device as claimed in claim 6 is characterized in that, said base station is the evolved base station in the long evolving system.
CN201110321050.6A 2011-10-20 2011-10-20 Method and system for determining dropped call rate Active CN102387260B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201110321050.6A CN102387260B (en) 2011-10-20 2011-10-20 Method and system for determining dropped call rate
PCT/CN2012/072848 WO2013056530A1 (en) 2011-10-20 2012-03-22 Method, apparatus and system for determining call drop rate

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110321050.6A CN102387260B (en) 2011-10-20 2011-10-20 Method and system for determining dropped call rate

Publications (2)

Publication Number Publication Date
CN102387260A true CN102387260A (en) 2012-03-21
CN102387260B CN102387260B (en) 2014-03-12

Family

ID=45826209

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110321050.6A Active CN102387260B (en) 2011-10-20 2011-10-20 Method and system for determining dropped call rate

Country Status (2)

Country Link
CN (1) CN102387260B (en)
WO (1) WO2013056530A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102711155A (en) * 2012-06-06 2012-10-03 中兴通讯股份有限公司 Call drop rate acquisition method and system
WO2013056530A1 (en) * 2011-10-20 2013-04-25 中兴通讯股份有限公司 Method, apparatus and system for determining call drop rate
CN104202756A (en) * 2014-08-08 2014-12-10 中国联合网络通信集团有限公司 Network service call drop rate determining method and device
US9738663B2 (en) 2013-05-06 2017-08-22 Euticals S.P.A. Process for the preparation of aminoaryl- and aminoheteroaryl boronic acids and esters
CN107948447A (en) * 2017-12-21 2018-04-20 中国联合网络通信集团有限公司 Cutting off rate detection method and device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1501671A (en) * 2002-11-15 2004-06-02 华为技术有限公司 Telephone traffic statistical method based on rearward shift of task
CN1863035A (en) * 2005-07-04 2006-11-15 华为技术有限公司 Method for improving checking function fault-tolerant performance of counter
CN1863403A (en) * 2006-03-29 2006-11-15 华为技术有限公司 Load controlling method
CN101150831A (en) * 2007-10-24 2008-03-26 华为技术有限公司 Network element data processing method and device
CN101170751A (en) * 2007-11-23 2008-04-30 中兴通讯股份有限公司 A processing method, device and system for cluster system performance parameters

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100770613B1 (en) * 2005-09-30 2007-10-29 엘지전자 주식회사 Method for reporting data and the mobile terminal thereof
CN101330716A (en) * 2007-06-21 2008-12-24 中兴通讯股份有限公司 Method for improving capability of wireless communication system
CN102387260B (en) * 2011-10-20 2014-03-12 中兴通讯股份有限公司 Method and system for determining dropped call rate

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1501671A (en) * 2002-11-15 2004-06-02 华为技术有限公司 Telephone traffic statistical method based on rearward shift of task
CN1863035A (en) * 2005-07-04 2006-11-15 华为技术有限公司 Method for improving checking function fault-tolerant performance of counter
CN1863403A (en) * 2006-03-29 2006-11-15 华为技术有限公司 Load controlling method
CN101150831A (en) * 2007-10-24 2008-03-26 华为技术有限公司 Network element data processing method and device
CN101170751A (en) * 2007-11-23 2008-04-30 中兴通讯股份有限公司 A processing method, device and system for cluster system performance parameters

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013056530A1 (en) * 2011-10-20 2013-04-25 中兴通讯股份有限公司 Method, apparatus and system for determining call drop rate
CN102711155A (en) * 2012-06-06 2012-10-03 中兴通讯股份有限公司 Call drop rate acquisition method and system
US9738663B2 (en) 2013-05-06 2017-08-22 Euticals S.P.A. Process for the preparation of aminoaryl- and aminoheteroaryl boronic acids and esters
US10196406B2 (en) 2013-05-06 2019-02-05 Euticals S.P.A. Process for the preparation of aminoaryl- and aminoheteroaryl boronic acids and esters
CN104202756A (en) * 2014-08-08 2014-12-10 中国联合网络通信集团有限公司 Network service call drop rate determining method and device
CN104202756B (en) * 2014-08-08 2018-04-27 中国联合网络通信集团有限公司 A kind of definite method and device of Network cutting off rate
CN107948447A (en) * 2017-12-21 2018-04-20 中国联合网络通信集团有限公司 Cutting off rate detection method and device
CN107948447B (en) * 2017-12-21 2021-02-19 中国联合网络通信集团有限公司 Method and device for detecting call drop rate

Also Published As

Publication number Publication date
CN102387260B (en) 2014-03-12
WO2013056530A1 (en) 2013-04-25

Similar Documents

Publication Publication Date Title
US20150271342A1 (en) Network resource allocation in communication networks
CN102387260B (en) Method and system for determining dropped call rate
US20180270760A1 (en) Mobile battery consumption analysis system and method of operating on delta charge samples
EP2519074A1 (en) Method and device for adjusting service processing resources in a multi-mode base station system
CN108632863B (en) Traffic early warning method and device and server
US10887639B2 (en) Video data processing method and device
US20090111382A1 (en) Methods for scheduling collection of key performance indicators from elements in a communications network
CN105163344A (en) Method for positioning TD-LTE intra-system interference
CN104038941A (en) Network capacity expansion method and network capacity expansion device
CN110677854A (en) Method, apparatus, device and medium for carrier frequency capacity adjustment
CN100421514C (en) Method for distributing block domain data service radio channels
EP3952420A1 (en) Fingerprint library creation and application methods and apparatuses, centralized processing device and base station
US11075989B2 (en) Cellular network hierarchical operational data storage
CN113891336B (en) Communication network frequency-reducing network-exiting method, device, computer equipment and storage medium
CN110475255B (en) Network load prediction method and device
CN108768589B (en) Method and device for adjusting initial MCS configuration
CN102612058A (en) Method and device for determining performance index statistical result
CN106793093A (en) A kind of method for processing business and device
CN109964502B (en) Cell grouping method and device
CN103200585B (en) Signaling traffic subsystem, extension counter treatment system and method
CN102404743B (en) Interference matrix generating method of mobile phone measurement report based on voice and data service
US20120302205A1 (en) Method and system for the online charging of a subscriber, program and computer program product
CN100505609C (en) Method for affirming transmission mode parameter in collocation of wireless link control layer
US8880024B2 (en) Method, device and computer program product for updating location numbers on an MSC
CN102724677A (en) Overload indication threshold value dynamic adjusting system and adjusting method

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
EE01 Entry into force of recordation of patent licensing contract

Application publication date: 20120321

Assignee: SHENZHEN ZTE MICROELECTRONICS TECHNOLOGY CO., LTD.

Assignor: ZTE Corporation

Contract record no.: 2015440020319

Denomination of invention: Method and system for determining dropped call rate

Granted publication date: 20140312

License type: Common License

Record date: 20151123

LICC Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model