Method and Apparatus for Detecting Man-In-The-Middle Attack
A system and method for detecting a man-in-the-middle attack, where the includes sending, by a secondary base station, a first check request message to a master base station, wherein the first check request message comprises first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information; receiving, by the master base station, the first check request message; obtaining second identifier information that matches the first identifier information, wherein the second identifier information is an identifier of a data radio bearer (DRB) corresponding to the ERAB; sending a second check request message to a user terminal, wherein the second check request message comprises the first data packet count value and the second identifier information; and receiving, by the master base station, a check response message from the user terminal.
This application is a continuation of U.S. patent application Ser. No. 15/270,722, filed on Sep. 20, 2016, which claims priority to International Patent Application No. PCT/CN2015/072300, filed on Feb. 5, 2015, which claims priority to Chinese Patent Application No. 201410106876.4, filed on Mar. 21, 2014. All of the aforementioned patent applications are hereby incorporated by reference in their entireties.
TECHNICAL FIELDThe present disclosure relates to the communications field, and in particular, to a method and an apparatus for detecting a man-in-the-middle attack.
BACKGROUNDAs informatization rapidly develops and network resources are increasingly rich, a service capability of a master Evolved NodeB (Master eNB, or MeNB for short) cannot meet a user requirement due to limited air interface bandwidth. In addition, expensive base station construction costs and high radio frequency also increase difficulty in base-station indoor coverage. Therefore, to improve a throughput of user plane data, a low-cost secondary eNodeB (Secondary eNB, or SeNB for short) is combined with the MeNB in networking, and the SeNB offloads partial traffic of the MeNB, which can resolve the foregoing problem. The master eNodeB is also referred to as a macro eNodeB (Macro eNB/cell), and the secondary eNodeB is also referred to as a small cell, which includes a pico cell/eNB and a femto cell/eNB. The small cell may be referred to as a pico base station or a femto base station.
A user terminal such as a User Equipment (UE) simultaneously maintains dual connectivity with the MeNB and the SeNB. The UE and the MeNB perform air-interface control plane signaling interworking with each other, and the UE simultaneously transmits user plane data to the MeNB and the SeNB. Because the user plane data between the UE and the SeNB is protected only by means of encryption processing, a man-in-the-middle (MITM) attack (MITM attack) may exist between the UE and the SeNB, and consequently there is a risk that the user plane data of interworking between the UE and the SeNB is inserted, tampered with, or forwarded, causing a user service to be fraudulently used and lawful interception to be unreliable, and the like.
In an existing communications network, after identifying a count value (e.g., a Packet Data Convergence Protocol (PDCP) count) of sent and received packets of a bearer between the UE and the eNB, the UE reports the count value to the eNB, such that the eNB detects whether a man-in-the-middle attack exists. A process is as follows. The eNB sends a counter check message to the UE, and adds multiple first PDCP count values corresponding to all bearers between the UE and the eNB to a counter check request message. The UE separately determines by comparison whether each first PDCP count value is the same as a stored second PDCP count value of each bearer. If the first PDCP count value of each of the bearers is the same as the second PDCP count value, the UE sends a check response message to the eNB. The check response message does not carry any PDCP count value. Alternatively, if the first PDCP count values of all the bearers are different from the second PDCP count value, the UE sends a check response message to the eNB, in which case the check response message carries different second PDCP count values. The eNB performs check processing on the check response message. If the check response message does not carry any PDCP count value, the detection procedure ends, and the eNB determines that no man-in-the-middle attack exists between the eNB and the UE. Alternatively, if the check response message carries the different second PDCP count values, the eNB determines that a man-in-the-middle attack exists between the eNB and the UE, such that the eNB sends a notification message to a mobility management entity (MME) or an operation and maintenance (O&M) server, and the MME or the O&M server performs subsequent processing and may release the bearer between the UE and the eNB.
It can be learned from the foregoing description that whether a man-in-the-middle attack exists between the UE and the eNB is detected by means of air-interface control plane signaling interworking, but in a scenario in which the UE maintains dual connectivity with the MeNB and the SeNB, no air-interface control plane signaling interworking occurs between the SeNB and the UE. Consequently, in this scenario, the SeNB cannot detect whether a man-in-the-middle attack exists between the SeNB and the UE.
SUMMARYEmbodiments of the present disclosure provide a method and an apparatus for detecting a man-in-the-middle attack, such that in a scenario in which UE maintains dual connectivity with an MeNB and an SeNB, it can be detected whether the SeNB and the UE are attacked by a man-in-the-middle.
In a first aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by a macro eNodeB (MeNB), a first check request message sent by a secondary eNodeB (SeNB), where the first check request message includes first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information; generating, by the MeNB, a second check request message according to the first identifier information; and sending the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is a data radio bearer (DRB) corresponding to the ERAB. The method further includes receiving, by the MeNB, a first check response message generated by the user terminal according to the second check request message, where the first check response message includes the second identifier information and the second data packet count value; and determining, by the MeNB when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal; or determining, by the MeNB when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal.
With reference to the first aspect, in a first possible implementation manner, the first check request message further includes an identifier of the SeNB. Additionally, generating, by the MeNB, a second check request message according to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to enable the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information includes generating, by the MeNB, the second check request message according to the first identifier information and the identifier of the SeNB, and sending the second check request message to the user terminal, such that the user terminal obtains, according to the second check request message, the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information.
With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the first check request message includes at least two pieces of first identifier information and at least two corresponding first data packet count values, and the first check response message includes at least two pieces of second identifier information and at least two corresponding second data packet count values. Additionally, determining, by the MeNB when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal includes determining, by the MeNB when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, determining, by the MeNB when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal includes determining, by the MeNB when the first data packet count values corresponding to all the first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal.
With reference to the first aspect or the first or the second possible implementation manner of the first aspect, in a third possible implementation manner, after the MeNB determines that no man-in-the-middle attack exists between the SeNB and the user terminal, the method further includes sending, by the MeNB, a second check response message to the SeNB, where the second check response message includes second indication information, and the second indication information is used to indicate that no man-in-the-middle attack exists between the SeNB and the UE.
With reference to the first aspect or the first, the second, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner, after the MeNB determines that a man-in-the-middle attack exists between the SeNB and the user terminal, the method further includes sending, by the MeNB, an exception report to a mobility management entity MME or an operation and maintenance O&M server.
With reference to the first aspect or the first, the second, the third, or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, after the MeNB determines that a man-in-the-middle attack exists between the SeNB and the user terminal, the method further includes sending, by the MeNB, a third check response message to the SeNB, where the third check response message includes third indication information, and the third indication information is used to indicate that a man-in-the-middle attack exists between the SeNB and the user terminal.
In a second aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes sending, by an SeNB, a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal; and receiving, by the SeNB, the check response message sent by the MeNB. Additionally, when the check response message is a second check response message and the second check response message includes second indication information, the method includes determining, by the SeNB according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, when the check response message is a third check response message and the third check response message includes third indication information, the method determining, by the SeNB according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the user terminal, and taking a preset measure for processing.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the first check request message further includes an identifier of the SeNB. Additionally, sending, by an SeNB, a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal includes sending, by the SeNB, the first check request message to the MeNB, where the first check request message includes the identifier of the SeNB, the first identifier information of the ERAB, and the first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate the second check request message according to the first identifier information and the identifier of the SeNB, and send the second check request message to the user terminal.
In a third aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by a user terminal, a second check request message sent by the MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and the second identifier information is a DRB corresponding to the ERAB; obtaining, by the user terminal, the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; and sending, by the user terminal, the second identifier information and the second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In a fourth aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by an MeNB, a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information; generating, by the MeNB, a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information; and sending the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB. The method further includes receiving, by the MeNB, a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, such that the SeNB performs processing according to the response message.
With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first check request message further includes an identifier of the SeNB. Additionally, generating, by the MeNB, a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information includes generating, by the MeNB, the second check request message according to the identifier of the SeNB, the first identifier information, and the first data packet count value corresponding to the first identifier information, and sending the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information.
With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, after receiving, by the MeNB, a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, such that the SeNB performs processing according to the response message, the method further includes, when the MeNB receives an exception report sent by the SeNB, sending, by the MeNB, the exception report to an MME or an O&M server.
In a fifth aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes sending, by an SeNB, a first check request message to an MeNB, where the first check request message includes first indication information, and the first indication information is used to instruct the MeNB to send a second check request message to a user terminal; receiving, by the SeNB, a check response message sent by the MeNB; and determining, by the SeNB according to the check response message, whether a man-in-the-middle attack exists. Additionally, when determining that the man-in-the-middle attack exists, the method includes taking, by the SeNB, a preset measure for processing and sending an exception report to the MeNB.
In a sixth aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by a user terminal, a second check request message sent by an MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and a first data packet count value corresponding to the first identifier information, and the second identifier information is a DRB corresponding to the ERAB; obtaining, by the user terminal, the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; determining, by the user terminal according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the user terminal; and generating, by the user terminal, a check response message according to a result of the determining, and sending the check response message to the MeNB.
With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, determining, by the user terminal according to the first data packet count value corresponding to the first identifier information and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the user terminal includes determining, by the user terminal when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, determining, by the user terminal according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists between an SeNB and the user terminal includes determining, by the user terminal when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal.
In a seventh aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by an MeNB, a first check request message sent by an SeNB; generating, by the MeNB, a second check request message according to the first check request message; and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information. The method further includes receiving, by the MeNB, a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, where the response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, the first check request message further includes an identifier of the SeNB. Additionally, generating, by the MeNB, a second check request message according to the first check request message, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information includes generating, by the MeNB, the second check request message according to the identifier of the SeNB and the first check request message, and sending the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the first identifier information of the DRB and the first data packet count value corresponding to the first identifier information.
With reference to the seventh aspect or the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, after the receiving, by the MeNB, a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, the method further includes, when the MeNB receives an exception report sent by the SeNB, sending, by the MeNB, the exception report to a mobility management entity MME or an operation and maintenance O&M server.
In an eighth aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes sending, by an SeNB, a first check request message to an MeNB, where the first check request message is used to enable the MeNB to generate a second check request message according to the first check request message, and send the second check request message to a user terminal; receiving, by the SeNB, a check response message sent by the MeNB, where the check response message includes first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; obtaining, by the SeNB according to the first identifier information, second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is an ERAB corresponding to the DRB; and determining, by the SeNB according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists. Additionally, when determining that the man-in-the-middle attack exists, the method includes taking, by the SeNB, a preset measure for processing and sending an exception report to the MeNB.
With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, determining, by the SeNB according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists includes determining, by the SeNB when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal; or determining, by the SeNB when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal.
In a ninth aspect, an embodiment of the present disclosure provides a method for detecting a man-in-the-middle attack. The method includes receiving, by a user terminal, a second check request message sent by an MeNB; obtaining, by the user terminal according to the second check request message, first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; and sending, by the user terminal, a check response message to the MeNB, where the check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to an SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the user terminal.
In a tenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information; and a sending unit configured to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB. The receiving unit is further configured to receive a first check response message generated by the user terminal according to the second check request message, where the first check response message includes the second identifier information and the second data packet count value. and the apparatus further includes a judging unit configured such that when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit determines that no man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit determines that a man-in-the-middle attack exists between the SeNB and the user terminal.
With reference to the tenth aspect, in a first implementation manner of the tenth aspect, the first check request message received by the receiving unit further includes an identifier of the SeNB. Additionally, the sending unit is further configured to generate the second check request message according to the first identifier information and the identifier of the SeNB, and send the second check request message to the user terminal, such that the user terminal obtains, according to the second check request message, the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information.
With reference to the tenth aspect or the first possible implementation manner of the tenth aspect, in a second possible implementation manner, the first check request message received by the receiving unit includes at least two pieces of first identifier information and at least two corresponding first data packet count values, and the first check response message received by the receiving unit includes at least two pieces of second identifier information and at least two corresponding second data packet count values. Additionally, the judging unit is configured such that when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the judging unit determines that a man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, the judging unit is configured such that when the first data packet count values corresponding to all the first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the judging unit determines that no man-in-the-middle attack exists between the SeNB and the user terminal.
With reference to the tenth aspect or the first or the second possible implementation manner of the tenth aspect, in a third possible implementation manner, the sending unit is further configured to send a second check response message to the SeNB, where the second check response message includes second indication information, and the second indication information is used to indicate that no man-in-the-middle attack exists between the SeNB and the UE.
With reference to the tenth aspect or the first or the second or the third possible implementation manner of the tenth aspect, in a fourth possible implementation manner, the sending unit is further configured to send an exception report to an MME or an O&M server.
With reference to the tenth aspect or the first or the second or the third or the fourth possible implementation manner of the tenth aspect, in a fifth possible implementation manner of the tenth aspect, the sending unit is further configured to send a third check response message to the SeNB, where the third check response message includes third indication information, and the third indication information is used to indicate that a man-in-the-middle attack exists between the SeNB and the user terminal.
In an eleventh aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a sending unit configured to send a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal. The apparatus further includes a receiving unit configured to receive the check response message sent by the MeNB, and a determining unit configured such that when the check response message is a second check response message and the second check response message includes second indication information, the determining unit determines, according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, when the check response message is a third check response message and the third check response message includes third indication information, the determining unit determines, according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the user terminal, and take a preset measure for processing.
With reference to the eleventh aspect, in a first possible implementation manner of the eleventh aspect, the first check request message sent by the sending unit further includes an identifier of the SeNB. Additionally, the sending unit is configured to send the first check request message to the MeNB, where the first check request message includes the identifier of the apparatus, the first identifier information of the ERAB, and the first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate the second check request message according to the first identifier information and the identifier of the apparatus, and send the second check request message to the user terminal.
In a twelfth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a second check request message sent by the MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and the second identifier information is a DRB corresponding to the ERAB; an obtaining unit configured to obtain the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; and a sending unit configured to send the second identifier information and the second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In a thirteenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information; and a sending unit configured to generate a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and send the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information. The sending unit is further configured to determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB. Additionally, the receiving unit is further configured to: receive a check response message generated by the user terminal according to the second check request message, and send the check response message to the SeNB, such that the SeNB performs processing according to the response message.
With reference to the thirteenth aspect, in a first possible implementation manner of the thirteenth aspect, the first check request message received by the receiving unit further includes an identifier of the SeNB. Additionally, the sending unit is configured to generate the second check request message according to the identifier of the SeNB, the first identifier information, and the first data packet count value corresponding to the first identifier information, and send the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information. The sending unit is further configured to determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information.
With reference to the thirteenth aspect or the first possible implementation manner of the thirteenth aspect, in a second possible implementation manner, the sending unit is further configured such that when the receiving unit receives an exception report sent by the SeNB, the sending unit sends the exception report to an MME or an O&M server.
In a fourteenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a sending unit configured to send a first check request message to an MeNB, where the first check request message includes first indication information, and the first indication information is used to instruct the MeNB to send a second check request message to a user terminal, and a receiving unit configured to receive a check response message sent by the MeNB. and the apparatus further includes a determining unit configured to determine, according to the check response message, whether a man-in-the-middle attack exists. The sending unit is further configured such that when the determining unit determines that the man-in-the-middle attack exists, the sending unit takes a preset measure for processing and send an exception report to the MeNB.
In a fifteenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a second check request message sent by an MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and a first data packet count value corresponding to the first identifier information, and the second identifier information is a DRB corresponding to the ERAB. The apparatus further includes an obtaining unit configured to obtain the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; a judging unit configured to determine, according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the apparatus; and a sending unit configured to generate a check response message according to a result determined by the judging unit, and send the check response message to the MeNB.
With reference to the fifteenth aspect, in a first possible implementation manner of the fifteenth aspect, when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit is configured to determine that no man-in-the-middle attack exists between the SeNB and the apparatus. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit is configured to determine that a man-in-the-middle attack exists between the SeNB and the apparatus.
In a sixteenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a first check request message sent by an SeNB, and a sending unit configured to: generate a second check request message according to the first check request message, and send the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information. The receiving unit is further configured to receive a check response message generated by the user terminal according to the second check request message, and send the check response message to the SeNB, where the response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
With reference to the sixteenth aspect, in a first possible implementation manner of the sixteenth aspect, the first check request message received by the receiving unit further includes an identifier of the SeNB. Additionally, the sending unit is configured to generate the second check request message according to the identifier of the SeNB and the first check request message, and send the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the first identifier information of the DRB and the first data packet count value corresponding to the first identifier information.
With reference to the sixteenth aspect or the first possible implementation manner of the sixteenth aspect, in a second possible implementation manner, the sending unit is further configured such that when the receiving unit receives an exception report sent by the SeNB, the sending unit sends the exception report to an MME or an O&M server.
In a seventeenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a sending unit configured to send a first check request message to an MeNB, where the first check request message is used to enable the MeNB to generate a second check request message according to the first check request message, and send the second check request message to a user terminal; a receiving unit configured to receive a check response message sent by the MeNB, where the check response message includes first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; an obtaining unit configured to obtain, according to the first identifier information, second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is an ERAB corresponding to the DRB; and a judging unit configured to determine, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists. The sending unit is further configured such that when the judging unit determines that the man-in-the-middle attack exists, the sending unit takes a preset measure for processing and send an exception report to the MeNB.
With reference to the seventeenth aspect, in a first possible implementation manner of the seventeenth aspect, the judging unit is configured such that when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit determines that no man-in-the-middle attack exists between the apparatus and the user terminal. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit determines that a man-in-the-middle attack exists between the apparatus and the user terminal.
In an eighteenth aspect, an embodiment of the present disclosure provides an apparatus for detecting a man-in-the-middle attack. The apparatus includes a receiving unit configured to receive a second check request message sent by an MeNB, and an obtaining unit configured to obtain, according to the second check request message, first identifier information of a DRB and a first data packet count value corresponding to the first identifier information. and the apparatus further includes a sending unit configured to send a check response message to the MeNB, where the check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to an SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the apparatus.
In conclusion, according to the method and the apparatus for detecting a man-in-the-middle attack provided in the embodiments of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. An MeNB receives a first data packet count value that is of a bearer between the SeNB and UE and is sent by the SeNB, and requires, according to the first data packet count value sent by the SeNB, the UE to report a second data packet count value of a bearer between the UE and the SeNB. When the first data packet count value is the same as the second data packet count value, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the user terminal, and notifies the SeNB. Therefore, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the following clearly and completely describes the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. The described embodiments are some but not all of the embodiments of the present disclosure. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.
For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments of the present disclosure constitute no limitation to the present disclosure.
Embodiment 1The following uses
Step 110: The MeNB receives a first check request message sent by a secondary eNodeB (SeNB), where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information.
The SeNB starts detection of a bearer between the SeNB and UE, and the SeNB sends the first check request message to the MeNB, where the first check request message includes the first identifier information of the evolved random access bearer (ERAB) between the SeNB and the UE and the first data packet count value corresponding to the first identifier information.
The MeNB receives the first check request message.
The first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
It may be understood that there are multiple bearers between the SeNB and the UE, and each bearer has one piece of first identifier information. In this embodiment of the present disclosure, the first check request message may include at least one piece of first identifier information corresponding to a bearer, and at least one first data packet count value corresponding to the first identifier information.
Step 120: The MeNB generates a second check request message according to the first identifier information, and sends the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB.
After receiving the first check request message, the MeNB determines that the SeNB starts detection of the bearer between the SeNB and the user terminal UE, and the MeNB obtains the first identifier information and the first data packet count value from the first check request message.
The MeNB locally stores the first data packet count value, and generates the second check request message according to the first identifier information, where the second check request message includes the first indication information, and the first indication information is used to instruct the UE to obtain the second identifier information that matches the first identifier information and is of the DRB between the UE and the SeNB, and the second data packet count value corresponding to the second identifier information.
The second data packet count value reflects a count, obtained by the UE, of sent and received data packets of the bearer between the SeNB and the UE.
It should be noted that because the first check request message may include at least two pieces of first identifier information of a bearer and at least two corresponding first data packet count values in step 110, when the UE obtains the second identifier information and the second data packet count value, the UE obtains, according to each piece of first identifier information, second identifier information corresponding to each piece of first identifier information, and a second data packet count value corresponding to the second identifier information.
Step 130: The MeNB receives a first check response message generated by the user terminal according to the second check request message, where the first check response message includes the second identifier information and the second data packet count value.
The UE obtains, according to the second check request message, the second identifier information that matches the first identifier information, and the second data packet count value. The UE adds the obtained second identifier information and the obtained second data packet count value to the first check response message, and sends the first check response message to the MeNB.
The MeNB receives the first check response message sent by the UE.
Step 140: When the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the user terminal.
In some implementations, the MeNB determines by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and if the first data packet count value is the same as the second data packet count value, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the UE.
According to the foregoing descriptions in step 110 and step 120, because there is at least one piece of first identifier information, at least one piece of second identifier information, at least one first data packet count value, and at least one second data packet count value, and each piece of first identifier information is corresponding to each piece of second identifier information, that the MeNB determines by comparison whether the first data packet count value is the same as the second data packet count value is such that the MeNB determines by comparison whether a first data packet count value corresponding to each piece of first identifier information is the same as a second data packet count value corresponding to the second identifier information that matches each piece of first identifier information.
When first data packet count values corresponding to all first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the UE.
After the MeNB determines that no man-in-the-middle attack exists between the SeNB and the UE, the MeNB sends a second check response message to the SeNB, where the second check response message includes second indication information, the second indication information is used to indicate that no man-in-the-middle attack exists between the SeNB and the UE, and the second indication information may be empty or may include a character string, or the like, such as a character string “no man-in-the-middle attack exists”.
Step 150: When the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the MeNB determines that a man-in-the-middle attack exists between the SeNB and the user terminal.
In some implementations, the MeNB determines by comparison whether the first data packet count value is the same as the second data packet count value, and if the first data packet count value is different from the second data packet count value, the MeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
Further, when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the MeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
After the MeNB determines that a man-in-the-middle attack exists between the SeNB and the UE, the MeNB sends a third check response message to the SeNB, and the third check response message is used to indicate that a man-in-the-middle attack exists between the SeNB and the UE. Further, the third check response message may further include all second data packet count values that are different from the first data packet count value corresponding to the first identifier information, and first identifier information corresponding to the second data packet count values, such that the SeNB determines that a man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, the third check response message may include only a result of the determining, for example, a result that a man-in-the-middle attack exists or no man-in-the-middle attack exists.
After the MeNB sends the third check response message to the SeNB, the MeNB further sends an exception report to a mobility management entity (MME) or an operation and maintenance (O&M) server, such that the MME or the O&M server takes a further measure. As an example instead of a limitation, the further measure is releasing or deleting the bearer between the SeNB and the user terminal, or counting, by the MME or the O&M server, received exception reports, and when a quantity of exception reports exceeds a quantity threshold, processing the bearer between the SeNB and the user terminal.
Optionally, the first check request message in step 110 in this embodiment of the present disclosure further includes an identifier of the SeNB.
That the MeNB generates a second check request message according to the first identifier information, and sends the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to enable the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information in step 120 in this embodiment of the present disclosure includes that the MeNB generates the second check request message according to the first identifier information and the identifier of the SeNB, and sends the second check request message to the UE, such that the UE obtains, according to the second check request message, the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information.
Further, when the first check request message includes the identifier of the SeNB, the second identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the second identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the second identifier information is allocated by the SeNB.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and an MeNB receives a first data packet count value that is of a bearer between the SeNB and UE and is sent by the SeNB, and requires, according to the first data packet count value sent by the SeNB, the UE to report a second data packet count value of a bearer between the UE and the SeNB. When the first data packet count value is the same as the second data packet count value, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the user terminal, and notifies the SeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 2For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 210: The SeNB sends a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal.
In some implementations, the SeNB starts detection of a bearer between the SeNB and the UE, and the SeNB sends the first check request message to the MeNB, where the first check request message includes the first identifier information of the ERAB between the SeNB and the UE and the first data packet count value corresponding to the first identifier information.
The MeNB receives the first check request message, generates the second check request message according to the first identifier information, and sends the second check request message to the UE.
A process in which the MeNB determines, according to the first data packet count value and a second data packet count value reported by the UE, whether a man-in-the-middle attack exists between the SeNB and the UE is described in detail in the foregoing Embodiment 1, and is not repeated here any further.
The second data packet count value is a data packet count value corresponding to second identifier information that matches the first identifier information.
Step 220: The SeNB receives the check response message sent by the MeNB.
Step 230: When the check response message is a second check response message and the second check response message includes second indication information, the SeNB determines, according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the user terminal.
In some implementations, if the MeNB determines that no man-in-the-middle attack exists between the SeNB and the UE, the check response message determined by the MeNB is the second check response message, the second check response message includes the second indication information, and the SeNB determines, according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the UE.
An implementation process of the second check response message is described in detail in the foregoing Embodiment 1, and is not repeated here any further.
Step 240: When the check response message is a third check response message and the third check response message includes third indication information, the SeNB determines, according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the user terminal, and takes a preset measure for processing.
In some implementations, if the MeNB determines that a man-in-the-middle attack exists between the SeNB and the UE, the check response message determined by the MeNB is the third check response message, the third check response message includes the third indication information, and the SeNB determines, according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the UE.
An implementation process of the third check response message is described in detail in the foregoing Embodiment 1, and is not repeated here any further.
Optionally, the first check request message sent by the SeNB to the MeNB in step 210 in this embodiment of the present disclosure further includes an identifier of the SeNB.
That the SeNB sends a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal in step 210 in this embodiment of the present disclosure includes that the SeNB sends the first check request message to the MeNB, where the first check request message includes the identifier of the SeNB, the first identifier information of the ERAB, and the first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate the second check request message according to the first identifier information and the identifier of the SeNB, and send the second check request message to the user terminal.
Further, when the first check request message includes the identifier of the SeNB, the second identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the second identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the second identifier information is allocated by the SeNB.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and the SeNB receives a check response message sent by an MeNB, and determines, according to the check response message, whether a man-in-the-middle attack exists between the SeNB and UE. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 3For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 310: The user terminal receives a second check request message sent by the MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and the second identifier information is a DRB(DRB) corresponding to the ERAB.
In some implementations, the SeNB starts detection of a bearer between the SeNB and the UE, the SeNB sends a first check request message to the MeNB, and the MeNB receives the first check request message, and generates the second check request message according to the first check request message, where the second check request message includes the first identifier information.
A detailed process in which the MeNB generates the second check request message and a meaning of the first identifier information are described in detail in the foregoing Embodiment 1, and are not repeated here any further.
The first identifier information is an identifier of the ERAB between the SeNB and the UE.
Step 320: The user terminal obtains the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information.
In some implementations, the UE obtains the second data packet count value corresponding to the second identifier information.
The second data packet count value reflects a count, obtained by the UE, of sent and received data packets of the bearer between the SeNB and the UE.
Step 330: The user terminal sends the second identifier information and the second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In some implementations, the UE sends the obtained second identifier information and the obtained second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
Further, the first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE, and the first data packet count value is corresponding to the first identifier information.
A described process in which the MeNB determines, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists is described in detail in the foregoing Embodiment 1, and is not repeated here any further.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and a UE obtains second identifier information and a second data packet count value according to first identifier information, and sends the second data packet count value to an MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies the SeNB. Therefore, a problem in other approaches that a scenario in which the SeNB offloads traffic of the MeNB is limited to some extent is resolved, and a case in which the MeNB, the SeNB, and the UE all participate in detection of a man-in-the-middle attack is implemented.
Further,
For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 510: The MeNB receives a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information.
In some implementations, the SeNB starts detection of a bearer between the SeNB and a UE, and the SeNB sends the first check request message to the MeNB, where the first check request message includes the first identifier information of the ERAB between the SeNB and the UE and the first data packet count value corresponding to the first identifier information.
The first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
It may be understood that there are multiple bearers between the SeNB and the UE, and each bearer has one piece of first identifier information. In this embodiment of the present disclosure, the first check request message includes at least two pieces of first identifier information corresponding to a bearer, and at least two first data packet count values corresponding to the first identifier information.
The MeNB receives the first check request message.
Step 520: The MeNB generates a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and sends the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value is the same as the second data packet count value, and the second identifier information is a DRB corresponding to the ERAB.
After receiving the first check request message, the MeNB determines that the SeNB starts detection of the bearer between the SeNB and the UE, and the MeNB obtains the first identifier information and the first data packet count value from the first check request message.
The MeNB generates the second check request message according to the first identifier information and the first data packet count value, and sends the second check request message to the UE, where the second check request message includes the first indication information, and the first indication information is used to instruct the UE to obtain the second identifier information that matches the first identifier information, and the second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value is the same as the second data packet count value.
Further, in this embodiment of the present disclosure, the UE may obtain, according to the first indication information, the second identifier information that matches the first identifier information and is of the DRB between the UE and the SeNB, and the second data packet count value corresponding to the second identifier information.
The second data packet count value reflects a count, obtained by the UE, of sent and received data packets of the bearer between the SeNB and the UE.
It should be noted that because the first check request message may include at least two pieces of first identifier information of a bearer and at least two corresponding first data packet count values in step 510, when the UE obtains the second identifier information and the second data packet count value, the UE obtains, according to each piece of first identifier information, second identifier information corresponding to each piece of first identifier information, and a second data packet count value corresponding to the second identifier.
Step 530: The MeNB receives a check response message generated by the user terminal according to the second check request message, and sends the check response message to the SeNB, such that the SeNB performs processing according to the check response message.
In some implementations, the UE determines by comparison whether the first data packet count value is the same as the second data packet count value, and generates the check response message according to a result of the comparing, and the UE sends the check response message to the MeNB.
According to the foregoing descriptions in step 510 and step 520, because there are at least two pieces of first identifier information, at least two pieces of second identifier information, at least two first data packet count values, and at least two second data packet count values, and each piece of first identifier information is corresponding to each piece of second identifier information, that the UE determines by comparison whether the first data packet count value is the same as the second data packet count value is such that the UE determines by comparison whether a first data packet count value corresponding to each piece of first identifier information is the same as a second data packet count value corresponding to the second identifier information that matches each piece of first identifier information.
When first data packet count values corresponding to all first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the UE determines that no man-in-the-middle attack exists between the SeNB and the UE.
When first data packet count values corresponding to at least two pieces of first identifier information are different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the UE determines that a man-in-the-middle attack exists between the SeNB and the UE.
The MeNB receives the check response message sent by the UE according to a result of the comparing and a result of the determining, and sends the check response message to the SeNB, such that the SeNB performs processing according to the response message.
In an embodiment of the present disclosure, the UE identifies whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and if the first data packet count value is the same as the second data packet count value, the UE determines that no man-in-the-middle attack exists between the SeNB and the UE, and generates a first check response message. The MeNB receives the first check response message sent by the UE, and sends the first check response message to the SeNB, such that the SeNB performs processing according to the first check response message, where the first check response message includes a first indication information, and the first indication information may be empty or may be a character string, such as a character string identifier “no” or “no man-in-the-middle attack exists”.
In another embodiment of the present disclosure, the UE identifies whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and if the first data packet count value is different from the second data packet count value, the UE determines that a man-in-the-middle attack exists between the SeNB and the UE, and generates a second check response message. The MeNB receives the second check response message sent by the UE, and sends the second check response message to the SeNB, such that the SeNB performs processing according to the second check response message. The second check response message includes second indication information, and the second indication information may further include all second data packet count values that are different from the first data packet count value corresponding to the first identifier information, and first identifier information corresponding to the second data packet count values, such that the SeNB determines that a man-in-the-middle attack exists between the SeNB and the user terminal; or the third check response message may include only a result of the determining, for example, include a result that a man-in-the-middle attack exists or no man-in-the-middle attack exists.
In this embodiment of the present disclosure, the SeNB determines, according to the check response message, whether a man-in-the-middle attack exists between the SeNB and the UE. When the SeNB determines, according to the check response message, that a man-in-the-middle attack exists between the SeNB and the UE, the SeNB sends an exception report to the MeNB.
Optionally, the first check request message sent in step 510 in this embodiment of the present disclosure further includes an identifier of the SeNB.
That the MeNB generates a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and sends the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value is the same as the second data packet count value in step 520 in this embodiment of the present disclosure includes that the MeNB generates the second check request message according to the identifier of the SeNB, the first identifier information, and the first data packet count value corresponding to the first identifier information, and sends the second check request message to the UE, where the second check request message includes the first indication information, and the first indication information is used to instruct the UE to obtain the second identifier information that matches the first identifier information, and the second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value is the same as the second data packet count value.
Further, when the first check request message includes the identifier of the SeNB, the second identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the second identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the second identifier information is allocated by the SeNB.
Optionally, after step 530 in this embodiment of the present disclosure, the method further includes a step in which the MeNB sends the exception report to an MME or an O&M.
In some implementations, when the MeNB receives the exception report sent by the SeNB, the MeNB sends the exception report to the MME or the O&M server.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and an MeNB sends a second check request message to UE according to a first check request message sent by the SeNB. When the UE determines, according to the second check request message, that a man-in-the-middle attack exists between the SeNB and the UE, the MeNB receives a check response message sent by the UE, and forwards the check response message to the SeNB. According to the technical solution provided in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 5For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 610: The SeNB sends a first check request message to an MeNB, where the first check request message includes first indication information, and the first indication information is used to instruct the MeNB to send a second check request message to a user terminal such as a UE.
In some implementations, the SeNB starts detection of a bearer between the SeNB and the UE, and the SeNB sends the first check request message to the MeNB, where the first check request message includes the first indication information, and the first indication information is used to instruct the MeNB to send the second check request message to the UE.
Content carried by the first check request message and a detailed process in which the MeNB sends the second check request message to the UE according to the first indication information are described in detail in the foregoing Embodiment 4, and are not repeated here any further.
Step 620: The SeNB receives a check response message sent by the MeNB.
In some implementations, the MeNB sends the second check request message to the UE, such that the UE determines, according to the second check request message, whether a man-in-the-middle attack exists between the SeNB and the UE, and sends the check response message to the MeNB according to a result of the determining. The MeNB sends the check response message to the SeNB.
Step 630: The SeNB determines, according to the check response message, whether a man-in-the-middle attack exists.
In some implementations, the SeNB receives the check response message, and determines, according to the check response message, whether a man-in-the-middle attack exists.
Further, when the check response message carries a data packet count value fed back by the UE, the SeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
Step 640: When determining that the man-in-the-middle attack exists, the SeNB takes a preset measure for processing and sends an exception report to the MeNB.
In some implementations, when the SeNB determines that a man-in-the-middle attack exists, the SeNB takes the preset measure for processing and sends the exception report to the MeNB, such that the MeNB sends the exception report to an MME or an O&M server.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. When a UE determines that a man-in-the-middle attack exists between the SeNB and the UE, the SeNB receives a check response message sent by an MeNB, and determines whether a man-in-the-middle attack exists between the SeNB and the UE. According to the technical solution provided in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 6For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 710: The UE receives a second check request message sent by an MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and a first data packet count value corresponding to the first identifier information, and the second identifier information is a DRB corresponding to the ERAB.
In some implementations, the UE receives the second check request message sent by the MeNB, where the second check request message includes the first identifier information of the ERAB between an SeNB and the UE and the first data packet count value corresponding to the first identifier information.
The first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
A detailed process in which the MeNB generates the second check request message according to a first check request message sent by the SeNB and sends the second check request message to the UE, and content carried in the first check request message are described in detail in the foregoing Embodiment 4, and are not repeated here any further.
Step 720: The UE obtains the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information.
In some implementations, the UE obtains, according to the first identifier information included in the second check request message, the second identifier information corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information.
Further, in this embodiment of the present disclosure, the UE obtains the second identifier information and the second data packet count value corresponding to the second identifier information.
The second data packet count value reflects a count, obtained by the UE, of sent and received data packets of the bearer between the SeNB and the UE.
It should be noted that because the first check request message may include at least two pieces of first identifier information of a bearer and at least two corresponding first data packet count values in step 710, when the UE obtains the second identifier information and the second data packet count value, the UE obtains, according to each piece of first identifier information, second identifier information corresponding to each piece of first identifier information, and a second data packet count value corresponding to the second identifier.
Step 730: The UE determines, according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the UE.
In some implementations, the UE determines by comparison whether the first data packet count value is the same as the second data packet count value, and when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the UE determines that no man-in-the-middle attack exists between the SeNB and the UE.
When the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the UE determines that a man-in-the-middle attack exists between the SeNB and the UE.
Further, according to the foregoing description in step 720, because there are at least two pieces of first identifier information, at least two pieces of second identifier information, at least two first data packet count values, and at least two second data packet count values, and each piece of first identifier information is corresponding to each piece of second identifier information, that the UE determines by comparison whether the first data packet count value is the same as the second data packet count value is such that the UE determines by comparison whether a first data packet count value corresponding to each piece of first identifier information is the same as a second data packet count value corresponding to the second identifier information that matches each piece of first identifier information.
When first data packet count values corresponding to all first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the UE determines that no man-in-the-middle attack exists between the SeNB and the UE.
When first data packet count values corresponding to at least two pieces of first identifier information are different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the UE determines that a man-in-the-middle attack exists between the SeNB and the UE.
Step 740: The UE generates a check response message according to a result of the determining, and sends the check response message to the MeNB.
In some implementations, the UE generates the check response message according to the result of the determining in step 730, and sends the check response message to the MeNB.
Further, in an implementation manner, the UE identifies whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and if the first data packet count value is the same as the second data packet count value, the UE determines that no man-in-the-middle attack exists between the SeNB and the UE, and generates a first check response message. The MeNB receives the first check response message sent by the UE, and sends the first check response message to the SeNB, such that the SeNB performs processing according to the first check response message.
In another implementation manner, the UE identifies whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information. If the first data packet count value is different from the second data packet count value, the UE determines that a man-in-the-middle attack exists between the SeNB and the UE, and generates a second check response message. The MeNB receives the second check response message sent by the UE, and sends the second check response message to the SeNB, such that the SeNB performs processing according to the second check response message.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and a UE determines, according to a second check request message sent by an MeNB, whether a man-in-the-middle attack exists between the SeNB and the UE. When the UE determines that a man-in-the-middle attack exists between the SeNB and the UE, the UE sends a check response message to the MeNB. According to the technical solution provided in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Further,
For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 910: The MeNB receives a first check request message sent by an SeNB.
In some implementations, the SeNB starts detection of a bearer between the SeNB and a UE, and the SeNB sends the first check request message to the MeNB, where the first check request message is used to enable the MeNB to send a second check request message to the UE.
Step 920: The MeNB generates a second check request message according to the first check request message and sends the second check request message to the UE, where the second check request message includes first indication information, and the first indication information is used to instruct the UE to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
In some implementations, after receiving the first check request message, the MeNB determines that the SeNB starts detection of the bearer between the SeNB and the UE, and the MeNB determines, according to the first check request message, that the SeNB expects to receive a data packet count value that is of the bearer between the SeNB and the UE and is reported by the UE, and the MeNB generates the second check request message and sends the second check request message to the UE.
Further, the second check request message includes the first indication information, and in this embodiment of the present disclosure, the UE may obtain, according to the first indication information, the first identifier information of the DRB between the UE and the SeNB and the first data packet count value corresponding to the first identifier information.
The first data packet count value reflects a count, obtained by the UE, of sent and received data packets of the bearer between the SeNB and the UE.
It may be understood that there are multiple bearers between the SeNB and the UE, and each bearer has a specified service. In this embodiment of the present disclosure, the SeNB may send one first check request message to the MeNB, such that the UE reports at least two first data packet count values corresponding to all bearers between the UE and the SeNB.
Step 930: The MeNB receives a check response message generated by the UE according to the second check request message, and sends the check response message to the SeNB, where the response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
In some implementations, the UE obtains the first identifier information and the first data packet count value according to the second check request message. The UE adds the obtained first identifier information and the obtained first data packet count value to the check response message, and sends the check response message to the MeNB.
The MeNB receives a first check response message sent by the UE.
The check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
Optionally, the first check request message received by the MeNB in step 910 in this embodiment of the present disclosure further includes an identifier of the SeNB.
That the MeNB generates a second check request message according to the first check request message, and sends the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information in step 920 in this embodiment of the present disclosure includes that the MeNB generates the second check request message according to the identifier of the SeNB and the first check request message, and sends the second check request message to the UE. The second check request message includes the first indication information, and the first indication information is used to instruct the UE to obtain the first identifier information and the first data packet count value corresponding to the first identifier information.
Further, when the first check request message includes the identifier of the SeNB, the first identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the first identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the first identifier information is allocated by the SeNB.
Optionally, after step 930 in this embodiment of the present disclosure, the method further includes a step in which the MeNB sends an exception report to an MME or an O&M server.
In some implementations, when the MeNB receives the exception report sent by the SeNB, the MeNB sends the exception report to the MME or the O&M server.
The exception report sent by the SeNB is generated after the SeNB determines, according to the first data packet count value and a second data packet count value that is stored and obtained by the SeNB, whether a man-in-the-middle attack exists.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. An MeNB sends a second check request message to a UE according to a first check request message sent by the SeNB, and forwards, to the SeNB, a check response message fed back by the UE, such that the SeNB determines whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies the MeNB. According to the technical solution provided in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 8For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 1010: The SeNB sends a first check request message to an MeNB, where the first check request message is used to enable the MeNB to generate a second check request message according to the first check request message, and send the second check request message to a user terminal such as a UE.
In some implementations, the SeNB starts detection of a bearer between the SeNB and UE, and the SeNB sends the first check request message to the MeNB, where the first check request message is used to enable the MeNB to generate the second check request message and send the second check request message to the UE.
A detailed process in which the MeNB generates the second check request message and sends the second check request message to the UE is described in detail in the foregoing Embodiment 8, and is not repeated here any further.
Step 1020: The SeNB receives a check response message sent by the MeNB, where the check response message includes first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
In some implementations, the UE obtains, according to the second check request message, the first identifier information of the DRB between the UE and the SeNB and the first data packet count value corresponding to the first identifier information. The UE adds the first identifier information and the first data packet count value to the check response message, and sends the check response message to the MeNB.
The MeNB sends the check response message to the SeNB.
The first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
It may be understood that there are multiple bearers between the SeNB and the UE, and each bearer has one piece of first identifier information. In this embodiment of the present disclosure, the first check request message may include at least two pieces of first identifier information corresponding to a bearer, and at least two first data packet count values.
Step 1030: The SeNB obtains, according to the first identifier information, second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is an ERAB corresponding to the DRB.
In some implementations, after receiving the check response message, the SeNB obtains the first identifier information and the first data packet count value from the check response message. The SeNB obtains, according to the first identifier information, the second identifier information that is corresponding to the first identifier information and is of the ERAB between the SeNB and the UE and the second data packet count value corresponding to the second identifier information.
The second data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
It should be noted that because the check response message includes at least two pieces of first identifier information in step 1020, when the SeNB obtains the second identifier information that matches the first identifier information, and the second data packet count value, the SeNB obtains, according to each piece of first identifier information, second identifier information that matches each piece of first identifier information, and a second data packet count value corresponding to the second identifier information.
Step 1040: The SeNB determines, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In some implementations, the SeNB identifies whether the first data packet count value is the same as the second data packet count value, and if the first data packet count value is the same as the second data packet count value, the SeNB determines that no man-in-the-middle attack exists between the SeNB and the UE. Alternatively, if the first data packet count value is different from the second data packet count value, the SeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
According to the foregoing descriptions in step 1020 and step 1030, because there are at least two pieces of first identifier information, at least two pieces of second identifier information, at least two first data packet count values, and at least two second data packet count values, and each piece of first identifier information is corresponding to each piece of second identifier information, that the SeNB determines whether the first data packet count value is the same as the second data packet count value is such that the SeNB identifies whether a first data packet count value corresponding to each piece of second identifier information is the same as a second data packet count value corresponding to the first identifier information that matches each piece of second identifier information.
When the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the SeNB determines that no man-in-the-middle attack exists between the SeNB and the UE.
That is, when first data packet count values corresponding to all first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the SeNB determines that no man-in-the-middle attack exists between the SeNB and the UE.
When the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the SeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
That is, when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the SeNB determines that a man-in-the-middle attack exists between the SeNB and the UE.
Step 1050: When it is determined that the man-in-the-middle attack exists, the SeNB takes a preset measure for processing and send an exception report to the MeNB.
In some implementations, after the SeNB determines that a man-in-the-middle attack exists between the SeNB and the UE, the SeNB takes the preset measure for processing and sends the exception report to the MeNB, such that the MeNB sends the exception report to an MME or an O&M server, and the MME or the O&M server takes a further measure. As an example instead of a limitation, the further measure is releasing or deleting the bearer between the SeNB and the user terminal. Alternatively, the further measure is counting, by the MME or the O&M server, received exception reports, and when a quantity of exception reports exceeds a quantity threshold, processing the bearer between the SeNB and the UE.
Optionally, the first check request message in step 1010 in this embodiment of the present disclosure further includes an identifier of the SeNB, and the second check request message further includes the identifier of the SeNB.
Further, when the first check request message includes the identifier of the SeNB, the first identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the first identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the second identifier information is allocated by the SeNB.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and requires a UE to report a first data packet count value of a bearer between the UE and the SeNB. The SeNB determines, according to the first data packet count value and an obtained second data packet count value stored by the SeNB, whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies an MeNB. According to the technical solution provided in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 9For better understanding of the embodiments of the present disclosure, the following uses embodiments to provide further explanations with reference to the accompanying drawings, and the embodiments constitute no limitation to the embodiments of the present disclosure.
The following uses
Step 1110: The user terminal such as a UE receives a second check request message sent by an MeNB.
In some implementations, an SeNB starts detection of a bearer between the SeNB and the UE, and the SeNB sends a first check request message to the MeNB, where the first check request message is used to enable the MeNB to generate the second check request message and send the second check request message to the UE.
The UE receives the second check request message sent by the MeNB.
A detailed process in which the MeNB generates the second check request message and sends the second check request message to the UE is described in detail in the foregoing Embodiment 8, and is not repeated here any further.
Step 1120: The UE obtains, according to the second check request message, first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
In some implementations, the UE obtains, according to the second check request message, the first identifier information of the DRB between the UE and the SeNB and the first data packet count value corresponding to the first identifier information.
The first data packet count value reflects a count, obtained by the SeNB, of sent and received data packets of the bearer between the SeNB and the UE.
It may be understood that there are multiple bearers between the SeNB and the UE, and each bearer has one piece of first identifier information. In this embodiment of the present disclosure, the first check request message may include at least two pieces of first identifier information corresponding to a bearer, and at least two corresponding first data packet count values.
Step 1130: The UE sends a check response message to the MeNB, where the check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to an SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the UE.
In some implementations, the UE adds the obtained first identifier information and the obtained first data packet count value to the check response message, and sends the check response message to the MeNB.
The check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to the SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the UE.
Optionally, the first check request message received by the MeNB in step 1110 in this embodiment of the present disclosure further includes an identifier of the SeNB.
Further, when the first check request message includes the identifier of the SeNB, the first identifier information is allocated by the SeNB.
Further, when the first check request message does not include the identifier of the SeNB, the first identifier information is allocated by the MeNB.
In this embodiment of the present disclosure, when the first check request message includes the identifier of the SeNB, the identifier of the SeNB is further carried in a subsequent check response message, such that a receiver determines, according to the identifier, that the first identifier information is allocated by the SeNB.
In conclusion, according to the method for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. A UE receives a second check request message sent by an MeNB, and sends a check response message to the MeNB according to the second check request message. The MeNB forwards the check response message to the SeNB, such that the SeNB determines whether a man-in-the-middle attack exists between the SeNB and the UE. Therefore, a problem in other approaches that a scenario in which the SeNB offloads traffic of the MeNB is limited to some extent is resolved, and a case in which the MeNB, the SeNB, and the UE all participate in detection of a man-in-the-middle attack is implemented.
Further,
Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 1310 included in the apparatus is configured to receive a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information.
The sending unit 1320 is configured generate a second check request message according to the first identifier information, and send the second check request message to a user terminal. The second check request message includes first indication information used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB.
The receiving unit 1310 is further configured to receive a first check response message generated by the user terminal according to the second check request message, where the first check response message includes the second identifier information and the second data packet count value.
The judging unit 1330 is configured such that when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit 1330 determines that no man-in-the-middle attack exists between the SeNB and the user terminal. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit 1330 determines that a man-in-the-middle attack exists between the SeNB and the user terminal.
The first check request message received by the receiving unit 1310 further includes an identifier of the SeNB.
The sending unit 1320 is further configured to generate the second check request message according to the first identifier information and the identifier of the SeNB, and send the second check request message to the user terminal, such that the user terminal obtains, according to the second check request message, the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information.
The first check request message received by the receiving unit 1310 includes at least two pieces of first identifier information and at least two corresponding first data packet count values, and the first check response message received by the receiving unit includes at least two pieces of second identifier information and at least two corresponding second data packet count values.
The judging unit 1330 is configured such that when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, the judging unit 1330 determines that a man-in-the-middle attack exists between the SeNB and the UE.
The judging unit 1330 is configured such that when the first data packet count values corresponding to all the first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, the judging unit 1330 determines that no man-in-the-middle attack exists between the SeNB and the UE.
The sending unit 1320 is further configured to send a second check response message to the SeNB, where the second check response message includes second indication information, and the second indication information is used to indicate that no man-in-the-middle attack exists between the SeNB and the UE.
The sending unit 1320 is further configured to send an exception report to an MME or an O&M server.
The sending unit 1320 is further configured to send a third check response message to the SeNB, where the third check response message includes third indication information, and the third indication information is used to indicate that a man-in-the-middle attack exists between the SeNB and the UE.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. An MeNB receives a first data packet count value that is of a bearer between the SeNB and a UE and is sent by the SeNB, and requires, according to the first data packet count value sent by the SeNB, the UE to report a second data packet count value of a bearer between the UE and the SeNB. When the first data packet count value is different from the second data packet count value, the MeNB determines that no man-in-the-middle attack exists between the SeNB and the UE, and notifies the SeNB. According to the technical solution and the apparatus in the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 11Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The sending unit 1410 included in the apparatus is configured to send a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information. The first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information. Additionally, the sending unit 1410 is configured to send the second check request message to a user terminal such as a UE.
The receiving unit 1420 is configured to receive the check response message sent by the MeNB.
The determining unit 1430 is configured such that when the check response message is a second check response message and the second check response message includes second indication information, the determining unit 1430 determines, according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the UE. Alternatively, when the check response message is a third check response message and the third check response message includes third indication information, the determining unit 1430 determines, according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the UE, and takes a preset measure for processing.
The first check request message sent by the sending unit 1410 further includes an identifier of the SeNB.
The sending unit 1410 is configured to send the first check request message to the MeNB, where the first check request message includes the identifier of the apparatus, the first identifier information of the ERAB, and the first data packet count value corresponding to the first identifier information. The first check request message is used to enable the MeNB to generate the second check request message according to the first identifier information and the identifier of the apparatus. The sending unit 1410 is further configured to send the second check request message to the UE.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. The SeNB receives a check response message sent by an MeNB, and determines, according to the check response message, whether a man-in-the-middle attack exists between the SeNB and a UE. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 12Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 1510 included in the apparatus is configured to receive a second check request message sent by the MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and the second identifier information is a DRB corresponding to the ERAB.
The obtaining unit 1520 is configured to obtain the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information.
The sending unit 1530 is configured to send the second identifier information and the second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. A UE obtains second identifier information and a second data packet count value according to first identifier information, and sends the second data packet count value to an MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies the SeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 13Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 1610 included in the apparatus is configured to receive a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information.
The sending unit 1620 is configured to generate a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and send the second check request message to a user terminal (e.g., UE), where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB.
The receiving unit 1610 is further configured to receive a check response message generated by the user terminal according to the second check request message, and send the check response message to the SeNB, such that the SeNB performs processing according to the response message.
The first check request message received by the receiving unit 1610 further includes an identifier of the SeNB.
The sending unit 1620 is configured to generate the second check request message according to the identifier of the SeNB, the first identifier information, and the first data packet count value corresponding to the first identifier information, and send the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information.
The sending unit 1620 is further configured such that when the receiving unit receives an exception report sent by the SeNB, the sending unit 1620 sends the exception report to an MME or an O&M server.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and an MeNB sends a second check request message to a UE according to a first check request message sent by the SeNB. When the UE determines, according to the second check request message, that a man-in-the-middle attack exists between the SeNB and the UE, the MeNB receives a check response message sent by the UE, and forwards the check response message to the SeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 14Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The sending unit 1710 included in the apparatus is configured to send a first check request message to an MeNB, where the first check request message includes first indication information, and the first indication information is used to instruct the MeNB to send a second check request message to a user terminal.
The receiving unit 1720 is configured to receive a check response message sent by the MeNB.
The determining unit 1730 is configured to determine, according to the check response message, whether a man-in-the-middle attack exists.
The sending unit 1710 is further configured such that when the determining unit 1730 determines that the man-in-the-middle attack exists, the sending unit 1710 takes a preset measure for processing and send an exception report to the MeNB.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. When a UE determines that a man-in-the-middle attack exists between the SeNB and the UE, the SeNB receives a check response message sent by an MeNB, and determines whether a man-in-the-middle attack exists between the SeNB and the UE. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 15Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 1810 included in the apparatus is configured to receive a second check request message sent by an MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and a first data packet count value corresponding to the first identifier information, and the second identifier information is a DRB corresponding to the ERAB.
The obtaining unit 1820 is configured to obtain the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information.
The judging unit 1830 is configured to determine, according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the apparatus.
The sending unit 1840 is configured to generate a check response message according to a result determined by the judging unit, and send the check response message to the MeNB.
The judging unit 1830 is configured such that when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit 1830 determines that no man-in-the-middle attack exists between the SeNB and the apparatus. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit 1830 determines that a man-in-the-middle attack exists between the SeNB and the apparatus.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and a UE determines, according to a second check request message sent by an MeNB, whether a man-in-the-middle attack exists between the SeNB and the UE. When the UE determines that a man-in-the-middle attack exists between the SeNB and the UE, the UE sends a check response message to the MeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 16Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 1910 included in the apparatus is configured to receive a first check request message sent by an SeNB.
The sending unit 1920 is configured to generate a second check request message according to the first check request message, and send the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
The receiving unit 1910 is further configured to receive a check response message generated by the user terminal according to the second check request message, and send the check response message to the SeNB, where the response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
The first check request message received by the receiving unit 1910 further includes an identifier of the SeNB.
The sending unit 1920 is configured to generate the second check request message according to the identifier of the SeNB and the first check request message, and send the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the first identifier information of the DRB and the first data packet count value corresponding to the first identifier information.
The sending unit 1920 is further configured such that when the receiving unit receives an exception report sent by the SeNB, the sending unit 1920 sends the exception report to an MME or an O&M server.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. An MeNB sends a second check request message to a UE according to a first check request message sent by the SeNB, and forwards, to the SeNB, a check response message fed back by the UE, such that the SeNB determines whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies the MeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 17Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The sending unit 2010 included in the apparatus is configured to send a first check request message to an MeNB, where the first check request message is used to enable the MeNB to generate a second check request message according to the first check request message, and send the second check request message to a user terminal.
The receiving unit 2020 is configured to receive a check response message sent by the MeNB, where the check response message includes first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
The obtaining unit 2030 is configured to obtain, according to the first identifier information, second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is an ERAB corresponding to the DRB.
The judging unit 2040 is configured to determine, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
The sending unit 2010 is further configured such that when the judging unit 2040 determines that the man-in-the-middle attack exists, the sending unit 2010 take a preset measure for processing and send an exception report to the MeNB.
The judging unit 2040 is configured such that when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, the judging unit 2040 determines that no man-in-the-middle attack exists between the apparatus and the user terminal. Alternatively, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, the judging unit 2040 determines that a man-in-the-middle attack exists between the apparatus and the user terminal.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack, and requires a UE to report a first data packet count value of a bearer between the UE and the SeNB. The SeNB determines, according to the first data packet count value and an obtained second data packet count value stored by the SeNB, whether a man-in-the-middle attack exists between the SeNB and the UE, and notifies an MeNB. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 18Accordingly, an embodiment of the present disclosure further provides an apparatus for detecting a man-in-the-middle attack. An implementation structure of the apparatus is shown in
The receiving unit 2110 included in the apparatus is configured to receive a second check request message sent by an MeNB.
The obtaining unit 2120 is configured to obtain, according to the second check request message, first identifier information of a DRB and a first data packet count value corresponding to the first identifier information.
The sending unit 2130 is configured to send a check response message to the MeNB, where the check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to an SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the apparatus.
In conclusion, according to the apparatus for detecting a man-in-the-middle attack provided in this embodiment of the present disclosure, an SeNB initiates detection of a man-in-the-middle attack. A UE receives a second check request message sent by an MeNB, and sends a check response message to the MeNB according to the second check request message. The MeNB forwards the check response message to the SeNB, such that the SeNB determines whether a man-in-the-middle attack exists between the SeNB and the UE. According to the technical solution of the present disclosure, in a scenario in which the SeNB offloads traffic of the MeNB, the MeNB, the SeNB, and the UE all can participate in detection of a man-in-the-middle attack.
Embodiment 19In addition, the apparatus for detecting a man-in-the-middle attack provided in Embodiment 10 of the present disclosure may also be implemented in the following manner, in order to implement the foregoing method for detecting a man-in-the-middle attack in Embodiment 1 of the present disclosure. As shown in
The network interface 2210 is configured to perform interaction and communication with a UE and an SeNB.
The memory 2230 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2230 is configured to store an application program, where the application program may be used to enable the processor 2220 to access and execute instructions. The instructions include: receiving a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information; generating a second check request message according to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB; receiving a first check response message generated by the user terminal according to the second check request message, where the first check response message includes the second identifier information and the second data packet count value; and determining, when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal; or determining, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal.
Further, the first check request message further includes an identifier of the SeNB.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process of generating a second check request message according to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to enable the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where executing the process comprises: generating the second check request message according to the first identifier information and the identifier of the SeNB, and sending the second check request message to the user terminal, such that the user terminal obtains, according to the second check request message, the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information.
Further, the first check request message includes at least two pieces of first identifier information and at least two corresponding first data packet count values, and the first check response message includes at least two pieces of second identifier information and at least two corresponding second data packet count values.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process of the determining, when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal, where executing the process comprises: determining, when a first data packet count value corresponding to at least one piece of first identifier information is different from the second data packet count value corresponding to the second identifier information that matches the first identifier information, that a man-in-the-middle attack exists between the SeNB and the user terminal.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process of determining, when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal, where executing the process comprises: determining, when the first data packet count values corresponding to all the first identifier information are the same as the second data packet count value corresponding to the second identifier information that matches the first identifier information, that no man-in-the-middle attack exists between the SeNB and the user terminal.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute the following process of sending a second check response message to the SeNB, where the second check response message includes second indication information, and the second indication information is used to indicate that no man-in-the-middle attack exists between the SeNB and the UE.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute the following process or sending an exception report to an MME or an O&M server.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute the following process of sending a third check response message to the SeNB, where the third check response message includes third indication information, and the third indication information is used to indicate that a man-in-the-middle attack exists between the SeNB and the user terminal.
In addition, as shown in
The memory 2230 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2230 is configured to store an application program, where the application program may be used to enable the processor 2220 to access and execute the following instructions: receiving a first check request message sent by an SeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information; generating a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, and the second identifier information is a DRB corresponding to the ERAB; and receiving a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, such that the SeNB performs processing according to the response message.
Further, the first check request message further includes an identifier of the SeNB.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process of generating a second check request message according to the first identifier information and the first data packet count value corresponding to the first identifier information, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, where executing the process comprises: generating the second check request message according to the identifier of the SeNB, the first identifier information, and the first data packet count value corresponding to the first identifier information, and sending the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the second identifier information that matches the first identifier information and the identifier of the SeNB, and the second data packet count value corresponding to the second identifier information, and determine by comparison whether the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process when the MeNB receives an exception report sent by the SeNB, where executing the process comprises sending the exception report to an MME or an O&M server.
In addition, as shown in
The memory 2230 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2230 is configured to store an application program, where the application program may be used to enable the processor 2220 to access and execute the following instructions: receiving a first check request message sent by an SeNB; generating a second check request message according to the first check request message, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; and receiving a check response message generated by the user terminal according to the second check request message, and sending the check response message to the SeNB, where the response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists.
Further, the first check request message further includes an identifier of the SeNB.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process of generating a second check request message according to the first check request message, and sending the second check request message to a user terminal, where the second check request message includes first indication information, and the first indication information is used to instruct the user terminal to obtain first identifier information of a DRB and a first data packet count value corresponding to the first identifier information, where executing the process comprises: generating the second check request message according to the identifier of the SeNB and the first check request message, and sending the second check request message to the user terminal, where the second check request message includes the first indication information, and the first indication information is used to instruct the user terminal to obtain the first identifier information of the DRB and the first data packet count value corresponding to the first identifier information.
Further, the application program stored in the memory 2230 further includes an instruction that may be used to enable the processor 2220 to execute a process when the apparatus receives an exception report sent by the SeNB, where executing the process comprises sending the exception report to an MME or an O&M server.
Embodiment 20In addition, the apparatus for detecting a man-in-the-middle attack provided in Embodiment 11 of the present disclosure may also be implemented in the following manner, in order to implement the foregoing method for detecting a man-in-the-middle attack in Embodiment 2 of the present disclosure. As shown in
The network interface 2310 is configured to perform interaction and communication with an MeNB and UE.
The memory 2330 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2330 is configured to store an application program, where the application program may be used to enable the processor 2320 to access and execute the following instructions: sending a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal; receiving the check response message sent by the MeNB; and when the check response message is a second check response message and the second check response message includes second indication information, determining, according to the second indication information, that no man-in-the-middle attack exists between the SeNB and the user terminal; or when the check response message is a third check response message and the third check response message includes third indication information, determining, according to the third indication information, that a man-in-the-middle attack exists between the SeNB and the user terminal, and taking a preset measure for processing.
Further, the first check request message further includes an identifier of the apparatus.
Further, the application program stored in the memory 2330 further includes an instruction that may be used to enable the processor 2320 to execute a process of sending a first check request message to an MeNB, where the first check request message includes first identifier information of an ERAB and a first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate a second check request message according to the first identifier information, and send the second check request message to a user terminal, where executing the process comprises: sending the first check request message to the MeNB, where the first check request message includes the identifier of the apparatus, the first identifier information of the ERAB, and the first data packet count value corresponding to the first identifier information, and the first check request message is used to enable the MeNB to generate the second check request message according to the first identifier information and the identifier of the SeNB, and send the second check request message to the user terminal.
In addition, as shown in
The memory 2330 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2330 is configured to store an application program, where the application program may be used to enable the processor 2320 to access and execute the following instructions: sending a first check request message to an MeNB, where the first check request message includes first indication information, and the first indication information is used to instruct the MeNB to send a second check request message to a user terminal; receiving a check response message sent by the MeNB; determining, according to the check response message, whether a man-in-the-middle attack exists; and when it is determined that the man-in-the-middle attack exists, taking a preset measure for processing and sending an exception report to the MeNB.
In addition, as shown in
The memory 2330 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2330 is configured to store an application program, where the application program may be used to enable the processor 2320 to access and execute the following instructions: sending a first check request message to an MeNB, where the first check request message is used to enable the MeNB to generate a second check request message according to the first check request message, and send the second check request message to a user terminal; receiving a check response message sent by the MeNB, where the check response message includes first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; obtaining, according to the first identifier information, second identifier information that matches the first identifier information, and a second data packet count value corresponding to the second identifier information, where the second identifier information is an ERAB corresponding to the DRB; determining, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists; and when it is determined that the man-in-the-middle attack exists, taking a preset measure for processing and sending an exception report to the MeNB.
Further, the application program stored in the memory 2330 further includes an instruction that may be used to enable the processor 2320 to execute a process of determining, according to the first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists, where executing the process of determining comprises: when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, determining that no man-in-the-middle attack exists between the apparatus and the user terminal. Alternatively, executing the process of determining comprises: when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, determining that a man-in-the-middle attack exists between the apparatus and the user terminal.
Embodiment 21In addition, the apparatus for detecting a man-in-the-middle attack provided in Embodiment 12 of the present disclosure may also be implemented in the following manner, in order to implement the foregoing method for detecting a man-in-the-middle attack in Embodiment 3 of the present disclosure. As shown in
The network interface 2410 is configured to perform interaction and communication with a UE and an MeNB.
The memory 2430 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2430 is configured to store an application program, where the application program may be used to enable the processor 2420 to access and execute the following instructions: receiving a second check request message sent by the MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and the second identifier information is a DRB corresponding to the ERAB; obtaining the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; and sending the second identifier information and the second data packet count value corresponding to the second identifier information to the MeNB, such that the MeNB determines, according to a first data packet count value and the second data packet count value, whether a man-in-the-middle attack exists.
In addition, as shown in
The memory 2330 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2330 is configured to store an application program, where the application program may be used to enable the processor 2320 to access and execute the following instructions: receiving a second check request message sent by an MeNB, where the second check request message includes second identifier information corresponding to first identifier information of an ERAB, and a first data packet count value corresponding to the first identifier information, and the second identifier information is a DRB corresponding to the ERAB; obtaining the second identifier information corresponding to the first identifier information, and a second data packet count value corresponding to the second identifier information; determining, according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the apparatus; and generating a check response message according to a result of the determining, and sending the check response message to the MeNB.
Further, the application program stored in the memory 2430 further includes an instruction that may be used to enable the processor 2420 to execute a process of determining, according to the first data packet count value corresponding to the first identifier information, and the second data packet count value corresponding to the second identifier information, whether a man-in-the-middle attack exists between an SeNB and the apparatus, where executing the process of determining comprises: when the first data packet count value corresponding to the first identifier information is the same as the second data packet count value corresponding to the second identifier information, determining that no man-in-the-middle attack exists between the SeNB and the apparatus. Alternatively, executing the process of determining comprises: when the first data packet count value corresponding to the first identifier information is different from the second data packet count value corresponding to the second identifier information, determining that a man-in-the-middle attack exists between the SeNB and the apparatus.
In addition, as shown in
The memory 2330 may be a permanent memory, for example, a hard disk drive and a flash memory, and the memory 2330 is configured to store an application program, where the application program may be used to enable the processor 2320 to access and execute the following instructions: receiving a second check request message sent by an MeNB; obtaining, according to the second check request message, first identifier information of a DRB and a first data packet count value corresponding to the first identifier information; and sending a check response message to the MeNB, where the check response message includes the first identifier information and the first data packet count value corresponding to the first identifier information, such that the MeNB sends the check response message to an SeNB, and the SeNB determines, according to the first data packet count value, whether a man-in-the-middle attack exists between the SeNB and the apparatus.
Further embodiments of the present disclosure are provided in the following. It should be noted that the numbering used in the following section does not necessarily need to comply with the numbering used in the previous sections.
A person skilled in the art may be further aware that, in combination with the examples described in the embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware, computer software, or a combination thereof. To clearly describe the interchangeability between the hardware and the software, the foregoing has generally described compositions and steps of each example according to functions. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present disclosure.
Steps of methods or algorithms described in the embodiments disclosed in this specification may be implemented by hardware, a software module executed by a processor, or a combination thereof. The software module may reside in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, or any other form of storage medium known in the art.
In the foregoing implementation manners, the objective, technical solutions, and benefits of the present disclosure are further described in detail. It should be understood that the foregoing descriptions are merely example implementation manners of the present disclosure, but are not intended to limit the protection scope of the present disclosure. Any modification, equivalent replacement, or improvement made without departing from the principle of the present disclosure should fall within the protection scope of the present disclosure.
Claims
1. A method for detecting a man-in-the-middle attack, the method comprising:
- sending, by a secondary base station, a first check request message to a master base station, wherein the first check request message comprises first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information;
- receiving, by the master base station, the first check request message;
- obtaining, by the master base station, second identifier information that matches the first identifier information, wherein the second identifier information is an identifier of a data radio bearer (DRB) corresponding to the ERAB;
- sending, by the master base station, a second check request message to a user terminal, wherein the second check request message comprises the first data packet count value and the second identifier information; and
- receiving, by the master base station, a check response message from the user terminal.
2. The method according to claim 1, further comprising:
- receiving, by the user terminal, the second check request message;
- determining, by the user terminal, whether a second data packet count value is equal to the first data packet count value, wherein the second data packet count value corresponds to the second identifier information; and
- sending, by the user terminal, the check response message to the master base station.
3. The method according to claim 2, further comprising generating, by the user terminal, the check response message based on determining whether the second data packet count value is equal to the first data packet count value.
4. The method according to claim 2, further comprising sending, by the master base station, an exception report to a mobility management entity or an operation and maintenance server when the check response message comprises the second data packet count value.
5. The method according to claim 2, wherein the first data packet count value reflects a count, obtained by the secondary base station, of sent and received data packets of a bearer between the secondary base station and the user terminal.
6. The method according to claim 2, wherein the second data packet count value reflects a count, obtained by the user terminal, of sent and received data packets of a bearer between the secondary base station and the user terminal.
7. A system for detecting a man-in-the-middle attack, wherein the system comprises:
- a master base station; and
- a secondary base station configured to send a first check request message, wherein the first check request message comprises first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information,
- wherein the master base station is configured to: receive the first check request message; obtain second identifier information that matches the first identifier information, wherein the second identifier information is an identifier of a data radio bearer (DRB) corresponding to the ERAB; send a second check request message to a user terminal, wherein the second check request message comprises the first data packet count value and the second identifier information; and receive a check response message from the user terminal.
8. The system according to claim 7, wherein the user terminal is configured to:
- receive the second check request message;
- determine whether a second data packet count value is equal to the first data packet count value, wherein the second data packet count value corresponds to the second identifier information; and
- send the check response message to the master base station.
9. The system according to claim 8, wherein the user terminal is further configured to generate the check response message based on determining whether the second data packet count value is equal to the first data packet count value.
10. The system according to claim 8, wherein the master base station is further configured to send an exception report to a mobility management entity or an operation and maintenance server when the check response message comprises the second data packet count value.
11. The system according to claim 8, wherein the first data packet count value reflects a count, obtained by the secondary base station, of sent and received data packets of a bearer between the secondary base station and the user terminal.
12. The system according to claim 8, wherein the second data packet count value reflects a count, obtained by the user terminal, of sent and received data packets of a bearer between the secondary base station and the user terminal.
13. A method for detecting a man-in-the-middle attack, the method comprising:
- receiving, by a master base station, a first check request message from a secondary base station, wherein the first check request message comprises first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information;
- obtaining, by the master base station, second identifier information that matches the first identifier information, wherein the second identifier information is an identifier of a data radio bearer (DRB) corresponding to the ERAB;
- sending, by the master base station, a second check request message to a user terminal, wherein the second check request message comprises the first data packet count value and the second identifier information that matches the first identifier information; and
- receiving, by the master base station, a check response message from the user terminal.
14. The method according to claim 13 wherein the check response message comprises a second data packet count value.
15. The method according to claim 13, further comprising sending, by the master base station, an exception report to a mobility management entity or an operation and maintenance server.
16. The method according to claim 13, wherein the first data packet count value reflects a count, obtained by the secondary base station, of sent and received data packets of a bearer between the secondary base station and the user terminal.
17. The method according to claim 14, wherein the second data packet count value reflects a count, obtained by the user terminal, of sent and received data packets of a bearer between the secondary base station and the user terminal.
18. An apparatus comprising:
- a network interface; and
- a processor coupled to the network interface, wherein the processor is configured to: receive a first check request message from a secondary base station through the network interface, wherein the first check request message comprises first identifier information of an evolved random access bearer (ERAB) and a first data packet count value corresponding to the first identifier information; obtain second identifier information that matches the first identifier information, wherein the second identifier information is an identifier of a data radio bearer (DRB) corresponding to the ERAB; send a second check request message to a user terminal through the network interface, wherein the second check request message comprises the first data packet count value and the second identifier information that matches the first identifier information; and receive a check response message from the user terminal through the network interface.
19. The apparatus according to claim 18, wherein the check response message comprises a second data packet count value.
20. The apparatus according to claim 18, wherein the processor is further configured to send an exception report to a mobility management entity or an operation and maintenance server.
Type: Application
Filed: May 24, 2019
Publication Date: Sep 12, 2019
Inventors: Rong Wu (Shenzhen), Chengdong He (Shenzhen), Lu Gan (Shenzhen)
Application Number: 16/422,051
