# US 10,771,979 B2 · Fake base station short message identification > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,771,979 B2 - Document ID: US10771979B2 - Status: Granted - Kind: B2 - Application number: 15/861,477 - Filed: 2018-01-03 - Published: 2018-07-05 - Granted: 2020-09-08 - Earliest claimed: 2017-01-03 - Assignees: Alibaba Group Holding Limited - Applicants: Alibaba Group Holding Limited - Inventors: XiaoYuan Bai; Hongru Zhu - Web page: https://patentgrep.com/patent/US10771979B2 ## CPC - H04W 12/122: Counter-measures against attacks; Protection against rogue devices - H04W 12/12: Detection or prevention of fraud - H04W 12/128: Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware - H04L 63/1416: {Event detection, e.g. attack signature detection} - H04L 63/166: {at the transport layer} - H04W 88/184: {Messaging devices, e.g. message centre} - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method includes: extracting a data value of receiver address field from a short message; wherein the short message sent by the short message center includes receiver address field, and the data value of the receiver address field includes the receiver's MSISDN; if the short message does not include the receiver address field or the data value is not local MSISDN such as the MSISDN of the receiver terminal, determining the short message as a fake base station short message. The MSISDN used in the present disclosure is an existing feature of the sender terminal and the receiver terminal without requiring the user to perform additional operations. Moreover, neither the short message center nor the receiver terminal needs to acquire the preset cryptogram in the gateway. Therefore, the present disclosure accurately detects a fake base station short message without requiring the user to perform additional operations. ## Claims ### Claim 1 A system comprising: a short message center and a receiver terminal, the short message center configure to: receive a first short message sent by a sender terminal, generate a second short message to a receiver terminal by adding a receiver address field of the receiver terminal to the received first short message in according to a preset short message format, and send the second short message to the receiver terminal; wherein: the preset short message format includes a receiver address field and a data value of the receiver address field includes a Mobile Station International Subscriber Directory Number (MSISDN) of the receiver terminal, the receiver terminal configured to: determine whether the second short message is a fake base station short message by extracting the receiver address field, determine the second short message as a fake base station short include the receiver address field and the data value of the receiver address field does not include the MSISDN of the receiver terminal, and delete the fake base station short message in response to determining that short message is the fake base station short message. ### Claim 2 (depends on 1) The system of claim 1, wherein the Mobile Station International Subscriber Directory Number (MSISDN) of the receiver terminal is a phone number of the receiver terminal. ### Claim 3 (depends on 1) The system of claim 1, further comprising: the sender terminal that sends the first short message to the short message center. ### Claim 4 (depends on 1) The system of claim 1, further comprising: the receiver terminal that receives the second short message sent by the short message center, and extracts the data value of the receiver address field from the second short message. ### Claim 5 (depends on 4) The system of claim 4, wherein: the receiver terminal, in response to determining that the second short message does not include the receiver address field or the data value is not the MSISDN of the receiver terminal, determines the second short message as a fake base station short message. ### Claim 6 (depends on 5) The system of claim 5, wherein: the receiver terminal deletes the fake base station short message. ### Claim 7 (depends on 5) The system of claim 5, wherein: the receiver terminal displays the fake base station short message in a spam folder of the receiver terminal. ### Claim 8 (depends on 4) The system of claim 4, wherein: the receiver terminal, in response to determining that the data value of the receiver address field includes the MSISDN of the receiver terminal, determines the second short message as a valid message. ### Claim 9 (depends on 1) The system of claim 1, wherein the preset short message format further includes: a Short Message Service Center Number (SCA); a Protocol Data Unit Type (PDU-Type); an Originator Address (OA); a Protocol Identification (PID); a Data Coding Scheme (DCS); and a Service Center Time Stamp (SCTS), a User Data Length (UDL), and a User Data (UD). ### Claim 10 A method comprising: receiving, by a short message center, a first short message sent by a sender terminal; generating, by the short message center, a second short message to a receiver terminal by adding a receiver address field of the receiver terminal to the received first short message in according to a preset short message format; sending, by the short message center, the second shod message to the receiver terminal; determining, by the receiver terminal, whether the second short message is a fake base station short message by extracting the receiver address field; wherein the preset short message format includes the receiver address field, and a data value of the receiver address field includes a unique identification of the receiver terminal that is a feature of the receive terminal; determining, by the receiver terminal, the second short message as a fake base station short message in response to determining that the second short message does not include the receiver address field and the data value of the receiver address field does not include the MSISDN of the receiver terminal; and deleting, by the receiver terminal, the fake base station short message in response to determining that short message is the fake base station short message. ### Claim 11 (depends on 10) The method of claim 10, wherein: the unique identification is a Mobile Station International Subscriber Directory Number (MSISDN) of the receiver terminal. ### Claim 12 (depends on 11) The method of claim 11, wherein the Mobile Station International Subscriber Directory Number (MSISDN) of the receiver terminal is a phone number of the receiver terminal. ### Claim 13 (depends on 10) The method of claim 10, wherein sending by the short message center the second short message to the receiver terminal includes: acquiring an International Mobile Subscriber Identity (IMSI) corresponding to the MSISDN; querying a current location corresponding to the IMSI in a Home Location Register (HLR); and sending the second short message to the Mobile Switching Center (MSC) corresponding to the current location of the receiver terminal to request the MSC to send the second short message to the receiver terminal. ### Claim 14 (depends on 10) The method of claim 10, wherein the preset short message format further includes: a Short Message Service Center Number (SCA); a Protocol Data Unit Type (PDU-Type); an Originator Address (OA); a Protocol Identification (PID); a Data Coding Scheme (DCS); and a Service Center Time Stamp (SCTS), a User Data Length (UDL), and a User Data (UD). ### Claim 15 One or more memories storing thereon computer-readable instructions that, when executed by the one or more processors, cause the one or more processors to perform acts comprising: receiving, a short message sent from a short message center; extracting, by a receiver terminal, a data value of a receiver address field from the short message; determining, by the receiver terminal, whether the short message includes the receiver address field and whether the data value includes a local Mobile Station International Subscriber Directory Number (MSISDN); and determining, by the receiver terminal, the short message as a fake base satiation short message in response to determining that the short message does not include the receiver address field and the data value does not include the MSISDN of the receiver terminal; deleting, by the receiver terminal, the fake base station short message in response to determining that short message is the fake base station short message. ### Claim 16 (depends on 15) The one or more memories of claim 15, wherein the Mobile Station International Subscriber Directory Number (MSISDN) of the receiver terminal is a phone number of the receiver terminal that receives the short message. ### Claim 17 (depends on 15) The one or more memories of claim 15, wherein the acts further comprise: controlling the short message to be invisible in a display area of the valid short message. ### Claim 18 (depends on 15) The one or more memories of claim 15, wherein the controlling the short message to be invisible in the display area of the valid short message includes: deleting the short message; or, displaying the short message in a display area of an invalid short message. ### Claim 19 (depends on 15) The one or more memories of claim 15, wherein the acts further comprise: in response to determining that the short message includes the receiver address field and the data value does not include the local MSISDN, determining the short message as a non-fake base station short message; and displaying the short message in a display area of a valid short message. ### Claim 20 (depends on 15) The one or more memories of claim 15, wherein the short message further includes: a Short Message Service Center Number (SCA); a Protocol Data Unit Type (PDU-Type); an Originator Address (OA); a Protocol Identification (PID); a Data Coding Scheme (DCS); and a Service Center Time Stamp (SCTS), a User Data Length (UDL), and a User Data (UD).