Method and device for acquiring communication protocol information, equipment and medium

Abstract

The embodiment of the invention provides a method and device for acquiring communication protocol information, equipment and a medium. The scheme comprises the steps of obtaining state information of the mobile terminal; triggering a process of providing communication protocol information by the server based on the state information; wherein the communication protocol information is the communication protocol information used in the process that the mobile terminal obtains the card information used for binding the card from the card. According to the flow, the mobile terminal obtains communication protocol information fed back by the server; and the mobile terminal stores the communication protocol information fed back by the server.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and more particularly to a method for obtaining communication protocol information. The present invention also relates to an apparatus, device, and medium for obtaining communication protocol information. Background Art

[0002] With the enhancement of mobile terminal functions, more and more transactions can be processed using mobile terminals. For example, mobile terminals can be used as virtual cards instead of physical cards for payment, access control, identity authentication, etc. In order to use mobile terminals to process corresponding transactions, the mobile terminal must be bound to the corresponding card in advance.

[0003] Therefore, a method is needed to facilitate users to bind mobile terminals with cards, so as to improve the user experience during the card binding process. Summary of the Invention

[0004] In view of this, embodiments of the present application provide a method, apparatus, device, and medium for obtaining communication protocol information to solve the problem of poor user experience during the existing card binding operation.

[0005] According to a first aspect of an embodiment of the present application, a method for obtaining communication protocol information is provided, including: obtaining status information of a mobile terminal; based on the status information, triggering a process in which a server provides communication protocol information; the communication protocol information is the communication protocol information used in a process in which the mobile terminal obtains card information for binding the card from a target type of card that supports a near-field communication function through near-field communication; according to the process, the mobile terminal obtains the communication protocol information fed back by the server; the communication protocol information includes communication protocol information that does not exist in the mobile terminal before the process is triggered; and the mobile terminal saves the communication protocol information fed back by the server.

[0006] According to the second aspect of an embodiment of the present application, a card binding method based on near-field communication is provided, including: a mobile terminal obtains a card binding trigger operation performed by a user; based on the card binding trigger operation, obtaining response information fed back by the target card based on the near-field communication through near-field communication; using the first communication protocol information saved in the mobile terminal to parse the response information to obtain the card information of the target card contained in the response information; and displaying the card information on a card binding page.

[0007] According to a third aspect of an embodiment of the present application, a device for obtaining communication protocol information is provided, including: a status acquisition module for obtaining status information of a mobile terminal; a determination module for triggering a process of a server providing communication protocol information based on the status information; the communication protocol information is the communication protocol information used in a process in which the mobile terminal obtains card information for binding the card from a target type of card supporting a near-field communication function through near-field communication; a protocol acquisition module for enabling the mobile terminal to obtain, according to the process, the communication protocol information fed back by the server; the communication protocol information includes communication protocol information that does not exist in the mobile terminal before the process is triggered; and a protocol storage module for enabling the mobile terminal to save the communication protocol information fed back by the server.

[0008] According to a fourth aspect of an embodiment of the present application, a card binding device based on near field communication is provided, comprising: a trigger operation acquisition module, configured to obtain, via a mobile terminal, a card binding trigger operation performed by a user; and a response information acquisition module, configured to obtain, via near field communication, response information fed back by a target card based on the near field communication, based on the card binding trigger operation. A parsing module is used to parse the response information using the first communication protocol information saved in the mobile terminal to obtain the card information of the target card contained in the response information; a display module is used to display the card information on the card binding page.

[0009] According to the fifth aspect of the embodiments of the present application, a computer device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute to implement the above-mentioned method of obtaining communication protocol information or the above-mentioned card binding method based on near-field communication.

[0010] According to the sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed by a processor, the steps of the above-mentioned method for obtaining communication protocol information or the steps of the above-mentioned card binding method based on near-field communication are implemented.

[0011] At least one embodiment of this specification can achieve the following beneficial effects: Based on the status information of the mobile terminal, the server can send the communication protocol information required for the card binding service to the mobile terminal. The mobile terminal will then save the acquired communication protocol information locally. The mobile terminal can then process the card binding service based on the locally stored communication protocol information. In this way, during the communication phase between the mobile terminal and the card during the card binding process, the mobile terminal can obtain the card information of the card based on the acquired communication protocol information used to identify the card information. This eliminates the need for the mobile terminal to interact with the server each time it processes the card binding service, thereby reducing the time consumption of the card binding operation and improving the user experience during the card binding operation. On the other hand, the server can provide the communication protocol information to the mobile terminal so that the mobile terminal does not need to update the terminal application version, thereby further improving the user experience and reducing service costs.

[0012] In at least one embodiment, by tapping or tapping a mobile terminal against a target card, the mobile terminal can obtain the target card's card information via near-field communication and display the card information on a card binding page, eliminating the need for the user to manually enter the card information for the card to be bound, thereby simplifying user operations. Furthermore, the mobile terminal can utilize locally stored communication protocol information to parse the card information obtained via near-field communication. This eliminates the need for the mobile terminal to interact with the server each time a card binding transaction is processed during the communication phase between the mobile terminal and the card during the card binding process. This reduces the time required for the card binding operation and improves the user experience during the card binding process. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0014] Figure 1 This is a schematic diagram of an application scenario of a method for obtaining communication protocol information provided in an embodiment of this specification; Figure 2 This is a flow chart of a method for obtaining communication protocol information provided by an embodiment of this specification; Figure 3 This is a schematic diagram of a card binding triggering page provided in an embodiment of this specification; Figure 4 This is a flowchart of a card binding method based on near field communication provided in an embodiment of this specification; Figure 5AThis is a page diagram of a target application provided by an embodiment of this specification; Figure 5B This is another page diagram of a target application provided by an embodiment of this specification; Figure 6 This is a schematic diagram of a card binding prompt page provided in an embodiment of this specification; Figure 7 This is a schematic diagram of an identification response page provided by an embodiment of this specification; Figure 8 is a schematic diagram of a first suspension page provided in an embodiment of this specification; Figure 9 This is a schematic diagram of another identification response page provided by an embodiment of this specification; Figure 10 is a schematic diagram of a second suspension page provided in an embodiment of this specification; Figure 11 This is a schematic diagram of a card adding page provided in an embodiment of this specification; Figure 12 This is a schematic diagram of a card binding page provided in an embodiment of this specification; Figure 13 This is a swimlane flow diagram of a method for obtaining communication protocol information and binding a card provided in an embodiment of this specification; Figure 14 This is a schematic diagram of the structure of a device for obtaining communication protocol information provided in an embodiment of this specification; Figure 15 This is a structural diagram of a card binding device based on near field communication provided in an embodiment of this specification; Figure 16 This is a structural block diagram of a computer device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0015] The following description sets forth many specific details to facilitate a thorough understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of the present application. Therefore, the present application is not limited to the specific implementations disclosed below.

[0016] The terms used in one or more embodiments of the present application are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of the present application. The singular forms "a", "said" and "the" used in one or more embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of the present application refers to and includes any or all possible combinations of one or more associated listed items. It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".

[0017] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0018] First, the terms involved in one or more embodiments of this specification are explained.

[0019] Near Field Communication (NFC) is a short-range, high-frequency wireless communication technology commonly used for rapid data exchange between devices. NFC technology typically operates when devices are in physical contact or very close to each other. It is widely used in various fields, such as payment systems, e-ticketing, smart cards, and device pairing.

[0020] The internationally accepted bank card chip standard (Europay MasterCard and Visa, EMV) is an international payment standard used to support secure transactions between smart cards and payment terminals.

[0021] During the process of binding a mobile terminal to a card through short-range communication, if the communication protocol information used by the mobile terminal for binding the card is inconsistent with the communication protocol information corresponding to the card, or the mobile terminal does not have the communication protocol information that can parse the card information, the mobile terminal will not be able to bind the card through short-range communication.

[0022] In the related art, each time a mobile terminal processes a card binding service, it needs to interact with the server to call the communication protocol information stored on the server to bind the card. However, if the communication quality between the mobile terminal and the server is poor, the interaction time between the mobile terminal and the server will be too long, which will in turn cause the user's card binding process to take a relatively long time, resulting in a relatively poor card binding experience for the user. In another related art, a client with a card binding function for binding a target card is required to bind the target card. Therefore, in order to achieve card binding, the mobile terminal needs to download and update the corresponding version of the client. However, this method requires a large amount of user network resources, and the user can only successfully bind the card after downloading the corresponding version of the client, which can easily lead to a low user conversion rate and a relatively small number of users who bind cards.

[0023] The technical solutions provided by the embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0024] Figure 1 This is a schematic diagram of an application scenario of a method for obtaining communication protocol information provided in an embodiment of this specification.

[0025] like Figure 1 As shown, the application scenario diagram includes a mobile terminal 101 , a server 102 and a card 103 .

[0026] In the embodiments of this specification, the mobile terminal 101 may include but is not limited to at least one of a smart phone, a tablet computer, a laptop computer, an intelligent interactive device, a wearable device, an in-vehicle intelligent terminal, and the like. The wearable device may include but is not limited to at least one of a smart bracelet, a smart watch, smart glasses, and the like. The server 102 may include but is not limited to at least one of any device, equipment, platform, equipment cluster, or cloud computing service center with computing and processing capabilities. The card 103 may include but is not limited to a bank card, a bus card, an access card, a shopping card, a discount card, a membership card, a tag card, a smart card, or the like with NFC functionality, or the card may also include any of the following cards in the form of a virtual card that carries the card information on a smart device with NFC functionality.

[0027] A communication connection is established between the mobile terminal 101 and the server 102. The communication connection may include, but is not limited to, a local area network (LAN) connection, a wide area network (WAN) connection, an internet connection, a short-range communication connection, or other types of data network connections. Short-range communication connections include, but are not limited to, near-field communication (NFC), LAN, Bluetooth, infrared, and other connection methods. The mobile terminal 101 may send a data acquisition request to the server 102, and the server 102 may respond to the request by returning response data to the mobile terminal 101. Alternatively, the server 102 may proactively send data to the mobile terminal 101. The mobile terminal 101 may be an initiating device, which actively triggers near-field communication and is responsible for generating a radio frequency field and initiating the NFC communication process. The card 103 may be a passive device, relying on the radio frequency field generated by the mobile terminal 101 for energy, or it may be an active card, using its own energy to communicate with the mobile terminal. The card 103 may send data to the mobile terminal 101 in response to a trigger signal from the mobile terminal 101.

[0028] In this application, a method for obtaining communication protocol information is provided, which is described in detail one by one in the following embodiments. Figure 2 This is a flowchart of a method for obtaining communication protocol information provided in an embodiment of this specification.

[0029] From a program perspective, the execution entity of the process can be a program installed on a device used to process communication protocol information. It is understood that the method can be executed by any device, equipment, platform, or device cluster with computing and processing capabilities, such as a mobile terminal, a server, or both.

[0030] like Figure 2 As shown, the process may include the following steps.

[0031] Step 202: Acquire status information of the mobile terminal.

[0032] In an embodiment of the present specification, the status information may include at least one of various information such as status information representing a terminal application started or installed in the mobile terminal, status information representing the time or space in which the mobile terminal is located, status information representing the device attributes or functional status of the mobile terminal, and status information representing the communication protocol information in the mobile terminal.

[0033] In the embodiments of this specification, there may be multiple triggering conditions for obtaining the status information of the mobile terminal. For example, the status information of the mobile terminal may be obtained according to a preset time period, or the status information of the mobile terminal may be obtained if a preset application in the mobile terminal is started, or the status information of the mobile terminal may be obtained if a preset page of a preset application in the mobile terminal is opened, or at least one of the status information of the mobile terminal may be obtained if the connection network of the mobile terminal changes.

[0034] In actual applications, the preset time period can be one day or another time period. The preset application can be a terminal application that can interact with the server. The preset page can be a card binding page or other page in the preset application, such as the application homepage, etc., without limitation.

[0035] Step 204: Based on the status information, trigger the server to provide a process of communication protocol information; the communication protocol information is the communication protocol information used by the mobile terminal in the process of obtaining card information for binding the card from a target type of card supporting the near field communication function through near field communication.

[0036] In the embodiments of this specification, if the status information of the mobile terminal satisfies the process of triggering the server to provide communication protocol information, the process of the server providing communication protocol information to the mobile terminal may be triggered. The communication protocol information may be the communication protocol information used in the process of obtaining card information from the card. The card information may be the information used to bind the card to the mobile terminal, such as: account opening bank information, card number information, card user information, etc.

[0037] In the embodiments of this specification, the card may be a card that supports near-field communication (NFC), and the communication method between the mobile terminal and the card may be a communication method based on NFC. In actual applications, the card may also support other communication functions, such as Bluetooth communication. The communication method between the mobile terminal and the card may be Bluetooth communication. The specific communication method is not limited here; it only requires that the mobile terminal can obtain the card information used for card binding.

[0038] In the embodiments of this specification, there may be a corresponding relationship between the target type of card and the communication protocol information provided by the server. For example, the target type of card may be a card that complies with the communication protocol information, or the information transmitted by the target type of card through near-field communication is information that complies with the communication protocol information. For example, in a scenario where a mobile terminal is bound to a bank card, if the target type is a UnionPay card type, the communication protocol information is protocol information that can identify a UnionPay card type card; if the target type is an EMV standard card type, the communication protocol information is protocol information that can identify an EMV standard card. For another example, in a scenario where a mobile terminal is bound to an access control card, if the target type is a radio frequency identification card type, the communication protocol information is protocol information that can identify a radio frequency identification card type card.

[0039] Step 206: According to the process, the mobile terminal obtains the communication protocol information fed back by the server; the communication protocol information includes communication protocol information that does not exist in the mobile terminal before triggering the process.

[0040] In the embodiments of this specification, the communication protocol information provided by the server may be the communication protocol information stored on the server for binding a card. Once the process for providing the communication protocol information is triggered, the server may send the communication protocol information stored on the server to the mobile terminal. To reduce the amount of information transmitted between the server and the mobile terminal, the communication protocol information provided by the server to the mobile terminal may include communication protocol information that was not present on the mobile terminal before the server provided the communication protocol information, allowing the mobile terminal to obtain communication protocol information that is not stored on the mobile terminal.

[0041] In actual applications, if the server does not have the communication protocol information that is not stored locally in the mobile terminal, the server may not return the communication protocol information to the mobile terminal.

[0042] Step 208: The mobile terminal saves the communication protocol information fed back by the server.

[0043] In the embodiment of this specification, the mobile terminal may store the communication protocol information sent by the server in a local storage unit, so as to perform card binding based on the locally stored communication protocol information.

[0044] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0045] Figure 2In the method, based on the status information of the mobile conversion, the server can send the communication protocol information required for the card binding service to the mobile terminal. The mobile terminal will save the acquired communication protocol information locally. Then, the mobile terminal can process the card binding service based on the locally stored communication protocol information. In this way, during the communication stage between the mobile terminal and the card during the card binding process, the mobile terminal can obtain the card information of the card based on the acquired communication protocol information used to identify the card information. The mobile terminal does not need to interact with the server every time it processes the card binding service, thereby reducing the time consumption of the card binding operation and improving the user experience during the card binding process. On the other hand, the communication protocol information can be maintained in the server, such as adding or expanding some communication protocol information that did not previously exist in the server. The server can also provide the newly expanded communication protocol information to the mobile terminal, so that the mobile terminal does not need to update the terminal application version, thereby further improving the user experience and reducing service costs.

[0046] based on Figure 2 The present specification also provides some specific implementation methods of the method, which are described below.

[0047] In the embodiments of this specification, the mobile terminal can be the active party in obtaining communication protocol information, and the server can feed back the communication protocol information to the mobile terminal based on the mobile terminal's request. Alternatively, the server can be the active party and proactively push the communication protocol information to the mobile terminal. The above two methods can be selected based on actual needs, and there is no limitation on this.

[0048] As an optional implementation, the above-mentioned obtaining the status information of the mobile terminal may specifically include: the mobile terminal obtaining the status information of the mobile terminal. Correspondingly, the above-mentioned process of triggering the server to provide communication protocol information based on the status information may specifically include: the mobile terminal sending a protocol acquisition request to the server based on the status information.

[0049] In the embodiments of this specification, a mobile terminal can obtain mobile terminal status information. After obtaining the mobile terminal status information, the mobile terminal can send a protocol acquisition request to a server based on the status information, so that the server returns communication protocol information to the mobile terminal in response to the received protocol acquisition request. The mobile terminal obtains the mobile terminal status information, eliminating the need for the server to obtain the mobile terminal status information. This reduces the server's workload and conserves server resources.

[0050] As another optional implementation, the above-mentioned obtaining of the status information of the mobile terminal may include: the server obtaining the status information of the mobile terminal. Correspondingly, the above-mentioned process of triggering the server to provide communication protocol information based on the status information may include: the server sending the communication protocol information to the mobile terminal based on the status information.

[0051] In the embodiments of this specification, a server can obtain status information from a mobile terminal. After obtaining the status information, the server can proactively send communication protocol information to the mobile terminal, causing the mobile terminal to store the communication protocol information. By obtaining the status information from the mobile terminal, the server can select appropriate timings to send protocol communication information to the mobile terminal, thereby reducing the workload of the mobile terminal. Furthermore, this can prevent interruptions to the server caused by the mobile terminal sending a request to obtain communication protocol information, thereby preventing disruption to the server's normal workflow.

[0052] In actual applications, in order to process the communication protocol information more efficiently, the server may provide the communication protocol information to the mobile terminal after the status information of the mobile terminal meets a preset condition.

[0053] In a scenario where a mobile terminal is the active party in obtaining communication protocol information, the step of determining the status may be performed by the mobile terminal. Optionally, the mobile terminal sends a protocol acquisition request to the server based on the status information. Specifically, the mobile terminal may determine whether the status of the mobile terminal satisfies a preset status based on the status information; and if the status of the mobile terminal satisfies the preset status, sending the protocol acquisition request to the server.

[0054] In the embodiments of this specification, after the mobile terminal obtains the mobile terminal's status information, the mobile terminal can determine whether the mobile terminal's status satisfies a preset state based on the obtained status information. If the mobile terminal determines that the mobile terminal's status satisfies the preset state, the mobile terminal can send a protocol acquisition request to the server, so that the server returns communication protocol information to the mobile terminal in response to the received protocol acquisition request. If the mobile terminal determines that the mobile terminal's status does not satisfy the preset state, the protocol acquisition request is not sent to the server. The mobile terminal can also continue to obtain subsequent status information of the mobile terminal, and after the mobile terminal's status satisfies the preset state, send a protocol acquisition request to the server. The mobile terminal determines the mobile terminal's status information, without the server having to determine the mobile terminal's status information, thereby reducing the server's workload and saving server resources.

[0055] In order to further improve the accuracy, in actual applications, after receiving the protocol acquisition request sent by the mobile terminal, the server can send a status information acquisition instruction to the mobile terminal. After receiving the status information returned by the mobile terminal in response to the status information acquisition instruction, the server verifies the status information. If the verification result indicates that the status of the mobile terminal meets the preset status, the communication protocol information is provided to the mobile terminal so that the mobile terminal saves the communication protocol information; if the verification result indicates that the status of the mobile terminal does not meet the preset status, the communication protocol information is not provided to the mobile terminal, and the verification result is sent to the mobile terminal so that the mobile terminal can further check the status of the mobile terminal.

[0056] In the embodiments of this specification, after the mobile terminal determines that the state of the mobile terminal satisfies a preset state, the server may further verify the state information to improve the accuracy of the determination of the state information. It is understood that the above-mentioned process of further verifying the state information determined by the mobile terminal to satisfy the preset state by the server may not be performed.

[0057] In a scenario where a mobile terminal is the active party in obtaining communication protocol information, the step of determining the status may also be performed by a server. Optionally, the mobile terminal sends a protocol acquisition request to the server based on the status information. Specifically, the mobile terminal sends a protocol acquisition request containing the status information to the server based on the status information; and the server determines, based on the status information, whether the status of the mobile terminal satisfies a preset status.

[0058] In the embodiments of this specification, after obtaining the mobile terminal's status information, the mobile terminal may send a protocol acquisition request containing the status information to the server. After receiving the protocol acquisition request sent by the mobile terminal, the server may parse the status information sent by the mobile terminal from the protocol acquisition request. The server may determine whether the status of the mobile terminal satisfies a preset status based on the received status information. If the status of the mobile terminal is determined to satisfy the preset status, the server may provide protocol communication information to the mobile terminal so that the mobile terminal saves the communication protocol information. If the status of the mobile terminal is determined not to satisfy the preset status, the server may not provide the protocol communication information to the mobile terminal.

[0059] In order to further improve the accuracy, in actual applications, if the server determines that the status of the mobile terminal does not meet the preset status, the server can also return the judgment result to the mobile terminal, and the mobile terminal can also verify the status of the mobile terminal based on the status information. If the verification result indicates that the status of the mobile terminal meets the preset status, the mobile terminal can re-send a protocol acquisition request containing the status information to the server, so that the server can re-determine whether the status of the mobile terminal meets the preset status based on the status information. After the server determines that the status of the mobile terminal does not meet the preset status, the mobile terminal can further verify the status information to improve the accuracy of the judgment on the status information. It can be understood that the above-mentioned operation of the server returning the judgment result to the mobile terminal and the mobile terminal verifying the status information based on the judgment result can also be omitted.

[0060] In actual applications, the mobile terminal may also send a protocol acquisition request containing identification information representing the status information to the server, so as to reduce the amount of data sent to the server and save storage resources and network resources of the server.

[0061] In the scenario where the server is the active party sending the communication protocol information, the step of determining the status may be performed by the server. Optionally, the server sending the communication protocol information to the mobile terminal based on the status information may include: the server determining whether the status of the mobile terminal meets a preset status based on the status information; and if the status of the mobile terminal meets the preset status, sending the communication protocol information to the mobile terminal.

[0062] In an embodiment of the present specification, after the server obtains the status information of the mobile terminal, the server can determine whether the status of the mobile terminal meets the preset status based on the obtained status information. If the server determines that the status of the mobile terminal meets the preset status, the server can actively send communication protocol information to the mobile terminal so that the mobile terminal can save the communication protocol information.

[0063] If the server determines that the mobile terminal's status does not meet the preset conditions, the server may not send the communication protocol information to the mobile terminal. Instead, the server may continue to obtain subsequent status information from the mobile terminal and only send the communication protocol information to the mobile terminal after the mobile terminal's status meets the preset conditions. After obtaining the mobile terminal's status information, the server may determine that the mobile terminal's status meets the preset conditions before providing the communication protocol information to the mobile terminal, thereby reducing the workload of the mobile terminal. Furthermore, this also avoids interruptions to the server caused by the mobile terminal sending a request to obtain communication protocol information, thereby preventing disruption to the server's normal workflow.

[0064] In the embodiments of this specification, the status information of the mobile terminal may include at least one of the following information: the current time information of the mobile terminal, communication protocol information for card binding stored in the mobile terminal, validity status information of the communication protocol information for card binding stored in the mobile terminal, application identification information of the application currently launched by the mobile terminal, identification information of the page currently displayed by the mobile terminal, identification information of the network currently connected to the mobile terminal, and device attribute information of the mobile terminal. The device attribute information of the mobile terminal may include at least one of the type of operating system of the operating device, the version of the operating system of the device, the model of the device, and the brand of the device. One or more embodiments are proposed for determining whether the status of the mobile terminal meets a preset status.

[0065] Optionally, the preset state is the state in which the server provides the communication protocol information; the judgment of whether the state of the mobile terminal meets the preset state may include at least one of the following: judging whether the current time of the mobile terminal reaches the cycle time for obtaining the communication protocol information; judging whether there is communication protocol information in the server that does not exist in the mobile terminal; judging whether the mobile terminal displays the card binding page; judging whether the mobile terminal starts the target application; the target application is an application that provides card binding services; judging whether the mobile terminal successfully parses the near-field communication response information provided by the card to be bound using the existing communication protocol information; judging whether the mobile terminal is connected from the first network to the second network; the network parameters of the second network are better than the network parameters of the first network; the network parameters include at least one of signal strength, data transmission speed, and delay time; judging whether the existing communication protocol information in the mobile terminal has expired; judging whether the device attributes of the mobile terminal are preset attributes; the device attributes include at least one of device system type, device system version, device model, and device brand.

[0066] In the embodiments of this specification, the preset state may be a state that satisfies the conditions for the server to provide communication protocol information to the mobile terminal. The state of the mobile terminal may be state information of the mobile terminal obtained by the mobile terminal or the server, or a terminal state further determined based on the obtained state information. If the mobile terminal is the active party in obtaining communication protocol information, the mobile terminal may determine whether the state of the mobile terminal satisfies the preset state; if the server is the active party in sending communication protocol information, the server may determine whether the state of the mobile terminal satisfies the preset state.

[0067] In the embodiment of this specification, the periodic time may refer to the time when the mobile terminal periodically obtains the communication protocol information from the server.

[0068] As an embodiment, the determination of whether the current time of the mobile terminal has reached the cycle time for obtaining the communication protocol information may include: determining whether the time interval between the current time and the time when the mobile terminal last obtained the communication protocol information is greater than or equal to the cycle time. If the current time of the mobile terminal has not reached the cycle time for obtaining the communication protocol information, that is, the time interval between the current time and the time when the mobile terminal last obtained the communication protocol information is less than the cycle time, it indicates that the state of the mobile terminal does not meet the preset state, and the process of the server providing the communication protocol information may not be triggered. If the current time of the mobile terminal has reached the cycle time for obtaining the communication protocol information, that is, the time interval between the current time and the time when the mobile terminal last obtained the communication protocol information is greater than or equal to the cycle time, it indicates that the state of the mobile terminal meets the preset state, and the process of the server providing the communication protocol information may be triggered.

[0069] In the embodiments of this specification, the cycle time may also refer to the time at which the server periodically sends communication protocol information to the mobile terminal. Determining whether the current time of the mobile terminal has reached the cycle time for obtaining communication protocol information may also be equivalent to determining whether the current time of the server has reached the cycle time for sending communication protocol information. As an embodiment, determining whether the current time of the server has reached the cycle time for sending communication protocol information may specifically include determining whether the time interval between the current time of the server and the last time the server sent communication protocol information is greater than or equal to the cycle time for sending communication protocol information. If the current time of the server has not reached the cycle time for sending communication protocol information, that is, the time interval between the current time of the server and the last time the server sent communication protocol information is less than the cycle time for sending communication protocol information, then it indicates that the status of the mobile terminal does not meet the preset status, and the process of the server providing communication protocol information may not be triggered. If the current time of the server has reached the cycle time for sending communication protocol information, that is, the time interval between the current time of the server and the last time the server sent communication protocol information is greater than or equal to the cycle time for sending communication protocol information, then it indicates that the status of the mobile terminal meets the preset status, and the process of the server providing communication protocol information may be triggered. In actual applications, after determining whether the current time of the mobile terminal has reached the cycle time for obtaining the communication protocol information and obtaining the judgment result, one or more other conditions can be further judged, and based on the judgment results of the other one or more conditions, it is determined whether the status of the mobile terminal meets the preset status.

[0070] In an embodiment of the present specification, it is determined whether there is communication protocol information in the server that does not exist in the mobile terminal. If there is communication protocol information in the server that does not exist in the mobile terminal, it indicates that the state of the mobile terminal meets the preset state, and the process of the server providing the communication protocol information can be triggered. If there is no communication protocol information in the server that does not exist in the mobile terminal, it indicates that the state of the mobile terminal does not meet the preset state, and the process of the server providing the communication protocol information may not be triggered. In actual applications, after determining whether there is communication protocol information in the server that does not exist in the mobile terminal and obtaining a determination result, one or more other conditions can be further determined, and based on the determination result of the other one or more conditions, it is determined whether the state of the mobile terminal meets the preset state.

[0071] In actual applications, if the server has communication protocol information that the mobile terminal does not have, the mobile terminal may send a request to the server to obtain the communication protocol information, or the server may send the communication protocol information to the mobile terminal.

[0072] In an embodiment of this specification, the card binding page may be a page for binding a mobile terminal to a card, such as a page for filling in the card information of a card during the card binding process. Determine whether the mobile terminal displays the card binding page. If the mobile terminal displays the card binding page, it indicates that the state of the mobile terminal meets the preset state, and the process for the server to provide communication protocol information may be triggered. If the mobile terminal does not display the card binding page, it indicates that the state of the mobile terminal does not meet the preset state, and the process for the server to provide communication protocol information may not be triggered. In actual applications, after determining whether the mobile terminal displays the card binding page and obtaining a judgment result, one or more other conditions may be further determined, and based on the judgment result of the other one or more conditions, determine whether the state of the mobile terminal meets the preset state. There is no limitation on this.

[0073] In actual applications, if the mobile terminal enters the card binding page, the mobile terminal may send a request to the server to obtain the communication protocol information, or the server may actively send the communication protocol information to the mobile terminal.

[0074] In the embodiments of this specification, it is determined whether the mobile terminal has launched a target application; the target application is an application that provides a card binding service. If the mobile terminal has launched the target application, it indicates that the status of the mobile terminal meets the preset status, and a process for the server to provide communication protocol information may be triggered. If the mobile terminal has not launched the target application, it indicates that the status of the mobile terminal does not meet the preset status, and the process for the server to provide communication protocol information may not be triggered.

[0075] In actual applications, after determining whether the mobile terminal has launched the target application and obtaining a determination result, one or more other conditions may be further determined, and based on the determination results of the other one or more conditions, whether the state of the mobile terminal satisfies a preset state is determined. This is not limited to this.

[0076] In actual applications, if the target application providing the card binding service is started, the mobile terminal may send a request to the server to obtain the communication protocol information, or the server may actively send the communication protocol information to the mobile terminal.

[0077] In an embodiment of this specification, it is determined whether the mobile terminal successfully parses the near-field communication response information provided by the card to be bound using the existing communication protocol information. If the mobile terminal fails to successfully parse the near-field communication response information provided by the card to be bound using the existing communication protocol information, it indicates that the status of the mobile terminal meets the preset status, and the process of the server providing the communication protocol information can be triggered. If the mobile terminal successfully parses the near-field communication response information provided by the card to be bound using the existing communication protocol information, it indicates that the status of the mobile terminal does not meet the preset status, and the process of the server providing the communication protocol information can be not triggered. In actual applications, it is also possible to determine whether to trigger the process of the server providing the communication protocol information based on multiple conditions. For example, after determining whether the mobile terminal successfully parses the near-field communication response information provided by the card to be bound using the existing communication protocol information and obtaining a judgment result, it is possible to further determine one or more other conditions, and determine whether the status of the mobile terminal meets the preset status based on the judgment results of the one or more other conditions. This is not limited to this.

[0078] In actual applications, after the mobile terminal obtains the card information of the card, if the card information cannot be parsed based on the local communication protocol information of the mobile terminal, the mobile terminal can send a request to obtain the communication protocol information to the server, or the server can actively send the communication protocol information to the mobile terminal.

[0079] In an embodiment of this specification, it is determined whether the mobile terminal is connected from the first network to the second network; the network parameters of the second network are better than the network parameters of the first network; the network parameters include at least one of signal strength, data transmission speed, and delay time. If the mobile terminal is connected from the first network to the second network, it means that the state of the mobile terminal meets the preset state, and the process of the server providing communication protocol information can be triggered. If the mobile terminal is not connected from the first network to the second network, it means that the state of the mobile terminal does not meet the preset state, and the process of the server providing communication protocol information may not be triggered. In actual applications, after determining whether the mobile terminal is connected from the first network to the second network and obtaining a judgment result, one or more other conditions can be further determined, and based on the judgment results of the other one or more conditions, it is determined whether the state of the mobile terminal meets the preset state. This is not limited.

[0080] In actual applications, if the network signal of the mobile terminal is enhanced, and / or the network speed is increased, and / or the network delay time is shortened, the mobile terminal can send a request to the server to obtain communication protocol information, or the server can actively send communication protocol information to the mobile terminal when it determines that the network signal of the mobile terminal is enhanced, and / or the network speed is increased, and / or the network delay time is shortened.

[0081] In the embodiments of this specification, it is determined whether the existing communication protocol information in the mobile terminal has expired. If the existing communication protocol information in the mobile terminal has expired, it indicates that the status of the mobile terminal meets the preset status, and a process for the server to provide the communication protocol information may be triggered. If the existing communication protocol information in the mobile terminal has not expired, it indicates that the status of the mobile terminal does not meet the preset status, and the process for the server to provide the communication protocol information may not be triggered.

[0082] In actual applications, after determining whether the existing communication protocol information in the mobile terminal has expired and obtaining a determination result, one or more other conditions may be further determined, and based on the determination results of the other one or more conditions, whether the status of the mobile terminal satisfies a preset status is determined. This is not limited to this.

[0083] In actual applications, if the existing communication protocol information in the mobile terminal is invalid, the mobile terminal may send a request to the server to obtain the communication protocol information, or the server may actively send the communication protocol information to the mobile terminal.

[0084] In the embodiments of this specification, it is determined whether the device attribute of the mobile terminal is a preset attribute; the device attribute includes at least one of the device system type, device system version, device model, and device brand. If the device attribute of the mobile terminal is a preset attribute, it indicates that the status of the mobile terminal meets the preset status, and a process for the server to provide communication protocol information may be triggered. If the device attribute of the mobile terminal is not a preset attribute, it indicates that the status of the mobile terminal does not meet the preset status, and the process for the server to provide communication protocol information may not be triggered.

[0085] In actual applications, after determining whether the device attributes of the mobile terminal meet the preset attributes and obtaining a determination result, one or more other conditions may be further determined, and based on the determination results of the other one or more conditions, whether the state of the mobile terminal meets the preset state is determined. This is not limited to this.

[0086] In actual applications, the server can deploy communication protocol information for a mobile terminal with a first device attribute in a first time period. The first device attribute may include at least one of a first device system type (such as Android), a first device system version (such as Android 12 version), a first device model (such as device A model 10), and a first device brand (such as the brand of device A). If, in the first time period, the communication protocol information terminal runs well on the mobile terminal with the first device attribute, the server can deploy communication protocol information for a mobile terminal with a second device attribute in a second time period. The second device attribute may include at least one of a second device system type (such as IOS), a second device system version (such as Android 13 version), a second device model (such as device A model 11), and a second device brand (such as the brand of device B).

[0087] In practical applications, the mobile terminal's location information can also be used to determine whether the mobile terminal's status satisfies a preset state. If the mobile terminal's location information changes, it can be determined that the mobile terminal's status satisfies the preset state. For example, if the mobile terminal user is from Country A and enters Country B from Country A, the mobile terminal can send a request to the server to obtain communication protocol information, or the server can proactively send the communication protocol information to the mobile terminal.

[0088] In the embodiments of this specification, multiple judgment conditions can also be used to determine whether the status of the mobile terminal meets the preset status. For example: if the current time of the mobile terminal has not reached the cycle time for obtaining communication protocol information, it is determined whether the existing communication protocol information in the mobile terminal has expired. If the existing communication protocol information in the mobile terminal has expired, it indicates that the status of the mobile terminal meets the preset status; if the existing communication protocol information in the mobile terminal has not expired, it indicates that the status of the mobile terminal does not meet the preset status. For another example: if the current time of the mobile terminal reaches the cycle time for obtaining communication protocol information, it is determined whether the mobile terminal is connected from the first network to the second network (the network parameters of the second network are better than the network parameters of the first network). If the mobile terminal is not connected from the first network to the second network, it indicates that the status of the mobile terminal does not meet the preset status; if the mobile terminal is connected from the first network to the second network, it indicates that the status of the mobile terminal meets the preset status. In actual applications, it is reasonable to select the content of further judgment of one or more other conditions, and this is not limited.

[0089] In an embodiment of this specification, the mobile terminal can obtain the communication protocol information provided by the server before performing the card binding service, and the mobile terminal can perform the card binding service based on the communication protocol information saved by the terminal. In an embodiment of this specification, after the mobile terminal saves the communication protocol information, a specific embodiment is also proposed for the method of binding the mobile terminal to the card. Optionally, after saving the communication protocol information, it can also include: the mobile terminal obtains a first operation performed by the user to obtain card information by means of near-field communication; based on the first operation, sends instruction information by means of the near-field communication; obtains response information fed back by the target card in response to the instruction information; uses the first communication protocol information selected from the various communication protocol information saved in the mobile terminal to parse the response information to obtain the card information of the target card; and displays the card information on the card binding page.

[0090] In the embodiments of this specification, the first operation may be an operation used by a user to obtain card information via near-field communication, such as a click, slide, or select operation on a card binding control within a mobile terminal's card binding trigger page. If a card is already bound to the mobile terminal or the target application of the mobile terminal, the bound card information may also be displayed on the card binding trigger page. The instruction information may be an instruction for requesting the target card to return card information to the mobile terminal, and the response information may be the card information of the target card.

[0091] Figure 3 This is a schematic diagram of a card binding triggering page provided in an embodiment of this specification. Figure 3As shown, the card binding trigger page may include a first area 301 for binding a card via near-field communication, and / or a second area 302 for adding a new card by entering a card number, and / or a third area 303 for adding a new card by taking a photo. If a card has already been bound to the mobile terminal or the target application of the mobile terminal, the page may also include a bound card area 304 that displays the user's bound cards.

[0092] In the embodiments of this specification, after a first operation is triggered, the mobile terminal generates instruction information for obtaining the card information of a target card in response to the first operation and transmits the instruction information to the target card via near-field communication. In actual applications, the mobile terminal may generate the instruction information based on one of the locally stored communication protocol information for card binding.

[0093] In the embodiments of this specification, the target card may be a card located near the mobile terminal, and may also be referred to as a card to be bound. After the target card receives the instruction information sent by the mobile terminal, it may feedback corresponding response information to the mobile terminal in response to the instruction information. In actual applications, the instruction information may be information generated by the mobile terminal in accordance with the protocol requirements of the determined communication protocol information. If the communication protocol information corresponding to the target card is consistent with the determined communication protocol information, the target card may recognize the instruction information and feedback response information to the mobile terminal in response to the instruction information. If the communication protocol information corresponding to the target card is inconsistent with the determined communication protocol information, the target card may not recognize the instruction information and may not feedback any response information to the mobile terminal. In actual applications, even if the communication protocol information corresponding to the target card is inconsistent with the determined communication protocol information, the target card may still recognize the instruction information sent by the mobile terminal and feedback response information. Whether the target card needs to correctly recognize the instruction information is not specifically limited here.

[0094] In the embodiments of this specification, the information stored in the target card or the feedback information fed back to the mobile terminal via near-field communication complies with the communication protocol information rules corresponding to the target card. If the communication protocol information corresponding to the target card is inconsistent with the determined communication protocol information, the mobile terminal will not be able to obtain a correct parsing result if it parses the obtained response information according to the determined communication protocol information.

[0095] In an embodiment of this specification, after the mobile terminal receives a response from the target card, it can parse the response using first communication protocol information selected from various communication protocol information stored in the mobile terminal to obtain the target card's card information, where the card information may include the target card's card number, the target card's expiration date, the target card's bank account, and the target card's corresponding user information. The mobile terminal can display the parsed card information from the response on a card binding page for user verification. If the mobile terminal receives a confirmation action from the user regarding the card information displayed on the card binding page, it can proceed with subsequent operations in the card binding process.

[0096] In the embodiments of this specification, the card binding trigger page may be a page generated by a mobile terminal, or may be a page generated by a server, which is not limited thereto.

[0097] In the embodiments of this specification, the communication protocol information is stored in the mobile terminal, so that the card binding operation can be performed based on the communication protocol information locally in the mobile terminal. There is no need for the mobile terminal to interact with the server every time the information in the card is obtained through near-field communication. The mobile terminal can execute based on the local existing information to improve the efficiency of card binding.

[0098] In the embodiments of this specification, a specific embodiment is also provided for a method of transmitting instruction information by a mobile terminal. Optionally, the method may further include: the mobile terminal transmitting an electromagnetic signal for triggering near-field communication; and determining, based on the electromagnetic signal, whether a card with near-field communication functionality is present near the mobile terminal. Accordingly, transmitting the instruction information via near-field communication may specifically include: transmitting the instruction information via near-field communication if a card with near-field communication functionality is present near the mobile terminal.

[0099] In the embodiments of this specification, the mobile terminal can be the card reader end, and the card can be the tag end. The mobile terminal is responsible for generating electromagnetic signals and sending electromagnetic information for triggering near-field communication. The card is responsible for receiving electromagnetic signals. After the user clicks or slides the card binding control in the mobile terminal, the mobile terminal can start the card reader mode and send out an electromagnetic signal.

[0100] In an embodiment of the present specification, the determination of whether there is a card with a near-field communication function near the mobile terminal based on the electromagnetic signal may include: determining whether the decrease in the signal strength of the electromagnetic signal emitted by the mobile terminal within a preset time period is greater than or equal to a preset threshold value; if the decrease in the signal strength within the preset time period is greater than or equal to the preset threshold value, it indicates that there is a card with a near-field communication function near the mobile terminal; if the decrease in the signal strength within the preset time period is less than the preset threshold value, it indicates that there is no card with a near-field communication function near the mobile terminal. In actual applications, a card with a near-field communication function can receive the electromagnetic signal sent by the mobile terminal through its own antenna. Once the electromagnetic signal is received, near-field communication can be established between the card and the mobile device, and communication parameters of the near-field communication, such as communication speed and mode, can be determined.

[0101] In the embodiment of this specification, if there is a card with near field communication function near the mobile terminal, the mobile terminal generates instruction information for obtaining card information of the card and sends the instruction information to the card with near field communication function via near field communication.

[0102] In the embodiments of this specification, a specific embodiment is also proposed for the method of parsing the response information fed back by the card.

[0103] Optionally, the use of first communication protocol information selected from various communication protocol information saved in the mobile terminal to parse the response information to obtain the card information of the target card can specifically include: using the first communication protocol information to parse and process the response information, if the response information can be successfully parsed, the card information of the target card is obtained; if the response information cannot be successfully parsed, selecting second communication protocol information from the various communication protocol information; using the second communication protocol information to parse the response information to obtain the card information of the target card.

[0104] In actual applications, if the selected first communication protocol information is consistent with the communication protocol information corresponding to the response information fed back by the card, the mobile terminal can successfully parse the response information based on the first communication protocol information to obtain the card information of the target card. Successfully parsing the response information can mean processing the response information in accordance with the protocol rules of the first communication protocol information to obtain information that meets preset rules. For example, a character string with a preset number of digits, a character string starting at a preset character, a character string whose constituent elements or structure meet preset requirements, etc. can be obtained. For example, assuming that the card information contains the card number of a certain bank card, and in actual applications, the correct card number is 19 digits, if the parsed card information contains a character string consisting of 19 digits, it can be indicated that the parsing was successful. If the parsed card information does not contain a character string consisting of 19 digits, it can be indicated that the parsing was unsuccessful. If the first communication protocol information is inconsistent with the communication protocol information corresponding to the response information, the mobile terminal will not be able to successfully parse the response information based on the first communication protocol information. The mobile terminal may then select second communication protocol information from the various communication protocol information stored in the mobile terminal and use the second communication protocol information to parse the response information. If the second communication protocol information cannot successfully parse the response information, the mobile terminal may select third communication protocol information from the various communication protocol information stored in the mobile terminal and use the third communication protocol information to parse the response information. The mobile terminal iteratively selects various communication protocol information stored in the mobile terminal until the response information is successfully parsed and the card information of the target card is obtained. The first communication protocol information, the second communication protocol information, and the third communication protocol information are all different from each other.

[0105] In an embodiment of the present specification, if the mobile terminal cannot successfully parse the response information fed back by the card based on the selected first communication protocol information, it can also select the second communication protocol information to parse the response information, and iterate in sequence until the response information is successfully parsed, thereby improving the success rate of parsing the response information.

[0106] In the embodiments of this specification, a specific embodiment is also proposed for selecting first communication protocol information from various communication protocol information stored in a mobile terminal. Optionally, the selecting of first communication protocol information from various communication protocol information stored in the mobile terminal may include at least one of the following methods: randomly selecting first communication protocol information from the various communication protocol information; selecting first communication protocol information commonly used by the mobile terminal from the various communication protocol information; selecting first communication protocol information most recently used by the mobile terminal in a card binding service from the various communication protocol information; selecting first communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal from the various communication protocol information; or selecting the first communication protocol information most recently saved in the mobile terminal from the various communication protocol information.

[0107] In an embodiment of this specification, the method of randomly selecting the first communication protocol information from the various communication protocol information may include: determining the communication protocol information stored in any manner, such as the earliest saved communication protocol information, the communication protocol information to be saved at a certain moment, or the most recently saved communication information, as the randomly selected communication protocol information. The first communication protocol information is randomly selected from the various communication protocol information so that each piece of communication protocol information has an equal probability of being selected, thereby improving the equality of the probability of each piece of communication protocol information being selected.

[0108] In an embodiment of the present specification, a method for selecting the first communication protocol information frequently used by the mobile terminal from the various communication protocol information may include: determining the frequently used communication protocol information from the communication protocol information that has been used a preset number of times within a recent preset period of time, etc. Selecting the frequently used communication protocol information as the selected communication protocol information can improve the success rate of the first communication protocol information being able to successfully parse the response information. For example, the communication protocol information used within the last year or six months can be sorted by the number of times used, and the communication protocol information with the highest number of times used or with a number of times used exceeding a preset number of times can be determined as the frequently used communication protocol information.

[0109] In an embodiment of this specification, selecting the first communication protocol information most recently used by the mobile terminal in a card binding service from the various communication protocol information may include: determining, based on the time of card binding services previously processed by the mobile terminal, the communication protocol information used for one or more recent card binding services. Alternatively, the mobile terminal may record local time information, such as a timestamp, when each communication protocol information was used, and determining the most recent communication protocol information used by the mobile terminal based on this time information. Selecting the communication protocol information most recently used in a card binding service as the selected communication protocol information can increase the success rate of the first communication protocol information being able to successfully parse the response information.

[0110] In an embodiment of the present specification, a method of selecting the first communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal from the various communication protocol information may include: determining the communication protocol information used in the country corresponding to the nationality of the terminal user as the communication protocol information corresponding to the country of the terminal user; or determining the communication protocol information used in the area corresponding to the location of the terminal user as the communication protocol information corresponding to the location of the terminal user. The communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal can be understood as the communication protocol information frequently used in the nationality or location of the terminal user of the mobile terminal. Using the communication protocol information frequently used in the nationality or location of the terminal user of the mobile terminal as the selected communication protocol information can improve the success rate of the first communication protocol information in successfully parsing the response information.

[0111] In an embodiment of the present specification, a method of selecting the first communication protocol information most recently saved in the mobile terminal from the various communication protocol information may include: determining the communication protocol information corresponding to the saving moment with the smallest time interval between the saving moment and the current moment as the most recently saved communication protocol information. For any communication protocol information in the mobile terminal, the mobile terminal may record the time information of obtaining the communication protocol information after obtaining the communication protocol information, and the time information may represent the above-mentioned saving moment. The current moment may be the moment when the card is identified, or the moment when the user-executed triggering card binding service is obtained, or the moment when the mobile terminal renders or displays the above-mentioned card binding trigger page, etc., which is not specifically limited here. Using the communication protocol information most recently saved in the mobile terminal as the selected communication information can improve the success rate of the first communication protocol information in successfully parsing the response information.

[0112] In actual applications, the first communication protocol information can also be selected according to various selection criteria. For example, a first plurality of communication protocol information commonly used by the mobile terminal can be randomly selected from the various communication protocol information, and then the first communication protocol information most recently used by the mobile terminal in the card binding service can be selected from the second plurality of communication protocol information. For another example, a second plurality of communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal can be selected from the various communication protocol information, and then the first communication protocol information most recently saved in the mobile terminal can be selected from the second plurality of communication protocol information. The first communication protocol information can also be selected according to other preset rules, which are not limited to this.

[0113] In the embodiments of this specification, the first communication protocol information can be selected from various communication protocol information stored in the mobile terminal through multiple selection methods, thereby increasing the diversity of selection methods for selecting the first communication protocol information.

[0114] In the embodiments of this specification, the selection of the second communication protocol information from the various communication protocol information specifically includes at least one of the following: randomly selecting the second communication protocol information from the various communication protocol information; selecting the second communication protocol information commonly used by the mobile terminal from the various communication protocol information; selecting the second communication protocol information most recently used by the mobile terminal in a card binding service from the various communication protocol information; selecting the second communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal from the various communication protocol information; or selecting the second communication protocol information most recently saved to the mobile terminal from the various communication protocol information. The method for selecting the second communication protocol information can refer to the method for selecting the first communication protocol information and will not be repeated here.

[0115] In actual applications, the first communication protocol information may be selected according to the first selection method, and the second communication rule may be selected according to the second selection method. For example, the first communication protocol information may be selected randomly from the various communication protocol information, and the second communication protocol information may be selected by selecting the communication protocol information commonly used by the mobile terminal from the various communication protocol information. This is not limited to the above.

[0116] In the embodiments of this specification, in order to reduce the pressure on the server, the mobile terminal may first try to obtain the card information using the local existing communication protocol information. If the information cannot be obtained correctly, the mobile terminal may then obtain the communication protocol information from the server.

[0117] Optionally, before obtaining the mobile terminal's status information, the method may further include: obtaining, by the mobile terminal, response information provided by a card with near-field communication functionality in response to the mobile terminal via near-field communication; and parsing the response information using at least one existing communication protocol information already stored in the mobile terminal. Correspondingly, obtaining the mobile terminal's status information may specifically include obtaining result information indicating that the mobile terminal failed to successfully parse the response information using the at least one existing communication protocol information.

[0118] In the embodiments of this specification, the response information may be information including card information of the card. The at least one existing communication protocol information may be one type of existing communication protocol information, or multiple types of existing communication protocol information, or may be all types of existing communication protocol information. The result information may be information indicating that the response information could not be successfully parsed using one type of existing communication protocol information. The result information may also be information indicating that the response information could not be successfully parsed using a second type of existing communication protocol information after the first type of existing communication protocol information failed to successfully parse the response information. The result information may also be information indicating that the response information could not be successfully parsed using multiple or all types of existing communication protocol information.

[0119] In an embodiment of the present specification, after the mobile terminal obtains a trigger operation performed by the user to obtain card information through near-field communication, the mobile terminal can send an electromagnetic signal that triggers near-field communication to the surrounding area of ​​the mobile terminal. If the mobile terminal monitors that the decrease in the signal strength of the electromagnetic signal sent within a preset time period is greater than or equal to a preset threshold, the mobile terminal can determine that there is a card with near-field communication function nearby, and then the mobile terminal can send instruction information for obtaining card information to the card. After receiving the instruction information sent by the mobile terminal, the card can feedback response information containing card information to the mobile terminal. For the response information fed back by the card, the mobile terminal can try to select the first existing communication protocol information from the various existing communication protocol information already in the mobile terminal; the mobile terminal uses the first existing communication protocol information to parse the response information. If the parsing is unsuccessful, the mobile terminal sends a communication protocol information acquisition request to the server, or the mobile terminal can try again to select the second existing communication protocol information from the various existing communication protocol information already in the mobile terminal. If the parsing is still unsuccessful, the mobile terminal sends a communication protocol information acquisition request to the server, or the mobile terminal can continue to try to select the third existing communication protocol information, and repeat the operation until the number of unsuccessful parsing reaches a preset number, then the mobile terminal sends a communication protocol information acquisition request to the server; or after the mobile terminal has selected all the existing communication protocol information already in the mobile terminal and still cannot parse successfully, the mobile terminal sends a communication protocol information acquisition request to the server.

[0120] As another embodiment, after the mobile terminal obtains the trigger operation performed by the user to obtain card information through near-field communication, or after the mobile terminal determines that there is a card nearby, the mobile terminal can select a first existing communication protocol information from various existing communication protocol information already in the mobile terminal, and send instruction information through the near-field communication according to the protocol rules of the first existing communication protocol information. If the mobile terminal does not obtain the response information fed back by the card within a preset time period, the mobile terminal can send a communication protocol information acquisition request to the server, or it can also select a second existing communication protocol information from various existing communication protocol information already in the mobile terminal, and send instruction information according to the protocol rules of the second existing communication protocol information. The protocol rules send instruction information through the near-field communication method. If the mobile terminal does not obtain the response information fed back by the card within the preset time period, the mobile terminal can send a communication protocol information acquisition request to the server, or can also select a third existing communication protocol information from the various existing communication protocol information already in the mobile terminal, and repeat the operation until the number of times that the response information fed back by the card cannot be obtained reaches a preset number, then the mobile terminal can send a communication protocol information acquisition request to the server; or after the mobile terminal has selected all the existing communication protocol information already in the mobile terminal, it still cannot obtain the response information fed back by the card, then the mobile terminal can send a communication protocol information acquisition request to the server.

[0121] In the embodiment of this specification, the mobile terminal will only request new communication protocol information from the server when all the existing communication protocol information saved by the mobile terminal cannot successfully parse the response information fed back by the card, thereby avoiding the defect of requesting communication protocol information from the server for each card binding task of the mobile terminal.

[0122] In the embodiments of this specification, the server may provide full communication protocol information to the mobile terminal, or may provide communication protocol information not present in the mobile terminal. Optionally, the communication protocol information fed back by the server is communication protocol information that did not exist in the mobile terminal before the process was triggered; alternatively, the communication protocol information fed back by the server is the full communication protocol information present in the server.

[0123] In an embodiment of the present specification, before the server sends communication protocol information to the mobile terminal, the mobile terminal may send the protocol identifiers of each communication protocol information locally stored in the mobile terminal to the server, so that the server can obtain the various existing communication protocol information locally stored in the mobile terminal based on the protocol identifiers sent by the mobile terminal, and then determine the various communication protocol information that does not exist in the mobile terminal, and send the determined various communication protocol information that does not exist in the mobile terminal to the mobile terminal.

[0124] In actual applications, the server can record information about each communication protocol information that has been sent to the mobile terminal. For example, the server can record which communication protocol information has been sent to which mobile terminals. When the server sends the communication protocol information again, it can determine the communication protocol information that has been sent to the mobile terminal based on the server's recorded information, that is, it can determine the various existing communication protocol information locally saved in the mobile terminal. Then, the server can determine the communication protocol information that has not been sent to the mobile terminal, that is, it can determine the various communication protocol information that does not exist in the mobile terminal. The server can send the various communication protocol information that has been determined to not exist in the mobile terminal to the mobile terminal.

[0125] In actual applications, communication protocol information can be maintained on the server side. If developers or managers determine new communication protocol information, the new communication protocol information can be saved on the server. The server can actively push the new communication protocol information to the mobile terminal, or the mobile terminal can also actively request the server to send the new communication protocol information.

[0126] In the embodiments of this specification, the communication protocol information provided by the server to the mobile terminal can be provided to the mobile terminal in at least one of the forms of components, modules, plug-ins, etc., and the mobile terminal does not need to update the entire application client.

[0127] In an embodiment of the present specification, the server can send the full communication protocol information in the server to the mobile terminal based on the triggered process of the server providing communication protocol information, so that the mobile terminal can update the various communication protocol information saved locally based on the full communication protocol information and supplement the communication protocol information not saved locally.

[0128] In an embodiment of the present specification, the server can pre-generate a public-private key pair, store the private key of the key pair at the server, and send the public key of the key pair to the mobile terminal so that the mobile terminal can store the public key. In actual applications, before sending the communication protocol information to the mobile terminal, the server can use the private key to encrypt the communication protocol information to be sent, and send the encrypted communication protocol information to the mobile terminal. After the mobile terminal receives the encrypted communication protocol information, it can use the locally stored public key to decrypt the encrypted communication protocol information to obtain the communication protocol information, thereby improving the security of the communication protocol information to be sent. In actual applications, the server can compress the communication protocol information to be sent based on a preset compression rule, and send the compressed communication protocol information to the mobile terminal. After receiving the compressed communication protocol information, the mobile terminal uses the decompression rule corresponding to the preset compression rule to decompress the compressed communication protocol information to obtain the communication protocol information, thereby reducing the amount of transmission data of the communication protocol information to be sent and saving network transmission resources.

[0129] In actual applications, the server can also encrypt and compress the communication protocol information to be sent, and send the processed communication protocol information to be sent to the mobile terminal. This can not only improve the security of the communication protocol information to be sent, but also reduce the amount of transmission data of the communication protocol information to be sent, thereby saving network transmission resources.

[0130] Based on Figure 2 With the same idea as the solution shown in , the embodiment of this specification also provides a card binding method based on near field communication. Figure 4 This is a flowchart of a card binding method based on near field communication provided in an embodiment of this specification.

[0131] From a program perspective, the process execution entity can include a program installed on a mobile terminal for card binding based on near-field communication. From a hardware perspective, the process execution entity can include a mobile terminal. It is understood that a mobile terminal can be any device, equipment, platform, or device cluster with computing and processing capabilities.

[0132] like Figure 4 As shown, the process may include the following steps.

[0133] Step 402: The mobile terminal obtains the card binding triggering operation performed by the user.

[0134] In the embodiments of this specification, the card binding triggering operation may be an operation for triggering the card binding process. For example, it may be a triggering operation on a card binding control for performing card binding in a target application on a mobile terminal, or a triggering operation on a preset button on the mobile terminal, where the preset button may be a power button, a volume button, etc. The target application may be the application for performing card binding.

[0135] For example, Figure 5A This is a page diagram of a target application provided by the embodiment of this specification. Figure 5A As shown, this page can be the homepage of the target application, which may include a control 501 for executing the card binding process. When the user clicks control 501, the card binding process can be triggered. This page may also include controls such as "Scan," "Payment," "Travel," and "Card Wallet" for quickly launching corresponding functions, as well as labels for various applications.

[0136] It should be noted that the card binding trigger operation may also be an operation performed by the user on controls for card binding on other pages, such as an operation performed by the user on controls displayed on the above-mentioned card binding trigger page, etc., and this is not limited to this.

[0137] In practical applications, the card binding triggering operation may also be the first operation performed by the user to obtain card information via near-field communication after obtaining the communication protocol information provided by the server, as described in the above embodiment. After the user triggers the card binding triggering operation, the mobile terminal and / or the server may execute the corresponding card binding process.

[0138] For example, Figure 5B This is another page diagram of a target application provided by the embodiment of this specification. Figure 5B As shown, the page may include a control 505 for triggering the card binding process via near-field communication. If the user operates on control 505, the mobile terminal may execute the card binding process to obtain card information via near-field communication. The page may also include a control 502 for manually entering the card number, a control 503 for entering the card number by taking a photo, or a control 504 for submitting the card number.

[0139] Figure 5A or Figure 5B It can also represent the card binding trigger page introduced in the above embodiment. In actual application, during the card binding process, the terminal can display Figure 5A as well as Figure 5B , for example, you can first display Figure 5A Show later Figure 5B The mobile terminal can start the NFC card reader function when the user Figure 5AIt is started after the control 501 in the above is operated, or it can be started after the user performs the above operation. Figure 5B It is started after the control 505 in the program is executed.

[0140] As another embodiment, the terminal may also only display Figure 5A or Figure 5B For example, the terminal may display Figure 5A After the user operates control 501, the terminal can start the near field communication function, obtain the card information of the nearby card through near field communication, and display the card binding page containing the card information after obtaining the card information. For another example, the application homepage may not include a control for binding the card through near field communication. The user can enter the page for triggering the card binding according to the existing card binding operation process, for example Figure 5B The page for obtaining card information shown may also be called a card binding trigger page. After the user operates the control 505, the terminal may execute a process of obtaining card information through near field communication.

[0141] Step 404: Based on the card binding triggering operation, response information fed back by the target card based on the near field communication is obtained through the near field communication.

[0142] In the embodiment of this specification, the card binding control may be a control indicating card binding via NFC, and the card binding trigger operation may be a trigger operation for the control. Figure 3 The trigger operation of the NFC control in the first area 301 of the card binding trigger page, or the ... Figure 5B A triggering operation of a control 505 in another page of a target application.

[0143] In the embodiment of this specification, the target card may be a card that needs to be bound, and the response information may be the card information in the target card.

[0144] In actual applications, the mobile terminal acts as a card reader, emitting electromagnetic information around the mobile terminal to detect whether there is a card with near-field communication function near the mobile terminal. If the mobile terminal detects that there is a card with near-field communication function near the mobile terminal, the mobile terminal sends instruction information for obtaining card information to the card. The card responds to the instruction information sent by the mobile terminal and feeds back response information to the mobile terminal.

[0145] Step 406: parse the response information using the first communication protocol information stored in the mobile terminal to obtain the card information of the target card contained in the response information.

[0146] In the embodiments of this specification, after receiving a response message from a target card, the mobile terminal may parse the response message using a first communication protocol information selected from various communication protocol information stored in the mobile terminal to obtain card information of the target card. The card information may include at least one of the following: the card number of the target card, the expiration date of the target card, the bank where the target card is issued, and user information corresponding to the target card.

[0147] In the embodiments of this specification, the first communication protocol information and other communication protocol information stored in the mobile terminal are all communication protocol information obtained according to the above-mentioned method for obtaining communication protocol information. The card binding method based on near-field communication in this embodiment can be based on the communication protocol information obtained by the above-mentioned method for obtaining communication protocol information.

[0148] Step 408: Display the card information on the card binding page.

[0149] In the embodiment of the present specification, after the mobile terminal successfully parses the response information fed back by the target card, the parsed card information of the target card may be displayed to the user on the card binding page for the user to verify.

[0150] Figure 4 In the method, a mobile terminal can acquire the target card's card information through near-field communication by tapping or tapping the target card against it. The mobile terminal can also display the card information on a card binding page, eliminating the need for the user to manually enter the card information of the card to be bound, thereby simplifying the card binding process. The mobile terminal can utilize locally stored communication protocol information to parse the card information acquired through near-field communication. This eliminates the need for the mobile terminal to interact with the server each time a card binding transaction is processed during the communication phase between the mobile terminal and the card, thereby reducing the time consumption of the card binding operation and improving the user experience during the card binding process.

[0151] based on Figure 4 The present specification also provides some specific implementation methods of the method, which are described below.

[0152] During the card binding process, the mobile terminal may also display a reminder message guiding the user to select near-field communication for card binding, so that the user can correctly bind the card via near-field communication. Optionally, the method may further include: displaying a card binding prompt page based on the card binding trigger operation; including prompt information on the card binding prompt page for prompting the user to use near-field communication to bind the card; and obtaining a first confirmation operation performed by the user based on the card binding prompt page. Correspondingly, obtaining response information fed back by the target card via near-field communication based on the near-field communication method may specifically include: obtaining response information fed back by the target card via near-field communication based on the first confirmation operation.

[0153] In the embodiments of this specification, the prompting information for prompting the user to bind a card using near-field communication can be textual, such as "Press your phone to the card," "Binding the card using NFC," or "Adding card information via NFC." The prompting information can also be graphical, such as an image or animated graphic showing a mobile terminal and a card being placed close together.

[0154] In an embodiment of the present specification, the card binding prompt page may further include a preset control for reflecting the user's confirmation of card binding via near field communication, wherein the preset control may carry words such as "Start", "Confirm", "Submit", and "Try It". The first confirmation operation may be a confirmation operation performed by the user on the preset control, wherein the confirmation operation may be any one of a click operation, a slide operation, and a box selection operation. In actual applications, the mobile terminal generates instruction information for obtaining response information via near field communication in response to the user's first confirmation operation on the preset control in the card binding prompt page. The mobile terminal sends the instruction information to the target card via near field communication, and the target card responds to the instruction information and feeds back the response information to the mobile terminal via near field communication. During the process of the user binding the card based on the mobile terminal, a reminder message for binding the card via near field communication may be displayed to the user to prompt the user to select near field communication to bind the card, so that the user can correctly bind the card via near field communication.

[0155] For example, Figure 6 This is a schematic diagram of a card binding prompt page provided in an embodiment of this specification. Figure 6 As shown, the card binding prompt page may include prompt information 601 in the form of an image and prompt information 603 in the form of a text to prompt the user to bind the card via near-field communication. The card binding prompt page may also include a preset control 602, so that the user can trigger the preset control 602 to instruct the terminal to execute the card binding process via near-field communication.

[0156] It should be noted that the card binding prompt page may not have a preset control for triggering the first confirmation operation. The card binding prompt page may be a near-field communication response process page. The user does not need to perform the first confirmation operation on the card binding prompt page. After the card binding prompt page displays the prompt information to the user, the mobile terminal can obtain the response information fed back by the target card via near-field communication. After the mobile terminal obtains the card information fed back by the target card, the card binding prompt page may automatically close, and the mobile terminal can then display the card binding page.

[0157] To improve the success rate of card binding between the mobile terminal and the target card, during the card binding process, prompt information guiding the user in performing the card binding operation may also be displayed to the user. Optionally, after the mobile terminal obtains the card binding trigger operation performed by the user, the following may be included: while the mobile terminal obtains the response information fed back by the target card via near-field communication, the identification response page is displayed; the identification response page includes prompt information for prompting the user to perform the operation during the card binding process.

[0158] In the embodiments of this specification, the identification response page may be a page displayed by the mobile terminal to the user during the card binding process via near-field communication to guide the user in performing the card binding operation. The identification response page may include real-time information used to inform the user of the card binding operation. For example, the identification response page may display words such as "Ready to scan" to inform the user that a scanning operation will be performed. The identification response page may also include reminders of operational matters that the user needs to pay attention to during the card binding process. For example, the identification response page may display words such as "Keep the phone close to the card, do not move" to prompt the user to perform the correct card binding operation during the card binding process, thereby improving the success rate of card binding.

[0159] In actual applications, the identification response page can be displayed in the form of a pop-up window within the card binding prompt page. Of course, the identification response page can also be displayed independently of the card binding prompt page. Alternatively, the identification response page and the card binding prompt page can be the same page. This is not specifically limited here. In actual applications, after the mobile terminal obtains the card binding trigger operation performed by the user, it can display the card binding prompt page or one of the identification response pages; alternatively, after the mobile terminal obtains the card binding trigger operation performed by the user, it can first display the card binding prompt page and then display the identification response page. This is not limited.

[0160] To facilitate user operation, optionally, the identification response page includes a cancel control for canceling interaction through near field communication.

[0161] In the embodiment of this specification, a cancel control is set in the identification response page to facilitate the user to cancel the card binding operation through near field communication, thereby improving the user experience during the card binding process.

[0162] For example, Figure 7 This is a schematic diagram of an identification response page provided by an embodiment of this specification. Figure 7 As shown, the recognition response page may include real-time information 701 of the card binding operation and operational matters 702 that need to be noted during the card binding process to improve the user's card binding success rate. It may also include a cancel control 703 to facilitate the user to terminate the card binding operation.

[0163] Optionally, the method may further include: if a user operation on the cancel control is obtained, terminating the process of obtaining the card information through near field communication.

[0164] In the embodiments of this specification, the user's operation on the cancel control can be any one of a click operation, a sliding operation, and a box selection operation. After the user triggers the operation on the cancel control, the user can turn off the card binding operation between the mobile terminal and the target card through near-field communication, or can also turn off the card reader function of the mobile terminal. If the mobile terminal has received the response information fed back by the target card when the user triggers the operation on the cancel control, the parsing operation on the response information can be stopped. In actual applications, after the user triggers the operation on the cancel control in the identification response page, the display page in the mobile terminal can return to the previous page of the identification response page, such as the card binding prompt page. Alternatively, it can also return to other pages, such as the homepage of the target application used for card binding, etc., without limitation.

[0165] In the embodiment of this specification, the user can terminate the card binding operation between the mobile terminal and the target card at any time by operating the cancel control in the identification response page, so that when the user's willingness to bind the card changes, the loss can be stopped in time, thereby improving the user's user experience of card binding.

[0166] To avoid users having to wait for long periods of time, the user may be prompted to rescan if the scan time is too long or exceeds a preset time period. Optionally, after the mobile terminal obtains the card binding trigger operation performed by the user, the following may be included: if the mobile terminal does not detect a card with near-field communication functionality within a first preset time period, a first abort page is displayed; the first abort page includes a prompt indicating that the card information was not successfully obtained.

[0167] In the embodiments of this specification, the first preset duration may start at the time when the user triggers the card binding operation. If the mobile terminal does not detect a card with near-field communication functionality near the terminal within the first preset duration after the user triggers the card binding operation, the mobile terminal may display a first suspension page. The first preset duration may be appropriately set based on the actual scenario. For example, the first preset duration may be 10 seconds, 20 seconds, 30 seconds, or other durations, and is not limited thereto.

[0168] In the embodiment of this specification, the mobile terminal does not detect a card with a near-field communication function. It can be understood that if the decrease in the signal strength at the mobile terminal within the first preset time period is less than the preset threshold, it means that the mobile terminal does not detect a card with a near-field communication function.

[0169] In the embodiments of this specification, the first suspension page may represent a page for temporarily suspending card binding via near-field communication. The first suspension page may include a prompt message indicating that the card information was not successfully obtained, such as the words "Scan failed". Alternatively, the first suspension page may also include card binding operation information for guiding the user to bind the card, such as the words "Scan interrupted, please place the front of the card close to the chip area on the back of the phone". During the process of the mobile terminal scanning the target card, if the scanning time is too long, a suspension page for suspending the scan may be displayed to the user to prompt the user to correct the user operation, thereby improving the success rate of card binding.

[0170] Optionally, the first suspension page further includes a first control for re-executing the process of obtaining card information through near field communication.

[0171] In the embodiments of this specification, a first control for re-executing the process of acquiring card information via near-field communication is provided on the first abort page. This allows the user to immediately re-scan after notifying the user of a scan failure, thereby improving the timeliness of card binding. In actual applications, the first abort page may display a countdown control. After the countdown in the countdown control expires, the target card information may be automatically re-identified, or the card binding process may be automatically terminated. This is not limited to this.

[0172] For example, Figure 8 This is a schematic diagram of a first suspension page provided in an embodiment of this specification. Figure 8 As shown, the first abort page may include a prompt message 801 indicating that the card information was not successfully obtained, and card binding operation information 802 for guiding the user to bind the card. It may also include a first control 803 to facilitate the user to re-execute the card binding operation.

[0173] Optionally, the method may further include: if a user operation on the first control is obtained, restarting the process of obtaining card information through near field communication.

[0174] In the embodiments of this specification, the user's operation on the first control can be any one of a click operation, a slide operation, and a selection operation. After the user triggers the operation on the first control, the mobile terminal can resend the electromagnetic signal to detect whether a target card with near-field communication functionality is present near the mobile terminal. In actual applications, after the user triggers the operation on the first control on the first suspension page, the mobile terminal can redisplay any of the card binding prompt page and the identification response page, or can display the identification response page after displaying the card binding prompt page, without limitation.

[0175] In the embodiment of this specification, the user can restart the process of obtaining card information through near field communication by operating the first control in the first suspension page, so as to improve the convenience of the user restarting the card binding process.

[0176] To avoid lengthy user waiting times, if the scanning time is too long or exceeds a preset time duration, a prompt indicating that card information was not successfully acquired may be displayed on the identification response page. Optionally, the method may further include: if the mobile terminal does not detect a card with near-field communication functionality within a second preset time duration, displaying a prompt indicating that card information was not successfully acquired on the identification response page.

[0177] In the embodiments of this specification, the second preset duration may start at the moment the user triggers the card binding operation. The second preset duration may be the same as the first preset duration, for example, 10 seconds, 20 seconds, 30 seconds, 40 seconds, or other durations. The second preset duration may also be different from the first preset duration, and this is not limited to this. In actual applications, a prompt message may be displayed in the form of a pop-up window on the recognition response page. The prompt message may include a message indicating a failure to obtain card information, such as "Scan Failed." In actual applications, the prompt message displayed in the form of a pop-up window on the recognition response page indicating that the card information was not successfully obtained may be displayed after waiting for a preset duration, or after the user performs an operation on the recognition response page. The preset duration may be 3 seconds, 5 seconds, or other durations, and this is not limited to this. During the process of the mobile terminal scanning the target card, if the scanning time is too long, an recognition response page containing a prompt indicating that the card information was not successfully obtained may be displayed to the user, prompting the user to re-recognize, thereby improving the success rate of card binding.

[0178] For example, Figure 9This is another schematic diagram of identifying a response page provided by an embodiment of this specification. Figure 9 As shown, the identification response page may include prompt information 901 indicating that the card information was not successfully obtained, so as to prompt the user to perform identification again.

[0179] It should be noted that Figure 7 The recognition response page in Figure 9 The recognition response page in can be the same response page, or can be different response pages. In actual application, you can first display Figure 7 If the recognition fails, the recognition response page will be displayed. Figure 9 Alternatively, you can also not display the recognition response page. Figure 7 The recognition response page in triggers the recognition process. If the recognition fails, it will be displayed directly. Figure 9 The identification response page in is not limited to this.

[0180] In actual applications, after the identification process is triggered, only the first suspension page may be displayed without displaying the identification response page, or only the identification response page may be displayed without displaying the first suspension page, without limitation. In actual applications, the first suspension page and / or the identification response page may be automatically closed after being displayed for a preset period of time, allowing the mobile terminal to display other pages.

[0181] In actual applications, if the target card does not support card binding via near field communication or the mobile terminal cannot parse the card information, the mobile terminal may also display a prompt message indicating read failure to the user.

[0182] Optionally, the method may further include: if the mobile terminal fails to successfully parse the card information of the target card from the response information, displaying a second suspension page; the second suspension page includes prompt information indicating that the card cannot be recognized.

[0183] In an embodiment of the present specification, after the mobile terminal performs a read operation on the target card via near-field communication, if no response information is read from the target card, a second termination page may be displayed to the user. Alternatively, after the mobile terminal performs a read operation on the target card via near-field communication, the mobile terminal may read response information from the target card. After the mobile terminal parses the read response information, if the parsed information does not contain information in the card specification format, such as the card number, card institution information, card production date information, or cardholder information, the second termination page may be displayed to the user. The second termination page may include a prompt indicating that the target card cannot be identified via near-field communication, such as a message stating "This card does not support identification via near-field communication."

[0184] In an embodiment of the present specification, after the mobile terminal reads the target card through near-field communication, if the card information of the target card is not recognized from the target card, a prompt message indicating that the card cannot be recognized can be displayed to the user to remind the user that the target card cannot be bound through near-field communication, thereby prompting the user to adopt other methods to bind the card.

[0185] Optionally, the second suspension page also includes at least one of a second control for starting a non-near field communication method to obtain card information and a third control for re-executing the process of obtaining card information through near field communication.

[0186] Methods for obtaining card information other than NFC can include manual input or photographing. Re-executing the process for obtaining card information via NFC can be understood as re-executing the process for obtaining card information via NFC for the original card, or re-executing the process for obtaining card information via NFC for a different card. The second abort page includes a second control and / or a third control that facilitates the user's selection of other card binding methods, thereby increasing the diversity of card binding methods and improving the user experience.

[0187] For example, Figure 10 This is a schematic diagram of a second suspension page provided in an embodiment of this specification. Figure 10 As shown, the second suspension page may include prompt information 1001 indicating that the card cannot be recognized, a second control 1003, and a third control 1004. The second suspension page may also include prompt information 1002 for prompting the user to select other methods for card binding.

[0188] To improve the success rate of user card binding, if the card binding operation cannot be completed via near-field communication within a preset time period, a page for binding the target card via other methods may be displayed to the user. Optionally, the method may further include: if the mobile terminal fails to obtain card information via near-field communication within a third preset time period, displaying a card addition page indicating that card information should be provided using a method other than near-field communication.

[0189] In the embodiments of this specification, the starting time of the third preset duration can be the moment when the user triggers the card binding operation. The third preset duration can be greater than or equal to the first preset duration, or greater than or equal to the second preset duration, or greater than or equal to the first preset duration and greater than or equal to the second preset duration. For example, the third preset duration, the second preset duration, and the first preset duration can be the same, and all can be 10 seconds, 20 seconds, 30 seconds, 40 seconds, or other durations; or the preset durations can be different, without limitation. The mobile terminal's failure to obtain card information via near-field communication can indicate that the mobile terminal failed to identify the target card via near-field communication, or it can indicate that the mobile terminal failed to parse the target card's card information from the response information fed back by the target card via near-field communication. The add-card page can include prompts for obtaining card information via methods other than near-field communication to increase the diversity of card binding methods available to users, thereby improving the success rate of card binding.

[0190] For example, Figure 11 This is a schematic diagram of a card adding page provided in the embodiment of this specification. Figure 11 As shown, the add card page may include an area 1101 for providing card information using a non-near-field communication method. The user can enter the card information manually or by taking a photo in area 1101. The add card page may also include a submit control 1102. After the user enters the card information in area 1101 and triggers an action on submit control 1102, the subsequent card binding process can be executed.

[0191] In actual applications, if the mobile terminal fails to successfully parse the target card information from the response information, the mobile terminal may display either the second suspension page or the add card page. Alternatively, after displaying the second suspension page, if the mobile terminal does not receive a user trigger operation on the second suspension page within a preset time period, the mobile terminal may close the second suspension page and display the add card page. This is not limited to this.

[0192] After triggering the operation on the first control in the first suspension page, if the card information of the target card is still not recognized after rescanning the target card, the add card page can also be displayed to the user so that the user can choose other ways to bind the card.

[0193] Optionally, the method may further include: if the mobile terminal fails to obtain the card information through near field communication based on the user's operation of the first control, displaying a card adding page indicating that the card information is provided by a non-near field communication method.

[0194] In the embodiments of this specification, for explanations regarding failure to obtain card information via near-field communication and providing card information via non-near-field communication methods, please refer to the above explanations and will not be repeated here. In actual applications, during the process of a mobile terminal obtaining response information from a target card via near-field communication, if the mobile terminal fails to identify the target card, the first abort page may not be displayed, or the control for re-binding the card on the first abort page may not be triggered, and the add card page may be directly displayed. This is not a limitation.

[0195] Optionally, the non-near field communication method may include at least one of a manual input method and a photo taking method.

[0196] In the embodiments of this specification, the card binding prompt page, identification response page, first termination page, second termination page, add card page and other pages can be pages generated by the mobile terminal, or can also be pages generated by the server, without limitation.

[0197] In the embodiment of this specification, in order to allow the user to confirm the card information obtained by the mobile terminal through near-field communication, the card binding page may also include a control for confirming or submitting the card information. The mobile terminal can submit the obtained card information to the server for the card binding process based on the user's operation of the control.

[0198] Optionally, after displaying the card information on the card binding page, it may also include: obtaining the information submission operation performed by the user based on the card binding page; sending the card information to the server based on the information submission operation; the server can execute the card binding process based on the card information.

[0199] In an embodiment of this specification, the information submission operation can be a submission operation performed by the user on the submission control in the card binding page after the user verifies that the card information displayed in the card binding page is correct, wherein the submission operation can be any one of a click operation, a sliding operation, and a box selection operation.

[0200] For example, Figure 12This is a schematic diagram of a card binding page provided in an embodiment of this specification. Figure 12 As shown, the card binding page may include a submit control 1205 indicating confirmation of card binding. It may also include an area 1201 for displaying the card number information of the card to be bound, an area 1202 for displaying the card type information of the card to be bound, and an area 1203 for displaying the card date information of the card to be bound. In actual applications, the card information displayed in areas 1201, 1202, and 1203 may be obtained from the card to be bound by the mobile terminal via near-field communication, eliminating the need for manual user input. The card information displayed in areas 1201, 1202, and 1203 may all be editable. If the user discovers an error, they can manually modify it or retrieve it again via near-field communication. Of course, in actual applications, users may also manually enter the corresponding card information in areas 1201, 1202, and 1203. This is not specifically limited here.

[0201] In the embodiments of this specification, after receiving a user's submission operation, the mobile terminal may transmit the card information on the card binding page and identification information associated with the mobile terminal to a server. Upon receiving the card information and identification information sent by the mobile terminal, the server may associate the card information with the identification information to complete the card binding operation between the card information and the identification information. In actual applications, the server that performs the card binding process and the server that provides the communication protocol information may be the same server or different servers, without limitation.

[0202] In actual application, after the card information and the identification information associated with the mobile terminal are bound, the card corresponding to the card information can be displayed on the bound card page of the target application of the mobile terminal. The bound card page can be the aforementioned card binding trigger page.

[0203] For example, continue with Figure 3 For example, Figure 3 The card binding trigger page may also include a new card binding area 305 that displays the user's newly bound card.

[0204] In practical applications, the identification information related to the mobile terminal may be the device identification information of the mobile terminal, such as a unique device identification code, or the identification information of a target application installed on the mobile terminal, such as an application identifier of the target application.

[0205] In an embodiment of the present specification, before sending the card information in the card binding page and the identification information associated with the mobile terminal to the server, the mobile terminal may also encrypt and / or compress the card information to be sent and the identification information, and send the encrypted and / or compressed data to the server to improve the security of the data to be sent and / or reduce the transmission data volume of the data to be sent.

[0206] In order to improve the compliance of card binding, a card binding authorization page can also be displayed to the user before the card information is submitted to the server.

[0207] Optionally, after obtaining the user's information submission operation on the card binding page, the method may further include: displaying a card binding authorization page; the card binding authorization page including the card information. Correspondingly, sending the card information to the server may specifically include: obtaining the user's authorization confirmation operation on the card binding authorization page, and sending a card binding request including the card information to the server.

[0208] In embodiments of this specification, the card binding authorization page may be a page used by a user to authorize a server to bind a target card to a mobile terminal. After the user triggers a submit control on the card binding page, the mobile terminal may display the card binding authorization page to the user. This page may include card information, allowing the user to reconfirm whether the card information is correct, thereby improving the success rate of card binding. The card binding authorization page may also include an authorization confirmation control. Clicking on the confirmation control indicates that the user authorizes the server to bind the target card to the mobile terminal.

[0209] In actual applications, the card binding authorization page can be displayed first, and the user can confirm the authorization information on the card binding authorization page before the card binding page is displayed, and then the subsequent card binding process can be executed through the card binding page.

[0210] It is understandable that after the user triggers the operation on the submit control in the card binding page, the card binding authorization page may not be displayed. The user triggers the operation on the submit control in the card binding page, which means that the user authorizes the server to bind the target card to the mobile terminal. For example, the card binding page may include relevant information of the optional user authorization agreement. The user's submission operation can indicate that the user agrees to the authorization and agrees to execute the card binding process. The specific page display method and operation method are not limited here. In actual application, after the user triggers the operation on the submit control in the card binding page, the mobile terminal can send the card information to the server. After receiving the authorization instruction sent by the mobile terminal, the server will execute the card binding process for the mobile terminal and the card information.

[0211] In actual applications, the card binding authorization page and the card binding page can also be the same page, where the authorization and submission operations can be independent operations. For example, after the user checks the authorization information on the page, it indicates that the user agrees to the authorization. After clicking Submit, the mobile terminal can send the card information to the server. Alternatively, the authorization and submission operations can be the same operation, and when the user clicks Submit, it indicates that the user has performed the authorization and submission operations.

[0212] In the embodiments of this specification, the card binding authorization page, the card binding page and other pages may be pages generated by the mobile terminal, or may be pages generated by the server, and this is not limited.

[0213] To further improve the accuracy of binding the target card, the target card's security verification code can be verified before binding the target card. Optionally, the card binding page can include an area for entering the security verification code of the card corresponding to the card information. The method can also include obtaining the security verification code of the card provided by the user in the area. Correspondingly, sending the card information to the server can specifically include sending the card information and the security verification code to the server.

[0214] In the embodiments of this specification, the Card Verification Value (CVV) may be a card verification code set by the issuing institution of the target card. The CVV is used to verify whether the user initiating card binding is the legitimate holder of the target card. In actual applications, the card binding page may also include an area for entering the CVV, and the CVV is obtained based on the information entered by the user in this area.

[0215] In actual application, the card information, security verification code, and identification information related to the mobile terminal are sent to the server. After receiving the card information, security verification code, and identification information related to the mobile terminal, the server can first verify whether the security verification code is consistent with the verification code of the target card corresponding to the card information. If the security verification code and the verification code of the target card corresponding to the card information are consistent, the card binding operation is performed for the card information and the identification information related to the mobile terminal. If the security verification code and the verification code of the target card corresponding to the card information are inconsistent, the card binding operation is not performed for the card information and the identification information related to the mobile terminal. Furthermore, the server can also return the verification result to the mobile terminal, so that the mobile terminal can resubmit the security verification code.

[0216] In actual applications, before sending the card information, security verification code and identification information associated with the mobile terminal in the card binding page to the server, the mobile terminal can also encrypt and / or compress the card information, security verification code and identification information to be sent, and send the encrypted and / or compressed data to the server to improve the security of the data to be sent and / or reduce the transmission data volume of the data to be sent.

[0217] For example, continue with Figure 12 For example, the card binding page may also include an area 1204 for displaying the security verification code of the card to be bound. The security verification code displayed in area 1204 can be editable. If the user finds an error, they can manually modify it or retrieve it again via near-field communication. Of course, in actual applications, the user can also manually enter the security verification code in area 1204, and this is not specifically limited here.

[0218] In actual applications, the page for filling in the security verification code can also be a page other than the card binding page. After the mobile terminal obtains the card information through near-field communication, the card information can be displayed on the card binding page. After the user confirms the card information on the card binding page, the card binding page can be triggered to jump to the page for filling in the security verification code. Alternatively, the card binding page can automatically jump to the page for filling in the security verification code after a preset time. After the user fills in the security verification code on the page, he clicks the submit control on the page to execute the subsequent card binding process.

[0219] It can be understood that during the actual card binding operation, the above-mentioned pages can be displayed in various situations or not, as long as the display pages are logical, and the above-mentioned pages can be the same page or different pages, as long as the corresponding page information can be displayed to enable the user to perform the card binding operation, there is no limitation here.

[0220] In the embodiments of this specification, a specific embodiment is also proposed for the method of obtaining the response information fed back by the target card.

[0221] Optionally, based on the card binding trigger operation, obtaining response information fed back by the target card based on the near field communication method through near field communication, may specifically include: based on the card binding trigger operation, sending instruction information through the near field communication method; obtaining response information fed back by the target card in response to the instruction information.

[0222] In the embodiments of this specification, the instruction information may be an instruction requesting the target card to return card information to the mobile terminal, and the response information may be the card information of the target card. After the card binding trigger operation is triggered, the mobile terminal generates instruction information for obtaining the card information of the target card in response to the card binding trigger operation and sends the instruction information to the target card via near-field communication. In actual applications, the mobile terminal may generate the instruction information based on one of the locally stored communication protocol information for card binding.

[0223] In the embodiment of this specification, the target card may be a card located near the mobile terminal, and may also be referred to as a card to be bound. After the target card obtains the instruction information sent by the mobile terminal, it may respond to the instruction information and feed back corresponding response information to the mobile terminal.

[0224] To avoid the mobile terminal interacting with the server each time it processes a card binding service, the communication protocol information used to parse the response information can be pre-saved in the mobile terminal. Optionally, before parsing the response information using the first communication protocol information saved in the mobile terminal, the method may further include: obtaining the communication protocol information sent by the server; and saving the communication protocol information.

[0225] In the embodiments of this specification, the communication protocol information sent by the server may be the communication protocol information stored on the server for binding a card. To reduce the amount of information transmitted between the server and the mobile terminal, the communication protocol information sent by the server to the mobile terminal may include communication protocol information that was not stored on the mobile terminal before the server sent the communication protocol information. This allows the mobile terminal to obtain communication protocol information that is not stored on the mobile terminal. In actual applications, if the server does not store the communication protocol information that is not stored locally on the mobile terminal, the server may not send the communication protocol information to the mobile terminal.

[0226] In the embodiment of this specification, the mobile terminal may store the communication protocol information sent by the server in a local storage unit, so as to perform card binding based on the locally stored communication protocol information.

[0227] Optionally, before obtaining the communication protocol information sent by the server, the method may further include: obtaining status information of the mobile terminal; and sending a protocol acquisition request to the server based on the status information.

[0228] Among them, the explanation of the status information can refer to the above explanation of the status information. In this embodiment, the mobile terminal can obtain the communication protocol information provided by the server in the manner described in the above embodiment of obtaining the communication protocol information, which will not be repeated here. In actual applications, the status information of the mobile terminal can be obtained by the mobile terminal. After the mobile terminal obtains the status information of the mobile terminal, the mobile terminal can judge whether the status of the mobile terminal meets the preset status based on the obtained status information. If the mobile terminal judges that the status of the mobile terminal meets the preset status, the mobile terminal can send a protocol acquisition request to the server. If the mobile terminal judges that the status of the mobile terminal does not meet the preset status, it may not send a protocol acquisition request to the server. It is also possible to continue to obtain subsequent status information of the mobile terminal, and after the status of the mobile terminal meets the preset status, send a protocol acquisition request to the server.

[0229] In the embodiments of this specification, the mobile terminal obtains the status information of the mobile terminal and determines the status information of the mobile terminal, without the server obtaining and determining the status information of the mobile terminal, thereby reducing the workload of the server and saving server resources.

[0230] It should be noted that Figure 3 、 Figure 5A 、 Figure 5B 、 Figures 6 to 12 The information shown in the figure is only an example. In actual applications, different information may be displayed. Specifically, other text, pictures, animations, controls, etc. may be displayed. Figure 3 、 Figure 5A 、 Figure 5B 、 Figures 6 to 12 The information shown is not limited.

[0231] In order to more clearly illustrate the method provided in the embodiments of this specification, Figure 13 This is a swim lane flow diagram of a method for obtaining communication protocol information and binding a card provided in an embodiment of this specification. The service execution process of this method may involve execution entities such as a target card, a mobile terminal, and a server.

[0232] like Figure 13 As shown, the process may include the following steps.

[0233] In an embodiment of the present specification, the process may include a communication protocol information saving stage and a card binding stage for the target card based on the saved communication protocol information, wherein the communication protocol information saving stage may include steps 1302 to 1306, and the card binding stage for the target card based on the saved communication protocol information may include steps 1308 to 1322.

[0234] Step 1302: The mobile terminal sends a protocol acquisition request to the server.

[0235] Step 1304: The server provides communication protocol information to the mobile terminal in response to the protocol acquisition request sent by the mobile terminal.

[0236] Step 1306: The mobile terminal obtains and saves the communication protocol information fed back by the server.

[0237] It is understandable that the description here is merely based on the example of starting a terminal application to obtain communication protocol information from a server. In actual applications, one or more of the various triggering conditions described above may also be used, which is not limited here.

[0238] Step 1308: The mobile terminal obtains the card binding triggering operation performed by the user.

[0239] The card binding triggering operation may be a first operation performed by the user to obtain card information through near field communication.

[0240] Step 1310: Based on the card binding triggering operation, the mobile terminal sends instruction information to the target card with the near field communication function through the near field communication method.

[0241] Step 1312: The target card feeds back response information to the mobile terminal in response to the received instruction information.

[0242] Step 1314: The mobile terminal obtains response information fed back by the target card in response to the instruction information.

[0243] Step 1316: The mobile terminal parses the response information using the first communication protocol information selected from various communication protocol information stored in the mobile terminal to obtain the card information of the target card.

[0244] Step 1318: Display the card information on the card binding page.

[0245] Step 1320: The mobile terminal sends the card information to the server according to the information submission operation performed by the user based on the card binding page.

[0246] Step 1322: The server executes the card binding process based on the card information.

[0247] For example, the server can establish a corresponding relationship between the card information and the mobile terminal or the terminal application of the card, so that the user can use the card to handle business through the mobile terminal or the terminal application of the card. The specific card binding process can be found in the relevant technical information and will not be repeated here.

[0248] In practical applications, the steps involved in the communication protocol information storage phase do not need to be performed before each card binding phase. That is, the steps involved in the communication protocol information storage phase and the steps involved in the card binding phase can be performed independently. Alternatively, the execution time interval between the steps involved in the communication protocol information storage phase and the steps involved in the card binding phase can be longer, as long as the mobile terminal can obtain card information based on the locally stored communication protocol information. There is no specific limitation on the execution order and timing of the steps.

[0249] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0250] Figure 14 This is a structural diagram of a device for obtaining communication protocol information provided by an embodiment of this specification.

[0251] like Figure 14 As shown, the device may include: The status acquisition module 1402 is used to obtain the status information of the mobile terminal; the determination module 1404 is used to trigger the process of the server providing communication protocol information based on the status information; the communication protocol information is the communication protocol information used in the process of the mobile terminal obtaining the card information for binding the card from the target type of card supporting the near field communication function through near field communication; the protocol acquisition module 1406 is used for the mobile terminal to obtain the communication protocol information fed back by the server according to the process; the communication protocol information includes communication protocol information that does not exist in the mobile terminal before the process is triggered; the protocol storage module 1408 is used for the mobile terminal to save the communication protocol information fed back by the server.

[0252] Figure 15 This is a structural diagram of a card binding device based on near field communication provided in an embodiment of this specification.

[0253] like Figure 15 As shown, the device may include: The trigger operation acquisition module 1502 is used by the mobile terminal to acquire a card binding trigger operation performed by a user. The response information acquisition module 1504 is used to obtain response information fed back by the target card via near-field communication based on the card binding trigger operation. The parsing module 1506 is used to parse the response information using the first communication protocol information stored in the mobile terminal to obtain the card information of the target card contained in the response information. The display module 1508 is used to display the card information on the card binding page.

[0254] Based on the same idea, the embodiments of this specification also provide devices corresponding to the above methods.

[0255] Figure 16 This is a block diagram of a computer device provided in the embodiment of this specification. Figure 16 As shown, the device 1600 may include: at least one processor 1610; and a memory 1630 communicatively connected to the at least one processor; wherein, The memory 1630 stores instructions 1620 that can be executed by the at least one processor 1610. The instructions are executed by the at least one processor 1610 so that the at least one processor 1610 can execute to implement the above-mentioned method of obtaining communication protocol information or the above-mentioned card binding method based on near-field communication.

[0256] The above is a schematic diagram of a device for obtaining communication protocol information according to this embodiment. It should be noted that the technical solution of this device is based on the same concept as the technical solution of the method for obtaining communication protocol information or the technical solution of the card binding method based on near-field communication described above. For details not described in detail in the technical solution of the device, please refer to the description of the technical solution of the method for obtaining communication protocol information or the technical solution of the card binding method based on near-field communication described above.

[0257] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device and equipment embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The devices, equipment and methods provided in the embodiments of this specification correspond to each other, so the devices and equipment also have beneficial technical effects similar to the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the corresponding devices and equipment will not be repeated here.

[0258] An embodiment of this specification also provides a computer-readable storage medium storing a computer program or instruction. When the computer program or instruction is executed by a processor, the steps of the above-mentioned method for obtaining communication protocol information or the steps of the above-mentioned card binding method based on near-field communication are implemented.

[0259] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the computer-readable storage medium embodiment is generally similar to the method embodiment described above, so its description is relatively simple. For relevant portions, refer to the partial description of the method embodiment described above.

[0260] The foregoing description describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. Multitasking and parallel processing are also possible or may be advantageous in certain embodiments.

[0261] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using physical hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system onto a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly performed using software called a "logic compiler." This is similar to the software compilers used during program development. Before compilation, the original code must be written in a specific programming language, called a Hardware Description Language (HDL). There are many types of HDL, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that simply by programming a method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0262] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the memory control logic. Those skilled in the art will also appreciate that, in addition to implementing the controller purely in computer-readable program code, the controller can also be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, an embedded microcontroller, etc. by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing the various functions included therein can also be considered as structures within the hardware component. Alternatively, the means for implementing the various functions can be considered both a software module implementing the method and a structure within the hardware component.

[0263] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0264] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0265] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0266] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0267] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0268] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0269] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-permanent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0270] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology for information storage. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0271] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0272] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0273] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A method for obtaining communication protocol information, comprising: Obtaining status information of the mobile terminal; Based on the status information, trigger the server to provide a process of communication protocol information; The communication protocol information is the communication protocol information used by the mobile terminal in the process of acquiring the card information used for binding the card from the target type of card supporting the near field communication function through the near field communication method; According to the process, the mobile terminal obtains the communication protocol information fed back by the server; the communication protocol information includes the communication protocol information that does not exist in the mobile terminal before triggering the process; The mobile terminal stores the communication protocol information fed back by the server.

2. The method according to claim 1, wherein obtaining the status information of the mobile terminal comprises: The mobile terminal obtains status information of the mobile terminal; The process of triggering the server to provide communication protocol information based on the status information specifically includes: The mobile terminal sends a protocol acquisition request to a server based on the status information.

3. The method according to claim 1, wherein obtaining the status information of the mobile terminal comprises: The server obtains the status information of the mobile terminal; The process of triggering the server to provide communication protocol information based on the status information specifically includes: The server sends the communication protocol information to the mobile terminal according to the status information.

4. The method according to claim 2, wherein the mobile terminal sends a protocol acquisition request to the server based on the status information, specifically comprising: The mobile terminal determines, based on the status information, whether the status of the mobile terminal satisfies a preset status; If the state of the mobile terminal meets the preset state, a protocol acquisition request is sent to the server.

5. The method according to claim 2, wherein the mobile terminal sends a protocol acquisition request to the server based on the status information, specifically comprising: The mobile terminal sends a protocol acquisition request containing the status information to a server based on the status information; The server determines whether the state of the mobile terminal meets a preset state according to the state information.

6. The method according to claim 3, wherein the server sends the communication protocol information to the mobile terminal according to the status information, specifically comprising: The server determines, according to the status information, whether the status of the mobile terminal satisfies a preset status; If the state of the mobile terminal meets the preset state, the communication protocol information is sent to the mobile terminal.

7. The method according to any one of claims 4 to 6, wherein the preset state is a state in which the server provides the communication protocol information; The determining whether the state of the mobile terminal satisfies a preset state includes at least one of the following: Determining whether the current time of the mobile terminal reaches the cycle time for acquiring communication protocol information; Determining whether there is communication protocol information in the server that does not exist in the mobile terminal; Determine whether the mobile terminal displays a card binding page; Determining whether the mobile terminal starts a target application; The target application is an application that provides card binding services; Determining whether the mobile terminal successfully parses the near field communication response information provided by the card to be bound using the existing communication protocol information; Determine whether the mobile terminal is connected from the first network to the second network; the network parameters of the second network are better than the network parameters of the first network; the network parameters include at least one of signal strength, data transmission speed, and delay time; Determining whether existing communication protocol information in the mobile terminal has expired; Determine whether the device attribute of the mobile terminal is a preset attribute; the device attribute includes at least one of a device system type, a device system version, a device model, and a device brand.

8. The method according to claim 1, after saving the communication protocol information, further comprising: The mobile terminal obtains a first operation performed by a user to obtain card information by means of near field communication; Based on the first operation, sending instruction information through the near field communication method; Acquire response information fed back by the target card in response to the instruction information; parse the response information by selecting first communication protocol information from various communication protocol information stored in the mobile terminal to obtain card information of the target card; The card information is displayed on the card binding page.

9. The method of claim 8, further comprising: The mobile terminal sends an electromagnetic signal for triggering near field communication; Based on the electromagnetic signal, determining whether there is a card with a near field communication function near the mobile terminal; The sending of the instruction information by means of the near field communication specifically includes: If there is a card with a near field communication function near the mobile terminal, the instruction information is sent via the near field communication.

10. The method according to claim 8, wherein the step of parsing the response information by selecting the first communication protocol information from the communication protocol information stored in the mobile terminal to obtain the card information of the target card comprises: parsing the response information using the first communication protocol information, If the response information can be parsed successfully, the card information of the target card is obtained; If the response information cannot be parsed successfully, selecting second communication protocol information from the various communication protocol information; The response information is parsed using the second communication protocol information to obtain the card information of the target card.

11. The method according to claim 8, wherein the selecting the first communication protocol information from each communication protocol information stored in the mobile terminal specifically comprises at least one of the following methods: Randomly selecting first communication protocol information from the various communication protocol information; Selecting first communication protocol information commonly used by the mobile terminal from the various communication protocol information; Selecting, from the various communication protocol information, first communication protocol information most recently used by the mobile terminal in the card binding service; Selecting first communication protocol information corresponding to the nationality or location of the terminal user of the mobile terminal from the various communication protocol information; The first communication protocol information that is most recently saved in the mobile terminal is selected from the various communication protocol information.

12. The method according to claim 1, before acquiring the status information of the mobile terminal, further comprising: The mobile terminal obtains, by means of near field communication, response information provided by a card with a near field communication function in response to the mobile terminal; Parsing the response information using at least one existing communication protocol information already in the mobile terminal; The obtaining of the status information of the mobile terminal specifically includes: Result information indicating that the mobile terminal fails to successfully parse the response information using the at least one existing communication protocol information is obtained.

13. According to the method as claimed in claim 1, the communication protocol information fed back by the server is the communication protocol information that does not exist in the mobile terminal before the process is triggered; or, the communication protocol information fed back by the server is the full communication protocol information in the server.

14. A card binding method based on near field communication, comprising: The mobile terminal obtains the card binding triggering operation performed by the user; Based on the card binding trigger operation, obtaining, through near field communication, response information fed back by the target card based on the near field communication; Parsing the response information using the first communication protocol information saved in the mobile terminal to obtain the card information of the target card contained in the response information; The card information is displayed on the card binding page.

15. The method of claim 14, further comprising: Based on the card binding trigger operation, display a card binding prompt page; The card binding prompt page includes prompt information for prompting the user to bind the card using near field communication; Acquire a first confirmation operation performed by the user based on the card binding prompt page; The step of obtaining the response information fed back by the target card based on the near field communication method specifically includes: Based on the first confirmation operation, response information fed back by the target card based on the near field communication is obtained through the near field communication.

16. The method according to claim 14, after the mobile terminal obtains the card binding triggering operation performed by the user, further comprising: In the process of the mobile terminal obtaining the response information fed back by the target card based on the near field communication method through the near field communication method, an identification response page is displayed; the identification response page includes prompt information for prompting the user of the operations to be performed by the user during the card binding process.

17. The method of claim 16, wherein the identification response page comprises a cancel control for canceling the interaction by means of near field communication.

18. The method of claim 17, further comprising: If the user's operation on the cancel control is obtained, the process of obtaining the card information by means of near field communication is terminated.

19. The method according to claim 14, after the mobile terminal obtains the card binding triggering operation performed by the user, further comprising: If the mobile terminal does not detect a card with a near field communication function within a first preset time period, displaying a first suspension page; The first suspension page includes prompt information indicating that the card information was not successfully obtained.

20. The method of claim 19, wherein the first suspension page further comprises a first control indicating a process for re-executing a process of obtaining card information by means of near field communication.

21. The method of claim 20, further comprising: If the user's operation on the first control is obtained, the process of obtaining the card information by means of near field communication is restarted.

22. The method of claim 16, further comprising: If the mobile terminal fails to detect the card with the near field communication function within the second preset time period, a prompt message indicating that the card information has not been successfully obtained is displayed in the identification response page.

23. The method of claim 14, further comprising: If the mobile terminal fails to successfully parse the card information of the target card from the response information, displaying a second suspension page; The second suspension page includes prompt information indicating that the card cannot be recognized.

24. The method as claimed in claim 23, wherein the second abort page further includes at least one of a second control for initiating a non-near field communication method to obtain card information and a third control for re-executing the process of obtaining card information through near field communication.

25. The method of claim 14, further comprising: If the mobile terminal fails to obtain the card information through the near field communication method within the third preset time period, a card adding page indicating that the card information is provided by a non-near field communication method is displayed.

26. The method of claim 21, further comprising: If the mobile terminal fails to obtain the card information through the near field communication method based on the user's operation on the first control, a card adding page indicating that the card information is provided by a non-near field communication method is displayed.

27. The method according to any one of claims 25 or 26, wherein the non-near field communication method comprises at least one of a manual input method and a photographing method.

28. The method according to claim 14, after displaying the card information on the card binding page, further comprising: Obtaining the information submission operation performed by the user based on the card binding page; Based on the information submission operation, sending the card information to a server; The server can execute the card binding process based on the card information.

29. The method according to claim 28, after obtaining the information submission operation performed by the user based on the card binding page, further comprising: Display the card binding authorization page; The card binding authorization page includes the card information; The sending of the card information to the server specifically includes: Obtain the authorization confirmation operation performed by the user based on the card binding authorization page, and send a card binding request containing the card information to the server.

30. The method of claim 28, wherein the card binding page further includes an area for filling in a security verification code of the card corresponding to the card information; the method further includes: Obtain information of a security verification code of the card provided by the user in the area; The sending of the card information to the server specifically includes: Send the card information and the security verification code information to the server.

31. The method according to claim 14, wherein based on the card binding trigger operation, obtaining the response information fed back by the target card based on the near field communication through the near field communication method specifically comprises: Based on the card binding trigger operation, sending instruction information through the near field communication method; Acquire response information fed back by the target card in response to the instruction information.

32. The method according to claim 14, before parsing the response information using the first communication protocol information stored in the mobile terminal, further comprising: Get the communication protocol information sent by the server; The communication protocol information is saved.

33. The method according to claim 32, before acquiring the communication protocol information sent by the server, further comprising: Obtaining status information of the mobile terminal; Based on the status information, a protocol acquisition request is sent to the server.

34. A device for obtaining communication protocol information, comprising: A status acquisition module, used to acquire status information of the mobile terminal; A determination module, configured to trigger a process of the server providing communication protocol information based on the status information; The communication protocol information is the communication protocol information used by the mobile terminal in the process of acquiring the card information used for binding the card from the target type of card supporting the near field communication function through the near field communication method; A protocol acquisition module, configured to enable the mobile terminal to acquire the communication protocol information fed back by the server according to the process; the communication protocol information includes the communication protocol information that does not exist in the mobile terminal before the process is triggered; The protocol storage module is used for the mobile terminal to store the communication protocol information fed back by the server.

35. A card binding device based on near field communication, comprising: A trigger operation acquisition module is used for the mobile terminal to acquire the card binding trigger operation performed by the user; A response information acquisition module, used to acquire, based on the card binding trigger operation, the response information fed back by the target card based on the near field communication method through the near field communication method; A parsing module, used to parse the response information by using the first communication protocol information saved in the mobile terminal to obtain the card information of the target card contained in the response information; The display module is used to display the card information on the card binding page.

36. A computer device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute to implement the method for obtaining communication protocol information described in any one of claims 1 to 13 or the card binding method based on near field communication described in any one of claims 14 to 33.

37. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the method for obtaining communication protocol information described in any one of claims 1 to 13 or the card binding method based on near field communication described in any one of claims 14 to 33.

Images