Abstract:
The present invention discloses a authentication method for network security, comprising: firstly, a media gateway controller (MGC) configures a media gateway (MG) with an authentication key and sets a security data package on a network protocol; thus, during the security authentication, the MGC utilizes the security data package to send security authentication request data to the MG; the MG performs an encryption calculation on the request data with the authentication key, and respond to MGC with the encrypted request data; the MGC determines whether the MG being authenticated is legal according to the authenticated result. Said method can prevent illegal or forged devices from accessing to a network; in addition, because that the authentication of MG is performed under the control of MGC, the method is featured with authentication randomness and thereby has higher security authentication efficiency.

Description:
FIELD OF THE INVENTION  
       [0001]     The present invention relates to an authentication method for network security.  
       BACKGROUND OF THE INVENTION  
       [0002]     In the Next Generation Network (NGN), there are many Media Gateways (MGs) based on Media Gateway Control Protocol (MGCP) or H248 protocol (another Media Gateway Control Protocol, i.e., MeGaCo); these numerous MGs are distributed in enterprises or residences widely, and are featured with covering a wide range, having a great quantity, and being based on dynamic IPs. However, because there being no security authentication mechanism on the application layer of MGCP protocol in the current NGN, the MGs using MGCP protocol are poor in security; though H248 protocol has security authentication mechanism on the application layer, i.e., a security header can be added into each transaction request message of H248 protocol, and the security authentication result can be returned in the transaction response message, but the security authentication mechanism requires exchanging a large amount of H248 messages between MGC and MG, resulting in increasing about 40% time for processing of encoding and decoding H248 messages; thus a security authentication solution provided by conventional H248 protocol severely degrades efficiency of the network system and its feasibility in actual application is poor. Therefore, the problems of system security in the NGN, such as forging MG or attacking to MGC are yet not solved.  
       SUMMARY OF THE INVENTION  
       [0003]     An object of the present invention is to provide an effective authentication method for the NGN security.  
         [0004]     To attain said object, the authentication method for network security according to the present invention comprises:  
         [0005]     step 1: a Media Gateway Controller (MGC) configuring a Media Gateway (MG) with an authentication key, and setting a security data package on a network protocol;  
         [0006]     step 2: the MGC, during the security authentication, sending security authentication request data to the MG using the data package; the MG performing an encryption calculation on the request data using the authentication key, and responding to MGC with the encrypted request data;  
         [0007]     step 3: the MGC determining whether the MG being authenticated is legal according to the authentication result.  
         [0008]     Said network protocol is Media Gateway Control Protocol (MGCP) or H248 protocol.  
         [0009]     Said data package comprises: a security authentication request signal and a security authentication completion event; said security authentication request signal comprises a security authentication parameter; said security authentication completion event comprises a security authentication result parameter.  
         [0010]     Said step 2 further comprises:  
         [0011]     step 21: the MGC sending the security authentication request signal in the data package to the MG;  
         [0012]     step 22: the MG, after receiving the security authentication parameter in the security authentication request signal, performing encryption calculation on said parameter using the authentication key, and reporting the encryption calculated result to the MGC through the security authentication result parameter in the security authentication completion event in the data package.  
         [0013]     Since the present invention uses a MGC to configure a MG with an authentication key and sets a network protocol security data package for security authentication of MG, it can prevent network access from illegal or forged devices; in addition, since the authentication of MG is performed under the control of MGC, (in other words, the authentication of MG is performed whenever the MGC considers authentication to be necessary), this kind of authentication has a characteristic of randomness and higher security authentication efficiency. 
     
    
     DETAILED DESCRIPTION OF THE EMBODIMENTS  
       [0014]     Hereunder the present invention will be further described in detail.  
         [0015]     The method according to the present invention is for implementing security management of MGs, which in substance comprising: configuring each MG with an authentication key; when initiating an authentication request, a MGC sends a random number to the MG; the MG, according to the random number sent from the MGC and the authentication key configured for the MG (of course, other information may also be included), performs an encryption calculation, and responds to the MGC with the encrypted result. The MGC performs the same calculation to determine whether the encrypted result is identical to that sent from the MG. If not, the MGC will consider the MG as illegal.  
         [0016]     The present invention may be implemented based on H248 protocol or MGCP protocol, thus a security data package on MGCP or H248 protocol needs to be added; said security data package is a collection of a security authentication signal and an event. The security authentication package on MGCP or H248 protocol employed by the present invention comprises a security authentication request signal and a security authentication completion event. Said security authentication request signal comprises a security authentication parameter. Said security authentication completion event comprises a security authentication result parameter. When the MGC is to perform security authentication of the MG, the MGC sends a security authentication request signal to the MG, and at the same time detects the security authentication completion event from the MG. When the MG receives the security authentication request signal sent from the MGC, it performs an encryption calculation in accordance with the authentication key configured thereon and the parameter in the security authentication request signal. Upon completion of the encryption calculation, the MG reports the security authentication completion event to the MGC, with the security encryption result included in the parameter of the security authentication completion event. When the MGC receives the security authentication completion event from the MG, it compares the encryption calculated result included in the parameter of the reported security authentication completion event with the encryption calculated result calculated by itself, determining whether they are identical or not. If not, the MGC will consider the MG as illegal.  
         [0017]     Hereunder the above procedures of the present invention are illustrated:  
         [0018]     The security data package on MGCP protocol implemented with MGCP protocol as described in the present invention comprises:  
         [0019]     Package identifier: Auth; version of data package: 1;  
         [0020]     Event included in the data package:  
         [0021]     1. Security authentication completion event  
         [0022]     Event Identifier: authoc;  
         [0023]     Event detection parameter identifier: 32*64 (a hexadecimal number);  
         [0024]     Note: the event detection parameter is used to return the authenticated result;  
         [0025]     Signal included in the data Package:  
         [0026]     1: Security authentication request signal  
         [0027]     Signal identifier: authreq;  
         [0028]     Signal parameter identifier: 32*64 (a hexadecimal number, 32 to 64 bits);  
         [0029]     The parameter in the security authentication request signal is a random number sent from the MGC to the MG. In this example, the random number is a string, which is longer than 16 bits and shorter than 32 bits. Each string is encoded into 2 hexadecimal numbers through ABNF (Augmented Backus-Naur Form) encoding.  
         [0030]     The authentication process based on above data package and the pseudo-codes used are:  
         [0031]     Step 11: the MGC initiates an authentication request to the MG: the MGC sends a Request Notification (RQNT) command to the MG and allocates Transaction Identifier (100) and Request Identifier (123), to request the MG to detect the security authentication completion event (auth/authoc); at the same time, it sends a security authentication request signal (auth/authreq), the MGC generates a 16-byte random number (0×78 0×90 0×ab 0×cd 0×ef 0×56 0×78 0×90 0×00 0×22 0×00 0×22 0×00 0×22 0×00 0×32) as the security authentication parameter of the security authentication request signal.  
         [0032]     Step 12: when receiving the Request Notification (RQNT) command sent from the MGC, the MG returns a correct response to this command (the response code being correct response (200) with the Transaction Identifier (100) identical to that in the Request Notification (RQNT) command sent from the MGC, to acknowledge the MG has received the Request Notification (RQNT) command from the MGC correctly.  
         [0033]     Step 13: When detecting a security authentication request signal after it receives the Request Notification (RQNT) command from the MGC, the MG begins to perform a security authentication calculation, i.e., performing an encryption calculation with the parameter taken out from the security authentication request signal and the authentication key configured thereon (the authentication key being assumed as 0×12 0×24 0×56 0×78 0×56 0×32 0×78 0×23 0×24 0×25 0×76 0×32 0×32 0×45 0×45 0×32). The result obtained through the encryption calculation is (0×12 0×34 0×ab 0×cd 0×ef 0×ab 0×ef 0×90 0×00 0×22 0×00 0×22 0×67 0×89 0×77 0×88), the MG generates a security authentication completion event and checks whether the MGC has requested to report the security authentication completion event; if detecting that the MGC has requested to report the event, the MG sends a Notify (NTFY) command to the MGC, with the detected event being the security authentication completion event (auth/authoc) and the parameter of the event being the encrypted result. The Request identifier (123) is identical to that in the Request Notification (RQNT) Command sent from the MGC, and the transaction identifier (200) is assigned.  
         [0034]     Step 14: when receiving the NTFY command from the MG, the MGC returns a correct response to this command, the response code being correct response (200), with the Transaction identifier (200) being identical to that in the Notify (NTFY) command reported from the MG, to acknowledge the MGC has received the Notify (NTFY) command from the MG correctly.  
         [0035]     Step 15: when receiving the encrypted result reported from the MG, the MGC compares the result with the encrypted result calculated by itself; if the two results are identical to each other, the MGC considers the MG as legal; if the two results are not identical to each other or the MG doesn&#39;t report the encrypted result within a predefined time, the MGC considers the MG as illegal.  
         [0036]     The security data package on H248 protocol implemented over H248 protocol according to the present invention comprises:  
         [0037]     Package identifier: auth; version of the data package: 1;  
         [0038]     Event in the data package:  
         [0039]     1: Security authentication completion event  
         [0040]     Event identifier: authoc (0×0001);  
         [0041]     Event detection parameter identifier: authenticated result;  
         [0042]     Parameter identifier: Res;  
         [0043]     ABNF code of the parameter value: 32*64 (a hexadecimal number, 32 to 64 bits);  
         [0044]     ASN.1 (abstract symbol notation) code of the parameter value: OCTET STRING (SIZE (16 . . . 32)); (octet of 16 to 32 bits)  
         [0045]     Signal included in the data package:  
         [0046]     1: Security authentication request signal  
         [0047]     Signal identifier: authreq  
         [0048]     Name of the signal parameter: request parameter;  
         [0049]     Parameter identifier: parm;  
         [0050]     ABNF code of the parameter value: 32*64 (a hexadecimal number);  
         [0051]     ASN.1 code of the parameter value: OCTET STRING (SIZE (16 . . . 32))  
         [0052]     The Authentication process based on above data package and the pseudo-codes used are:  
         [0053]     Step 21: the MGC initiates an authentication request to the MG: the MGC sends a Modify command to the MG and allocates a Transaction Identifier (100) and a Request Identifier (2223), to request the MG to detect the security authentication completion event (auth/authoc); at the same time, the MGC sends a security authentication request signal (auth/authreq), and generates a 16-byte random number (0×78 0×90 0×ab 0×cd 0×ef 0×56 0×78 0×90 0×00 0×22 0×00 0×22 0×00 0×22 0×00 0×32) as the security authentication parameter of the security authentication request signal.  
         [0054]     Step 22: when receiving the Modify command from the MGC, the MG returns a correct response to this command, with the Transaction Identifier (10001) identical to that in the Modify command, to acknowledge the MG has received the Modify command from the MGC correctly.  
         [0055]     Step 23: When detecting a security authentication request signal after receiving the Modify command from the MGC, the MG begins to perform a security authentication calculation, i.e., performing an encryption calculation with the parameter taken out from the security authentication request signal and the authentication key configured thereon (the authentication key being assumed as: 0×12 0×24 0×56 0×78 0×56 0×32 0×78 0×23 0×24 0×25 0×76 0×32 0×32 0×45 0×45 0×32). The result obtained through the encryption calculation is (0×12 0×34 0×ab 0×cd 0×ef 0×ab 0×ef 0×90 0×00 0×22 0×00 0×22 0×67 0×89 0×77 0×88). The MG generates a security authentication completion event and checks whether the MGC has requested to report the encryption completion event; if detecting the MGC has requested to report the event, the MG sends a Notify (NTFY) command to the MGC, with the detected event being the security authentication completion event (auth/authoc) and the event parameter being the encrypted result. The Request Identifier (2223) is identical to that in the Modify Command sent from the MGC, and the Transaction Identifier (10002) is assigned.  
         [0056]     Step 24: when receiving the Notify command from the MG, the MGC returns a correct response to this command, with the Transaction Identifier (10002) being identical to that in the Notify (NTFY) command sent from the MG, to acknowledge the MGC has received the Notify (NTFY) command from the MG correctly.  
         [0057]     Step 25: when receiving the encrypted result reported from the MG, the MGC compares the result with the encrypted result calculated by itself; if the two results are identical to each other, it considers the MG as legal; if the two results are not identical to each other or the MG doesn&#39;t report the encrypted result within a predefined time, it considers the MG as illegal.