CN101175053B - Charging package management method for broadband remote connecting to server equipment - Google Patents
Charging package management method for broadband remote connecting to server equipment Download PDFInfo
- Publication number
- CN101175053B CN101175053B CN2007100774360A CN200710077436A CN101175053B CN 101175053 B CN101175053 B CN 101175053B CN 2007100774360 A CN2007100774360 A CN 2007100774360A CN 200710077436 A CN200710077436 A CN 200710077436A CN 101175053 B CN101175053 B CN 101175053B
- Authority
- CN
- China
- Prior art keywords
- charging
- bag
- described charging
- charging bag
- management method
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The present invention discloses a method for managing the charging packet for accessing broadband into the server equipment; a RADIUS charging packet is organized according to the received charging requirement and then the charging packet is emitted by a usable server when the usable server exists; when the response of emitting the charging packet is received, the processing flow after the successful emission of the charging packet is started. The technical proposal of the present invention increases the reliability of the transmission of RADIUS charging packet on the basis of ensuring the transmission efficiency.
Description
Technical field
The present invention relates to a kind of charging package management method, the charging package management method of especially a kind of BRAS (BroadbandRemote Access Server, Broadband Remote Access Server) equipment.
Background technology
BRAS equipment is the novel IAD of using towards broadband network, mainly finish two aspect functions, the one, network carrying function: the PPPoE (Point-to-PointPotocol Over Ethernet transmits the mode of PPP session on the Ethernet) that is responsible for the termination user connects, converges user's traffic engineering capability; The 2nd, control realizes function: match with Verification System, charge system and client management system and service strategy control system and realize authentication, charging and the management function that the user inserts.
RADIUS (remote authentication dial-in customer service) is used to provide authentication, mandate and record keeping service.Radius client sends user rs credentials and is connected parameter information to radius server with the form of RADIUS bag; Radius server carries out authentication and mandate to the radius client request, and beams back the response of RADIUS bag.
BRAS equipment cooperates the accounting management that realizes the user with backstage radius server and account software.Because the RADIUS bag transmits as UDP (User Datagram Protocol, User Datagram Protoco (UDP)) message, the reliability of transmission is lower, thereby has influenced the reliable realization of the billing function of BRAS equipment.
Summary of the invention
The technical problem to be solved in the present invention provides a kind of charging package management method of BRAS equipment, has improved the reliability of RADIUS account bag transmission under the situation that guarantees efficiency of transmission.
The technical solution adopted for the present invention to solve the technical problems is:
A kind of charging package management method of Broadband Remote Access Server equipment may further comprise the steps:
The RADIUS account bag is organized in the charging request that a, basis receive;
B, when having available server, send described charging bag by described available server;
C, when receiving the response after described charging bag sends, entering the handling process after the bag that charges sends successfully.
In the such scheme, described charging bag begin for chargeing to wrap or the situation of the end packet that charges under, when not having available server, enter the caching process flow process after then executing described step a; Described charging bag is under the situation of charging update package, when not having available server, then executes the handling process that enters behind the described step a after the bag that charges sends failure.
In the such scheme, described charging bag begin for chargeing to wrap or the situation of the end packet that charges under, when not receiving the response after described charging bag sends all the time, enter described caching process flow process after then executing described step b; Described charging bag is under the situation of charging update package, when not receiving the response after described charging bag sends all the time, then executes the handling process that enters behind the described step b after described charging bag sends failure.
In the such scheme, described charging bag is under the situation of charging end packet, among the described step a, after organizing described charging bag, whether the charging that also will judge described charging bag correspondence begins bag and exists, and exists if corresponding charging begins bag, then enters the charging inclusion to depositing flow process; Otherwise, carry out corresponding step according to the situation that exists of available server.
In the such scheme, described charging bag is under the situation of charging update package, among the described step a, organize described charging bag after, further comprising the steps of:
Whether the charging of 1. judging described charging bag correspondence begins bag and exists, if exist, enters step 2.; Otherwise, enter with available server have a situation corresponding step;
2. judge whether described charging bag leaves the waiting-timeout formation in, if enter the charging inclusion to depositing flow process; Otherwise, enter the handling process after described charging bag sends failure.
In the such scheme, described charging inclusion may further comprise the steps depositing flow process:
(1), described charging bag and corresponding charging are begun inclusion and begin to wrap the waiting-timeout formation at place leaving described charging in;
(2), judge whether to receive the response after described charging bag sends, if do not receive response, then enter the handling process after described charging bag sends failure, otherwise, enter described step b.
In the such scheme, described caching process flow process may further comprise the steps:
I, judge whether charging buffer memory switch is opened,, then enter the handling process after described charging bag sends failure if do not open, otherwise, described charging bag is stored in local cache;
Entering handling process charging bag send failure after when arriving the life cycle of II, described charging bag, otherwise, satisfy local cache and charge when wrapping the trigger condition that resends, get back to described step b.
In the such scheme, when sending described charging bag among the described step b, select an available server to send described charging bag,, then directly send described charging bag once more if do not receive the response after described charging bag sends and send number of times less than default repeating transmission number of times; If do not receive the response after described charging bag sends and send number of times to reach default repeating transmission number of times, then reselect an available server and send described charging bag once more.
In the such scheme, charge trigger condition that bag resends of described local cache is meant and reaches the setup time of local cache and have an available server.
In the such scheme, described charging bag is under the situation that begins to wrap of chargeing, store the deposit position and the state of described charging bag by the charging accelerator, the deposit position of described charging bag and state be the waiting-timeout formation and sent out, the waiting-timeout formation and wait to send out and local cache and wait to send out the three one of them.
Beneficial effect of the present invention mainly shows: charging of the present invention is assured reason mechanism under the prerequisite of the simplicity of assuring reason and RADIUS account bag efficiency of transmission that guarantees to charge, improve the reliability of RADIUS account bag transmission, thereby improved the reliability of the billing function realization of BRAS equipment.
Description of drawings
Fig. 1 is the charging package management method flow chart of BRAS equipment of the present invention;
Fig. 2 begins the package management method flow chart for the charging of BRAS equipment of the present invention;
Fig. 3 is the charging update package management method flow chart of BRAS equipment of the present invention;
Fig. 4 is the charging end packet management method flow chart of BRAS equipment of the present invention.
Embodiment
With reference to Fig. 1, a kind of charging package management method of BRAS equipment may further comprise the steps:
Step 101: organize the RADIUS account bag according to the charging request that receives;
Step 102: when having available server, send described charging bag by available server;
Step 103: when receiving the response after described charging bag sends, enter the handling process after the bag that charges sends successfully.
The RADIUS account bag comprises chargeing and begins bag, charging update package and charging end packet, below just in conjunction with Fig. 2 to Fig. 4 the management of the above-mentioned three kinds bags that charge are further described respectively.
With reference to Fig. 2, BRAS equipment begins bag when managing to charging, may further comprise the steps:
Step 201: receiving charges begin request after, the relevant information that charging is begun to ask adds the wait-for-response formation;
Step 202: organize RADIUS account to begin bag;
Step 203: judge whether to exist available server,, enter step 204 if exist; If do not exist, enter step 208;
Step 204: will charge begins to wrap the waiting-timeout formation that adds corresponding with service device group, simultaneously, revises positional information and state that the charging on the Adelson-Velskii-Landis tree (balanced binary ordering tree) that is kept at the charging OverDrive Processor ODP begins to wrap;
Step 205-step 207: select an available server to send charging and begin bag; Do not respond and send number of times less than default repeating transmission number of times as if receiving, then directly send charging once more and begin bag; If receive that responding and send number of times does not reach default repeating transmission number of times, then reselect an available server and send once more to charge and begin bag; Therebetween, in case receive response, chargeing on deletion wait-for-response formation, waiting-timeout formation and the charging OverDrive Processor ODP Adelson-Velskii-Landis tree begins to wrap corresponding information, and charges and begin to wrap processing after sending successfully, enters step 211 afterwards; If available server all is used, do not receive all the time any response then to enter step 208;
Step 208: judge whether charging buffer memory switch is opened,, enter step 209,, then enter step 210 if charging buffer memory switch is opened if do not open;
Step 209: after reclaiming the respective queue resource, chargeing begins to wrap the processing that sends after failing, and enters step 211 afterwards;
Step 210: will charge to begin to wrap and leave local cache in, and promptly add the charging buffer queue, and simultaneously, revise the positional information and the state that charge and begin to wrap on the Adelson-Velskii-Landis tree; During charging begins to wrap life cycle no show, charge when beginning to wrap the trigger condition that resends, get back to step 204 if satisfy local cache; Arrived life cycle in case charge to begin to wrap, the charging of then deleting in the charging buffer queue begins bag, and chargeing begins to wrap the processing that sends after failing, and enters step 211 afterwards;
Step 211: finish all operations.
In the above-mentioned flow process, local cache charges and to begin to wrap the trigger condition that resends and be meant and reach the setup time of local cache and have an available server.Deposit position that charging begins to wrap and state information are kept on the Adelson-Velskii-Landis tree of charging OverDrive Processor ODP, keyword is the standard attribute account-session-id of RADIUS, wherein comprising information is: the deposit position and the state that charge and to begin to wrap specifically comprise following three kinds of situations: the waiting-timeout formation and sent out, the waiting-timeout formation and wait to send out, charging buffer queue and wait to send out.
With reference to Fig. 3, when BRAS equipment manages the charging update package, may further comprise the steps:
Step 301: after receiving the charging update request, with the relevant information adding wait-for-response formation of charging update request;
Step 302: organize the RADIUS account update package;
Step 303: judge that corresponding charging begins bag and whether exists,, enter step 307 if do not exist, otherwise, enter step 304;
Step 304: judge that according to the deposit position information that the correspondence charging of storing on the Adelson-Velskii-Landis tree begins to wrap corresponding charging begins bag and whether leaves the waiting-timeout formation in,, enter step 305 if leave the waiting-timeout formation in; Otherwise, enter step 312;
Step 305-step 306: the charging update package is begun inclusion to depositing with corresponding charging, and judge that this charging begins bag and whether sent success, promptly whether received the response after this charging begins to wrap transmission, if beginning bag, this charging sent success, enter step 308, otherwise, enter step 312; Wherein, charging update package and corresponding charging are begun inclusion when depositing, become a partner and deposit, cover original charging update package when then depositing if this charging begins to wrap existing charging update package;
Step 307: judge whether to exist available server,, enter step 308 if exist; If do not exist, enter step 312;
Step 308: the waiting-timeout formation that the charging update package is added corresponding with service device group;
Step 309-step 311: select an available server to send the charging update package; If do not receive and respond and send number of times, then directly send the charging update package once more less than default repeating transmission number of times; If do not receive that responding and send number of times reaches default repeating transmission number of times, then reselects an available server and sends the charging update package once more; Therebetween, in case receive response, the charging update package in deletion wait-for-response formation, the waiting-timeout formation, and the processing of the update package that charges after sending successfully enter step 313 afterwards; If available server all is used, do not receive any response all the time, then reclaim the respective queue resource after, enter step 312;
Step 312: the update package that charges sends the processing after the failure, enters step 313 afterwards;
Step 313: finish all operations.
With reference to Fig. 4, when BRAS equipment manages the charging end packet, may further comprise the steps:
Step 401: after receiving the charging ending request, with the relevant information adding wait-for-response formation of charging ending request;
Step 402: organize the RADIUS account end packet;
Step 403: judge that corresponding charging begins bag and whether exists,, enter step 406 if do not exist, otherwise, enter step 404;
Step 404-step 405: the charging end packet is begun inclusion to depositing with corresponding charging, and judge that this charging begins bag and whether sent success, promptly whether received the response after this charging begins to wrap transmission, if beginning bag, this charging sent success, enter step 407, otherwise, enter step 413; Wherein, charging end packet and corresponding charging are begun inclusion when depositing, become a partner and deposit, cover original charging end packet when then depositing if this charging begins to wrap existing charging end packet;
Step 406: judge whether to exist available server,, enter step 407 if exist; If do not exist, enter step 411;
Step 407: the waiting-timeout formation that the charging end packet is added corresponding with service device group;
Step 408-step 410: select an available server to send the charging end packet; If do not receive and respond and send number of times, then directly send the charging end packet once more less than default repeating transmission number of times; If do not receive that responding and send number of times reaches default repeating transmission number of times, then reselects an available server and sends the charging end packet once more; Therebetween, in case receive response, the charging end packet in deletion wait-for-response formation, the waiting-timeout formation, and the processing of the end packet that charges after sending successfully enter step 414 afterwards; If available server all is used, do not receive all the time any response then to enter step 411;
Step 411: judge whether charging buffer memory switch is opened,, after the recovery respective queue resource, enter step 413 if do not open; If charging buffer memory switch is opened, then enter step 412;
Step 412: leave the charging end packet in local cache, promptly add the charging buffer queue; During the life cycle no show of charging end packet,, get back to step 407 if when satisfying the trigger condition that local cache charging end packet resends; In case the charging end packet has arrived life cycle, then deletes the charging end packet in the charging buffer queue, enters step 413;
Step 413: the end packet that charges sends the processing after the failure, enters step 414 afterwards;
Step 414: finish all operations.
In the above-mentioned flow process, the trigger condition that local cache charging end packet resends is meant and reaches the setup time of local cache and have an available server.
More than having described charges with user-dependent three classes wraps in management method on the BRAS equipment, under the prerequisite of guaranteed efficiency, having improved the reliability of the bag transmission of chargeing.
Claims (9)
1. the charging package management method of a Broadband Remote Access Server equipment is characterized in that, may further comprise the steps:
Remote authentication dial-in customer service charging bag is organized in the charging request that a, basis receive;
B, when not having available server, if described charging bag begins for chargeing to wrap or the situation of the end packet that charges under, then enter the caching process flow process;
When not having available server,, then enter the handling process after the bag that charges sends failure if described charging bag is under the situation of charging update package;
When having available server, send described charging bag by described available server;
C, when receiving the response after described charging bag sends, entering the handling process after the bag that charges sends successfully.
2. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 1, it is characterized in that: described charging bag begin for chargeing to wrap or the situation of the end packet that charges under, if available server all is used, when not receiving the response after described charging bag sends all the time, enter described caching process flow process after then executing described step b; Described charging bag is under the situation of charging update package, when not receiving the response after described charging bag sends all the time, then executes the handling process that enters behind the described step b after described charging bag sends failure.
3. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 2, it is characterized in that: described charging bag is under the situation of charging end packet, among the described step a, after organizing described charging bag, whether the charging that also will judge described charging bag correspondence begins bag and exists, exist if corresponding charging begins bag, then enter the charging inclusion depositing flow process; Otherwise, carry out corresponding step according to the situation that exists of available server.
4. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 3 is characterized in that: described charging bag is under the situation of charging update package, among the described step a, organize described charging bag after, further comprising the steps of:
Whether the charging of 1. judging described charging bag correspondence begins bag and exists, if exist, enters step 2.; Otherwise, carry out corresponding step according to the situation that exists of available server;
2. judge whether described charging bag leaves the waiting-timeout formation in, if enter the charging inclusion to depositing flow process; Otherwise, enter the handling process after described charging bag sends failure.
5. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 4 is characterized in that, described charging inclusion may further comprise the steps depositing flow process:
(1), described charging bag and corresponding charging are begun inclusion and begin to wrap the waiting-timeout formation at place leaving described charging in;
(2), judge whether to receive the response after described charging bag sends, if available server all is used, do not receive response all the time, then enter the handling process after described charging bag sends failure, otherwise, enter described step b.
6. as the charging package management method of one of them described Broadband Remote Access Server equipment of claim 1 to 5, it is characterized in that described caching process flow process may further comprise the steps:
I, judge whether charging buffer memory switch is opened,, then enter the handling process after described charging bag sends failure if do not open, otherwise, described charging bag is stored in local cache;
Entering handling process charging bag send failure after when arriving the life cycle of II, described charging bag, otherwise, satisfy local cache and charge when wrapping the trigger condition that resends, get back to described step b.
7. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 6, it is characterized in that, when sending described charging bag among the described step b, select an available server to send described charging bag, if do not receive the response after described charging bag sends and send number of times, then directly send described charging bag once more less than default repeating transmission number of times; If do not receive the response after described charging bag sends and send number of times to reach default repeating transmission number of times, then reselect an available server and send described charging bag once more.
8. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 7 is characterized in that: charge trigger condition that bag resends of described local cache is meant and reaches the setup time of local cache and have an available server.
9. the charging package management method of Broadband Remote Access Server equipment as claimed in claim 8, it is characterized in that: described charging bag is under the situation that begins to wrap of chargeing, store the deposit position and the state of described charging bag by the charging accelerator, the deposit position of described charging bag and state be the waiting-timeout formation and sent out, the waiting-timeout formation and wait to send out and local cache and wait to send out the three one of them.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100774360A CN101175053B (en) | 2007-11-28 | 2007-11-28 | Charging package management method for broadband remote connecting to server equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100774360A CN101175053B (en) | 2007-11-28 | 2007-11-28 | Charging package management method for broadband remote connecting to server equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101175053A CN101175053A (en) | 2008-05-07 |
| CN101175053B true CN101175053B (en) | 2011-01-05 |
Family
ID=39423317
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007100774360A Expired - Fee Related CN101175053B (en) | 2007-11-28 | 2007-11-28 | Charging package management method for broadband remote connecting to server equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101175053B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101478409B (en) * | 2009-02-09 | 2011-09-21 | 中兴通讯股份有限公司 | Fee charging control method and wideband access server |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1536811A (en) * | 2003-04-09 | 2004-10-13 | 华为技术有限公司 | Network authentication charging method |
| CN1614930A (en) * | 2003-11-06 | 2005-05-11 | 华为技术有限公司 | Charging server detecting system and method in wide-band inserting system |
| CN1878068A (en) * | 2006-07-12 | 2006-12-13 | 华为技术有限公司 | Multi-service selective network and implementation method for service supporting same |
-
2007
- 2007-11-28 CN CN2007100774360A patent/CN101175053B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1536811A (en) * | 2003-04-09 | 2004-10-13 | 华为技术有限公司 | Network authentication charging method |
| CN1614930A (en) * | 2003-11-06 | 2005-05-11 | 华为技术有限公司 | Charging server detecting system and method in wide-band inserting system |
| CN1878068A (en) * | 2006-07-12 | 2006-12-13 | 华为技术有限公司 | Multi-service selective network and implementation method for service supporting same |
Non-Patent Citations (1)
| Title |
|---|
| JP特开2007-226620A 2007.09.06 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101175053A (en) | 2008-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104753980B (en) | Data transmission method and relevant apparatus and communication system | |
| CN101141420B (en) | Method and system for performing data communication between private network and public network | |
| CN102904930B (en) | The dual accelerated method of content and network-linked and system | |
| CN101997661B (en) | Data packet sending method, data packet acquiring method and device | |
| CN101521683B (en) | Online game system and accessing method and client communication method thereof | |
| CN105871703A (en) | Push and pull combined instant communication message acquisition system and method | |
| CN103986647A (en) | Message transmission method and device | |
| CN102422704A (en) | Methods for transmitting rlc data blocks | |
| CN102143444A (en) | Method, relevant equipment and system for pushing service delivery platform message | |
| CN103856440A (en) | Message processing method, server and message processing system based on distributed bus | |
| CN102892089A (en) | Message pushing method, device and system | |
| CN105939297A (en) | TCP message reassembling method and TCP message reassembling device | |
| CN103547339B (en) | File uploading method, client side and server side | |
| CN108900392A (en) | A kind of method and system of smart home multiple gateway access | |
| CN102833339B (en) | CDN (Content Delivery Network) and network fused service control method and service control equipment | |
| CN105991680A (en) | Internet of things smart device software automatic upgrading method and system | |
| CN102065136A (en) | P2P (Peer-to-Peer) network safety data transmission method and system | |
| CN102752188A (en) | Transmission control protocol connection migratory method and system | |
| CN102137088B (en) | Message exchanging method for service delivery platform (SDP) system, SDP system and device | |
| CN101175053B (en) | Charging package management method for broadband remote connecting to server equipment | |
| CN103856435A (en) | Address resolution protocol cache and caching method | |
| CN101388854A (en) | Method, system and gateway for multimedia message transmission | |
| JP3893247B2 (en) | Data distribution management device | |
| CN106302426A (en) | A kind of udp protocol stack implementation method of band retransmission mechanism based on FPGA | |
| CN102681969B (en) | Based on the long frame data transmission method of CAN |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110105 Termination date: 20161128 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |