Method for safety communication between devices

Abstract

The invention relates to a method for realizing safe communication between devices, wherein it comprises: first, the communicated two devices process identification encrypted parameter consultation and the exchange, to complete the consultation, exchange and synchronization of parameters as message identification random number, to make them obtain the consistent message identification encrypted parameters, while said parameters comprises the random number and the maximum serial number; then one terminal should load said message identification information in the message sent to opposite one; said message comprises the message identification encrypted parameter and the generated identification information; and the opposite one should first identify the message after receiving the message, then treat the message; if the identification is not passes, throw said message. The invention can improve the safety, without adding condition machine on each message.

Description

technical field [0001] The invention relates to the technical field of NGN communication security, in particular to a method for secure communication between devices. Background technique [0002] With the extensive use of IP technology in the field of telecommunications, the security and reliability of the IP network itself has gradually become a key issue that needs to be solved urgently for the commercial use of this technology in the telecommunications network with high security requirements. [0003] Due to the openness of the IP network, anyone who can access the IP network can intercept and analyze the communication data transmitted in the IP network, or send messages in any format to any device in the network at any time. Since the IP packet itself does not have any security features, the address of the IP packet can be easily counterfeited. Refer to the accompanying drawings for a detailed description of the counterfeiting of messages and their hazards: [0004] S...

AI Technical Summary

Problems solved by technology

[0013] It can be seen from the above that the HTTP DIGEST authentication technology guarantees the certainty of the identity of both parties sending the message. However, this technical solution usually only authenticates out-of-call request messages such as INVITE, while for in-call request messages (such as CANCEL, BYE, etc.) ) does not authenticate

Therefore, it can only solve the problem of counterfeiting outbound request messages such as INVITE, but cannot solve the problem of counterfeiting other messages and the problem of message replay

[0014] If HTTP DIGEST is used for authentication for each request message, the message flow will become very complicated

This is because each device already has a call state machine, which is relatively complicated. If you want to use the HTTP DIGEST method to authenticate all request messages, such as the authentication of CANCEL, ACK, and UPDATE call messages, you need Adding a state machine to each message to activate authentication and generate authentication parameters will obviously make the implementation extremely complicated, so it is impossible to use the existing method to guarantee the security of the response message

Images