Near field service method, device and equipment

Abstract

The embodiments of this specification disclose a near-field service method, device, and apparatus. The NFC tag of the table is read through the near-field communication NFC function; the NFC tag is sent to the table application server, so that the table application server determines the table identification corresponding to the NFC tag based on the pre-stored correspondence between the NFC tag and the table identification; the page address containing the table identification returned by the table application server is received; and the page is jumped to the table application page corresponding to the page address, so that the user can perform a service selection operation on the table application page. Thus, the user can directly enter the page address to select the service and pay through the NFC function.

Description

Technical Field

[0001] This specification relates to the field of Internet technology, and in particular to near-field service methods, devices, and equipment. Background Art

[0002] When merchants provide near-field services at tables, they often provide the table's QR code for users to identify, thereby binding the table and the user, making it easier for users to select services and make subsequent payments. Currently, the near-field service entrance is usually based on scanning codes, searching, entering addresses, etc., to enter services such as ordering food, receiving coupons, joining clubs, placing orders, etc., and the steps are relatively cumbersome.

[0003] Based on this, a more convenient near-field service solution is needed. Summary of the invention

[0004] This specification and embodiments provide a near-field service method, apparatus, device, and storage medium to solve the following technical problem: A more convenient near-field service solution is needed.

[0005] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0006] In a first aspect, an embodiment of the present specification provides a near-field service method, which is applied to a user end of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the method comprises: reading the NFC tag of the table through a near-field communication NFC function; sending the NFC tag to a table application server, so that the table application server determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; receiving a page address containing the table identifier returned by the table application server; and jumping to a table application page corresponding to the page address, so that the user can perform a service selection operation on the table application page.

[0007] In a second aspect, an embodiment of the present specification provides another near-field service method, which is applied to a merchant side of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the method comprises: obtaining a table identification of the table; obtaining the NFC tag of the table through a near-field communication NFC function; and sending the table identification and the NFC tag to a table application server side, so that the table application server side generates and stores a correspondence between the table identification and the NFC tag.

[0008] In a third aspect, an embodiment of the present specification provides another near-field service method, which is applied to a table application server of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the method comprises: receiving an NFC tag sent by a user terminal; determining a table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; and sending a page address containing the table identifier to the user terminal so that the user terminal jumps to a table application page corresponding to the page address.

[0009] Corresponding to the first aspect, an embodiment of the present specification provides a near-field service device, which is applied to a user end of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the device comprises: a first NFC module, which reads the NFC tag of the table through a near-field communication NFC function; a first sending module, which sends the NFC tag to a table application server, so that the table application server determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; a first receiving module, which receives a page address containing the table identifier returned by the table application server; and a first jumping module, which jumps to a table application page corresponding to the page address, so that the user can perform a service selection operation on the table application page.

[0010] Corresponding to the second aspect, an embodiment of the present specification provides another near-field service device, which is applied to a merchant side of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the device comprises: a second acquisition module, which acquires a table identification of the table; a second NFC module, which acquires the NFC tag of the table through a near-field communication NFC function; and a second sending module, which sends the table identification and the NFC tag to a table application server, so that the table application server generates and stores a correspondence between the table identification and the NFC tag.

[0011] Corresponding to the second aspect, an embodiment of the present specification provides another near-field service device, which is applied to a table application server end of a table service, wherein a near-field communication NFC tag is pre-installed in the table, and the device includes: a third receiving module, which receives the NFC tag sent by the user end; a third determining module, which determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; and a third sending module, which sends a page address containing the table identifier to the user end, so that the user end jumps to the table application page corresponding to the page address.

[0012] In a fourth aspect, an embodiment of the present specification provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in the first aspect, the second aspect, or the third aspect.

[0013] In the fifth aspect, an embodiment of the present specification provides a non-volatile computer storage medium storing computer executable instructions. When a computer reads the computer executable instructions in the storage medium, the instructions enable one or more processors to execute the method described in the first aspect, the second aspect, or the third aspect.

[0014] At least one of the above technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: reading the NFC tag of the table through the near field communication NFC function; sending the NFC tag to the table application server, so that the table application server determines the table identification corresponding to the NFC tag based on the pre-stored correspondence between the NFC tag and the table identification; receiving the page address containing the table identification returned by the table application server; jumping to the table application page corresponding to the page address, so that the user can perform service selection operations on the table application page. Therefore, the user can directly enter the page address to select services and pay through the NFC function. The user only needs to bring the mobile device with the NFC function activated close to the near field communication NFC tag pre-set in the table, which greatly shortens the user's operation process and improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 A flowchart of a near-field service method provided in an embodiment of this specification;

[0017] Figure 2 A logical schematic diagram of a user terminal performing a meal ordering service provided in an embodiment of this specification;

[0018] Figure 3 A flowchart of another near-field service method provided in an embodiment of this specification;

[0019] Figure 4A logical schematic diagram of binding a table identification and an NFC tag at a merchant end provided in an embodiment of this specification;

[0020] Figure 5 A schematic diagram of an operation link of a merchant terminal provided in an embodiment of this specification;

[0021] Figure 6 A flowchart of another near-field service method provided in an embodiment of this specification;

[0022] Figure 7 A schematic diagram of the structure of a near-field service device provided in an embodiment of this specification;

[0023] Figure 8 A schematic diagram of the structure of another near-field service device provided in an embodiment of this specification;

[0024] Fig. 9 A schematic diagram of the structure of another near-field service device provided in an embodiment of this specification;

[0025] Fig.10 A schematic diagram of the structure of an electronic device for near field service provided in an embodiment of this specification. DETAILED DESCRIPTION

[0026] The embodiments of this specification provide a near field service method, apparatus, device, and storage medium.

[0027] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0028] The table service in the embodiments of this specification refers to a table with multiple different table identifiers provided by the merchant. The merchant provides the same optional services on each table. The merchant determines the service types selected by different users through different table identifiers, including services such as ordering food, board games, temporary storage, study rooms, etc. In the table services currently provided by merchants, a QR code (usually including a table identifier, such as a table number) or a public account is usually provided, allowing users to scan and enter the corresponding payment page to select services.

[0029] Taking table ordering as an example, in this process, the user needs to perform the following steps: unlock the mobile device --> find the relevant application --> open the application --> click the "Scan" function -> scan the QR code -> enter the mini program ordering service page. That is, at least 6 steps are required to enter the mini program ordering service page.

[0030] Based on this, the embodiments of this specification provide a more convenient near-field service solution. Specifically, it includes three aspects: user end, merchant end and desktop application server end. The desktop application server end includes the front end and back end of the service application that can provide relevant functions (such as ordering food, game selection, etc.).

[0031] In the first aspect, Figure 1 As shown, Figure 1 A flowchart of a near field service method provided in an embodiment of the present specification is applied to a user end of a table service, wherein a near field communication NFC tag is pre-installed in the table, and the method comprises the following steps:

[0032] S101, reading the NFC tag of the table through the near field communication NFC function.

[0033] The user terminal can use the Near Field Communication (NFC) function contained in various mobile devices (including mobile phones, tablets, etc.) carried by the user to approach the Near Field Communication NFC tag preset in the table.

[0034] The NFC tag is used to uniquely identify an NFC chip, which is usually a string of a predetermined length. The NFC tag in the NFC chip is usually erasable and writable. In the embodiment of this specification, the table can be pre-set with an NFC chip with an NFC tag written in it, so that the table is pre-set with a near field communication NFC tag.

[0035] S103, sending the NFC tag to the desktop application server.

[0036] It should be noted that when the user reads the NFC tag, it can also read the custom path schemeurl pre-written in the NFC chip to start the relevant application and wait for the user's operation and the information returned by the server in the startup interface of the relevant application.

[0037] After the user sends the NFC tag to the table application server, the table application server can perform analysis based on the correspondence between the table identifier and the NFC tag pre-stored by the merchant, thereby identifying the table identifier corresponding to the NFC tag.

[0038] The table identifier corresponds to the actual table at the merchant end, that is, each table identifier is used to uniquely identify a table provided by the merchant. For example, if the merchant provides a total of 20 tables, each table can be given a table identifier from 01 to 20.

[0039] S105: Receive a page address including the table identifier returned by the table application server.

[0040] After determining the table ID, the table application server can generate a page address including the table ID, for example, https: / / xxx.com / xxxx / 12, where "12" is the table ID, indicating that the entity corresponding to the received NFC tag is the 12th table.

[0041] S107 , jumping to the desktop application page corresponding to the page address, so that the user can perform a service selection operation on the desktop application page.

[0042] After the mobile device of the user receives the page address, it can jump to the table application page corresponding to the page address. In the table application page, various service items are provided for users to select so that users can perform service selection operations. In addition, it should be noted that in the table application page after the jump, the table logo can be explicitly displayed, for example, it can be displayed at the top of the page that this is the 12th table; the table logo can also be hidden, so that the display of the table application page entered by users at different tables is the same, and users do not need to care about their actual location.

[0043] It can be seen that through the above-mentioned first aspect of the solution, the user only needs to touch the following three steps: NFC tag -> unlock the mobile phone -> enter the desktop application page containing the desktop logo, that is, the corresponding service selection can be realized in the desktop application page, and the process is greatly shortened.

[0044] The method of the embodiment of this specification reads the NFC tag of the table through the near field communication NFC function; sends the NFC tag to the table application server, so that the table application server determines the table identification corresponding to the NFC tag based on the pre-stored correspondence between the NFC tag and the table identification; receives the page address containing the table identification returned by the table application server; jumps to the table application page corresponding to the page address, so that the user can perform service selection operations on the table application page. Therefore, the user can directly enter the page address to select services and pay through the NFC function. The user only needs to bring the mobile device with the NFC function activated close to the near field communication NFC tag pre-set in the table, which greatly shortens the user's operation process and improves the user experience.

[0045] In one embodiment, after the user has entered the table application page, the table application server may further determine whether it is necessary to issue benefits to the table (benefits include cash, discount coupons, deduction coupons, etc.).

[0046] Specifically, it can be determined whether the merchant has an ongoing benefit distribution activity. If so, the desktop application server can obtain the benefit page address corresponding to the merchant ID, push it to the desktop application page of the user end, and display the benefit collection page or link so that the user can collect it. In this way, accurate service and benefit distribution can be achieved, and the path of benefit distribution can be shortened, thereby improving user experience.

[0047] In one embodiment, the desktop application server may determine the merchant identifier in the following manner:

[0048] The first method is to determine the merchant ID corresponding to the NFC tag from the code of the NFC tag. Since the NFC tag is predetermined by humans, a certain encoding method can be used to include both the merchant ID and the table ID in the NFC tag. For example, taking an NFC tag with a length of 10 as an example, a format such as "guidance identifier + merchant ID + table ID" can be used, where the length of the guidance identifier is 2, the length of the merchant ID is 5, and the length of the table ID is 3. Thus, the table application server can directly identify the merchant ID from the NFC tag, and then determine whether the merchant has a corresponding rights issuance activity on the table application server.

[0049] The second method is to determine the merchant ID from the pre-stored correspondence between the NFC tag and the merchant ID. That is, the merchant has bound the correspondence between the NFC tag and the merchant ID in advance and stored it in the desktop application server. The correspondence stored in the desktop application server is the correspondence between "NFC tag, merchant ID, and desktop ID", so that the merchant ID can be directly queried.

[0050] In one embodiment, the user can also perform payment operations in the desktop application page, thereby generating a payment transaction including the desktop identifier (that is, extracted from the desktop application page), and sending the payment transaction to the desktop application server, so that the desktop application server executes the payment according to the desktop identifier. After the transaction is completed, the desktop application server can forward the payment result including the desktop identifier to the merchant, so that the merchant can confirm and settle the transaction, thereby realizing a closed transaction loop between the merchant and the user and improving the experience of the merchant and the user.

[0051] like Figure 2 As shown, Figure 2This is a logical diagram of a user terminal ordering service provided in an embodiment of this specification. The entrance to the near-field service is pre-placed in the operating system layer of the device. The user only needs to use the NFC function of the device to read the NFC tag and then directly enter the table application page on the user terminal to select the service. In this process, the user can order the service and receive the rights and interests without having to perceive the table selected at will.

[0052] In the second aspect, Figure 3 As shown, Figure 3 A flowchart of another near field service method provided in an embodiment of the present specification is applied to a merchant end of a table service, wherein a near field communication NFC tag is pre-installed in the table, and the method comprises the following steps:

[0053] S301: Obtain a table identifier of the table.

[0054] The acquisition here can be manually specified and input by the merchant in the merchant's mini-program (that is, the merchant can manually specify the number of the table where the NFC tag is located), or a digital object unique identifier (digital object unique identifier, DOI) containing the table identification already exists on the table, and the DOI is identified to obtain the table identification.

[0055] S303, obtaining the NFC tag of the table through the near field communication NFC function.

[0056] Similar to the situation in the first aspect, a chip containing a near field communication NFC tag is pre-installed in the table. For example, the NFC chip can be set below the QR code on the table, so that the NFC tag of the table can be obtained by approaching the QR code.

[0057] S305: Send the table identifier and the NFC tag to the table application server, so that the table application server generates and stores the corresponding relationship between the table identifier and the NFC tag.

[0058] The correspondence between the table identification and the NFC tag can be bound in the merchant end or in the table application server end, which is not limited here.

[0059] Through the above method, it is possible to bind the table identification and the NFC tag on the table application server based on the needs of the merchant.

[0060] In one embodiment, the merchant may pre-set a chip containing an NFC tag under the DOI containing the table identification. The table identification of the table can be obtained by scanning the DOI containing the table identification through the merchant-side application and identifying the DOI. Furthermore, the corresponding binding plug-in can be called up in the application, and the NFC function of the merchant-side device where the application is located is activated through the binding plug-in, so that the merchant can bring the device close to the DOI to obtain the NFC tag (because the chip is pre-embedded under the DOI, the distance when the merchant scans the DOI may be enough to obtain the NFC tag), and perform subsequent corresponding binding. In this way, the merchant only needs to scan the preset DOI in the table once to automatically complete the subsequent binding in the application, which is more convenient for the merchant.

[0061] In one embodiment, the table identification of the table can be represented by a page address. For example, a page address such as https: / / xxx.com / xxxx / 12 is written in the DOI preset on the table, where "12" is the table identification. Then, the page address and the obtained NFC tag are sent to the table application server so that the table application server generates and stores the corresponding relationship between the page address and the NFC tag. After the binding is successful, the table application server can return a notification message indicating the successful binding.

[0062] In addition, the scanned table logo may also include information about the merchant and store. Figure 4 As shown, Figure 4 This is a logic diagram of a merchant end binding a table identification and an NFC tag provided in an embodiment of this specification. In this diagram, an NFC chip containing an NFC tag is preset below a QR code containing a table code identification so that the merchant can scan it. Figure 5 As shown, Figure 5 A schematic diagram of an operation link of a merchant end provided in an embodiment of the present specification. In the schematic diagram, if the merchant has not activated the NFC function in advance, the plug-in in the binding application can also prompt the merchant to activate the NFC function after scanning the table identification, and the NFC function can be activated and the NFC tag can be read without leaving the page of the binding application, that is, for the merchant, only the device needs to be close to the pre-laid QR code and chip to complete the binding of the two in the binding application, which improves the efficiency of the binding operation for merchants with a large number of tables to be bound.

[0063] In a third aspect of the embodiments of this specification, another near field service method is provided, which is applied to a table application server end of a table service, wherein a near field communication NFC tag is pre-set in the table, such as Figure 6 As shown, Figure 6A flowchart of another near-field service method provided in an embodiment of this specification, the method comprising:

[0064] S601, receiving an NFC tag sent by a user terminal, wherein the NFC tag is obtained by the user terminal from a near field communication NFC tag pre-set on a table through an NFC function.

[0065] S603: Determine the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier.

[0066] In the aforementioned second aspect, the method for generating the correspondence between the NFC tag and the table identifier has been explained and will not be repeated here.

[0067] S603: Send a page address including the desktop identifier to the user terminal, so that the user terminal jumps to the desktop application page corresponding to the page address.

[0068] If the server stores the correspondence between the page address containing the table identifier and the NFC tag, the page address obtained by querying based on the correspondence can be directly sent to the user end; if the server stores the correspondence between the table identifier and the NFC tag, the page address containing the table identifier can be generated on the server and then sent to the user end. The user end can click or jump based on the received page address, so that the user can jump to the table application page corresponding to the page address for user operation.

[0069] In one embodiment, the server can also query the merchant identifier corresponding to the NFC tag to determine whether the merchant has any promotional activities. Specifically, the merchant identifier corresponding to the NFC tag can be determined from the code of the NFC tag. Since the NFC tag is predetermined by humans, a certain encoding method can be used to include both the merchant identifier and the table identifier in the NFC tag. Then, the table application server determines whether the merchant has a corresponding rights distribution activity; or, the merchant identifier is determined from the pre-stored correspondence between the NFC tag and the merchant identifier. That is, the merchant has already bound the correspondence between the NFC tag and the merchant identifier and stored it in the table application server. The correspondence stored in the table application server is the correspondence of "NFC tag, merchant identifier, table identifier", so that the merchant identifier can be directly queried. Figure 4 As shown in , when the merchant sends the table identification and NFC tag to the table application server, the merchant can also send the merchant identification and store information to the table application server at the same time, so that the table application server can generate and store the correspondence between "NFC tag, merchant identification, table identification" based on the received information.

[0070] In this way, the merchant ID can be determined based on the NFC tag, and then the rights and interests page address corresponding to the merchant ID can be obtained, and the rights and interests page address can be sent to the user terminal, so that the user terminal can display the rights and interests claiming page corresponding to the rights and interests page address in the desktop application page, and claim the rights and interests. In this way, accurate service and rights and interests issuance can be achieved, the merchant's promotion income can be increased, and the merchant's store operation can be promoted more efficiently.

[0071] Corresponding to the first aspect, the embodiment of the present specification further provides a near field service device, which is applied to a user end of a table service, wherein a near field communication NFC tag is pre-installed in the table, such as Figure 7 As shown, Figure 7 This is a schematic diagram of the structure of a near-field service device provided in an embodiment of this specification, the device comprising:

[0072] The first NFC module 701 reads the NFC tag of the table through the near field communication NFC function;

[0073] A first sending module 703 sends the NFC tag to the table application server, so that the table application server determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier;

[0074] A first receiving module 705 receives a page address including the table identification returned by the table application server;

[0075] The first jump module 707 jumps to the desktop application page corresponding to the page address, so that the user can perform a service selection operation on the desktop application page.

[0076] Optionally, the first receiving module 705 is also used for 7, receiving the rights page address returned by the desktop application server, wherein the rights page address is determined by the desktop application server based on the NFC tag; and displaying the rights collection page corresponding to the rights page address in the desktop application page.

[0077] Optionally, the rights and interests page address received by the first receiving module 705 is determined by the desktop application server in the following manner: the desktop application server determines the merchant identifier corresponding to the NFC tag from the code of the NFC tag, and obtains the rights and interests page address corresponding to the merchant identifier; or, the desktop application server determines the merchant identifier from a pre-stored correspondence between the NFC tag and the merchant identifier, and obtains the rights and interests page address corresponding to the merchant identifier.

[0078] Optionally, the device also includes a payment module 709, which receives a user's payment operation in the desktop application page, generates a payment transaction including the desktop identifier, sends the payment transaction to the desktop application server, so that the desktop application server executes the payment according to the desktop identifier, and forwards the payment result including the desktop identifier to the merchant.

[0079] Corresponding to the second aspect, the embodiment of the present specification also provides another near field service device, which is applied to a merchant end of a table service, wherein a near field communication NFC tag is pre-installed in the table, such as Figure 8 As shown, Figure 8 This is a schematic diagram of the structure of another near-field service device provided in an embodiment of this specification, the device comprising:

[0080] The second acquisition module 801 acquires the table identifier of the table;

[0081] The second NFC module 803 obtains the NFC tag of the table through the near field communication NFC function;

[0082] The second sending module 805 sends the table identifier and the NFC tag to the table application server, so that the table application server generates and stores the corresponding relationship between the table identifier and the NFC tag.

[0083] Optionally, the second acquisition module 801 scans the digital object unique identifier DOI provided by the table, identifies the DOI to generate a table identification of the table; the second NFC module acquires the NFC tag preset under the DOI through the near field communication NFC function.

[0084] Optionally, the second acquisition module 801 acquires the page address containing the table identifier; correspondingly, the second sending module sends the page address and the NFC tag to the table application server, so that the table application server generates and stores the correspondence between the page address and the NFC tag.

[0085] Corresponding to the third aspect, the embodiment of the present specification also provides another near field service device, which is applied to a table application server end of a table service, wherein a near field communication NFC tag is pre-set in the table, such as Fig. 9 As shown, Fig. 9 A schematic diagram of the structure of another near-field service device provided in an embodiment of this specification, the device comprising:

[0086] The third receiving module 901 receives the NFC tag sent by the user terminal;

[0087] A third determination module 903 determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier;

[0088] The third sending module 905 sends a page address including the table identifier to the user terminal, so that the user terminal jumps to the table application page corresponding to the page address.

[0089] Optionally, the third determination module 905 determines the merchant identifier corresponding to the NFC tag, and obtains the rights and interests page address corresponding to the merchant identifier; the third sending module sends the rights and interests page address to the user terminal, so that the user terminal displays the rights and interests claiming page corresponding to the rights and interests page address in the desktop application page.

[0090] In a fourth aspect, the embodiments of this specification further provide an electronic device, Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification, the device includes:

[0091] at least one processor; and,

[0092] a memory communicatively connected to the at least one processor; wherein,

[0093] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method as described in any one of the first aspect, the second aspect, or the third aspect.

[0094] In the fifth aspect, based on the same idea, the embodiments of this specification also provide a non-volatile computer storage medium storing computer executable instructions. When the computer reads the computer executable instructions in the storage medium, the instructions enable one or more processors to execute the method described in the first aspect, the second aspect or the third aspect.

[0095] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one 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. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0096] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0097] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a 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 a combination of any of these devices.

[0098] For the convenience of description, the above device is described by dividing it into various units according to its functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0099] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

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

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

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

[0103] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

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

[0105] 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 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 tape 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 temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0106] 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 more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0107] This 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. This 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.

[0108] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0109] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0110] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A near field service method, applied to a user end of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, and the method comprises: Reading the NFC tag of the table through the NFC function; Sending the NFC tag to the table application server, so that the table application server determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; Receiving a page address including the table identification returned by the table application server; Jump to the desktop application page corresponding to the page address, so that the user can perform a service selection operation on the desktop application page; The corresponding relationship is obtained based on the following processing of the merchant end of the table service: Scanning the digital object unique identifier DOI provided by the table, identifying the DOI to generate a table identifier of the table; Obtain the NFC tag preset under the DOI through the near field communication NFC function; The table identifier and the NFC tag are sent to the table application server, so that the table application server generates and stores a corresponding relationship between the table identifier and the NFC tag.

2. The method of claim 1, wherein: The method further comprises: Receiving a rights page address returned by the desktop application server, wherein the rights page address is determined by the desktop application server based on the NFC tag; The benefit claiming page corresponding to the benefit page address is displayed in the desktop application page.

3. The method of claim 2, wherein: The rights page address is determined by the desktop application server based on the NFC tag, including: The desktop application server determines the merchant ID corresponding to the NFC tag from the code of the NFC tag, and obtains the rights and interests page address corresponding to the merchant ID; or, The desktop application server determines the merchant identifier from the pre-stored correspondence between the NFC tag and the merchant identifier, and obtains the rights and interests page address corresponding to the merchant identifier.

4. The method of claim 1, further comprising: receiving a user's payment operation in the table application page, and generating a payment transaction including the table identifier; The payment transaction is sent to the table application server, so that the table application server performs the payment according to the table identifier and forwards the payment result including the table identifier to the merchant.

5. A near field service method, applied to a merchant end of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, the method comprising: Acquiring the table identification of the table, including: scanning a digital object unique identifier DOI provided by the table, identifying the DOI to generate the table identification of the table; Acquiring the NFC tag of the table through the near field communication NFC function, including: acquiring the NFC tag preset under the DOI through the near field communication NFC function; The table identifier and the NFC tag are sent to the table application server, so that the table application server generates and stores a corresponding relationship between the table identifier and the NFC tag.

6. The method of claim 5, wherein: Obtaining the table identifier of the table, including: Obtaining the page address containing the table identifier; Correspondingly, sending the table identifier and the NFC tag to the table application server so that the table application server generates and stores the correspondence between the table identifier and the NFC tag, including: sending the page address and the NFC tag to the table application server so that the table application server generates and stores the correspondence between the page address and the NFC tag.

7. A near field service method, applied to a table application server of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, the method comprising: Receive the NFC tag sent by the user; Determine the table identifier corresponding to the NFC tag based on the pre-stored correspondence between the NFC tag and the table identifier; Sending a page address including the table identifier to the user terminal so that the user terminal jumps to the table application page corresponding to the page address; The corresponding relationship is obtained based on the following processing of the merchant end of the table service: Scanning the digital object unique identifier DOI provided by the table, identifying the DOI to generate a table identifier of the table; Obtain the NFC tag preset under the DOI through the near field communication NFC function; The table identifier and the NFC tag are sent to the table application server, so that the table application server generates and stores a corresponding relationship between the table identifier and the NFC tag.

8. The method of claim 7, further comprising: Determine the merchant ID corresponding to the NFC tag, and obtain the rights and interests page address corresponding to the merchant ID; The rights and interests page address is sent to the user terminal so that the user terminal displays the rights and interests claiming page corresponding to the rights and interests page address in the desktop application page.

9. A near field service device, applied to a user end of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, and the device comprises: A first NFC module reads the NFC tag of the table through a near field communication (NFC) function; A first sending module, sending the NFC tag to the table application server, so that the table application server determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; A first receiving module receives a page address including the table identification returned by the table application server; A first jump module jumps to a desktop application page corresponding to the page address, so that the user can perform a service selection operation on the desktop application page; The corresponding relationship is obtained based on the following processing of the merchant end of the table service: Scanning the digital object unique identifier DOI provided by the table, identifying the DOI to generate a table identifier of the table; Obtain the NFC tag preset under the DOI through the near field communication NFC function; The table identifier and the NFC tag are sent to the table application server, so that the table application server generates and stores a corresponding relationship between the table identifier and the NFC tag.

10. The device of claim 9, wherein: The first receiving module is also used to receive a rights and interests page address returned by the desktop application server, wherein the rights and interests page address is determined by the desktop application server based on the NFC tag; and display a rights and interests collection page corresponding to the rights and interests page address in the desktop application page.

11. In the device as described in claim 10, the rights and interests page address received by the first receiving module is determined by the desktop application server in the following manner: the desktop application server determines the merchant identifier corresponding to the NFC tag from the code of the NFC tag, and obtains the rights and interests page address corresponding to the merchant identifier; or, the desktop application server determines the merchant identifier from the pre-stored correspondence between the NFC tag and the merchant identifier, and obtains the rights and interests page address corresponding to the merchant identifier.

12. The device of claim 9, wherein: The device also includes a payment module, which receives a user's payment operation in the table application page, generates a payment transaction including the table identifier, sends the payment transaction to the table application server, so that the table application server executes the payment according to the table identifier, and forwards the payment result including the table identifier to the merchant.

13. A near field service device, applied to a merchant terminal of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, and the device comprises: The second acquisition module acquires the table identification of the table, including: scanning the digital object unique identifier DOI provided by the table, identifying the DOI to generate the table identification of the table; The second NFC module obtains the NFC tag of the table through the near field communication NFC function, including: obtaining the NFC tag preset under the DOI through the near field communication NFC function; The second sending module sends the table identifier and the NFC tag to the table application server, so that the table application server generates and stores the corresponding relationship between the table identifier and the NFC tag.

14. The device of claim 13, wherein: The second acquisition module acquires the page address containing the table identifier; correspondingly, the second sending module sends the page address and the NFC tag to the table application server, so that the table application server generates and stores the corresponding relationship between the page address and the NFC tag.

15. A near field service device, applied to a table application server of a table service, wherein a near field communication (NFC) tag is pre-installed in the table, and the device comprises: A third receiving module receives an NFC tag sent by a user terminal; A third determination module determines the table identifier corresponding to the NFC tag based on a pre-stored correspondence between the NFC tag and the table identifier; A third sending module sends a page address including the table identifier to the user terminal, so that the user terminal jumps to the table application page corresponding to the page address; The corresponding relationship is obtained based on the following processing of the merchant end of the table service: Scanning the digital object unique identifier DOI provided by the table, identifying the DOI to generate a table identifier of the table; Obtain the NFC tag preset under the DOI through the near field communication NFC function; The table identifier and the NFC tag are sent to the table application server, so that the table application server generates and stores a corresponding relationship between the table identifier and the NFC tag.

16. The device as described in claim 15, wherein the third determination module determines the merchant identifier corresponding to the NFC tag and obtains the rights and interests page address corresponding to the merchant identifier; the third sending module sends the rights and interests page address to the user terminal so that the user terminal displays the rights and interests collection page corresponding to the rights and interests page address in the desktop application page.

17. An electronic device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 8.

Images