A method, apparatus, device, and medium for obtaining communication protocol information

Abstract

Embodiments of the present specification provide a method, device, equipment and medium for obtaining communication protocol information. The method comprises: obtaining state information of a mobile terminal; triggering a server to provide a flow of communication protocol information based on the state information; wherein the communication protocol information is the communication protocol information used in a process in which the mobile terminal obtains card information from a card for binding the card. According to the flow, the mobile terminal obtains the communication protocol information fed back by the server; and the mobile terminal saves the communication protocol information fed back by the server.

Description

[0001] This application is a divisional application of a Chinese patent application. The original application was filed on March 4, 2025, with application number 202510245245.9 and the invention title being: "A method, apparatus, device, and medium for acquiring communication protocol information." Technical Field

[0002] This application relates to the field of computer technology, and in particular to a method for acquiring communication protocol information. This application also relates to apparatus, devices, and media for acquiring communication protocol information. Background Technology

[0003] As mobile terminal functions become more sophisticated, more and more transactions can be handled using mobile terminals. For example, mobile terminals can be used as virtual cards to replace physical cards for payments, access control, and identity verification. However, in order to use mobile terminals to handle these transactions, the mobile terminals must be bound to the corresponding cards beforehand.

[0004] Therefore, there is a need for a method that makes it easier for users to bind their mobile devices to their cards, in order to improve the user experience during the card binding process. Summary of the Invention

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

[0006] According to a first aspect of the present application, a method for obtaining communication protocol information is provided, comprising: obtaining state information of a mobile terminal; triggering a process of a server providing communication protocol information based on the state information; wherein the communication protocol information is communication protocol information used by the mobile terminal in the process of obtaining card information for binding the card from a target type card that supports near-field communication via near-field communication; wherein, according to the process, the mobile terminal obtains communication protocol information fed back by the server; wherein the communication protocol information includes communication protocol information that did not exist in the mobile terminal before the process was triggered; and wherein the mobile terminal saves the communication protocol information fed back by the server.

[0007] According to a second aspect of the embodiments of this application, a card binding method based on near-field communication is provided, comprising: a mobile terminal acquiring a card binding trigger operation performed by a user; based on the card binding trigger operation, acquiring response information fed back by a target card via near-field communication; parsing the response information using first communication protocol information already stored in the mobile terminal to obtain card information of the target card contained in the response information; and displaying the card information on a card binding page.

[0008] According to a third aspect of the embodiments of this application, an apparatus for obtaining communication protocol information is provided, comprising: a status acquisition module for acquiring 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; wherein the communication protocol information is communication protocol information used by the mobile terminal in the process of obtaining card information for binding the card from a target type card supporting near-field communication via near-field communication; a protocol acquisition module for the mobile terminal to acquire communication protocol information fed back by the server according to the process; wherein the communication protocol information includes communication protocol information that did not exist in the mobile terminal before the process was triggered; and a protocol storage module for the mobile terminal to store the communication protocol information fed back by the server.

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

[0010] According to a fifth aspect 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, the instructions being executed by the at least one processor to enable the at least one processor to perform the above-described method for obtaining communication protocol information or the above-described card-binding method based on near-field communication.

[0011] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores a computer program or instructions, which, when executed by a processor, implement the steps of the method for obtaining communication protocol information described above or the steps of the card-binding method based on near-field communication described above.

[0012] At least one embodiment in 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 saves the acquired communication protocol information locally, and then the mobile terminal can process the card binding service based on the locally stored communication protocol information. During the communication phase between the mobile terminal and the card in the card binding process, the mobile terminal can obtain the card information based on the already acquired communication protocol information used to identify the card, eliminating the need for the mobile terminal to interact with the server every time it processes the card binding service. This reduces the time spent on the card binding operation and improves the user experience during the card binding process. Furthermore, the server can provide the communication protocol information to the mobile terminal, eliminating the need for the mobile terminal to update its application version, thereby further improving the user experience and reducing business costs.

[0013] In at least one embodiment, the mobile terminal and the target card communicate by tapping or sticking together. The mobile terminal can obtain the card information of the target card via near-field communication (NFC) and display the card information on the card binding page, thus eliminating the need for the user to manually input the card information to be bound, simplifying the user operation. Furthermore, the mobile terminal can utilize locally stored communication protocol information to parse the card information obtained via NFC. This eliminates the need for the mobile terminal to interact with the server every time a card binding transaction is processed during the communication phase between the mobile terminal and the card, thereby reducing the time required for the card binding operation and improving the user experience. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 This is a schematic diagram illustrating an application scenario of a method for obtaining communication protocol information provided in the embodiments of this specification;

[0016] Figure 2 This is a flowchart illustrating a method for obtaining communication protocol information provided in an embodiment of this specification;

[0017] Figure 3 This is a schematic diagram of a card binding trigger page provided in an embodiment of this specification;

[0018] Figure 4This is a flowchart illustrating a card-binding method based on near-field communication provided in the embodiments of this specification;

[0019] Figure 5A This is a schematic diagram of a target application page provided in an embodiment of this specification;

[0020] Figure 5B This is another page illustration of a target application provided in the embodiments of this specification;

[0021] Figure 6 This is a schematic diagram of a card binding prompt page provided in an embodiment of this specification;

[0022] Figure 7 This is a schematic diagram illustrating an example of identifying a response page provided in this specification.

[0023] Figure 8 This is a schematic diagram of a first termination page provided in an embodiment of this specification;

[0024] Figure 9 This is a schematic diagram of another identification response page provided in the embodiments of this specification;

[0025] Figure 10 This is a schematic diagram of a second termination page provided in the embodiments of this specification;

[0026] Figure 11 This is a schematic diagram of a card-adding page provided in an embodiment of this specification;

[0027] Figure 12 This is a schematic diagram of a card binding page provided in an embodiment of this specification;

[0028] Figure 13 This is a schematic diagram of the swimlane flow of a method for obtaining communication protocol information and binding a card, provided in the embodiments of this specification.

[0029] Figure 14 This is a schematic diagram of the structure of a device for obtaining communication protocol information provided in the embodiments of this specification;

[0030] Figure 15 This is a schematic diagram of a card-binding device based on near-field communication provided in the embodiments of this specification;

[0031] Figure 16 This is a structural block diagram of a computer device provided in the embodiments of this specification. Detailed Implementation

[0032] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0033] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and the appended claims are also intended to include the 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 this 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 this application, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word “if” as used herein can be interpreted as “when,” “in response to a determination,” or “when…”.

[0034] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0035] First, the terms and concepts used in one or more embodiments of this specification will be explained.

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

[0037] The internationally recognized 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.

[0038] If the communication protocol used by the mobile terminal for binding the card is inconsistent with the communication protocol used by the card, or if the mobile terminal does not have the communication protocol information to parse the card information, the mobile terminal will be unable to bind the card through short-range communication.

[0039] In one related technology, the mobile terminal needs to interact with the server each time it processes a card binding service, using 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 will be too long, resulting in a relatively long card binding process for the user and a poor user experience. Another related technology requires a client with card binding functionality specific to the target card to bind it. Therefore, to achieve card binding, the mobile terminal needs to download and update the corresponding client version. However, this method consumes a significant amount of user network resources, and users can only successfully bind their cards after downloading the corresponding client version, which can easily lead to a low conversion rate and a relatively small number of users binding cards.

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

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

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

[0043] In the embodiments of this specification, mobile terminal 101 may include, but is not limited to, at least one of the following terminals: smartphone, tablet computer, laptop computer, smart interactive device, wearable device, in-vehicle smart terminal, etc. Wearable device may include, but is not limited to, at least one of the following terminals: smart bracelet, smartwatch, smart glasses, etc. Server 102 may include, but is not limited to, at least one of the following servers: any device, equipment, platform, device cluster, or cloud computing service center with computing and processing capabilities. Card 103 may include, but is not limited to, bank cards, public transport cards, access cards, shopping cards, discount cards, membership cards, tag cards, smart cards, etc., cards with NFC function, or cards may include any form of card such as a virtual card that carries the card information on a smart device with NFC function.

[0044] A communication connection is established between mobile terminal 101 and server 102. This communication connection can be, but is not limited to, a local area network (LAN) connection, a wide area network (WAN) connection, an internet connection, a short-range communication (SMR) connection, or other types of data network connections. SMR connections include, but are not limited to, Near Field Communication (NFC), LAN, Bluetooth, and infrared connections. Mobile terminal 101 can send a data acquisition request to server 102, and server 102 responds by returning response data to mobile terminal 101. Alternatively, server 102 can actively send data to mobile terminal 101. Mobile terminal 101 can be an initiating device, which actively triggers NFC communication and is responsible for generating a radio frequency field and initiating the NFC communication process. Card 103 can be a passively responding device, relying on the radio frequency field generated by mobile terminal 101 for power supply, or card 103 can be an active card, communicating with the mobile terminal based on its own energy. Card 103 can send data to mobile terminal 101 in response to a trigger signal from mobile terminal 101.

[0045] This application provides a method for obtaining communication protocol information, which will be described in detail in the following embodiments. Figure 2 This is a flowchart illustrating a method for obtaining communication protocol information provided in an embodiment of this specification.

[0046] From a programming perspective, the entity executing the process can be a program mounted on a device used to process communication protocol information. It can be understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities; for example, it can be a mobile terminal, a server, or both.

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

[0048] Step 202: Obtain the status information of the mobile terminal.

[0049] In the embodiments of this specification, the status information may include at least one of various types of information, such as status information indicating the status of a terminal application started or installed in the mobile terminal, status information indicating the time or space in which the mobile terminal is located, status information indicating the device attributes or functional status of the mobile terminal, and status information indicating the communication protocol information in the mobile terminal.

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

[0051] In practical applications, the preset time period can be one day, or other time periods. The preset application can be a terminal application capable of interacting with the server. The preset page can be a card binding page, or other pages within the preset application, such as the application homepage; there are no restrictions on this.

[0052] Step 204: Based on the status information, trigger the process of the server providing communication protocol information; the communication protocol information is the communication protocol information used by the mobile terminal to obtain card information for binding the card from a target type card that supports near-field communication via near-field communication.

[0053] In the embodiments of this specification, if the status information of the mobile terminal meets the requirements for triggering the server to provide communication protocol information, then the process of the server providing communication protocol information to the mobile terminal can be triggered. The communication protocol information can be the communication protocol information used in the process of obtaining card information from the card. The card information can be information used when binding the card to the mobile terminal, such as: bank information, card number information, card user information, etc.

[0054] In the embodiments described in this specification, the card can be a card that supports near-field communication (NFC) functionality, and the communication method between the mobile terminal and the card can be a communication method established based on NFC. In practical applications, the card can also be a card that supports other communication functions, such as a card that supports Bluetooth communication functionality. The communication method between the mobile terminal and the card can be Bluetooth communication. The specific communication method is not limited here, as long as it enables the mobile terminal to obtain the card information used for binding the card.

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

[0056] 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 did not exist in the mobile terminal before the process was triggered.

[0057] In this embodiment, the communication protocol information provided by the server can be the communication protocol information for binding the card that is already present on the server. Once the process of the server providing communication protocol information is triggered, the server can send the communication protocol information from 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 did not exist 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.

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

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

[0060] In the embodiments described in this specification, the mobile terminal can save the communication protocol information sent by the server in its local storage unit so as to bind the card based on the locally stored communication protocol information.

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

[0062] Figure 2The proposed method, based on mobile transition status information, allows the server to send the communication protocol information required for card binding to the mobile terminal. The mobile terminal saves this information locally and can then process the card binding process based on this stored information. During the card binding process, the mobile terminal can retrieve the card information from the communication protocol information already acquired for card identification, eliminating the need for the mobile terminal to interact with the server every time it processes a card binding transaction. This reduces the time required for card binding and improves the user experience. Furthermore, the server can maintain the communication protocol information, adding or expanding it to include protocols not previously present. The server can then provide this new information to the mobile terminal, eliminating the need for the mobile terminal to update its application, further enhancing the user experience and reducing operational costs.

[0063] based on Figure 2 In addition to the method described herein, this specification also provides some specific implementation methods of the method, which will be described below.

[0064] In the embodiments described in this specification, the mobile terminal may be the initiator of obtaining communication protocol information, and the server may respond with communication protocol information to the mobile terminal based on the mobile terminal's request. Alternatively, the server may be the initiator, actively pushing communication protocol information to the mobile terminal. One or both of these methods can be selected according to actual needs, and no limitation is imposed.

[0065] As an optional implementation, the above-mentioned acquisition of the mobile terminal's status information may specifically include: the mobile terminal acquiring its own status information. 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.

[0066] In the embodiments described in this specification, the mobile terminal can obtain its own status information. After obtaining this status information, the mobile terminal can send a protocol acquisition request to the server based on this information. The server then responds to the received protocol acquisition request by returning communication protocol information to the mobile terminal. By having the mobile terminal obtain its own status information, instead of the server needing to do so, the server's workload is reduced, thus saving server resources.

[0067] As another optional implementation, the above-mentioned acquisition of the mobile terminal's status information may include: the server acquiring the mobile terminal's status information. 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 according to the status information.

[0068] In the embodiments described in this specification, the server can obtain the status information of the mobile terminal. After obtaining the status information, the server can proactively send communication protocol information to the mobile terminal so that the mobile terminal can save the communication protocol information. Having the server obtain the mobile terminal's status information allows the server to choose an appropriate time to send protocol communication information to the mobile terminal, reducing the workload of the mobile terminal. Furthermore, it avoids interference to the server caused by the mobile terminal sending requests to obtain communication protocol information, thereby preventing disruption to the server's normal workflow.

[0069] In practical applications, in order to process communication protocol information more effectively, the server can provide communication protocol information to the mobile terminal only after the mobile terminal's status information meets preset conditions.

[0070] In scenarios where the mobile terminal is the initiator of acquiring communication protocol information, the step of determining the state can be performed by the mobile terminal. Optionally, the mobile terminal sends a protocol acquisition request to the server based on the state information, which may specifically include: the mobile terminal determining whether its state meets a preset state based on the state information; if the mobile terminal's state meets the preset state, then sending a protocol acquisition request to the server.

[0071] In the embodiments of this specification, after the mobile terminal obtains its own status information, it can determine whether its status meets a preset state. If the mobile terminal determines that its status meets the preset state, it can send a protocol acquisition request to the server, causing the server to return communication protocol information in response. If the mobile terminal determines that its status does not meet the preset state, it does not send a protocol acquisition request to the server. It can also continue to obtain subsequent status information and send a protocol acquisition request to the server once its status meets the preset state. By having the mobile terminal determine its own status information, instead of requiring the server to do so, the server's workload is reduced, thus saving server resources.

[0072] To further improve accuracy, in practical applications, after receiving a protocol retrieval request from a mobile terminal, the server can send a status information retrieval instruction to the mobile terminal. After receiving the status information returned by the mobile terminal in response to the status information retrieval instruction, the server verifies the status information. If the verification result indicates that the mobile terminal's status meets a preset state, the server provides communication protocol information to the mobile terminal so that the mobile terminal can save the communication protocol information. If the verification result indicates that the mobile terminal's status does not meet the preset state, the server does not provide communication protocol information to the mobile terminal and sends the verification result to the mobile terminal so that the mobile terminal can further check its status.

[0073] In the embodiments of this specification, after the mobile terminal determines that its state meets a preset state, the server can further verify the state information to improve the accuracy of the state information judgment. It is understood that the process of the server further verifying the state information determined by the mobile terminal to meet the preset state may also be omitted.

[0074] In scenarios where the mobile terminal is the initiator of acquiring communication protocol information, the step of determining the state can also be performed by the server. Optionally, the mobile terminal sends a protocol acquisition request to the server based on the state information, which may specifically include: the mobile terminal sending a protocol acquisition request containing the state information to the server; and the server determining whether the state of the mobile terminal meets a preset state based on the state information.

[0075] In the embodiments of this specification, after the mobile terminal obtains its own status information, it can send a protocol acquisition request containing that status information to the server. Upon receiving the protocol acquisition request, the server can parse the status information from the request. The server can then determine whether the mobile terminal's status meets a preset state based on the received status information. If the server determines that the mobile terminal's status meets the preset state, it provides protocol communication information to the mobile terminal so that the mobile terminal can save the communication protocol information. If the server determines that the mobile terminal's status does not meet the preset state, it does not provide protocol communication information to the mobile terminal.

[0076] To further improve accuracy, in practical applications, if the server determines that the mobile terminal's state does not meet the preset state, the server can return the determination result to the mobile terminal. The mobile terminal can then verify its state based on this state information. If the verification result indicates that the mobile terminal's state meets the preset state, the mobile terminal can resend a protocol acquisition request containing this state information to the server, so that the server can re-determine whether the mobile terminal's state meets the preset state based on this state information. After the server determines that the mobile terminal's state does not meet the preset state, the mobile terminal can further verify the state information to improve the accuracy of the state information determination. It is understood that the operations described above, such as the server returning the determination result to the mobile terminal and the mobile terminal verifying the state information based on the determination result, can also be omitted.

[0077] In practical applications, mobile terminals can also send protocol acquisition requests containing identification information representing the status information to the server, thereby reducing the amount of data sent to the server and saving server storage and network resources.

[0078] In scenarios where the server acts as the initiator of sending communication protocol information, the step of determining the state can be performed by the server. Optionally, the server sends the communication protocol information to the mobile terminal based on the state information, which may specifically include: the server determining whether the state of the mobile terminal meets a preset state based on the state information; if the state of the mobile terminal meets the preset state, then sending the communication protocol information to the mobile terminal.

[0079] In the embodiments of this 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.

[0080] If the server determines that the mobile terminal's state does not meet the preset state, the server may not send communication protocol information to the mobile terminal. Instead, it can continue to acquire subsequent state information from the mobile terminal, sending the communication protocol information only after the mobile terminal's state meets the preset state. This approach reduces the workload on the mobile terminal by allowing the server to determine if the state meets the preset state. Furthermore, it avoids interrupting the server's normal workflow by having the mobile terminal send requests for communication protocol information.

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

[0082] Optionally, the preset state is the state in which the server provides the communication protocol information; determining whether the state of the mobile terminal meets the preset state may include at least one of the following: determining whether the current time of the mobile terminal has reached the period for obtaining communication protocol information; determining whether there is communication protocol information in the server that does not exist in the mobile terminal; determining 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 service; 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; determining whether the mobile terminal connects from a first network to a 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 latency; determining whether the existing communication protocol information in the mobile terminal has expired; determining 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.

[0083] In the embodiments of this specification, the preset state can be a state that meets the conditions for the server to provide communication protocol information to the mobile state. The state of the mobile terminal can be the state information of the mobile terminal obtained by the mobile terminal or the server, or the terminal state further determined based on the obtained state information. For the mobile terminal as the initiator of obtaining communication protocol information, the mobile terminal can determine whether its state meets the preset state; for the server as the initiator of sending communication protocol information, the server can determine whether the state of the mobile terminal meets the preset state.

[0084] In this embodiment, the periodic time can refer to the time during which the mobile terminal periodically obtains communication protocol information from the server. As one implementation, determining whether the current time of the mobile terminal has reached the periodic time for obtaining communication protocol information may include: determining whether the time interval between the current time and the time of the mobile terminal's most recent acquisition of communication protocol information is greater than or equal to the periodic time. If the current time of the mobile terminal has not reached the periodic time for obtaining communication protocol information, i.e., the time interval between the current time and the time of the mobile terminal's most recent acquisition of communication protocol information is less than the periodic time, it indicates 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. If the current time of the mobile terminal has reached the periodic time for obtaining communication protocol information, i.e., the time interval between the current time and the time of the mobile terminal's most recent acquisition of communication protocol information is greater than or equal to the periodic time, it indicates that the state of the mobile terminal meets the preset state, and the process of the server providing communication protocol information may be triggered.

[0085] In this embodiment, the periodic time can also refer to the time during which the server periodically sends communication protocol information to the mobile terminal. Determining whether the current time of the mobile terminal has reached the periodic time for obtaining communication protocol information can also be equivalent to determining whether the current time of the server has reached the periodic time for sending communication protocol information. As one implementation, determining whether the current time of the server has reached the periodic time for sending communication protocol information may specifically include: determining whether the time interval between the server's current time and the server's most recent transmission of communication protocol information is greater than or equal to the periodic time for sending communication protocol information. If the server's current time has not reached the periodic time for sending communication protocol information, i.e., the time interval between the server's current time and the server's most recent transmission of communication protocol information is less than the periodic time for sending communication protocol information, then 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. If the server's current time has reached the periodic time for sending communication protocol information, i.e., the time interval between the server's current time and the server's most recent transmission of communication protocol information is greater than or equal to the periodic time for sending communication protocol information, then the state of the mobile terminal meets the preset state, and the process of the server providing communication protocol information may be triggered. In practical applications, after determining whether the current time of the mobile terminal has reached the period for acquiring communication protocol information and obtaining the determination result, it is possible to further determine one or more other conditions. Based on the determination results for the other one or more conditions, it is determined whether the state of the mobile terminal meets the preset state.

[0086] In this embodiment, it is determined whether communication protocol information not present in the mobile terminal exists in the server. If the server contains such information, the mobile terminal's state meets a preset condition, and the process of the server providing communication protocol information can be triggered. If the server does not contain such information, the mobile terminal's state does not meet the preset condition, and the process of the server providing communication protocol information can not be triggered. In practical applications, after determining whether communication protocol information not present in the mobile terminal exists in the server and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for these other conditions, it can be determined whether the mobile terminal's state meets the preset condition.

[0087] In practical applications, if the server contains communication protocol information that the mobile terminal does not have, the mobile terminal can send a request to the server to obtain the communication protocol information, or the server can send the communication protocol information to the mobile terminal.

[0088] In this embodiment, the card binding page can be a page used to bind a mobile terminal to a card, such as a page used to fill in card information during the card binding process. The system determines whether the mobile terminal displays the card binding page. If the mobile terminal displays the card binding page, it indicates that the mobile terminal's state meets a preset state, and the process of the server providing communication protocol information can be triggered. If the mobile terminal does not display the card binding page, it indicates that the mobile terminal's state does not meet the preset state, and the process of the server providing communication protocol information can not be triggered. In practical applications, after determining whether the mobile terminal displays the card binding page and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for these other conditions, it can be determined whether the mobile terminal's state meets the preset state. This is not limited.

[0089] In practical applications, if a mobile terminal enters the card binding page, the mobile terminal can send a request to the server to obtain communication protocol information, or the server can proactively send communication protocol information to the mobile terminal.

[0090] In this embodiment of the specification, it is determined whether the mobile terminal has launched the target application. The target application is an application that provides card binding service. If the mobile terminal has launched the target application, 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 has not launched the target application, 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 can not be triggered.

[0091] In practical applications, after determining whether the mobile terminal has launched the target application and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for the other one or more conditions, it can be determined whether the state of the mobile terminal meets a preset state. No limitations are imposed on this.

[0092] In practical applications, if the target application providing the card binding service is launched, the mobile terminal can send a request to the server to obtain communication protocol information, or the server can proactively send communication protocol information to the mobile terminal.

[0093] In this embodiment, it is determined whether the mobile terminal successfully parses the near-field communication (NFC) response information provided by the card to be bound using existing communication protocol information. If the mobile terminal fails to parse the NFC response information, it indicates that the mobile terminal's state meets a preset state, and the process of the server providing communication protocol information can be triggered. If the mobile terminal successfully parses the NFC response information, it indicates that the mobile terminal's state does not meet the preset state, and the process of the server providing communication protocol information can not be triggered. In practical applications, multiple conditions can be used to determine whether to trigger the process of the server providing communication protocol information. For example, after determining whether the mobile terminal successfully parses the NFC response information provided by the card to be bound using existing communication protocol information and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for these other conditions, it can be determined whether the mobile terminal's state meets the preset state. This is not limited.

[0094] In practical applications, if a mobile terminal cannot parse the card information based on its local communication protocol information after obtaining the card information, the mobile terminal can send a request to the server to obtain the communication protocol information, or the server can proactively send the communication protocol information to the mobile terminal.

[0095] In this embodiment, it is determined whether the mobile terminal is connected to a second network from a first network; the network parameters of the second network are superior to those of the first network; the network parameters include at least one of signal strength, data transmission speed, and latency. If the mobile terminal is connected to the second network from the first network, it indicates that the mobile terminal's state meets a preset state, and the process of the server providing communication protocol information can be triggered. If the mobile terminal is not connected to the second network from the first network, it indicates that the mobile terminal's state does not meet the preset state, and the process of the server providing communication protocol information can not be triggered. In practical applications, after determining whether the mobile terminal is connected to the second network from the first network and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for the other one or more conditions, it can be determined whether the mobile terminal's state meets the preset state. This is not limited.

[0096] In practical applications, if the mobile terminal's network signal is enhanced, and / or the network speed is faster, and / or the network latency is reduced, the mobile terminal can send a request to the server to obtain communication protocol information. Alternatively, the server can proactively send communication protocol information to the mobile terminal after determining that the mobile terminal's network signal is enhanced, and / or the network speed is faster, and / or the network latency is reduced.

[0097] In this embodiment of the 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 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 existing communication protocol information in the mobile terminal has not expired, 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 can be avoided.

[0098] In practical applications, after determining whether the existing communication protocol information in the mobile terminal has expired and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for the other one or more conditions, it can be determined whether the state of the mobile terminal meets the preset state. No limitations are imposed on this.

[0099] In practical applications, if the communication protocol information already in the mobile terminal has become invalid, the mobile terminal can send a request to the server to obtain the communication protocol information, or the server can proactively send the communication protocol information to the mobile terminal.

[0100] In this embodiment of the specification, it is determined whether the device attribute of the mobile terminal is a preset attribute; the device attribute includes at least one of device system type, device system version, device model, and device brand. If the device attribute of the mobile terminal is a preset attribute, 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 device attribute of the mobile terminal is not a preset attribute, 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 can not be triggered.

[0101] In practical applications, after determining whether the device attributes of the mobile terminal are preset attributes and obtaining the determination result, one or more other conditions can be further determined. Based on the determination results for the other one or more conditions, it can be determined whether the state of the mobile terminal meets the preset state. No limitations are imposed on this.

[0102] In practical applications, the server can deploy communication protocol information for mobile terminals with a first device attribute in the first time period. The first device attribute may include at least one of the following: first device system type (e.g., Android), first device system version (e.g., Android 12), first device model (e.g., device A model 10), and first device brand (e.g., the brand of device A). If the communication protocol information terminal runs well on the mobile terminal with the first device attribute in the first time period, the server can deploy communication protocol information for mobile terminals with a second device attribute in the second time period. The second device attribute may include at least one of the following: second device system type (e.g., iOS), second device system version (e.g., Android 13), second device model (e.g., device A model 11), and second device brand (e.g., the brand of device B).

[0103] In practical applications, the location information of the mobile terminal can also be used to determine whether the state of the mobile terminal meets a preset state. If the location information of the mobile terminal changes, it can be determined that the state of the mobile terminal meets the preset state. For example, if the user of the mobile terminal 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 communication protocol information to the mobile terminal.

[0104] In the embodiments of this specification, multiple judgment conditions can also be used to determine whether the state of the mobile terminal meets the preset state. For example: if the current time of the mobile terminal has not reached the periodic time for acquiring 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 state of the mobile terminal meets the preset state; if the existing communication protocol information in the mobile terminal has not expired, it indicates that the state of the mobile terminal does not meet the preset state. As another example: if the current time of the mobile terminal has reached the periodic time for acquiring communication protocol information, it is determined whether the mobile terminal has connected from the first network to the second network (the network parameters of the second network are superior to those of the first network). If the mobile terminal has not connected from the first network to the second network, it indicates that the state of the mobile terminal does not meet the preset state; if the mobile terminal has connected from the first network to the second network, it indicates that the state of the mobile terminal meets the preset state. In practical applications, it is reasonable to choose to further judge one or more other conditions, and this is not limited.

[0105] In this embodiment of the specification, the mobile terminal can obtain communication protocol information provided by the server before performing the card binding service. The mobile terminal can then perform the card binding service based on the communication protocol information already saved on the terminal. This embodiment of the specification also proposes a specific implementation method for binding cards after the mobile terminal saves the communication protocol information. Optionally, after saving the communication protocol information, the process may further include: the mobile terminal obtaining a first operation performed by the user to obtain card information via near-field communication; based on the first operation, sending instruction information via near-field communication; obtaining response information from the target card in response to the instruction information; parsing the response information using first communication protocol information selected from the various communication protocol information already saved on the mobile terminal to obtain the card information of the target card; and displaying the card information on the card binding page.

[0106] In the embodiments of this specification, the first operation can be an operation performed by the user to obtain card information via near-field communication, such as clicking, swiping, or selecting controls on the card binding trigger page of the mobile terminal. If a card is already bound to the mobile terminal or its target application, the card binding trigger page can also display the bound card information. The instruction information can be an instruction to request the target card to return card information to the mobile terminal, and the response information can be the target card information.

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

[0108] In the embodiments described in this specification, after the first operation is triggered, the mobile terminal responds to the first operation by generating instruction information for obtaining card information of the target card, and sends the instruction information to the target card via near-field communication. In practical applications, the mobile terminal can generate instruction information based on one of the communication protocol information stored locally for card binding.

[0109] In this embodiment, the target card can be a card located near the mobile terminal, or a card to be bound. After receiving the instruction information sent by the mobile terminal, the target card can respond to the instruction information by sending corresponding response information back to the mobile terminal. In practical applications, the instruction information can be information generated by the mobile terminal according to 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 can recognize the instruction information and respond to the instruction information by sending response information back to the mobile terminal. If the communication protocol information corresponding to the target card is inconsistent with the determined communication protocol information, the target card may not be able to recognize the instruction information, and the target card may not send any response information back to the mobile terminal. In practical 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 send response information. Here, there is no specific limitation on whether the target card needs to correctly recognize the instruction information.

[0110] In the embodiments described in this specification, the information stored in the target card or the feedback information fed back to the mobile terminal via near-field communication conforms to 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 correctly obtain the parsing result if it parses the obtained response information according to the determined communication protocol information.

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

[0112] In the embodiments described in this specification, the card binding trigger page can be a page generated by the mobile terminal or a page generated by the server, and there is no limitation on this.

[0113] In the embodiments described in this specification, the communication protocol information is stored on the mobile terminal, so that the card binding operation can be performed based on the communication protocol information on the mobile terminal. This eliminates the 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 the operation based on the information already available locally, thereby improving the efficiency of card binding.

[0114] This specification also provides a specific embodiment of a method for a mobile terminal to send instruction information. Optionally, the method may further include: the mobile terminal sending an electromagnetic signal to trigger near-field communication; and based on the electromagnetic signal, determining whether there is a card with near-field communication functionality near the mobile terminal. Correspondingly, sending instruction information via near-field communication may specifically include: if there is a card with near-field communication functionality near the mobile terminal, then sending instruction information via near-field communication.

[0115] In the embodiments of this specification, the mobile terminal can be a card reader, the card can be a tag, the mobile terminal is responsible for generating electromagnetic signals and sending electromagnetic information to trigger near-field communication, and 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 activate the card reader mode and send electromagnetic signals.

[0116] In this embodiment of the specification, determining whether a card with near-field communication (NFC) functionality exists near the mobile terminal based on the electromagnetic signal may include: determining whether the decrease in 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. If the decrease in signal strength within the preset time period is greater than or equal to the preset threshold, it indicates that a card with NFC functionality exists near the mobile terminal; if the decrease in signal strength within the preset time period is less than the preset threshold, it indicates that no card with NFC functionality exists near the mobile terminal. In practical applications, a card with NFC functionality can receive electromagnetic signals sent by a mobile terminal through its own antenna. Once the electromagnetic signal is received, NFC communication can be established between the card and the mobile device, and the communication parameters of the NFC communication, such as communication speed and mode, can be determined.

[0117] In the embodiments of this specification, if there is a card with near-field communication (NFC) function near the mobile terminal, the mobile terminal generates instruction information for obtaining card information and sends the instruction information to the card with NFC function via NFC.

[0118] In this specification, a specific embodiment of the method for parsing the response information from the card feedback is also proposed.

[0119] Optionally, the step of parsing the response information using first communication protocol information selected from various communication protocol information already stored in the mobile terminal to obtain the card information of the target card may specifically include: parsing the response information using the first communication protocol 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, a second communication protocol information is selected from the various communication protocol information; and the response information is parsed using the second communication protocol information to obtain the card information of the target card.

[0120] In practical applications, if the selected first communication protocol information matches the communication protocol information corresponding to the response information from 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. Successful parsing of the response information can mean processing the response information according to the protocol rules of the first communication protocol information to obtain information that meets preset rules. For example, obtaining a string of a preset number of digits, a string starting at a preset character position, or a string whose constituent elements or structure meet preset requirements. For instance, assuming the card information contains a bank card number, and in practical applications a correct card number is 19 digits, if the parsed card information contains a string consisting of 19 digits, the parsing is successful; if the parsed card information does not contain a string consisting of 19 digits, the parsing is unsuccessful. If the communication protocol information corresponding to the first communication protocol information is inconsistent with the communication protocol information corresponding to the response information, the mobile terminal will be unable to successfully parse the response information based on the first communication protocol information. In this case, the mobile terminal can select the second communication protocol information from the various communication protocol information already stored in the mobile terminal and use it to parse the response information. If the second communication protocol information cannot successfully parse the response information, the mobile terminal can select the third communication protocol information from the various communication protocol information already stored in the mobile terminal and use it to parse the response information. The mobile terminal iteratively selects each of the various communication protocol information already stored in the mobile terminal until it successfully parses the response information and obtains the card information of the target card. The first, second, and third communication protocol information are all different from each other.

[0121] In the embodiments of this 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 this way until the response information is successfully parsed, thereby improving the success rate of parsing the response information.

[0122] In this specification, a specific embodiment is proposed for selecting first communication protocol information from various communication protocol information already stored in the mobile terminal. Optionally, selecting the first communication protocol information from the various communication protocol information already stored in the mobile terminal may specifically 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 SIM card binding services from the various communication protocol information; selecting first communication protocol information corresponding to the nationality or location of the mobile terminal user from the various communication protocol information; or selecting the most recently saved first communication protocol information in the mobile terminal from the various communication protocol information.

[0123] In the embodiments 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 saved in any way, such as the earliest saved communication protocol information, communication information to be saved at a certain time, or the most recently saved communication information, as the randomly selected communication protocol information. Randomly selecting the first communication protocol information from the various communication protocol information ensures that the probability of each communication protocol information being selected is equal, thereby improving the equality of the selection probability of each communication protocol information.

[0124] In the embodiments of this specification, the method for selecting commonly used first communication protocol information of the mobile terminal from the various communication protocol information may include: determining commonly used communication protocol information by identifying communication protocol information that has been used a preset number of times within the most recent preset time period. Using commonly used communication protocol information as the selected communication protocol information can improve the success rate of successfully parsing response information from the first communication protocol information. For example, communication protocol information used within the most recent year or 6 months can be sorted according to the number of times it has been used, and the communication protocol information with the highest number of uses or a number greater than a preset number of uses can be determined as commonly used communication protocol information.

[0125] In this embodiment of the specification, the method for selecting the first communication protocol information most recently used by the mobile terminal in the SIM card binding service from the various communication protocol information may include: determining the communication protocol information used in the most recent one or more SIM card binding services based on the processing time of the SIM card binding services processed by the mobile terminal. Alternatively, the mobile terminal may also record the time information of each communication protocol information used locally, such as a timestamp, and determine the most recent one or more communication protocol information used by the mobile terminal based on this time information. Using the most recently used communication protocol information in the SIM card binding service as the selected communication protocol information can improve the success rate of successfully parsing the response information from the first communication protocol information.

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

[0127] In this embodiment of the specification, the method for selecting the latest first communication protocol information saved to the mobile terminal from the various communication protocol information may include: determining the communication protocol information corresponding to the saving time with the smallest time interval between the saving time and the current time as the latest saved communication protocol information. For any communication protocol information in the mobile terminal, after the mobile terminal obtains the communication protocol information, it can record the time information of obtaining the communication protocol information, which can represent the aforementioned saving time. The current time may be the time when the card is recognized, or the time when the user triggers the card binding service, or the time when the mobile terminal renders or displays the aforementioned card binding trigger page, etc., and is not specifically limited here. Using the latest communication protocol information saved to the mobile terminal as the selected communication information can improve the success rate of successfully parsing the response information from the first communication protocol information.

[0128] In practical applications, the first communication protocol information can be selected according to various selection criteria. For example, a first set 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 SIM card binding service can be selected from the second set of communication protocol information. Another example is that a second set of communication protocol information corresponding to the nationality or location of the mobile terminal user can be selected from the various communication protocol information, and then the first communication protocol information most recently saved to the mobile terminal can be selected from the second set of communication protocol information. Other preset rules can also be used to select the first communication protocol information, and there are no limitations on this.

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

[0130] In this embodiment of the specification, selecting 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 the SIM card binding service from the various communication protocol information; selecting the second communication protocol information corresponding to the nationality or location of the mobile terminal user from the various communication protocol information; and selecting the second communication protocol information most recently saved to the mobile terminal from the various communication protocol information. The method of selecting the second communication protocol information can refer to the method of selecting the first communication protocol information, and will not be repeated here.

[0131] In practical applications, the first communication protocol information can be selected according to a first selection method, and the second communication rule can be selected according to a second selection method. For example, the first communication protocol information can be selected randomly from the various communication protocol information, and the second communication protocol information can be selected from the various communication protocol information to select the communication protocol information commonly used by the mobile terminal. No limitation is imposed on this.

[0132] In the embodiments described in this specification, in order to reduce the pressure on the server, the mobile terminal can first try to obtain the card information using the existing local communication protocol information. If it cannot obtain the information correctly, it can then obtain the communication protocol information from the server.

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

[0134] In the embodiments of this specification, the response information may be card information including the card itself. At least one existing communication protocol information may be one existing communication protocol information, multiple existing communication protocol information, or all existing communication protocol information. The result information may be information indicating that the response information could not be successfully parsed using one existing communication protocol information. The result information may also be information indicating that the response information could not be successfully parsed using a second existing communication protocol information after the first failed attempt. The result information may also be information indicating that the response information could not be successfully parsed using multiple or all existing communication protocol information.

[0135] In this embodiment of the specification, after the mobile terminal receives a trigger operation performed by the user to obtain card information via near-field communication, the mobile terminal can send an electromagnetic signal to trigger near-field communication to the surrounding area. If the mobile terminal detects that the signal strength of the electromagnetic signal sent within a preset time period decreases by more than or equal to a preset threshold, the mobile terminal can determine that there is a card with near-field communication function nearby. Then, the mobile terminal can send instruction information to the card to obtain card information. After receiving the instruction information sent by the mobile terminal, the card can send back response information containing card information to the mobile terminal. Regarding the response information from the card feedback, the mobile terminal can attempt to select a first existing communication protocol information from the various existing communication protocol information it already possesses. The mobile terminal uses the first existing communication protocol information to parse the response information. If the parsing fails, the mobile terminal sends a communication protocol information retrieval request to the server. Alternatively, the mobile terminal can attempt to select a second existing communication protocol information from the various existing communication protocol information it already possesses. If the parsing still fails, the mobile terminal sends a communication protocol information retrieval request to the server. Or, the mobile terminal can continue to try selecting a third existing communication protocol information. This process is repeated until the number of unsuccessful parsing attempts reaches a preset number, at which point the mobile terminal sends a communication protocol information retrieval request to the server. Alternatively, if the mobile terminal selects all the existing communication protocol information it already possesses and still fails to parse the information, the mobile terminal sends a communication protocol information retrieval request to the server.

[0136] As another implementation, after the mobile terminal receives a trigger operation from the user to obtain card information via near-field communication, or after the mobile terminal determines that a card exists nearby, the mobile terminal can select a first existing communication protocol from the various existing communication protocol information it already possesses, and send instruction information via near-field communication according to the protocol rules of the first existing communication protocol information. If the mobile terminal does not receive a response from the card within a preset time period, the mobile terminal can send a communication protocol information retrieval request to the server, or it can select a second existing communication protocol from the various existing communication protocol information it already possesses, and send instruction information according to the protocol rules of the second existing communication protocol information. The protocol rules send instruction information through near-field communication. If the mobile terminal does not receive a response from the card within a preset time period, it can send a communication protocol information retrieval request to the server. Alternatively, it can select a third existing communication protocol from the existing communication protocol information already available in the mobile terminal. This process is repeated until the number of times the card response cannot be obtained reaches a preset number. Then, the mobile terminal can send a communication protocol information retrieval request to the server. Alternatively, if the mobile terminal still cannot obtain a response from the card after selecting all the existing communication protocol information available in the mobile terminal, it can send a communication protocol information retrieval request to the server.

[0137] In the embodiments described in this specification, the mobile terminal will only request new communication protocol information from the server when none of the existing communication protocol information saved by the mobile terminal can successfully parse the response information fed back by the card. This avoids the defect of requesting communication protocol information from the server for every card binding task of the mobile terminal.

[0138] In the embodiments described in this specification, the server can provide full communication protocol information to the mobile terminal, or it can provide communication protocol information that is 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; or, the communication protocol information fed back by the server is full communication protocol information that the server possesses.

[0139] In the embodiments of this 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 already stored locally on the mobile terminal to the server. This allows the server to know the existing communication protocol information already stored locally on the mobile terminal based on the protocol identifiers sent by the mobile terminal, and then determine the communication protocol information that does not exist in the mobile terminal, and send the determined communication protocol information that does not exist in the mobile terminal to the mobile terminal.

[0140] In practical applications, the server can record information about various communication protocols that have been sent to the mobile terminal. For example, the server can record which communication protocols have been sent to which mobile terminals. When the server sends communication protocol information again, it can determine the communication protocol information that has already been sent to the mobile terminal based on the server's records. In other words, it can determine the various existing communication protocol information that has been stored locally on the mobile terminal. Furthermore, the server can determine the communication protocol information that has not yet been sent to the mobile terminal. In other words, it can determine the various communication protocol information that does not exist in the mobile terminal. The server can then send the determined communication protocol information that does not exist in the mobile terminal to the mobile terminal.

[0141] In practical applications, communication protocol information can be maintained on the server side. If developers or administrators determine new communication protocol information, they can save the new communication protocol information to the server. The server can actively push the new communication protocol information to the mobile terminal, or the mobile terminal can actively request the server to send the new communication protocol information.

[0142] 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 form, such as a component, module, or plug-in, so that the mobile terminal does not need to update the entire application client.

[0143] In the embodiments of this specification, the server can send all 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 already saved locally and supplement the communication protocol information not saved locally based on the full communication protocol information.

[0144] In this embodiment, the server can pre-generate a public-private key pair, store the private key on the server, and send the public key to the mobile terminal so that the mobile terminal can store the public key. In practical applications, before sending communication protocol information to the mobile terminal, the server can encrypt the communication protocol information to be sent using the private key, and then send the encrypted communication protocol information to the mobile terminal. After receiving the encrypted communication protocol information, the mobile terminal can decrypt the encrypted communication protocol information using the locally stored public key to obtain the communication protocol information, thereby improving the security of the communication protocol information to be sent. In practical applications, the server can compress the communication protocol information to be sent based on a preset compression rule, and then send the compressed communication protocol information to the mobile terminal. After receiving the compressed communication protocol information, the mobile terminal can decompress the compressed communication protocol information using a decompression rule corresponding to the preset compression rule to obtain the communication protocol information, thereby reducing the amount of data transmitted for the communication protocol information to be sent and saving network transmission resources.

[0145] In practical applications, the server can also encrypt and compress the communication protocol information to be sent, and then send the processed communication protocol information to the mobile terminal. This can improve the security of the communication protocol information to be sent, reduce the amount of data transmitted, and save network transmission resources.

[0146] Based on and Figure 2 Following the same approach as the scheme shown, this specification also provides a card-binding method based on near-field communication in its embodiments. Figure 4 This is a flowchart illustrating a card-binding method based on near-field communication provided in the embodiments of this specification.

[0147] From a programmatic perspective, the entity executing the process can include a program mounted on a mobile terminal for SIM card binding based on near-field communication. From a hardware perspective, the entity executing the process can include the mobile terminal itself. It can be understood that a mobile terminal can be any device, equipment, platform, or cluster of devices with computing and processing capabilities.

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

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

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

[0151] For example, Figure 5A This is a schematic diagram of a target application provided in an embodiment of this specification. For example... Figure 5A As shown, this page can be the homepage of the target application. This page can include a control 501 for executing the card binding process. Clicking control 501 triggers the card binding operation. The page can also include controls such as "Scan," "Payment," "Travel," and "Wallet" for quickly launching corresponding functions, as well as tabs for various applications.

[0152] It should be noted that the card binding trigger operation can also be an operation performed by the user on controls used for card binding on other pages, such as the user's operation on controls displayed on the card binding trigger page mentioned above, etc., and there is no limitation on this.

[0153] In practical applications, the card binding trigger operation can 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 embodiments. After the user triggers the card binding trigger operation, the mobile terminal and / or the server can execute the corresponding card binding process.

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

[0155] Figure 5A or Figure 5B This can also refer to the card binding trigger page described in the above embodiments. In practical applications, during the card binding process, the terminal can display... Figure 5A as well as Figure 5B For example, you can first display Figure 5A Then it will be displayed. Figure 5B Among these, activating the NFC reader function on a mobile terminal can be done after the user has made the above-mentioned... Figure 5AIt is activated after the control 501 in the middle performs an operation, or it can be activated after the user interacts with the above. Figure 5B The control 505 in the middle is activated after performing an operation.

[0156] As another implementation method, the terminal may also only display Figure 5A or Figure 5B One of them. For example, the terminal can display Figure 5A After the user performs an operation on control 501, the terminal can activate the near-field communication (NFC) function to obtain card information from nearby cards. Once the card information is obtained, a card binding page containing that information is displayed. Alternatively, the application homepage may not include a control for binding cards via NFC; the user can follow the existing card binding process to access a page that triggers the binding process. Figure 5B The page shown is for obtaining card information, also known as the card binding trigger page. After the user performs an operation on control 505, the terminal can execute the process of obtaining card information through near-field communication.

[0157] Step 404: Based on the card binding trigger operation, obtain the response information fed back by the target card through near-field communication.

[0158] In the embodiments of this specification, the card binding control can be a control indicating card binding via NFC, and the card binding trigger operation can be a trigger operation targeting this control. For example, regarding the above... Figure 3 The NFC control within the first area 301 of the card binding trigger page is activated, or the above-mentioned... Figure 5B The trigger action of control 505 in another page of a target application.

[0159] In the embodiments of this specification, the target card can be the card that needs to be bound, and the response information can be the card information in the target card.

[0160] In practical applications, the mobile terminal acts as a card reader, emitting electromagnetic information in all directions to detect whether there are cards with near-field communication (NFC) capabilities nearby. If the mobile terminal detects a card with NFC capabilities nearby, it sends a command to the card to obtain card information. The card responds to the command by sending a response message back to the mobile terminal.

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

[0162] In this embodiment of the specification, after receiving the response information from the target card, the mobile terminal can parse the response information using first communication protocol information selected from various communication protocol information already stored in the mobile terminal to obtain the card information of the target card. The card information may include at least one of the following: the target card number, the target card's expiration date, the issuing bank of the target card, and the user information corresponding to the target card.

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

[0164] Step 408: Display the card information to the card binding page.

[0165] In this embodiment of the specification, after the mobile terminal successfully parses the response information returned by the target card, it can display the parsed card information of the target card to the user on the card binding page so that the user can verify it.

[0166] Figure 4 The proposed method involves the mobile terminal and the target card interacting via tap-to-tap or stick-to-stick. The mobile terminal obtains the target card's information through near-field communication (NFC) and displays this information on the card-binding page. This eliminates the need for the user to manually input the card's information, simplifying the card-binding process. The mobile terminal can parse the card information obtained through NFC using locally stored communication protocol information. This eliminates the need for the mobile terminal to interact with the server every time a card-binding transaction is processed, reducing the time required for the binding process and improving the user experience.

[0167] based on Figure 4 In addition to the method described herein, this specification also provides some specific implementation methods of the method, which will be described below.

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

[0169] In the embodiments of this specification, the prompting information used to guide the user to bind the card using near-field communication (NFC) can be in text form, such as "Place your phone close to the card," "Bind the card via NFC," or "Add card information via NFC." The prompting information can also be in image form, such as an image or animation showing the mobile terminal and the card being tapped together.

[0170] In this embodiment of the 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 (NFC). The preset control may carry words such as "Start," "Confirm," "Submit," or "Try." The first confirmation operation can be a confirmation operation performed by the user on the preset control, which can be any of the following operations: click, swipe, or selection. In practical applications, the mobile terminal responds to the user's first confirmation operation on the preset control on the card binding prompt page by generating instruction information for obtaining response information via NFC. The mobile terminal sends this instruction information to the target card via NFC, and the target card responds to the instruction information by sending response information back to the mobile terminal via NFC. During the card binding process using the mobile terminal, a reminder message for card binding via NFC can be displayed to the user, prompting them to select NFC for card binding so that they can correctly bind their cards via NFC.

[0171] 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 an image-based prompt 601 and a text-based prompt 603 to prompt the user to bind the card via near-field communication (NFC). The card binding prompt page may also include a preset control 602, which the user can trigger to instruct the terminal to perform the card binding process via NFC.

[0172] 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 can be a response process page using near-field communication (NFC). 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 based on NFC via NFC. After the mobile terminal obtains the card information fed back by the target card, the card binding prompt page can automatically close, and the mobile terminal can then display the card binding page.

[0173] To improve the success rate of card binding between the mobile terminal and the target card, prompts can be displayed to the user during the binding process to guide them through the process. Optionally, after the mobile terminal receives the card binding trigger operation performed by the user, the process may further include: displaying a recognition response page while the mobile terminal receives the response information fed back by the target card via near-field communication; the recognition response page includes prompts to guide the user on the operations that need to be performed during the card binding process.

[0174] In this embodiment of the specification, the identification response page can be a page displayed by the mobile terminal to the user during the card binding process via near-field communication, guiding the user through the card binding operation. The identification response page may include real-time information to inform the user of the card binding operation, such as displaying phrases like "Ready to scan" to inform the user that a scanning operation will proceed. The identification response page may also include reminders for user precautions during the card binding process, such as displaying phrases like "Keep your phone close to the card, do not move," to guide the user on the correct card binding operation and improve the success rate.

[0175] In practical applications, the recognition response page can be displayed as a pop-up window within the card binding prompt page. Alternatively, the recognition response page can be displayed independently of the card binding prompt page, or the two pages can be the same. No specific limitations are imposed here. In practical applications, after the mobile terminal receives the user's card binding trigger operation, it can display either the card binding prompt page or one of the recognition response pages; alternatively, after receiving the user's card binding trigger operation, the mobile terminal can display the card binding prompt page first, followed by the recognition response page. No limitations are imposed in this regard.

[0176] To facilitate user operation, the identification response page may optionally include a cancellation control for canceling interactions via near-field communication.

[0177] In this embodiment of the specification, a cancellation control is set in the recognition response page, which makes it easier for users to cancel the card binding operation via near field communication, thereby improving the user experience during the card binding process.

[0178] For example, Figure 7 This is a schematic diagram illustrating an example of identifying a response page provided in this specification. For example... Figure 7 As shown, the response page can include real-time information 701 about the card binding operation, as well as operational precautions 702 during the card binding process, to improve the success rate of card binding for users. It can also include a cancellation control 703 to allow users to terminate the card binding operation.

[0179] Optionally, the method may further include: if a user's operation on the cancel control is detected, then terminating the process of obtaining card information via near-field communication.

[0180] In the embodiments of this specification, the user's operation on the cancel control can be any one of the following: a click operation, a swipe operation, or a selection operation. After the user triggers the cancel control operation, the user can disable the card binding operation between the mobile terminal and the target card via near-field communication, or the user can disable the card reader function of the mobile terminal. If the mobile terminal has already received the response information from the target card when the user triggers the cancel control operation, the parsing operation for that response information can be stopped. In practical applications, after the user triggers the cancel control operation on the recognition response page, the display page on the mobile terminal can return to the previous page of the recognition response page, such as the card binding prompt page. Alternatively, it can return to other pages, such as the homepage of the target application used for card binding, etc., without limitation.

[0181] In the embodiments described in this specification, users can terminate the card binding operation between the mobile terminal and the target card at any time by operating the cancel control on the recognition response page. This allows for timely mitigation of losses should the user's card binding intention change, thereby improving the user experience when binding cards.

[0182] To avoid prolonged user waiting, the system can prompt the user to rescan if the scanning time is too long or exceeds a preset time. Optionally, after the mobile terminal obtains the card binding trigger operation performed by the user, it can further include: if the mobile terminal does not detect a card with near-field communication (NFC) functionality within a first preset time, a first abort page is displayed; the first abort page contains a prompt indicating that card information was not successfully obtained.

[0183] In this embodiment of the specification, the start time of the first preset duration can be the moment when the user performs the card binding trigger operation. If, within the first preset duration after the user performs the card binding trigger operation, the mobile terminal does not detect a card with near-field communication function near the terminal, the mobile terminal can display a first abort page. The first preset duration can be reasonably set according to the actual scenario. For example, the first preset duration can be 10 seconds, 20 seconds, 30 seconds, etc., or it can be other durations, which are not limited.

[0184] In the embodiments of this specification, the mobile terminal does not detect a card with near-field communication function. This can be understood as the mobile terminal not detecting a card with near-field communication function if the signal strength at the mobile terminal decreases by less than a preset threshold within a first preset time period.

[0185] In this embodiment of the specification, the first abort page can indicate a temporary halt to card binding via near-field communication. The first abort page may include a message indicating that card information was not successfully obtained, such as "Scan failed." Alternatively, the first abort page may also include card binding operation information to guide the user, such as "Scan interrupted, please place the front of the card firmly against the chip area on the back of the phone." During the scanning process of the target card by the mobile terminal, if the scanning time is too long, an abort page can be displayed to the user to prompt them to correct their operation, thereby improving the card binding success rate.

[0186] Optionally, the first abort page may also include a first control indicating a process for re-executing the process of obtaining card information via near-field communication.

[0187] In this embodiment, a first control is provided on the first abort page for re-executing the process of obtaining card information via near-field communication. This allows the user to immediately rescan after noticing a scan failure, improving the timeliness of card binding. In practical applications, a countdown control may be displayed on the first abort page. After the countdown ends, the card information in the target card may be automatically re-identified, or the card binding process may be automatically exited; this is not limited.

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

[0189] Optionally, the method may further include: if user operation on the first control is detected, restarting the process of obtaining card information via near-field communication.

[0190] In the embodiments described in this specification, the user's operation on the first control can be any one of a click operation, a swipe operation, or a selection operation. After the user triggers an operation on the first control, the mobile terminal can resend electromagnetic signals to detect whether there is a target card with near-field communication capability near the mobile terminal. In practical applications, after the user triggers an operation on the first control on the first pause page, the mobile terminal can re-display either the card binding prompt page or the identification response page, or it can display the card binding prompt page first and then the identification response page; there is no limitation on this.

[0191] In this embodiment of the specification, the user can restart the process of obtaining card information via near-field communication by operating the first control on the first abort page, thereby improving the convenience of restarting the card binding process.

[0192] To avoid prolonged user waiting times, if the scanning time is too long or exceeds a preset duration, a prompt indicating that card information was not successfully obtained can be displayed on the recognition 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 duration, displaying a prompt indicating that card information was not successfully obtained on the recognition response page.

[0193] In this embodiment, the start time of the second preset duration can be the moment when the user performs the card binding trigger operation. The second preset duration can be the same as the first preset duration, for example, both can be 10 seconds, 20 seconds, 30 seconds, 40 seconds, or other durations. The second preset duration can also be different from the first preset duration, which is not limited. In practical applications, a pop-up message can be displayed on the recognition response page, indicating that the card information acquisition failed, such as "scan failed". In practical applications, the pop-up message indicating that the card information was not successfully acquired can be displayed on the recognition response page after waiting for a preset duration, or it can be displayed after the user performs an operation on the recognition response page. The preset duration can be 3 seconds, 5 seconds, or other durations, which is not limited. During the scanning process of the target card by the mobile terminal, if the scanning time is too long, a recognition response page with a message indicating that the card information was not successfully acquired can be displayed to the user to prompt the user to re-identify, thereby improving the card binding success rate.

[0194] For example, Figure 9This is a schematic diagram of another identification response page provided in the embodiments of this specification. For example... Figure 9 As shown, the recognition response page may include a prompt message 901 indicating that the card information was not successfully obtained, so as to prompt the user to re-identify.

[0195] It should be noted that, Figure 7 The recognition response page in the middle and Figure 9 The identification response page can be the same page or different pages. In practical applications, it can be displayed first. Figure 7 The recognition response page will then display the following if recognition fails: Figure 9 The recognition response page. Alternatively, it can be left undisplayed. Figure 7 The recognition response page in the system will directly display the message if recognition fails after the recognition process is triggered. Figure 9 The identification response page in the middle is not limited to this.

[0196] In practical applications, after the recognition process is triggered, either the first abort page can be displayed without the recognition response page, or only the recognition response page can be displayed without the first abort page; there is no limitation on this. In practical applications, the first abort page and / or the recognition response page can automatically close after a preset duration to allow the mobile terminal to display other pages.

[0197] In practical 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 can also display a reading failure message to the user.

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

[0199] In this embodiment of the specification, after the mobile terminal performs a reading operation on the target card via near-field communication (NFC), if no response information is read from the target card, a second abort page can be displayed to the user. Alternatively, after the mobile terminal performs a reading operation on the target card via NFC, it can read response information from the target card. After parsing the read response information, if the parsed information does not contain card specification information, such as card number, card issuing institution information, card manufacturing date information, or cardholder information, a second abort page can be displayed to the user. The second abort page may include a prompt indicating that the target card cannot be identified via NFC, such as the message "This card does not support identification via NFC."

[0200] In this embodiment of the specification, after the mobile terminal reads the target card via near-field communication, if the card information of the target card cannot be identified from the target card, it can display a prompt message to the user indicating that the card cannot be identified, so as to prompt the user that the target card cannot be bound via near-field communication, thereby prompting the user to use other methods to bind the card.

[0201] Optionally, the second abort page may also include at least one of a second control indicating the initiation of a non-near-field communication method for obtaining card information and a third control indicating the re-execution of the process of obtaining card information via near-field communication.

[0202] The methods for obtaining card information without near-field communication (NFC) can include manual input or photographing. Re-executing the process of obtaining card information via NFC can be understood as re-executing the process for the original card or for other cards. The second abort page includes second and / or third controls to facilitate users in selecting alternative card binding methods, thereby increasing the diversity of card binding methods and improving the user experience.

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

[0204] To improve the success rate of card binding, if the target card cannot be bound via near-field communication within a preset time period, a page can be displayed to the user indicating that the target card can be bound using other methods. 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, a card addition page indicating that card information can be provided using non-near-field communication methods is displayed.

[0205] In this embodiment, the start time of the third preset duration can be the moment when the user performs the card binding trigger operation. The third preset duration can be greater than or equal to the first preset duration, or it can be greater than or equal to the second preset duration, or it can be greater than or equal to both the first and second preset durations. For example, the third, second, and first preset durations can be the same, such as 10 seconds, 20 seconds, 30 seconds, 40 seconds, or other durations; or the preset durations can be different, without limitation. If the mobile terminal fails to obtain card information through near-field communication, it may indicate that the mobile terminal has not identified the target card through near-field communication, or it may indicate that the mobile terminal has not parsed the target card information from the response information returned by the target card through near-field communication. The card adding page can include prompts for obtaining card information through methods other than near-field communication to increase the diversity of card binding methods for users, thereby increasing the success rate of card binding.

[0206] For example, Figure 11 This is a schematic diagram of a card-adding page provided in an embodiment of this specification. Figure 11 As shown, the card addition page may include an area 1101 indicating that card information is provided using a non-near-field communication method. Users can enter card information manually or by taking a photo in area 1101. The card addition page may also include a submission control 1102. After the user enters card information in area 1101, triggering the submission control 1102 will execute the subsequent card binding process.

[0207] In practical applications, if the mobile terminal fails to parse the card information of the target card from the response information, the mobile terminal may display either the second suspension page or the card addition page. Alternatively, after displaying the second suspension page, if the mobile terminal does not receive any user-triggered operation on the second suspension page within a preset time period, the mobile terminal may close the second suspension page and display the card addition page; this is not limited.

[0208] If, after triggering the operation of the first control on the first aborted page, the target card information is still not recognized after rescanning, the card addition page can also be displayed to the user so that the user can choose other methods to bind the card.

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

[0210] In the embodiments of this specification, the explanations for obtaining card information without near-field communication (NFC) and providing card information through non-NFC methods can be found above and will not be repeated here. In practical applications, during the process of the mobile terminal obtaining the response information fed back by the target card via NFC, if the mobile terminal fails to identify the target card, it may not display the first abort page, or trigger the control on the first abort page used to re-execute the card binding operation, but directly display the card adding page. This is not limited.

[0211] Optionally, the non-near-field communication method may include at least one of manual input or photographing.

[0212] In the embodiments of this specification, the card binding prompt page, identification response page, first suspension page, second suspension page, card addition page, etc., can be pages generated by the mobile terminal or pages generated by the server, and there is no limitation on this.

[0213] In this embodiment of the specification, in order to enable users 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 card information. The mobile terminal can submit the obtained card information to the server for card binding based on the user's operation of the control.

[0214] Optionally, after displaying the card information to the card binding page, the process may further include: obtaining an 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; and the server being able to execute the card binding process based on the card information.

[0215] In the embodiments of this specification, the information submission operation can be a submission operation performed by the user on the submission control on the card binding page after verifying that the card information displayed on the card binding page is correct. The submission operation can be any one of the following: click operation, swipe operation, and box selection operation.

[0216] For example, Figure 12This is a schematic diagram of a card binding page provided in an embodiment of this specification. For example... Figure 12 As shown, the card binding page may include a submit control 1205 indicating confirmation of card binding, and 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 practical applications, the card information displayed in areas 1201, 1202, and 1203 can be obtained by the mobile terminal from the card to be bound via near-field communication, without requiring manual input by the user. The card information displayed in areas 1201, 1202, and 1203 is all editable; if the user finds an error, they can manually modify it or re-obtain it via near-field communication. Of course, in practical applications, users can also manually input the corresponding card information in areas 1201, 1202, and 1203. No specific limitations are imposed here.

[0217] In this embodiment, after receiving the user's submission operation, the mobile terminal can send the card information and the identification information associated with the mobile terminal from the card binding page to the server. Upon receiving the card information and the identification information associated with the mobile terminal, the server can associate the card information with the identification information to complete the card binding operation between the card information and the identification information. In practical applications, the server executing the card binding process and the server providing the communication protocol information can be the same server or different servers; this is not limited.

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

[0219] For example, continue with Figure 3 For example, Figure 3 The card binding trigger page can also include a new card binding area 305 that displays the newly bound card by the user.

[0220] In practical applications, the identification information associated with a mobile terminal can be its device identification information, such as a unique device identifier. It can also be the identification information of the target application installed on the mobile terminal, such as the application identifier.

[0221] In the embodiments of this specification, before sending the card information and the identification information associated with the mobile terminal from the card binding page 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 amount of data to be transmitted.

[0222] To improve the compliance of card binding, a card binding authorization page can be displayed to users before submitting the card information to the server.

[0223] Optionally, after obtaining the information submission operation performed by the user based on the card binding page, the process may further include: displaying a card binding authorization page; the card binding authorization page includes the card information. Correspondingly, sending the card information to the server may specifically include: obtaining the authorization confirmation operation performed by the user based on the card binding authorization page, and sending a card binding request containing the card information to the server.

[0224] In this embodiment, the card binding authorization page is a page used by the user to authorize the server to bind the target card to the mobile terminal. After the user triggers an operation on the submit control on the card binding page, the mobile terminal can display the card binding authorization page to the user. The card binding authorization page may contain card information so that the user can confirm whether the card information is correct, thereby improving the success rate of card binding. The card binding authorization page may also contain an authorization confirmation control. After the user operates on the authorization confirmation control, it indicates that the user authorizes the server to bind the target card to the mobile terminal.

[0225] In practical applications, the card binding authorization page can be displayed first, and after the user confirms the authorization information on the card binding authorization page, the card binding page can be displayed again, and then the subsequent card binding process can be executed through the card binding page.

[0226] It's understandable that after a user triggers the submit control on the card binding page, the card binding authorization page doesn't necessarily need to be displayed. The user's action of submitting the control on the card binding page signifies authorization to the server to bind the target card to the mobile terminal. For example, the card binding page could include optional user authorization agreement information; the user's submission indicates agreement to authorize and execute the card binding process. Specific page display and operation methods are not limited here. In practical applications, after a user triggers the submit control on the card binding page, the mobile terminal can send the card information to the server. After receiving the authorization instruction from the mobile terminal, the server then executes the card binding process between the mobile terminal and the card information.

[0227] In practical applications, the card binding authorization page and the card binding page can be the same page. The authorization and submission operations can be independent. For example, after a 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 also be the same operation; when the user clicks submit, it means that the user has performed both the authorization and submission operations.

[0228] In the embodiments of this specification, the card binding authorization page, card binding page, and other pages can be pages generated by the mobile terminal or pages generated by the server, and there is no limitation on this.

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

[0230] In this embodiment, the Card Verification Value (CVV) can be a card verification code set by the issuing institution of the target card for the target card. The CVV is used to verify whether the user initiating the card binding is the legitimate holder of the target card. In practical 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 that area.

[0231] In practical applications, card information, a security verification code, and identification information related to the mobile terminal are sent to the server. Upon receiving these documents, the server first verifies whether the security verification code matches the verification code of the target card corresponding to the card information. If the security verification code matches, the server performs a card binding operation based on the card information and the identification information related to the mobile terminal. If the security verification code does not match, the server does not perform the card binding operation. Furthermore, the server can return a verification result to the mobile terminal, allowing the mobile terminal to resubmit the security verification code.

[0232] In practical applications, before sending the card information, security verification code, and identification information associated with the mobile terminal from 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 amount of data to be transmitted.

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

[0234] In practical applications, the page used to fill in the security verification code can be any page other than the card binding page. After the mobile terminal obtains the card information via near-field communication, it can display the card information on the card binding page. After the user confirms the card information on the card binding page, the card binding page can be redirected to the page for filling in the security verification code by triggering the card binding page. Alternatively, the card binding page can automatically redirect 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, they can click the submit control on the page to execute the subsequent card binding process.

[0235] It is understandable that the above pages may or may not be displayed during the actual card binding process, as long as the display is logical. Furthermore, the above pages may be the same page or different pages, as long as the corresponding page information can be displayed to enable the user to bind the card. There are no restrictions here.

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

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

[0238] In the embodiments described in this specification, the instruction information can be an instruction to request the target card to return card information to the mobile terminal, and the response information can be the card information of the target card. After the card binding trigger operation is triggered, the mobile terminal responds to the card binding trigger operation by generating instruction information for obtaining the card information of the target card, and sends the instruction information to the target card via near-field communication. In practical applications, the mobile terminal can generate instruction information based on one of the communication protocol information for card binding stored locally.

[0239] In the embodiments described in this specification, the target card can be a card located near the mobile terminal, or it can be referred to as a card to be bound. After receiving the instruction information sent by the mobile terminal, the target card can respond to the instruction information by sending corresponding response information back to the mobile terminal.

[0240] To avoid the mobile terminal interacting with the server every time it processes a SIM 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 already saved in the mobile terminal, the process may further include: obtaining the communication protocol information sent by the server; and saving the communication protocol information.

[0241] In the embodiments of this specification, the communication protocol information sent by the server can be the communication protocol information for binding the card that is already present on the server. 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 did not exist on the mobile terminal before the server sent it, allowing the mobile terminal to obtain communication protocol information that is not stored on the mobile terminal. In practical applications, if the server does not have communication protocol information that is not stored locally on the mobile terminal, the server may choose not to send the communication protocol information to the mobile terminal.

[0242] In the embodiments described in this specification, the mobile terminal can save the communication protocol information sent by the server in its local storage unit so as to bind the card based on the locally stored communication protocol information.

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

[0244] The interpretation of the status information can be found in the explanation above. In this embodiment, the mobile terminal can obtain the communication protocol information provided by the server in the manner described in the embodiment for obtaining communication protocol information, which will not be repeated here. In practical applications, the mobile terminal can obtain its own status information. After obtaining the status information, the mobile terminal can determine whether its status meets a preset state. If the mobile terminal determines that its status meets the preset state, it can send a protocol acquisition request to the server. If the mobile terminal determines that its status does not meet the preset state, it can choose not to send a protocol acquisition request to the server. It can also continue to obtain subsequent status information of the mobile terminal, and then send a protocol acquisition request to the server after the mobile terminal's status meets the preset state.

[0245] In the embodiments described in this specification, the mobile terminal obtains and determines the status information of the mobile terminal, without the need for the server to obtain and determine the status information of the mobile terminal, thereby reducing the workload of the server and saving server resources.

[0246] It should be noted that, Figure 3 , Figure 5A , Figure 5B , Figures 6 to 12 The information shown is for illustrative purposes only. In actual applications, different information may be displayed than shown in the image. Specifically, other text, images, animations, controls, etc., may be displayed. Figure 3 , Figure 5A , Figure 5B , Figures 6 to 12 The information displayed is not specifically limited.

[0247] To more clearly illustrate the methods provided in the embodiments of this specification, Figure 13 This is a swimlane flowchart illustrating a method for obtaining communication protocol information and binding a card, as provided in an embodiment of this specification. The business execution flow of this method may involve execution entities such as the target card, mobile terminal, and server.

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

[0249] In the embodiments of this 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. 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.

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

[0251] Step 1304: The server responds to the protocol acquisition request sent by the mobile terminal and provides communication protocol information to the mobile terminal.

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

[0253] It is understood that this is only an example of obtaining communication protocol information from the server by launching a terminal application. In actual applications, one or more of the various triggering conditions described above can also be used, which are not limited here.

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

[0255] Among them, the card binding trigger operation can be the first operation performed by the user to obtain card information through near-field communication.

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

[0257] Step 1312: The target card responds to the received instruction information by sending a response message back to the mobile terminal.

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

[0259] Step 1316: The mobile terminal uses the first communication protocol information selected from the various communication protocol information already stored in the mobile terminal to parse the response information and obtain the card information of the target card.

[0260] Step 1318: Display the card information to the card binding page.

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

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

[0263] For example, the server can establish a correspondence between the card information and a mobile terminal or a terminal application linked to the card, allowing the user to use the card to conduct business through that mobile terminal or the linked terminal application. Specific card-linking procedures can be found in relevant technical documentation and will not be elaborated upon here.

[0264] In practical applications, the steps related to the communication protocol information storage phase do not need to be executed before each card binding phase step. That is, the steps related to the communication protocol information storage phase and the card binding phase can be executed independently. Alternatively, the execution time interval between the steps related to the communication protocol information storage phase and the card binding phase steps can be relatively long, as long as the mobile terminal can obtain the card information based on the locally stored communication protocol information. Here, there are no specific restrictions on the execution order and time of each step.

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

[0266] Figure 14 This is a schematic diagram of the structure of a device for obtaining communication protocol information provided in the embodiments of this specification.

[0267] like Figure 14 As shown, the device may include:

[0268] The status acquisition module 1402 is used to acquire the status information of the mobile terminal; the determination module 1404 is used 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 to obtain card information for binding the card from a target type card that supports near-field communication via near-field communication; the protocol acquisition module 1406 is used to acquire the communication protocol information fed back by the server according to the process; the communication protocol information includes communication protocol information that did not exist in the mobile terminal before the process was triggered; the protocol storage module 1408 is used to store the communication protocol information fed back by the server in the mobile terminal.

[0269] Figure 15 This is a schematic diagram of a card-binding device based on near-field communication provided in the embodiments of this specification.

[0270] like Figure 15 As shown, the device may include:

[0271] The trigger operation acquisition module 1502 is used by the mobile terminal to acquire the card binding trigger operation performed by the user. The response information acquisition module 1504 is used to acquire the 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 first communication protocol information already 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.

[0272] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0273] Figure 16 This is a structural block diagram of a computer device provided in an embodiment of this specification. Figure 16 As shown, 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 being executed by the at least one processor 1610 to enable the at least one processor 1610 to perform the above-described method for obtaining communication protocol information or the above-described card binding method based on near-field communication.

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

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

[0276] An embodiment of this specification also provides a computer-readable storage medium storing a computer program or instructions that, when executed by a processor, implement the steps of the method for obtaining communication protocol information described above, or the steps of the card-binding method based on near-field communication described above.

[0277] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the computer-readable storage medium embodiments are basically similar to the method embodiments described above, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments above.

[0278] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0279] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as 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 should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0280] The controller can be implemented in any suitable manner. For example, it 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, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0282] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

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

[0284] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0285] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0286] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0288] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (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, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0289] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0290] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0291] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for obtaining communication protocol information, comprising: Obtain the status information of the mobile terminal; The status information is the status that meets the conditions for the server to provide communication protocol information to the mobile terminal. Based on the aforementioned status information, the process of the server providing communication protocol information is triggered. 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 the target type of card; According to the process described above, the mobile terminal obtains the communication protocol information fed back by the server; The mobile terminal stores the communication protocol information fed back by the server, so that the mobile terminal can use the locally stored communication protocol information to read the card information of the card to be bound.

2. The method as described in claim 1, wherein obtaining the status information of the mobile terminal specifically includes: The mobile terminal acquires the status information of the mobile terminal; Alternatively, the server may obtain 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: Based on the status information, the mobile terminal sends a protocol acquisition request to the server; Alternatively, the server may send the communication protocol information to the mobile terminal based on the status information.

3. The method as described in claim 2, wherein the mobile terminal sends a protocol acquisition request to the server based on the status information, specifically including: Based on the status information, the mobile terminal determines whether the status of the mobile terminal meets the preset status. If the state of the mobile terminal meets the preset state, a protocol acquisition request is sent to the server; Alternatively, the mobile terminal may send a protocol acquisition request containing the status information to the server based on the status information. The server determines whether the state of the mobile terminal meets the preset state based on the state information.

4. The method as described in claim 2, wherein the server sends the communication protocol information to the mobile terminal according to the status information, specifically including: The server determines whether the state of the mobile terminal meets the preset state based on the state information. If the state of the mobile terminal meets the preset state, then the communication protocol information is sent to the mobile terminal.

5. The method as described in any one of claims 3 or 4, wherein the preset state is the state in which the server provides the communication protocol information; The step of determining whether the state of the mobile terminal meets a preset state includes at least one of the following: Determine whether the current time of the mobile terminal has reached the periodic time for acquiring communication protocol information; Determine whether the server contains communication protocol information that is not present in the mobile terminal; Determine whether the mobile terminal displays a card binding page; Determine whether the mobile terminal has launched the target application; The target application is one that provides card binding services; Determine whether the mobile terminal has successfully parsed the near-field communication response information provided by the card to be bound using existing communication protocol information; Determine whether the mobile terminal is connected to the second network from the first network; the network parameters of the second network are better than those of the first network; the network parameters include at least one of signal strength, data transmission speed, and latency. Determine whether the existing communication protocol information in the mobile terminal has become invalid; Determine 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.

6. The method as described in claim 1, further comprising, after saving the communication protocol information: The mobile terminal acquires the first operation performed by the user to obtain card information via near-field communication; Based on the first operation, instruction information is sent via near-field communication. Obtain the response information fed back by the target card in response to the instruction information; The response information is parsed by selecting the first communication protocol information from the various communication protocol information already stored in the mobile terminal to obtain the card information of the target card; The card information will be displayed on the card binding page.

7. The method of claim 6, further comprising: The mobile terminal sends an electromagnetic signal to trigger near-field communication; Based on the electromagnetic signal, it is determined whether there is a card with near-field communication function near the mobile terminal; The sending of command information via the near-field communication method specifically includes: If a card with near-field communication (NFC) capability is present near the mobile terminal, instruction information is sent via NFC.

8. The method as described in claim 7, wherein determining whether a card with near-field communication functionality exists near the mobile terminal based on the electromagnetic signal specifically includes: Determine 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. If the signal strength decreases by more than or equal to the preset threshold within a preset time period, it indicates that there is a card with near-field communication function near the mobile terminal. If the decrease in signal strength within a preset time period is less than the preset threshold, it indicates that there are no cards with near-field communication functionality near the mobile terminal.

9. The method as described in claim 6, wherein parsing the response information by selecting first communication protocol information from various communication protocol information stored in the mobile terminal to obtain the card information of the target card specifically includes: The response information is parsed and processed using the first communication protocol information; If the response information can be successfully parsed, the card information of the target card can be obtained; If the response information cannot be successfully parsed, then a second communication protocol information is selected 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.

10. The method of claim 6, wherein selecting the first communication protocol information from the various communication protocol information already stored in the mobile terminal specifically includes at least one of the following methods: Randomly select the first communication protocol information from the various communication protocol information; Select the first communication protocol information commonly used by the mobile terminal from the various communication protocol information; Select the first communication protocol information most recently used by the mobile terminal in the SIM card binding service from the various communication protocol information; Select the first communication protocol information from the various communication protocol information that corresponds to the nationality or location of the terminal user of the mobile terminal; Select the latest first communication protocol information from the various communication protocol information and save it to the mobile terminal.

11. The method of claim 1, further comprising: The mobile terminal selects a first existing communication protocol from the various existing communication protocol information already present in the mobile terminal; In accordance with the protocol rules of the first existing communication protocol information, instruction information is sent to the card via near-field communication.

12. The method as described in claim 1, further comprising, before obtaining the status information of the mobile terminal: The mobile terminal obtains response information provided by a card with near-field communication functionality in response to the mobile terminal via near-field communication. The response information is parsed and processed using at least one existing communication protocol information already present in the mobile terminal; The acquisition of the mobile terminal's status information specifically includes: Obtain result information indicating that the mobile terminal failed to successfully parse the response information using at least one existing communication protocol.

13. The method as described in claim 1, wherein 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; or, the communication protocol information fed back by the server is all the communication protocol information that the server possesses.

14. The method as described in claim 1, wherein the target type card is a target card that supports near-field communication (NFC) function, and the communication protocol information is the communication protocol information used by the mobile terminal to obtain card information from the target card through NFC. Alternatively, the target type of card is a target card that supports Bluetooth communication, and the communication protocol information is the communication protocol information used by the mobile terminal to obtain card information from the target card via Bluetooth communication.

15. A method for binding a card, comprising: The mobile terminal obtains the card binding trigger operation performed by the user; Based on the card binding trigger operation, obtain the response information from the target card; The response information is parsed using the first communication protocol information already stored in the mobile terminal to obtain the card information of the target card contained in the response information; the various communication protocol information already stored in the mobile terminal includes the communication protocol information obtained according to the method of claim 1. The card information will be displayed on the card binding page.

16. The method of claim 15, further comprising: Based on the card binding trigger operation, a card binding prompt page is displayed; The card binding prompt page includes prompts for users to bind their cards using near-field communication. Obtain the first confirmation operation performed by the user based on the card binding prompt page; The acquisition of the response information from the target card specifically includes: Based on the first confirmation operation, the response information fed back by the target card via near-field communication is obtained.

17. The method of claim 15, wherein after the mobile terminal obtains the card binding trigger operation performed by the user, it further includes: During the process of the mobile terminal obtaining the response information from the target card, an identification response page is displayed; The identification response page includes prompts to guide users on the operations they need to perform during the card binding process.

18. The method as described in claim 17, wherein if the mobile terminal obtains the response information from the target card via near-field communication, the identification response page includes a cancellation control for canceling the interaction via near-field communication; The method further includes: If the user's operation on the cancel control is detected, the process of obtaining card information via near-field communication is terminated.

19. The method as described in claim 17, wherein if the mobile terminal obtains the response information from the target card via near-field communication, after the mobile terminal obtains the card binding trigger operation performed by the user, the method further includes: If the mobile terminal does not detect a card with near-field communication function within the first preset time period, the first abort page will be displayed; The first abort page contains a prompt message indicating that the card information was not successfully obtained and / or a first control indicating that the process of obtaining the card information via near-field communication is to be re-executed.

20. The method of claim 19, further comprising: If user interaction with the first control is detected, the process of obtaining card information via near-field communication is restarted.

21. The method of claim 17, further comprising: If the mobile terminal does not detect a card with near-field communication function within the second preset time period, a prompt message indicating that the card information was not successfully obtained will be displayed on the identification response page.

22. The method of claim 15, further comprising: If the mobile terminal fails to parse the card information of the target card from the response information, a second abort page is displayed; The second abort page includes at least one of the following: a prompt message indicating that the card cannot be recognized, a second control indicating that the card information can be obtained by non-near field communication, and a third control indicating that the process of obtaining card information by near field communication is re-executed. Alternatively, if the mobile terminal fails to obtain card information via near-field communication within a third preset time period, a card addition page indicating that card information is provided using non-near-field communication will be displayed.

23. The method of claim 20, further comprising: If the mobile terminal fails to obtain card information via near-field communication based on the user's operation of the first control, a card addition page indicating that card information is provided using a non-near-field communication method is displayed.

24. The method of any one of claims 22 or 23, wherein the non-near-field communication method includes at least one of manual input or photographic input.

25. The method of claim 15, wherein after displaying the card information to the card binding page, it further includes: Obtain the information submission operation performed by the user based on the card binding page; Based on the information submission operation, the card information is sent to the server; The server can perform a card binding process based on the card information.

26. The method of claim 25, further comprising, after obtaining the information submission operation performed by the user based on the card binding page: Display the card binding authorization page; The card binding authorization page includes the card information; Sending 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.

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

28. The method as described in claim 15, wherein obtaining the response information from the target card based on the card binding trigger operation specifically includes: Based on the card binding trigger operation, instruction information is sent via near-field communication; Obtain the response information fed back by the target card in response to the instruction information.

29. The method of claim 15, further comprising, before parsing the response information using the first communication protocol information already stored in the mobile terminal: Obtain the communication protocol information sent by the server; Save the communication protocol information.

30. The method of claim 29, further comprising, before obtaining the communication protocol information sent by the server: Obtain the status information of the mobile terminal; Based on the status information, a protocol acquisition request is sent to the server.

31. The method as described in claim 15, wherein obtaining the response information from the target card specifically includes: The response information fed back by the target card based on the near-field communication method is obtained through near-field communication. Alternatively, the response information fed back by the target card via Bluetooth communication can be obtained.

32. A method for binding a card, comprising: The mobile terminal obtains the card binding trigger operation performed by the user; Based on the card binding trigger operation, communication protocol information is selected from the various communication protocol information already stored in the mobile terminal to generate instruction information; the various communication protocol information already stored in the mobile terminal includes the communication protocol information obtained according to the method described in claim 1. The instruction information is sent to the target card so that the target card can provide card information containing the target card.

33. An apparatus for acquiring communication protocol information, comprising: The status acquisition module is used to acquire the status information of the mobile terminal; The status information is the status that meets the conditions for the server to provide communication protocol information to the mobile terminal. The determination module 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 by the mobile terminal in the process of obtaining card information for binding the card from the target type of card; The protocol acquisition module is used to acquire the communication protocol information fed back by the server according to the process described above. The protocol storage module is used to store the communication protocol information fed back by the server, so that the mobile terminal can read the card information of the card to be bound using the locally stored communication protocol information.

34. A card-binding device, comprising: The trigger operation acquisition module is used to acquire the card binding trigger operation performed by the user; The response information acquisition module is used to acquire the response information fed back by the target card based on the card binding trigger operation; The parsing module is used to parse the response information using the first communication protocol information already stored in the mobile terminal to obtain the card information of the target card contained in the response information; the various communication protocol information already stored in the mobile terminal includes the communication protocol information obtained according to the method of claim 1. The display module is used to display the card information on the card binding page.

35. 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 executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the method for acquiring communication protocol information as claimed in any one of claims 1 to 14 or the card binding method as claimed in any one of claims 15 to 32.

36. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the method for acquiring communication protocol information as claimed in any one of claims 1 to 14 or the card-binding method as claimed in any one of claims 15 to 32.

Images