Near Field Communication-Based Check-In Processing Method and Device

Abstract

The embodiments of this specification provide a check - in processing method and device based on near - field communication. Among them, a check - in processing method based on near - field communication includes: during the process of a user performing a check - in process based on a near - field communication device, establishing a near - field communication connection with the near - field communication device deployed in the target venue, and obtaining a link containing a preset identifier and a dynamic token from the near - field communication device through the near - field communication connection. Then, starting the target application corresponding to the preset identifier, and passing the link to the target application. Finally, submitting the link and the login user information of the target application to the server through the target application for check - in, so as to implement the user's check - in process based on the near - field communication device.

Description

Technical Field

[0001] This document relates to the field of near-field communication technology, and particularly to a sign-in processing method and device based on near-field communication. Background Art

[0002] With the continuous development of Internet and wireless communication technologies, non-contact communication technology has gradually become one of the main factors to improve user experience. Among them, near-field communication (NFC) technology, as a short-distance high-frequency wireless communication technology, has been widely used in multiple fields such as payment and public transportation. However, with the popularization of smart devices and the increasing demand for convenience from users, the application scenarios based on near-field communication technology are constantly expanding. How to further provide solutions to meet the needs based on near-field communication technology in different environments has become the focus of attention in the industry. Summary of the Invention

[0003] One or more embodiments of this specification provide a sign-in processing method based on near-field communication, including: establishing a near-field communication connection with a near-field communication device deployed in a target venue. Obtaining a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection. Starting a target application corresponding to the preset identifier and passing the link to the target application. Submitting the link and the logged-in user information of the target application to a server through the target application for sign-in processing.

[0004] One or more embodiments of this specification provide another sign-in processing method based on near-field communication, including: obtaining a link containing a preset identifier and a dynamic token from a server. Sending the link to a user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform sign-in processing. Sending a query request to the server and receiving a sign-in result returned by the server after sign-in processing.

[0005] One or more embodiments of this specification provide a sign-in processing device based on near-field communication, including: a connection establishment module configured to establish a near-field communication connection with a near-field communication device deployed in a target venue. A link acquisition module configured to obtain a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection. An application start module configured to start a target application corresponding to the preset identifier and pass the link to the target application. A data submission module configured to submit the link and the logged-in user information of the target application to a server through the target application for sign-in processing.

[0006] One or more embodiments of this specification provide another check-in processing device based on near-field communication, including: a link acquisition module configured to acquire a link containing a preset identifier and a dynamic token from a server. A link sending module configured to send the link to a user terminal that has established a near-field communication connection, so that the user terminal cooperates with the server to perform check-in processing. A result receiving module configured to send a check-in query request to the server and receive a check-in result returned by the server after performing check-in processing.

[0007] One or more embodiments of this specification provide a check-in processing device based on near-field communication, including: a processor; and a memory configured to store computer-executable instructions, where the computer-executable instructions, when executed, cause the processor to: establish a near-field communication connection with a near-field communication device deployed at a target location. Acquire a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection. Start a target application corresponding to the preset identifier and pass the link into the target application. Submit the link and the login user information of the target application to the server through the target application to perform check-in processing.

[0008] One or more embodiments of this specification provide another check-in processing device based on near-field communication, including: a processor; and a memory configured to store computer-executable instructions, where the computer-executable instructions, when executed, cause the processor to: acquire a link containing a preset identifier and a dynamic token from a server. Send the link to a user terminal that has established a near-field communication connection, so that the user terminal cooperates with the server to perform check-in processing. Send a query request to the server and receive a check-in result returned by the server after performing check-in processing.

[0009] One or more embodiments of this specification provide a computer-readable storage medium for storing computer-executable instructions, and the computer-executable instructions, when executed, implement the following process: establish a near-field communication connection with a near-field communication device deployed at a target location. Acquire a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection. Start a target application corresponding to the preset identifier and pass the link into the target application. Submit the link and the login user information of the target application to the server through the target application to perform check-in processing.

[0010] One or more embodiments of this specification provide another computer-readable storage medium for storing computer-executable instructions, which, when executed, implement the following process: Obtain a link containing a preset identifier and a dynamic token from a server. Send the link to a user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform a check-in process. Send a query request to the server and receive a check-in result returned by the server after the check-in process. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0012] Figure 1 Schematic diagram of an implementation environment of a check-in processing method based on near-field communication provided by one or more embodiments of this specification;

[0013] Figure 2 Flowchart of a check-in processing method based on near-field communication provided by one or more embodiments of this specification;

[0014] Figure 3 Flowchart of a check-in processing method based on near-field communication applied to the cashier check-in scenario of merchant members provided by one or more embodiments of this specification;

[0015] Figure 4 Flowchart of a check-in processing method based on near-field communication applied to the check-in scenario of a target venue provided by one or more embodiments of this specification;

[0016] Figure 5 Flowchart of another check-in processing method based on near-field communication provided by one or more embodiments of this specification;

[0017] Figure 6 Schematic diagram of an embodiment of a check-in processing device based on near-field communication provided by one or more embodiments of this specification;

[0018] Figure 7 Schematic diagram of another embodiment of a check-in processing device based on near-field communication provided by one or more embodiments of this specification;

[0019] Figure 8 Schematic diagram of the structure of a check-in processing device based on near-field communication provided by one or more embodiments of this specification;

[0020] Figure 9 Schematic structural diagram of another near-field communication-based check-in processing device provided for one or more embodiments of this specification. Detailed implementation manners

[0021] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will clearly and completely describe the technical solutions in one or more embodiments of this specification with reference to the accompanying drawings in one or more embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this document.

[0022] The near-field communication-based check-in processing method provided for one or more embodiments of this specification is applicable to the implementation environment of check-in processing. Referring to Figure 1 , this implementation environment at least includes: a near-field communication device 101, a user terminal 102, and a server 103;

[0023] Among them, the near-field communication device 101 can be deployed at the target location for check-in processing;

[0024] The user terminal 102 is installed with a target application. After the user terminal 102 establishes a near-field communication connection with the near-field communication device 101, the target application and the server 103 cooperate to perform the check-in processing of the user; the user terminal 102 can specifically be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality), a vehicle-mounted terminal, an IoT device, a wearable intelligent device, a laptop computer, a desktop computer, and so on;

[0025] The server 103 is used to cooperate with the user terminal 102 to perform the check-in processing of the user through the near-field communication device 101.

[0026] In this implementation environment, during the process of a user performing a check-in operation based on near-field communication, the near-field communication device 101 obtains a link containing a preset identifier and a dynamic token from the server 103. After the user terminal 102 establishes a near-field communication connection with the near-field communication device 101 deployed at the target location, the near-field communication device 101 sends the link to the user terminal 102 that has established the near-field communication connection. Correspondingly, the user terminal 102 obtains the link containing the preset identifier and the dynamic token from the near-field communication device 101 through the near-field communication connection, starts the target application corresponding to the preset identifier, passes the link to the target application, and finally the user terminal 102 submits the link and the login user information of the target application to the server 103 for check-in processing, thereby implementing the user's check-in processing based on the near-field communication device. Correspondingly, after the user terminal 102 performs the check-in processing, the near-field communication device 101 sends a check-in query request to the server 103 and receives the check-in result returned after the server 103 performs the check-in processing, thereby implementing the query of the check-in result of the user's check-in processing.

[0027] One or more embodiments of a check-in processing method based on near-field communication provided in this specification are as follows:

[0028] Refer to Figure 2 , the check-in processing method based on near-field communication provided in this embodiment specifically includes steps S202 to S208.

[0029] Step S202: Establish a near-field communication connection with the near-field communication device deployed at the target location.

[0030] The target location in this embodiment refers to the location where the near-field communication device is deployed; specifically, the target location can be a merchant where the near-field communication device is deployed; the target location can also be a conference venue where the near-field communication device is deployed. In addition, the target location can also be other locations, such as an institutional venue or an exhibition venue where the near-field communication device is deployed and participants need to check in, or a scenic spot where the near-field communication device is deployed and tourists need to check in, or a task point where the near-field communication device is deployed and relevant personnel need to check in to participate in a task.

[0031] The near - field communication device refers to a device configured with a near - field communication component. The near - field communication device can communicate with the server in the background. Specifically, the near - field communication device can be a cash register device configured with a near - field communication component, or a check - in device configured with a near - field communication component. In addition, the near - field communication device can also be other devices configured with a near - field communication component, such as a detection device configured with a near - field communication component. Optionally, the near - field communication device includes a cash register device configured with a near - field communication component. Among them, the near - field communication component includes a component configured on the user terminal that can establish a near - field communication connection with other devices.

[0032] In specific implementation, during the process of the user performing a check - in process based on near - field communication, the user establishes a near - field communication connection between the user terminal and the near - field communication device deployed at the target location through the user terminal, thereby providing a basis for the subsequent check - in process.

[0033] Specifically, during the process of establishing a near - field communication connection with the near - field communication device deployed at the target location, the establishment of the near - field communication connection can be initiated actively by the user terminal, that is: the user terminal invokes the near - field communication component to establish the near - field communication connection. The establishment of the near - field communication connection can also be initiated actively by the near - field communication device, that is: the near - field communication device invokes the near - field communication component to establish the near - field communication connection. This embodiment does not make a limitation here.

[0034] Based on the data communication between the near - field communication device and the server in the background, the near - field communication device can further obtain a link. The link can be requested and obtained from the server after the near - field communication connection is established between the near - field communication device and the user terminal, or can be actively sent by the server to the near - field communication device. The following provides two ways for the near - field communication device to obtain the link, and specifically describes the two ways of obtaining respectively.

[0035] Obtaining method 1:

[0036] In order to enable the near - field communication device to realize the timely update of the link, or for scenarios where the link needs to be updated frequently, such as in a target location with high traffic or high frequency of use, in order to enable the near - field communication device to obtain a link containing a preset identifier and a dynamic token regularly, the near - field communication device can obtain the link by using a polling method. In an optional implementation manner provided in this embodiment, the method for obtaining the link includes:

[0037] Send a link acquisition request carrying the device identifier to the server by using a polling method, and receive the link returned by the server.

[0038] The device identifier refers to an identifier used to identify the near - field communication device.

[0039] Specifically, the near-field communication device can be configured to send a link acquisition request to the server at regular preset intervals. Each time it polls, the near-field communication device generates a link acquisition request containing the device identifier and sends the link acquisition request carrying the device identifier to the server. After receiving the link acquisition request, the server generates a new link containing a preset identifier and a dynamic token and returns the link to the near-field communication device. The near-field communication device receives the link for use in the next near-field interaction with the user terminal.

[0040] Acquisition Method 2:

[0041] To improve the response speed so that the near-field communication device can immediately obtain a link after establishing a near-field communication connection with the user terminal, or for target venues with low usage frequency, to initiate a link acquisition request only when actually needed to reduce unnecessary network load, the near-field communication device can also receive the link returned by the server based on the submitted link acquisition request after establishing a near-field communication connection with the user terminal; in an optional implementation provided in this embodiment, the acquisition methods of the link include:

[0042] After establishing a near-field communication connection with the user terminal, send a link acquisition request carrying the device identifier to the server and receive the link returned by the server.

[0043] Specifically, after the near-field communication device establishes a near-field communication connection with the user terminal, it generates a link acquisition request containing the device identifier and sends the link acquisition request to the server. After receiving the link acquisition request, the server generates a new link containing a preset identifier and a dynamic token and returns the link to the near-field communication device. After receiving the link, the near-field communication device can send the link to the user's user terminal for the user to perform subsequent check-in processing.

[0044] In addition, in addition to the two link acquisition methods for the near-field communication device provided above, the near-field communication device can also obtain the link actively sent by the server. Specifically, after the previous check-in processing of the near-field communication device is completed, the server sends the link to the near-field communication device. Correspondingly, the near-field communication device obtains the link sent by the server; optionally, after the previous check-in processing of the near-field communication device is completed, the server sends the link to the near-field communication device.

[0045] For example, if logged-in user A checks in based on the near-field communication device, the check-in request of logged-in user A is processed and relevant information is recorded. After confirming that the check-in processing is completed, the server generates a new link containing a preset identifier and a dynamic token. This link is unique and has nothing to do with the check-in request of logged-in user A. The server sends the new link to the near-field communication device. After receiving the link, the near-field communication device is prepared for the check-in request of the next logged-in user.

[0046] Step S204, obtain a link containing a preset identifier and a dynamic token from the NFC device through the NFC connection.

[0047] In specific implementation, based on establishing an NFC connection with the NFC device deployed at the target location, obtain a link containing a preset identifier and a dynamic token from the NFC device through the NFC connection, so as to parse the obtained link in the subsequent execution process to obtain the corresponding preset identifier and dynamic token; specifically, the NFC device can pre-obtain a link containing a preset identifier and a dynamic token; on the one hand, the dynamic token contained in the link is used to verify the identity of the user performing the check-in process, and on the other hand, it can further improve the security and uniqueness of the check-in process.

[0048] The preset identifier refers to the identification information used for the check-in process. The preset identifier can be an identifier for identifying and / or starting an application, or an address information for identifying and / or starting an application. Specifically, it refers to the identifier and / or address information for identifying and / or starting the target application for the check-in process; the target application can be the application program corresponding to the NFC device, or the service subroutine corresponding to the NFC device within the application program. Optionally, the target application includes the application program and / or the service subroutine; here, the application program can also be a third-party application program, which is not limited in this embodiment.

[0049] The dynamic token can be a unique identifier assigned by the server when generating the link. Specifically, the dynamic token can be generated by an algorithm or by a component; optionally, the link includes a preset identifier and a dynamic token, and the link is obtained by the NFC device from the server.

[0050] For example, the link can be a schema link, and the format of the link is: fixed prefix + dynamic token, where the fixed prefix can be the preset identifier.

[0051] Step S206, start the target application corresponding to the preset identifier and pass the link to the target application.

[0052] After obtaining the link containing the preset identifier and the dynamic token from the NFC device through the NFC connection as described above, in order to correctly identify and start the specified application, parse the link based on the obtained link to obtain the preset identifier contained in the link, then start the target application corresponding to the preset identifier, and pass the link to the target application.

[0053] In specific implementation, in order to perform sign-in processing through a specified application, so as to accurately pass the obtained link to the target application, thereby ensuring the accuracy of subsequent sign-in processing. Based on the link obtained from the near-field communication device, the target application corresponding to the preset identifier included in the link is started, and the link is passed to the target application.

[0054] Specifically, in the process of starting the target application corresponding to the preset identifier, the target application corresponding to the preset identifier can be searched in the user terminal based on the preset identifier. Specifically, the target application corresponding to the preset identifier can be searched in the application list installed in the user terminal, and the target application corresponding to the found preset identifier is started.

[0055] Furthermore, in the process of passing parameters to the target application, specifically, a link containing the preset identifier and the dynamic token can be passed to the target application, or the preset identifier and the dynamic token can be passed to the target application. That is to say, passing the link to the target application can be replaced by passing the preset identifier and the dynamic token to the target application.

[0056] In the specific execution process, after starting the target application corresponding to the preset identifier and passing the link to the target application, in order to provide an application program for sign-in processing that can be applied to different scenarios and / or requirements, and to provide a more lightweight application program for sign-in processing to improve the response speed, it is further possible to enter the service subroutine for sign-in processing in the target application on the basis of starting the target application, and pass parameters to the service subroutine. In an optional implementation manner provided in this embodiment, after passing the link to the target application, it further includes:

[0057] Enter the service subroutine corresponding to the near-field communication device based on the preset identifier, and pass the link to the service subroutine.

[0058] Specifically, on the basis of starting the target application based on the preset identifier, further enter the service subroutine corresponding to the near-field communication device in the target application based on the preset identifier, and pass the link to the service subroutine, so as to perform subsequent sign-in processing.

[0059] In addition, in order to further improve the response speed and processing capacity, and reduce unnecessary resource consumption. For example, in the case of facing high-concurrency requests, submitting the link and the logged-in user information through the target application for each sign-in processing may cause too high a load. Based on this, in another optional implementation manner provided in this embodiment, after passing the link to the target application, it further includes:

[0060] Enter the service subroutine corresponding to the near-field communication device based on the preset identifier, and pass the link to the service subroutine;

[0061] Submit the link and the login user information of the target application to the server through the service subroutine for check-in processing.

[0062] Specifically, on the basis of starting the target application based on the preset identifier, further enter the service subroutine corresponding to the near-field communication device in the target application based on the preset identifier, and pass the link into the service subroutine, so as to submit the link and the login user information of the target application to the server through the service subroutine, thereby performing subsequent check-in processing. Optionally, the link and the login user information are submitted to the server through the service subroutine.

[0063] It should be noted that in addition to starting the target application corresponding to the preset identifier and passing the link into the target application as described above, it is also possible to enter the service subroutine in the target application corresponding to the preset identifier and pass the link into the service subroutine. That is, starting the target application corresponding to the preset identifier and passing the link into the target application can be replaced by: starting the application program based on the preset identifier and entering the service subroutine corresponding to the near-field communication device in the application program, and passing the link into the service subroutine; correspondingly, subsequently submitting the link and the login user information of the target application to the server through the target application for check-in processing can be replaced by: submitting the link and the login user information of the target application to the server through the service subroutine for check-in processing.

[0064] Step S208, submit the link and the login user information of the target application to the server through the target application for check-in processing.

[0065] In specific implementation, submit the link and the login user information of the target application to the server through the target application for check-in processing. Specifically, after submitting the link and the login user information of the target application to the server through the target application, the server can perform check-in processing based on the link and the login user information and obtain the check-in result, and return the obtained check-in result. Correspondingly, the check-in result returned by the server can be obtained.

[0066] Among them, the server can be the server of the application program, the server of the service subroutine, or the server of a third-party application program; the server can be one server or multiple servers; in the case of multiple servers, the first server can generate a link containing the preset identifier and the dynamic token and send it to the near-field communication device, and receive the link and the login user information submitted by the user terminal, and the first server needs to synchronize information related to check-in processing such as the device identifier, the login user information, and the dynamic token to the second server, and the second server performs check-in processing and generates the corresponding check-in result.

[0067] The above-mentioned check-in process can be a check-in process carried out by a merchant member of a merchant based on a cash register device. In this case, during the check-in process of the merchant member based on the cash register device, a check-in relationship needs to be established between the merchant member and the cash register device.

[0068] In the specific implementation process, in order to improve the effectiveness of the merchant's management of the merchant member's check-in, the merchant member can check in based on the cash register device. In this case, in order to improve the accuracy of the check-in process, a check-in relationship can be established between the merchant member and the cash register device. Optionally, the logged-in user of the target application includes the merchant members of the merchant; the check-in process includes: establishing a check-in relationship between the merchant member and the cash register device.

[0069] Here, the merchant member can be the merchant owner, the cashier of the merchant, and / or the staff of the merchant, or can also be other merchant members who need to perform check-in processing in the merchant; the check-in relationship can be a cash register check-in relationship.

[0070] In an optional implementation manner provided in this embodiment, establishing a check-in relationship between a merchant member and a cash register device includes: establishing a cash register check-in relationship between the merchant member and the cash register device based on the binding record of the merchant member and the cash register device.

[0071] Specifically, relevant information of the merchant member and / or the cash register device can be obtained from the target application, and a cash register check-in relationship between the merchant member and the cash register device can be established based on the binding record of the merchant member and the cash register device. Correspondingly, based on the establishment of the cash register check-in relationship, after the merchant member initiates a check-in process, a corresponding check-in result can be returned to the merchant member to inform the merchant member of successful or failed check-in. At the same time, the check-in result of the merchant member can also be returned to the relevant management personnel of the merchant.

[0072] In the specific implementation process, during the process of establishing a cash register check-in relationship between a merchant member and a cash register device so that the merchant member can perform a check-in process based on the cash register device, in order to improve the enthusiasm of the merchant member to check in based on the target application, corresponding rewards can be issued to the member account of the merchant member who has successfully checked in through the cash register device; in an optional implementation manner provided in this embodiment, it further includes:

[0073] After the cash register check-in relationship is established, the rewards obtained after payment and cash register through the cash register device are issued to the member account of the merchant member.

[0074] The reward refers to the feedback obtained by merchant members after completing preset operations. For example, the reward can be the reward issued to the member account of the merchant member after the merchant member performs a check-in process based on the cash register device; the form of the reward can be virtual resources, such as payment rights for payment within the target application, or exchange rights for exchanging goods within the target application. In addition, the reward can also be other forms of resources, such as funds, which are not limited in this embodiment.

[0075] Specifically, in order to improve the efficiency of the merchant's management of the merchant member's check-in and at the same time enhance the enthusiasm of the merchant member for performing the check-in process based on the cash register device, after the merchant member establishes a check-in relationship with the cash register device and the merchant member conducts payment and cash register through the cash register device, the reward obtained by the merchant member for conducting payment and cash register can be issued to the member account of the merchant member.

[0076] Furthermore, on the basis of establishing the check-in relationship between the merchant member and the cash register device, the merchant member can perform a check-in process and obtain the check-in result of the check-in process. In an optional implementation manner provided in this embodiment, the check-in process is implemented in the following manner:

[0077] Generate a check-in record including the device identifier of the cash register device, the logged-in user information, and the dynamic token, and send the check-in result carrying the check-in record to the cash register device and the user terminal.

[0078] Specifically, after the merchant member submits the link and the logged-in user information of the target application to the server, the server receives the link and the logged-in user information, and parses the device identifier and the dynamic token of the cash register device from the link. Based on this, the server generates a check-in record based on the obtained device identifier of the cash register device, the logged-in user information, and the dynamic token, and sends the check-in result carrying the check-in record to the cash register device and the user terminal of the merchant member.

[0079] In addition, the above process of performing the check-in process can also be the project check-in process of the user based on the near-field communication device at the target location. In this case, during the process of the user performing the project check-in process based on the near-field communication device, the check-in method for performing the check-in process can be determined first, and the check-in process can be performed based on the determined check-in method.

[0080] In the specific execution process, during the process of performing the check-in process, on the one hand, by providing the check-in method that meets the user's needs for the user, the operation process of the user is simplified, and the user satisfaction is improved. On the other hand, by providing a suitable check-in method according to the different device types, location types, and / or user types of the near-field communication device, the adaptability and flexibility of the process of the user performing the check-in process are enhanced. In an optional implementation manner provided in this embodiment, performing the check-in process includes:

[0081] Determine the check-in method according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, and perform check-in processing according to the check-in method.

[0082] For example, according to the device type of the near-field communication device, such as an NFC device, a QR code scanning device, or other near-field communication devices, determine the check-in method suitable for the near-field communication device to perform check-in processing according to the check-in method; or, according to the venue type of the target venue, such as a meeting, an exhibition, a scenic spot, or other venues that require check-in, determine the check-in method suitable for the target venue to perform check-in processing according to the check-in method; or, according to the user type of the logged-in user, such as a participant in a meeting and / or an exhibition, a tourist at a scenic spot, or other logged-in users who need to perform check-in, determine the check-in method suitable for the logged-in user to perform check-in processing according to the check-in method.

[0083] It should be noted that during the process of determining the check-in method, the check-in method can be determined based on any one or more of the device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user according to the actual processing needs; for example, determine the check-in method according to the device type of the near-field communication device, the venue type of the target venue, or the user type of the logged-in user; for another example, determine the check-in method according to the device type of the near-field communication device and the venue type of the target venue, or determine the check-in method according to the venue type of the target venue and the user type of the logged-in user; for another example, determine the check-in method according to the device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user. This embodiment does not make any limitations here.

[0084] In addition, during the above process of determining the check-in method, it can also be combined with other implementation methods to form a new process for determining the check-in method, or any one or more of the above-mentioned device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user can be combined with other implementation methods to form a new process for determining the check-in method; for example, determine the check-in method according to the venue type of the target venue and the location area type of the logged-in user. This embodiment does not make any limitations here.

[0085] Optionally, the check-in method includes at least one of the following: performing user check-in processing for the logged-in user on the near-field communication device, performing location check-in processing or venue check-in processing for the logged-in user at the target venue, and performing item check-in processing for the target venue or the items corresponding to the near-field communication device for the logged-in user.

[0086] In view of this, the process of determining the check-in method and performing the check-in process described above can be replaced with: determining the check-in method as performing the user check-in process of the logged-in user for the near-field communication device, performing the location check-in process or the venue check-in process of the logged-in user at the target venue, and / or performing the item check-in process for the target venue or the item corresponding to the near-field communication device for the logged-in user, according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, and performing the check-in process according to the check-in method.

[0087] It should be noted that during the check-in process, any one or any two or all of the above check-in methods can be selected according to the actual processing needs as the check-in method for performing the check-in process; or, any one or any two or all of the above check-in methods can also be combined with other implementation methods according to the actual processing needs to form a new check-in method, which is not limited in this embodiment.

[0088] Furthermore, on the basis of determining the check-in method according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, the user can perform the check-in process according to the check-in method and obtain the check-in result of the check-in process. In an optional implementation manner provided in this embodiment, the check-in process is implemented as follows:

[0089] Generate a check-in record including the device identifier of the near-field communication device, the logged-in user information, and the dynamic token, and send the check-in result carrying the check-in record to the near-field communication device and the user terminal.

[0090] Specifically, after the user submits the link and the logged-in user information of the target application to the server through the target application, the server receives the link and the logged-in user information, and parses and obtains the device identifier and the dynamic token of the near-field communication device from the link. Based on this, the server generates a check-in record based on the obtained device identifier of the near-field communication device, the logged-in user information, and the dynamic token, and sends the check-in result carrying the check-in record to the near-field communication device and the user terminal.

[0091] As described above, in order to provide an application program for performing the check-in process that can be applied to different scenarios and / or requirements, it is further possible to enter the service subroutine corresponding to the near-field communication device in the target application based on a preset identifier on the basis of starting the target application, and pass the link to the service subroutine. That is, it is also possible to submit the link and the logged-in user information of the target application to the server through the service subroutine to perform the check-in process; based on this, submitting the link and the logged-in user information of the target application to the server through the target application can be replaced with: submitting the link and the logged-in user information of the target application to the server through the service subroutine.

[0092] In summary, in the check-in processing method based on near field communication provided in this embodiment, during the process of a user performing check-in processing based on near field communication, first, a near field communication connection with a near field communication device deployed at a target venue is established to provide a basis for subsequent check-in processing. Second, in order to improve the security and uniqueness of the check-in processing process, a link containing a preset identifier and a dynamic token is further obtained from the near field communication device through the near field communication connection, so as to parse the obtained link during subsequent execution to obtain the corresponding preset identifier and dynamic token. Then, in order to implement check-in processing through a specified application, based on the link obtained from the near field communication device, the target application corresponding to the preset identifier included in the link is started, and the link is passed to the target application to ensure the accuracy of subsequent check-in processing. Finally, based on starting the target application and passing the link to the target application, the link and the login user information of the target application are submitted to the server through the target application for check-in processing, thereby realizing the user's check-in processing based on the near field communication device.

[0093] It should be noted that considering that relevant data such as the login user information of the users involved in this specification may, to a certain extent, belong to the privacy of the users, therefore, if you want to collect or transmit relevant data such as login user information, you can obtain the authorization of the user before collecting or transmitting the data, so that the operation of collecting or transmitting the data complies with relevant data management regulations. For example, the user can perform data authorization when starting the target application; the specific method of data authorization can be to send a data authorization reminder to the user, and the user can obtain data authorization after confirming the reminder through an instruction. Or, the method of data authorization can also be to obtain data collection or data transmission authorization by signing a data authorization agreement. This embodiment does not make any limitations here.

[0094] The following takes the application of the check-in processing method based on near field communication provided in this embodiment in the cashier check-in scenario of merchant members as an example, and combines Figure 3 , to further illustrate the check-in processing method based on near field communication provided in this embodiment. See Figure 3 , the check-in processing method based on near field communication applied to the cashier check-in scenario of merchant members specifically includes the following steps.

[0095] Step S302, establish a near field communication connection with the cashier device deployed by the merchant.

[0096] Step S310, obtain a link containing a preset identifier and a dynamic token sent by the cashier device.

[0097] Step S312, start the target application corresponding to the preset identifier.

[0098] Step S314, pass the link to the target application.

[0099] Step S316: Submit the link and the login user information of the target application to the server through the target application.

[0100] Step S318: Based on the binding record between the merchant member and the cash register device, establish the cash register signing-in relationship between the merchant member and the cash register device.

[0101] In the above-mentioned step S302, steps S310 to S318 provided in this embodiment are executed by the user terminal. It should be noted that the above-mentioned step S302, steps S310 to S318 executed by the user terminal and the steps S304 to S308, steps S320 to S322 executed by the near-field communication device in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding content of steps S304 to S308, steps S320 to S322 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of step S302, steps S310 to S318 provided in this embodiment.

[0102] It should be noted that any one step or any combination of steps S302, steps S310 to S318 can be combined with any one step or any combination of the above steps S202 to S208 to form a new implementation manner according to the needs of implementation deployment; in addition, according to the actual deployment needs, any one or any combination of technical features in steps S302, steps S310 to S318 can be selected and combined with any one or more technical features provided in the above steps S202 to S208 to form a new implementation manner; or, any one or any combination of technical features in steps S302, steps S310 to S318 can also be replaced with any one or more technical features provided in the above steps S202 to S208 according to the actual deployment needs to form a new implementation manner, which will not be elaborated here one by one.

[0103] The following takes the application of a near-field communication-based signing-in processing method provided in this embodiment in the signing-in scenario of a target venue as an example to further illustrate the near-field communication-based signing-in processing method provided in this embodiment. See Figure 4 The near-field communication-based signing-in processing method applied to the signing-in scenario of a target venue specifically includes the following steps.

[0104] Step S402: Establish a near-field communication connection with the near-field communication device deployed in the target venue.

[0105] Step S410: Obtain a link containing a preset identifier and a dynamic token sent by the near-field communication device.

[0106] Step S412: Start the target application corresponding to the preset identifier.

[0107] Step S414, pass the link to the target application.

[0108] Step S416, submit the link and the login user information of the target application to the server through the target application.

[0109] Step S418, perform project check-in processing for the item corresponding to the near-field communication device for the user.

[0110] The above steps S402, steps S410 to S418 provided in this embodiment are executed by the user terminal. It should be noted that the above steps S402, steps S410 to S418 executed by the user terminal and the steps S404 to S408, steps S420 to S422 executed by the near-field communication device in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding content of steps S404 to S408, steps S420 to S422 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of steps S402, steps S410 to S418 provided in this embodiment.

[0111] It should be noted that any one step or any combination of steps among steps S402, steps S410 to S418 can be combined with any one step or any combination of the above steps S202 to S208 to form a new implementation manner according to the needs of the implementation deployment; in addition, according to the actual deployment needs, any one or any combination of technical features in steps S402, steps S410 to S418 can be combined with any one or more technical features provided by the above steps S202 to S208 to form a new implementation manner; or, any one or any combination of technical features in steps S402, steps S410 to S418 can also be replaced by any one or more technical feature combinations provided by the above steps S202 to S208 according to the actual deployment needs to form a new implementation manner, which will not be elaborated here one by one.

[0112] One or more embodiments of another near-field communication-based check-in processing method provided in this specification are as follows:

[0113] Refer to Figure 5 This embodiment provides a near-field communication-based check-in processing method, which is applied to a near-field communication device, and the method specifically includes steps S502 to S506.

[0114] Step S502, obtain a link containing a preset identifier and a dynamic token from the server.

[0115] The near-field communication device described in this embodiment refers to a device configured with a near-field communication component, which can communicate with a server in the background. Specifically, the near-field communication device can be a cash register device configured with a near-field communication component, or a check-in device configured with a near-field communication component. In addition, the near-field communication device can also be other devices configured with a near-field communication component, such as a detection device configured with a near-field communication component. Optionally, the near-field communication device includes a cash register device of a merchant configured with a near-field communication component, and the near-field communication device is deployed in a target location. Among them, the near-field communication component includes a component configured on the user terminal that can establish a near-field communication connection with other devices.

[0116] Among them, the target location refers to the location where the near-field communication device is deployed. Specifically, the target location can be a merchant where the near-field communication device is deployed, or a conference venue where the near-field communication device is deployed. In addition, the target location can also be other locations, such as an institutional venue or exhibition venue where the near-field communication device is deployed and participants need to check in, or a scenic spot where the near-field communication device is deployed and tourists need to check in, or a task point where the near-field communication device is deployed and relevant personnel need to check in to participate in a task.

[0117] In specific implementation, to improve the security and uniqueness of the check-in process, a link containing a preset identifier and a dynamic token is obtained from the server. Specifically, after establishing a near-field communication connection between the user terminal and the near-field communication device deployed in the target location, a link containing a preset identifier and a dynamic token can be obtained from the server, or before establishing a near-field communication connection between the user terminal and the near-field communication device deployed in the target location, a link containing a preset identifier and a dynamic token can be obtained from the server. This embodiment does not limit this.

[0118] Specifically, during the process of establishing a near-field communication connection between the user terminal and the near-field communication device deployed in the target location, the establishment of the near-field communication connection can be initiated by the user terminal, that is, the user terminal calls the near-field communication component to establish the near-field communication connection. The establishment of the near-field communication connection can also be initiated by the near-field communication device, that is, the near-field communication device calls the near-field communication component to establish the near-field communication connection. This embodiment does not limit this.

[0119] The preset identifier refers to the identifier information used for check-in processing. The preset identifier can be an identifier for identifying and / or starting an application, or it can be an address information for identifying and / or starting an application. Specifically, it refers to the identifier and / or address information for identifying and / or starting the target application for check-in processing. The target application can be an application program corresponding to a near-field communication device, or a service subroutine corresponding to the near-field communication device within the application program. Optionally, the target application includes an application program and / or a service subroutine. Here, the application program can also be a third-party application program, which is not limited in this embodiment.

[0120] The dynamic token can be a unique identifier assigned by the server when generating the link. Specifically, the dynamic token can be generated by an algorithm or by a component. Optionally, the link includes a preset identifier and a dynamic token, and the link is obtained by the near-field communication device from the server.

[0121] For example, the link can be a schema link, and the format of the link is: fixed prefix + dynamic token (token), where the fixed prefix can be the preset identifier.

[0122] The following provides three ways to obtain the link, and specifically describes the three ways to obtain the link.

[0123] Obtaining method 1:

[0124] In order to be able to update the link in a timely manner, or for scenarios where the link needs to be updated frequently, such as in a target place with high traffic or high frequency of use, in order to be able to obtain the link containing the preset identifier and the dynamic token regularly, the polling method can be used to obtain the link. In an optional implementation provided in this embodiment, obtaining the link containing the preset identifier and the dynamic token from the server includes:

[0125] Sending a link acquisition request carrying the device identifier to the server in a polling manner and receiving the link returned by the server.

[0126] The device identifier refers to the identifier used to identify the near-field communication device.

[0127] Specifically, a link acquisition request can be sent to the server every certain preset time. Each time of polling, a link acquisition request containing the device identifier is generated and the link acquisition request carrying the device identifier is sent to the server. After receiving the link acquisition request, the server generates a new link containing the preset identifier and the dynamic token and returns it. Based on this, the link containing the preset identifier and the dynamic token can be obtained from the server.

[0128] Obtaining method 2:

[0129] To improve the response speed to immediately obtain a link after establishing a near-field communication connection with a user terminal, or for a target venue with a low usage frequency, to initiate a link acquisition request only when actually needed to reduce unnecessary network load, a link returned by the server can also be received based on the submitted link acquisition request after establishing a near-field communication connection with the user terminal; in an alternative implementation provided in this embodiment, obtaining a link including a preset identifier and a dynamic token from the server includes:

[0130] After establishing a near-field communication connection with the user terminal, send a link acquisition request carrying the device identifier to the server and receive the link returned by the server.

[0131] Specifically, after establishing a near-field communication connection with the user terminal, generate a link acquisition request including the device identifier and send the link acquisition request to the server. After the server receives the link acquisition request, it generates a new link including a preset identifier and a dynamic token and returns it. Based on this, a link including a preset identifier and a dynamic token can be obtained from the server.

[0132] Acquisition method three:

[0133] In addition to the above-mentioned method of requesting to obtain a link from the server after establishing a near-field communication connection with the user terminal, a link actively sent by the server can also be obtained. For example, in the scenario of high-frequency check-in, the server can send a link after the previous check-in processing is completed. Correspondingly, the link sent by the server can be received; in an alternative implementation provided in this embodiment, obtaining a link including a preset identifier and a dynamic token from the server includes:

[0134] Receive the link sent by the server after the previous check-in processing of the near-field access device is completed.

[0135] For example, when the logged-in user A completes the check-in, the check-in request of the logged-in user A is processed and relevant information is recorded. After confirming that the check-in processing is completed, the server generates a new link including a preset identifier and a dynamic token. This link is unique and has nothing to do with the check-in request of the logged-in user A. The server sends the new link to the near-field communication device. After receiving the link, the near-field communication device prepares for the check-in request of the next logged-in user.

[0136] Step S504, send the link to the user terminal that has established a near-field communication connection, so that the user terminal cooperates with the server for check-in processing.

[0137] In specific implementation, based on obtaining a link including a preset identifier and a dynamic token from the server, further send the link to the user terminal that has established a near-field communication connection, so that the user terminal cooperates with the server for check-in processing; correspondingly, the user terminal receives the link including a preset identifier and a dynamic token.

[0138] Specifically, during the process of the user terminal cooperating with the server for check-in processing, the user terminal first receives a link containing a preset identifier and a dynamic token. After receiving the link, it parses the obtained link to obtain the corresponding preset identifier and dynamic token, then starts the target application corresponding to the preset identifier, passes the link to the target application, and finally submits the link and the login user information of the target application to the server for check-in processing.

[0139] Among them, the server can be the server of an application program, the server of a service subroutine, or the server of a third-party application program; the server can be a single server or multiple servers; in the case of multiple servers, the first server can generate a link containing a preset identifier and a dynamic token and send it to the near-field communication device, and receive the link and login user information submitted by the user terminal. Moreover, the first server needs to synchronize information related to check-in processing, such as device identifiers, login user information, and dynamic tokens, to the second server, and the second server performs check-in processing and generates corresponding check-in results.

[0140] The above process of the user terminal cooperating with the server for check-in processing can be the check-in processing by merchant members of a merchant based on a cash register device. In this case, during the process of the merchant members performing check-in processing based on the cash register device, a check-in relationship needs to be established between the merchant members and the cash register device.

[0141] In the specific implementation process, to improve the effectiveness of the merchant's management of merchant members' check-ins, the merchant members can perform check-ins based on the cash register device. In this case, to improve the accuracy of check-in processing, a check-in relationship can be established between the merchant members and the cash register device. Optionally, the login users of the target application include the merchant members of the merchant; the check-in processing includes: establishing a check-in relationship between the merchant members and the cash register device.

[0142] Here, the merchant members can be the merchant owner, the cashier of the merchant, and / or the staff of the merchant, or other merchant members who need to perform check-in processing in the merchant; the check-in relationship can be a cash register check-in relationship.

[0143] In an optional implementation manner provided in this embodiment, establishing a check-in relationship between the merchant members and the cash register device includes: establishing a cash register check-in relationship between the merchant members and the cash register device based on the binding record between the merchant members and the cash register device.

[0144] Specifically, relevant information of merchant members and / or cashier devices can be obtained from the target application, and based on the binding records between merchant members and cashier devices, a cashier sign-in relationship between merchant members and cashier devices can be established. Correspondingly, based on the establishment of the cashier sign-in relationship, after a merchant member initiates a sign-in process, a corresponding sign-in result can be returned to the merchant member to inform the merchant member of successful or failed sign-in. At the same time, the sign-in result of the merchant member can also be returned to the relevant management personnel of the merchant.

[0145] During the specific implementation process, in the process of establishing the cashier sign-in relationship between merchant members and cashier devices to enable merchant members to perform sign-in processing based on cashier devices, in order to improve the enthusiasm of merchant members to sign in based on the target application, corresponding rewards can be distributed to the member accounts of merchant members who have successfully signed in through the cashier device; in an optional implementation manner provided in this embodiment, it further includes:

[0146] After the cashier sign-in relationship is established, the rewards obtained after payment and cashiering through the cashier device are distributed to the member accounts of merchant members.

[0147] The rewards refer to the feedback obtained by merchant members after completing preset operations. For example, the rewards can be the rewards distributed to the member accounts of merchant members after they perform sign-in processing based on the cashier device; the form of the rewards can be virtual resources, such as payment rights for payment within the target application, or exchange rights for exchanging goods within the target application. In addition, the rewards can also be other forms of resources, such as funds, which are not limited in this embodiment.

[0148] Specifically, in order to improve the efficiency of merchants in managing the sign-in of merchant members and at the same time improve the enthusiasm of merchant members to perform sign-in processing based on cashier devices, after a merchant member establishes a sign-in relationship with a cashier device and the merchant member performs payment and cashiering through the cashier device, the rewards obtained by the merchant member for payment and cashiering can be distributed to the member account of the merchant member.

[0149] Furthermore, on the basis of establishing the sign-in relationship between merchant members and cashier devices, merchant members can perform sign-in processing and obtain the sign-in result of the sign-in processing. In an optional implementation manner provided in this embodiment, the sign-in processing is implemented in the following way:

[0150] Generate a sign-in record including the device identifier of the cashier device, login user information, and dynamic token, and send the sign-in result carrying the sign-in record to the cashier device and the user terminal.

[0151] Specifically, after a merchant member submits a link and the login user information of the target application to the server through the target application, the server receives the link and the login user information, and parses the device identifier and the dynamic token of the cash register device from the link. Based on this, a corresponding check-in record is generated based on the obtained device identifier of the cash register device, the login user information, and the dynamic token, and a check-in result carrying the check-in record is sent to the cash register device and the user terminal of the merchant member.

[0152] In addition, the process of the above user terminal cooperating with the server for check-in processing can also be the project check-in processing based on the near-field communication device. In this case, during the process of the user performing project check-in processing based on the near-field communication device, the check-in method for performing the check-in processing can be determined first, and the check-in processing is performed based on the determined check-in method.

[0153] In the specific implementation process, during the check-in processing, on the one hand, by providing the check-in method that meets the user's needs for the user, the operation process of the user is simplified, and the user satisfaction is improved. On the other hand, by providing a suitable check-in method according to the device type, the venue type, and / or the user type of the near-field communication device, the adaptability and flexibility of the process of the user performing the check-in processing are enhanced. In an optional implementation manner provided in this embodiment, performing the check-in processing includes:

[0154] Determine the check-in method according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, and perform the check-in processing according to the check-in method.

[0155] For example, the check-in method suitable for the near-field communication device can be determined according to the device type of the near-field communication device, such as an NFC device, a QR code scanning device, or other near-field communication devices, so as to perform the check-in processing according to the check-in method; or, the check-in method suitable for the target venue can be determined according to the venue type of the target venue, such as a meeting, an exhibition, a scenic spot, or other venues that require check-in, so as to perform the check-in processing according to the check-in method; or, the check-in method suitable for the logged-in user can also be determined according to the user type of the logged-in user, such as a participant in a meeting and / or an exhibition, a tourist at a scenic spot, or other logged-in users who need to perform check-in, so as to perform the check-in processing according to the check-in method.

[0156] It should be noted that in the process of determining the check-in method, the check-in method can be determined based on any one or more of the device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user according to the actual processing needs; for example, the check-in method is determined according to the device type of the near-field communication device, the venue type of the target venue, or the user type of the logged-in user; for another example, the check-in method is determined according to the device type of the near-field communication device and the venue type of the target venue, or according to the venue type of the target venue and the user type of the logged-in user; for another example, the check-in method is determined according to the device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user. This embodiment does not make any limitations here.

[0157] In addition, in the process of determining the check-in method as described above, it can also be combined with other implementation methods to form a new process for determining the check-in method, or any one or more of the device type of the near-field communication device, the venue type of the target venue, and the user type of the logged-in user as described above can be combined with other implementation methods to form a new process for determining the check-in method; for example, the check-in method is determined according to the venue type of the target venue and the location area type of the logged-in user. This embodiment does not make any limitations here.

[0158] Optionally, the check-in method includes at least one of the following: performing user check-in processing for the logged-in user on the near-field communication device, performing location check-in processing or venue check-in processing for the logged-in user at the target venue, and performing item check-in processing for the target venue or the item corresponding to the near-field communication device for the logged-in user.

[0159] In this regard, the process of determining the check-in method and performing the check-in processing can be replaced by: determining, according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, that the check-in method is to perform user check-in processing for the logged-in user on the near-field communication device, perform location check-in processing or venue check-in processing for the logged-in user at the target venue, and / or perform item check-in processing for the target venue or the item corresponding to the near-field communication device for the logged-in user, and performing the check-in processing according to the check-in method.

[0160] It should be noted that in the process of performing the check-in processing, any one or any two or all of the above check-in methods can be selected according to the actual processing needs as the check-in method for performing the check-in processing; or, according to the actual processing needs, any one or any two or all of the above check-in methods can be combined with other implementation methods to form a new check-in method. This embodiment does not make any limitations here.

[0161] Further, based on determining the check-in method according to the device type of the near-field communication device, the venue type of the target venue, and / or the user type of the logged-in user, the check-in process is performed according to the check-in method. In an alternative implementation provided in this embodiment, the check-in process is implemented as follows:

[0162] Generate a check-in record including the device identifier of the near-field communication device, the logged-in user information, and the dynamic token, and send the check-in result carrying the check-in record to the near-field communication device and the user terminal.

[0163] Specifically, after submitting the link and the logged-in user information of the target application to the server through the target application, the server receives the link and the logged-in user information, and parses the device identifier and the dynamic token of the near-field communication device from the link. Based on this, a corresponding check-in record is generated based on the obtained device identifier of the near-field communication device, the logged-in user information, and the dynamic token, and the check-in result carrying the check-in record is sent to the near-field communication device and the user terminal.

[0164] Step S506, send a check-in query request to the server, and receive the check-in result returned by the server after the check-in process.

[0165] In practical applications, after the user completes the check-in process based on near-field communication at the target venue through the user terminal, correspondingly, the check-in result after the check-in process can be returned to inform the user whether the check-in is successful or failed.

[0166] Specifically, in order to obtain the check-in result of the user's check-in process based on near-field communication, after the above user performs the check-in process based on the user terminal, a check-in query request is sent to the server, and correspondingly, the check-in result returned by the server after the check-in process is received; specifically, the check-in query request may include the logged-in user information of the user, the device identifier, the preset identifier, and / or the dynamic token; the check-in result may include the check-in status (check-in successful or failed), the check-in time, and / or the check-in location. In addition, it may also include other information related to the check-in process, which is not limited in this embodiment.

[0167] In summary, in the sign-in processing method based on near-field communication provided in this embodiment, during the process of the user performing sign-in processing based on near-field communication, in order to improve the security and uniqueness of the sign-in processing process, first obtain a link containing a preset identifier and a dynamic token from the server. On the basis of obtaining the link containing the preset identifier and the dynamic token from the server, further send the link to the user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform sign-in processing. After that, in order to obtain the sign-in result of the user performing sign-in processing based on near-field communication, further send a sign-in query request to the server after the user performs sign-in processing based on the user terminal, and receive the sign-in result returned by the server after performing sign-in processing, so as to implement the sign-in of the user based on the near-field communication device and the query and reception of the sign-in result.

[0168] The following takes the application of the sign-in processing method based on near-field communication provided in this embodiment in the cashier sign-in scenario of merchant members as an example, and combines Figure 3 to further illustrate the sign-in processing method based on near-field communication provided in this embodiment. See Figure 3 The sign-in processing method based on near-field communication applied to the cashier sign-in scenario of merchant members specifically includes the following steps.

[0169] Step S304, send a link acquisition request carrying the device identifier of the cashier device to the server in a polling manner.

[0170] Step S306, obtain a link containing a preset identifier and a dynamic token from the server.

[0171] Step S308, send the link to the user terminal that has established a near-field communication connection.

[0172] Step S320, send a sign-in query request to the server.

[0173] After that, the server performs sign-in processing and obtains a sign-in result, and sends the sign-in result to the cashier device.

[0174] Step S322, obtain the sign-in result returned by the server after performing sign-in processing.

[0175] It should be noted that any one or any combination of steps from step S304 to step S308 and steps from step S320 to step S322 can be combined with any one or any combination of the above steps S502 to S506 according to the needs of implementation and deployment to form a new implementation method; in addition, according to the actual deployment needs, any one or any combination of technical features can be selected from steps S304 to S308 and steps S320 to S322, and combined with any one or more technical features provided by the above steps S502 to S506 to form a new implementation method; or, any one or any combination of technical features in steps S304 to S308 and steps S320 to S322 can also be replaced by any one or more combinations of technical features provided by the above steps S502 to S506 according to the actual deployment needs to form a new implementation method, which will not be elaborated here one by one.

[0176] The following takes the application of a check-in processing method based on near field communication provided in this embodiment in the check-in scenario of a target venue as an example to further illustrate the check-in processing method based on near field communication provided in this embodiment. Refer to Figure 4 , the check-in processing method based on near field communication applied to the check-in scenario of a target venue specifically includes the following steps.

[0177] Step S404, send a link acquisition request carrying the device identifier of the near field communication device to the server.

[0178] Step S406, obtain a link containing a preset identifier and a dynamic token from the server.

[0179] Step S408, send the link to the user terminal that has established a near field communication connection.

[0180] Step S420, send a check-in query request to the server.

[0181] After that, the server obtains the check-in result and sends the check-in result to the cash register device.

[0182] Step S422, obtain the check-in result returned by the server after check-in processing.

[0183] It should be noted that any one or any combination of steps S404 to S408 and steps S420 to S422 can be combined with any one or any combination of the above steps S502 to S506 to form a new implementation according to the needs of implementation and deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S404 to S408 and steps S420 to S422 can be selected and combined with any one or more technical features provided in the above steps S502 to S506 to form a new implementation; or, any one or any combination of technical features in steps S404 to S408 and steps S420 to S422 can also be replaced by any one or more technical feature combinations provided in the above steps S502 to S506 according to the needs of actual deployment to form a new implementation, which will not be elaborated here one by one.

[0184] An embodiment of a check-in processing device based on near field communication provided in this specification is as follows:

[0185] In the above embodiment, a check-in processing method based on near field communication is provided. Correspondingly, a check-in processing device based on near field communication is also provided, which will be described below with reference to the accompanying drawings.

[0186] Refer to Figure 6 , which shows a schematic diagram of an embodiment of a check-in processing device based on near field communication provided in this embodiment.

[0187] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiments described below are only illustrative.

[0188] This embodiment provides a check-in processing device based on near field communication. The device includes:

[0189] A connection establishment module 602, configured to establish a near field communication connection with a near field communication device deployed at a target location;

[0190] A link acquisition module 604, configured to acquire a link containing a preset identifier and a dynamic token from the near field communication device through the near field communication connection;

[0191] An application startup module 606, configured to start a target application corresponding to the preset identifier and pass the link to the target application;

[0192] A data submission module 608, configured to submit the link and the login user information of the target application to a server through the target application for check-in processing.

[0193] Another embodiment of the check-in processing device based on near-field communication provided in this specification is as follows:

[0194] In the above embodiment, another check-in processing method based on near-field communication is provided. Correspondingly, another check-in processing device based on near-field communication is also provided. The following is an explanation with reference to the accompanying drawings.

[0195] Refer to Figure 7 , which shows a schematic diagram of another embodiment of the check-in processing device based on near-field communication provided in this embodiment.

[0196] Since the device embodiment corresponds to the method embodiment, the description is relatively simple. For the relevant parts, please refer to the corresponding description of the method embodiment provided above. The device embodiments described below are merely illustrative.

[0197] This embodiment provides a check-in processing device based on near-field communication. The device includes:

[0198] A link acquisition module 702, configured to acquire a link containing a preset identifier and a dynamic token from a server;

[0199] A link sending module 704, configured to send the link to a user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform check-in processing;

[0200] A result receiving module 706, configured to send a check-in query request to the server and receive a check-in result returned by the server after performing check-in processing.

[0201] Another embodiment of the check-in processing device based on near-field communication provided in this specification is as follows:

[0202] Corresponding to the above-described check-in processing method based on near-field communication, based on the same technical concept, one or more embodiments of this specification also provide a check-in processing device based on near-field communication. This check-in processing device based on near-field communication is used to execute the above-provided check-in processing method based on near-field communication. Figure 8 It is a schematic diagram of the structure of a check-in processing device based on near-field communication provided by one or more embodiments of this specification.

[0203] The check-in processing device based on near-field communication provided in this embodiment includes:

[0204] As Figure 8As shown, the near field communication-based check-in processing device can vary significantly due to configuration or performance differences, and may include one or more processors 801 and a memory 802. One or more application programs or data may be stored in the memory 802. Among them, the memory 802 can be transient storage or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the near field communication-based check-in processing device. Further, the processor 801 can be configured to communicate with the memory 802 and execute a series of computer-executable instructions in the memory 802 on the near field communication-based check-in processing device. The near field communication-based check-in processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0205] In a specific embodiment, the near field communication-based check-in processing device includes a memory and one or more programs. One or more of the programs are stored in the memory, and one or more of the programs may include one or more modules. Each module may include a series of computer-executable instructions in the near field communication-based check-in processing device and is configured to be executed by one or more processors. The one or more programs include the following computer-executable instructions for:

[0206] Establish a near field communication connection with a near field communication device deployed at a target location;

[0207] Obtain a link containing a preset identifier and a dynamic token from the near field communication device through the near field communication connection;

[0208] Start the target application corresponding to the preset identifier and pass the link to the target application;

[0209] Submit the link and the login user information of the target application to the server through the target application for check-in processing.

[0210] Another embodiment of the near field communication-based check-in processing device provided in this specification is as follows:

[0211] Corresponding to the above-described another near field communication-based check-in processing method, based on the same technical concept, one or more embodiments of this specification also provide another near field communication-based check-in processing device. This near field communication-based check-in processing device is used to execute the above-provided another near field communication-based check-in processing method. Figure 9Schematic structural diagram of another near field communication-based check-in processing device provided for one or more embodiments of this specification.

[0212] A near field communication-based check-in processing device provided in this embodiment includes:

[0213] As Figure 9 shown, the near field communication-based check-in processing device may vary greatly due to configuration or performance differences, and may include one or more processors 901 and a memory 902. One or more applications or data may be stored in the memory 902. Among them, the memory 902 may be transient storage or persistent storage. The applications stored in the memory 902 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the near field communication-based check-in processing device. Further, the processor 901 may be configured to communicate with the memory 902 and execute a series of computer-executable instructions in the memory 902 on the near field communication-based check-in processing device. The near field communication-based check-in processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.

[0214] In a specific embodiment, the near field communication-based check-in processing device includes a memory and one or more programs. One or more of the programs are stored in the memory, and one or more of the programs may include one or more modules, and each module may include a series of computer-executable instructions in the near field communication-based check-in processing device, and is configured to be executed by one or more processors. The one or more programs include the following computer-executable instructions:

[0215] Obtain a link containing a preset identifier and a dynamic token from the server;

[0216] Send the link to the user terminal that has established a near field communication connection, so that the user terminal cooperates with the server for check-in processing;

[0217] Send a check-in query request to the server and receive the check-in result returned by the server after check-in processing.

[0218] An embodiment of a computer-readable storage medium provided in this specification is as follows:

[0219] Corresponding to the above-described near field communication-based check-in processing method, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0220] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented:

[0221] Establish a near-field communication connection with a near-field communication device deployed at a target location;

[0222] Obtain a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection;

[0223] Start a target application corresponding to the preset identifier, and pass the link to the target application;

[0224] Submit the link and the login user information of the target application to a server through the target application for check-in processing.

[0225] It should be noted that the embodiment of a computer-readable storage medium in this specification and the embodiment of a near-field communication-based check-in processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and the repeated parts will not be elaborated.

[0226] Another embodiment of the computer-readable storage medium provided in this specification is as follows:

[0227] Corresponding to another near-field communication-based check-in processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0228] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented:

[0229] Obtain a link containing a preset identifier and a dynamic token from a server;

[0230] Send the link to a user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform check-in processing;

[0231] Send a check-in query request to the server, and receive a check-in result returned by the server after performing check-in processing.

[0232] It should be noted that the embodiment of another computer-readable storage medium in this specification and the embodiment of another near-field communication-based check-in processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and the repeated parts will not be elaborated.

[0233] An embodiment of a computer program product provided in this specification is as follows:

[0234] Corresponding to the above-described near-field communication-based check-in processing method, based on the same inventive concept, one or more embodiments of this specification also provide a computer program product.

[0235] A computer program product includes computer programs / instructions, and when the computer programs / instructions are executed by a processor, the following steps are implemented:

[0236] Establish a near-field communication connection with a near-field communication device deployed at a target location;

[0237] Obtain a link containing a preset identifier and a dynamic token from the near-field communication device through the near-field communication connection;

[0238] Start a target application corresponding to the preset identifier and pass the link to the target application;

[0239] Submit the link and the login user information of the target application to a server through the target application for check-in processing.

[0240] It should be noted that the embodiments of a computer program product in this specification and the embodiments of a near-field communication-based check-in processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the corresponding method described above, and repeated parts will not be elaborated.

[0241] Another embodiment of the computer program product provided in this specification is as follows:

[0242] Corresponding to another near-field communication-based check-in processing method described above, based on the same inventive concept, one or more embodiments of this specification also provide another computer program product.

[0243] A computer program product includes computer programs / instructions, and when the computer programs / instructions are executed by a processor, the following steps are implemented:

[0244] Obtain a link containing a preset identifier and a dynamic token from a server;

[0245] Send the link to a user terminal that has established a near-field communication connection, so that the user terminal and the server cooperate to perform check-in processing;

[0246] Send a check-in query request to the server and receive a check-in result returned by the server after performing check-in processing.

[0247] It should be noted that the embodiments of another computer program product in this specification and the embodiments of another near-field communication-based check-in processing method in this specification are based on the same inventive concept. Therefore, for the specific implementation of this embodiment, reference may be made to the implementation of the corresponding method described above, and repeated parts will not be elaborated.

[0248] The various embodiments in this specification are described in a progressive manner. For the same or similar parts among the various embodiments, reference can be made to each other. The key point of each embodiment is to illustrate the differences from other embodiments. For example, the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments are all similar to the method embodiments, so the description is relatively simple. For the relevant content in the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, please refer to the corresponding description in the method embodiments.

[0249] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the specific order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0250] In the 1930s, it was obvious to distinguish whether an improvement in a technology was a hardware improvement (e.g., improvement in circuit structures such as diodes, transistors, switches, etc.) or a software improvement (improvement in method flows). However, with the development of technology, many improvements in method flows today can be regarded as direct improvements in hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structures by programming the improved method flows into the hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented with a hardware entity module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. The designer can program by himself to "integrate" a digital system on a PLD, without having to ask the chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL), and there is not only one kind of HDL, but many kinds, 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, RHDL (Ruby Hardware Description Language), etc. Currently, the most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply making a little logical programming of the method flow with the above-mentioned several hardware description languages and programming it into the integrated circuit, it is easy to obtain the hardware circuit implementing the logical method flow.

[0251] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or the structures within the hardware component.

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

[0253] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0254] Those skilled in the art should understand that one or more embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, one or more embodiments of this specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, this specification can take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0255] This specification is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable interactive processing device in a live streaming room to produce a machine, such that the instructions executed by the processor of the computer or other programmable interactive processing device in the live streaming room produce means for implementing the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0256] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable interactive processing device in a live streaming room to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means that implement the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0257] These computer program instructions can also be loaded onto a computer or other programmable interactive processing device in a live streaming room, such that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.

[0258] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0259] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0260] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer-readable 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0261] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, the elements defined by the sentence "includes at least one ..." do not exclude the presence of other identical elements in the process, method, commodity or device including the elements.

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

[0263] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A check-in processing method based on near-field communication, comprising: Establishing a near-field communication connection with a cash register device deployed by a merchant; Obtaining a link containing a preset identifier and a dynamic token from the cash register device through the near-field communication connection; Starting a target application corresponding to the preset identifier and passing the link to the target application; Submitting the link and the merchant member information of the target application to a server through the target application to establish a check-in relationship between the merchant member and the cash register device.

2. The check-in processing method based on near-field communication according to claim 1, wherein the cash register device is configured with a near-field communication component; and the logged-in user of the target application includes the merchant member.

3. The check-in processing method based on near field communication according to claim 2, wherein establishing the check-in relationship between the merchant member and the cash register device includes: Based on the binding record between the merchant member and the cash register device, a cash register check-in relationship between the merchant member and the cash register device is established.

4. The check-in processing method based on near-field communication according to claim 3, after the cash register check-in relationship is established, the rewards obtained after payment and cash register through the cash register device are distributed to the member account of the merchant member.

5. The check-in processing method based on near-field communication according to claim 2, after the operation of passing the link to the target application is executed, and before the operation of submitting the link and the merchant member information of the target application to the server through the target application, further comprising: Entering a service subroutine corresponding to the cash register device based on the preset identifier and passing the link to the service subroutine; Wherein, the link and the merchant member information are submitted to the server through the service subroutine.

6. The check-in processing method based on near-field communication according to claim 1, further comprising: Determining a check-in method according to the device type of the cash register device, the venue type of the merchant and / or the user type of the merchant member, and performing check-in processing according to the check-in method.

7. The check-in processing method based on near-field communication according to claim 6, the check-in method includes at least one of the following: Performing user check-in processing of merchant members for the cash register device, performing location check-in processing or venue check-in processing of merchant members in the merchant, and performing item check-in processing of corresponding items of the merchant or the cash register device for merchant members.

8. The check-in processing method based on near-field communication according to claim 1, wherein the link is obtained by the cashier device from the server; The obtaining method of the link includes: Sending a link obtaining request carrying a device identifier to the server in a polling manner and receiving the link returned by the server; Or, after establishing a near-field communication connection with a user terminal, sending a link obtaining request carrying a device identifier to the server and receiving the link returned by the server.

9. The check-in processing method based on near-field communication according to claim 1, after the previous check-in processing of the cash register device is completed, the server sends the link to the cash register device.

10. The check-in processing method based on near-field communication according to claim 1, the establishing of the check-in relationship between the merchant member and the cash register device is implemented in the following manner: Generate a check-in record including the device identifier of the cash register device, the merchant member information, and the dynamic token, and send a check-in result carrying the check-in record to the cash register device and the user terminal.

11. A check-in processing method based on near field communication, applied to a cash register device deployed by a merchant, the method comprising: Obtain a link including a preset identifier and a dynamic token from a server; Send the link to a user terminal with which a near field communication connection is established, so that the user terminal cooperates with the server to establish a check-in relationship between a merchant member and the cash register device; Send a check-in query request to the server, and receive a check-in result returned by the server after establishing the check-in relationship.

12. The check-in processing method based on near field communication according to claim 11, wherein the obtaining a link including a preset identifier and a dynamic token from the server comprises: Send a link acquisition request carrying a device identifier to the server in a polling manner, and receive the link returned by the server; Alternatively, after establishing a near field communication connection with the user terminal, send a link acquisition request carrying a device identifier to the server, and receive the link returned by the server.

13. The check-in processing method based on near field communication according to claim 11, wherein the cash register device is configured with a near field communication component; the logged-in users of the target application corresponding to the preset identifier include the merchant members.

14. The check-in processing method based on near-field communication according to claim 13, wherein establishing the check-in relationship between the merchant member and the cash register device includes: Establish a check-in relationship between the merchant member and the cash register device based on the binding record between the merchant member and the cash register device.

15. The check-in processing method based on near field communication according to claim 14, further comprising: Determine a check-in method according to the device type of the cash register device, the venue type of the merchant, and / or the user type of the merchant member, and perform check-in processing according to the check-in method; Wherein, the check-in method includes at least one of the following: performing user check-in processing of a merchant member for the cash register device, performing location check-in processing or venue check-in processing of a merchant member in a merchant, and performing item check-in processing of a merchant or an item corresponding to the cash register device for a merchant member.

16. The check-in processing method based on near field communication according to claim 11, wherein the obtaining a link including a preset identifier and a dynamic token from the server comprises: Receive the link sent by the server after the previous check-in processing of the cash register device is completed.

17. A check-in processing device based on near field communication, comprising: A connection establishment module configured to establish a near field communication connection with a cash register device deployed by a merchant; A link acquisition module configured to obtain a link including a preset identifier and a dynamic token from the cash register device through the near field communication connection; An application startup module configured to start a target application corresponding to the preset identifier and pass the link to the target application; A data submission module configured to submit the link and the merchant member information of the target application to a server through the target application to establish a check-in relationship between a merchant member and the cash register device.

18. A check-in processing device based on near field communication, which is applied to a cash register device deployed by a merchant. The device includes: A link acquisition module, configured to acquire a link containing a preset identifier and a dynamic token from a server; A link sending module, configured to send the link to a user terminal that has established a near field communication connection, so that the user terminal and the server cooperate to establish a check-in relationship between a merchant member and the cash register device; A result receiving module, configured to send a check-in query request to the server and receive a check-in result returned by the server after establishing the check-in relationship.

19. A check-in processing device based on near field communication, including: A processor; And a memory configured to store computer-executable instructions, where the computer-executable instructions, when executed, cause the processor to: Establish a near field communication connection with a cash register device deployed by a merchant; Obtain a link containing a preset identifier and a dynamic token from the cash register device through the near field communication connection; Start a target application corresponding to the preset identifier and pass the link to the target application; Submit the link and the merchant member information of the target application to the server through the target application to establish a check-in relationship between a merchant member and the cash register device.

20. A check-in processing device based on near field communication, including: A processor; And a memory configured to store computer-executable instructions, where the computer-executable instructions, when executed, cause the processor to: Obtain a link containing a preset identifier and a dynamic token from a server; Send the link to a user terminal that has established a near field communication connection, so that the user terminal and the server cooperate to establish a check-in relationship between a merchant member and a cash register device deployed by the merchant; Send a check-in query request to the server and receive a check-in result returned by the server after establishing the check-in relationship.

21. A computer-readable storage medium for storing computer-executable instructions, where the computer-executable instructions, when executed, implement the steps of the method according to claim 1 or 11.

Images