Secure payment method, terminal, server and payment system

By using the first identification code to encrypt payment information and status feature information in the RCS session between the mobile payment terminal and the server, the problem of weak mobile payment security is solved, and higher payment security and user experience is achieved.

CN112418852BActive Publication Date: 2024-11-19ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201910785834.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-08-23
Publication Date
2024-11-19
Estimated Expiration
2039-08-23

AI Technical Summary

Technical Problem

The existing mobile payment methods have weak payment security, and terminals are vulnerable to attacks by criminals during the payment process, affecting the user experience.

Method used

By establishing an RCS session between the terminal and the server, the payment information and status feature information are formed using the first identification code to form encrypted information, and the payment operation is performed only after the server is verified and passed, ensuring information security.

Benefits of technology

It effectively avoids users being deceived during payment or transfer, and improves payment security and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112418852B_ABST
    Figure CN112418852B_ABST
Patent Text Reader

Abstract

The present application discloses a secure payment method, terminal, server and payment system. The secure payment method includes: obtaining a first identification code based on an RCS session, then using the first identification code to encrypt state feature information or a combination of state feature information and payment information, and sending confirmation information of the payment request when the decrypted state feature information is verified to be correct, thereby realizing a secure payment process. In the embodiment of the present application, since the unique first identification code in the RCS session is used for encryption operations, and only the server can perform the corresponding decryption and verification operations, it is possible to prevent users from being deceived during the payment or transfer process, thereby improving the payment security of users and improving the user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to but are not limited to the field of communication technology, and in particular, to a secure payment method, terminal, server, payment system and computer-readable storage medium. Background Art

[0002] With the popularity of mobile payment, more and more users are accustomed to using terminals to make payments and transfers. At present, if a terminal is to realize mobile payment, it only needs to meet the following functions: 1. It can connect to the network to download payment orders, upload user bank card information, and interact with the payment platform; 2. It can send and receive text messages or calls to receive identity verification passwords.

[0003] However, the above functions of the terminal all have loopholes that criminals can exploit, which will threaten the payment security of users and affect their usage experience. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] On the first aspect, the embodiments of the present application provide a secure payment method, terminal, server, payment system and computer-readable storage medium, which can improve the user's payment security and thus improve the user's usage experience.

[0006] In a second aspect, an embodiment of the present application provides a secure payment method, which is applied to a terminal, including:

[0007] Initiate a payment request;

[0008] Establishing an RCS session with a server, and obtaining a first identification code in the RCS session;

[0009] Obtain payment information and status characteristic information;

[0010] Based on the first identification code, the payment information and the status characteristic information are converted into encrypted information;

[0011] Sending the encrypted information to a server;

[0012] Obtaining confirmed payment information corresponding to the payment information;

[0013] Send confirmation information corresponding to the confirmed payment information to the server, complete the payment, and exit the RCS session.

[0014] In a third aspect, the embodiment of the present application further provides a secure payment method, which is applied to a server and includes:

[0015] Establishing an RCS session with a terminal, and obtaining a first identification code in the RCS session;

[0016] Acquire encrypted information formed based on the first identification code, the payment information and the status characteristic information;

[0017] restoring the encrypted information to the payment information and the status characteristic information using the first identification code;

[0018] Verifying the status characteristic information, and when the verification is correct, sending the payment information to a clearing center;

[0019] Obtaining confirmation information corresponding to the payment information;

[0020] The verification confirmation information is sent to the clearing house to complete the payment and exit the RCS session.

[0021] In a fourth aspect, the present application also provides a secure payment method, which is applied to a payment system, including:

[0022] The terminal initiates a payment request;

[0023] The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session;

[0024] The terminal obtains payment information and status characteristic information;

[0025] The terminal converts the payment information and the status characteristic information into encrypted information based on the first identification code, and sends the encrypted information to the server;

[0026] The server obtains the encrypted information, and uses the first identification code to restore the encrypted information into the payment information and the status characteristic information;

[0027] The server verifies the status characteristic information, and when the verification is correct, sends the payment information to the clearing center;

[0028] The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server;

[0029] The server obtains the confirmation information and sends the confirmed information to the clearing house;

[0030] The terminal completes the payment and exits the RCS session with the server.

[0031] In a fifth aspect, an embodiment of the present application further provides a terminal, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the secure payment method of the second aspect described above is implemented.

[0032] In a sixth aspect, an embodiment of the present application further provides a server, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the secure payment method as described in the third aspect above is implemented.

[0033] In a seventh aspect, an embodiment of the present application further provides a payment system, including a terminal and a server, wherein when the terminal initiates a payment request:

[0034] The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session;

[0035] The terminal obtains payment information and status characteristic information;

[0036] The terminal converts the payment information and the status characteristic information into encrypted information based on the first identification code, and sends the encrypted information to the server;

[0037] The server obtains the encrypted information, and uses the first identification code to restore the encrypted information into the payment information and the status characteristic information;

[0038] The server verifies the status characteristic information, and when the verification is correct, sends the payment information to the clearing center;

[0039] The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server;

[0040] The server obtains the confirmation information and sends the confirmed information to the clearing center after verification;

[0041] The terminal completes the payment and exits the RCS session with the server.

[0042] In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the secure payment method as described above.

[0043] The embodiment of the present application includes: the terminal interacts with the server based on the RCS session, and when the terminal sends the payment information to realize the payment, the terminal first uses the first identification code in the RCS session to form the payment information and the state characteristic information into encrypted information, and then sends the encrypted information as an RCS message; when the server receives the encrypted information, the first identification code is used to restore the encrypted information to the payment information and the state characteristic information, and when the state characteristic information is verified to be correct, the server will send the payment information to the clearing center, for example, to the bank or the third-party payment platform, so that the bank or the third-party payment platform can realize the payment or transfer processing. According to the scheme provided by the embodiment of the present application, when the user uses the terminal to send the payment information, the state characteristic information and the payment information of the terminal will be encrypted by the first identification code, and only when the server restores the state characteristic information and the payment information of the terminal, and when the state characteristic information is verified to be correct, the subsequent payment operation is realized, so that the user can be prevented from being deceived during the payment or transfer process, thereby improving the payment security of the user and improving the user's experience.

[0044] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings are used to provide further understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0046] Figure 1 It is a schematic diagram of a framework of a system structure platform for executing a secure payment method provided by an embodiment of the present application;

[0047] Figure 2 is a flow chart of a secure payment method applied to a terminal provided by an embodiment of the present application;

[0048] Figure 3 is a flow chart of forming encrypted information in a secure payment method applied to a terminal provided by another embodiment of the present application;

[0049] Figure 4 is a flow chart of encryption status characteristic information in a secure payment method applied to a terminal provided by another embodiment of the present application;

[0050] Figure 5 is a flow chart of a secure payment method applied to a server provided by an embodiment of the present application;

[0051] Figure 6 is a flowchart of restoring information in a secure payment method applied to a server provided in another embodiment of the present application;

[0052] Figure 7 is a flow chart of decrypting state characteristic information in a secure payment method applied to a server provided by another embodiment of the present application;

[0053] Figure 8 is a schematic diagram of a terminal provided by an embodiment of the present application;

[0054] Fig. 9 It is a schematic diagram of a server provided in one embodiment of the present application. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0056] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0057] With the popularity of mobile payment, more and more users are accustomed to using terminals to make payments and transfers. At present, if a terminal is to realize mobile payment, it only needs to meet the following functions: 1. It can connect to the network to download payment orders, upload user bank card information, and interact with the payment platform; 2. It can send and receive text messages or calls to receive identity verification passwords.

[0058] However, the above functions of the terminal have loopholes that criminals can exploit. For example, in most payment scenarios, wireless networks are required, but there is currently no technology that can identify fake base stations during the payment process; for example, when users use the terminal to download payment orders, upload user bank card information, or interact with the payment platform, they may be eavesdropped and the merchant information may be replaced; for example, the terminal receives authentication passwords through SMS or phone calls, which may be monitored and used for illegal payments. Therefore, the existing mobile payment methods have the possibility of payment security being threatened, thus affecting the user experience.

[0059] Based on this, the present application provides a secure payment method, terminal, server, payment system and computer-readable storage medium. The terminal uses the first identification code in the RCS (Rich Communication Suite) session to form payment information and status feature information into encrypted information, and uses RCS messages to send the encrypted information. The payment operation is only implemented when the server recovers the terminal's status feature information and payment information, and when the status feature information is verified to be correct, thereby preventing users from being deceived during the payment or transfer process, thereby improving the user's payment security and improving the user's usage experience.

[0060] The embodiments of the present application are further described below in conjunction with the accompanying drawings.

[0061] like Figure 1 As shown, Figure 1 It is a schematic diagram of the framework of a system structure platform for executing a secure payment method provided by an embodiment of the present application.

[0062] like Figure 1 As shown, the system structure platform 100 includes a terminal 110 and a server 120. The terminal 110 includes a terminal memory 111 and a terminal processor 112. The server 120 includes a service memory 121 and a service processor 122. The terminal memory 111 and the terminal processor 112 can be connected via a bus or other means. Figure 1 The service memory 121 and the service processor 122 may be connected via a bus or other means. Figure 1 The example of connecting through bus is taken in the following.

[0063] In addition, if Figure 1 As shown, the terminal processor 112 in the terminal 110 is constructed with an RCS client 113, and the RCS client 113 is provided with a security information generation module 114 for using a first identification code to form encrypted information from payment information and status characteristic information; the service processor 122 in the server 120 is constructed with an RCS server 123, and the RCS server 123 is provided with a security information checking module 124 for using the first identification code to restore the encrypted information to payment information and status characteristic information.

[0064] When the terminal 110 performs a payment operation, the terminal 110 has the following features and capabilities:

[0065] 1. The MSISDN (Mobile Station International Subscriber Directory Number) of the terminal 110 has been registered with a bank or a third-party payment platform;

[0066] 2. The terminal 110 has and has enabled the RCS service function;

[0067] 3. The terminal 110 and the server 120 have established an IMS PDN (IP Multimedia Subsystem Packet Data Network) connection bearer, or the terminal 110 has been connected to a valid hotspot, established an IPsec (Internet Protocol Security) tunnel and established an IMS PDN connection with the server 120 over the tunnel.

[0068] When the terminal 110 performs a payment operation, an RCS session is established among the terminal 110, the server 120 and the clearing center, and MSRP (Message Session Relay Protocol) channels are established between the terminal 110 and the server 120, between the terminal 110 and the clearing center, and between the server 120 and the clearing center to send and receive RCS messages. The clearing center can be a bank or a third-party payment platform.

[0069] Those skilled in the art will appreciate that the terminal 110 may be any type of intelligent terminal, such as a smart phone, a tablet computer, or other handheld mobile devices.

[0070] The terminal memory 111 and the service memory 121 are respectively used as a non-transient computer-readable storage medium, which can be used to store non-transient software programs and non-transient computer executable programs. In addition, the terminal memory 111 and the service memory 121 may include high-speed random access memory, and may also include non-transient memory, such as at least one disk storage device, flash memory device, or other non-transient solid-state storage device. In some embodiments, the terminal memory 111 may optionally include a memory remotely arranged relative to the terminal processor 112, and these remote memories may be connected to the terminal 110 via a network. In other embodiments, the service memory 121 may optionally include a memory remotely arranged relative to the service processor 122, and these remote memories may be connected to the server 120 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0071] Those skilled in the art will understand that Figure 1 The device structure shown in the figure does not constitute a limitation on the system structure platform 100, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0072] exist Figure 1 In the system structure platform 100 shown, the terminal processor 112 in the terminal 110 can be used to call the payment control program stored in the terminal memory 111, and the service processor 122 in the server 120 can be used to call the payment control program stored in the service memory 121, and the two cooperate with each other to perform the following steps:

[0073] The terminal initiates a payment request;

[0074] The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session;

[0075] The terminal obtains payment information and status characteristic information;

[0076] The terminal converts the payment information and the status characteristic information into encrypted information based on the first identification code, and sends the encrypted information to the server;

[0077] The server obtains the encrypted information and uses the first identification code to restore the encrypted information into payment information and status characteristic information;

[0078] The server verifies the status characteristic information and sends the payment information to the clearing center if the verification is correct;

[0079] The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server;

[0080] The server obtains the confirmation information and sends the verified confirmation information to the clearing house;

[0081] The terminal completes the payment and exits the RCS session with the server.

[0082] Furthermore, the status characteristic information includes but is not limited to at least one of the following:

[0083] Cell ID information and cell frequency information;

[0084] Cell ID information, IMSI (International Mobile Subscriber Identification) information and GPS coordinate information;

[0085] Contact list information at the current time point and subscription status;

[0086] Photo information.

[0087] Based on the above system structure platform 100, various embodiments of the secure payment method of the present application are proposed.

[0088] like Figure 2 As shown, Figure 2 This is a flowchart of a secure payment method applied to a terminal provided by an embodiment of the present application. The secure payment method includes but is not limited to the following steps:

[0089] Step S100, initiating a payment request.

[0090] In one embodiment, when a user uses a terminal to obtain a payment order sent by a merchant through the Internet, if the user confirms that the payment order is authentic, the user can confirm the payment order on the terminal, so that the terminal sends a payment request corresponding to the payment order to the clearing center. After the terminal initiates the payment request, the terminal will perform subsequent operations to realize the user's safe shopping payment behavior.

[0091] Those skilled in the art can understand that the payment request in step S100 of this embodiment should not be limited to a shopping payment request between a user and a merchant, but can also be a transfer payment request between two users. As long as it is a payment request generated based on a transaction between two parties, it should belong to the payment request in step S100 of this embodiment.

[0092] Step S200: Establish an RCS session with the server and obtain a first identification code in the RCS session.

[0093] In one embodiment, when the terminal initiates a payment request, the terminal will open the RCS client and establish an RCS session with the server. In addition, in order to achieve secure payment operations, an RCS session can be established between the terminal, the server and the clearing center. First, the terminal sends a session invitation message to the clearing center through the server, and then, when the terminal receives the session confirmation message, an RCS session is established between the terminal, the server and the clearing center. After the RCS session is established, the terminal can obtain the first identification code according to the RCS session, so as to facilitate the subsequent encryption operations.

[0094] In one embodiment, each RCS session has a unique first identification code, which appears in a SIP (Session Initiation Protocol) invitation message during the process of creating the RCS session and exists in subsequent response messages and session end messages.

[0095] In one embodiment, the first identification code may be implemented in different ways, for example, the first identification code may be a call ID in an RCS session, or a Dialog tag ID in an RCS session. Wherein, the call ID is a unique session identifier in an RCS session, and the Dialog tag ID is a unique target identifier in an RCS session. The first identification code may be selected according to actual usage. In this embodiment, the first identification code is preferably a Dialog tag ID in an RCS session.

[0096] Step S300, obtaining payment information and status characteristic information.

[0097] In one embodiment, when a user sends a payment request using a terminal according to an acquired payment order, in order to prevent the user from being affected by a fake base station, Trojan virus, fraudulent website or phishing website and causing property loss, step S300 in this embodiment will first obtain payment information and status characteristic information, and in subsequent steps, use the first identification code for encryption processing, thereby ensuring the security of the user during the transaction and achieving the purpose of improving the user experience.

[0098] In one embodiment, the payment information includes but is not limited to the merchant account number, the payment amount, and the user's bank card information filled in by the user. The status feature information includes but is not limited to the following combinations: cell ID information and cell frequency information; cell ID information, IMSI information, and GPS coordinate information; contact list information of the current time point and subscribing status; and photo information.

[0099] Step S400, forming encrypted information from payment information and status characteristic information based on the first identification code.

[0100] In one embodiment, payment information and status characteristic information are formed into encrypted information based on the first identification code, so that the status characteristic information that is highly relevant to the user can be kept confidential, which not only facilitates subsequent server identity authentication processing, but also prevents information from being stolen, thereby ensuring the security of the information.

[0101] In one embodiment, there are multiple implementation methods for forming encrypted information from payment information and status characteristic information based on the first identification code. For example, the status characteristic information may be encrypted using the first identification code first, and then the encrypted status characteristic information and payment information may be combined into encrypted information by splicing them head to tail; for another example, the payment information and status characteristic information may be combined by splicing them head to tail, and then the combined information may be encrypted using the first identification code to obtain encrypted information; for another example, the status characteristic information and payment information may be encrypted using the first identification code first, and then the encrypted status characteristic information and the encrypted payment information may be combined into encrypted information by splicing them head to tail.

[0102] Step S500: Send encrypted information to the server.

[0103] In one embodiment, the terminal sends encrypted information to the server, so that the server can perform relevant processing on the encrypted information, so as to judge the current status of the user based on it to confirm whether the current status of the user is normal, thereby achieving the purpose of improving payment security.

[0104] Step S600, obtaining confirmation payment information corresponding to the payment information.

[0105] In one embodiment, when the state characteristic information is decrypted in the server and the state characteristic information is verified to be correct, the terminal will receive the confirmation payment information corresponding to the payment information from the clearing center. When the terminal receives the confirmation payment information, it means that the current state characteristic information of the terminal has been successfully verified, and the terminal is not currently affected by a fake base station, Trojan virus, fraudulent website or phishing website. Since the environmental security of the terminal has been verified in the server and the clearing center, the user is no longer required to enter a password for confirmation, which can effectively save the user's operation process while ensuring information security, thereby improving the user's experience. In addition, since the terminal, server and clearing center are still in the RCS session, the confirmation payment information is sent to the terminal in the form of an RCS message, and the confirmation payment information can also be information that has been encrypted by the clearing center using the first identification code, so that the terminal can be guaranteed to be secure when sending and receiving messages, and avoid being stolen.

[0106] In one embodiment, the payment confirmation information may be implemented in different ways. For example, the payment confirmation information is a confirmation interface for the user to select, and the confirmation interface may display an option representing confirmation and an option representing cancellation; for another example, the payment confirmation information may be a facial recognition request requiring the user to perform face recognition; for another example, the payment confirmation information may be a fingerprint recognition request requiring the user to perform fingerprint recognition; for another example, the payment confirmation information may be a QR code scanning recognition request requiring the user to recognize a QR code.

[0107] In one embodiment, the payment information confirmation can be configured as a short-term validity mode, a delete-after-reading mode, or an invalid-after-reading mode, thereby preventing information leakage or theft.

[0108] Step S700, sending confirmation information corresponding to the confirmed payment information to the server, completing the payment, and exiting the RCS session.

[0109] In one embodiment, after the user confirms the confirmation payment information, the terminal will send the confirmation information corresponding to the confirmation payment information to the clearing center, so that the clearing center completes the payment operation. In this embodiment, before the terminal sends the confirmation information to the clearing center, the terminal will first send the confirmation information to the server, and after the server verifies that the confirmation information is valid, the server will send the confirmation information to the clearing center, so as to ensure the security of the information. In addition, since the terminal, the server and the clearing center are still in the RCS session, the terminal will send the confirmation information in the form of an RCS message, and before sending the confirmation information, the terminal can also encrypt it with the first identification code, and then send the encrypted confirmation information out, so as to ensure the security of the server when receiving the confirmation information, and avoid theft. When the clearing center completes the payment operation, the current payment request has been processed, so the terminal will exit the RCS session, thereby releasing the connection resources and avoiding the waste of connection resources.

[0110] like Figure 3 As shown, in one embodiment, step S400 includes but is not limited to the following steps:

[0111] Step S410, using the first identification code to encrypt the state characteristic information to obtain a first data block;

[0112] Step S420, combining the payment information and the first data block into encrypted information.

[0113] In one embodiment, after the terminal obtains the status characteristic information, it encrypts it using the first identification code to obtain a first data block, then the terminal combines the payment information and the first data block into encrypted information, and finally sends the encrypted information to the server. Since the encrypted information is formed by combining the payment information and the encrypted status characteristic information, and can be combined in a specific combination method, the risk of being cracked can be reduced, thereby improving the security of the information.

[0114] In one embodiment, the payment information and the first data block are combined into encrypted information, and there may be different implementation methods. For example, the payment information and the first data block may be concatenated head to tail, and then a header data for identifying the starting position is set in the first bit of the data, and a tail data for identifying the ending position is set in the last bit of the data, thereby forming encrypted information; for another example, the payment information and the first data block may be split and interlaced according to a preset format, and then a header data for identifying the starting position is set in the first bit of the data, and a tail data for identifying the ending position is set in the last bit of the data, thereby forming encrypted information.

[0115] Those skilled in the art will appreciate that concatenating the payment information and the first data block head to tail or splitting and interlacing them according to a preset format does not limit the order of the combination, and the payment information can be in front of or behind the first data block.

[0116] like Figure 4 As shown, in one embodiment, step S410 includes but is not limited to the following steps:

[0117] Step S411, obtaining a second identification code in the RCS session;

[0118] Step S412, using the second identification code to perform integrity processing on the state characteristic information to obtain a second data block;

[0119] Step S413: encrypt the second data block using the first identification code to obtain the first data block.

[0120] In one embodiment, each RCS session has a unique second identification code, which appears in a SIP invitation message during the process of creating the RCS session and exists in subsequent response messages and session end messages.

[0121] In one embodiment, the second identification code may be implemented in different ways. For example, the second identification code may be a call ID in an RCS session or a Dialog tag ID in an RCS session. However, it is worth noting that the second identification code needs to be different from the first identification code. In this embodiment, the second identification code is preferably a call ID in an RCS session.

[0122] In one embodiment, a second identification code is first obtained from the RCS session, and then the second identification code is used to perform integrity processing on the status feature information to obtain a second data block, and then the first identification code is used to encrypt the second data block to obtain a first data block, thereby ensuring the integrity and encryption security of the information and preventing the information from being lost or stolen and cracked during transmission, thereby affecting subsequent processing steps.

[0123] In one embodiment, the second identification code and the first identification code can be used in conjunction with different specific algorithms to implement information integrity processing and encryption processing.

[0124] The following is an example description:

[0125] The second identification code uses the call ID in the RCS session, and the first identification code uses the Dialog tagID in the RCS session, wherein the call ID is used as the key for the integrity protection operation, and the Dialog tag ID is used as the key for the encryption process. First, the call ID is used in conjunction with any one of the MD5 algorithm, SHA1 algorithm, and HMAC algorithm to perform an integrity protection operation on the state feature information to generate a second data block; then, the Dialog tag ID is used in conjunction with any one of the AES algorithm, DES algorithm, and 3DES algorithm to perform an encryption operation on the second data block to generate a first data block. Among them, the MD5 algorithm, SHA1 algorithm, and HMAC algorithm are all message digest algorithms that can generate hash values ​​to ensure the integrity and consistency of information transmission; the AES algorithm, DES algorithm, and 3DES algorithm are all encryption algorithms that can encrypt information to ensure that the information cannot be cracked.

[0126] In addition, in any of the above embodiments of the secure payment method applied to a terminal, the state characteristic information may be implemented in different ways. Specifically, the state characteristic information includes but is not limited to at least one of the following combinations: cell ID information and cell frequency information; cell ID information, IMSI information and GPS coordinate information; contact list information of the current time point and subscribing status; photo information. For example, the state characteristic information may include cell ID information and cell frequency information, and may also include cell ID information, IMSI information and GPS coordinate information, and may also include contact list information of the current time point and subscribing state, and may also include photo information, and may also include cell frequency information, cell ID information, IMSI information and GPS coordinate information, and may also include cell frequency information, cell ID information, current time point and contact list information of the subscribing state, and may also include cell ID information, cell frequency information and photo information, and may also include cell ID information, IMSI information, GPS coordinate information, current time point and contact list information of the subscribing state, and may also include cell ID information, IMSI information, GPS coordinate information and photo information, and may also include contact list information of the current time point and subscribing state and photo information, and may also include cell frequency information, cell ID information, IMSI information, GPS coordinate information, current time point, contact list information of the subscribing state and photo information, etc. By using different contents in the state characteristic information for encryption processing, the randomness of the encrypted information can be increased, and the information can be prevented from being intercepted and cracked or monitored and misused, thereby improving the payment security of the user and improving the user's usage experience.

[0127] Reference Figure 5 Another embodiment of the present application further provides a secure payment method applied to a server, which includes but is not limited to the following steps:

[0128] Step A100: Establish an RCS session with the terminal and obtain a first identification code in the RCS session.

[0129] In one embodiment, when the terminal establishes an RCS session with a clearing center through a server, the terminal first sends a session invitation message to the clearing center through the server. During the establishment of the RCS session, when the server detects that the peer user of the RCS session is the clearing center, the server extracts and saves the first identification code in the RCS session for use as a decryption key. After the clearing center receives the session invitation message, the clearing center also saves the first identification code for use as an encryption key. In addition, the clearing center also saves the MSISDN number of the terminal for identity authentication.

[0130] In one embodiment, the first identification code may be implemented in different ways. For example, the first identification code may be a call ID in an RCS session or a Dialog tag ID in an RCS session. The call ID is a unique session identifier in an RCS session, and the Dialog tag ID is a unique target identifier in an RCS session. The first identification code may be selected according to actual usage, but it should be noted that the first identification code saved in the server needs to be consistent with the first identification code saved in the terminal. In this embodiment, the first identification code is preferably a Dialog tag ID in an RCS session.

[0131] Step A200, obtaining encrypted information formed based on the first identification code, payment information and status characteristic information.

[0132] In one embodiment, the payment information includes but is not limited to the merchant account number, the payment amount, and the user's bank card information filled in by the user. The status feature information includes but is not limited to the following combinations: cell ID information and cell frequency information; cell ID information, IMSI information, and GPS coordinate information; contact list information of the current time point and subscribing status; and photo information.

[0133] Step A300, using the first identification code to restore the encrypted information to payment information and status characteristic information.

[0134] In one embodiment, after receiving the encrypted information sent by the terminal, the server first restores the encrypted information to payment information and status characteristic information to facilitate subsequent verification of the status characteristic information.

[0135] In one embodiment, the encrypted information formed based on the first identification code, payment information and status characteristic information can be formed in different ways. For example, the status characteristic information can be encrypted using the first identification code, and then the encrypted status characteristic information and payment information can be combined into encrypted information by splicing them head to tail; for another example, the payment information and status characteristic information can be combined by splicing them head to tail, and then the combined information can be encrypted using the first identification code to obtain encrypted information; for another example, the status characteristic information and payment information can be encrypted using the first identification code, and then the encrypted status characteristic information and the encrypted payment information can be combined into encrypted information by splicing them head to tail. Therefore, for different ways of forming encrypted information, the server can perform relevant processing accordingly, so that the payment information and status characteristic information can be restored.

[0136] Step A400, verify the status characteristic information, and when the verification is correct, send the payment information to the clearing center.

[0137] In one embodiment, there are different implementations for verifying the state characteristic information. For example, the verification operation can be performed by the server itself, by comparing the restored state characteristic information with the pre-registered state characteristic information, if they are consistent, it means that the verification is correct; for another example, the verification operation can be performed by the server in cooperation with the core network, by comparing the restored state characteristic information with the state characteristic information queried from the core network, if they are consistent, it means that the verification is correct.

[0138] In one embodiment, when the clearing center receives the payment information sent by the server, the clearing center can read the pre-saved MSISDN number of the terminal and compare the MSISDN number with the MSISDN number of the terminal obtained when establishing the RCS session. If they are consistent, it means that the user's identity is confirmed to be correct. At this time, the clearing center will send confirmation payment information corresponding to the payment information to the terminal so that the user can confirm the payment amount.

[0139] In one embodiment, since the server and the clearing center are in an RCS session, the server will send the payment information to the clearing center in the form of an RCS message, and since the payment information is sent when the status characteristic information is verified to be correct, the accuracy of the payment information can be guaranteed, avoiding the situation where the payment information is tampered with, thereby ensuring the security of the payment.

[0140] Step A500, obtaining confirmation information corresponding to the payment information.

[0141] In one embodiment, after the clearing center sends the confirmation payment information to be confirmed to the terminal based on the payment information, if the user confirms it, the terminal will send the confirmation information confirmed by the user to the server so that the server can perform subsequent processing on the confirmation information. Since the terminal, the server and the clearing center are still in the RCS session, the terminal will send the confirmation information in the form of an RCS message, and before sending the confirmation information, the terminal can also encrypt it with the first identification code and then send the encrypted confirmation information out, so that the security of the server when receiving the confirmation information can be guaranteed to avoid theft.

[0142] Step A600, sending the verified confirmation information to the clearing center, completing the payment, and exiting the RCS session.

[0143] In one embodiment, when the server receives the confirmation information confirmed by the user, the server will verify the confirmation information to ensure the authenticity of the confirmation information. Since the terminal and the server exchange information through RCS messages, the server can analyze the data structure of the confirmation information. If it is normal, it means that the confirmation information is true. Those skilled in the art will understand that when the confirmation information received by the server is encrypted, the server can first decrypt the confirmation information, and then determine whether the data structure of the confirmation information is correct. When the server verifies that the confirmation information is correct and valid, the server will forward the confirmation information to the clearing center so that the clearing center can complete the final payment operation. When the clearing center completes the payment operation, the current payment request has been processed. Therefore, the server and the clearing center will exit the RCS session, thereby releasing connection resources and avoiding waste of connection resources.

[0144] like Figure 6 As shown, in one embodiment, step A300 includes but is not limited to the following steps:

[0145] Step A310, splitting the encrypted information into payment information and a first data block;

[0146] Step A320: Decrypt the first data block using the first identification code to obtain status characteristic information.

[0147] In one embodiment, when the server receives the encrypted information sent by the terminal, the server first splits the encrypted information into payment information and a first data block, and then uses the first identification code to decrypt the first data block to obtain the terminal status feature information. Figure 3 The corresponding inverse processing of steps S410 to S420 in the illustrated embodiment enables the server to correctly split the encrypted information into the payment information and the first data block. After the server obtains the state characteristic information of the terminal, the server verifies the correctness of the state characteristic information. Only when the state characteristic information is verified to be correct will the server send the payment information to the clearing center, thereby ensuring the correctness of the payment information, avoiding the situation where the payment information is tampered with, and ensuring the security of the payment.

[0148] In one embodiment, there may be different implementations for verifying the state characteristic information. For example, after the server decrypts the state characteristic information, the server may first determine whether the data structure of the state characteristic information is correct. If it is not correct, it means that the decryption process has failed, and it can be considered that the payment information was intercepted by wiretapping and then forged and sent. In this case, the server will refuse to send the payment information to the clearing center to avoid damage to the user's property. For another example, after the server decrypts the state characteristic information, the server or the server cooperates with the core network to compare and analyze the specific content of the state characteristic information. When the result of the comparison and analysis is correct, the server will send the payment information to the clearing center.

[0149] like Figure 7 As shown, in one embodiment, step A320 includes but is not limited to the following steps:

[0150] Step A321, obtaining a second identification code in the RCS session;

[0151] Step A322, using the first identification code to decrypt the first data block to obtain a second data block;

[0152] Step A323, use the second identification code to perform integrity processing on the second data block to obtain status characteristic information.

[0153] In one embodiment, each RCS session has a unique second identification code, which appears in a SIP invitation message during the process of creating the RCS session and exists in subsequent response messages and session end messages.

[0154] In one embodiment, the second identification code may be implemented in different ways. For example, the second identification code may be a call ID in an RCS session or a Dialog tag ID in an RCS session. However, it is worth noting that the second identification code needs to be different from the first identification code. In this embodiment, the second identification code is preferably a call ID in an RCS session.

[0155] In one embodiment, the second identification code is first obtained from the RCS session, and then the first data block is decrypted using the first identification code to obtain the second data block. Then, the second data block is integrity processed using the second identification code to obtain state characteristic information. Since the state characteristic information is processed for data integrity after being decrypted, the integrity of the information can be guaranteed to avoid loss of information during transmission and affect subsequent processing steps.

[0156] In one embodiment, the second identification code and the first identification code can be used in conjunction with different specific algorithms to implement information integrity processing and decryption processing.

[0157] The following is an example description:

[0158] The second identification code uses the call ID in the RCS session, and the first identification code uses the Dialog tagID in the RCS session, where the call ID is used as the key for the integrity protection operation, and is used in conjunction with any one of the MD5 algorithm, SHA1 algorithm, and HMAC algorithm to implement the integrity protection operation; the Dialog tag ID is used as the key for the decryption process, and is used in conjunction with any one of the AES algorithm, DES algorithm, and 3DES algorithm to implement the decryption operation. It is worth noting that the algorithm used for the integrity protection operation and the algorithm used for the decryption operation in the server need to be consistent with the algorithm used for the integrity protection operation and the algorithm used for the encryption operation in the terminal. For example, the terminal uses the call ID in conjunction with the MD5 algorithm to implement the integrity protection operation, and uses the Dialog tag ID in conjunction with the AES algorithm to implement the encryption operation. Then, the server needs to use the call ID in conjunction with the MD5 algorithm to implement the integrity protection operation, and use the Dialog tag ID in conjunction with the AES algorithm to implement the decryption operation.

[0159] In addition, in any of the above embodiments of the secure payment method applied to the server, the state characteristic information may be implemented in different ways. Specifically, the state characteristic information includes but is not limited to at least one of the following combinations: cell ID information and cell frequency information; cell ID information, IMSI information and GPS coordinate information; contact list information of the current time point and subscribing status; photo information.

[0160] Based on the different implementation methods of the above-mentioned state characteristic information, in Figure 5 In the illustrated embodiment, the verification process of the state characteristic information in step A400 may be implemented in different ways, and the following is an exemplary description:

[0161] First embodiment:

[0162] The server determines the data structure of the status characteristic information. If the data structure of the status characteristic information is incorrect, it can be considered that the payment information was intercepted by wiretapping and then forged and sent. In this case, the server will refuse to send the payment information to the clearing center to avoid damage to the user's property. The status characteristic information can be formed by merging the cell ID information and the cell frequency information, or by merging the cell ID information, IMSI information and GPS coordinate information in sequence, or by merging the current time point and the contact list information of the subscribing status.

[0163] Second implementation method:

[0164] The status characteristic information includes cell ID information and cell frequency information. The server applies to the core network database for the cell frequency information configured by the operator based on the cell ID information. The server compares the cell frequency information of the terminal with the cell frequency information configured by the operator. If they are consistent, it means that the network where the terminal is located is normal. Otherwise, it means that the terminal is registered in a fake base station, and the server terminates the payment process.

[0165] Third embodiment:

[0166] The status characteristic information includes cell ID information, IMSI information and GPS coordinate information. The server applies to the core network database to obtain the base station address where the terminal is currently registered based on the cell ID information and IMSI information. The server calculates the distance between the terminal's GPS address and the base station address based on the terminal's GPS coordinate information, and compares whether the distance meets the cell radiation radius of the base station. If so, it means that the network where the terminal is located is normal. Otherwise, it means that the terminal is registered in a fake base station, and the server terminates the payment process.

[0167] Fourth embodiment:

[0168] The status characteristic information includes the contact list information of the current time point and the subscribing status. According to the current time point of the terminal, the server queries the contact status corresponding to the time point and the terminal recorded in the server, and compares it with the contact status in the contact list information corresponding to the current time point provided by the terminal. If it is incorrect, it can be considered that the hacker has used the user account or intercepted the payment information to forge and send it, and the server terminates the payment process. Specifically, it is assumed that at a certain time point when the RCS session is established, there are contacts A and B in the contact list information of the terminal, the status of contact A is online, and its capability status has been updated by the current terminal, so that the current terminal registers its latest capability status, among which the capability status of contact A is to support chat and video calls, but not to support file transfer and group chat; the status of contact B is offline. After the server obtains the contact list information corresponding to the subscribing status at a certain time point, the server compares the online status and capability status of contact A and contact B at that time point. If they match, the RCS service registration status of the terminal is considered normal, otherwise, it is judged to be abnormal, and the server terminates the payment process.

[0169] Fifth embodiment:

[0170] The status characteristic information includes photo information. The server searches for the photo information corresponding to the user recorded in the server based on the photo information sent by the terminal, and compares the two photo information. If the two photo information are inconsistent, it can be considered that a hacker has used the user's account or intercepted the payment information and forged it, and the server terminates the payment process.

[0171] Sixth embodiment:

[0172] The status characteristic information includes cell frequency information, cell ID information, IMSI information and GPS coordinate information. The server performs the verification process of the status characteristic information in the second embodiment and the verification process of the status characteristic information in the fourth embodiment at the same time according to the cell frequency information, cell ID information, IMSI information and GPS coordinate information. When both verification process implementations are normal, it means that the terminal is in a normal state. If any of the two verification process implementations is judged to be abnormal, it can be considered that the terminal is in an abnormal state, and the server terminates the payment process.

[0173] In addition, there may be other implementation methods for verifying the status characteristic information, such as the above-mentioned first implementation method in combination with the second implementation method, the above-mentioned first implementation method in combination with the fourth implementation method and the fifth implementation method, etc., that is, for any one or more combinations of cell ID information and cell frequency information, cell ID information and IMSI information and GPS coordinate information, current time point and subscribable status contact list information, and photo information, there may be corresponding verification processing implementation methods, which will not be repeated here.

[0174] In addition, compared with the above Figure 5 The verification process of the status characteristic information in step A400 in the illustrated embodiment may also have other embodiments to achieve the purpose of protecting users from being defrauded.

[0175] In one embodiment, a database of authenticated merchant accounts is established in the server. When the server receives payment information sent by the terminal, the server can read the merchant account from the payment information, and by comparing whether the merchant account is in the database of authenticated merchant accounts, it can be confirmed whether the merchant account is a fraudulent account. If it is a fraudulent account, the server terminates the payment process.

[0176] The following is an example description:

[0177] Merchants need to provide business registration information and account information to the server in advance for registration. Operators can check the business registration information and credit information of the merchant through the server, provide registration services to legal, compliant and creditworthy merchants, and establish a legal and compliant merchant database. During the payment process, the server obtains the merchant account from the payment information sent by the terminal, and compares the merchant account with the information in the merchant database. If the merchant account does not exist, it means that the merchant account is a fraudulent account, and the server terminates the payment process, avoiding the risk of users paying to fraudulent merchants.

[0178] In addition, another embodiment of the present application further provides a secure payment method applied to a payment system, the secure payment method including but not limited to the following steps:

[0179] Step B100, the terminal initiates a payment request;

[0180] Step B200: The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session;

[0181] Step B300, the terminal obtains payment information and status characteristic information;

[0182] Step B400, the terminal converts the payment information and the status characteristic information into encrypted information based on the first identification code, and sends the encrypted information to the server;

[0183] Step B500, the server obtains the encrypted information, and uses the first identification code to restore the encrypted information into payment information and status characteristic information;

[0184] Step B600, the server verifies the status characteristic information, and when the verification is correct, sends the payment information to the clearing center;

[0185] Step B700, the terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server;

[0186] Step B800, the server obtains the confirmation information and sends the verified confirmation information to the clearing house;

[0187] Step B900: The terminal completes the payment and exits the RCS session with the server.

[0188] In addition, in one embodiment, step B400 includes but is not limited to the following steps:

[0189] Step B410, the terminal uses the first identification code to encrypt the state characteristic information to obtain a first data block;

[0190] Step B420, the terminal combines the payment information and the first data block into encrypted information;

[0191] Step B430: The terminal sends encrypted information to the server.

[0192] In addition, in one embodiment, step B410 includes but is not limited to the following steps:

[0193] Step B411, the terminal obtains the second identification code in the RCS session;

[0194] Step B412, the terminal uses the second identification code to perform integrity processing on the status characteristic information to obtain a second data block;

[0195] Step B413: The terminal encrypts the second data block using the first identification code to obtain the first data block.

[0196] In addition, in one embodiment, step B500 includes but is not limited to the following steps:

[0197] Step B510, the server obtains the encrypted information;

[0198] Step B520, the server splits the encrypted information into payment information and a first data block;

[0199] Step B530: The server uses the first identification code to decrypt the first data block to obtain status characteristic information.

[0200] In addition, in one embodiment, step B530 includes but is not limited to the following steps:

[0201] Step B531, the server obtains the second identification code in the RCS session;

[0202] Step B532, the server uses the first identification code to decrypt the first data block to obtain a second data block;

[0203] Step B533: The server uses the second identification code to perform integrity processing on the second data block to obtain status characteristic information.

[0204] In addition, in any of the above embodiments of the secure payment method applied to the payment system, the state characteristic information may be implemented in different ways. Specifically, the state characteristic information includes but is not limited to at least one of the following combinations: cell ID information and cell frequency information; cell ID information, IMSI information and GPS coordinate information; contact list information of the current time point and subscribing status; photo information.

[0205] It should be noted that the secure payment method applied to the payment system in the above-mentioned embodiment, the secure payment method applied to the terminal in the above-mentioned embodiment, and the secure payment method applied to the server in the above-mentioned embodiment are all based on the same inventive concept, and the difference between the three is that the focus is different. For example, the focus of the secure payment method applied to the terminal in the above-mentioned embodiment is the terminal, and the focus of the secure payment method applied to the server in the above-mentioned embodiment is the server, and the focus of the secure payment method applied to the payment system in the above-mentioned embodiment is the system including the terminal and the server. Therefore, the above three have the same beneficial effect, that is, the payment information and the state feature information can be formed into encrypted information based on the first identification code in the RCS session, and the encrypted information can be decrypted by the server to obtain the state feature information of the terminal, and only when the state feature information is verified to be correct, the subsequent payment operation is realized, so that the user can be prevented from being deceived during the payment or transfer process, thereby improving the payment security of the user and improving the user's usage experience. In addition, since the above three have similar method principles and the difference is only in the focus on different subjects, the method principle of the secure payment method applied to the payment system in this embodiment will not be described in detail here.

[0206] Reference Figure 8 An embodiment of the present application provides a terminal, and the terminal 200 can be any type of intelligent terminal, such as a smart phone, a tablet computer, a laptop or a desktop computer.

[0207] Specifically, the terminal 200 includes: a memory 201, a processor 202, and a computer program stored in the memory 201 and executable on the processor 202, and the processor 202 is constructed with an RCS client 203, and the RCS client 203 is provided with a security information generation module 204 for using a first identification code to form encrypted information from payment information and status feature information.

[0208] The processor 202 and the memory 201 may be connected via a bus or other means. Figure 8 The example of connecting through bus is taken in the following.

[0209] It should be noted that the terminal 200 in this embodiment is Figure 1 The system structure platform 100 in the embodiment shown is based on the same inventive concept. The terminal 200 in this embodiment can constitute Figure 1 The system structure platform 100 in the illustrated embodiment is a part of the system structure platform 100, so both have the same implementation principles and beneficial effects, which will not be described in detail here.

[0210] The non-transient software program and instructions required to implement the secure payment method applied to the terminal in the above embodiment are stored in the memory 201. When executed by the processor 202, the secure payment method applied to the terminal in the above embodiment is executed, for example, the above described Figure 2 The method steps S100 to S700, Figure 3 Steps S410 to S420 of the method, Figure 4 Method steps S411 to S413 in.

[0211] Reference Fig. 9 An embodiment of the present application provides a server, and the server 300 can be any type of server, such as a local server, a cloud server, etc.

[0212] Specifically, the server 300 includes: a memory 301, a processor 302, and a computer program stored in the memory 301 and executable on the processor 302, and the processor 302 is constructed with an RCS server 303, and the RCS server 303 is provided with a security information checking module 304 for restoring encrypted information to payment information and status characteristic information using a first identification code.

[0213] The processor 302 and the memory 301 may be connected via a bus or other means. Fig. 9 The example of connecting through bus is taken in the following.

[0214] It should be noted that the server 300 in this embodiment is Figure 1 The system structure platform 100 in the embodiment shown is based on the same inventive concept. The server 300 in this embodiment can constitute Figure 1 The system structure platform 100 in the illustrated embodiment is a part of the system structure platform 100, so both have the same implementation principles and beneficial effects, which will not be described in detail here.

[0215] The non-transient software program and instructions required to implement the secure payment method applied to the server in the above embodiment are stored in the memory 301. When executed by the processor 302, the secure payment method applied to the server in the above embodiment is executed, for example, the above described Figure 5 Method steps A100 to A600, Figure 6 Method steps A310 to A320, Figure 7 Method steps A321 to A323.

[0216] In addition, an embodiment of the present application further provides a payment system, including a terminal and a server. When the terminal initiates a payment request:

[0217] The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session;

[0218] The terminal obtains payment information and status characteristic information;

[0219] The terminal converts the payment information and the status characteristic information into encrypted information based on the first identification code, and sends the encrypted information to the server;

[0220] The server obtains the encrypted information and uses the first identification code to restore the encrypted information into payment information and status characteristic information;

[0221] The server verifies the status characteristic information and sends the payment information to the clearing center if the verification is correct;

[0222] The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server;

[0223] The server obtains the confirmation information and sends the verified confirmation information to the clearing house;

[0224] The terminal completes the payment and exits the RCS session with the server.

[0225] In one embodiment, the status characteristic information includes but is not limited to at least one of the following:

[0226] Cell ID information and cell frequency information;

[0227] Cell ID information, IMSI information and GPS coordinate information;

[0228] Contact list information at the current time point and subscription status;

[0229] Photo information.

[0230] It should be noted that the payment system in the above-mentioned embodiment and the secure payment method applied to the payment system in the above-mentioned embodiment are based on the same inventive concept. Therefore, the corresponding content of the secure payment method applied to the payment system in the above-mentioned embodiment is also applicable to the payment system in the above-mentioned embodiment and will not be described in detail here.

[0231] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0232] In addition, an embodiment of the present application further provides a computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being executed by a processor or controller, for example, Figure 8 The processor 202 in the embodiment can be executed by executing the secure payment method applied to the terminal in the embodiment, for example, executing the above-described Figure 2 The method steps S100 to S700, Figure 3 Steps S410 to S420 of the method, Figure 4 In the method steps S411 to S413. Fig. 9 The processor 302 in the embodiment can be executed by executing the secure payment method applied to the server in the embodiment, for example, executing the above-described Figure 5 Method steps A100 to A600, Figure 6 Method steps A310 to A320, Figure 7 Steps A321 to A323 of the method. Figure 1 The terminal processor 112 and the service processor 122 cooperate to execute, so that the terminal processor 112 and the service processor 122 cooperate to execute the secure payment method applied to the payment system in the above embodiment, for example, execute method steps B100 to B900, method steps B410 to B430, method steps B411 to B413, method steps B510 to B530, and method steps B531 to B533 in the above embodiment.

[0233] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0234] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions without violating the spirit of the present application. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present application.

Claims

1. A secure payment method, applied to a terminal, comprising: Initiate a payment request; Establishing an RCS session with a server, and acquiring a first identification code in the RCS session, wherein the first identification code is a target identification in the RCS session; Obtain payment information and status characteristic information; Acquire a second identification code in the RCS session, wherein the second identification code is a session identifier in the RCS session; Using the second identification code to perform integrity processing on the state characteristic information to obtain a second data block; encrypting the second data block using the first identification code to obtain a first data block; combining the payment information and the first data block into encrypted information; Sending the encrypted information to a server; Obtaining confirmed payment information corresponding to the payment information; Send confirmation information corresponding to the confirmed payment information to the server, complete the payment, and exit the RCS session.

2. The secure payment method according to claim 1, characterized in that: The state characteristic information includes cell ID information and at least one of the following: Cell frequency information; IMSI information and GPS coordinates information.

3. The secure payment method according to claim 1 or 2, characterized in that: The state characteristic information includes at least one of the following: Contact list information at the current time point and subscription status; Photo information.

4. A secure payment method, applied to a server, comprising: Establishing an RCS session with a terminal, and acquiring a first identification code in the RCS session, wherein the first identification code is a target identification in the RCS session; Acquire encrypted information formed based on the first identification code, the payment information and the status characteristic information; Splitting the encrypted information into the payment information and a first data block; Acquire a second identification code in the RCS session, wherein the second identification code is a session identifier in the RCS session; Decrypting the first data block using the first identification code to obtain a second data block; Using the second identification code to perform integrity processing on the second data block to obtain the state characteristic information; Verifying the status characteristic information, and when the verification is correct, sending the payment information to a clearing center; Obtaining confirmation information corresponding to the payment information; The verification confirmation information is sent to the clearing house to complete the payment and exit the RCS session.

5. The secure payment method according to claim 4, characterized in that: The state characteristic information includes cell ID information and at least one of the following: Cell frequency information; IMSI information and GPS coordinates information.

6. The secure payment method according to claim 4 or 5, characterized in that: The state characteristic information includes at least one of the following: Contact list information at the current time point and subscription status; Photo information.

7. A secure payment method, applied to a payment system, comprising: The terminal initiates a payment request; The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session, wherein the first identification code is a target identification in the RCS session; The terminal obtains payment information and status characteristic information; The terminal obtains a second identification code in the RCS session, wherein the second identification code is a session identifier in the RCS session; The terminal uses the second identification code to perform integrity processing on the state characteristic information to obtain a second data block; The terminal encrypts the second data block using the first identification code to obtain a first data block; The terminal combines the payment information and the first data block into encrypted information; The terminal sends the encrypted information to the server; The server obtains the encrypted information; The server splits the encrypted information into the payment information and the first data block; The server obtains the second identification code in the RCS session; The server uses the first identification code to decrypt the first data block to obtain a second data block; The server performs integrity processing on the second data block using the second identification code to obtain the state characteristic information; The server verifies the status characteristic information, and when the verification is correct, sends the payment information to the clearing center; The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server; The server obtains the confirmation information and sends the confirmed information to the clearing house; The terminal completes the payment and exits the RCS session with the server.

8. The secure payment method according to claim 7, characterized in that: The state characteristic information includes cell ID information and at least one of the following: Cell frequency information; IMSI information and GPS coordinates information.

9. The secure payment method according to claim 7 or 8, characterized in that: The state characteristic information includes at least one of the following: Contact list information at the current time point and subscription status; Photo information.

10. A terminal, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the secure payment method as claimed in any one of claims 1 to 3 when executing the computer program.

11. A server, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the secure payment method as described in any one of claims 4 to 6 when executing the computer program.

12. A payment system, comprising a terminal and a server, characterized in that: The terminal initiates a payment request; The terminal and the server establish an RCS session, and the terminal and the server respectively obtain a first identification code in the RCS session, wherein the first identification code is a target identifier in the RCS session; The terminal obtains payment information and status characteristic information; The terminal obtains a second identification code in the RCS session, wherein the second identification code is a session identifier in the RCS session; The terminal uses the second identification code to perform integrity processing on the status feature information to obtain a second data block; The terminal encrypts the second data block using the first identification code to obtain a first data block; The terminal combines the payment information and the first data block into encrypted information; The terminal sends the encrypted information to the server; The server obtains the encrypted information; The server splits the encrypted information into the payment information and the first data block; The server obtains the second identification code in the RCS session; The server uses the first identification code to decrypt the first data block to obtain a second data block; The server uses the second identification code to perform integrity processing on the second data block to obtain the state characteristic information; The server verifies the status characteristic information, and when the verification is correct, sends the payment information to the clearing center; The terminal obtains confirmation payment information corresponding to the payment information, and sends confirmation information corresponding to the confirmation payment information to the server; The server obtains the confirmation information and sends the confirmed information to the clearing center after verification; The terminal completes the payment and exits the RCS session with the server.

13. The payment system according to claim 12, characterized in that: The state characteristic information includes cell ID information and at least one of the following: Cell frequency information; IMSI information and GPS coordinates information.

14. The payment system according to claim 12 or 13, characterized in that: The state characteristic information includes at least one of the following: Contact list information at the current time point and subscription status; Photo information.

15. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the secure payment method described in any one of claims 1 to 3, or to execute the secure payment method described in any one of claims 4 to 6, or to execute the secure payment method described in any one of claims 7 to 9.