CN102148688A - Charging method and NAS (Network Access Server) - Google Patents
Charging method and NAS (Network Access Server) Download PDFInfo
- Publication number
- CN102148688A CN102148688A CN2010101095585A CN201010109558A CN102148688A CN 102148688 A CN102148688 A CN 102148688A CN 2010101095585 A CN2010101095585 A CN 2010101095585A CN 201010109558 A CN201010109558 A CN 201010109558A CN 102148688 A CN102148688 A CN 102148688A
- Authority
- CN
- China
- Prior art keywords
- radius server
- nas
- radius
- main
- message
- 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
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a charging method and an NAS (Network Access Server). The method comprises the following steps of: arranging at least two RADIUS (Remote Authentication Dial-In User Service) servers for each NAS, wherein the RADIUS servers have the same user configuration, and the NAS is provided with the same Identifier counter for all the RADIUS servers; sending an authentication request message aiming at a user to a main RADIUS server and keeping the authentication request message when the NAS finds that the user logs on and sending the stored authentication request message to all standby RADIUS servers when an authentication passing message of the main RADIUS server is received; and sending the same charging updating message to the standby RADIUS servers by the NAS when sending a charging updating message to the main RADIUS server and permitting the user to be continuously online only if the NAS receives an answering message answered by any RADIUS server in a preset duration. The invention improves the transaction and charging reliability of users.
Description
Technical field
The present invention relates to the billing technology field, be specifically related to charging method and network access server.
Background technology
Usually, the user is by network access server (NAS, Network Access Server) authentication is entered the Internet, NAS is again by remote authentication dial-in user service (RADIUS, RemoteAuthentication Dial In User Service) agreement, on radius server, the user is authenticated, user's charge information is sent on the radius server charge.
As shown in Figure 1, the structure of RADIUS message is as follows:
Code: code field, 1 byte is used to illustrate the type of RADIUS message;
Identifier: identification field, 1 byte is used for matching request and answer;
Length: length field, 2 bytes have indicated the length of data package that comprises coding, identifier, length, authentication code and Attribute domain;
Authenticator: authentication code field, 16 bytes;
Attributes: Attribute domain field.
Wherein, the Identifier field is used to distinguish the request of NAS transmission and replying of radius server response.RADIUS request message of the every transmission of NAS (message that does not comprise repeating transmission), all the Identifier value is increased 1, the Identifier of each request message is inequality like this, radius server just can be distinguished different request messages according to the Identifier field, when radius server is responded request message, Identifier value in the request message is put in the response message, and NAS just can learn that this is replied is replying at which request message according to the Identifier in the response message like this.
In order to guarantee reliability, as shown in Figure 2, dispose two radius servers usually for a NAS, respectively as active and standby server.Specific implementation mainly contains two kinds:
One, NAS carries out authentification of user to main radius server earlier, after authentication is passed through, send charging message to main radius server, when obstructed or main radius server breaks (DOWN) between NAS and the main radius server, when NAS can not get the response of main radius server at the charging message of some, force users rolled off the production line, and on the radius server user was being authenticated fully again, after authentication is passed through, send charging message to being equipped with radius server.
The shortcoming of this method is: when obstructed or main radius server broke between NAS and the main radius server, the NAS force users rolled off the production line, and can make like this and the customer service aborted reduce user experience.
Two, NAS carries out authentification of user to main radius server, after authentication is passed through, to active and standby radius server broadcasting charging message.
The shortcoming of this method is: compatible relatively poor, because: radius server normally can not handled charging message under the situation by authentication the user, and when the software of active and standby radius server is inequality, because the Database Systems that software uses, the memory cell of data etc. may be inequality, realize that the backup between two class databases is very difficult, thereby reduced the charging reliability.
Summary of the invention
The invention provides charging method and NAS, to improve customer service reliability and charging reliability.
Technical scheme of the present invention is achieved in that
A kind of charging method, for each NAS is provided with at least two radius servers, wherein one is main radius server, other is for being equipped with radius server, and the user on all radius servers disposes identical, and NAS is same Identifier counter for all radius servers are provided with, and this method comprises:
NAS finds that the user reaches the standard grade, to the authentication request packet of main radius server transmission at this user, and preserve this authentication request packet, when message is passed through in the authentication that receives main radius server, the authentication request packet of preserving is sent to all be equipped with radius server;
NAS is in the billing update packet that sends to main radius server at this user, be equipped with radius server to all and send identical billing update packet, Identifier field value in all billing update packets is identical, in default duration, as long as NAS receives the response message that arbitrary radius server is responded, it is online then to allow the user to continue.
Described NAS further comprises after all are equipped with the identical billing update packet of radius server transmission when main radius server sends billing update packet:
NAS does not receive main radius server, does not receive any response message that radius server returns that is equipped with yet in the first default duration, then according to default retransmission rules, repeat to send described billing update packet to all radius servers, if in default second duration, do not receive the response message that any radius server returns yet, then force users rolls off the production line.
Described in default duration, as long as NAS receives the response message that arbitrary radius server is responded, then thinking charges normally comprises:
NAS receives the response message at described billing update packet for the first time in default duration, this response message is handled, and the follow-up response message that receives at described billing update packet directly abandons this response message.
Describedly the authentication request packet of preserving is sent to all be equipped with radius server and comprise:
Be equipped with the authentication request packet that radius server sends preset times to all.
Described NAS with the authentication request packet of preserving send to all be equipped with after the radius server, when main radius server sends billing update packet, be equipped with radius server to all and further comprise before sending identical billing update packet:
NAS sends the beginning message that charges to main radius server, after receiving the charging response message that main radius server returns, according to default retransmission rules, is equipped with radius server to all and repeats to send to charge and begin message;
Perhaps further comprise: NAS is equipped with radius server to main radius server and all simultaneously and repeats to send the beginning message that charges according to default retransmission rules.
As long as described NAS receives the response message that arbitrary radius server is responded, then allow the user to continue online further comprising afterwards:
Charging at described user finishes, and NAS is equipped with radius server to main radius server and all simultaneously and repeats to send accounting completion packet according to default retransmission rules.
A kind of NAS, corresponding at least two radius servers of this NAS, wherein one is main radius server, other is for being equipped with radius server, and the user on all radius servers disposes identical, and NAS is same Identifier counter for all radius servers are provided with, and this NAS comprises:
Authentication module, find that the user reaches the standard grade,, and preserve this authentication request packet to the authentication request packet of main radius server transmission at this user, when message is passed through in the authentication that receives main radius server, the authentication request packet of preserving is sent to all be equipped with radius server;
Accounting module, when main radius server sends billing update packet, be equipped with radius server to all and send identical billing update packet, Identifier field value in all billing update packets is identical, in default duration, as long as NAS receives the response message that arbitrary radius server is responded, then think and charge normally.
Described accounting module is further used for, be equipped with the identical billing update packet of radius server transmission to all after, if in the first default duration, do not receive main radius server, do not receive any response message that radius server returns that is equipped with yet, then according to default retransmission rules, repeat to send described billing update packet to all radius servers, if in default second duration, do not receive the response message that any radius server returns yet, then force users rolls off the production line.
Described accounting module is further used for, when chargeing beginning, send the beginning message that charges to main radius server, after receiving the charging response message that main radius server returns, according to default retransmission rules, be equipped with radius server to all and repeat to send the beginning message that charges;
Perhaps, when chargeing beginning,, be equipped with radius server to main radius server and all simultaneously and repeat to send the beginning message that charges according to default retransmission rules.
Described accounting module is further used for, and when chargeing end, according to default retransmission rules, is equipped with radius server to main radius server and all simultaneously and repeats to send accounting completion packet.
Compared with prior art, among the present invention, for each NAS is provided with at least two radius servers, user on all radius servers disposes identical, and for a user, NAS is first to the authentication request packet of main radius server initiation at this user, and preserves this authentication request packet, after authentication is passed through, NAS is equipped with radius server to all and sends this authentication request packet, afterwards, NAS sends same billing update packet to all radius servers simultaneously, like this, as long as NAS is normal with being connected of a radius server, NAS just can receive response message, and is online thereby NAS will allow the user to continue, and improves the customer service reliability; Simultaneously, as long as NAS is normal with being connected of a radius server, user's charge information just can not lost, thereby has guaranteed the charging reliability.And the present invention does not need to increase the attribute of any private, does not need existing radius server is changed, and realizes that cost is lower.
Description of drawings
Fig. 1 is the structural representation of RADIUS message;
Fig. 2 is existing radius server backup networking diagram;
The charging method flow chart that Fig. 3 provides for the embodiment of the invention;
The structural representation of the NAS that Fig. 4 provides for the embodiment of the invention.
Embodiment
The present invention is further described in more detail below in conjunction with drawings and the specific embodiments.
The charging method flow chart that Fig. 3 provides for the embodiment of the invention, as shown in Figure 3, its concrete steps are as follows:
Step 301: for each NAS is provided with at least two radius servers, wherein one is main radius server, and other all is to be equipped with radius server, and the user who preserves on active and standby radius server configuration is all identical; NAS is provided with a global I dentifier counter for all radius servers simultaneously.
The user who preserves on the active and standby radius server disposes identical, then will make: if a user can then also can be equipped with the authentication of radius server by all by the authentication of main radius server.
NAS is provided with a global I dentifier counter for all radius servers, and like this, NAS only needs according to Identifier field value matching request and response message, and does not need to be concerned about the source address and the port of the message that receives.
Step 302:NAS detects the user and reaches the standard grade, and the state of finding active and standby radius server all is to activate (Active), then username and password is carried at and sends to main radius server in the authentication request packet, preserves this authentication request packet simultaneously.
Here, authentication protocol between NAS and user can adopt password authentication protocol (PAP, PasswordAuthentication Protocol), also can adopt challenge handshake authentication protocol (CHAP, ChallengeHandshake Authentication Protocol).
Step 303:NAS receives authentication that main radius server returns by message, and then the authentication request packet that step 302 is preserved sends to respectively and respectively is equipped with radius server.
Because it is identical that the user who preserves on the active and standby radius server disposes, then here, NAS with authentication request packet send to respectively be equipped with radius server after, will inevitably receive that respectively being equipped with the authentication that radius server returns passes through message.
In order to prevent that sending to the authentication request packet that is equipped with radius server loses, NAS can retransmit this message according to preset rules, and after transmission finishes, the authentication request packet that deletion is preserved.Simultaneously, because NAS has received main radius server at the response message of this authentication request packet, so NAS directly abandons this response message and gets final product when receiving radius server fully to the response message of authentication request packet.
If NAS receives the authentication refusal message that main radius server returns, perhaps in default duration, do not receive the response message of main radius server, then delete the authentication request packet that step 302 is preserved.
Arbitrary radius server to the NAS return authentication when the message, the information of reaching the standard grade that all can preserve the user comprises: user name, reach the standard grade constantly etc.
Step 304:NAS begins message to the charging that main radius server sends the user, preserves this charging beginning message simultaneously.
Step 305:NAS receives the charging that main radius server returns and begins response message, and then the charging that step 304 is preserved begins message and sends to respectively and respectively be equipped with radius server.
The beginning message is the sign that charges and begin owing to charge, extremely important to charging process, therefore, here, if NAS does not receive that default the wait in the duration charging that main radius server returns begins response message, then, repeat to send the beginning message that charges to main radius server according to default retransmission rules.Simultaneously, in order to guarantee that radius server can be received the beginning message that charges fully, NAS also can repeat to send the beginning message that charges to respectively being equipped with radius server according to default retransmission rules.
Perhaps, step 304～305 are also replaceable to be: NAS is according to default retransmission rules, is equipped with the charging that radius server repeats to send the user to main radius server and all simultaneously and begins message.
Arbitrary radius server receives the beginning message that charges, charge information that can recording user as: charge the zero hour etc.
Step 306:NAS regularly sends user's billing update packet to main radius server, simultaneously, this billing update packet is sent to respectively radius server fully.
The content (comprising Identifier) that sends to the billing update packet of active and standby radius server is identical, and different is destination address and port information.
Step 307: for each billing update packet that sends, NAS judges whether to receive the response message that any one radius server returns in first scheduled duration, if, execution in step 308; Otherwise, execution in step 309.
Arbitrary radius server is when the echo reply message, and the charge information that all can upgrade the user is as charging duration etc.
Step 308:NAS judges whether to charge and finishes, if, execution in step 312; Otherwise, return step 306.
Step 309:NAS repeats to send current billing update packet to all radius servers according to default retransmission rules.
Step 310: repeating transmission finishes, and NAS judges whether to receive the response message that any one radius server returns in the second default duration, if return step 308; Otherwise, execution in step 311.
Step 311:NAS determines to interrupt with being connected of all radius servers, and then force users rolls off the production line, and goes to step 312.
When being connected all just often of NAS and all radius servers, because the response message that all radius servers are responded is identical, NAS only can handle the response message of receiving at first, as long as receive a response message, just think that this billing update packet is responded, promptly, as long as receive the response message of an Identifier in the coupling billing update packet, no matter this response message is main radius server or is equipped with the radius server response, NAS thinks that this billing update packet has obtained response, receive the response message with same Identifier again, NAS directly abandons and gets final product.
The structure of replying (Accounting-response) message of billing update packet is as follows:
Code:1 byte, value are 5, and the expression type of message is the charging response message;
The Identifier:1 byte, value is identical with corresponding billing update packet;
Length:2 byte, value are fixed value 20;
Authenticator:16 byte, the field that authenticates mutually for NAS and radius server;
Authenticator＝MD5(Code+Identifier+Length+RequestAuth+Attributes+Secret)
Wherein, MD5 is the algorithm title, and Code, Identifier, Length are the field value in the charging response message; RequestAuth is the Authenticator field value in the corresponding billing update packet; Usually, the charging response message is not need the Attributes field, if the Attribute field is arranged, then because the configuration of all radius servers is identical, therefore, all radius servers are identical at the Attribute field value in the response message of same billing update packet; Secret is the shared key of NAS and all radius servers.Like this, all radius servers are identical at the Authenticator field value in the response message of same billing update packet
As seen, at same billing update packet, each field value in the response message that different radius servers are responded is identical.
Step 312:NAS sends accounting completion packet to all radius servers.
Because accounting completion packet is the sign that charges and finish, also very important to charging process, therefore, here, NAS can repeat to send accounting completion packet to all radius servers according to default retransmission rules.
In the embodiment of the invention, after sending billing update packet, as long as NAS receives any one response message with the Identifier of this billing update packet coupling, just think that this billing update packet is responded, that is: which radius server NAS can be indifferent to response message from, and is based on the following:
At first, in the radius protocol the source address of the response message that receives of regulation must be the destination address of corresponding requests message.The source address of the response message that care receives whether has following two kinds of implementations:
One, be indifferent to the source address of response message, at this moment, NAS can the Identifier field be set to overall sharing, promptly, NAS only is provided with a global I dentifier counter, and, radius server sends billing update packet to all radius servers simultaneously, and the Identifier field value in the message is identical, like this, every primary charging that sends simultaneously upgrades message, the value of an Identifier counter of change, and NAS is in matching request with when replying, only need to consider the Identifier field value of response message, and the source address that need not consider response message promptly: the address of radius server.
Two, be concerned about the source address of response message, at this moment, NAS can be provided with an Identifier counter at each radius server, when a radius server sends message, only change the value of the Identifier counter of this server correspondence, and, because the Identifier counter of each radius server is independently, therefore, in matching request with when replying, the source address that also need consider response message promptly: the address of radius server.
As seen, because in the step 301, NAS is provided with a global I dentifier counter, and, sending billing update packet simultaneously to all radius servers, the Identifier field value in the message is identical, like this, the Identifier field value of the response message that all radius servers are responded is also identical, thereby NAS only need come matching request and response message according to the Identifier field value, and does not need to be concerned about the source address of response message.
From flow process shown in Figure 3 as can be seen, because NAS sends billing update packet to all radius servers simultaneously, Identifier field value in the message is identical, like this, as long as NAS is normal with being connected of a radius server, NAS just can receive response message, thereby NAS just can force users not roll off the production line, only when NAS interrupted with being connected of all radius servers, NAS just understood force users and rolls off the production line, and had so just guaranteed that customer service can aborted; Simultaneously, as long as NAS is normal with being connected of a radius server, user's charge information just can not lost, thereby has guaranteed the charging reliability.In addition, because that the user on all radius servers disposes is identical, and NAS can initiate user authentication process to all radius servers, therefore, all radius servers all can to the user reach the standard grade and charge information carries out synchronously and backup.
The structural representation of the NAS that Fig. 4 provides for the embodiment of the invention, as shown in Figure 4, corresponding at least two radius servers of this NAS, wherein one is main radius server, other is for being equipped with radius server, and the user on all radius servers dispose identical, and NAS for all radius servers are provided with same Identifier counter, this NAS mainly comprises: authentication module 41 and accounting module 42, wherein:
Authentication module 41: find that a user reaches the standard grade, to the authentication request packet of main radius server transmission at this user, and preserve this authentication request packet, when message is passed through in the authentication that receives main radius server, the authentication request packet of preserving is sent to all be equipped with radius server, send the indication of chargeing to accounting module 42.
Accounting module 42: receive the charging indication that authentication module 41 is sent, send the beginning message that charges, after receiving the response message that main radius server returns, be equipped with radius server to all and send the beginning message that charges to main radius server; Regularly be equipped with radius server and send billing update packet simultaneously to main radius server and all, Identifier field value in all billing update packets of Fa Songing is identical simultaneously, in default duration, as long as NAS receives the response message that arbitrary radius server is responded, then think and charge normally; Charge when finishing, be equipped with radius server to main radius server and all simultaneously and send identical accounting completion packet.
Accounting module 42 is further used for, be equipped with to main radius server and all after radius server sends billing update packet simultaneously, if in the first default duration, do not receive main radius server, do not receive any response message that radius server returns that is equipped with yet, then according to default retransmission rules, repeat to send described billing update packet to all radius servers, if in default second duration, do not receive the response message that any radius server returns yet, then force users rolls off the production line.
The above only is process of the present invention and method embodiment, in order to restriction the present invention, all any modifications of being made within the spirit and principles in the present invention, is not equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. charging method, it is characterized in that, for each network access server NAS is provided with at least two remote authentication dial-in user service radius servers, wherein one is main radius server, other is for being equipped with radius server, and the user on all radius servers disposes identical, and NAS for all radius servers are provided with same Identifier counter, this method comprises:
NAS finds that the user reaches the standard grade, to the authentication request packet of main radius server transmission at this user, and preserve this authentication request packet, when message is passed through in the authentication that receives main radius server, the authentication request packet of preserving is sent to all be equipped with radius server;
NAS is in the billing update packet that sends to main radius server at this user, be equipped with radius server to all and send identical billing update packet, Identifier field value in all billing update packets is identical, in default duration, as long as NAS receives the response message that arbitrary radius server is responded, it is online then to allow the user to continue.
2. the method for claim 1 is characterized in that, described NAS further comprises after all are equipped with the identical billing update packet of radius server transmission when main radius server sends billing update packet:
NAS does not receive main radius server, does not receive any response message that radius server returns that is equipped with yet in the first default duration, then according to default retransmission rules, repeat to send described billing update packet to all radius servers, if in default second duration, do not receive the response message that any radius server returns yet, then force users rolls off the production line.
3. the method for claim 1 is characterized in that, and is described in default duration, as long as NAS receives the response message that arbitrary radius server is responded, then thinking charges normally comprises:
NAS receives the response message at described billing update packet for the first time in default duration, this response message is handled, and the follow-up response message that receives at described billing update packet directly abandons this response message.
4. the method for claim 1 is characterized in that, describedly the authentication request packet of preserving is sent to all is equipped with radius server and comprises:
Be equipped with the authentication request packet that radius server sends preset times to all.
5. the method for claim 1, it is characterized in that, described NAS with the authentication request packet of preserving send to all be equipped with after the radius server, when main radius server sends billing update packet, be equipped with radius server to all and further comprise before sending identical billing update packet:
NAS sends the beginning message that charges to main radius server, after receiving the charging response message that main radius server returns, according to default retransmission rules, is equipped with radius server to all and repeats to send to charge and begin message;
Perhaps further comprise: NAS is equipped with radius server to main radius server and all simultaneously and repeats to send the beginning message that charges according to default retransmission rules.
6. the method for claim 1 is characterized in that, as long as described NAS receives the response message that arbitrary radius server is responded, then allows the user to continue online further comprising afterwards:
Charging at described user finishes, and NAS is equipped with radius server to main radius server and all simultaneously and repeats to send accounting completion packet according to default retransmission rules.
7. NAS, it is characterized in that, corresponding at least two radius servers of this NAS, wherein one is main radius server, other is for being equipped with radius server, and the user on all radius servers disposes identical, and NAS for all radius servers are provided with same Identifier counter, this NAS comprises:
Authentication module, find that the user reaches the standard grade,, and preserve this authentication request packet to the authentication request packet of main radius server transmission at this user, when message is passed through in the authentication that receives main radius server, the authentication request packet of preserving is sent to all be equipped with radius server;
Accounting module, when main radius server sends billing update packet, be equipped with radius server to all and send identical billing update packet, Identifier field value in all billing update packets is identical, in default duration, as long as NAS receives the response message that arbitrary radius server is responded, then think and charge normally.
8. NAS as claimed in claim 7, it is characterized in that, described accounting module is further used for, be equipped with the identical billing update packet of radius server transmission to all after, if in the first default duration, do not receive main radius server, do not receive any response message that radius server returns that is equipped with yet, then according to default retransmission rules, repeat to send described billing update packet to all radius servers, if in default second duration, do not receive the response message that any radius server returns yet, then force users rolls off the production line.
9. as claim 7 or 8 described NAS, it is characterized in that, described accounting module is further used for, when chargeing beginning, send the beginning message that charges to main radius server, after receiving the charging response message that main radius server returns,, be equipped with radius server to all and repeat to send the beginning message that charges according to default retransmission rules;
Perhaps, when chargeing beginning,, be equipped with radius server to main radius server and all simultaneously and repeat to send the beginning message that charges according to default retransmission rules.
10. as claim 7 or 8 described NAS, it is characterized in that described accounting module is further used for, when chargeing end,, be equipped with radius server to main radius server and all simultaneously and repeat to send accounting completion packet according to default retransmission rules.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010109558.5A CN102148688B (en) | 2010-02-09 | 2010-02-09 | Charging method and NAS (Network Access Server) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010109558.5A CN102148688B (en) | 2010-02-09 | 2010-02-09 | Charging method and NAS (Network Access Server) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102148688A true CN102148688A (en) | 2011-08-10 |
| CN102148688B CN102148688B (en) | 2014-02-26 |
Family
ID=44422710
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010109558.5A Active CN102148688B (en) | 2010-02-09 | 2010-02-09 | Charging method and NAS (Network Access Server) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102148688B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103532687A (en) * | 2013-10-18 | 2014-01-22 | 上海斐讯数据通信技术有限公司 | Method and system for realizing redundant backup of dynamic host configuration protocol server |
| CN103763144A (en) * | 2014-01-26 | 2014-04-30 | 杭州华三通信技术有限公司 | Method and device of user for carrying out renewal to go online |
| CN105591762A (en) * | 2015-07-29 | 2016-05-18 | 杭州华三通信技术有限公司 | User charging method and device |
| CN106603251A (en) * | 2017-02-21 | 2017-04-26 | 上海斐讯数据通信技术有限公司 | Charging update message sending method and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1299203C (en) * | 2004-09-14 | 2007-02-07 | 中国人民解放军上海警备区司令部指挥自动化工作站 | Data disaster tocerance backup control system |
| CN100518112C (en) * | 2005-10-27 | 2009-07-22 | 华为技术有限公司 | User access method and apparatus based on multiple users |
| CN101141260A (en) * | 2007-10-22 | 2008-03-12 | 中兴通讯股份有限公司 | Method and device for performing passway detection to remote subscriber dialing authentication system server |
-
2010
- 2010-02-09 CN CN201010109558.5A patent/CN102148688B/en active Active
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103532687A (en) * | 2013-10-18 | 2014-01-22 | 上海斐讯数据通信技术有限公司 | Method and system for realizing redundant backup of dynamic host configuration protocol server |
| CN103763144A (en) * | 2014-01-26 | 2014-04-30 | 杭州华三通信技术有限公司 | Method and device of user for carrying out renewal to go online |
| CN103763144B (en) * | 2014-01-26 | 2017-04-05 | 杭州华三通信技术有限公司 | A kind of user continues to pay dues the method and apparatus reached the standard grade |
| CN105591762A (en) * | 2015-07-29 | 2016-05-18 | 杭州华三通信技术有限公司 | User charging method and device |
| CN105591762B (en) * | 2015-07-29 | 2019-01-08 | 新华三技术有限公司 | The method and apparatus of user's charging |
| CN106603251A (en) * | 2017-02-21 | 2017-04-26 | 上海斐讯数据通信技术有限公司 | Charging update message sending method and system |
| CN106603251B (en) * | 2017-02-21 | 2020-03-24 | 上海斐讯数据通信技术有限公司 | Method and system for sending charging update message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102148688B (en) | 2014-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11218459B2 (en) | Reoccuring keying system | |
| CN102664871B (en) | A kind of processing method of intelligent terminal address list | |
| CN103037312B (en) | Information push method and device | |
| CN101317359B (en) | Method and device for generating local interface cryptographic key | |
| CN110958111B (en) | Block chain-based identity authentication mechanism of electric power mobile terminal | |
| US11880450B2 (en) | Method and apparatus for updating password of electronic device, device and storage medium | |
| CN108880794A (en) | Across chain user identity and its digital asset management system | |
| CN101039310B (en) | Link sharing service apparatus and communication method thereof | |
| CN100471135C (en) | Device, system and method for realizing business distribution and synchronization | |
| RU2013143020A (en) | COMMUNICATION SYSTEM, DATABASE, CONTROL DEVICE, COMMUNICATION METHOD AND PROGRAM | |
| CN112333214B (en) | Safe user authentication method and system for Internet of things equipment management | |
| CN109729000B (en) | Instant messaging method and device | |
| CN103747051A (en) | Service platform of vehicle-mounted terminal | |
| CN102148688A (en) | Charging method and NAS (Network Access Server) | |
| CN101730085A (en) | Address book data synchronizing method and system | |
| CN113515075A (en) | Intelligent control system and method through low-power-consumption long-distance radio frequency wireless network | |
| CN104995864A (en) | Systems, methods, and computer program products for providing a universal persistence cloud service | |
| CN102137102A (en) | Realizing method of service supporting platform for supporting multiclass information publishing modes | |
| KR20150053422A (en) | Certification telephone number management server and method for managing certification telephone number, and electronic business server and method for certificating electronic business | |
| CN102665215A (en) | Light safety authentication method and system thereof of intelligent mobile phone based on SNS (social network service) | |
| CN106162645B (en) | A kind of the quick of Mobile solution reconnects method for authenticating and system | |
| CN114036576A (en) | Method and device for recovering ipsec tunnel and readable storage medium | |
| CN114338762A (en) | Same city data open system, method, electronic equipment and storage medium | |
| CN101924636A (en) | Relevant authentication information issuing method, device and network equipment | |
| KR101308628B1 (en) | Server and method for transferring mms contents during call from soip device |
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 | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CP03 | Change of name, title or address |