Resource acquisition, transmission and information transmission method and device based on near field communication

Abstract

Embodiments of the present specification provide a resource acquisition method, device and equipment based on near field communication, a resource sending method, device and equipment, an information sending method, device and equipment. The scheme comprises: a user terminal acquires a near field terminal identifier of a near field communication terminal at a specified location through a near field communication mode, and sends a resource type identifier of a resource to be collected by the user to the near field communication terminal, and sends the near field terminal identifier and the resource type identifier to a server. The near field communication terminal sends the resource type identifier to the server. After judging that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near field communication terminal, the server sends the resource corresponding to the resource type identifier to the user terminal.

Description

Technical Field

[0001] This application relates to the field of service processing technology in wireless communication, and particularly to a resource acquisition method based on near-field communication. This application also relates to resource acquisition apparatus and devices, resource transmission methods, apparatus and devices, and information transmission methods, apparatus and devices based on near-field communication. Background Technology

[0002] Currently, to promote the development of the offline economy, online activities are often launched to attract customers. For example, businesses can distribute resources online to attract users to visit their physical locations. However, during the resource distribution process, some users may maliciously defraud the resource distributor, causing the distributor to suffer resource losses.

[0003] Therefore, improving the security of resource distribution and reducing resource losses for resource providers has become an urgent technical problem to be solved. Summary of the Invention

[0004] In view of this, embodiments of this application provide a resource acquisition method, apparatus and device, a resource transmission method, apparatus and device, and an information transmission method, apparatus and device based on near-field communication, to solve the problem of poor security in existing resource distribution.

[0005] This specification provides a resource acquisition method based on near-field communication (NFC), applied to a user terminal, comprising: acquiring a near-field terminal identifier of a near-field communication terminal located at a specified location via NFC; sending a resource type identifier of a resource to be claimed by the user to the NFC terminal; the resource type identifier being sent by the NFC terminal to a server; sending a resource acquisition request to the server for the resource corresponding to the resource type identifier, along with the NFC terminal identifier; and receiving the resource corresponding to the resource type identifier sent by the server; the resource being sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the NFC terminal.

[0006] This specification provides a resource sending method, applied to a server, comprising:

[0007] The system receives a resource acquisition request sent by a user terminal for requesting resources corresponding to a first resource type identifier, as well as a near-field terminal identifier; the near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location; it acquires a second resource type identifier sent by the near-field communication terminal; it determines whether the first resource type identifier and the second resource type identifier are consistent, and obtains an identifier determination result; if the identifier determination result indicates that the first resource type identifier and the second resource type identifier are consistent, it sends the resource corresponding to the first resource type identifier to the user terminal.

[0008] This specification provides an embodiment of an information transmission method based on near-field communication, applied to a near-field communication terminal, comprising:

[0009] The near-field communication terminal's near-field terminal identifier is sent to the user terminal via near-field communication. This near-field terminal identifier is used by the user terminal to send the near-field terminal identifier along with a resource type identifier of the resource to be claimed to the server. The server then retrieves the resource type identifier from the user terminal and sends it to the server, so that the server, after determining that the resource type identifier sent by the near-field communication terminal matches the resource type identifier sent by the user terminal, sends the resource corresponding to the resource type identifier to the user terminal.

[0010] This specification provides an embodiment of a resource acquisition device based on near-field communication, applied to a user terminal, comprising:

[0011] The user-side near-field communication module is used to obtain the near-field terminal identifier of the near-field communication terminal located at a specified location via near-field communication; and to send the resource type identifier of the resource to be claimed by the user to the near-field communication terminal; the resource type identifier is used by the near-field communication terminal to send to the server.

[0012] The request sending module is used to send a resource acquisition request to the server for requesting the resource corresponding to the resource type identifier and the near-field terminal identifier;

[0013] The resource receiving module is used to receive the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

[0014] This specification provides a resource sending device, applied to a server, comprising:

[0015] The request receiving module is used to receive a resource acquisition request sent by a user terminal for requesting a resource corresponding to a first resource type identifier, as well as a near-field terminal identifier; the near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location.

[0016] The information acquisition module is used to acquire the second resource type identifier sent by the near-field communication terminal;

[0017] The judgment module is used to determine whether the first resource type identifier and the second resource type identifier are consistent, and to obtain the identifier judgment result;

[0018] The resource sending module is used to send the resource corresponding to the first resource type identifier to the user terminal if the identifier judgment result indicates that the first resource type identifier is consistent with the second resource type identifier.

[0019] This specification provides an embodiment of an information transmission device based on near-field communication, applied to a near-field communication terminal, comprising:

[0020] The device-side near-field communication module is used to send the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication; the near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server; and to obtain the resource type identifier from the user terminal;

[0021] The information sending module is used to send the resource type identifier to the server, so that the server can determine that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then send the resource corresponding to the resource type identifier to the user terminal.

[0022] This specification provides an embodiment of a user terminal device, comprising:

[0023] At least one processor; and,

[0024] A memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions executable by the at least one processor. These instructions, when executed by the at least one processor, enable the at least one processor to: acquire a near-field terminal identifier (NFC) of a near-field communication terminal located at a specified location via near-field communication; send a resource type identifier of a resource to be claimed by a user to the near-field communication terminal; the resource type identifier is sent by the near-field communication terminal to a server; send a resource acquisition request to the server, requesting the resource corresponding to the resource type identifier, along with the near-field terminal identifier; and receive the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal matches the resource type identifier sent by the near-field communication terminal.

[0026] This specification provides an embodiment of a server, comprising:

[0027] At least one processor; and,

[0028] A memory communicatively connected to the at least one processor; wherein,

[0029] The memory stores instructions executable by the at least one processor. These instructions, when executed by the at least one processor, enable the at least one processor to: receive a resource acquisition request from a user terminal requesting resources corresponding to a first resource type identifier and a near-field terminal identifier; the near-field terminal identifier being an identifier of a near-field communication terminal located at a specified location; acquire a second resource type identifier sent by the near-field communication terminal; determine whether the first resource type identifier and the second resource type identifier are consistent, obtaining an identifier determination result; if the identifier determination result indicates that the first resource type identifier and the second resource type identifier are consistent, then send the resource corresponding to the first resource type identifier to the user terminal.

[0030] This specification provides an embodiment of a near-field communication device, comprising:

[0031] At least one processor; and,

[0032] A memory communicatively connected to the at least one processor; wherein,

[0033] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0034] The near-field communication terminal's near-field terminal identifier is sent to the user terminal via near-field communication. This near-field terminal identifier is used by the user terminal to send the near-field terminal identifier along with a resource type identifier of the resource to be claimed to the server. The server then retrieves the resource type identifier from the user terminal and sends it to the server, so that the server, after determining that the resource type identifier sent by the near-field communication terminal matches the resource type identifier sent by the user terminal, sends the resource corresponding to the resource type identifier to the user terminal.

[0035] At least one embodiment in this specification can achieve the following beneficial effects:

[0036] By placing a near-field communication (NFC) terminal at a designated location, users can obtain the NFC terminal identifier and send the resource type identifier of the resource they wish to claim to the NFC terminal upon arriving at that location. Subsequently, the server determines the corresponding NFC terminal based on the NFC terminal identifier sent by the user's terminal, and then matches the resource type identifier sent by the determined NFC terminal with the resource type identifier sent by the user's terminal. If they match, the server sends the resource corresponding to that resource type identifier to the user's terminal. This scheme ensures that users can only claim resources after arriving at the designated location of the NFC terminal and after the data sent by the user's terminal and the NFC terminal have been verified. This mitigates the risk of cheating during resource claiming, thereby improving the security of resource distribution and reducing the risk of resource loss for the resource distributor. Attached Figure Description

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

[0038] Figure 1 This is a schematic diagram illustrating an application scenario of a resource acquisition method based on near-field communication provided in the embodiments of this specification.

[0039] Figure 2 This is a flowchart illustrating a resource acquisition method based on near-field communication provided in an embodiment of this specification.

[0040] Figure 3 This is a schematic diagram of a first resource retrieval page provided in an embodiment of this specification;

[0041] Figure 4 This is a schematic diagram of a second resource acquisition page provided in the embodiments of this specification;

[0042] Figure 5 This is a schematic diagram of a resource display page provided in an embodiment of this specification;

[0043] Figure 6 This is a flowchart illustrating a resource sending method provided in an embodiment of this specification;

[0044] Figure 7 This is a flowchart illustrating an information transmission method based on near-field communication provided in the embodiments of this specification;

[0045] Figure 8 The embodiments provided in this specification correspond to Figure 2 , Figure 6 as well as Figure 7 A schematic diagram of the swimlane flow for resource allocation methods;

[0046] Figure 9 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of a resource acquisition device based on near-field communication;

[0047] Figure 10 The embodiments provided in this specification correspond to Figure 6 A schematic diagram of the structure of a resource sending device;

[0048] Figure 11 The embodiments provided in this specification correspond to Figure 7 A schematic diagram of an information transmission device based on near-field communication;

[0049] Figure 12 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a user terminal device;

[0050] Figure 13 The embodiments provided in this specification correspond to Figure 6 A schematic diagram of the structure of a server device;

[0051] Figure 14 The embodiments provided in this specification correspond to Figure 7 A schematic diagram of the structure of a near-field communication device. Detailed Implementation

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

[0053] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” used in one or more embodiments of this application and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in one or more embodiments of this application refers to and includes any or all possible combinations of one or more associated listed items.

[0054] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this application, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

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

[0056] Currently, resource providers typically set low access permissions when distributing resources, such as allowing users to directly claim resources. However, in order to obtain resources, users may sometimes resort to deception to trick resource providers, thus posing a risk of resource loss to the resource providers.

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

[0058] Figure 1 This is a schematic diagram illustrating an application scenario of a resource acquisition method based on near-field communication provided in the embodiments of this specification.

[0059] like Figure 1 As shown in the diagram, the application scenario includes user device 101, target device 102, and server 103.

[0060] In the embodiments of this specification, the user equipment may include, but is not limited to, smartphones, tablets, laptops, smart interactive devices, wearable devices, and in-vehicle smart terminals, wherein wearable devices may include, but are not limited to, smart bracelets, smartwatches, smart glasses, etc. User equipment 101 can be any one of these user equipment.

[0061] The target device may include, but is not limited to, NFC tags, smart cards, access control cards, payment terminals or other smart devices, and the target device 102 may be any one of the target devices.

[0062] A server can be, but is not limited to, any device, equipment, platform, equipment cluster, or cloud computing service center with computing and processing capabilities. Server 103 is any type of server.

[0063] A short-range communication connection can be established between the user equipment and the target device. This short-range communication connection includes, but is not limited to, Near Field Communication (NFC), local area network (LAN), Bluetooth, and infrared connections. The target device can exchange data in response to requests from the user equipment.

[0064] Both the user device and the target device can establish a communication connection with the server. This communication connection can take various forms, including but not limited to local area network (LAN) connections, wide area network (WAN) connections, internet connections, or other types of data network connections. Both the user device and the target device can also exchange data with the server.

[0065] This application provides a resource acquisition method based on near-field communication, which will be described in detail in the following embodiments.

[0066] Figure 2 This is a flowchart illustrating a resource acquisition method based on near-field communication provided in the embodiments of this specification.

[0067] From a programming perspective, the entity executing the process can be a program mounted on a user terminal. It can be understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

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

[0069] Step 202: Obtain the near-field terminal identifier of the near-field communication terminal located at the specified location through near-field communication.

[0070] In the embodiments of this specification, both the user terminal and the near-field communication terminal can be terminal devices with near-field communication functionality. During near-field communication between the user terminal and the near-field communication terminal, the user terminal can be a device that actively initiates communication, responsible for generating a radio frequency field and initiating the NFC communication process. The near-field communication terminal can be a device that passively responds. The user terminal can interact with the near-field communication terminal by sending commands and data, and the near-field communication terminal relies on the radio frequency field generated by the user terminal for power supply and data transmission.

[0071] In practical applications, the user terminal can send a near-field terminal identifier acquisition request to the near-field communication terminal based on NFC. In response to the near-field terminal identifier acquisition request sent by the user terminal, the near-field communication terminal sends the near-field terminal identifier to the user terminal.

[0072] In the embodiments described in this specification, the designated location can be a location pre-set by the resource provider, indicating that the user can only receive the corresponding resources upon arriving at the designated location. In practical applications, taking a scenic area scenario as an example, the designated location can be any location within the scenic area, such as the exit gate or the attraction information area, without limitation.

[0073] In the embodiments described in this specification, the near-field terminal identifier can be any one of the name, serial number, or ID number that is pre-set for the near-field communication terminal, and there is no limitation on this.

[0074] Step 204: Send the resource type identifier of the resource to be claimed by the user to the near-field communication terminal; the resource type identifier is used by the near-field communication terminal to send to the server.

[0075] In the embodiments described in this specification, the resources can be digital resources displayed to the user in an application logged into on the user's terminal, where the resources are distributed by a resource provider. The application can be developed by the resource provider or by other third-party service providers. This application can display and distribute not only resources provided by the resource provider but also resources provided by other resource providers.

[0076] The resource type identifier can be any one of the following: resource name, resource type number, resource ID number, or resource order number. The resource order number can be a random string generated by the user terminal after the user selects the resource, based on user information, the resource information corresponding to the selected resource, user terminal information, and the timestamp information when the user selected the resource. User information may include the user's identity information or the user's account information when logging into the application. Resource information may include at least one of the following: resource name, resource type number, or resource ID number. User terminal information may be the unique device identifier information corresponding to the user terminal or the IP address information corresponding to the user terminal.

[0077] In the embodiments described in this specification, after a user logs into an application on their terminal that provides resources from a resource provider, they can see various types of resources on a resource display page. When a user triggers a claim operation on any resource to be claimed on the resource display page (e.g., any resource associated with the specified location), the user terminal can determine the resource type identifier for the selected resource based on the user's claim operation. In practical applications, different resources on the application's resource display page can correspond to different resource type identifiers. For example, when a user performs a claim operation on the first resource on the application's resource display page, the user terminal can determine the first resource type identifier corresponding to the first resource in response to the user's claim operation; similarly, when a user performs a claim operation on the second resource on the application's resource display page, the user terminal can determine the second resource type identifier corresponding to the second resource in response to the user's claim operation.

[0078] In the embodiments described in this specification, after the user terminal establishes a near-field communication connection with the near-field communication terminal, the user terminal can send the determined resource type identifier to the near-field communication terminal, so that the near-field communication terminal can send the received resource type identifier to the server. The server can be the server corresponding to the application that issued the resource from the resource issuer.

[0079] Step 206: Send a resource acquisition request to the server for requesting the resource corresponding to the resource type identifier, as well as the near-field terminal identifier.

[0080] In the embodiments of this specification, the user terminal can generate a resource acquisition request based on the determined resource type identifier to obtain the resource corresponding to the resource type identifier, and send the generated resource acquisition request to the server so that the server can respond to the resource acquisition request sent by the user terminal and determine the resource corresponding to the resource type identifier.

[0081] In the embodiments of this specification, the user terminal may also send the near-field terminal identifier obtained from the near-field communication terminal to the server, so that the server can determine the corresponding near-field communication terminal based on the near-field terminal identifier.

[0082] Step 208: Receive the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

[0083] In the embodiments of this specification, the resources obtained by the user terminal from the server can be resources determined by the server based on resource type identifiers. Specifically, before sending the resources corresponding to the resource type identifier to the user terminal, the server needs to determine the corresponding near-field communication terminal based on the near-field terminal identifier sent by the user terminal, and query the resource type identifier sent to the server by that near-field communication terminal. In response to the resource acquisition request sent by the user terminal, the server needs to parse the resource type identifier sent to the server by the user terminal based on the resource acquisition request, and match whether the resource type identifier sent to the server by the near-field communication terminal is consistent with the resource type identifier sent to the server by the user terminal. If they are consistent, the server sends the resources corresponding to the resource type identifier to the user terminal; if they are inconsistent, the server does not send the resources corresponding to the resource type identifier to the user terminal. Furthermore, the server can also return a reason for prohibiting the sending of resources to the user terminal, so that the user terminal can make corresponding adjustments based on the reason.

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

[0085] Figure 2 The method described above involves data interaction between the user terminal and the near-field communication terminal via near-field communication. This ensures that the user is only eligible to receive resources when they are located at the designated location of the near-field communication terminal. Furthermore, before sending resources to the user terminal, the server must verify whether the resource type identifier sent by the user terminal matches the resource type identifier sent by the near-field communication terminal. Only if they match will the server send the resources to the user terminal. This approach mitigates the risk of cheating during resource acquisition, thereby enhancing the security of resource distribution and reducing the risk of resource loss for the resource distributor.

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

[0087] To further enhance the security of resources provided by the resource provider, the server can further determine whether the user terminal's current location meets the requirements before sending resources to the user terminal.

[0088] Optionally, before receiving the resource corresponding to the resource type identifier sent by the server, the method may further include: obtaining the current first location information of the user terminal; sending the first location information to the server; wherein the resource sent by the server and received by the user terminal is the resource sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal and that the first location information is consistent with the pre-registered designated location information of the near-field communication terminal.

[0089] In the embodiments described in this specification, the first location information can be location information collected by the user terminal based on its own positioning function regarding the user terminal's current location. The user terminal can obtain the first location information after establishing a near-field communication connection with the near-field communication terminal.

[0090] In the embodiments of this specification, the user terminal may send the first location information to the server simultaneously with sending the near-field terminal identifier and the resource type identifier. For example, the first location information may be included in the resource acquisition request. Alternatively, the user terminal may send the first location information to the server before or after sending the near-field terminal identifier and the resource type identifier.

[0091] In the embodiments of this specification, the first location information can be location point information, such as longitude AA.XXXXXX and latitude BB.XXXXXX, or it can be location range information, such as longitude range AA.XXXXXX-AA.YYYYYY and latitude range BB.XXXXXX-BB.YYYYYY. The specified location information can also be location point information or location range information. There are no limitations on either.

[0092] In the embodiments of this specification, the designated location information can be information pre-registered by the near-field communication terminal on the server to reflect the installation location of the near-field communication terminal. The server can store the designated location information of the near-field communication terminal. The first location information is consistent with the designated location information, which can be understood as the first location information and the designated location information being completely identical, for example, the first location information and the designated location information are both [AA.XXXXXX, BB.XXXXXX]; or it can be understood as the location corresponding to the first location information being within the range of the location corresponding to the designated location information; or it can be understood as the distance between the location corresponding to the first location information and the location corresponding to the designated location information being less than a preset distance, the preset distance can be 10 meters, or other values, which are not limited thereto.

[0093] In the embodiments of this specification, before sending resources to the user terminal, the server verifies that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal. It can also verify that the first location information of the user terminal is currently consistent with the pre-registered designated location information of the near-field communication terminal. This can further prevent cheating behavior by the resource recipient during the resource receiving process (e.g., using the near-field communication terminal to receive resources in a location other than the designated location), thereby avoiding resource loss problems for the resource issuer.

[0094] Before establishing near-field communication between the user terminal and the near-field communication terminal, the resource type identifier corresponding to the resource that the user needs to claim can be determined in advance.

[0095] Optionally, before obtaining the near-field terminal identifier of the near-field communication terminal located at a specified location via near-field communication, the method may further include: receiving a user's resource claiming operation; and in response to the resource claiming operation, determining the resource type identifier of the resource to be claimed by the user.

[0096] In the embodiments described in this specification, the user terminal device may have an application installed on it for the user to receive resources distributed by the resource distributor.

[0097] Optionally, before receiving the user's resource claiming operation, the process may further include: obtaining a first triggering operation by the user for an application on the user's terminal; in response to the first triggering operation for the application, displaying a first resource claiming page to the user; the first resource claiming page may contain at least one resource icon.

[0098] Figure 3 This is a schematic diagram of a first resource acquisition page provided in an embodiment of this specification. For example... Figure 3 As shown, the first resource claiming page can contain multiple resource icons. Figure 3 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 3 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 3 The information displayed is not specifically limited.

[0099] Optionally, receiving the user's resource claiming operation may specifically include: receiving a second triggering operation from the user on the icon representing the resource to be claimed by the user among the at least one resource icons.

[0100] In this embodiment of the specification, in response to a second triggering operation by the user on the icon of the resource to be claimed by the user, a second resource claiming page is displayed to the user.

[0101] Figure 4 This is a schematic diagram of a second resource acquisition page provided in an embodiment of this specification. For example... Figure 4 As shown, the second resource claiming page may include a resource details control to trigger resource details information, and a promotional slogan guiding users to claim the resource. When a user triggers a third action on the resource details control, the resource details page is displayed to the user in response to the third action. Figure 4 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 4 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 4 The information displayed is not specifically limited.

[0102] Optionally, in response to the resource claiming operation, determining the resource type identifier of the resource to be claimed by the user may specifically include: determining the resource type identifier corresponding to the icon targeted by the second triggering operation as the resource type identifier to be claimed by the user.

[0103] Optionally, the resources include digital collections.

[0104] In this embodiment of the specification, digital collectibles can be digital items with collectible value. Each digital collectible possesses a unique identifier or code, signifying its uniqueness. The quantity of digital collectibles is limited, signifying their scarcity. Ownership, transaction records, and other information about digital collectibles are permanently stored on the blockchain, unchangeable and undeletable, signifying their immutability. Digital collectibles can be bought and sold on multiple platforms, signifying their transferability. Types of digital collectibles may include, but are not limited to: works of art, musical works, video works, virtual items (equipment, characters, etc. in games), digital souvenirs, and virtual real estate (virtual land or buildings sold on the Metaverse platform), etc.

[0105] Optionally, the resources may include any one of the following: visual digital resources, coupons, and virtual currency.

[0106] Optionally, after receiving the resource corresponding to the resource type identifier sent by the server, the process may further include: displaying the resource on the user terminal.

[0107] In the embodiments described in this specification, after the user terminal receives the resource sent by the server, it can display the resource to the user on the resource display page.

[0108] Figure 5 This is a schematic diagram of a resource display page provided in an embodiment of this specification. For example... Figure 5 As shown, the resource display page presents the user with the three types of resources that the user has already claimed. Figure 5 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 5 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 5 The information displayed is not specifically limited.

[0109] Based on and Figure 2 Following the same approach as the solution shown, this specification also provides a resource sending method in its embodiments. Figure 6 This is a flowchart illustrating a resource sending method provided in an embodiment of this specification. From a programming perspective, the entity executing the process can be a program hosted on a server. It is understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

[0110] like Figure 6 As shown, the process may include the following steps.

[0111] Step 602: Receive a resource acquisition request sent by the user terminal for requesting the resource corresponding to the first resource type identifier, and a near-field terminal identifier; the near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location.

[0112] In this embodiment, after receiving a resource acquisition request from a user terminal, the server can determine whether to allocate resources to that user based on the user's historical resource allocation history. In practical applications, if the user has already claimed resource A, other resources besides resource A can be allocated to the user; or if the user has already claimed resource A, and the time interval between the time the user claimed resource A and the time the user received this resource acquisition request is greater than a preset duration, the user can claim any resource, where the preset duration can be one day and is not limited thereto; or if the user has already claimed resource A, all resources cannot be allocated to the user.

[0113] In the embodiments of this specification, the near-field terminal identifier can be the identifier of the near-field communication terminal located at a specified location, obtained by the user terminal device through near-field communication.

[0114] In the embodiments of this specification, the explanations of resource type identifier, near-field communication terminal identifier, specified location, and resource acquisition request can refer to the above-mentioned explanations of... Figure 2 The details of the process will not be repeated here.

[0115] Step 604: Obtain the second resource type identifier sent by the near-field communication terminal.

[0116] In the embodiments described in this specification, the second resource type identifier can be a resource type identifier sent by the user terminal to the near-field communication terminal.

[0117] Step 606: Determine whether the first resource type identifier and the second resource type identifier are consistent, and obtain the identifier determination result.

[0118] In this embodiment, after receiving a resource acquisition request and a near-field terminal identifier from a user terminal, the server can parse the first resource type identifier sent by the user terminal based on the resource acquisition request. The server can also determine the corresponding near-field communication terminal based on the near-field terminal identifier, and query whether a second resource type identifier sent by that near-field communication terminal exists. If a second resource type identifier sent by that near-field communication terminal exists, the server determines whether the first resource type identifier and the second resource type identifier are consistent, obtaining an identifier determination result. If a second resource type identifier sent by that near-field communication terminal does not exist, the server does not send the resource corresponding to the resource type identifier to the user terminal. Furthermore, the server can also return a reason for prohibiting the sending of resources to the user terminal, so that the user terminal can make corresponding adjustments based on the reason.

[0119] In the embodiments of this specification, if the server does not receive a second resource type identifier from the near-field communication terminal corresponding to the near-field terminal identifier within a preset time period after receiving the near-field terminal identifier sent by the user terminal, then the server will not send the resource corresponding to the resource type identifier to the user terminal. Furthermore, the server can also return a reason for prohibiting the sending of resources to the user terminal so that the user terminal can make corresponding adjustments based on the reason.

[0120] Step 608: If the identification judgment result indicates that the first resource type identifier is consistent with the second resource type identifier, then send the resource corresponding to the first resource type identifier to the user terminal.

[0121] In the embodiments of this specification, if the first resource type identifier sent by the user terminal is consistent with the second resource type identifier sent by the near-field communication terminal, then the resource corresponding to the first resource type identifier is sent to the user terminal; if the first resource type identifier sent by the user terminal is inconsistent with the second resource type identifier sent by the near-field communication terminal, then the resource corresponding to the resource type identifier may not be sent to the user terminal, or further, a reason for prohibiting the sending of the resource corresponding to the first resource type identifier may be returned to the user terminal, so that the user terminal can make corresponding adjustments based on the reason.

[0122] In practical applications, before sending resources to the user terminal, the server can also send a resource sending confirmation message to the user terminal so that the user terminal can verify whether the resource determined by the server is the resource expected by the user terminal. After receiving the confirmation message sent by the user terminal to instruct the server to send the resource, the server sends the determined resource to the user terminal.

[0123] In the embodiments described in this specification, before the server sends resources to the user terminal, the user terminal can also confirm the resources determined by the server, thereby improving the accuracy of resource allocation and user experience.

[0124] Figure 6 The method described above involves the server sending resources to the user terminal only after determining that the first resource type identifier sent by the user terminal matches the second resource type identifier sent by the near-field communication terminal. This avoids the risk of cheating by the user during the resource acquisition process, thereby improving the security of resource distribution and reducing the risk of resource loss for the resource distributor.

[0125] based on Figure 6 In addition to the method described herein, this specification also provides some improved implementation methods, which will be described below.

[0126] To further enhance the security of resources provided by the resource provider, the server can further determine whether the user terminal's current location meets the requirements before sending resources to the user terminal.

[0127] Optionally, before sending the resource corresponding to the first resource type identifier to the user terminal, the method may further include: receiving first location information indicating the location of the user terminal; obtaining specified location information indicating the location of the near-field communication terminal; determining whether the first location information and the specified location information are consistent, and obtaining a location determination result.

[0128] If the identifier determination result indicates that the first resource type identifier is consistent with the second resource type identifier, then the resource corresponding to the first resource type identifier is sent to the user terminal. Specifically, this may include: if the identifier determination result indicates that the first resource type identifier is consistent with the second resource type identifier and the location determination result indicates that the first location information is consistent with the specified location information, then the resource corresponding to the first resource type identifier is sent to the user terminal.

[0129] In the embodiments of this specification, the explanations of the first location information, the specified location information, and the consistency between the first location information and the specified location information can be found in the following examples. Figure 2 The details of the process will not be repeated here.

[0130] In the embodiments described in this specification, the server may receive the first location information sent by the user terminal at the same time as receiving the resource acquisition request sent by the user terminal, or before or after receiving the resource acquisition request sent by the user terminal. This is not limited to this.

[0131] In the embodiments described in this specification, the server may pre-store the designated location information of the near-field communication terminal. After obtaining the near-field terminal identifier sent by the user terminal, the server can query the corresponding near-field communication terminal based on the near-field terminal identifier, and query the designated location information that the near-field communication terminal has pre-registered with the server based on the near-field communication terminal.

[0132] In the embodiments of this specification, the server can determine whether the first location information is consistent with the specified location information only after determining that the first resource type identifier sent by the user terminal is consistent with the second resource type identifier sent by the near-field communication terminal. In other words, if the server determines that the first resource type identifier and the second resource type identifier are inconsistent, it does not need to determine whether the first location information is consistent with the specified location information, thus improving the utilization rate of server resources.

[0133] In the embodiments of this specification, the conditions that the server needs to meet to send the resource corresponding to the first resource type identifier to the user terminal may include: the first resource type identifier is consistent with the second resource type identifier, and / or the first location information is consistent with the specified location information.

[0134] In the embodiments of this specification, before sending resources to the user terminal, the server can verify that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal. It can also verify that the first location information of the user terminal is currently consistent with the pre-registered designated location information of the near-field communication terminal. This can further prevent cheating behavior by the resource recipient during the resource acquisition process, thereby avoiding the resource loss problem of the resource issuer.

[0135] To facilitate resource allocation by the server, the server can pre-register the specified location information of the near-field communication terminal.

[0136] Optionally, before obtaining the specified location information representing the location of the near-field communication terminal, the process may further include: receiving a near-field terminal registration request sent by the near-field communication terminal; the near-field terminal registration request carrying the near-field terminal identifier of the near-field communication terminal and the specified location information; and generating and saving the association information between the near-field terminal identifier and the specified location information.

[0137] In the embodiments described in this specification, the near-field terminal registration request can be a request generated by the near-field communication terminal to request the server to register the association between the near-field terminal identifier and the specified location information.

[0138] In the embodiments of this specification, after receiving a near-field terminal registration request sent by a near-field communication terminal, the server responds to the registration request by generating association information between the near-field terminal identifier corresponding to the near-field communication terminal and the specified location information, and saves the association information to the server's storage unit, so that the server can quickly determine the corresponding specified location information based on the association information and the near-field terminal identifier, thereby improving the efficiency of the server in allocating resources.

[0139] To improve the accuracy of registering specified location information for near-field communication terminals, the current location of the near-field communication terminal can be verified to meet the requirements before registration.

[0140] Optionally, before obtaining the specified location information representing the location of the near-field communication terminal, the process may further include: receiving a near-field terminal registration request sent by the near-field communication terminal; the near-field terminal registration request carrying the near-field terminal identifier of the near-field communication terminal, the location information of the near-field communication terminal, and the specified location information to be registered; determining whether the location information and the specified location information are consistent, and obtaining a registration determination result; if the registration determination result indicates that the location information and the specified location information are consistent, then generating and saving the association information between the near-field terminal identifier and the specified location information.

[0141] In the embodiments of this specification, the location information of the near-field communication terminal can be the location information collected based on the positioning function of the near-field communication terminal itself for the current location of the near-field communication terminal, and the time interval between the collection time of the near-field communication terminal location information and the time when the server receives the near-field terminal registration request sent by the near-field communication terminal is less than a preset duration, wherein the preset duration can be 1 minute or other values, which are not limited thereto.

[0142] In the embodiments of this specification, the location information of the near-field communication terminal can be location point information or location range information, and there is no limitation thereto.

[0143] In the embodiments of this specification, the location information of the near-field communication terminal is consistent with the designated location information, which can be understood as the location information of the near-field communication terminal being completely identical to the designated location information. For example, the location information of the near-field communication terminal and the designated location information are both [AA.XXXXXX, BB.XXXXXX]; or it can be understood as the location corresponding to the location information of the near-field communication terminal being within the range of the location corresponding to the location information of the designated location; or it can be understood as the distance between the location corresponding to the location information of the near-field communication terminal and the location corresponding to the location information of the designated location being less than a preset distance, which can be 10 meters or other values, and is not limited thereto.

[0144] In the embodiments of this specification, when registering the specified location information provided by the near-field communication terminal, it is also necessary to determine whether the specified location information registered for the near-field communication terminal is consistent with the current location information of the near-field communication terminal. Only if they are consistent will the specified location information provided by the near-field communication terminal be registered, thereby improving the authenticity of the specified location information registered for the near-field communication terminal and ensuring the security of the subsequent resource allocation process.

[0145] Optionally, before generating and saving the association information between the near-field terminal identifier and the specified location information if the registration judgment result indicates that the current location information is consistent with the specified location information, the method may further include: obtaining the installation location information set by the resource provider for the near-field communication terminal; determining whether the specified location information is consistent with the specified installation location information; and generating and saving the association information between the near-field terminal identifier and the specified location information if the specified location information is consistent with the specified installation location information.

[0146] In the embodiments of this specification, the installation location information can be location point information or location range information, and there is no limitation on it.

[0147] In the embodiments of this specification, the rules for determining whether the installation location information is consistent with the specified location information can be referred to the rules for determining whether the specified location information is consistent with the first location information, and will not be repeated here.

[0148] In the embodiments described in this specification, the resource provider can pre-plan one or more specific installation location information for each near-field communication terminal and store this planning information in advance on the server. After receiving the specified location information sent by the near-field communication terminal, the server can query the pre-planned installation location information corresponding to the near-field communication terminal. Only after determining that the installation location information is consistent with the specified location information will the association information between the near-field terminal identifier and the specified location information be generated and saved. This can further improve the authenticity of the specified location information registered for the near-field communication terminal and thus ensure the security of the subsequent resource allocation process.

[0149] After generating and saving the association information between the near-field communication terminal identifier and the specified location information, it is also possible to determine whether the near-field communication terminal has been moved from the specified location, so as to avoid the resources being maliciously obtained.

[0150] Optionally, after generating and saving the association information between the near-field terminal identifier and the designated location information, the process may further include: receiving near-field terminal heartbeat information sent by the near-field communication terminal according to a preset period; the near-field terminal heartbeat information carrying the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal; determining whether the current location information is consistent with the designated location information to obtain a heartbeat determination result; if the heartbeat determination result indicates that the current location information is inconsistent with the designated location information, then canceling the association information between the near-field terminal identifier and the designated location information.

[0151] In the embodiments of this specification, the near-field terminal heartbeat information can be heartbeat information actively sent by the near-field communication terminal to the server according to a preset period. Alternatively, the server can send a near-field terminal heartbeat information acquisition command to the near-field communication terminal according to a preset period, and the near-field communication terminal responds to the near-field terminal heartbeat information acquisition command by sending near-field terminal heartbeat information to the server. The preset period can be 1 hour or other values, which are not limited thereto.

[0152] In practical applications, if no near-field terminal heartbeat information is received from the near-field communication terminal within a preset time period, the association information between the near-field terminal identifier generated for that near-field communication terminal and the specified location information is cancelled. The preset time period is greater than or equal to the duration corresponding to a preset period; the preset time period can be 2 hours or other values, without limitation.

[0153] In the embodiments of this specification, the current location information of the near-field communication terminal can be the location information collected based on the near-field communication terminal's own positioning function for its current location. Furthermore, the time interval between the collection time of the near-field communication terminal's current location information and the time when the server receives the near-field terminal's heartbeat information sent by the near-field communication terminal is less than a preset duration, which can be 5 minutes or other values, without limitation.

[0154] In the embodiments described in this specification, the current location information of the near-field communication terminal can be location point information or location range information, and there is no limitation on this.

[0155] In the embodiments of this specification, after the server obtains the near-field terminal heartbeat information sent by the near-field communication terminal, it can query the specified location information registered for the near-field terminal identifier based on the near-field terminal identifier carried in the heartbeat information, and then determine whether the queried specified location information is consistent with the current location information of the near-field communication terminal carried in the heartbeat information.

[0156] In the embodiments of this specification, the judgment rule for whether the specified location information is consistent with the current location information of the near-field communication terminal can refer to the judgment rule for whether the specified location information is consistent with the first location information, and will not be repeated here.

[0157] In the embodiments of this specification, if it is determined that the specified location information of the near-field communication terminal is consistent with the current location information of the near-field communication terminal, then the generation timestamp of the association information between the near-field terminal identifier and the specified location information generated for the near-field communication terminal is updated. If it is determined that the specified location information is inconsistent with the current location information of the near-field communication terminal, then the association information between the near-field terminal identifier and the specified location information generated for the near-field communication terminal is cancelled.

[0158] To enhance the security of resource distribution, the server can verify whether the user is actually located near the near-field communication terminal before sending resources to the user terminal.

[0159] Optionally, before sending the resource corresponding to the first resource type identifier to the user terminal, the method may further include: acquiring image information acquired by a first image acquisition device at the location of the near-field communication terminal; the first time interval between the first acquisition time of the image information acquisition and the request sending time of the user terminal sending the resource acquisition request is less than or equal to a preset first duration; and determining, based on the image information, whether there is a user within a first preset distance from the near-field communication terminal, and obtaining a first usage determination result.

[0160] Sending the resource corresponding to the first resource type identifier to the user terminal may specifically include: if the first usage judgment result indicates that there is a user within a first preset distance from the near-field communication terminal, then sending the resource corresponding to the first resource type identifier to the user terminal.

[0161] In the embodiments described in this specification, the first image acquisition device may actively send the acquired image information to the server simultaneously with or after the near-field communication terminal sends the second resource type identifier to the server. Alternatively, the server may send an image information acquisition command to the first image acquisition device, causing the first image acquisition device to send image information to the server in response to the image information acquisition command.

[0162] In the embodiments of this specification, the first image acquisition device may include any one of the following: an image acquisition device on a near-field communication terminal, an image acquisition device connected to the near-field communication terminal, or a completely independent image acquisition device (a camera next to the near-field communication terminal) not connected to the near-field communication terminal. If the first image acquisition device is not an image acquisition device on the near-field communication terminal, the distance between the first image acquisition device and the near-field communication terminal is less than a preset threshold. The preset threshold is used to reflect that the first image acquisition device can acquire images of the near-field communication terminal and users (if any) near the near-field communication terminal.

[0163] In the embodiments of this specification, the image information acquired by the first image acquisition device may include at least one of video information, image information, or animated image information. The image information may include a near-field communication terminal.

[0164] In the embodiments described in this specification, the first duration can be 10 seconds or other values, and there is no limitation thereto.

[0165] In this embodiment of the specification, existing image recognition technology can be used to identify whether a user exists within a first preset distance from the near-field communication terminal in the image information sent by the first image acquisition device. If a user exists, the resource corresponding to the first resource type identifier is sent to the user terminal; if no user exists, the resource corresponding to the resource type identifier is not sent to the user terminal. Furthermore, a reason for prohibiting the sending of resources to the user terminal can be returned, so that the user terminal can make corresponding adjustments based on the reason. The first preset distance can be 1 meter or other values, and is not limited thereto.

[0166] In the embodiments described in this specification, before sending resources to the user terminal, the server also needs to determine whether there is a user near the near-field communication terminal. If there is a user, the server will send resources to the user terminal, thereby improving the security of resource distribution.

[0167] To further enhance the security of resource allocation, after determining that there is a user near the near-field communication terminal, it can also be determined whether that user is the one currently requesting resources from the server.

[0168] Optionally, if the first determination result indicates that a user exists within a first preset distance from the near-field communication terminal, then sending the resource corresponding to the first resource type identifier to the user terminal may specifically include: sending a user action command to the user terminal; acquiring motion image information captured by the first image acquisition device for the target action performed by the user based on the user action command; determining whether the target action displayed in the motion image information matches the action indicated by the user action command; if the target action matches the action indicated by the user action command, then sending the resource corresponding to the first resource type identifier to the user terminal.

[0169] In practical applications, if it is determined that there is a user within a first preset distance from the near-field communication terminal, the resource corresponding to the first resource type identifier can be sent directly to the user terminal. This can reduce disturbance to the user, improve the user experience, and also improve the efficiency of resource allocation.

[0170] To facilitate subsequent verification of user resource collection, information about the surrounding environment when the user collects resources can also be recorded.

[0171] Optionally, the method may further include: sending an image acquisition command to a second image acquisition device located at the position indicated by the specified location information; and acquiring on-site image resources acquired by the second image acquisition device in response to the image acquisition command.

[0172] In the embodiments described in this specification, the location represented by the specified location information can be any location that includes the specified location information. In practical applications, taking a scenic area as an example, the specified location information can be any location within the scenic area, and the location represented by the specified location information can be the area covered by the scenic area.

[0173] In the embodiments described in this specification, the second image acquisition device and the first image acquisition device may be the same image acquisition device, or the second image acquisition device and the first image acquisition device may be different image acquisition devices, and there is no limitation on this.

[0174] In the embodiments of this specification, the on-site image resources acquired by the second image acquisition device may include at least one of video information resources, image information resources, or animated image information resources. In practical applications, the on-site image resources may be image resources of a near-field communication terminal corresponding to the specified location information, acquired for a scenic area. Specifically, taking a scenic area scene as an example, it may be image resources acquired for popular photo spots within the scenic area, where the specified location information corresponds to the location of the popular photo spot.

[0175] In practical applications, after the server receives a resource acquisition request from the user terminal requesting the resource corresponding to the first resource type identifier, such as before or after sending the resource corresponding to the first resource type identifier to the user terminal, the server can send an image acquisition command to the second image acquisition device to enable the second image acquisition device to acquire on-site image resources. There are no restrictions on this.

[0176] To enhance the user experience, the on-site image resources acquired by the second image acquisition device can also be sent to the user terminal.

[0177] Optionally, after acquiring the on-site image resources acquired by the second image acquisition device in response to the image acquisition command, the step may further include: sending the on-site image resources to the user terminal; the on-site image resources are used to display on the user terminal to the user.

[0178] In the embodiments described in this specification, the server may send on-site image resources to the user terminal at the same time as or after sending resources to the user terminal.

[0179] In the embodiments of this specification, in addition to sending the resources that the user wishes to receive to the user terminal, image resources containing on-site information of the user receiving resources can also be sent to the user terminal as a reward, thereby enhancing the user's sense of participation and experience in receiving resources.

[0180] To facilitate subsequent verification of on-site image resources, on-site image resources can also be stored based on the image acquisition time.

[0181] Optionally, after sending an image acquisition command to the second image acquisition device located at the position indicated by the specified location information, the process may further include: obtaining a second acquisition time for acquiring the on-site image resources; and storing the on-site image resources and the second acquisition time together.

[0182] In this embodiment, the on-site image resource can carry the second acquisition time of that image resource. For each on-site image resource, the image resource is associated with and stored in conjunction with the corresponding second acquisition time. Subsequently, the corresponding on-site image resource can be retrieved based on the second acquisition time.

[0183] In practical applications, the time information associated with the on-site image resources can be the time interval information that includes the second acquisition time of the on-site image resource. For example, if the second acquisition time is t1, the time interval information can be the time period from t0 to t2, where the time period from t0 to t2 includes t1. In this way, when the specific time of the second acquisition cannot be determined, the convenience and success rate of querying the corresponding on-site image resources can be improved.

[0184] In the process of resource distribution, in order to further enhance resource security, such as to stop losses in time in case of potential resource theft, compliance inspections can be carried out on the resources distributed to the server.

[0185] Optionally, after sending the resource corresponding to the first resource type identifier to the user terminal, the method may further include: acquiring image information acquired by a first image acquisition device at the location of the near-field communication terminal during the second acquisition time; determining, based on the image information, whether there is a user within a first preset distance from the near-field communication terminal, and obtaining a second usage judgment result; if the second usage judgment result indicates that there is no user within a first preset distance from the near-field communication terminal, generating a warning message; the warning message is used to indicate that there is a risk of resource being illegally acquired during the second acquisition time.

[0186] In this embodiment, the image information acquired by the first image acquisition device at the second acquisition time may include: image information acquired at the second acquisition time within a preset time interval including the second acquisition time.

[0187] In this embodiment, based on existing image recognition technology, it can identify whether a user exists within a first preset distance from the near-field communication terminal in the image information acquired by the first image acquisition device during the second acquisition time. If no user exists, an early warning message is generated and sent to the user terminal of the administrator managing the near-field communication terminal. The early warning message indicates a risk of unauthorized resource acquisition during the second acquisition time. If a user exists, compliance information is generated and sent to the administrator's user terminal.

[0188] In practical applications, if the image information acquired by the first image acquisition device at the location of the near-field communication terminal during the second acquisition time is not obtained, an early warning message is generated.

[0189] In this embodiment, by conducting compliance checks on the resources already allocated to the server, if a risk of unauthorized acquisition of resources is detected, the administrator can be notified in a timely manner to rectify the situation and reduce the losses of the resource issuer.

[0190] Optionally, the resources may include digital collections.

[0191] In this illustrative embodiment, the explanation of digital collectibles can be referred to the above explanation of digital collectibles, and will not be repeated here.

[0192] Based on and Figure 2 Following the same approach as the scheme shown, this specification also provides an information transmission method based on near-field communication. Figure 7This is a flowchart illustrating an information transmission method based on near-field communication provided in an embodiment of this specification. From a programming perspective, the execution entity of the process can be a program mounted on a near-field communication terminal. It is understood that this method can be executed by any device, equipment, platform, or cluster of devices with computing and processing capabilities.

[0193] like Figure 7 As shown, the process may include the following steps.

[0194] Step 702: Send the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication; the near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server.

[0195] In the embodiments described in this specification, the near-field communication terminal can send a near-field terminal identifier to the user terminal after establishing a near-field communication connection with the user terminal.

[0196] In the embodiments of this specification, the explanations of resource type identifiers and near-field communication terminal identifiers can be found in the above-described examples. Figure 2 The details of the process will not be repeated here.

[0197] Step 704: Obtain the resource type identifier from the user terminal.

[0198] In the embodiments of this specification, the resource type identifier can be an identifier sent by the user terminal to the near-field communication terminal after the user terminal establishes a near-field communication connection with the near-field communication terminal.

[0199] Step 706: Send the resource type identifier to the server so that the server can determine that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then send the resource corresponding to the resource type identifier to the user terminal.

[0200] In the embodiments described in this specification, after receiving a resource type identifier sent by a user terminal, the near-field communication terminal can send a resource type identifier to the server. After determining that the resource type identifier sent by the near-field communication terminal matches the resource type identifier sent by the user terminal, the server sends the resource corresponding to the resource type identifier to the user terminal.

[0201] Figure 7The method described above allows the near-field communication terminal to send the resource type identifier received from the user terminal to the server. The server will only send the resource to the user terminal after determining that the resource type identifier sent by the user terminal matches the resource type identifier sent by the near-field communication terminal. This can avoid the risk of cheating by users in the process of receiving resources, thereby improving the security of resource distribution and reducing the risk of resource loss for the resource distributor.

[0202] based on Figure 7 In addition to the method described herein, this specification also provides some improved implementation methods, which will be described below.

[0203] To facilitate resource allocation, near-field communication terminals can pre-register their designated location information with the server.

[0204] Optionally, before sending the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication, the process may further include: sending a near-field terminal registration request to the server; the near-field terminal registration request carrying the near-field terminal identifier of the near-field communication terminal and specified location information; the near-field terminal registration request being used to request the establishment of association information between the near-field terminal identifier and the specified location information.

[0205] In the embodiments described in this specification, the near-field terminal registration request can be a request generated by the near-field communication terminal to request the server to register the association between the near-field terminal identifier and the specified location information.

[0206] In the embodiments of this specification, after the near-field communication terminal is installed, it can send a near-field terminal registration request to the server. The near-field terminal registration request can carry the near-field terminal identifier and specified location information of the near-field communication terminal, so that after receiving the near-field terminal registration request sent by the near-field communication terminal, the server can respond to the registration request and generate association information between the near-field terminal identifier and the specified location information corresponding to the near-field communication terminal.

[0207] After generating and saving the association information between the near-field communication terminal identifier and the specified location information, it is also possible to verify whether the current location of the near-field communication terminal meets the requirements.

[0208] Optionally, after sending the near-field terminal registration request to the server, the process may further include: sending near-field terminal heartbeat information to the server according to a preset period; the near-field terminal heartbeat information carries the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal, so that the server can determine whether to cancel the association information between the near-field terminal identifier and the specified location information.

[0209] In the embodiments described in this specification, the near-field communication terminal can actively send near-field terminal heartbeat information to the server according to a preset period. Alternatively, after receiving a near-field terminal heartbeat information acquisition instruction sent by the server according to a preset period, the near-field communication terminal can send near-field terminal heartbeat information to the server in response to the heartbeat information acquisition instruction. The preset period can be 1 hour or other values, and is not limited thereto.

[0210] In the embodiments of this specification, the near-field terminal heartbeat information may carry the near-field terminal identifier and the current location information of the near-field communication terminal. This allows the server to determine the corresponding specified location information based on the near-field terminal identifier and compare the determined specified location information with the current location information of the near-field communication terminal. If the comparison result indicates that the specified location information matches the current location information of the near-field communication terminal, the generation timestamp of the association information between the near-field terminal identifier and the specified location information generated for the near-field communication terminal is updated. If the comparison result indicates that the specified location information does not match the current location information of the near-field communication terminal, the association information between the near-field terminal identifier and the specified location information generated for the near-field communication terminal is cancelled.

[0211] In the embodiments described in this specification, the current location of the near-field communication terminal is periodically checked, thereby avoiding the risk of malicious users moving the near-field communication terminal to other locations and improving the security of resource transmission.

[0212] Optionally, the resources may include digital collections.

[0213] Figure 8 The embodiments provided in this specification correspond to Figure 2 , Figure 6 as well as Figure 7 The diagram below illustrates the swimlane flow of the resource allocation method. The business execution flow of this resource allocation method may involve execution entities such as user terminals, near-field communication terminals, and servers.

[0214] like Figure 8 As shown, the process may include the following steps.

[0215] Step 802: The near-field communication terminal sends a near-field terminal registration request to the server.

[0216] In the embodiments described in this specification, the near-field terminal registration request carries the near-field terminal identifier and the specified location information of the near-field communication terminal.

[0217] Step 804: In response to the near-field terminal registration request, the server establishes and stores the association information between the near-field terminal identifier and the specified location information for the near-field communication terminal.

[0218] Step 806: The near-field communication terminal sends near-field terminal heartbeat information to the server.

[0219] In the embodiments described in this specification, the near-field terminal heartbeat information carries the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal.

[0220] Step 808: Based on the near-field terminal heartbeat information, the server determines whether the current location information of the near-field communication terminal is consistent with the specified location information, and obtains the heartbeat judgment result.

[0221] Step 810: If the heartbeat judgment result indicates that the current location information is inconsistent with the specified location information, then cancel the association information between the near-field terminal identifier and the specified location information.

[0222] Step 812: If the heartbeat judgment result indicates that the current location information is consistent with the specified location information, then update the generation timestamp information of the association information between the near-field terminal identifier generated for the near-field communication terminal and the specified location information.

[0223] Step 814: Obtain the user's triggered actions for the application on the user's terminal.

[0224] In the embodiments described in this specification, the application can be an application installed on the user's terminal for the user to obtain resources.

[0225] Step 816: In response to a triggering operation for the application, display a resource claim page to the user; the resource claim page contains at least one resource icon.

[0226] Step 818: Receive a trigger operation from the user on the icon representing the resource to be claimed by the user in at least one resource icon.

[0227] Step 820: Determine the resource type identifier corresponding to the icon targeted by the triggering operation as the resource type identifier to be claimed by the user.

[0228] Step 822: Based on near-field communication, the near-field communication terminal sends a near-field terminal identifier to the user terminal.

[0229] Step 824: The user terminal sends a resource type identifier to the near-field communication terminal.

[0230] Step 826: The near-field communication terminal sends a resource type identifier to the server.

[0231] Step 828: The user terminal sends the resource type identifier, near-field terminal identifier, and first location information to the server.

[0232] Step 830: Determine whether the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal, and whether the first location information of the user terminal is consistent with the specified location information of the near-field communication terminal.

[0233] Step 832: If the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal, and the first location information of the user terminal is also consistent with the specified location information of the near-field communication terminal, then optionally, image information acquired by the first image acquisition device at the location of the near-field communication terminal can be obtained.

[0234] Step 834: Based on the image information, determine whether there is a user within a first preset distance from the near-field communication terminal.

[0235] Step 836: If a user exists within a first preset distance from the near-field communication terminal, then send the resource corresponding to the resource type identifier to the user terminal.

[0236] Step 838: Optionally, an image acquisition command may also be sent to a second image acquisition device located at the position indicated by the specified location information.

[0237] Step 840: Obtain the on-site image resources acquired by the second image acquisition device in response to the image acquisition command.

[0238] Step 842: Send the on-site image resources to the user terminal.

[0239] Step 844: Associate and store the on-site image resources with the second acquisition time of acquiring the on-site image resources.

[0240] Step 846: Obtain image information acquired by the first image acquisition device at the location of the near-field communication terminal during the second acquisition time.

[0241] Step 848: Based on the image information, determine whether there is a user within a first preset distance from the near-field communication terminal.

[0242] Step 850: If there are no users within a first preset distance from the near-field communication terminal, generate a warning message.

[0243] In this embodiment of the specification, the warning information is used to indicate that there is a risk of resources being illegally acquired during the second data collection time. In practical applications, this warning information can be sent to terminal devices used by one or more parties, such as resource providers and application administrators.

[0244] In practical applications, steps 806, 808, 810, and 812 can be located at any stage after step 804, and there is no limitation on this. The time for sending the resource corresponding to the resource type identifier to the user terminal in step 836 can be the same as the time for sending the field image resource to the user terminal in step 842, and there is no limitation on this.

[0245] The various technical features in the above embodiments can be combined arbitrarily, as long as there is no conflict or contradiction between the combinations of features. However, due to space limitations, they have not been described one by one. Therefore, the arbitrary combination of various technical features in the above embodiments is also within the scope of this specification.

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

[0247] Figure 9 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of a resource acquisition device based on near-field communication.

[0248] like Figure 9 As shown, the device may include:

[0249] The user-side near-field communication module 902 is used to obtain the near-field terminal identifier of the near-field communication terminal located at a specified location via near-field communication; send the resource type identifier of the resource to be claimed by the user to the near-field communication terminal; the resource type identifier is used to be sent by the near-field communication terminal to the server.

[0250] The request sending module 904 is used to send a resource acquisition request to the server for requesting the resource corresponding to the resource type identifier and the near-field terminal identifier.

[0251] The resource receiving module 906 is used to receive the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

[0252] based on Figure 9 The embodiments of this specification also provide some improved implementations of the device, which are described below.

[0253] Optionally, the device may further include:

[0254] The location information acquisition module is used to acquire the current first location information of the user terminal.

[0255] A location information sending module is used to send the first location information to the server. The resource received by the user terminal from the server is a resource sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal, and that the first location information is consistent with the pre-registered designated location information of the near-field communication terminal.

[0256] Optionally, the device may further include:

[0257] The resource claiming operation receiving module is used to receive users' resource claiming operations.

[0258] The resource type identifier determination module is used to determine the resource type identifier of the resource to be claimed by the user in response to the resource claiming operation.

[0259] Optionally, the resources include digital collections.

[0260] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0261] The above is an illustrative scheme of a resource acquisition device based on near-field communication according to this embodiment. It should be noted that the technical solution of this resource acquisition device based on near-field communication and the technical solution of the resource acquisition method based on near-field communication described above belong to the same concept. For details not described in detail in the technical solution of the resource acquisition device based on near-field communication, please refer to the description of the technical solution of the resource acquisition method based on near-field communication described above.

[0262] Figure 10 The embodiments provided in this specification correspond to Figure 6 A schematic diagram of the structure of a resource sending device.

[0263] like Figure 10 As shown, the device may include:

[0264] The request receiving module 1002 is used to receive a resource acquisition request sent by a user terminal for requesting the resource corresponding to the first resource type identifier, as well as a near-field terminal identifier; the near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location.

[0265] Information acquisition module 1004 is used to acquire the second resource type identifier sent by the near-field communication terminal;

[0266] The judgment module 1006 is used to determine whether the first resource type identifier and the second resource type identifier are consistent, and to obtain the identifier judgment result.

[0267] The resource sending module 1008 is used to send the resource corresponding to the first resource type identifier to the user terminal if the identifier judgment result indicates that the first resource type identifier is consistent with the second resource type identifier.

[0268] based on Figure 10 The embodiments of this specification also provide some improved implementations of the device, which are described below.

[0269] Optionally, the device may further include:

[0270] The location information receiving module is used to receive first location information indicating the location of the user terminal.

[0271] The specified location information acquisition module is used to acquire specified location information that indicates the location of the near-field communication terminal.

[0272] The first location information determination module is used to determine whether the first location information is consistent with the specified location information, and to obtain a location determination result.

[0273] The resource sending module 1008 may specifically include:

[0274] The first resource sending unit is configured to send the resource corresponding to the first resource type identifier to the user terminal if the identifier judgment result indicates that the first resource type identifier is consistent with the second resource type identifier and the location judgment result indicates that the first location information is consistent with the specified location information.

[0275] Optionally, the device may further include:

[0276] The first registration request receiving module is used to receive a near-field terminal registration request sent by the near-field communication terminal; the near-field terminal registration request carries the near-field terminal identifier of the near-field communication terminal and the specified location information.

[0277] The first association information generation module is used to generate and save the association information between the near-field terminal identifier and the specified location information.

[0278] Optionally, the device may further include:

[0279] The second registration request receiving module is used to receive a near-field terminal registration request sent by the near-field communication terminal; the near-field terminal registration request carries the near-field terminal identifier of the near-field communication terminal, the location information of the near-field communication terminal, and the specified location information to be registered.

[0280] The second location information judgment module is used to determine whether the current location information is consistent with the specified location information, and to obtain the registration judgment result.

[0281] The second association information generation module is used to generate and save the association information between the near-field terminal identifier and the specified location information if the registration judgment result indicates that the location information is consistent with the specified location information.

[0282] Optionally, the device may further include:

[0283] The near-field terminal heartbeat information receiving module is used to receive near-field terminal heartbeat information sent by the near-field communication terminal according to a preset period; the near-field terminal heartbeat information carries the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal.

[0284] The third location information judgment module is used to determine whether the current location information is consistent with the specified location information, and to obtain the heartbeat judgment result.

[0285] The association information cancellation module is used to cancel the association information between the near-field terminal identifier and the specified location information if the heartbeat judgment result indicates that the current location information is inconsistent with the specified location information.

[0286] Optionally, the device may further include:

[0287] The first image information acquisition module is used to acquire image information acquired by the first image acquisition device at the location of the near-field communication terminal; the first time interval between the first acquisition time of acquiring the image information and the request sending time of the user terminal sending the resource acquisition request is less than or equal to a preset first duration.

[0288] The first user determination module is used to determine, based on the image information, whether there is a user within a first preset distance from the near-field communication terminal, and to obtain a first user determination result.

[0289] The resource sending module 1008 may specifically include:

[0290] The second resource sending unit is configured to send the resource corresponding to the first resource type identifier to the user terminal if the first usage judgment result indicates that there is a user within a first preset distance from the near-field communication terminal.

[0291] Optionally, the device may further include:

[0292] The image acquisition command sending module is used to send an image acquisition command to a second image acquisition device located at the position indicated by the specified location information.

[0293] The on-site image resource acquisition module is used to acquire on-site image resources acquired by the second image acquisition device in response to the image acquisition command.

[0294] Optionally, the device may further include:

[0295] The on-site image resource sending module is used to send the on-site image resources to the user terminal; the on-site image resources are used to be displayed on the user terminal.

[0296] Optionally, the device may further include:

[0297] The second acquisition time acquisition module is used to acquire the second acquisition time of the acquired scene image resources.

[0298] The storage module is used to store the on-site image resources and the second acquisition time together.

[0299] Optionally, the device may further include:

[0300] The second image information acquisition module is used to acquire image information acquired by the first image acquisition device at the location of the near-field communication terminal during the second acquisition time.

[0301] The second user determination module is used to determine, based on the image information, whether there is a user within a first preset distance from the near-field communication terminal, and to obtain a second user determination result.

[0302] The warning information generation module is used to generate warning information if the second usage judgment result indicates that there is no user within a first preset distance from the near-field communication terminal; the warning information is used to indicate that there is a risk of resources being illegally acquired during the second collection time.

[0303] Optionally, the resources include digital collections.

[0304] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0305] The above is an illustrative scheme of a resource sending device according to this embodiment. It should be noted that the technical solution of this resource sending device and the technical solution of the resource sending method described above belong to the same concept. For details not described in detail in the technical solution of the resource sending device, please refer to the description of the technical solution of the resource sending method described above.

[0306] Figure 11 The embodiments provided in this specification correspond to Figure 7 A schematic diagram of the structure of an information transmission device based on near-field communication.

[0307] like Figure 11 As shown, the device may include:

[0308] The device-side near-field communication module 1102 is used to send the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication; the near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server; and to obtain the resource type identifier from the user terminal.

[0309] The information sending module 1104 is used to send the resource type identifier to the server, so that the server can determine that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then send the resource corresponding to the resource type identifier to the user terminal.

[0310] based on Figure 11 The embodiments of this specification also provide some improved implementations of the device, which are described below.

[0311] Optionally, the device may further include:

[0312] The registration request sending module is used to send a near-field terminal registration request to the server; the near-field terminal registration request carries the near-field terminal identifier and specified location information of the near-field communication terminal; the near-field terminal registration request is used to request the establishment of association information between the near-field terminal identifier and the specified location information.

[0313] Optionally, the device may further include:

[0314] The near-field terminal heartbeat information sending module is used to send near-field terminal heartbeat information to the server according to a preset period. The near-field terminal heartbeat information carries the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal, so that the server can determine whether to cancel the association information between the near-field terminal identifier and the specified location information.

[0315] Optionally, the resources include digital collections.

[0316] It is understood that the modules mentioned above refer to computer programs or program segments used to perform one or more specific functions. Furthermore, the distinction between these modules does not imply that the actual program code must also be separate.

[0317] The above is an illustrative scheme of an information transmission device based on near-field communication according to this embodiment. It should be noted that the technical solution of this information transmission device based on near-field communication and the technical solution of the information transmission method based on near-field communication described above belong to the same concept. For details not described in detail in the technical solution of the information transmission device based on near-field communication, please refer to the description of the technical solution of the information transmission method based on near-field communication described above.

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

[0319] Figure 12 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a user terminal device. For example... Figure 12 As shown, device 1200 may include:

[0320] At least one processor 1220; and,

[0321] Memory 1210 communicatively connected to the at least one processor; wherein,

[0322] The memory 1210 stores instructions executable by the at least one processor 1220. These instructions, when executed by the at least one processor 1220, enable the at least one processor 1220 to: acquire a near-field terminal identifier of a near-field communication terminal located at a specified location via near-field communication; send a resource type identifier of a resource to be claimed by a user to the near-field communication terminal; the resource type identifier is sent by the near-field communication terminal to a server; send a resource acquisition request to the server requesting the resource corresponding to the resource type identifier, along with the near-field terminal identifier; and receive the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal matches the resource type identifier sent by the near-field communication terminal.

[0323] Figure 12 A structural block diagram of a user terminal device 1200 according to an embodiment of this application is shown. The components of the user terminal device 1200 include, but are not limited to, a memory 1210 and a processor 1220. The processor 1220 is connected to the memory 1210 via a bus 1230, and a database 1250 is used to store data.

[0324] User terminal equipment 1200 also includes access device 1240, which enables user terminal equipment 1200 to communicate via one or more networks 1260.

[0325] In one embodiment of this application, the aforementioned components of the user terminal device 1200 and Figure 12 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 12 The user terminal device structural block diagram shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0326] Specifically, when the processor 1220 executes the computer instructions, it implements the steps of the resource acquisition method based on near-field communication.

[0327] The above is an illustrative scheme of a user terminal device according to this embodiment. It should be noted that the technical solution of this user terminal device and the technical solution of the resource acquisition method based on near-field communication described above belong to the same concept. For details not described in detail in the technical solution of the user terminal device, please refer to the description of the technical solution of the resource acquisition method based on near-field communication described above.

[0328] Figure 13 The embodiments provided in this specification correspond to Figure 6 A schematic diagram of the structure of a server device. (Example) Figure 13 As shown, device 1300 may include:

[0329] At least one processor 1320; and,

[0330] Memory 1310 communicatively connected to the at least one processor; wherein,

[0331] The memory 1310 stores instructions executable by the at least one processor 1320. These instructions, when executed by the at least one processor 1320, enable the at least one processor 1320 to: receive a resource acquisition request sent by a user terminal for requesting resources corresponding to a first resource type identifier, and a near-field terminal identifier; the near-field terminal identifier being an identifier of a near-field communication terminal located at a specified location; acquire a second resource type identifier sent by the near-field communication terminal; determine whether the first resource type identifier and the second resource type identifier are consistent, obtaining an identifier determination result; if the identifier determination result indicates that the first resource type identifier and the second resource type identifier are consistent, then send the resource corresponding to the first resource type identifier to the user terminal.

[0332] Figure 13A structural block diagram of a server device 1300 according to an embodiment of this application is shown. The components of the server device 1300 include, but are not limited to, a memory 1310 and a processor 1320. The processor 1320 is connected to the memory 1310 via a bus 1330, and a database 1350 is used to store data.

[0333] Server device 1300 also includes access device 1340, which enables server device 1300 to communicate via one or more networks 1360.

[0334] In one embodiment of this application, the aforementioned components of the server device 1300 and Figure 13 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 13 The server device structure diagram shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0335] The processor 1320 implements the steps of the resource sending method when executing the computer instructions.

[0336] The above is an illustrative scheme of a server device according to this embodiment. It should be noted that the technical solution of this server device and the technical solution of the resource sending method described above belong to the same concept. For details not described in detail in the technical solution of the server device, please refer to the description of the technical solution of the resource sending method described above.

[0337] Figure 14 The embodiments provided in this specification correspond to Figure 7 A schematic diagram of the structure of a near-field communication device. (See diagram below.) Figure 14 As shown, device 1400 may include:

[0338] At least one processor 1420; and,

[0339] Memory 1410 communicatively connected to the at least one processor; wherein,

[0340] The memory 1410 stores instructions executable by the at least one processor 1420. These instructions, when executed by the at least one processor 1420, enable the at least one processor 1420 to: send a near-field communication terminal identifier to the user terminal via near-field communication; the near-field terminal identifier is used by the user terminal to send the near-field terminal identifier along with a resource type identifier of a resource to be claimed to the server; obtain the resource type identifier from the user terminal; and send the resource type identifier to the server, so that the server, after determining that the resource type identifier sent by the near-field communication terminal matches the resource type identifier sent by the user terminal, sends the resource corresponding to the resource type identifier to the user terminal.

[0341] Figure 14 A structural block diagram of a near-field communication device 1400 according to an embodiment of this application is shown. The components of the near-field communication device 1400 include, but are not limited to, a memory 1410 and a processor 1420. The processor 1420 is connected to the memory 1410 via a bus 1430, and a database 1450 is used to store data.

[0342] The near-field communication device 1400 also includes an access device 1440, which enables the near-field communication device 1400 to communicate via one or more networks 1460.

[0343] In one embodiment of this application, the aforementioned components of the near-field communication device 1400 and Figure 14 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 14 The block diagram of the near-field communication device shown is for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can add or replace other components as needed.

[0344] Specifically, when the processor 1420 executes the computer instructions, it implements the steps of the information transmission method based on near-field communication.

[0345] The above is an illustrative scheme of a near-field communication device according to this embodiment. It should be noted that the technical solution of this near-field communication device and the technical solution of the above-described information transmission method based on near-field communication belong to the same concept. For details not described in detail in the technical solution of the near-field communication device, please refer to the description of the technical solution of the above-described information transmission method based on near-field communication.

[0346] Figure 12 Network 1260, Figure 13 Network 1360 Figure 14Examples of network 1460 include a Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet. Access device 1440 may include one or more of any type of wired or wireless network interface (e.g., a network interface controller (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0347] User equipment 1200, server equipment 1300, and near-field communication equipment 1400 can all be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). Near-field communication equipment 1400 can also be a mobile or stationary server.

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

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

[0350] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

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

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

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

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

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

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

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

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

[0359] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

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

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

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

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

Claims

1. A resource acquisition method based on near-field communication, applied to a user terminal, comprising: Obtain the near-field terminal identifier of the near-field communication terminal located at a specified location through near-field communication; The resource type identifier of the resource to be claimed by the user is sent to the near-field communication terminal; the resource type identifier is used by the near-field communication terminal to send to the server. Send a resource acquisition request to the server for the resource type identifier and the near-field terminal identifier; Receive the resource corresponding to the resource type identifier sent by the server; The resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

2. The method as described in claim 1, further comprising, before receiving the resource corresponding to the resource type identifier sent by the server: Obtain the current first location information of the user terminal; Send the first location information to the server; The resources received by the user terminal from the server are resources sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal and that the first location information is consistent with the pre-registered designated location information of the near-field communication terminal.

3. The method as described in claim 1, further comprising, before obtaining the near-field terminal identifier of the near-field communication terminal located at a designated location via near-field communication: Receive resource request requests from users; In response to the resource claiming operation, the resource type identifier of the resource to be claimed by the user is determined.

4. The method according to any one of claims 1 to 3, wherein, The resources include digital collections.

5. A resource sending method, applied to a server, comprising: Receive a resource acquisition request sent by the user terminal for requesting the resource corresponding to the first resource type identifier, and a near-field terminal identifier; The near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location; Obtain the second resource type identifier sent by the near-field communication terminal; Determine whether the first resource type identifier and the second resource type identifier are consistent, and obtain the identifier determination result; If the identification result indicates that the first resource type identifier is consistent with the second resource type identifier, then the resource corresponding to the first resource type identifier is sent to the user terminal.

6. The method of claim 5, further comprising, before sending the resource corresponding to the first resource type identifier to the user terminal: Receive first location information indicating the location of the user terminal; Obtain specified location information representing the location of the near-field communication terminal; Determine whether the first location information is consistent with the specified location information to obtain a location determination result; If the identification determination result indicates that the first resource type identifier and the second resource type identifier are consistent, then the resource corresponding to the first resource type identifier is sent to the user terminal, specifically including: If the identification judgment result indicates that the first resource type identifier is consistent with the second resource type identifier and the location judgment result indicates that the first location information is consistent with the specified location information, then the resource corresponding to the first resource type identifier is sent to the user terminal.

7. The method of claim 6, further comprising, before obtaining the specified location information representing the location of the near-field communication terminal: Receive the near-field terminal registration request sent by the near-field communication terminal; The near-field terminal registration request carries the near-field terminal identifier and specified location information of the near-field communication terminal; Generate and save the association information between the near-field terminal identifier and the specified location information.

8. The method of claim 6, further comprising, before obtaining the specified location information representing the location of the near-field communication terminal: Receive the near-field terminal registration request sent by the near-field communication terminal; The near-field terminal registration request carries the near-field terminal identifier of the near-field communication terminal, the location information of the near-field communication terminal, and the specified location information to be registered; Determine whether the current location information is consistent with the specified location information to obtain the registration determination result; If the registration judgment result indicates that the location information is consistent with the specified location information, then the association information between the near-field terminal identifier and the specified location information is generated and saved.

9. The method of claim 7 or 8, further comprising: Receive near-field terminal heartbeat information sent by the near-field communication terminal according to a preset period; The near-field terminal heartbeat information carries the near-field terminal identifier of the near-field communication terminal and the current location information of the near-field communication terminal; Determine whether the current location information is consistent with the specified location information to obtain the heartbeat determination result; If the heartbeat determination result indicates that the current location information is inconsistent with the specified location information, then the association information between the near-field terminal identifier and the specified location information is cancelled.

10. The method of claim 5, further comprising, before sending the resource corresponding to the first resource type identifier to the user terminal: Acquire image information acquired by a first image acquisition device at the location of the near-field communication terminal; The first time interval between the first acquisition time of the image information acquisition and the request sending time of the user terminal sending the resource acquisition request is less than or equal to a preset first duration; Based on the image information, it is determined whether there is a user within a first preset distance from the near-field communication terminal, and a first usage determination result is obtained; Sending the resource corresponding to the first resource type identifier to the user terminal specifically includes: If the first usage judgment result indicates that there is a user within a first preset distance from the near-field communication terminal, then the resource corresponding to the first resource type identifier is sent to the user terminal.

11. The method of claim 5, further comprising: Send an image acquisition command to the second image acquisition device located at the position indicated by the specified location information; Acquire the on-site image resources acquired by the second image acquisition device in response to the image acquisition command.

12. The method of claim 11, further comprising, after acquiring the on-site image resources acquired by the second image acquisition device in response to the image acquisition command: Send the on-site image resources to the user terminal; The on-site image resources are used to display on the user's terminal.

13. The method of claim 11, further comprising, after sending an image acquisition command to a second image acquisition device located at the position indicated by the specified location information: The second acquisition time for acquiring the on-site image resources; The on-site image resources are stored in association with the second acquisition time.

14. The method of claim 13, further comprising, after sending the resource corresponding to the first resource type identifier to the user terminal: Obtain image information acquired by the first image acquisition device at the location of the near-field communication terminal during the second acquisition time; Based on the image information, it is determined whether there is a user within a first preset distance from the near-field communication terminal, and a second usage determination result is obtained; If the second judgment result indicates that there is no user within a first preset distance from the near-field communication terminal, then a warning message is generated; The warning information is used to indicate that there is a risk of resources being illegally acquired during the second data collection time.

15. The method according to any one of claims 5 to 14, wherein, The resources include digital collections.

16. A method for transmitting information based on near-field communication, applied to a near-field communication terminal, comprising: The near-field terminal identifier of the near-field communication terminal is sent to the user terminal via near-field communication. The near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server; Obtain the resource type identifier from the user terminal; The resource type identifier is sent to the server so that the server determines that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then sends the resource corresponding to the resource type identifier to the user terminal.

17. The method of claim 16, further comprising, before sending the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication: Send a near-field terminal registration request to the server; The near-field terminal registration request carries the near-field terminal identifier and specified location information of the near-field communication terminal; The near-field terminal registration request is used to request the establishment of an association between the near-field terminal identifier and the specified location information.

18. The method of claim 17, further comprising, after sending the near-field terminal registration request to the server: According to a preset cycle, near-field terminal heartbeat information is sent to the server; The near-field terminal heartbeat information carries the near-field terminal identifier and the current location information of the near-field communication terminal, so that the server can determine whether to cancel the association information between the near-field terminal identifier and the specified location information.

19. The method according to any one of claims 16 to 18, wherein, The resources include digital collections.

20. A resource acquisition device based on near-field communication, applied to a user terminal, comprising: The user-side near-field communication module is used to obtain the near-field terminal identifier of the near-field communication terminal located at a specified location through near-field communication. The resource type identifier of the resource to be claimed by the user is sent to the near-field communication terminal; the resource type identifier is used by the near-field communication terminal to send to the server. The request sending module is used to send a resource acquisition request to the server for requesting the resource corresponding to the resource type identifier and the near-field terminal identifier; A resource receiving module is used to receive the resource corresponding to the resource type identifier sent by the server; The resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

21. A resource sending device, applied to a server, comprising: The request receiving module is used to receive a resource acquisition request sent by the user terminal for requesting the resource corresponding to the first resource type identifier, as well as the near-field terminal identifier; The near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location; The information acquisition module is used to acquire the second resource type identifier sent by the near-field communication terminal; The judgment module is used to determine whether the first resource type identifier and the second resource type identifier are consistent, and to obtain the identifier judgment result; The resource sending module is used to send the resource corresponding to the first resource type identifier to the user terminal if the identifier judgment result indicates that the first resource type identifier is consistent with the second resource type identifier.

22. An information transmission device based on near-field communication, applied to a near-field communication terminal, comprising: The device-side near-field communication module is used to send the near-field terminal identifier of the near-field communication terminal to the user terminal via near-field communication. The near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server; Obtain the resource type identifier from the user terminal; The information sending module is used to send the resource type identifier to the server, so that the server can determine that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then send the resource corresponding to the resource type identifier to the user terminal.

23. A user terminal device, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: Obtain the near-field terminal identifier of the near-field communication terminal located at a specified location through near-field communication; The resource type identifier of the resource to be claimed by the user is sent to the near-field communication terminal; the resource type identifier is used by the near-field communication terminal to send to the server. Send a resource acquisition request to the server for the resource type identifier and the near-field terminal identifier; The server receives the resource corresponding to the resource type identifier sent by the server; the resource is sent by the server after determining that the resource type identifier sent by the user terminal is consistent with the resource type identifier sent by the near-field communication terminal.

24. A server, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The system receives a resource acquisition request sent by a user terminal, which requests a resource corresponding to a first resource type identifier, and a near-field terminal identifier; the near-field terminal identifier is the identifier of a near-field communication terminal located at a specified location. Obtain the second resource type identifier sent by the near-field communication terminal; Determine whether the first resource type identifier and the second resource type identifier are consistent, and obtain the identifier determination result; If the identification result indicates that the first resource type identifier is consistent with the second resource type identifier, then the resource corresponding to the first resource type identifier is sent to the user terminal.

25. A near-field communication device, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: The near-field terminal identifier of the near-field communication terminal is sent to the user terminal via near-field communication; the near-field terminal identifier is used by the user terminal to send the near-field terminal identifier together with the resource type identifier of the resource to be claimed by the user to the server. Obtain the resource type identifier from the user terminal; The resource type identifier is sent to the server so that the server determines that the resource type identifier sent by the near-field communication terminal is consistent with the resource type identifier sent by the user terminal, and then sends the resource corresponding to the resource type identifier to the user terminal.

Images