Service access processing method and apparatus based on near field communication

Abstract

The embodiment of the present specification provides a service access processing method and device based on near field communication, wherein the service access processing method based on near field communication comprises the following steps: in the process of accessing the service subprogram of the application program, calling the near field communication component to establish the near field communication connection with the merchant device, uploading the device interaction information to the server through the merchant device, receiving the application program access instruction transmitted by the merchant device, entering the application program to receive the service recommendation data of the service subprogram of the merchant accessed by the server and displaying, and after detecting the service access instruction for the service subprogram, entering the service subprogram based on the subprogram access address contained in the service recommendation data.

Description

[0001] This application is a divisional application of Chinese invention patent application No. 202410172286.5, filed on February 6, 2024, entitled "Service Access Processing Method and Apparatus Based on Near Field Communication". Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a service access processing method and apparatus based on near-field communication. Background Technology

[0003] With the continuous development of internet technology and the continuous improvement of software technology, more and more applications are starting to develop subroutines or mini-programs within the application to provide users with diversified software services. This allows users to obtain multiple software services within one application, improving software efficiency. However, as more and more applications add mini-programs, the size of various applications is also increasing, and the number of mini-programs within applications is also increasing. This has caused some inconvenience for users and also placed higher demands on application providers. Summary of the Invention

[0004] This specification provides one or more embodiments of a service access processing method based on near-field communication (NFC), applied to a user terminal. The method includes: invoking a NFC component to establish a NFC connection with a merchant device, so as to upload device interaction information to a server through the merchant device; receiving a program access instruction from the merchant device; entering the application in response to the program access instruction; receiving and displaying service recommendation data for accessing a merchant's service subroutine issued by the server; the merchant being accessed is determined based on the device interaction information; and, upon detecting a service access instruction for the service subroutine, entering the service subroutine based on the subroutine access address contained in the service recommendation data.

[0005] This specification provides one or more embodiments of another service access processing method based on near-field communication (NFC), applied to a server. The method includes: acquiring device interaction information uploaded by a merchant device, and sending an application access instruction to the merchant device for transmission to a user terminal. The application access instruction is transmitted via a NFC connection. The merchant is determined based on the device interaction information; the access address of the service subroutine of the merchant is queried; and service recommendation data for the service subroutine is generated based on the access address. The service recommendation data is then sent to the user terminal, causing the user terminal to display the service recommendation data and access the service subroutine after entering the application.

[0006] This specification provides one or more embodiments of a service access processing device based on near-field communication (NFC), running on a user terminal. The device includes: a NFC connection establishment module configured to invoke a NFC component to establish a NFC connection with a merchant device, so as to upload device interaction information to a server through the merchant device; a program access instruction receiving module configured to receive program access instructions from the application transmitted by the merchant device; a service recommendation data display module configured to respond to the program access instruction by entering the application, receiving and displaying service recommendation data for accessing a merchant's service subroutine issued by the server; the accessing merchant is determined based on the device interaction information; and a service subroutine access module configured to, upon detecting a service access instruction for the service subroutine, enter the service subroutine based on the subroutine access address contained in the service recommendation data.

[0007] This specification provides one or more embodiments of another service access processing apparatus based on near-field communication (NFC), running on a server. The apparatus includes: a program access instruction issuing module configured to acquire device interaction information uploaded by a merchant device and issue a program access instruction for an application to the merchant device for transmission to a user terminal. The program access instruction is transmitted via a NFC connection. A service recommendation data generation module configured to determine the accessing merchant based on the device interaction information, query the access address of the service subroutine of the accessing merchant, and generate service recommendation data for the service subroutine based on the access address. A service recommendation data issuing module configured to issue the service recommendation data to the user terminal, so that the user terminal displays the service recommendation data and enters the service subroutine after entering the application.

[0008] This specification provides one or more embodiments of a user terminal, including: a processor; and a memory configured to store computer-executable instructions, the processor executing the computer-executable instructions to implement the following process: invoking a near-field communication component to establish a near-field communication connection with a merchant device to upload device interaction information to a server through the merchant device; receiving a program access instruction from the merchant device; entering the application in response to the program access instruction; receiving and displaying service recommendation data for accessing a merchant's service subroutine issued by the server; the merchant being accessed is determined based on the device interaction information; and, upon detecting a service access instruction for the service subroutine, entering the service subroutine based on the subroutine access address contained in the service recommendation data.

[0009] This specification provides one or more embodiments of a server, including: a processor; and a memory configured to store computer-executable instructions, the processor executing the computer-executable instructions to implement the following process: acquiring device interaction information uploaded by a merchant device, and issuing a program access instruction for an application to the merchant device for transmission to a user terminal. The program access instruction is transmitted via a near-field communication connection. Based on the device interaction information, the accessing merchant is determined; the access address of the service subroutine of the accessing merchant is queried; and service recommendation data for the service subroutine is generated based on the access address. The service recommendation data is sent to the user terminal, so that the user terminal displays the service recommendation data and enters the service subroutine after entering the application.

[0010] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions that, when executed, perform the following process: Invoking a near-field communication component to establish a near-field communication connection with a merchant device to upload device interaction information to a server via the merchant device; Receiving a program access instruction from the merchant device; Entering the application in response to the program access instruction; Receiving and displaying service recommendation data for accessing a merchant's service subroutine issued by the server; The merchant being accessed is determined based on the device interaction information; Upon detecting a service access instruction for the service subroutine, entering the service subroutine based on the subroutine access address contained in the service recommendation data.

[0011] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions that, when executed, perform the following process: acquiring device interaction information uploaded by a merchant device and issuing a program access instruction for an application to the merchant device for transmission to a user terminal. The program access instruction is transmitted via a near-field communication connection. Based on the device interaction information, the merchant to be accessed is determined; the access address of the service subroutine of the merchant is queried; and service recommendation data for the service subroutine is generated based on the access address. The service recommendation data is then sent to the user terminal, causing the user terminal to display the service recommendation data and, upon entering the application, access the service subroutine. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more 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 specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 A schematic diagram illustrating the implementation environment of a service access processing method based on near-field communication provided for one or more embodiments of this specification; Figure 2 A flowchart of a service access processing method based on near-field communication provided for one or more embodiments of this specification; Figure 3(a) is a schematic diagram showing the first type of interactive animation frame provided in one or more embodiments of this specification; Figure 3(b) is a schematic diagram showing a second type of interactive animation frame provided in one or more embodiments of this specification; Figure 4 A schematic diagram of a recommendation window provided for one or more embodiments of this specification; Figure 5 A schematic diagram of a service recommendation window provided for one or more embodiments of this specification; Figure 6 A timing diagram illustrating a service access processing method based on near-field communication for a first interactive scenario, provided in one or more embodiments of this specification. Figure 7 A timing diagram illustrating a service access processing method based on near-field communication for a second interactive scenario, provided in one or more embodiments of this specification. Figure 8 Flowchart of another service access processing method based on near-field communication provided in one or more embodiments of this specification; Figure 9 A schematic diagram of an embodiment of a service access processing apparatus based on near-field communication provided for one or more embodiments of this specification; Figure 10 A schematic diagram of another embodiment of a service access processing apparatus based on near-field communication provided in one or more embodiments of this specification; Figure 11 A schematic diagram of the structure of a server provided for one or more embodiments of this specification; Figure 12 This is a schematic diagram of the structure of a user terminal provided for one or more embodiments of this specification. Detailed Implementation

[0013] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0014] The service access processing method based on near-field communication provided in this embodiment can be applied to the service subroutine access implementation environment. (Refer to...) Figure 1 The implementation environment includes at least server 101, which can be one or more servers, a server cluster consisting of several servers, or a cloud server of a cloud computing platform. Server 101 is used to issue program access commands to applications and to generate and distribute service recommendation data.

[0015] The implementation environment also includes at least a user terminal 102 and a merchant device 103. The user terminal 102 can be a smartphone, tablet, e-book reader, wearable device, or a device that interacts with information based on AR (Augmented Reality) / VR (Virtual Reality). The user terminal 102 is used to establish a near-field communication connection with the merchant device 103 to exchange and transmit device interaction information and program access commands. The merchant device 103 can be a POS (point of sale) machine equipped with near-field communication components. The merchant device 103 is used to upload device interaction information to the server 101, transmit program access commands to the user terminal 102, and establish a near-field communication connection with the user terminal 102.

[0016] The implementation environment may also include a merchant terminal 104, which can be connected to the merchant device 103. The merchant terminal 104 can work with the merchant device 103 to upload device interaction information to the server 101 and send program access commands to the user terminal 102. In addition, the merchant terminal 104 can also work with the merchant device 103 to generate and upload order information for product orders.

[0017] In this implementation environment, during service access, user terminal 102 first calls the near-field communication component to establish a near-field communication connection with merchant device 103, so as to send device interaction information to server 101 through merchant device 103. After receiving the device interaction information, server 101 generates a program access instruction for the application and sends it to merchant device 103. Merchant device 103 transmits it to user terminal 102 through near-field communication connection. Server 101 determines the merchant to be accessed based on the device interaction information, generates service recommendation data based on the access address of the service subroutine of the accessed merchant in the application, and sends it to user terminal 102. User terminal 102 receives and responds to the program access instruction to enter the application and displays the service recommendation data on the application's main page. After detecting the service access instruction for the service subroutine, it enters the service subroutine of the accessed merchant in the application based on the access address of the service subroutine contained in the service recommendation data.

[0018] This specification provides one or more embodiments of a service access processing method based on near-field communication, as follows: Reference Figure 2 The service access processing method based on near-field communication provided in this embodiment can be applied to user terminals, and specifically includes steps S202 to S208.

[0019] Step S202: Invoke the near-field communication component to establish a near-field communication connection with the merchant device, so as to upload device interaction information to the server through the merchant device.

[0020] In practical applications, an application may contain multiple service subroutines, mini-programs, or service modules. Users can access these service subroutines within the application to obtain the services they provide. Users can access each service subroutine by triggering interactions with their terminal within the application. However, some service subroutines require multiple triggering jumps, affecting user efficiency. To address this, this embodiment uses near-field communication (NFC) interaction with the merchant's device corresponding to the service subroutine to access the subroutine, avoiding the cumbersome operation of multiple jumps and improving user efficiency.

[0021] This embodiment sends service recommendation data for accessing a merchant's service subroutine to the user terminal after the user terminal enters the application. The user terminal then displays this service recommendation data. By using near-field communication (NFC) interaction, cumbersome page redirects are avoided. Instead, the application can be accessed and the service recommendation data for the subroutine displayed immediately after the NFC connection is established. Access to the service subroutine is then initiated after the service recommendation data is displayed, thus improving service access efficiency. Optionally, the merchant access is determined based on device interaction information.

[0022] In this embodiment, merchant device refers to terminal device belonging to a merchant. The terminal device can be a device that supports NFC (Near Field Communication) interaction. The merchant includes merchants with at least one store. The merchant can be a chain brand. Merchants can configure merchant devices in different stores. The identification information of the merchant device can be preset with fields that represent the merchant. The identification information can be configured in the near field communication tag. The user terminal can read the fields that represent the merchant by interacting with the merchant device through near field communication.

[0023] In practice, the user terminal approaches the merchant's device and activates the near-field communication (NFC) component to establish a NFC connection, enabling the merchant device to upload device interaction information to the server. Specifically, the user terminal can use its location information as the device interaction information, transmitting it to the merchant device via the NFC connection for uploading to the server; alternatively, the merchant device can use its device identification information as the device interaction information, uploading it to the server after establishing the NFC connection. Optionally, the application includes a payment application.

[0024] In this embodiment, device interaction information refers to information submitted to the server after interaction and transmission between the user terminal and the merchant device. This information can be device information of the user terminal and / or the merchant device itself, such as device identification information and terminal location information, or user information of the user to whom the user terminal belongs, such as user identity information and user account information. The server determines the merchant corresponding to the merchant device through the device interaction information. It should be noted that the device interaction information can be any one of the above-mentioned information, or a combination of multiple information, and this embodiment does not limit it. Optionally, the device interaction information includes: the merchant device's device identification information.

[0025] It should be noted that during the interaction between the user terminal and the merchant device, the interaction can be near-field communication (NFC) interaction. During NFC interaction, the user terminal can read the NFC tag of the merchant device to establish a NFC connection, or the merchant device can read the NFC tag of the user terminal to establish a NFC connection. This embodiment does not limit this.

[0026] In practical applications, users can access a merchant's service subroutine via page redirection. Based on this, when a user enters the application, or when the user enters the application's service page (i.e., the page in the application that records each merchant's service subroutine but has not yet performed near-field communication (NFC) interaction), the server generates a NFC interaction animation for the merchant based on the user's location information and sends it to the user's terminal for display. In one optional implementation of this embodiment, before establishing an NFC connection with the merchant's device by calling the NFC component, the following steps are also included: The application is accessed according to the user's access instruction, and the user's location information is sent to the server to determine the target merchant corresponding to the user's location information; Receive the interactive animation frames of the target merchant sent by the server and perform display processing.

[0027] Optionally, the server determines the store where the user terminal is located by querying stores that match the user's location information, renders the interactive animation frame according to the merchant's identification material of the store, and sends it to the user terminal.

[0028] Optionally, interactive animation frames are displayed after entering the application's service page.

[0029] As shown in Figure 3, the user enters the application by triggering the application identifier. After entering the application, the user terminal uploads the user's location information to the server. The server queries the store that matches the user's location information as the store where the user terminal is located, queries the merchant's logo material of the store to which the merchant belongs to render the interactive animation frame that interacts with the merchant's device, and sends it to the user terminal. The user terminal displays the interactive animation frames shown in Figure 3(a) to Figure 3(b) on the upper half of the screen.

[0030] In practical applications, there are situations where multiple services share the same user credential. For example, various passenger transport services need to share user identity credentials for entry and exit verification, and various medical services need to share user insurance credentials for medical payment verification. To address this, the server can generate interactive animation frames for the service type of the application's subroutine page and send them to the user terminal for display. In one optional implementation of this embodiment, before invoking the near-field communication component to establish a near-field communication connection with the merchant's device, the following steps are also included: Upon entering the application's sub-program page according to the user's access instruction, the service type of the service to which the sub-program page belongs is determined and sent to the server; Receive interactive animation frames for the service sent by the server and display them on the subroutine page.

[0031] Optionally, the interactive animation frame is obtained by rendering the identifier material based on the user credential corresponding to the service.

[0032] For example, when a user terminal enters a subprogram page of a medical institution based on a user access command, it sends the service type of the medical service to the server. The server then renders an interactive animation frame of the medical service based on the identifier material of the user's guarantee certificate corresponding to the service type of the medical service, and sends the interactive animation frame to the user terminal so that the user terminal can display it on the subprogram page of the medical service.

[0033] Step S204: Receive the application access instruction transmitted by the merchant device.

[0034] In practice, after receiving the device interaction information uploaded by the merchant's device, the server first generates an application access command and sends it back to the merchant's device. This allows the merchant's device to forward the access command to the user terminal, ensuring that the user terminal is within the application and can access the merchant's service subroutines. Specifically, the merchant's device receives the access command from the server and forwards it to the user terminal, thus keeping the user terminal within the application.

[0035] In practice, the merchant's device can transmit program access commands to the user terminal via NFC connection; alternatively, the program access commands can be transmitted via near-field communication connection.

[0036] Step S206: In response to the program access instruction, enter the application, receive and display the service recommendation data of the service subroutine of the access merchant issued by the server.

[0037] This embodiment sends service recommendation data for accessing a merchant's service subroutine to the user terminal after the user terminal enters the application. The user terminal then displays this service recommendation data. By using near-field communication (NFC) interaction, cumbersome page redirects are avoided. Instead, the application can be accessed and the service recommendation data for the subroutine displayed immediately after the NFC connection is established. Access to the service subroutine is then initiated after the service recommendation data is displayed, thus improving service access efficiency. Optionally, the merchant access is determined based on device interaction information.

[0038] In practice, the server first determines the merchant corresponding to the merchant's device based on the device interaction information, which is also the merchant accessed by the user. Based on the access address of the service subroutine of the accessed merchant in the application, the server generates service recommendation data and sends it to the user terminal. The user terminal responds to the program access instruction sent by the server, enters the application, receives the service recommendation data of the service subroutine of the accessed merchant sent by the server, and displays the service recommendation data.

[0039] In the specific execution process, based on the uploaded device interaction information, the server can generate service recommendation data for different device interaction information. For example, when the device interaction information is the identification information of a merchant device, the merchant corresponding to the merchant identification field in the identification information can be used as the accessing merchant to determine the merchant where the user is located and generate service recommendation data. In an optional implementation method provided in this embodiment, the accessing merchant is determined in the following way: Extract the merchant identifier field contained in the device identifier information, and query whether the merchant identifier field has a corresponding merchant; if yes, use the target merchant obtained by the query as the access merchant; if no, no processing is required.

[0040] Specifically, a merchant identifier field representing merchant information can be preset in the device identifier information of the merchant device. This field can be read by the user terminal and uploaded by the merchant device, or the merchant device can actively upload the merchant identifier field to the server. The server queries the data table recording merchant information for the merchant identifier field corresponding to the merchant. If the query finds a merchant, it indicates that the merchant device is bound to a merchant, and the found target merchant is used as the access merchant. If the query does not find a merchant, or the merchant identifier field is not read, it indicates that the merchant device is not bound to a merchant, and a query failure message can be returned to the user terminal.

[0041] Alternatively, when the device interaction information is the user terminal's location information, the merchant to which the store corresponding to the terminal location information belongs can be used as the accessing merchant to determine the merchant where the user is located and generate service recommendation data. In another optional implementation provided in this embodiment, the accessing merchant is determined in the following way: Query store information that matches the terminal location information, and query the target merchants corresponding to the stores based on the store information; Check if the target merchant has registered a terminal device. If so, designate the target merchant as the accessing merchant; otherwise, do nothing.

[0042] It should be noted that the merchant access information can also be determined by combining the merchant device's identification information with the user terminal's location information. For example: querying stores that match the terminal's location information to obtain the first merchant information; reading the merchant field contained in the merchant device's identification information to obtain the second merchant information corresponding to the merchant field; checking whether the first and second merchant information match; if they do, the store's merchant and / or the merchant corresponding to the merchant field is used as the accessed merchant; otherwise, no processing is required. Optionally, the device interaction information includes: the user terminal's location information. Optionally, the device interaction information includes: the merchant device's identification information.

[0043] Furthermore, there are situations where a user stays at one store for a period of time before moving to the next, during which the service page is continuously displayed, i.e., the interactive animation frames of the merchant belonging to the previous store are always shown. To address this, when the server generates the interactive animation frames for near-field communication based on the user's location information uploaded by the user's terminal, a consistency check can be performed between the merchant belonging to the store determined by the user's location information and the merchant determined by the merchant's device identification information. If the check fails, the merchant corresponding to the device identification information is taken as the accessing merchant. In one optional implementation of this embodiment, the accessing merchant is determined in the following way: Extract the device identification information of the merchant's device contained in the device interaction information, and query the service merchant corresponding to the device identification information; detect whether the service merchant is the same as the target merchant, and if not, use the service merchant as the access merchant.

[0044] When a user enters the service page of a service subroutine of a merchant within an application, since the user is already inside the application, they can enter the application without responding to the application access command. Instead, they can respond to the application access command by detecting whether they are already inside the application. After detecting that they are inside the application's service page, they render and display the service subroutine's recommendation window based on the recommendation window materials and access address contained in the service recommendation data. In one optional implementation of this embodiment, entering the application, receiving service recommendation data, and displaying it includes: Check whether the service page is displayed. If so, render the recommendation window of the service subroutine based on the recommendation window material included in the service recommendation data and the access address, and display it on the service page; if not, no action is required.

[0045] like Figure 4 As shown, the user terminal calls the rendering component to render the service subroutine's recommendation window based on the recommendation window materials contained in the service recommendation data and the access address of the service subroutine accessing the merchant, and displays it on the service page.

[0046] In addition, the recommendation window can also be rendered and displayed on the user terminal when the user terminal enters the application in response to the program access command. That is, even when the user terminal is not on the service page, the recommendation window of the service subroutine can be rendered and displayed on the service page based on the recommendation window material and access address included in the service recommendation data sent by the server.

[0047] In the specific execution process, the server can also obtain the merchant's activity data, such as promotional activities and gift activities, generate benefit recommendation data based on the activity data, and send it to the user terminal so that the user can be aware of the merchant's activities in a timely manner. Specifically, after rendering the interactive animation frame of the merchant to which the user terminal belongs and sending it to the user terminal, the server can obtain the merchant's recommended activity data, generate benefit recommendation data, and send this data to the user terminal to be displayed in the application's service page. In an optional implementation of this embodiment, after rendering the interactive animation frame and sending it to the user terminal, the server further includes: Obtain the recommendation activity data of the merchants to which the store belongs, and generate benefit recommendation data for the merchants to which the store belongs based on the recommendation activity data; The benefit recommendation data is sent to the user terminal so that the user terminal can display the benefit recommendation data on the service page.

[0048] As shown in Figure 3, the system obtains the recommended activity data of the merchants to which the user terminal belongs, generates the discount activity data of the merchants to which the store belongs based on the recommended activity data, and sends the discount activity data to the user terminal so that the user terminal can display the discount redemption interface 301(a) and 301(b) on the band of the service page, and the user can trigger the discount redemption interface to redeem the merchant coupon.

[0049] In addition, there are cases where the user is on the system's main page before engaging in near-field communication interaction. The user terminal can respond to the application's program access command to enter the application's main page, where service recommendation data can be displayed. For this, the server can render a service recommendation window based on the merchant's identifier and the access address of the service subroutine, using the rendered window parameters as service recommendation data to improve interaction efficiency. In one optional implementation of this embodiment, responding to the program access command to enter the application, receiving and displaying service recommendation data includes: The user is redirected from the system page to the main page according to the program access instruction, and a service recommendation window is generated and displayed based on the service window parameters contained in the service recommendation data.

[0050] Optionally, the service window parameters are obtained by rendering based on the merchant identification material of the accessed merchant and the access address.

[0051] Optionally, service recommendation data can be displayed on the application's main page.

[0052] Specifically, the server obtains the merchant identification material of the accessing merchant and the access address of the service subroutine of the accessing merchant. Based on the merchant identification material and the access address, it calls the rendering component to render the service recommendation window of the service subroutine. The service window parameters of the service recommendation window are sent to the user terminal as service recommendation data. The user terminal first jumps from the system page to the main page of the application based on the program access command. The service recommendation window is generated and displayed on the main page according to the service window parameters.

[0053] like Figure 5 As shown, the user terminal displays a service recommendation window on the main page of the payment application.

[0054] It should be noted that the method of rendering the service recommendation window by the server and using the service window parameters of the service recommendation window as service recommendation data can also be implemented when the user terminal is displaying service recommendation data on the application's service page. That is, the user terminal generates and displays the service recommendation window based on the service window parameters within the application's service page. This embodiment does not limit this. It should be noted that the service recommendation window can be a service recommendation window that is rendered and displayed by the user terminal based on the service recommendation data sent by the server.

[0055] In practical applications, there can be various service subroutines for accessing merchants, such as registration services, benefits services, and order placement services. To address this, the server can determine service recommendation data based on the user identity information contained in the device interaction information, thereby improving the availability of the NFC fast access service. In one optional implementation provided in this embodiment, the service recommendation data is generated in the following manner: Extract the user identity information contained in the device interaction information, and detect whether the user identity information matches the registered user information of the accessed merchant; if yes, generate the service recommendation data based on the access address of the rights and benefits service subroutine; if no, generate the service recommendation data based on the access address of the registration service subroutine.

[0056] Optionally, the service subroutines include: a registration service subroutine and / or a rights service subroutine. The server can determine service recommendation data based on the user identity information contained in the device interaction information.

[0057] Specifically, the user identity information contained in the device interaction information is extracted, and it is checked whether the user identity information matches the registered user information of the registered users in the merchant's registered user database. If they match, it indicates that the user is a registered user of the merchant, and service recommendation data is generated based on the access address of the merchant's rights subroutine. If they do not match, it indicates that the user is not a registered user of the merchant, and service recommendation data is generated based on the access address of the merchant's registration subroutine. Here, the user identity information can be an identifier code representing the user, and the rights subroutine can be a membership rights subroutine.

[0058] It should be noted that the method of determining access service recommendation data based on user identity information provided above can be implemented not only when the service recommendation data is displayed on the main page of the application, but also when the interactive animation frames are displayed on the service page of the application. That is, it can be implemented when the service recommendation data is displayed on the service page of the application. This embodiment does not limit it here.

[0059] Step S208: After detecting a service access instruction for the service subroutine, enter the service subroutine based on the subroutine access address contained in the service recommendation data.

[0060] This embodiment avoids the cumbersome page redirection process and improves service access efficiency by using near-field communication interaction. In specific implementation, after detecting a service access instruction for a service subroutine, the service subroutine is accessed according to the access address of the service subroutine of the accessing merchant contained in the service recommendation data.

[0061] In the specific execution process, the access command of the service subroutine can be triggered by the user in response to the service recommendation data displayed on the user terminal. For example, the user can trigger the access interface of the service recommendation window displayed on the user terminal, which will then trigger the access command of the service subroutine. Alternatively, the user can actively trigger the access interface of the service subroutine after the display time of the service recommendation window expires. Optionally, the service access command can be triggered after the user triggers the service access interface contained in the service recommendation window, or after the display time of the service recommendation window expires.

[0062] like Figure 4 and Figure 5 As shown, the user access command can be triggered by the user triggering the access interface 401 of the service recommendation window displayed on the application's service page or the access interface 501 of the service recommendation window displayed on the application's main page, or it can be triggered after the display time of the service recommendation window on the application's service page or the service recommendation window on the application's main page has elapsed.

[0063] It should be noted that the service recommendation window can be a service recommendation window that is rendered and displayed by the user terminal based on the service recommendation data sent by the server, or it can be a service recommendation window that is rendered and generated by the server and then sent to the user terminal. This embodiment does not limit this; that is, the service recommendation windows generated and displayed by the user terminal in the above two ways can be triggered by the above two service access commands. This embodiment will not elaborate on this further.

[0064] In practical applications, after accessing the merchant's service subroutine, users can perform operations such as ordering, placing orders, and shopping, and may make payments. Since near-field communication (NFC) interaction has already been performed, user account information can be uploaded to the server as device interaction information during NFC interaction. This allows the merchant's device to upload the user's payment instructions and order information to the server during payment, improving payment efficiency. In one optional implementation of this embodiment, it further includes: Obtain the user's payment instruction and transmit it to the merchant device to submit the order information to the server through the merchant device; Receive payment completion information from the server and display it on the service page of the service subroutine.

[0065] Optionally, the server generates a payment order based on the order information, and after detecting the user's payment instruction, processes the payment order based on the user account information corresponding to the user account information contained in the device interaction information.

[0066] Optionally, the user payment instruction is transmitted via a near-field communication connection. Optionally, the device interaction information includes: user account information.

[0067] Specifically, the user terminal receives the user's payment instruction and transmits it to the merchant device. The merchant device then obtains the order information for the corresponding product order and submits the order information and the user's payment instruction to the server. Upon receiving the user's payment instruction, the server generates a payment order based on the order information and processes the payment order based on the user account information contained in the device interaction information, generating payment completion information and sending it to the user terminal. After receiving the payment completion information, the user terminal displays it on the service page of the service subroutine. The service subroutine can be a shopping subroutine or a food ordering subroutine, and the merchant device can be a merchant POS terminal with wireless communication and near-field communication interaction capabilities.

[0068] Based on the above-mentioned generation of interactive animation frames according to the service type of the service to which the application's subroutine page belongs, after entering the service subroutine of the merchant, the user's credential identifier can also be used as a near-field communication tag for secondary near-field communication interaction. For example, after entering the service subroutine of a medical institution, the user's insurance credential identifier can be used as a near-field communication tag to perform secondary near-field communication interaction with the medical institution's near-field communication equipment for payment processing. Alternatively, after entering the ride-hailing service, the user's identity credential identifier can be used as a near-field communication tag to perform secondary near-field communication interaction with the station's entry and exit verification equipment for identity verification processing. In an optional implementation of this embodiment, it further includes: Invoke the near-field communication component and use the credential identifier of the user credential as the near-field communication tag; A secondary near-field communication connection is established between the near-field communication tag and the merchant's device for identity verification and / or payment processing.

[0069] Furthermore, the credential identifier of the user credential may be stored within the application. The user terminal can first call the application's credential interface to obtain the credential identifier of the user credential, so as to use the credential identifier of the user credential within the service subroutine of accessing the merchant; optionally, the credential identifier is obtained by calling back the application's credential interface. It should be noted that when the interactive animation frame is generated based on the service type of the service to which the application's subroutine page belongs, that is, when the interactive animation frame is generated based on the identifier material of the user credential, the accessing merchant is a service merchant that provides various services, such as: transportation service merchants, medical service merchants, accommodation service merchants, etc., used for identity verification and / or payment processing through the user credential.

[0070] In summary, the one or more service access processing methods based on near-field communication provided in this embodiment can be applied to user terminals. During the service access process, a near-field communication component is invoked to establish a near-field communication connection with the merchant device, so that the merchant device can upload device interaction information to the server. After the server completes the processing, it receives the application access instruction transmitted by the merchant device, enters the application in response to the application access instruction, receives and displays the server recommendation data for accessing the merchant's service subroutine issued by the server, and enters the service subroutine based on the subroutine access address contained in the service recommendation data after detecting the service access instruction for the service subroutine, thereby improving the service access efficiency. Before engaging in near-field communication (NFC) interaction, interactive animation frames illustrating the NFC interaction can be generated based on the user's location information and displayed on the application's service page to remind the user that NFC interaction is available for quick access to services, thus enhancing the user's perception of NFC interaction.

[0071] The above-described implementation process of a service access processing method based on near-field communication can be executed by a user terminal. The following method embodiment provides another implementation process of a service access processing method based on near-field communication, which can be executed by a server. The two can cooperate with each other during execution. Therefore, when reading the above implementation process, you can refer to the corresponding content of the following other method embodiment based on near-field communication. Similarly, when reading the following other method embodiment based on near-field communication, you can also refer to the corresponding content of the above method embodiment.

[0072] The following description uses the application of a service access processing method based on near-field communication provided in this embodiment in a first interactive scenario as an example to further illustrate the service access processing method based on near-field communication provided in this embodiment. See [link to documentation]. Figure 6 The service access processing method based on near-field communication, applied to the first interaction scenario, specifically includes the following steps.

[0073] Step S602: Invoke the near-field communication component to establish a near-field communication connection with the merchant device, so as to upload device interaction information to the server through the merchant device.

[0074] Optionally, device interaction information includes: device identification information of the merchant's device.

[0075] Step S616: Receive the application access instruction transmitted by the merchant's device, and receive the service window parameters of the service recommendation window sent by the server.

[0076] Optionally, program access commands are transmitted via a near-field communication connection.

[0077] Step S618: In response to the program access command, enter the application from the system page, generate a service recommendation window based on the service window parameters, and display it.

[0078] Optionally, a service recommendation window can be displayed on the application's main page.

[0079] Step S620: After the display time of the service recommendation window expires, the service program triggers a service access instruction and enters the service subroutine based on the subroutine access address contained in the service window parameters.

[0080] In this embodiment, steps S602 and S616 to S620 are executed by the user terminal. It should be noted that the steps S602 and S616 to S620 executed by the user terminal can cooperate with steps S604 to S614 executed by the server in the following embodiment. Therefore, when reading this embodiment, please refer to the corresponding content of steps S604 to S614 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of steps S602 and S616 to S620 provided in this embodiment.

[0081] The following description uses the application of a service access processing method based on near-field communication provided in this embodiment in a second interaction scenario as an example to further illustrate the service access processing method based on near-field communication provided in this embodiment. See [link to documentation]. Figure 7 The service access processing method based on near-field communication, applied to the second interaction scenario, specifically includes the following steps.

[0082] Step S702: According to the user's access instruction, enter the application's service page and send the user's location information to the server to determine the target merchant corresponding to the user's location information.

[0083] Step S708: Receive the interactive animation frames of the target merchant sent by the server and perform display processing.

[0084] Optionally, interactive animation frames are displayed on the application's service page.

[0085] Step S710: Invoke the near-field communication component to establish a near-field communication connection with the merchant device, so as to upload device interaction information to the server through the merchant device.

[0086] Step S722: Check whether the application's service page is displayed; If so, proceed to step S724; If not, no action needs to be taken.

[0087] Step S724: Receive service recommendation data sent by the server, render the recommendation window based on the recommendation window materials contained in the service recommendation data and the access address of the service subroutine of the accessing merchant, and display it on the service page.

[0088] Step S726: After detecting that the user has triggered the access interface of the recommendation window to submit a service access instruction, the service subroutine is entered based on the access address of the service subroutine of the accessing merchant.

[0089] Steps S702, S708 to S710, and S722 to S726 provided in this embodiment are executed by the user terminal. It should be noted that the steps S702, S708 to S710, and S722 to S726 executed by the user terminal can cooperate with steps S704 to S706 and S712 to S720 executed by the server in the following embodiment during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S704 to S706 and S712 to S720 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of steps S702, S708 to S710, and S722 to S726 provided in this embodiment.

[0090] One or more embodiments of another service access processing method based on near-field communication provided in this specification are as follows: Reference Figure 8 The service access processing method based on near-field communication provided in this embodiment can be applied to a server, and specifically includes steps S802 to S806.

[0091] Step S802: Obtain device interaction information uploaded by the merchant device, and send a program access instruction for the application to the merchant device for transmission to the user terminal.

[0092] In practical applications, an application may contain multiple service subroutines, mini-programs, or service modules. Users can access these service subroutines within the application to obtain the services they provide. Users can access each service subroutine by triggering interactions with their terminal within the application. However, some service subroutines require multiple triggering jumps, affecting user efficiency. To address this, this embodiment uses near-field communication (NFC) interaction with the merchant's device corresponding to the service subroutine to access the subroutine, avoiding the cumbersome operation of multiple jumps and improving user efficiency.

[0093] This embodiment sends service recommendation data for accessing a merchant's service subroutine to the user terminal after the user terminal enters the application. The user terminal then displays this service recommendation data. By using near-field communication (NFC) interaction, cumbersome page redirects are avoided. Instead, the application can be accessed and the service recommendation data for the subroutine displayed immediately after the NFC connection is established. Access to the service subroutine is then initiated after the service recommendation data is displayed, thus improving service access efficiency. Optionally, the merchant access is determined based on device interaction information.

[0094] In this embodiment, merchant device refers to terminal device belonging to a merchant. The terminal device can be a device that supports near-field communication interaction. The merchant includes a merchant with at least one store. The merchant can be a chain brand. Merchants can configure merchant devices in different stores. The identification information of the merchant device can be preset with fields that represent the merchant. The identification information can be configured in the near-field communication tag. The user terminal can read the fields that represent the merchant by interacting with the merchant device through near-field communication.

[0095] In practice, the user terminal approaches the merchant's device and uses the near-field communication (NFC) component to establish a NFC connection, allowing the merchant's device to upload device interaction information to the server. Upon receiving this information, the server sends an application access command to the merchant's device for transmission to the user terminal. The user terminal then responds to the server's access command and enters the application.

[0096] Specifically, the user terminal can use its location information as device interaction information, transmitting it to the merchant device via a near-field communication (NFC) connection, so that the merchant device can upload it to the server; alternatively, the merchant device can use its device identification information as device interaction information, uploading the device identification information to the server after establishing a NFC connection. Optionally, the application includes a payment application.

[0097] In this embodiment, device interaction information refers to information submitted to the server after interaction and transmission between the user terminal and the merchant device. This information can be device information of the user terminal and / or the merchant device itself, such as device identification information and terminal location information, or user information of the user to whom the user terminal belongs, such as user identity information and user account information. The server determines the merchant corresponding to the merchant device through the device interaction information. It should be noted that the device interaction information can be any one of the above-mentioned information, or a combination of multiple information, and this embodiment does not limit it. Optionally, the device interaction information includes: the merchant device's device identification information.

[0098] It should be noted that during the interaction between the user terminal and the merchant device, the interaction can be near-field communication (NFC) interaction. During NFC interaction, the user terminal can read the NFC tag of the merchant device to establish a NFC connection, or the merchant device can read the NFC tag of the user terminal to establish a NFC connection. This embodiment does not limit this.

[0099] In practical applications, users can access a merchant's service subroutine via page redirection. Based on this, when a user enters the application, or when the user enters the application's service page (i.e., the page in the application that records each merchant's service subroutine but has not yet performed near-field communication (NFC) interaction), the server generates a NFC interaction animation for the merchant based on the user's location information and sends it to the user's terminal for display. In one optional implementation of this embodiment, before establishing an NFC connection with the merchant's device by calling the NFC component, the following steps are also included: The application is accessed according to the user's access instruction, and the user's location information is sent to the server to determine the target merchant corresponding to the user's location information; Receive the interactive animation frames of the target merchant sent by the server and perform display processing.

[0100] Optionally, the server determines the store where the user terminal is located by querying stores that match the user's location information, renders the interactive animation frame according to the merchant's identification material of the store, and sends it to the user terminal.

[0101] Optionally, interactive animation frames are displayed after entering the application's service page.

[0102] As shown in Figure 3, the user enters the application by triggering the application identifier. After entering the application, the user terminal uploads the user's location information to the server. The server queries the store that matches the user's location information as the store where the user terminal is located, queries the merchant's identifier material of the store to which the merchant belongs to render the interactive animation frame that interacts with the merchant's device, and sends it to the user terminal. The user terminal displays the interactive animation frames shown in Figure 3(a) to Figure 3(b).

[0103] In practical applications, there are situations where multiple services share the same user credential. For example, various passenger transport services need to share user identity credentials for entry and exit verification, and various medical services need to share user insurance credentials for medical payment verification. To address this, the server can generate interactive animation frames for the service type of the application's subroutine page and send them to the user terminal for display. In one optional implementation of this embodiment, before invoking the near-field communication component to establish a near-field communication connection with the merchant's device, the following steps are also included: Upon entering the application's sub-program page according to the user's access instruction, the service type of the service to which the sub-program page belongs is determined and sent to the server; Receive interactive animation frames for the service sent by the server and display them on the subroutine page.

[0104] Optionally, the interactive animation frame is obtained by rendering the identifier material based on the user credential corresponding to the service.

[0105] For example, when a user terminal enters a subprogram page of a medical institution based on a user access command, it sends the service type of the medical service to the server. The server then renders an interactive animation frame of the medical service based on the identifier material of the user's guarantee certificate corresponding to the service type of the medical service, and sends the interactive animation frame to the user terminal so that the user terminal can display it on the subprogram page of the medical service.

[0106] Step S804: Determine the accessing merchant based on the device interaction information, query the access address of the service subroutine of the accessing merchant, and generate service recommendation data for the service subroutine based on the access address.

[0107] This embodiment sends service recommendation data for accessing a merchant's service subroutine to the user terminal after the user terminal enters the application. The user terminal then displays this service recommendation data. By using near-field communication (NFC) interaction, cumbersome page redirects are avoided. Instead, the application can be accessed and the service recommendation data for the subroutine displayed immediately after the NFC connection is established. Access to the service subroutine is then initiated after the service recommendation data is displayed, thus improving service access efficiency. Optionally, the merchant access is determined based on device interaction information.

[0108] In practice, the server first determines the merchant corresponding to the merchant's device based on the device interaction information, which is also the merchant accessed by the user. Based on the access address of the service subroutine of the accessed merchant in the application, the server generates service recommendation data and sends it to the user terminal. The user terminal responds to the program access instruction sent by the server, enters the application, receives the service recommendation data of the service subroutine of the accessed merchant sent by the server, and displays the service recommendation data.

[0109] In the specific execution process, based on the uploaded device interaction information, the server can generate service recommendation data for different device interaction information. For example, when the device interaction information is the identification information of a merchant device, the merchant corresponding to the merchant identification field in the identification information can be used as the accessing merchant to determine the merchant where the user is located and generate service recommendation data. In an optional implementation method provided in this embodiment, the accessing merchant is determined in the following way: Extract the merchant identifier field contained in the device identifier information, and query whether the merchant identifier field has a corresponding merchant; if yes, use the target merchant obtained by the query as the access merchant; if no, no processing is required.

[0110] Specifically, a merchant identifier field representing merchant information can be preset in the device identifier information of the merchant device. This field can be read by the user terminal and uploaded by the merchant device, or the merchant device can actively upload the merchant identifier field to the server. The server queries the data table recording merchant information for the merchant identifier field corresponding to the merchant. If the query finds a merchant, it indicates that the merchant device is bound to a merchant, and the found target merchant is used as the access merchant. If the query does not find a merchant, or the merchant identifier field is not read, it indicates that the merchant device is not bound to a merchant, and a query failure message can be returned to the user terminal.

[0111] Alternatively, when the device interaction information is the user terminal's location information, the merchant to which the store corresponding to the terminal location information belongs can be used as the accessing merchant to determine the merchant where the user is located and generate service recommendation data. In another optional implementation provided in this embodiment, the accessing merchant is determined in the following way: Query store information that matches the terminal location information, and query the target merchants corresponding to the stores based on the store information; Check if the target merchant has registered a terminal device. If so, designate the target merchant as the accessing merchant; otherwise, do nothing.

[0112] It should be noted that the merchant to be accessed can also be determined by the merchant's device identification information and the user's terminal location information. For example: query the store that matches the terminal location information and obtain the first merchant information of the store; read the merchant field contained in the device identification information of the merchant device and obtain the second merchant information of the merchant corresponding to the merchant field; check whether the first merchant information and the second merchant information match. If they match, the store's merchant and / or the merchant corresponding to the merchant field is used as the accessed merchant. If not, no processing is required.

[0113] Furthermore, there are situations where a user stays at one store for a period of time before moving to the next, during which the service page is continuously displayed, i.e., the interactive animation frames of the merchant belonging to the previous store are always shown. To address this, when the server generates the interactive animation frames for near-field communication based on the user's location information uploaded by the user's terminal, a consistency check can be performed between the merchant belonging to the store determined by the user's location information and the merchant determined by the merchant's device identification information. If the check fails, the merchant corresponding to the device identification information is taken as the accessing merchant. In one optional implementation of this embodiment, the accessing merchant is determined in the following way: Extract the device identification information of the merchant's device contained in the device interaction information, and query the service merchant corresponding to the device identification information; detect whether the service merchant is the same as the target merchant, and if not, use the service merchant as the access merchant.

[0114] In the specific execution process, the server can also obtain the merchant's activity data, such as promotional activities and gift activities, generate benefit recommendation data based on the activity data, and send it to the user terminal so that the user can be aware of the merchant's activities in a timely manner. Specifically, after rendering the interactive animation frame of the merchant to which the user terminal belongs and sending it to the user terminal, the server can obtain the merchant's recommended activity data, generate benefit recommendation data, and send this data to the user terminal to be displayed in the application's service page. In an optional implementation of this embodiment, after rendering the interactive animation frame and sending it to the user terminal, the server further includes: Obtain the recommendation activity data of the merchants to which the store belongs, and generate benefit recommendation data for the merchants to which the store belongs based on the recommendation activity data; The benefit recommendation data is sent to the user terminal so that the user terminal can display the benefit recommendation data on the service page.

[0115] As shown in Figure 3, the system obtains the recommended activity data of the merchants to which the user terminal belongs, generates the discount activity data of the merchants to which the store belongs based on the recommended activity data, and sends the discount activity data to the user terminal so that the user terminal can display the discount claim interface 301(a) and 301(b) on the band of the service page. The user can trigger the discount claim interface 301(a) and 301(b) to claim the merchant coupon.

[0116] In practical applications, there can be various service subroutines for accessing merchants, such as registration services, benefits services, and order placement services. In this regard, the server can determine service recommendation data based on the user identity information contained in the device interaction information. In one optional implementation provided in this embodiment, the service recommendation data is generated in the following way: Extract the user identity information contained in the device interaction information, and detect whether the user identity information matches the registered user information of the accessed merchant; if yes, generate the service recommendation data based on the access address of the rights and benefits service subroutine; if no, generate the service recommendation data based on the access address of the registration service subroutine.

[0117] Optionally, the service subroutines include: a registration service subroutine and / or a rights service subroutine.

[0118] Specifically, the user identity information contained in the device interaction information is extracted, and it is checked whether the user identity information matches the registered user information of the registered users in the merchant's registered user database. If they match, it indicates that the user is a registered user of the merchant, and service recommendation data is generated based on the access address of the merchant's rights subroutine. If they do not match, it indicates that the user is not a registered user of the merchant, and service recommendation data is generated based on the access address of the merchant's registration subroutine. Here, the user identity information can be an identifier code representing the user, and the rights subroutine can be a membership rights subroutine.

[0119] It should be noted that the method of determining access service recommendation data based on user identity information provided above can be implemented not only when the service recommendation data is displayed on the main page of the application, but also when the interactive animation frames are displayed on the service page of the application. That is, it can be implemented when the service recommendation data is displayed on the service page of the application. This embodiment does not limit it here.

[0120] Step S806: Send the service recommendation data to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine after entering the application.

[0121] This embodiment avoids the cumbersome page navigation process and improves service access efficiency by using near-field communication interaction. In specific implementation, the generated service recommendation data is sent to the user terminal. After receiving the service recommendation data, the user terminal displays the service recommendation data and, upon detecting a service access command, enters the service subroutine of the access merchant within the application.

[0122] When a user enters the service page of a service subroutine of a merchant within an application, since the user is already inside the application, they can enter the application without responding to the application access command. Instead, they can respond to the application access command by detecting whether they are already inside the application. After detecting that they are inside the application's service page, they render and display the service subroutine's recommendation window based on the recommendation window materials and access address contained in the service recommendation data. In one optional implementation of this embodiment, entering the application, receiving service recommendation data, and displaying it includes: Check whether the service page is displayed. If so, render the recommendation window of the service subroutine based on the recommendation window material included in the service recommendation data and the access address, and display it on the service page; if not, no action is required.

[0123] like Figure 4 As shown, the user terminal calls the rendering component to render the service subroutine's recommendation window based on the recommendation window materials contained in the service recommendation data and the access address of the service subroutine accessing the merchant, and displays it on the service page.

[0124] In addition, the recommendation window can also be rendered and displayed on the user terminal when the user terminal enters the application in response to the program access command. That is, even when the user terminal is not on the service page, the recommendation window of the service subroutine can be rendered and displayed on the service page based on the recommendation window material and access address included in the service recommendation data sent by the server.

[0125] In addition, there are cases where the user is on the system's main page before engaging in near-field communication interaction. The user terminal can respond to the application's program access command to enter the application's main page, where service recommendation data can be displayed. For this, the server can render a service recommendation window based on the merchant's identifier and the access address of the service subroutine, using the rendered window parameters as service recommendation data to improve interaction efficiency. In one optional implementation of this embodiment, responding to the program access command to enter the application, receiving and displaying service recommendation data includes: The user is redirected from the system page to the main page according to the program access instruction, and a service recommendation window is generated and displayed based on the service window parameters contained in the service recommendation data.

[0126] Optionally, the service window parameters are obtained by rendering based on the merchant identification material of the accessed merchant and the access address.

[0127] Optionally, service recommendation data can be displayed on the application's main page.

[0128] Specifically, the server obtains the merchant identification material of the accessing merchant and the access address of the service subroutine of the accessing merchant. Based on the merchant identification material and the access address, it calls the rendering component to render the service recommendation window of the service subroutine. The service window parameters of the service recommendation window are sent to the user terminal as service recommendation data. The user terminal first jumps from the system page to the main page of the application based on the program access command. The service recommendation window is generated and displayed on the main page according to the service window parameters.

[0129] like Figure 5 As shown, the user terminal displays a service recommendation window on the main page of the payment application.

[0130] It should be noted that the method of rendering the service recommendation window by the server and using the service window parameters of the service recommendation window as service recommendation data can also be implemented when the user terminal is displaying service recommendation data on the application's service page. That is, the user terminal generates and displays the service recommendation window based on the service window parameters within the application's service page. This embodiment does not limit this. It should be noted that the service recommendation window can be a service recommendation window that is rendered and displayed by the user terminal based on the service recommendation data sent by the server.

[0131] After service recommendation data is displayed on the user terminal, a service access subroutine can be accessed upon detecting a service access command. This service subroutine access command can be triggered by the user in response to the service recommendation data displayed on the user terminal. For example, the user can trigger the service subroutine access command after triggering the access interface of the service recommendation window displayed on the user terminal, or the service subroutine access interface can be actively triggered after the display time of the service recommendation window expires. Optionally, the service access command can be triggered after the user triggers the service access interface contained in the service recommendation window, or after the display time of the service recommendation window expires.

[0132] like Figure 4 and Figure 5 As shown, the user access command can be triggered by the user triggering the access interface 401 of the service recommendation window displayed on the application's service page or the access interface 501 of the service recommendation window displayed on the application's main page, or it can be triggered after the display time of the service recommendation window on the application's service page or the service recommendation window on the application's main page has elapsed.

[0133] It should be noted that the service recommendation window can be a service recommendation window that is rendered and displayed by the user terminal based on the service recommendation data sent by the server, or it can be a service recommendation window that is rendered and generated by the server and then sent to the user terminal. This embodiment does not limit this; that is, the service recommendation windows generated and displayed by the user terminal in the above two ways can be triggered by the above two service access commands. This embodiment will not elaborate on this further.

[0134] In practical applications, after accessing the merchant's service subroutine, users can perform operations such as ordering, placing orders, and shopping, and may make payments. Since near-field communication (NFC) interaction has already been performed, user account information can be uploaded to the server as device interaction information during NFC interaction. This allows the merchant's device to upload the user's payment instructions and order information to the server during payment, improving payment efficiency. In one optional implementation of this embodiment, it further includes: Obtain the user's payment instruction and transmit it to the merchant device to submit the order information to the server through the merchant device; Receive payment completion information from the server and display it on the service page of the service subroutine.

[0135] Optionally, the server generates a payment order based on the order information, and after detecting the user's payment instruction, processes the payment order based on the user account information corresponding to the user account information contained in the device interaction information.

[0136] Optionally, the user payment instruction is transmitted via a near-field communication connection.

[0137] Specifically, the user terminal receives the user's payment instruction and transmits it to the merchant device. The merchant device then obtains the order information for the corresponding product order and submits the order information and the user's payment instruction to the server. Upon receiving the user's payment instruction, the server generates a payment order based on the order information and processes the payment order based on the user account information contained in the device interaction information, generating payment completion information and sending it to the user terminal. After receiving the payment completion information, the user terminal displays it on the service page of the service subroutine. The service subroutine can be a shopping subroutine or a food ordering subroutine, and the merchant device can be a merchant POS terminal with wireless communication and near-field communication interaction capabilities.

[0138] Based on the above-mentioned generation of interactive animation frames according to the service type of the service to which the application's subroutine page belongs, after entering the service subroutine of the merchant, the user's credential identifier can also be used as a near-field communication tag for secondary near-field communication interaction. For example, after entering the service subroutine of a medical institution, the user's insurance credential identifier can be used as a near-field communication tag to perform secondary near-field communication interaction with the medical institution's near-field communication equipment for payment processing. Alternatively, after entering the ride-hailing service, the user's identity credential identifier can be used as a near-field communication tag to perform secondary near-field communication interaction with the station's entry and exit verification equipment for identity verification processing. In an optional implementation of this embodiment, it further includes: Invoke the near-field communication component and use the credential identifier of the user credential as the near-field communication tag; A secondary near-field communication connection is established between the near-field communication tag and the merchant's device for identity verification and / or payment processing.

[0139] Furthermore, the credential identifier of the user credential may be stored within the application. The user terminal can first call the application's credential interface to obtain the credential identifier of the user credential, so as to use the credential identifier of the user credential within the service subroutine of accessing the merchant; optionally, the credential identifier is obtained by calling the application's credential interface back.

[0140] In summary, the one or more service access processing methods based on near-field communication provided in this embodiment can be applied to a server. During the process of accessing services through near-field communication, device interaction information uploaded by the merchant's device is obtained, application access instructions are sent to the merchant's device to be transmitted to the user terminal, the merchant is determined based on the device interaction information, the access address of the service subroutine of the merchant is queried, service recommendation data of the service subroutine is generated based on the access address, and the service recommendation data is sent to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine after entering the application. By entering the merchant's service subroutine through near-field communication interaction, the access efficiency is improved. Before establishing a near-field communication connection between the user terminal and the merchant's device, interactive animation frames illustrating near-field communication interaction can be generated based on the user's location information and displayed on the application's service page to remind the user that near-field communication interaction is available for quick access to services, thus enhancing the user's perception of near-field communication interaction.

[0141] The following description uses the application of a service access processing method based on near-field communication provided in this embodiment in a first interactive scenario as an example to further illustrate the service access processing method based on near-field communication provided in this embodiment. See [link to documentation]. Figure 6 The service access processing method based on near-field communication, applied to the first interaction scenario, specifically includes the following steps.

[0142] Step S604: Obtain the device interaction information uploaded by the merchant device, and send the application's program access instruction to the merchant device to transmit it to the user terminal.

[0143] Step S606: Extract the merchant identifier field from the device identifier information of the merchant device contained in the device interaction information, query the target merchant corresponding to the merchant identifier field, and use the target merchant as the access merchant.

[0144] Step S608: Obtain the merchant identification material of the accessing merchant.

[0145] Step S610: Extract the user identity information contained in the device interaction information and check whether the user identity information matches the registered user information of the accessing merchant.

[0146] If so, proceed to step S612; If not, no action needs to be taken.

[0147] Step S612: Obtain the access address of the member subroutine for accessing the merchant.

[0148] Step S614: Render the service recommendation window based on the merchant identification material and access address, and send the service window parameters of the service recommendation window to the user terminal.

[0149] Optionally, if the execution result of step S610 is negative, the access address of the merchant's registration subroutine can be obtained; a service recommendation window can be rendered based on the merchant's identification material and the access address; and the service window parameters of the service recommendation window can be sent to the user terminal.

[0150] The following description uses the application of a service access processing method based on near-field communication provided in this embodiment in a second interaction scenario as an example to further illustrate the service access processing method based on near-field communication provided in this embodiment. See [link to documentation]. Figure 7 The service access processing method based on near-field communication, applied to the second interaction scenario, specifically includes the following steps.

[0151] Step S704: Obtain the user location information uploaded by the user terminal, and query the store information of the stores that match the user location information.

[0152] Step S706: Render interactive animation frames based on the merchant identification material of the store's owner included in the store information, and send them to the user terminal.

[0153] Step S712: Obtain device interaction information uploaded by the merchant device, and send a program access instruction for the application to the merchant device for transmission to the user terminal.

[0154] Step S714: Extract the device identification information of the merchant's device contained in the device interaction information, and query the merchant corresponding to the device identification information.

[0155] Step S716: Match the merchant information of the store's owner with the merchant information of the merchant corresponding to the device identification information.

[0156] Step S718: If the match is successful, determine the merchant to which the store belongs and the merchant corresponding to the device identification information as the visiting merchant, query the access address of the service subroutine of the visiting merchant, and generate service recommendation data based on the merchant identification material and the access address.

[0157] Step S720: Service recommendation data is sent to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine of the merchant after entering the application.

[0158] This specification provides an embodiment of a service access processing device based on near-field communication as follows: In the above embodiments, a service access processing method based on near-field communication applied to a user terminal is provided. Correspondingly, a service access processing device based on near-field communication running on a user terminal is also provided, which will be described below with reference to the accompanying drawings.

[0159] Reference Figure 9This illustration shows a schematic diagram of an embodiment of a service access processing device based on near-field communication provided in this embodiment.

[0160] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0161] This embodiment provides a service access processing device based on near-field communication, which operates on a user terminal and includes: The near-field communication connection establishment module 902 is configured to call the near-field communication component to establish a near-field communication connection with the merchant device, so as to upload device interaction information to the server through the merchant device; The program access instruction receiving module 904 is configured to receive program access instructions for the application transmitted by the merchant's device; The service recommendation data display module 906 is configured to respond to the program access command to enter the application, receive and display the service recommendation data of the service subroutine of the accessed merchant issued by the server; the accessed merchant is determined based on the device interaction information; The service subroutine access module 908 is configured to, upon detecting a service access instruction for the service subroutine, enter the service subroutine based on the subroutine access address contained in the service recommendation data.

[0162] Another embodiment of the service access processing device based on near-field communication provided in this specification is as follows: In the above embodiments, a service access processing method based on near-field communication for a server is provided. Correspondingly, a service access processing device based on near-field communication running on a server is also provided, which will be described below with reference to the accompanying drawings.

[0163] Reference Figure 10 This illustration shows a schematic diagram of an embodiment of a service access processing device based on near-field communication provided in this embodiment.

[0164] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0165] This embodiment provides another service access processing device based on near-field communication, which runs on a server. The device includes: The program access instruction issuing module 1002 is configured to obtain device interaction information uploaded by the merchant device and issue a program access instruction for the application to the merchant device for transmission to the user terminal; the program access instruction is transmitted through a near-field communication connection. The service recommendation data generation module 1004 is configured to determine the access merchant based on the device interaction information, query the access address of the service subroutine of the access merchant, and generate service recommendation data of the service subroutine based on the access address; The service recommendation data delivery module 1006 is configured to deliver the service recommendation data to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine after entering the application.

[0166] This specification provides the following embodiment of a user terminal: Corresponding to the service access processing method based on near-field communication described above, and based on the same technical concept, one or more embodiments of this specification also provide a user terminal for executing the service access processing method based on near-field communication described above. Figure 11 This is a schematic diagram of the structure of a user terminal provided for one or more embodiments of this specification.

[0167] This embodiment provides a user terminal, including: like Figure 11 As shown, user terminals can vary significantly due to differences in configuration or performance. They may include one or more processors 1101 and memory 1102, with memory 1102 storing one or more application programs or data. Memory 1102 can be temporary or persistent storage. The application programs stored in memory 1102 may include one or more modules (not shown), each module including a series of computer-executable instructions from the user terminal. Furthermore, processor 1101 may be configured to communicate with memory 1102 to execute the series of computer-executable instructions stored in memory 1102 on the user terminal. The user terminal may also include one or more power supplies 1103, one or more wired or wireless network interfaces 1104, one or more input / output interfaces 1105, one or more keyboards 1206, etc.

[0168] In one specific embodiment, the user terminal includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the user terminal, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: The near-field communication component is invoked to establish a near-field communication connection with the merchant's device, so as to upload device interaction information to the server through the merchant's device; Receive application access instructions transmitted by the merchant's device; In response to the program access command, the application enters, receives and displays service recommendation data from the service subroutine of the accessing merchant issued by the server; the accessing merchant is determined based on the device interaction information. Upon detecting a service access instruction for the service subroutine, the system enters the service subroutine based on the subroutine access address contained in the service recommendation data.

[0169] This specification provides the following server implementation example: Corresponding to the other service access processing method based on near-field communication described above, and based on the same technical concept, one or more embodiments of this specification also provide a server for executing the other service access processing method based on near-field communication described above. Figure 11 This is a schematic diagram of the structure of a server provided for one or more embodiments of this specification.

[0170] This embodiment provides a server, including: like Figure 12 As shown, servers can vary significantly due to differences in configuration or performance. They may include one or more processors 1201 and memory 1202, with memory 1202 storing one or more application programs or data. Memory 1202 can be temporary or persistent storage. The application programs stored in memory 1202 may include one or more modules (not shown), each module including a series of computer-executable instructions for the server. Furthermore, processor 1201 may be configured to communicate with memory 1202, executing the series of computer-executable instructions stored in memory 1202 on the server. The server may also include one or more power supplies 1203, one or more wired or wireless network interfaces 1204, one or more input / output interfaces 1205, etc.

[0171] In one specific embodiment, the server includes memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the server, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: The system acquires device interaction information uploaded by the merchant's device and sends a program access command to the merchant's device for transmission to the user terminal; the program access command is transmitted via a near-field communication connection. The access merchant is determined based on the device interaction information, the access address of the service subroutine of the access merchant is queried, and service recommendation data of the service subroutine is generated based on the access address; The service recommendation data is sent to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine after entering the application.

[0172] This specification provides an embodiment of a computer-readable storage medium as follows: Corresponding to the service access processing method based on near-field communication described above, and based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0173] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: The near-field communication component is invoked to establish a near-field communication connection with the merchant's device, so as to upload device interaction information to the server through the merchant's device; Receive application access instructions transmitted by the merchant's device; In response to the program access command, the application enters, receives and displays service recommendation data from the service subroutine of the accessing merchant issued by the server; the accessing merchant is determined based on the device interaction information. Upon detecting a service access instruction for the service subroutine, the system enters the service subroutine based on the subroutine access address contained in the service recommendation data.

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

[0175] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the other service access processing method based on near-field communication described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0176] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: The system acquires device interaction information uploaded by the merchant's device and sends a program access command to the merchant's device for transmission to the user terminal; the program access command is transmitted via a near-field communication connection. The access merchant is determined based on the device interaction information, the access address of the service subroutine of the access merchant is queried, and service recommendation data of the service subroutine is generated based on the access address; The service recommendation data is sent to the user terminal so that the user terminal can display the service recommendation data and enter the service subroutine after entering the application.

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

[0178] The various embodiments in this specification are described in a progressive manner. For the same or similar parts between the various embodiments, please refer to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment, and storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. For reading the relevant content of the device embodiment, equipment embodiment, and storage medium embodiment, please refer to the description of the method embodiment.

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

[0180] In the 1930s, 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 improvements to the methodology 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 an improvement to the methodology 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 and "integrate" a digital system onto a PLD themselves, 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 also 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 also 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.

[0181] 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 626D, Atmel AT151SAM, Microchip PIC18F26K20, and Silicon Labs C8061F320. 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.

[0182] 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.

[0183] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0184] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may 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.

[0185] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. 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.

[0186] 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.

[0187] 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.

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

[0189] 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.

[0190] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by 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 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.

[0191] 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.

[0192] One or more embodiments of this specification 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 particular task or implement a particular abstract data type. One or more embodiments of this specification 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.

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

Claims

1. A service access processing method based on near-field communication, applied to a user terminal, the method comprising: The application enters according to the user's access instruction and sends the user's location information to the server to determine the target merchant corresponding to the user's location information. It then receives the interactive animation frames of the target merchant sent by the server and displays them. The near-field communication component is invoked to establish a near-field communication connection with the merchant's device, so as to upload device interaction information to the server through the merchant's device; Receive the application access instruction transmitted by the merchant's device, detect whether it is in the application in response to the application access instruction, and after detecting that it is in the service page of the application, render and display the recommendation window of the service subroutine of the merchant based on the recommendation window material and access address contained in the service recommendation data. Upon detecting a service access instruction for the service subroutine, the system enters the service subroutine based on the subroutine access address contained in the service recommendation data.

2. The service access processing method based on near-field communication according to claim 1, wherein the accessing merchant is determined based on the device interaction information; in, The device interaction information includes the device identification information of the merchant's device, and the merchant corresponding to the merchant identification field in the device identification information is used as the accessing merchant.

3. The service access processing method based on near-field communication according to claim 1, wherein the device interaction information includes the terminal location information of the user terminal; The merchant to which the store corresponding to the terminal location information belongs is regarded as the accessing merchant.

4. The service access processing method based on near-field communication according to claim 1, wherein the service access instruction is triggered after the user triggers the service access interface contained in the recommendation window; The recommendation window is generated and displayed based on the service recommendation data.

5. The service access processing method based on near-field communication according to claim 1, wherein the service subroutine includes: Registration service subroutine and / or rights service subroutine; Accordingly, the service recommendation data is generated in the following manner: Extract the user identity information contained in the device interaction information, and detect whether the user identity information matches the registered user information of the accessing merchant; If so, generate the service recommendation data based on the access address of the rights service subroutine; If not, generate the service recommendation data based on the access address of the registration service subroutine.

6. The service access processing method based on near-field communication according to claim 1, wherein the accessing merchant is determined in the following manner: Extract the device identification information of the merchant's device contained in the device interaction information, and query the service merchant corresponding to the device identification information; The system checks whether the service provider is the same as the target provider. If not, the service provider is selected as the access provider.

7. The service access processing method based on near-field communication according to claim 1 further includes: Obtain the user's payment instruction and transmit it to the merchant device, so as to submit the order information and the user's payment instruction to the server through the merchant device; The user payment instruction is transmitted via a near-field communication connection; Receive payment completion information from the server and display it on the service page of the service subroutine; The server generates a payment order based on the order information, and processes the payment order according to the user's payment instruction and the user account corresponding to the user account information contained in the device interaction information.

8. The service access processing method based on near-field communication according to claim 1, before the step of calling the near-field communication component to establish a near-field communication connection with the merchant device to upload device interaction information to the server through the merchant device, it further includes: Upon entering the application's sub-program page according to the user's access instruction, the service type of the service to which the sub-program page belongs is determined and sent to the server; Receive interactive animation frames for the service sent by the server and display them on the subroutine page; The interactive animation frames are rendered based on the identifier material of the user credential corresponding to the service.

9. The service access processing method based on near-field communication according to claim 8, after the step of entering the service subroutine based on the subroutine access address contained in the service recommendation data after detecting the service access instruction for the service subroutine, further includes: Invoke the near-field communication component and use the credential identifier of the user credential as the near-field communication tag; A secondary near-field communication connection is established between the near-field communication tag and the merchant's device for identity verification and / or payment processing.

10. A service access processing method based on near-field communication, applied to a server, the method comprising: The system obtains user location information uploaded by the user terminal and queries store information that matches the user location information. Based on the merchant identification material of the merchant to which the store belongs, it renders interactive animation frames and sends them to the user terminal. Obtain device interaction information uploaded by the merchant's devices; The access merchant is determined based on the device interaction information, the access address of the service subroutine of the access merchant is queried, and service recommendation data of the service subroutine is generated based on the access address; The service recommendation data is sent to the user terminal so that the user terminal displays a recommendation window of the service subroutine rendered based on the recommendation window material and access address contained in the service recommendation data, and enters the service subroutine after detecting a service access instruction for the service subroutine. The service recommendation data is sent to the user terminal after the user terminal responds to the application access command transmitted by the merchant's device and detects that the user is on the service page of the application.

11. The service access processing method based on near-field communication according to claim 10, wherein the device interaction information includes: The device identification information of the merchant's equipment; Accordingly, determining the accessing merchant based on the device interaction information includes: Extract the merchant identifier field contained in the device identifier information, and query whether the merchant identifier field contains a corresponding merchant; If so, the target merchant obtained from the query will be used as the accessed merchant.

12. The service access processing method based on near-field communication according to claim 10, wherein the user terminal enters the application according to the user access instruction and sends the user location information to the server.

13. The service access processing method based on near-field communication according to claim 12, wherein the interactive animation frame is displayed after the user terminal enters the service page of the application; Accordingly, generating service recommendation data for the service subroutine based on the access address includes: The recommended window is rendered based on the merchant's identification material and the access address. The window parameters of the service recommendation window are used as the service recommendation data.

14. The service access processing method based on near-field communication according to claim 10, wherein the service subroutine includes: Registration service subroutine and / or rights service subroutine; Accordingly, the service recommendation data is generated in the following manner: Extract the user identity information contained in the device interaction information, and detect whether the user identity information matches the registered user information of the accessing merchant; If so, generate the service recommendation data based on the access address of the rights service subroutine; If not, generate the service recommendation data based on the access address of the registration service subroutine.

15. The service access processing method based on near-field communication according to claim 10, further comprising: Obtain the order information submitted by the merchant's device and generate a payment order based on the order information; Upon detecting a user payment instruction, the payment order is processed according to the user account information corresponding to the user account information contained in the device interaction information, and a payment completion message is generated and sent to the user terminal after the payment is completed. The user payment instruction is transmitted from the user terminal to the merchant device via a near-field communication connection, and then submitted by the merchant device to the server.

16. A service access processing apparatus based on near-field communication, operating on a user terminal, the apparatus comprising: The near-field communication connection establishment module is configured to enter the application according to the user's access instruction and send the user's location information to the server to determine the target merchant corresponding to the user's location information, receive the interactive animation frames of the target merchant sent by the server and perform display processing. The near-field communication component is invoked to establish a near-field communication connection with the merchant's device, so as to upload device interaction information to the server through the merchant's device; The service recommendation data display module is configured to receive the application access instruction transmitted by the merchant's device, detect whether it is within the application in response to the application access instruction, and after detecting that it is within the service page of the application, render and display the recommendation window of the access merchant's service subroutine based on the recommendation window material and access address contained in the service recommendation data. The service subroutine access module is configured to, upon detecting a service access instruction for the service subroutine, enter the service subroutine based on the subroutine access address contained in the service recommendation data.

17. A user terminal, comprising: processor; And, a memory configured to store computer-executable instructions, which the processor executes to implement the following process: The application enters according to the user's access instruction and sends the user's location information to the server to determine the target merchant corresponding to the user's location information. It then receives the interactive animation frames of the target merchant sent by the server and displays them. The near-field communication component is invoked to establish a near-field communication connection with the merchant's device, so as to upload device interaction information to the server through the merchant's device; Receive the application access instruction transmitted by the merchant's device, detect whether it is in the application in response to the application access instruction, and after detecting that it is in the service page of the application, render and display the recommendation window of the service subroutine of the merchant based on the recommendation window material and access address contained in the service recommendation data. Upon detecting a service access instruction for the service subroutine, the system enters the service subroutine based on the subroutine access address contained in the service recommendation data.

18. A computer-readable storage medium for storing computer-executable instructions that, when executed, implement the steps of the method of claim 1 or 10.

Images