WO2018094594A1

WO2018094594A1 - Communication method and device

Info

Publication number: WO2018094594A1
Application number: PCT/CN2016/106885
Authority: WO
Inventors: 刘海
Original assignee: 华为技术有限公司
Priority date: 2016-11-23
Filing date: 2016-11-23
Publication date: 2018-05-31

Abstract

Provided are a communication method and device. The method comprises: a terminal device receiving a short message key sent by a server accessed by the terminal device; and when the terminal device receives a short message, decrypting the short message according to the short message key. The embodiments of the present application can ensure the security of a short message received by the terminal device, and a short message sent by a short message service centre can be decrypted correctly; however, a short message sent by a pseudo base station may be decrypted into a messy code, so that the decrypted content can indicate whether the short message is legal, thereby reducing the influence of illegal short messages on users.

Description

Communication method and device

Technical field

The present application relates to the field of communications and, more particularly, to a communication method and apparatus.

Background technique

In the Global System for Mobile Communication (GSM), the network can authenticate the terminal device, and the terminal device does not authenticate the network. In this case, the pseudo base station can masquerade as the base station of the operator, forcibly connect the terminal device to the pseudo base station, and send a short message to the terminal device. Since the short message sent by the pseudo base station often contains malicious spoofed content, the user is deceived.

Summary of the invention

The embodiment of the present application provides a communication method and device, which can ensure the security of a short message received by the terminal device.

In a first aspect, the embodiment of the present application provides a communication method, including: receiving, by a terminal device, the short information key sent by a server accessed by the terminal device; when receiving the short message, the terminal device according to the The short message key decrypts the short message.

Therefore, in the embodiment of the present application, the terminal device decrypts the received short message according to the short message key sent by the server, so that the security of the short message received by the terminal device can be ensured, and the short message service center sends the short message service center. The short message can be decrypted correctly, and the short message sent by the pseudo base station may be decrypted into garbled, so that the content after the decryption can indicate whether the short message is legal, thereby reducing the influence of the illegal short message on the user.

In addition, the terminal device receives the short message key sent by the server, and can prevent the short message service from being sent by the short message service center to the terminal device, where the terminal device cannot know that the key sender is a short message service. The center is also a problem with pseudo base stations.

In an optional implementation manner, when the terminal device decrypts the short message according to the short message key and the decryption fails, the method further includes: the terminal device hiding or deleting the short message; / or the terminal device sends the short message to a server accessed by the terminal device.

At this time, the terminal device directly hides or deletes the decrypted short message without presenting the decrypted content to the user, and can reduce the interference of the short message to the user; The short message is directly sent to the server, so that the server can perform big data analysis, thereby assisting the government department in combating the work of the pseudo base station.

Optionally, in the embodiment of the present application, when the terminal device decrypts the short message and decrypts successfully, the terminal device may present the short message to the user.

Optionally, in the embodiment of the present application, after decrypting the short message, the terminal device may present the obtained content to the user, and the user may determine the legality of the short message according to whether the content is garbled.

In an optional implementation, before the terminal device receives the short message key sent by the server accessed by the terminal device, the method further includes: the terminal device according to the terminal device Determining, by the at least one of the type of the attached network, the location of the terminal device, and the user setting, whether the short message service center corresponding to the terminal device needs to encrypt the short message to be sent to the terminal device; When the short message service center needs to encrypt the short message to be sent to the terminal device, the terminal device sends the first indication information to the server, where the first indication information is used to indicate that the short message service center needs to be sent The short message of the terminal device is encrypted.

Optionally, when the type of the network to which the terminal device is attached is a global mobile communication system attachment type, the server may determine that the short message service center needs to encrypt a short message to be sent to the terminal device; When the type of the network to which the terminal device is attached is a long term evolution attachment type, the server may determine that the short message service center does not need to encrypt the short message to be sent to the terminal device.

Optionally, an area where the long-term evolution signal strength is less than a preset threshold may be defined as a long-term evolution weak coverage area, and an area where the long-term evolution signal strength is greater than or equal to a preset threshold is defined as a long-term evolution strong coverage area, where When the terminal device is in a weak coverage area of the long term evolution signal, the server may determine that the short message service center needs to encrypt the short message to be sent to the terminal device; when the terminal device is in a strong coverage area of the long term evolution signal The server may determine that the short message service center does not need to encrypt the short message to be sent to the terminal device.

Optionally, when the user is configured to require encryption, the server may determine, according to the user equipment, that the short message service center needs to encrypt the short message to be sent to the terminal device; when the user sets the encryption to be unnecessary, the server The server may determine, according to the user equipment, that the short message service center does not need to encrypt the short message to be sent to the terminal device.

In an optional implementation manner, the terminal device receives the service accessed by the terminal device Before the short message key sent by the server, the method further includes: the terminal device transmitting, to the server, at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting Species

The terminal device receives the short message key sent by the server accessed by the terminal device, and the terminal device receives the short message key, where the short message key is the server Determining, according to at least one of a type of a network to which the terminal device is attached, a location of the terminal device, and the user setting, that the short message service center needs to encrypt a short message to be sent to the terminal device .

In an optional implementation manner, the method further includes: receiving, by the terminal device, algorithm indication information that is sent by the server to indicate an encryption algorithm; and determining, by the terminal device, the Encryption Algorithm;

The terminal device decrypts the short message according to the short message key when receiving the short message, and the terminal device: the terminal device decrypts the short message according to the short information key and the encryption algorithm. .

Optionally, the encryption algorithm may be a data encryption algorithm standard or an advanced encryption standard.

In a second aspect, the embodiment of the present application provides a communication method, including: a short message service center encrypts a short message to be sent to the terminal device according to a short information key corresponding to the terminal device; the short message service center The encrypted short message to be sent is sent to the terminal device.

Therefore, in the embodiment of the present application, the short message service center needs to encrypt the short message to be sent to the terminal device by using the short message key, thereby ensuring the security of the short message received by the terminal device, and the short message service. The short message sent by the center can be decrypted correctly, and the short message sent by the pseudo base station may be decrypted into garbled code, so that the content after the decryption can indicate whether the short message is legal, thereby reducing the influence of the illegal short message on the user.

In an optional implementation manner, the method further includes: receiving, by the short message service center, a notification message sent by the server, where the notification message is used to notify the short message service center to send the a short message key; the short message service center generates the short message key; the short message service center sends the short message key to the server.

Optionally, the short message service center may randomly generate the short message key.

At this time, when the short message service center generates the short message key, different short message keys can be set for each terminal device, thereby further improving security.

In an optional implementation, the method further includes: receiving, by the short message service center The short message key sent by the server.

In an optional implementation manner, before the short message service center and the server perform information transmission, the method further includes: the short message service center establishing a connection with the server.

In an optional implementation manner, the method further includes: the short message service center receives algorithm indication information sent by the server to indicate an encryption algorithm; and the SMSC determines where the algorithm indicates information Encryption algorithm

The short message service center encrypts the short message to be sent to the terminal device according to the short message key corresponding to the terminal device, including: the short message service center according to the short message key and the encryption algorithm Encrypt the short message.

In an optional implementation manner, the method further includes: the short message service center determines an encryption algorithm; and the short message service center sends an algorithm indication information for indicating the encryption algorithm to the server;

In a third aspect, the embodiment of the present application provides a communication method, including: a server generating a short message key; the server transmitting the short message key to a terminal device and the terminal device that have accessed the server Corresponding short message service center, wherein the short message key is used by the terminal device to decrypt the received short message, and the short message service center encrypts the short message to be sent to the terminal device .

Therefore, in the embodiment of the present application, the terminal device needs to decrypt the received short message by using the short message key, and the short message service center corresponding to the terminal device needs to be sent to the terminal by using the short message key. The short message of the device is encrypted, so that the security of the short message received by the terminal device can be ensured, and the short message sent by the short message service center can be correctly decrypted, and the short message sent by the pseudo base station may be decrypted into garbled code, so that after decryption The content can indicate whether the short message is legal, thereby reducing the impact of the illegal short message on the user.

In addition, when the short message key is sent to the terminal device by the server, and the short message service center can be prevented from transmitting the short message key to the terminal device, the terminal device cannot know that the key sender is the short message service center. It is also a problem of the pseudo base station; and when the server generates the short message key, different short message keys can be set for each terminal device, thereby further improving security.

Optionally, the server may randomly generate the short message key.

In an optional implementation, before the server generates the short message key, the method further includes: the server is configured according to a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting. Determining, according to the encryption indication information sent by the terminal device, whether the short message service center needs to encrypt the short message to be sent to the terminal device;

The server generates the short message key, and the server generates the short message key when it is determined that the short message service center sends the short message to be treated to the terminal device.

In an optional implementation manner, the server may further determine, according to the user information and the preset rule, that the short message service center needs to encrypt the short message to be sent to the terminal device.

In an optional implementation manner, before the server sends the short message key to a terminal device that has accessed the server and a short message service center corresponding to the terminal device, the method further includes: The server determines the short message service center corresponding to the terminal device; the server establishes a new connection with the short message service center.

In an optional implementation manner, the determining, by the server, the short message service center corresponding to the terminal device, the determining, by the server, determining, according to the phone number segment uploaded by the terminal device, the terminal device The short message service center.

In an optional implementation manner, the method further includes: the server determining an encryption algorithm, where the encryption algorithm is when the terminal device decrypts the received short message according to the short message key, and And an encryption algorithm required by the short message service center to encrypt the short message to be sent to the terminal device according to the short message key; the server sends an algorithm indication information for indicating the encryption algorithm to the a terminal device and the short message service center.

In an optional implementation manner, the method further includes: the server receiving, by the short message service center, algorithm indication information for indicating an encryption algorithm, where the algorithm indication information is used to indicate that the terminal device is And an encryption algorithm required to be used when the short message service center decrypts the received short message according to the short message key, and the short message service center encrypts the short message to be sent to the terminal device according to the short message key; The server sends the algorithm indication information to the terminal device.

In an optional implementation manner, the server is a cloud server.

In a fourth aspect, the embodiment of the present application provides a terminal device, which is used to perform the method in any of the foregoing possible implementation manners of the first aspect or the first aspect. Specifically, the terminal device includes a module unit for performing the method in any of the above possible implementation manners of the first aspect or the first aspect.

In a fifth aspect, the embodiment of the present application provides a short message service center, which is used to perform the method in any of the foregoing possible implementation manners of the second aspect or the second aspect. Specifically, the short message service center includes a module unit for performing the method in any of the above possible implementation manners of the second aspect or the second aspect.

In a sixth aspect, the embodiment of the present application provides a server, which is used to perform the method in any one of the foregoing possible implementation manners of the third aspect or the third aspect. In particular, the server comprises a modular unit for performing the method of any of the possible implementations of the third aspect or the third aspect described above.

In a seventh aspect, the embodiment of the present application provides a terminal device, where the method of any one of the foregoing first aspect or the first aspect is implemented, where the terminal device includes a processor, a memory, and a transceiver. The processor, the memory, and the transceiver are coupled by a bus system, wherein the memory is for storing instructions, the transceiver is for receiving and transmitting information, and the processor is configured to perform the memory storage instruction.

The transceiver is configured to receive a short message key sent by a server accessed by the terminal device;

The processor is configured to decrypt the short message according to the short message key when the receiving module receives the short message.

In an eighth aspect, the embodiment of the present application provides a short message service center, where the method of any one of the foregoing second aspect or the second aspect is implemented, where the short message service center includes a processor, a memory and a transceiver, the processor, the memory and the transceiver are connected by a bus system, wherein the memory is for storing instructions, the transceiver is for receiving and transmitting information, and the processor is configured to execute The instructions stored in the memory.

The processor is configured to encrypt a short message to be sent to the terminal device according to a short information key corresponding to the terminal device;

The transceiver is configured to send the short message encrypted by the encryption module to the terminal device.

In a ninth aspect, the embodiment of the present application provides a server for performing the foregoing third aspect or A method in any one of the possible implementations of the third aspect, the server comprising a processor, a memory and a transceiver, the processor, the memory and the transceiver are connected by a bus system, wherein the memory For storing instructions, the transceiver is for receiving and transmitting information, and the processor is configured to execute the instructions stored by the memory.

Wherein the processor is configured to generate a short message key;

The transceiver is configured to send the short message key to a terminal device that has accessed the server and a short message service center corresponding to the terminal device, where the short message key is used for the terminal device Decrypting the received short message and encrypting the short message to be sent to the terminal device by the short message service center.

In a tenth aspect, the embodiment of the present application provides a computer readable medium for storing a computer program, where the computer program includes any possible implementation manner for performing the above first aspect or the first aspect, and second Aspect or any of the possible implementations of the second aspect and the instructions of the method of the third aspect or any of the possible implementations of the third aspect.

DRAWINGS

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

2 is a schematic interaction diagram of a communication method in accordance with an embodiment of the present application.

FIG. 3 is a schematic interaction diagram of a communication method according to an embodiment of the present application.

4 is a schematic interaction diagram of a communication method in accordance with an embodiment of the present application.

FIG. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.

FIG. 6 is a schematic block diagram of a short message service center according to an embodiment of the present application.

FIG. 7 is a schematic block diagram of a server in accordance with an embodiment of the present application.

FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

FIG. 9 is a schematic structural diagram of a short message service center according to an embodiment of the present application.

FIG. 10 is a schematic structural diagram of a server according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a GSM system, Code Division Multiple Access ("CDMA") system. Wideband Code Division Multiple Access (WCDMA) system, Long Term Evolution (LTE) system, LTE Frequency Division Duplex (referred to as "Frequency Division Duplex" FDD") system, LTE Time Division Duplex ("TDD"), Universal Mobile Telecommunication System (UMTS), and the fifth generation (5th-Generation) For "5G") communication systems, etc.

The present application describes various embodiments in connection with a terminal device. The terminal device may also refer to a user equipment (User Equipment, referred to as "UE"), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication. Device, user agent, or user device. The terminal device has a function of receiving a short message.

FIG. 1 is a schematic diagram of an application scenario 100 of an embodiment of the present application. As shown in FIG. 1 , in a normal short message sending process, the short message service center (SMSC) 10 first sends a short message to a mobile switching center (Mobile Switch Center, referred to as “MSC” for short). The MSC 20 sends the short message to the base station 30, and the base station 30 sends the short message to the terminal device 40.

The pseudo base station 50 can forcibly connect the terminal device 40 to the pseudo base station 50. At this time, the pseudo base station 50 sends short information including the spoofed content to the terminal device 40, and the terminal device 40 does not know that the short message is false. The base station 50 sends.

Therefore, in order to solve the problem, the embodiment of the present application provides a communication method and device. The communication method of the embodiment of the present application will be described below with reference to FIG. 2 to FIG.

FIG. 2 shows a schematic interaction diagram of a communication method 200 of an embodiment of the present application. The method 200 can be applied to the scenario shown in FIG. 1 and can also be applied to other scenarios. For example, the SMSC 10 can send a short message to the terminal device 40 through other devices, which is not limited in this embodiment of the present application.

In 201, the server accessed by the terminal device acquires a short message key. The short message key is used by the terminal device to decrypt the received short message, and the short message key used by the terminal device is encrypted by the SMSC to be sent to the terminal device.

In this embodiment of the present application, the server may obtain the short message key in the following manner.

In the first implementation manner, the server may generate the short message key; the server may send the short message key to the SMSC corresponding to the terminal device.

Alternatively, the server may randomly generate the short message key.

In a second implementation manner, the server may send a notification message to the SMSC corresponding to the terminal device, where the notification message is used to notify the SMSC to send the short message key to the server; the server may receive the Short message key.

Optionally, in the embodiment of the present application, before the server obtains the short message key, the server may determine whether the SMSC needs to encrypt the short message to be sent to the terminal device; and the server determines that the SMSC needs to be sent. When the short message of the terminal device is encrypted, the server can acquire the short message key.

Specifically, the server may determine whether the SMSC needs to encrypt the short message sent to the terminal device in the following manner.

Mode 1

The terminal device may send, to the server, at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting; the server may be based on a type of the network to which the terminal device is attached, a location of the terminal device, and At least one of the user settings determines whether the SMSC corresponding to the terminal device needs to encrypt the short message to be sent to the terminal device.

Optionally, the type of the network to which the terminal device is attached may include a GSM attachment type and an LTE attachment type.

Optionally, the location of the terminal device may include that the terminal device is in a weak coverage area of the LTE and the terminal device is in a strong coverage area of the LTE, where an area where the LTE signal strength is less than a preset threshold may be defined as a weak coverage of the LTE. The area, the area where the LTE signal strength is greater than or equal to the preset threshold is defined as a strong coverage area of LTE.

Optionally, the user setting may include: requiring encryption and no encryption, wherein the user is configured to indicate that the SMSC needs to encrypt the short message to be sent to the terminal device when the user needs to be encrypted, and the user is configured to use the encryption when not required. The SMSC is instructed not to encrypt the short message to be sent to the terminal device.

For example, when the type of the network to which the terminal device is attached is the GSM attachment type, the server may determine that the SMSC needs to encrypt the short message to be sent to the terminal device; when the type of the network to which the terminal device is attached is the LTE attachment type, The server can determine that the SMSC does not need to encrypt the short message to be sent to the terminal device.

For another example, when the terminal device is in a weak coverage area of the LTE signal, the server may determine that the SMSC needs to encrypt the short message to be sent to the terminal device; When the LTE signal has a strong coverage area, the server may determine that the SMSC does not need to encrypt the short message to be sent to the terminal device.

For another example, when the user is set to require encryption, the server may determine, according to the user setting, that the SMSC needs to encrypt the short message to be sent to the terminal device; when the user device does not need to be encrypted, the server may determine according to the user setting. The SMSC does not need to encrypt the short message to be sent to the terminal device.

Optionally, the server may determine, according to the type of the network to which the terminal device is attached, the location of the terminal device, and the highest priority in the user setting, whether the SMSC corresponding to the terminal device needs to be sent to the The short message of the terminal device is encrypted.

For example, the priority of the location of the terminal device is higher than the type of the network to which the terminal device is attached, and when the type of the network to which the terminal device is attached is the LTE attachment type, and the terminal device is in the weak coverage area of the LTE signal, The server may determine that the SMSC needs to encrypt the short message to be sent to the terminal device.

For example, if the priority set by the user is higher than the type of the network to which the terminal device is attached, the type of the network to which the terminal device is attached is a GSM attachment type, and the user sets the SMS to be sent to the terminal device by the SMSC. When encrypting, the server can determine that the SMSC does not need to encrypt the short message to be sent to the terminal device.

For example, if the priority set by the user is higher than the type of the network to which the terminal device is attached and the location of the terminal device, the type of the network to which the terminal device is attached is the LTE attachment type, the weak coverage area of the LTE signal, and the user. When the SMSC does not need to encrypt the short message to be sent to the terminal device, the server may determine that the SMSC does not need to encrypt the short message to be sent to the terminal device.

Optionally, the terminal device may periodically send, to the server, at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting.

Optionally, the terminal device may send the location of the terminal device to the server when the location of the terminal device changes.

Optionally, the terminal device may send the user setting to the server when the user setting changes.

Mode 2

The terminal device can be based on the type of the network to which the terminal device is attached and the location of the terminal device. And determining, by the at least one of the user settings, whether the SMSC corresponding to the terminal device needs to encrypt the short message to be sent to the terminal device; when the terminal device determines that the encryption is required, the terminal device may send the first indication to the server The first indication information is used to indicate that the SMSC needs to encrypt the short message to be sent to the terminal device. The server may determine, according to the first indication information, that the SMSC needs to encrypt the short message to be sent to the terminal device.

For example, when the type of the network to which the terminal device is attached is the GSM attachment type, the weak coverage area in the LTE, or the user sets the corresponding SMSC to encrypt the short message to be sent to the terminal device, the terminal device determines that encryption is required, and Sending the first indication information to the server.

It should be understood that the case where the terminal device determines whether the encryption is needed in the mode 2 is similar to the case where the server determines whether the encryption is needed in the mode 1, and details are not described herein again.

Optionally, in the embodiment of the present application, when the terminal device determines that encryption is not required according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting, the terminal device may The server sends the second indication information, where the second indication information is used to indicate that the SMSC does not need to encrypt the short message to be sent to the terminal device; the server may determine, according to the second indication information, that the SMSC does not need to be sent to the The short message of the terminal device is encrypted.

For example, when the type of the network to which the terminal device is attached is the LTE attachment type, the terminal device may determine that the corresponding SMSC does not need to encrypt the short message to be sent to the terminal device, and send the second indication information to the server.

Optionally, in the embodiment of the present application, when the server determines that the SMSC corresponding to the terminal device does not need to encrypt the short message to be sent to the terminal device, and the SMSC corresponding to the terminal device is to be sent to the terminal device. In the case where the short message has been encrypted, the server can notify the SMSC that it does not need to encrypt when sending a short message to the terminal device, and can notify the terminal device that it does not need to decrypt when receiving the short message.

Optionally, in the embodiment of the present application, the server may further determine, according to the user information and the preset rule that the terminal device counts, whether the SMSC needs to encrypt the short message to be sent to the terminal device.

For example, the terminal device may collect statistics on the processing of the short message by the user and send the information to the server, and the server may determine the click rate of the link in the short message, and if the click rate exceeds a certain threshold, the user may be determined to be a vulnerable user. It is determined that the SMSC needs to encrypt the short message to be sent to the terminal device.

As another example, the server can determine that the SMSC needs to encrypt the message to be sent to the terminal device during a certain time period.

Optionally, in the embodiment of the present application, when the server determines that the SMSC corresponding to the terminal device needs to encrypt the short message to be sent to the terminal device, the server may determine the SMSC corresponding to the terminal device.

Optionally, the server may determine the SMSC corresponding to the terminal device according to the phone number segment uploaded by the terminal device.

For example, the server stores a mapping table of the telephone number segment and the SMSC, and the telephone number segment of the terminal device is 131, and the server can determine that the telephone number segment 131 corresponds to the SMSC1 according to the mapping table.

It should be understood that the server may further determine the SMSC corresponding to the terminal device according to other information of the terminal device, for example, the terminal device uploads the identification code of the phone number segment, and the server may determine the corresponding SMSC according to the identification code.

Optionally, in the embodiment of the present application, before the information transmission between the server and the SMSC, the server may determine whether a connection has been established with the SMSC; if the connection is not established, the server establishes a new connection with the SMSC.

For example, the server may send a connection establishment request message to the SMSC for requesting to establish a connection with the SMSC; after receiving the connection establishment request message, the SMSC may establish a connection with the server; after the connection establishment is completed, the server may A connection establishment complete message is fed back to the SMSC.

Optionally, in the embodiment of the present application, the server may determine an encryption algorithm, and send algorithm indication information for indicating the encryption algorithm to the terminal device and the SMSC; or the server may receive the identifier sent by the SMSC for indicating encryption. The algorithm of the algorithm indicates information, and the algorithm indication information used to indicate the encryption algorithm is sent to the terminal device.

Optionally, the encryption algorithm may be a Data Encryption Standard ("DES") or an Advanced Encryption Standard ("AES").

In 202, the server sends the short message key to the accessed terminal device.

In 203, the terminal device receives the short message key.

Optionally, in the embodiment of the present application, the server may be a cloud server, or may be another server.

Optionally, the terminal device accesses the cloud server before sending the information to the cloud server, and disconnects from the cloud server after receiving the short message key; the terminal device may also access the cloud server all the time.

Optionally, the terminal device may receive algorithm indication information sent by the server to indicate an encryption algorithm.

At 204, the SMSC obtains the short message key.

In an implementation, the SMSC can receive the short message key sent by the server.

In another implementation manner, the SMSC may receive the notification information sent by the server, where the notification message is used to notify the SMSC to send the short message key to the server; the SMSC generates the short message key; the SMSC will The short message key is sent to the server.

Optionally, the SMSC can randomly generate the short message key.

Optionally, in the embodiment of the present application, the SMSC may determine an encryption algorithm, and send the algorithm indication information used to indicate the encryption algorithm to the server; or the SMSC receives an algorithm indication information sent by the server to indicate the encryption algorithm. .

In 205, when the SMSC needs to send a short message to the terminal device, the SMSC can encrypt the short message according to the short message key.

Optionally, if the encryption algorithm is specified, the SMSC may encrypt the short message according to the encryption algorithm and the short message key.

In 206, the SMSC sends the encrypted short message to the terminal device.

In 207, the terminal device receives the short message.

Optionally, the short message may be an encrypted short message sent by the SMSC, or may be a short message sent by the pseudo base station.

In 208, the terminal device can decrypt the received short message according to the short message key.

Optionally, in the embodiment of the present application, when the terminal device decrypts the short message and the decryption succeeds, the terminal device may present the short message to the user.

For example, after the decryption, the information content obtained by the terminal device is “debitage occurs in your bank account”, the terminal device may determine that the short message is a legitimate short message, and present the information content to the user, so that the user can learn the short message content. .

Optionally, in the embodiment of the present application, when the terminal device decrypts the short message and the decryption fails, the terminal device may hide or delete the short message.

Optionally, in the embodiment of the present application, the decryption failure refers to that the content obtained after decryption is used for The user may not be readable, that is, the content that failed to decrypt is some garbled meaningless.

For example, after the decryption, the information content obtained by the terminal device is “*&#@!!UU”, that is, when the garbled code is obtained, the terminal device can determine that the short message is an illegal short message, and may not present the short message to the user, SMS deletion or hiding.

Optionally, in the embodiment of the present application, when the terminal device decrypts the short message and fails to decrypt, the terminal device may send the short message to the server, so that the server can perform big data analysis, thereby assisting the government department to attack the pseudo base station. jobs.

For example, when the information content obtained by the terminal device is garbled after decryption, the terminal device can determine that the short message is an illegal short message, and the short message can be sent to the server, and the short message can be deleted after being sent.

Optionally, in the embodiment of the present application, when the terminal device decrypts the short message and the decryption fails, the terminal device may further prompt the user that the short message decryption fails.

Optionally, in the embodiment of the present application, after decrypting the short message, the terminal device may present the obtained content to the user, because the content obtained when the decryption fails is not readable by the user, so the user The legitimacy of the short message can be determined based on whether the content is readable.

Optionally, if the encryption algorithm is specified, the terminal device may decrypt the received short message according to the encryption algorithm and the short message key.

Therefore, in the embodiment of the present application, the terminal device needs to decrypt the received short message by using the short message key, and the SMSC corresponding to the terminal device needs to use the short message key to encrypt the short message to be sent to the terminal device. Therefore, the security of the short message received by the terminal device can be ensured, and the short message sent by the SMSC can be correctly decrypted, and the short message sent by the pseudo base station may be decrypted into a garbled code, so that the content after the decryption can indicate whether the short message is legal, thereby Reduce the impact of illegal SMS on users.

In addition, when the short message key is sent to the terminal device by the server, it is possible to avoid the problem that the terminal device cannot know whether the key sender is the SMSC or the pseudo base station when the SMSC sends the short message key to the terminal device; When the server or the SMSC generates the short message key, different short message keys can be set for each terminal device, thereby further improving security.

In order to facilitate a clearer understanding of the present application, the communication method of the embodiment of the present application will be described below in conjunction with the method 300 shown in FIG. 3 and the method 400 shown in FIG.

FIG. 3 is a schematic interaction diagram of a communication method 300 in accordance with an embodiment of the present application. In the communication method 300, the server is described as a cloud server.

In 301, the terminal device may send, to the cloud server, at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting.

In 302, the cloud server may determine, according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting, that the SMSC corresponding to the terminal device needs to send a message to the terminal device. Encrypt.

Optionally, the cloud server may determine an SMSC corresponding to the terminal device.

Optionally, the cloud server may determine whether a connection is established with the SMSC corresponding to the terminal device; if the connection is not established, the cloud server may newly establish a connection with the SMSC.

In 303, the cloud server can generate a short message key.

Optionally, the cloud server can specify an encryption algorithm.

In 304, the cloud server can send the short message key to the terminal device.

Optionally, when the cloud server specifies an encryption algorithm, the cloud server may send algorithm indication information for indicating an encryption algorithm to the terminal device.

In 305, the cloud server may send the short message key to the SMSC corresponding to the terminal device.

Optionally, when the cloud server specifies an encryption algorithm, the cloud server may send algorithm indication information for indicating an encryption algorithm to the SMSC.

In 306, when the SMSC needs to send a short message to the terminal device, the SMS message may be encrypted according to the short message key to obtain the first short message.

In 307, the SMSC sends the first short message to the terminal device.

In 308, the terminal device decrypts the first short message according to the short message key.

Optionally, if the encryption algorithm is specified, the terminal device may decrypt the first short message according to the encryption algorithm and the short message key.

Since the first short message is a short message sent by the SMSC corresponding to the terminal device, the first short message can be decrypted correctly, so that the user can know the short message content.

In 309, the pseudo base station sends a second short message to the terminal device.

In 310, the terminal device decrypts the second short message according to the short message key.

Since the second short message is a short message sent by the pseudo base station, the user cannot be decrypted normally, so that the user cannot know the short message content, so that the user can avoid being affected by the short message sent by the pseudo base station.

It should be understood that, in the embodiments of the present application, the size of the sequence numbers of the foregoing processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the embodiment of the present application. Form any limit.

It should be understood that the implementation of the steps in the communication method 300 in the embodiment of the present application in FIG. 3 may refer to the specific description in the communication method 200 according to the embodiment of the present application in FIG. 2, and details are not described herein for brevity.

In addition, the generation of the short message key by the cloud server can reduce the burden on the SMSC.

4 is a schematic interaction diagram of a communication method 400 in accordance with an embodiment of the present application. In the communication method 400, the server is described as a cloud server.

In 401, the terminal device may determine, according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting, that the SMSC corresponding to the terminal device needs to send a short message to the terminal device. Encrypt.

In 402, the terminal device may send first indication information to the cloud server, where the first indication information is used to indicate that the SMSC needs to encrypt the short message to be sent to the terminal device.

In 403, the cloud server may determine, according to the first indication information, that the SMSC needs to encrypt the short message to be sent to the terminal device.

In 404, the cloud server may send a notification message to the SMSC corresponding to the terminal device, where the notification message is used to notify the SMSC to send the short message key to the cloud server.

In 405, the SMSC can generate a short message key.

Optionally, the SMSC can specify an encryption algorithm.

In 406, the SMSC can send the short message key to the cloud server.

Optionally, when the SMSC specifies an encryption algorithm, the SMSC may send the cloud server to the cloud server. An algorithm indication information for indicating an encryption algorithm is sent.

In 407, the cloud server can send the short message key to the terminal device.

Optionally, when the cloud server receives the algorithm indication information, the cloud server may send the algorithm indication information to the terminal device.

The execution process of 408 to 412 is the same as the execution process of 306 to 310 in the communication method 300 shown in FIG. 3, and details are not described herein again.

It should be understood that the implementation of the steps in the communication method 400 in the embodiment of the present application in FIG. 4 may be referred to the specific description in the communication method 200 according to the embodiment of the present application in FIG. 2, and details are not described herein for brevity.

It should also be understood that the communication method 300 according to the embodiment of the present application in FIG. 3 and the communication method 400 according to the embodiment of the present application in FIG. 4 are not completely independent, and features directly belonging to different methods may be combined with each other.

In addition, generating a short message key by the SMSC can give the SMSC the freedom to allocate the short message key.

The communication method according to the embodiment of the present application is described in detail above with reference to FIG. 2 to FIG. 4, and the terminal device, the SMSC, and the server according to the embodiment of the present application will be described in detail below with reference to FIG. 5 to FIG.

FIG. 5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application. As shown in FIG. 5, the terminal device 500 includes:

The receiving module 501 is configured to receive a short message key sent by a server accessed by the terminal device;

The decryption module 502 is configured to decrypt the short message according to the short message key when the receiving module receives the short message.

Therefore, in the embodiment of the present application, the terminal device needs to decrypt the received short message by using the short message key, and the SMSC corresponding to the terminal device needs to use the short message key to encrypt the short message to be sent to the terminal device. Therefore, the security of the short message received by the terminal device can be ensured, and the short message sent by the SMSC short message service center can be correctly decrypted, and the short message sent by the pseudo base station may be decrypted into garbled code, so that the content after the decryption can indicate the Whether the SMS is legal, thus reducing the impact of illegal SMS on the user.

In addition, the terminal device receives the short message key sent by the server, and can prevent the short message service center from sending the short message key to the terminal device, and the terminal device cannot know whether the key sender is the short message service center or The problem with the pseudo base station.

Optionally, in the embodiment of the present application, the terminal device further includes a processing module, configured to hide or delete the short message; and/or a first sending module, configured to send the short message to the server.

Optionally, in the embodiment of the present application, the terminal device further includes a determining module, configured to determine, according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting, the terminal device Whether the corresponding SMSC needs to encrypt the short message sent to the terminal device;

a second sending module, configured to send, to the server, first indication information, when the SMSC needs to encrypt the short message to be sent to the terminal device, where the first indication information is used to indicate that the SMSC needs to be sent to the terminal device The text message is encrypted.

Optionally, in the embodiment of the present application, the terminal device further includes a third sending module, configured to send, to the server, at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting;

The receiving module 501 is specifically configured to receive the short message key, where the short message key is determined by the server according to at least one of a type of a network to which the terminal device is attached, a location of the terminal device, and the user setting. It is sent when the SMS sent to the terminal device is encrypted.

Optionally, in the embodiment of the present application, the receiving module 501 is further configured to receive algorithm indication information that is sent by the server and used to indicate an encryption algorithm. The receiving module is further configured to determine the encryption algorithm indicated by the algorithm indication information. The decryption module 502 is further configured to decrypt the short message according to the short message key and the encryption algorithm.

It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the terminal device 500 respectively In order to implement the corresponding processes of the respective methods in FIG. 2 to FIG. 4, for brevity, details are not described herein again.

FIG. 6 is a schematic block diagram of an SMSC 600 in accordance with an embodiment of the present application. As shown in FIG. 6, the SMSC 600 includes:

The encryption module 601 is configured to encrypt the short message to be sent to the terminal device according to the short message key corresponding to the terminal device;

The sending module 602 is configured to send the short message encrypted by the encryption module to the terminal device.

Therefore, in the embodiment of the present application, the terminal device needs to decrypt the received short message by using the short message key, and the SMSC corresponding to the terminal device needs to use the short message key to encrypt the short message to be sent to the terminal device. Therefore, the security of the short message received by the terminal device can be ensured, and the short message sent by the SMSC can be correctly decrypted, and the short message sent by the pseudo base station may be decrypted into garbled code, so that the content after the decryption can indicate whether the short message is legal. Thereby reducing the impact of illegal text messages on users.

Optionally, in the embodiment of the present application, the SMSC 600 further includes a first receiving module, configured to receive a notification message sent by the server accessed by the terminal device, where the notification message is used to notify the SMSC to send the short message to the server. An information key; a generating module, configured to generate the short message key; the sending module 602 is further configured to send the short message key to the server.

Optionally, in the embodiment of the present application, the SMSC 600 further includes a second receiving module, configured to receive the short message key sent by the server accessed by the terminal device.

Optionally, in the embodiment of the present application, the SMSC 600 further includes a connection module, configured to establish a connection with the server.

Optionally, in the embodiment of the present application, the SMSC 600 further includes a third receiving module, configured to receive algorithm indication information that is sent by the server that is accessed by the terminal device to indicate an encryption algorithm, and the third receiving module further uses The encryption algorithm indicated by the algorithm indication information is determined; the encryption module 601 is further configured to encrypt the short message according to the short information key and the encryption algorithm.

Optionally, in the embodiment of the present application, the SMSC 600 further includes a determining module, configured to determine an encryption algorithm, where the sending module 602 is further configured to send, to the terminal device, the algorithm indication information used to indicate the encryption algorithm. The encryption module 601 is further configured to encrypt the short message according to the short message key and the encryption algorithm.

It should be understood that the SMSC 600 according to the embodiment of the present application may correspond to the SMSC in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the SMSC 600 are respectively implemented to implement the respective methods in FIG. 2 to FIG. The process, for the sake of brevity, will not be described here.

FIG. 7 is a schematic block diagram of a server 700 in accordance with an embodiment of the present application. As shown in FIG. 7, the server 700 includes:

a generating module 701, configured to generate a short message key;

The sending module 702 is configured to send the short message key to the terminal device that has accessed the server and the short message service center SMSC corresponding to the terminal device, where the short message key is used by the terminal device to receive The short message is decrypted, and the short message for the SMSC to be sent to the terminal device is encrypted.

In addition, when the short message key is sent to the terminal device by the server, and the short message service center can be prevented from transmitting the short message key to the terminal device, the terminal device cannot know whether the key sender is a short message service center or a fake. The problem of the base station; and, when the server generates the short message key, a different short message key can be set for each terminal device, thereby further improving security.

Optionally, in the embodiment of the present application, the server 700 further includes a first determining module, configured to: according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting, or according to the The encryption indication information sent by the terminal device determines whether the SMSC needs to encrypt the short message to be sent to the terminal device; the generating module 701 is specifically configured to: when determining that the SMSC needs to encrypt the short message to be sent to the terminal device, generate the Short message key.

Optionally, in the embodiment of the present application, the server 700 further includes a second determining module, configured to determine the SMSC corresponding to the terminal device, and a connection module, configured to establish a new connection with the SMSC.

Optionally, the second determining module is specifically configured to determine, according to the phone number segment uploaded by the terminal device, the SMSC corresponding to the terminal device.

Optionally, in the embodiment of the present application, the server 700 further includes a third determining module, configured to determine an encryption algorithm, where the encryption algorithm is used by the terminal device to decrypt the received short message according to the short message key. And an encryption algorithm required by the SMSC to encrypt the short message to be sent to the terminal device according to the short message key; the sending module 702 is further configured to send the algorithm indication information used to indicate the encryption algorithm to the terminal device And the SMSC.

Optionally, in the embodiment of the present application, the server 700 further includes a receiving module, configured to receive algorithm indication information that is sent by the SMSC to indicate an encryption algorithm, where the algorithm indication information is used to indicate that the terminal device is according to the short The encryption algorithm used by the information key to decrypt the received short message; the sending module 702 is further configured to send the algorithm indication information to the terminal device.

Optionally, in the embodiment of the present application, the server 700 is a cloud server.

It should be understood that the server 700 according to the embodiment of the present application may correspond to the server in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the server 700 respectively implement the respective methods in FIG. 2 to FIG. The corresponding process, for the sake of brevity, will not be described here.

FIG. 8 is a schematic structural diagram of a terminal device 800 according to an embodiment of the present application. As shown in FIG. 8, the terminal device 800 includes a processor 801, a memory 802, a transceiver 803, and a bus system 804. The processor 801, the memory 802, and the transceiver 803 are connected by a bus system 804, wherein the memory 802 For storing instructions, the processor 801 is configured to execute instructions stored in the memory, and the transceiver 803 is configured to receive and transmit information.

The transceiver 803 is configured to receive a short message key sent by a server accessed by the terminal device;

The processor 801 is configured to decrypt the short message according to the short message key when the receiving module receives the short message.

It should be understood that the terminal device 800 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the terminal device 800 are respectively implemented in FIG. 2 to FIG. 4 . The corresponding processes of the various methods are not repeated here for the sake of brevity.

FIG. 9 is a schematic structural diagram of an SMSC 900 according to an embodiment of the present application. As shown in FIG. 9, the SMSC 900 includes a processor 901, a memory 902, a transceiver 903, and a bus system 904. The processor 901, the memory 902, and the transceiver 903 are connected by a bus system 904, wherein the memory 902 is used for The instructions are stored by the processor 901 for executing instructions stored in the memory, and the transceiver 903 is configured to receive and transmit information.

The processor 901 is configured to encrypt a short message to be sent to the terminal device according to the short information key corresponding to the terminal device;

The transceiver 903 is configured to send the short message encrypted by the encryption module to the terminal device.

It should be understood that the SMSC 900 according to the embodiment of the present application may correspond to the SMSC in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the SMSC 900 are respectively implemented to implement the respective methods in FIG. 2 to FIG. The process, for the sake of brevity, will not be described here.

FIG. 10 is a schematic structural diagram of a server 1000 according to an embodiment of the present application. As shown in FIG. 10, the server 1000 includes a processor 1001, a memory 1002, a transceiver 1003, and a bus system 1004. The processor 1001, the memory 1002, and the transceiver 1003 are connected by a bus system 1004, wherein the memory 1002 is used. For storing instructions, the processor 1001 is configured to execute instructions stored in the memory, and the transceiver 1003 is configured to receive and transmit information.

The processor 1001 is configured to generate a short message key;

The transceiver 1003 is configured to send the short message key to a terminal device that has accessed the server and a short message service center corresponding to the terminal device, where the short message key is used by the terminal device to receive the The short message is decrypted, and the short message service center encrypts the short message to be sent to the terminal device.

It should be understood that the server 1000 according to the embodiment of the present application may correspond to the server in the embodiment of the present application, and the foregoing and other operations and/or functions of the respective modules in the server 1000 respectively implement the respective methods in FIG. 2 to FIG. The corresponding process, for the sake of brevity, will not be described here.

In this embodiment, the processor may be a Central Processing Unit ("CPU"), a Network Processor ("NP"), or a combination of a CPU and an NP. The processor may further include a hardware chip. The hardware chip may be an Application-Specific Integrated Circuit ("ASIC"), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a Field-Programmable Gate Array (FPGA), and a Generic Array Logic (Generic Array Logic). Referred to as "GAL" or any combination thereof.

The memory can be either volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, abbreviated as "ROM"), a programmable read only memory (Programmable ROM, abbreviated as "PROM"), and an erasable programmable read only memory ( Erasable PROM (abbreviated as "EPROM"), electrically erasable programmable read only memory ("EEPROM") or flash memory. The volatile memory may be a Random Access Memory (RAM), which is used as an external cache.

The bus system may include a power bus, a control bus, and a status signal bus in addition to the data bus. For the sake of convenience, only one thick line is used to indicate the bus system, but it does not mean There is only one bus or one type of bus.

The embodiment of the present application provides a computer readable medium for storing a computer program, where the computer program includes a communication method for performing the foregoing embodiments of the present application in FIGS. 2 to 4. The readable medium may be a ROM or a RAM, which is not limited in this embodiment of the present application.

It should be understood that the terms "and/or" and "at least one of A or B" herein are merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, Representation: There are three cases where A exists separately, A and B exist at the same time, and B exists separately. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The function is implemented in the form of a software functional unit and sold or made as a standalone product When used, it can be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory, a random access memory, a magnetic disk, or an optical disk.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A communication method, comprising:

Receiving, by the terminal device, a short message key sent by a server accessed by the terminal device;

When receiving the short message, the terminal device decrypts the short message according to the short message key.
The method according to claim 1, wherein when the terminal device decrypts the short message according to the short message key and the decryption fails, the method further includes:

The terminal device hides or deletes the short message; and/or

The terminal device sends the short message to the server.
The method according to claim 1 or 2, wherein before the terminal device receives the short message key sent by the server accessed by the terminal device, the method further includes:

Determining, by the terminal device, according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting, whether the short message service center SMSC corresponding to the terminal device needs to be sent to the The short message of the terminal device is encrypted;

When determining that the SMSC needs to encrypt the short message to be sent to the terminal device, the terminal device sends the first indication information to the server, where the first indication information is used to indicate that the SMSC needs to be sent to the The short message of the terminal device is encrypted.
The method according to claim 1 or 2, wherein before the terminal device receives the short message key sent by the server accessed by the terminal device, the method further includes:

Transmitting, by the terminal device, at least one of a type of a network to which the terminal device is attached, a location of the terminal device, and a user setting to the server;

The terminal device receives the short message key sent by the server accessed by the terminal device, including:

Receiving, by the terminal device, the short message key, where the short message key is at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and the user setting. Determining that the SMSC needs to be encrypted when the short message to be sent to the terminal device is encrypted.
The method according to any one of claims 1 to 4, further comprising:

Receiving, by the terminal device, algorithm indication information that is sent by the server and used to indicate an encryption algorithm;

Determining, by the terminal device, the encryption algorithm indicated by the algorithm indication information;

The terminal device decrypts the short message according to the short message key when receiving the short message, including:

The terminal device decrypts the short message according to the short message key and the encryption algorithm.
A communication method, comprising:

The short message service center SMSC encrypts the short message to be sent to the terminal device according to the short message key corresponding to the terminal device;

The SMSC sends the encrypted short message to the terminal device.
The method of claim 6 wherein the method further comprises:

Receiving, by the SMSC, a notification message sent by the server that is accessed by the terminal device, where the notification message is used to notify the SMSC to send the short message key to the server;

The SMSC generates the short message key;

The SMSC sends the short message key to the server.
The method of claim 6 wherein the method further comprises:

The SMSC receives the short message key sent by a server accessed by the terminal device.
The method according to claim 7 or 8, wherein before the information transmission between the SMSC and the server, the method further comprises:

The SMSC establishes a connection with the server.
The method according to any one of claims 6 to 9, wherein the method further comprises:

The SMSC receives algorithm indication information sent by a server accessed by the terminal device to indicate an encryption algorithm;

The SMSC determines the encryption algorithm indicated by the algorithm indication information;

The SMSC encrypts the short message to be sent to the terminal device according to the short information key corresponding to the terminal device, including:

The SMSC encrypts the short message according to the short message key and the encryption algorithm.
The method according to any one of claims 6 to 9, wherein the method further comprises:

The SMSC determines an encryption algorithm;

The SMSC sends algorithm indication information for indicating the encryption algorithm to the server;

The SMSC encrypts the short message to be sent to the terminal device according to the short information key corresponding to the terminal device, including:

The SMSC encrypts the short message according to the short message key and the encryption algorithm.
A communication method, comprising:

The server generates a short message key;

Sending, by the server, the short message key to the terminal device that has accessed the server and the short message service center SMSC corresponding to the terminal device, where the short message key is used by the terminal device pair The received short message is decrypted, and the short message for the SMSC to be sent to the terminal device is encrypted.
The method according to claim 12, wherein before the server generates the short message key, the method further comprises:

Determining, by the server, whether the SMSC needs to be sent to the SMSC according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting, or according to the encryption indication information sent by the terminal device. The short message of the terminal device is encrypted;

The server generates a short message key, including:

The server generates the short message key when it is determined that the SMSC needs to encrypt the short message to be sent to the terminal device.
The method according to claim 12 or 13, wherein before the server sends the short message key to the terminal device that has accessed the server and the SMSC corresponding to the terminal device, The method also includes:

The server determines the SMSC corresponding to the terminal device;

The server newly establishes a connection with the SMSC.
The method according to claim 14, wherein the determining, by the server, the SMSC corresponding to the terminal device comprises:

The server determines, according to the phone number segment uploaded by the terminal device, the SMSC corresponding to the terminal device.
The method according to any one of claims 12 to 15, wherein the method further comprises:

Determining, by the server, an encryption algorithm, when the terminal device decrypts the received short message according to the short information key, and the SMSC is to be sent according to the short information key to the The encryption algorithm required for the short message of the terminal device to be encrypted;

The server sends algorithm indication information for indicating the encryption algorithm to the terminal device and the SMSC.
The method according to any one of claims 12 to 15, wherein the method further comprises:

The server receives the algorithm indication information that is sent by the SMSC to indicate an encryption algorithm, where the algorithm indication information is used to indicate that the terminal device needs to use the decryption of the received short message according to the short information key. Encryption Algorithm;

The server sends the algorithm indication information to the terminal device.
The method according to any one of claims 12 to 17, wherein the server is a cloud server.
A terminal device, comprising:

a receiving module, configured to receive a short message key sent by a server accessed by the terminal device;

And a decryption module, configured to decrypt the short message according to the short message key when the receiving module receives the short message.
The terminal device according to claim 19, wherein the terminal device further comprises:

a processing module for hiding or deleting the short message; and/or

The first sending module is configured to send the short message to the server.
The terminal device according to claim 19 or 20, wherein the terminal device further comprises:

a determining module, configured to determine, according to at least one of a type of the network to which the terminal device is attached, a location of the terminal device, and a user setting, whether the short message service center SMSC corresponding to the terminal device needs to be sent to the office The short message of the terminal device is to be encrypted;

a second sending module, configured to send, to the server, first indication information, when the SMSC needs to encrypt the short message to be sent to the terminal device, where the first indication information is used to indicate that the SMSC needs to be treated The short message sent to the terminal device is encrypted.
The terminal device according to claim 19 or 20, wherein the terminal device further comprises:

a third sending module, configured to send, to the server, at least one of a type of a network to which the terminal device is attached, a location of the terminal device, and a user setting;

The receiving module is specifically configured to receive the short information key, where the short information key is in a type according to a network to which the terminal device is attached, a location of the terminal device, and the user setting. At least one of determining that the SMSC needs to encrypt a short message to be sent to the terminal device.
The terminal device according to any one of claims 19 to 22, wherein the receiving module is further configured to receive algorithm indication information sent by the server for indicating an encryption algorithm;

The receiving module is further configured to determine the encryption algorithm indicated by the algorithm indication information;

The decryption module is further configured to decrypt the short message according to the short message key and the encryption algorithm.
A short message service center SMSC, comprising:

The encryption module is configured to encrypt the short message to be sent to the terminal device according to the short message key corresponding to the terminal device;

And a sending module, configured to send the short message encrypted by the encryption module to the terminal device.
The SMSC according to claim 24, wherein the SMSC further comprises:

a first receiving module, configured to receive a notification message sent by a server that is accessed by the terminal device, where the notification message is used to notify the SMSC to send the short message key to the server;

Generating a module, configured to generate the short message key;

The sending module is further configured to send the short message key to the server.
The SMSC according to claim 24, wherein the SMSC further comprises:

The second receiving module is configured to receive the short message key sent by the server accessed by the terminal device.
The SMSC according to claim 25 or 26, wherein the SMSC further comprises:

a connection module for establishing a connection with the server.
The SMSC according to any one of claims 24 to 27, wherein the SMSC further comprises:

a third receiving module, configured to receive, by the server accessed by the terminal device, an indication Algorithm indicating information of the encryption algorithm;

The third receiving module is further configured to determine the encryption algorithm indicated by the algorithm indication information;

The encryption module is further configured to encrypt the short message according to the short message key and the encryption algorithm.
The SMSC according to any one of claims 24 to 27, wherein the SMSC further comprises:

a determining module for determining an encryption algorithm;

The sending module is further configured to send algorithm indication information used to indicate the encryption algorithm to a server accessed by the terminal device;

The encryption module is further configured to encrypt the short message according to the short message key and the encryption algorithm.
A server, comprising:

a generating module for generating a short message key;

a sending module, configured to send the short message key to a terminal device that has accessed the server and a short message service center SMSC corresponding to the terminal device, where the short message key is used for the terminal The device decrypts the received short message and encrypts the short message to be sent to the terminal device by the SMSC.
The server according to claim 30, wherein the server further comprises:

a first determining module, configured to determine, according to at least one of a type of a network to which the terminal device is attached, a location of the terminal device, and a user setting, or according to the encryption indication information sent by the terminal device, whether the SMSC is The message to be sent to the terminal device needs to be encrypted;

The generating module is specifically configured to generate the short message key when determining that the SMSC needs to encrypt the short message to be sent to the terminal device.
The server according to claim 30 or 31, wherein the server further comprises:

a second determining module, configured to determine the SMSC corresponding to the terminal device;

a connection module, configured to newly establish a connection with the SMSC.
The server according to claim 32, wherein the second determining module is specifically configured to determine the SMSC corresponding to the terminal device according to a phone number segment uploaded by the terminal device.
The server according to any one of claims 30 to 33, wherein the server further comprises:

a third determining module, configured to determine an encryption algorithm, when the terminal device decrypts the received short message according to the short information key, and the SMSC is treated according to the short information key An encryption algorithm required for encrypting a short message sent to the terminal device;

The sending module is further configured to send algorithm indication information for indicating the encryption algorithm to the terminal device and the SMSC.
The server according to any one of claims 30 to 33, wherein the server further comprises:

a receiving module, configured to receive algorithm indication information that is sent by the SMSC to indicate an encryption algorithm, where the algorithm indication information is used to indicate that the terminal device needs to decrypt the received short message according to the short information key. The encryption algorithm used;

The sending module is further configured to send the algorithm indication information to the terminal device.
The server according to any one of claims 30 to 35, wherein the server is a cloud server.