CN102739657A - Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server - Google Patents
Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server Download PDFInfo
- Publication number
- CN102739657A CN102739657A CN2012101992147A CN201210199214A CN102739657A CN 102739657 A CN102739657 A CN 102739657A CN 2012101992147 A CN2012101992147 A CN 2012101992147A CN 201210199214 A CN201210199214 A CN 201210199214A CN 102739657 A CN102739657 A CN 102739657A
- Authority
- CN
- China
- Prior art keywords
- tacacs
- enable
- server
- enable authentication
- client
- 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.)
- Pending
Links
Images
Abstract
The invention discloses an enable authentication method and an enable authentication method for a butt TACACS (Terminal Access Controller Access Control System) + a server. The method comprises the following steps that in an IP (Internet protocol) network, the TACACS+ client side sends an enable authentication request message which contains an enable authentication type to the TACACS+ server to request the TACACS+ server to authenticate; after receiving the enable authentication request message, the TACACS+ server extracts the enable authentication type from the enable authentication request message, generates an enable authentication response message responding to the enable authentication request message according to the enable authentication type, and sends the enable authentication response message to the TACACS+ client side; the TACACS+ client side judges whether the enable authentication on the butt TACACS+ server is successful or not according to the enable authentication response message; and when the authentication is not successful, the TACACS+ client side modifies the enable authentication type in the enable authentication request message, and the steps are repeated until the enable authentication on the butt TACACS+ server is successful.
Description
Technical field
The present invention relates to the communications field, particularly a kind of treatment technology of TACACS+enable authentication different authentication type.
Background technology
TACACS+ (Terminal Access Controller Access Control System) is a terminal access controller access control system, is the network application agreement of a kind of AAA (Authentication, Authorization, Accounting) type.TACACS+ supports independently authentication function, allows different TACACS+ security servers respectively as authentication, authorization and accounting server, is used for functions such as authentication.
This agreement has realized the Long-distance Control for user's access.The enable authentication is that the user adopts the TACACS+ server authentication when carrying out the enable authentication.The TACACS+draft regulation, for the enable authentication, the authen_type of its message (auth type) does not use (not used).
The TACACS+ server is many at present, and different TACACS+ servers is handled also different to the auth type field of enable authentication request packet, and all adopt the different TACACS+ server of enable authentication butt joint can dock unsuccessful.Because TACACS+draft does not clearly stipulate the enable auth type occurrence of enable authentication request packet, therefore, how to guarantee that the different TACACS+ server of enable authentication success butt joint becomes problem demanding prompt solution.
Summary of the invention
The object of the present invention is to provide a kind of enable authentication method and system of the TACACS+ of butt joint server, can solve the problem that different TACACS+ server failures are docked in the enable authentication better.
According to an aspect of the present invention, a kind of enable authentication method of the TACACS+ of butt joint server is provided, has comprised:
In IP network, the TACACS+ client is sent the enable authentication request packet that comprises the enable auth type to the TACACS+ server, and request TACACS+ server carries out authentication;
After the TACACS+ server is received said enable authentication request packet; Extract enable auth type wherein; And according to said enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to said TACACS+ client;
The TACACS+ client judges according to said enable authentication response message whether enable authentication butt joint TACACS+ server is successful;
When judged result is when success, the TACACS+ client is revised the enable auth type in the enable authentication request packet, and repeats above step, until the success of enable authentication butt joint TACACS+ server.
Preferably, said TACACS+ client is carried out Timing Processing after sending the enable authentication request packet, wait for that said TACACS+ server responds said enable authentication request packet in the given time.
Preferably, in the scheduled time after said TACACS+ client is being sent the enable authentication request packet, when not receiving the enable authentication response message of said TACACS+ server response, confirm the not success of enable authentication butt joint TACACS+ server.
Preferably; In the scheduled time after said TACACS+ client is being sent the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response; Resolve said enable authentication response message, and utilize analysis result to confirm whether enable authentication butt joint TACACS+ server is successful.
Preferably, said enable auth type comprises none, ascii, pap, chap, arap, mschap.
According to a further aspect in the invention, a kind of enable Verification System of the TACACS+ of butt joint server is provided, has comprised the TACACS+ client and the TACACS+ server that operate on the IP network, it is characterized in that,
Said TACACS+ client; Be used for sending the enable authentication request packet that comprises the enable auth type to the TACACS+ server; Request TACACS+ server carries out the enable authentication, and according to the enable authentication response message of receiving, judges whether enable authentication butt joint TACACS+ server is successful; When judged result is when success; Revise the enable auth type in the enable authentication request packet, and repeat the enable authentication, until the success of enable authentication butt joint TACACS+ server;
Said TACACS+ server; Be used for after receiving said enable authentication request packet; Extract enable auth type wherein; And according to said enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to said TACACS+ client.
Preferably, said TACACS+ client comprises:
Client packet sending and receiving unit is used to send the enable authentication request packet that comprises the enable auth type, and receives the said enable authentication response message of said TACACS+ server response;
The client timing unit is used for after said packet sending and receiving unit sends said enable authentication request packet, carrying out Timing Processing, waits for that said TACACS+ server responds said enable authentication request packet in the given time;
The client resolution unit is used to resolve the said enable authentication response message of receiving;
The client certificate judging unit is used for according to said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.
Preferably; In the scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When not receiving the enable authentication response message of said TACACS+ server response, said client certificate judging unit is confirmed the not success of enable authentication butt joint TACACS+ server.
Preferably; In the scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response; Said client certificate judging unit utilizes said client resolution unit to resolve the analysis result of said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.
Preferably, said TACACS+ server comprises:
Server packet sending and receiving unit; Be used to receive said enable authentication request packet, and send the enable authentication response message that is used to respond said enable authentication request packet to said TACACS+ client from comprising of TACACS+ client of said enable auth type;
The server parses unit is used to resolve the said enable authentication request packet that said server packet sending and receiving unit is received, extracts enable auth type wherein;
The server authentication unit is used for according to said enable auth type, generates said enable authentication response message.
Compared with prior art, beneficial effect of the present invention is:
When the present invention adopts enable authentication butt joint TACACS+ server failure; Can attempt revising the field of the enable auth type of enable authentication request packet; And dock the TACACS+ server again; Be revised as the enable auth type that corresponding TACACS+ server is supported up to this field, realized that the enable authentication success docks different TACACS+ servers.
Description of drawings
Fig. 1 is the enable authentication method block diagram of the butt joint TACACS+ server that provides of the embodiment of the invention;
Fig. 2 is the enable Verification System network topological diagram of the butt joint TACACS+ server that provides of the embodiment of the invention;
Fig. 3 is the particular flow sheet of the enable authentication different authentication type of process that provides of the embodiment of the invention.
Embodiment
, should be appreciated that following illustrated preferred embodiment only is used for explanation and explains the present invention, and be not used in qualification the present invention a preferred embodiment of the present invention will be described in detail below in conjunction with accompanying drawing.
Fig. 1 is the enable authentication method block diagram of the butt joint TACACS+ server that provides of the embodiment of the invention, and is as shown in Figure 1, comprising:
Step S101, in IP network, the TACACS+ client is sent the enable authentication request packet comprise the enable auth type to the TACACS+ server, request TACACS+ server carries out authentication.
Further, said TACACS+ client is carried out Timing Processing after sending the enable authentication request packet, wait for that said TACACS+ server responds said enable authentication request packet in the given time.
After step S102, TACACS+ server are received said enable authentication request packet; Extract enable auth type wherein; And according to said enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to said TACACS+ client.
Step S103, TACACS+ client judge according to said enable authentication response message whether enable authentication butt joint TACACS+ server is successful.
Step S104, when judged result is when success, the TACACS+ client is revised the enable auth type in the enable authentication request packet, and repeats above step, until the success of enable authentication butt joint TACACS+ server.
Further, in the scheduled time after said TACACS+ client is being sent the enable authentication request packet, when not receiving the enable authentication response message of said TACACS+ server response, confirm the not success of enable authentication butt joint TACACS+ server.
Further; In the scheduled time after said TACACS+ client is being sent the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response; Resolve said enable authentication response message, and utilize analysis result to confirm whether enable authentication butt joint TACACS+ server is successful.
Above-mentioned enable auth type comprises none, ascii, pap, chap, arap, mschap.
When adopting enable authentication butt joint TACACS+ server; The enable auth type adopts the default value of using earlier; If butt joint TACACS+ server failure; Then attempt revising the corresponding field value (none, ascii, pap, chap, arap, mschap) of enable auth type except that default value, the new enable of the initiation authentication of laying equal stress on is up to successfully docking the TACACS+ server.
Fig. 2 is the enable Verification System network topological diagram of the butt joint TACACS+ server that provides of the embodiment of the invention, and is as shown in Figure 2, comprises the TACACS+ client and the TACACS+ server that operate on the IP network.When the user carried out the enable authentication, the TACACS+ client was sent the enable authentication request packet to the TACACS+ server, and waits for that said TACACS+ server responds said enable authentication request packet.Wherein:
Said TACACS+ client; Be used for sending the enable authentication request packet that comprises the enable auth type to the TACACS+ server; Request TACACS+ server carries out the enable authentication, and according to the enable authentication response message of receiving, judges whether enable authentication butt joint TACACS+ server is successful; When judged result is when success; Revise the enable auth type in the enable authentication request packet, and repeat the enable authentication, until the success of enable authentication butt joint TACACS+ server.
Particularly, said TACACS+ client comprises:
Client packet sending and receiving unit is used to send the enable authentication request packet that comprises the enable auth type, and receives the said enable authentication response message of said TACACS+ server response;
The client timing unit is used for after said packet sending and receiving unit sends said enable authentication request packet, carrying out Timing Processing, waits for that said TACACS+ server responds said enable authentication request packet in the given time;
The client resolution unit is used to resolve the said enable authentication response message of receiving;
The client certificate judging unit is used for according to said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.In the i.e. scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When not receiving the enable authentication response message of said TACACS+ server response, said client certificate judging unit is confirmed the not success of enable authentication butt joint TACACS+ server.In the scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response; Said client certificate judging unit utilizes said client resolution unit to resolve the analysis result of said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.
Said TACACS+ server; Be used for after receiving said enable authentication request packet; Extract enable auth type wherein; And according to the enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to said TACACS+ client.
Particularly, said TACACS+ server comprises:
Server packet sending and receiving unit; Be used to receive said enable authentication request packet, and send the enable authentication response message that is used to respond said enable authentication request packet to said TACACS+ client from comprising of TACACS+ client of said enable auth type;
The server parses unit is used to resolve the said enable authentication request packet that said server packet sending and receiving unit is received, extracts enable auth type wherein;
The server authentication unit is used for according to said enable auth type, generates said enable authentication response message.
The workflow of the enable Verification System of said butt joint TACACS+ server specifies as follows:
1, at first adopt the authentication of TACACS+enable mode, the TACACS+ client is initiated authentication request through sending the enable authentication request packet to the TACACS+ server, writes down the default value of the enable auth type in the said enable authentication request packet.
2, the TACACS+ server judges whether the numerical value that the corresponding field of enable authentication request packet is filled in meets TACACS+ draft (The TACACS+ Protocol Version 1.78) regulation, thereby judgement enable authentication success is still failed.Draft specifies enable authentication request packet is filled in following field:
action=TAC_PLUS_AUTHEN_LOGIN
priv_lvl=implementation?dependent
authen_type=not?used
service=TAC_PLUS_AUTHEN_SVC_ENABLE
Because TACACS+ is a draft, does not form RFC, different TACACS+ servers are not quite similar to the fill request of authen_type field.
When the numerical value of filling in when the corresponding authen_type field of enable authentication request packet meets the fill request of TACACS+ server; The TACACS+ server sends to the TACACS+ client and is used to represent to dock successful enable authentication response message, otherwise is used to represent to dock the enable authentication response message of failure to the transmission of TACACS+ client.
3, the TACACS+ client receives said enable authentication response message and resolves, when judging the success of enable authentication butt joint TACACS+ server, and process ends.For example; The status value of the said enable authentication response message that the TACACS+ client is received is not TAC_PLUS_AUTHEN_STATUS_ERROR (0x07); Then enable authentication butt joint TACACS+ server success, promptly said TACACS+ client uses the TACACS+ server end to carry out the enable authentication success.
When 4, the TACACS+ client confirms that enable authentication butt joint TACACS+ server is unsuccessful; Revising the enable auth type is next enable auth type; And be not the default value used and all enable auth types when not attempting not finishing at the enable auth type of judging current enable authentication request packet, continue to initiate authentication request until the success of enable authentication butt joint TACACS+ server to the TACACS+ server.
The situation that the situation of said butt joint failure, promptly said TACACS+ client use the TACACS+ server to carry out enable authentication butt joint TACACS+ server failure comprises:
(1) the TACACS+ client receives that the status value of the enable authentication response message that the TACACS+ server returns is TAC_PLUS_AUTHEN_STATUS_ERROR (0x07).
(2) the TACACS+ client is connected under the normal condition with network, can not receive the said enable authentication response message of TACACS+ server response in the scheduled time after sending the enable authentication request packet.
Fig. 3 is the idiographic flow that the embodiment of the invention provides enable authentication different authentication type of process, and is as shown in Figure 3, comprising:
Step S301, at first adopt the TACACS+enable authentication mode, auth type adopts the default value of using (such as none), notes this default value.
Step S302, TACACS+ client are initiated authentication through send the enable authentication request packet that comprises the enable auth type to the TACACS+ server.
If step S303 TACACS+ client is confirmed the success of enable authentication butt joint TACACS+ server, process ends then, otherwise, execution in step S304.
If step S304 TACACS+ client is confirmed enable authentication butt joint TACACS+ server failure, then this enable auth type is revised as down a kind of enable auth type.
Step S305, TACACS+ client judge whether the enable auth type of said enable authentication request packet is the default value of using; If default value, execution in step S304 then remodifies the enable auth type of enable authentication request packet; Otherwise, execution in step S306.
Step S306, TACACS+ client judge whether all enable auth types of enable authentication request packet were all attempted, if, process ends then, otherwise execution in step S302.
In sum, the present invention has following technique effect:
The present invention has overcome the defective that the enable auth type of enable authentication request packet can not be revised, and has realized revising through self adaptation the enable auth type of enable authentication request packet, the function of successfully docking different TACACS+ servers.
Although preceding text specify the present invention, the invention is not restricted to this, those skilled in the art of the present technique can carry out various modifications according to principle of the present invention.Therefore, all modifications of doing according to the principle of the invention all are to be understood that to falling into protection scope of the present invention.
Claims (10)
- One kind dock terminal access controller access control system TACACS+ server enable the enable authentication method, it is characterized in that, comprising:In IP network, the TACACS+ client is sent the enable authentication request packet that comprises the enable auth type to the TACACS+ server, and request TACACS+ server carries out authentication;After the TACACS+ server is received said enable authentication request packet; Extract enable auth type wherein; And according to said enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to the TACACS+ client;The TACACS+ client judges according to said enable authentication response message whether enable authentication butt joint TACACS+ server is successful;When judged result is when success, the TACACS+ client is revised the enable auth type in the enable authentication request packet, and repeats above step, until the success of enable authentication butt joint TACACS+ server.
- 2. method according to claim 1 is characterized in that, said TACACS+ client is carried out Timing Processing after sending the enable authentication request packet, wait for that said TACACS+ server responds said enable authentication request packet in the given time.
- 3. method according to claim 2; It is characterized in that; In the scheduled time after said TACACS+ client is being sent the enable authentication request packet; When not receiving the enable authentication response message of said TACACS+ server response, confirm the not success of enable authentication butt joint TACACS+ server.
- 4. method according to claim 2; It is characterized in that; In the scheduled time after said TACACS+ client is being sent the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response, resolve said enable authentication response message, and utilize analysis result to confirm whether enable authentication butt joint TACACS+ server is successful.
- 5. according to any described method of claim 1-4, it is characterized in that said enable auth type comprises none, ascii, pap, chap, arap, mschap.
- One kind dock terminal access controller access control system TACACS+ server enable the enable Verification System, comprise the TACACS+ client and the TACACS+ server that operate on the IP network, it is characterized in that,Said TACACS+ client is used for sending the enable authentication request packet that comprises the enable auth type to the TACACS+ server, and request TACACS+ server carries out authentication; And according to the enable authentication response message of receiving; Judge the whether success of enable authentication butt joint TACACS+ server, when judged result during for success, the enable auth type in the modification enable authentication request packet; And repeat the enable authentication, until the success of enable authentication butt joint TACACS+ server;Said TACACS+ server; Be used for after receiving said enable authentication request packet; Extract enable auth type wherein; And according to said enable auth type, generation is used to respond the enable authentication response message of said enable authentication request packet and is sent to said TACACS+ client.
- 7. system according to claim 6 is characterized in that, said TACACS+ client comprises:Client packet sending and receiving unit is used to send the enable authentication request packet that comprises the enable auth type, and receives the said enable authentication response message of said TACACS+ server response;The client timing unit is used for after said packet sending and receiving unit sends said enable authentication request packet, carrying out Timing Processing, waits for that said TACACS+ server responds said enable authentication request packet in the given time;The client resolution unit is used to resolve the said enable authentication response message of receiving;The client certificate judging unit is used for according to said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.
- 8. system according to claim 7; It is characterized in that; In the scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When not receiving the enable authentication response message of said TACACS+ server response, said client certificate judging unit is confirmed the not success of enable authentication butt joint TACACS+ server.
- 9. system according to claim 7; It is characterized in that; In the scheduled time after said client packet sending and receiving unit is sending the enable authentication request packet; When receiving the enable authentication response message of said TACACS+ server response, said client certificate judging unit utilizes said client resolution unit to resolve the analysis result of said enable authentication response message, confirms whether enable authentication butt joint TACACS+ server is successful.
- 10. according to Claim 8 or 9 described systems, it is characterized in that said TACACS+ server comprises:Server packet sending and receiving unit; Be used to receive said enable authentication request packet, and send the enable authentication response message that is used to respond said enable authentication request packet to said TACACS+ client from comprising of TACACS+ client of said enable auth type;The server parses unit is used to resolve the said enable authentication request packet that said server packet sending and receiving unit is received, extracts enable auth type wherein;The server authentication unit is used for according to said enable auth type, generates said enable authentication response message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101992147A CN102739657A (en) | 2012-06-15 | 2012-06-15 | Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101992147A CN102739657A (en) | 2012-06-15 | 2012-06-15 | Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102739657A true CN102739657A (en) | 2012-10-17 |
Family
ID=46994441
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012101992147A Pending CN102739657A (en) | 2012-06-15 | 2012-06-15 | Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102739657A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017076363A1 (en) * | 2015-11-06 | 2017-05-11 | Mediatek Inc. | Method for efficient reliable transmission |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6466964B1 (en) * | 1999-06-15 | 2002-10-15 | Cisco Technology, Inc. | Methods and apparatus for providing mobility of a node that does not support mobility |
| CN1753359A (en) * | 2004-09-24 | 2006-03-29 | 华为技术有限公司 | Method of implementing transmission syncML synchronous data |
| CN1859415A (en) * | 2006-04-04 | 2006-11-08 | 华为技术有限公司 | Method and device for forced verifying from end-to-end protocol |
| CN101083528A (en) * | 2007-06-08 | 2007-12-05 | 中兴通讯股份有限公司南京分公司 | Dynamic host configuring protocol based security access method and system |
| CN101742497A (en) * | 2009-12-24 | 2010-06-16 | 中兴通讯股份有限公司 | Method for realizing access authentication and client |
-
2012
- 2012-06-15 CN CN2012101992147A patent/CN102739657A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6466964B1 (en) * | 1999-06-15 | 2002-10-15 | Cisco Technology, Inc. | Methods and apparatus for providing mobility of a node that does not support mobility |
| CN1753359A (en) * | 2004-09-24 | 2006-03-29 | 华为技术有限公司 | Method of implementing transmission syncML synchronous data |
| CN1859415A (en) * | 2006-04-04 | 2006-11-08 | 华为技术有限公司 | Method and device for forced verifying from end-to-end protocol |
| CN101083528A (en) * | 2007-06-08 | 2007-12-05 | 中兴通讯股份有限公司南京分公司 | Dynamic host configuring protocol based security access method and system |
| CN101742497A (en) * | 2009-12-24 | 2010-06-16 | 中兴通讯股份有限公司 | Method for realizing access authentication and client |
Non-Patent Citations (1)
| Title |
|---|
| D. CARREL ET AL.: "《The TACACS+ Protocol Version 1.78》", 《IETF》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017076363A1 (en) * | 2015-11-06 | 2017-05-11 | Mediatek Inc. | Method for efficient reliable transmission |
| US10142253B2 (en) | 2015-11-06 | 2018-11-27 | Hfi Innovation Inc. | Method for efficient reliable transmission |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3068093B1 (en) | Security authentication method and bidirectional forwarding detection method | |
| CN102638468B (en) | The method of protection information transmission security, transmitting terminal, receiving terminal and system | |
| WO2016192282A1 (en) | Link detection method and device | |
| CN105407008A (en) | Reconnecting method and system for interrupted TCP (Transmission Control Protocol) connection, terminal and server | |
| CN103825881A (en) | Method and apparatus for realizing redirection of WLAN user based on wireless access controller (AC) | |
| CN103825777A (en) | DMZ server switching method and device | |
| CN103685398B (en) | Communication connection method for building up and communication system | |
| CN104821940A (en) | Method and equipment for sending portal redirected address | |
| CN103199990B (en) | A kind of method and apparatus of Routing Protocol certification migration | |
| CN111404918A (en) | Cloud mobile phone distributed service emergency authentication method, device and system | |
| CN104009961A (en) | PPPoE session ID distribution method and equipment thereof | |
| CN102739657A (en) | Enable authentication method and method for butt TACACS (Terminal Access Controller Access Control System) + server | |
| CN106331074B (en) | A kind of certification switching method | |
| CN104735050A (en) | Authentication method integrating mac authentication and web authentication | |
| CN102195943B (en) | Safety information interaction method and system | |
| EP3313039A1 (en) | Home gateway, communication management method and communication system thereof | |
| CN106330971A (en) | Authentication method, server and system based on stateless service | |
| US20130227157A1 (en) | Terminal apparatus, operation method of terminal apparatus, and program product | |
| CN101316165B (en) | Method and server for implementing communication between application system and communication network | |
| JP3990412B2 (en) | Wireless LAN authentication system compatible with WakeOnLAN | |
| CN108270613B (en) | Message sending method and network equipment | |
| CN106332078B (en) | dot1x user authentication system, method and device | |
| US20120222088A1 (en) | Method and Apparatus for Implementing Communication of Stand-Alone Software | |
| CN105045759B (en) | Control communication method of financial self-service equipment | |
| CN102065072B (en) | Method and device for fast establishing PPPOE (Point-to-Point Protocol over Ethernet) link layer connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121017 |