Nfc-based web access method and apparatus

Abstract

The embodiment of the present specification provides a web page access method and device based on NFC, wherein the web page access method based on NFC comprises the following steps: in a web page access process, obtaining an NFC tag address field and an identification field, starting an application program based on the address field and transmitting parameters to the application program, verifying whether the starting type parameter transmitted through the application program corresponds to the NFC starting type, if yes, obtaining the web page address and the access token mapped by the identification field from a server, and performing web page access based on the web page address and access authentication based on the access token, so as to realize web page access in the application program through communication with the NFC tag.

Description

Technical Field

[0001] This document relates to the field of web technology, and in particular to a web access method and device based on NFC. Background Technology

[0002] With the continuous development and promotion of the Internet and terminal devices, the application of web page access based on the Internet and terminal devices is becoming more and more widespread, and the forms of web page access are becoming more and more flexible. For example, users can scan QR codes to access web pages through the scanning function of the application installed on the terminal device, or they can access web pages by clicking hyperlinks, or they can access web pages by "sticking" NFC (Near Field Communication) tags. However, many scenarios in reality have put forward higher requirements for the security of web page access. Summary of the Invention

[0003] This specification provides one or more embodiments of an NFC-based webpage access method applied to a user terminal. The method includes: acquiring webpage address information stored in an NFC tag. The webpage address information includes an address field and an identification field. An application is launched based on the address field, and the webpage address information and a launch type parameter are passed to the application. The application verifies whether the launch type parameter corresponds to an NFC launch type. If so, the webpage address mapped by the identification field and an access token are obtained from a server. Webpage access is performed based on the webpage address, and access authentication is performed based on the access token.

[0004] This specification provides one or more embodiments of another NFC-based webpage access method, applied to a server. The method includes: receiving an address query request carrying an identification field sent by an application. The identification field is obtained from address information stored in an NFC tag. The method queries the webpage address of the target webpage mapped by the identification field and generates an access token for the target webpage. The method returns the webpage address and the access token to the application in response to the address query request. The method then cooperates with the application to perform webpage access and authentication for the target webpage.

[0005] This specification provides one or more embodiments of an NFC-based web page access device, running on a user terminal. The device includes: an address acquisition module configured to acquire web page address information stored in an NFC tag. The web page address information includes an address field and an identification field. A program launch module configured to launch an application based on the address field and pass the web page address information and a launch type parameter to the application. A launch verification module configured to verify whether the launch type parameter corresponds to an NFC launch type through the application; if so, to run the web page access module. The web page access module is configured to obtain the web page address mapped by the identification field and an access token from a server, perform web page access based on the web page address, and perform access authentication based on the access token.

[0006] This specification provides one or more embodiments of another NFC-based web page access device, operating on a server. The device includes: a request receiving module configured to receive an address query request carrying an identification field sent by an application. The identification field is obtained from address information stored in an NFC tag. An address query module configured to query the web page address of the target web page mapped by the identification field and generate an access token for the target web page. An address return module configured to return the web page address and the access token to the application in response to the address query request. A web page access module configured to cooperate with the application to perform web page access and access authentication for the target web page.

[0007] This specification provides one or more embodiments of an NFC-based web access device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire web address information stored in an NFC tag. The web address information includes an address field and an identification field. An application is launched based on the address field, and the web address information and a launch type parameter are passed to the application. The application verifies whether the launch type parameter corresponds to an NFC launch type; if so, the web address mapped by the identification field and an access token are obtained from a server, and web access is performed based on the web address, and access authentication is performed based on the access token.

[0008] This specification provides one or more embodiments of another NFC-based web access device, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive an address query request carrying an identification field sent by an application. The identification field is obtained from address information stored in an NFC tag. The processor queries the web address of a target webpage mapped by the identification field and generates an access token for the target webpage. The processor returns the webpage address and the access token to the application in response to the address query request. The processor then cooperates with the application to perform webpage access and authentication for the target webpage.

[0009] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions. When executed, these computer-executable instructions perform the following process: obtaining webpage address information stored on an NFC tag. The webpage address information includes an address field and an identification field. An application is launched based on the address field, and the webpage address information and a launch type parameter are passed to the application. The application verifies whether the launch type parameter corresponds to an NFC launch type. If so, the webpage address mapped by the identification field and an access token are obtained from a server. Webpage access is performed based on the webpage address, and access authentication is performed based on the access token.

[0010] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions, which, when executed, perform the following process: receiving an address query request carrying an identification field sent by an application. The identification field is obtained from address information stored in an NFC tag. The webpage address of the target webpage mapped by the identification field is queried, and an access token for the target webpage is generated. The webpage address and the access token are returned to the application in response to the address query request. The application is then assisted in accessing and authenticating access to the target webpage. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the 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.

[0012] Figure 1 A schematic diagram illustrating an implementation environment for one or more embodiments of this specification of a web page access method based on NFC;

[0013] Figure 2 A flowchart illustrating an NFC-based web page access method provided for one or more embodiments of this specification;

[0014] Figure 3 This specification provides a timing diagram for processing an NFC-based web page access method applied to a web page access scenario, as shown in one or more embodiments.

[0015] Figure 4 A schematic diagram illustrating an implementation environment for another NFC-based web page access method provided in one or more embodiments of this specification;

[0016] Figure 5 A schematic diagram illustrating an embodiment of an NFC-based web access device provided in one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram illustrating another embodiment of an NFC-based web access device provided in one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of the structure of an NFC-based web access device provided for one or more embodiments of this specification;

[0019] Figure 8 This is a schematic diagram of another NFC-based web access device provided for one or more embodiments of this specification. Detailed Implementation

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

[0021] The NFC-based web page access method provided in one or more embodiments of this specification is applicable to the web page access implementation environment. (Refer to...) Figure 1 The implementation environment includes at least:

[0022] NFC tag 101, user terminal 102, and server 103;

[0023] The NFC tag 101 is used to store web page address information, which includes an address field and an identification field.

[0024] User terminal 102 has an application 102-1 and an NFC service 102-2 installed. The NFC service 102-2 is used to communicate with the NFC tag 101. The application 102-1 works with the server 103 to access web pages within the application 102-1. The user terminal 102 can be a mobile phone, personal computer, tablet computer, e-book reader, VR (Virtual Reality) based information interaction device, vehicle terminal, IoT device, wearable smart device, laptop computer and desktop computer, etc.

[0025] The server 103 is used to cooperate with the application 102-1 to access web pages and to perform access authentication during the web page access process.

[0026] In this implementation environment, after establishing communication with the NFC tag 101, the NFC service 102-2 installed on the user terminal 102 obtains web address information containing address and identification fields from the NFC tag 101. After obtaining the address and identification fields, the user terminal 102 launches the application 102-1 based on the address field and passes the web address information and launch type parameters to the application 102-1. The application 102-1 verifies whether the passed launch type parameters correspond to the NFC launch type. If they correspond, the application 102-1 obtains the web address and access token mapped by the identification field from the server 103 based on the passed identification field, and performs web access based on the obtained web address. It also cooperates with the server 103 to perform access authentication with the access token, avoiding the risk that the target webpage can be directly accessed through the address field stored in the NFC tag 101. This ensures that webpage access can only be performed within the application 102-1 through communication with the NFC tag 101, thus improving the security of webpage access within the application 102-1.

[0027] This specification provides one or more embodiments of an NFC-based web page access method as follows:

[0028] Reference Figure 2 The NFC-based web page access method provided in this embodiment can be applied to user terminals. The method specifically includes steps S202 to S208.

[0029] Step S202: Obtain the web address information stored in the NFC tag.

[0030] The NFC tag described in this embodiment refers to an NFC material or NFC device used for web page access. The NFC tag stores web page address information. The web page address information refers to information related to web page access. Optionally, the web page address information includes an address field and an identification field.

[0031] The identifier field records a webpage identifier, which corresponds to the target webpage to be accessed. Optionally, the target webpage includes webpages embedded within an application; alternatively, the target webpage can be a webpage recommending services within an application; the application can be a third-party application outside of a browser, such as a payment application. In this embodiment, to avoid the leakage of the target webpage's address due to the leakage of the webpage address information stored in the NFC tag, the target webpage's address is not recorded in the webpage address information. Instead, the identifier field is used to indicate that the webpage to be accessed is the target webpage corresponding to the identifier field.

[0032] In this embodiment, to avoid the risk of the webpage address information stored in the NFC tag being leaked, which could lead to direct access to the target webpage through the NFC tag, the webpage address of the target webpage is not recorded in the address field. In this case, the target webpage cannot be accessed directly through the address field, thereby improving the security of webpage access through the NFC tag. The function of the address field is to determine the application to be launched on the user terminal, that is, the address field can determine which application the webpage access is performed in.

[0033] Specifically, the address recorded in the address field can be understood as an address field that avoids direct access to the target webpage through the address field. Specifically, the address recorded in the address field can be the webpage address of another webpage besides the target webpage, so as to avoid direct access to the target webpage by redirecting to other webpages through the address field. In this case, the address recorded in the address field can be understood as a hidden address or a proxy address. In addition, the address recorded in the address field can also be an encrypted webpage address obtained by encrypting or masking the webpage address of the target webpage using technical means. In this case, the address recorded in the address field can be understood as an encrypted webpage address of the target webpage.

[0034] In practical applications, when the address field contained in the webpage address information cannot directly access the target webpage, the address recorded in the address field can be used to redirect traffic to the application, thereby increasing the application's access traffic. Specifically, the address field contained in the webpage address information can be set as the webpage address used to redirect traffic to the application. Correspondingly, the webpage corresponding to the address field contained in the webpage address information can be a referral webpage used to redirect traffic to the application; optionally, the webpage corresponding to the address field includes: a download guide webpage used to download the application.

[0035] In this embodiment, in addition to the address field and the identifier field included in the web page address information, the web page address information may also include an access type field, that is, the web page address information includes an address field, an identifier field and an access type field; the access type field is used to indicate the type of web page access currently being performed through an NFC tag.

[0036] For example, the web address information stored in the NFC tag is "https: / / yourhost / landing.html?nfcCode=A", which consists of three parts: address field, identifier field, and access type field.

[0037] The field "https: / / yourhost / landing.html" is an address field, which is the webpage address of the application's download guide page;

[0038] The “nfcCode” field is the access type field, indicating that webpage access is performed via an NFC tag;

[0039] The "A" field is an identifier field, representing the webpage identifier of the application's target webpage.

[0040] In specific implementation, the process of obtaining the web address information stored in the NFC tag involves obtaining the web address information from the NFC tag after establishing communication with it. In one optional implementation provided in this embodiment, obtaining the web address information stored in the NFC tag includes: establishing communication with the NFC tag and sending a query signal to the NFC tag; and receiving the web address information returned by the NFC tag in response to the query signal.

[0041] As mentioned above, the purpose of the address field in the webpage address information is to determine the application to be launched on the user's terminal. In other words, the address field can determine which application is used to access the webpage. In actual scenarios, when a user's terminal obtains the webpage address information stored in the NFC tag to access the webpage, there may be cases where the user's terminal has already installed the application corresponding to the address field. In this case, the application corresponding to the address field is launched and the webpage is accessed through the application. In addition, there may be cases where the user's terminal does not have the application corresponding to the address field installed. In this case, the webpage cannot be accessed through the application. To address this, the address recorded in the address field can be used to redirect traffic to the application, thereby increasing the application's access traffic.

[0042] Specifically, the system can detect whether the user's terminal has the application corresponding to the address field installed by checking the address field in the webpage address information. If it is installed, the webpage access process can be performed within the application corresponding to the address field through subsequent processing. If it is not installed, the corresponding webpage used for traffic redirection can be accessed through the browser installed on the user's terminal.

[0043] Specifically, in one optional implementation of this embodiment, it is found that the user terminal has installed the application corresponding to the address field.

[0044] If so, perform the following step S204: start the application based on the address field, and pass the web page address information and the startup type parameter to the application;

[0045] If not, launch the browser installed on the user's terminal, retrieve the webpage data corresponding to the address field from the server through the browser, and load and display the webpage.

[0046] Furthermore, based on the webpage address information including address field, identifier field, and access type field, to ensure that webpage access can only be performed within the specified application on the user terminal through communication between the user terminal and the NFC tag, thereby further enhancing the security of webpage access, in an optional implementation of this embodiment, after obtaining the webpage address information stored in the NFC tag, it can also be determined whether the access type field contained in the webpage address information is a preset type field. For example, it can be determined whether the access type field contained in the webpage address information stored in the NFC tag is the "nfcCode" access type field. If yes, step S204 is executed or the above-mentioned operation of detecting whether the user terminal has installed the application corresponding to the address field is executed; if no, an access failure reminder is generated or no action is taken. Alternatively, it can also be determined whether the webpage address information contains an access type field. If yes, step S204 is executed or the above-mentioned operation of detecting whether the user terminal has installed the application corresponding to the address field is executed; if no, an access failure reminder is generated or no action is taken.

[0047] Step S204: Launch the application based on the address field, and pass the web page address information and launch type parameter to the application.

[0048] After obtaining the web address information stored in the NFC tag, the web address information can be parsed. Based on the parsing result, the address field and identification field contained in the web address information can be extracted. Alternatively, the address field, identification field, and access type field contained in the web address information can be extracted based on the parsing result. These fields can be used for subsequent web access processing based on the address field and the identification field, or for subsequent web access processing based on the address field, identification field, and access type field.

[0049] In practice, during the process of launching an application based on the address field, the launched application can be the application corresponding to the address field, that is, the application corresponding to the address field can be launched. Specifically, the application corresponding to the application identifier contained in the address field can be launched. After the application is launched, the web page address information and launch type parameters are passed to the launched application for web page access within the application; in addition, the identifier field and launch type parameters can also be passed to the application, or the identifier field, access type field, and launch type parameters can be passed to the application.

[0050] The startup type parameter is generated by the user terminal's operating system. Specifically, when the user terminal's operating system detects that the service being launched is the user terminal's NFC service, it generates the startup type parameter corresponding to the NFC service.

[0051] For example, after obtaining the web address information "https: / / yourhost / landing.html?nfcCode=A" stored in the NFC tag, the application corresponding to the application identifier "yourhost" installed on the user terminal is launched based on the application identifier "yourhost" contained in the address field "https: / / yourhost / landing.html".

[0052] Step S206: Verify whether the startup type parameter corresponds to the NFC startup type through the application.

[0053] In the specific execution process, after launching the application and passing the web address information and launch type parameters to the application, the application accesses the web page according to the passed web address information and launch type parameters. Specifically, in order to ensure that web page access can only be performed within the application through communication between the user terminal and the NFC tag, the launch type parameters are verified to correspond to the NFC launch type to verify whether the current web page access within the application is triggered by interaction with the NFC tag.

[0054] If the startup type parameter corresponds to the NFC startup type, it indicates that the current web page access within the application is triggered by interaction with the NFC tag. Execute step S208 below to perform the corresponding web page access processing within the application.

[0055] If the startup type parameter does not correspond to the NFC startup type, it indicates that the current web page access within the application is not triggered by interaction with the NFC tag. To ensure that web page access within the application can only be performed through communication between the user terminal and the NFC tag, in this case, an access failure reminder can be generated or no action can be taken.

[0056] It should be noted that, when the webpage address information includes an address field, an identifier field, and an access type field, in order to ensure that webpage access can only be performed within the designated application on the user terminal through communication between the user terminal and the NFC tag, thereby improving the security of webpage access, in an optional implementation of this embodiment, before verifying whether the launch type parameter corresponds to the NFC launch type through the application, the application can also determine whether the access type field contained in the webpage address information is a preset type field. For example, it can determine whether the access type field contained in the webpage address information stored from the NFC tag is the "nfcCode" access type field. If yes, the operation of verifying whether the launch type parameter corresponds to the NFC launch type through the application is performed; if no, an access failure reminder is generated or no action is taken. Alternatively, the application can also determine whether the webpage address information contains an access type field. If yes, the operation of verifying whether the launch type parameter corresponds to the NFC launch type through the application is performed; if no, an access failure reminder is generated or no action is taken.

[0057] Step S208: Obtain the web address and access token mapped by the identification field from the server, access the web page based on the web address, and authenticate access based on the access token.

[0058] During web page access within the application, to ensure that web page access can only be performed through communication between the user terminal and the NFC tag, the application verifies whether the current web page access within the application is performed through communication with the NFC tag by checking whether the launch type parameter corresponds to the NFC launch type. If the launch type parameter corresponds to the NFC launch type, that is, if the current web page access within the application is performed through communication with the NFC tag, the application obtains the web address and access token mapped by the identification field from the server, performs web page access based on the web address, and performs access authentication based on the access token.

[0059] In practice, during the process of obtaining the web address and access token mapped by the identifier field from the server, the application can request the web address and access token from the server by sending the identifier field or by sending an address query request carrying the identifier field. After receiving the identifier field, the server queries the web address mapped by the identifier field according to the mapping table, generates the access token, and returns the web address and access token to the application.

[0060] In one optional implementation of this embodiment, obtaining the web address and access token mapped to the identifier field from the server includes:

[0061] Send an address query request carrying an identifier field to the server;

[0062] Receive the web address information mapped by the identifier field returned by the server, and parse the received web address information to obtain the web address and access token.

[0063] Optionally, the web address information mapped to the identifier field can be obtained in the following way:

[0064] Query the target webpage address mapped by the identifier field in the pre-established mapping table, and generate an access token for the target webpage;

[0065] The retrieved webpage address is concatenated with the generated access token to obtain the webpage address information mapped to the identifier field.

[0066] The mapping table is a pre-established data table used to record the mapping relationship between web page identifiers and web page addresses. The web page addresses recorded in the mapping table are the actual web page addresses. After querying the web page address of the target web page from the mapping table, the current target web page can be accessed within the application based on the queried web page address.

[0067] Continuing with the previous example, the webpage address information "https: / / yourhost / landing.html?nfcCode=A" contains the identifier field "A". After the application sends an address query request carrying the identifier field "A" to the server, the server performs a webpage address query based on the identifier field "A" in a pre-established mapping table. The webpage address of the target webpage found is "yourapp: / / page / activity?p1=xxx". Further, a one-time random number (token) is generated using a random number generation algorithm as an access token to access the target webpage. The server then concatenates the webpage address "yourapp: / / page / activity?p1=xxx" with the generated random number (token) to obtain the webpage address information mapped to the identifier field "A" as "yourapp: / / page / activity?p1=xxx&tk=token", and sends this webpage address information to the application.

[0068] In practice, after the application obtains the web address and access token from the server, it accesses the web page based on the web address and performs access authentication based on the access token. Specifically, it accesses the target web page within the application based on the web address and performs access authentication for the target web page during the web page access process.

[0069] During webpage access and authentication, the application can obtain the webpage data corresponding to the webpage address from the server, that is, obtain the webpage data of the target webpage, load and execute the webpage data to obtain the target webpage, and cooperate with the server to authenticate the target webpage based on the access token before displaying the target webpage in the application. If the authentication is successful, the target webpage is displayed in the application; otherwise, if the authentication fails, an authentication failure reminder and a reminder to access the webpage again are displayed, or no action is taken.

[0070] In one optional implementation of this embodiment, webpage access based on webpage address and access authentication based on access token are performed, including:

[0071] Retrieve the webpage data corresponding to the webpage address from the server, load and execute the webpage data to obtain the target webpage;

[0072] Submit an authentication request carrying an access token to the server;

[0073] If the server returns an authentication result indicating successful authentication, the target webpage will be displayed within the application.

[0074] In practice, after receiving an authentication request carrying an access token, the server performs access token authentication. The server-side access token authentication can be implemented in the following ways:

[0075] Check whether the terminal information in the authentication request is the same as the terminal information in the access record; if they are different, it is determined that the authentication failed.

[0076] If they are the same, check if the access token is within its validity period. If yes, authentication is successful; otherwise, authentication fails. Optionally, the validity period is determined based on the token generation time and the token's validity duration. Terminal information refers to the user terminal's device information, such as the user terminal's model information and / or operating system information.

[0077] In summary, the NFC-based webpage access method provided in this embodiment avoids the risk of webpage address leakage caused by storing webpage address information containing address and identification fields on the NFC tag. The address field can be a hidden address, proxy address, or encrypted webpage address. Based on this, during webpage access via communication with the NFC tag, the webpage address information is obtained from the NFC tag. The application is launched based on the address field contained in the webpage address information, and the webpage address information and launch type parameters are passed to the application. The application verifies whether the current webpage access within the application is via communication with the NFC tag by checking whether the launch type parameter corresponds to the NFC launch type. If the launch type parameter corresponds to the NFC launch type, the webpage address mapped by the identification field and the access token are obtained from the server. Webpage access is performed based on the webpage address, and access authentication is performed based on the access token. This ensures that webpage access within the application can only be performed via communication with the NFC tag, thus improving the security of webpage access via NFC tag communication.

[0078] The following example uses an NFC-based web page access method provided in this embodiment to illustrate its application in a web page access scenario. Figure 3 The NFC-based web page access method provided in this embodiment will be further explained below. Figure 3 An NFC-based web access method for web access scenarios includes the following steps.

[0079] Step S302: Establish communication with the NFC tag and send a query signal to the NFC tag.

[0080] Step S304: Receive the web address information returned by the NFC tag in response to the query signal.

[0081] The webpage address information includes an address field and an identifier field.

[0082] Step S306: Detect whether the user terminal has the application corresponding to the address field installed;

[0083] If so, proceed with steps S308 to S310 below;

[0084] If not, launch the browser installed on the user's terminal, retrieve the webpage data of the download guide webpage corresponding to the address field from the server through the browser, and load and display the webpage.

[0085] Step S308: Start the application based on the address field and pass the web address information and startup type parameter to the application.

[0086] Step S310: Verify whether the startup type parameter corresponds to the NFC startup type through the application.

[0087] If so, proceed with step S312 below;

[0088] If not, generate an access failure notification or do nothing.

[0089] Step S312: Send an address query request carrying an identifier field to the server.

[0090] Step S320: Receive the web address and access token returned by the server.

[0091] Step S322: Obtain the webpage data corresponding to the webpage address from the server, load and execute the webpage data to obtain the target webpage.

[0092] Step S324: Submit an authentication request carrying an access token to the server.

[0093] Step S332: If the authentication result returned by the server is successful, display the target webpage within the application.

[0094] Steps S302 to S312, S320 to S324, and S332 provided in this embodiment are executed by the user terminal. It should be noted that the steps S302 to S312, S320 to S324, and S332 executed by the user terminal can cooperate with steps S314 to S318 and S326 to S330 executed by the server in the following embodiment. Therefore, when reading this embodiment, please refer to the corresponding content of steps S314 to S318 and S326 to S330 provided in the following method embodiment. When reading the following method embodiment, please refer to the corresponding content of steps S302 to S312, S320 to S324, and S332 provided in this embodiment.

[0095] It should be noted that any one or more of steps S302 to S312, S320 to S324, and S332 can be combined with any one or more of steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S302 to S312, S320 to S324, and S332 can be selected and combined with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S302 to S312, S320 to S324, and S332 can also be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0096] One or more embodiments of another NFC-based web page access method provided in this specification are as follows:

[0097] Reference Figure 4 The NFC-based web page access method provided in this embodiment can be applied to the server side. The method specifically includes steps S402 to S408.

[0098] Step S402: Receive an address query request carrying an identifier field sent by the application.

[0099] In this embodiment, the identification field can be obtained from the webpage address information stored in the NFC tag. An NFC tag refers to an NFC material or NFC device used for webpage access, and the NFC tag stores webpage address information; the webpage address information refers to information related to webpage access, and optionally, the webpage address information includes an address field and an identification field;

[0100] The identifier field records a webpage identifier, which corresponds to the target webpage to be accessed. Optionally, the target webpage includes webpages embedded within an application; alternatively, the target webpage can be a webpage recommending services within an application; the application can be a third-party application outside of a browser, such as a payment application. In this embodiment, to avoid the leakage of the target webpage's address due to the leakage of the webpage address information stored in the NFC tag, the target webpage's address is not recorded in the webpage address information. Instead, the identifier field is used to indicate that the webpage to be accessed is the target webpage corresponding to the identifier field.

[0101] In this embodiment, to avoid the risk of the webpage address information stored in the NFC tag being leaked, which could lead to direct access to the target webpage through the NFC tag, the webpage address of the target webpage is not recorded in the address field. In this case, the target webpage cannot be accessed directly through the address field, thereby improving the security of webpage access through the NFC tag. The function of the address field is to determine the application to be launched on the user terminal, that is, the address field can determine which application the webpage access is performed in.

[0102] Specifically, the address recorded in the address field can be understood as an address field that avoids direct access to the target webpage through the address field. Specifically, the address recorded in the address field can be the webpage address of another webpage besides the target webpage, so as to avoid direct access to the target webpage by redirecting to other webpages through the address field. In this case, the address recorded in the address field can be understood as a hidden address or a proxy address. In addition, the address recorded in the address field can also be an encrypted webpage address obtained by encrypting or masking the webpage address of the target webpage using technical means. In this case, the address recorded in the address field can be understood as an encrypted webpage address of the target webpage.

[0103] In practical applications, when the address field contained in the webpage address information cannot directly access the target webpage, the address recorded in the address field can be used to redirect traffic to the application, thereby increasing the application's access traffic. Specifically, the address field contained in the webpage address information can be set as the webpage address used to redirect traffic to the application. Correspondingly, the webpage corresponding to the address field contained in the webpage address information can be a referral webpage used to redirect traffic to the application; optionally, the webpage corresponding to the address field includes: a download guide webpage used to download the application.

[0104] In this embodiment, in addition to the address field and the identifier field included in the web page address information, the web page address information may also include an access type field, that is, the web page address information includes an address field, an identifier field and an access type field; the access type field is used to indicate the type of web page access currently being performed through an NFC tag.

[0105] For example, the webpage address information stored in the NFC tag is "https: / / yourhost / landing.html?nfcCode=A". This webpage address information consists of three parts: an address field, an identifier field, and an access type field. Among them, the "https: / / yourhost / landing.html" field is the address field, which is the webpage address of the application's download guide webpage; the "nfcCode" field is the access type field, used to indicate webpage access via the NFC tag; and the "A" field is the identifier field, representing the webpage identifier of the application's target webpage.

[0106] In practice, during webpage access via communication with the NFC tag, the user terminal first obtains the webpage address information stored in the NFC tag. The obtained webpage address information includes an address field and an identification field. Based on the address field, the application is launched, and the webpage address information and launch type parameters are passed to the application. The application verifies whether the passed launch type parameters correspond to the NFC launch type. If the passed launch type parameters correspond to the NFC launch type, the application obtains the webpage address and access token mapped by the identification field from the server. Specifically, this is done by sending an address query request carrying the identification field to obtain the webpage address and access token mapped by the identification field.

[0107] Optionally, an address lookup request is sent if the application's launch type parameter corresponds to the NFC launch type. The correspondence between the launch type parameter and the NFC launch type can be determined after the user terminal launches the application based on the address field contained in the webpage address information and passes the webpage address information and launch type parameter to the application.

[0108] During execution, the application launched can be the application corresponding to the address field, specifically, the application corresponding to the application identifier contained in the address field can be launched. After the application is launched, the web page address information and launch type parameters are passed to the launched application for web page access within the application; in addition, the identifier field and launch type parameters can also be passed to the application, or the identifier field, access type field, and launch type parameters can be passed to the application.

[0109] The startup type parameter is generated by the user terminal's operating system. Specifically, when the user terminal's operating system detects that the service being launched is the user terminal's NFC service, it generates the startup type parameter corresponding to the NFC service.

[0110] For example, after obtaining the web address information "https: / / yourhost / landing.html?nfcCode=A" stored in the NFC tag, the application corresponding to the application identifier "yourhost" installed on the user terminal is launched based on the application identifier "yourhost" contained in the address field "https: / / yourhost / landing.html".

[0111] Step S404: Query the web address of the target webpage mapped by the identifier field, and generate an access token for the target webpage.

[0112] In practice, when querying the target webpage address mapped to the identifier field, the webpage address mapped to the identifier field can be retrieved from the mapping relationship table. That is, the webpage address can be obtained by querying the pre-established mapping relationship table based on the identifier field. The mapping relationship table is a pre-established data table used to record the mapping relationship between webpage identifiers and webpage addresses. The webpage addresses recorded in the mapping relationship table are the actual webpage addresses. After retrieving the target webpage address from the mapping relationship table, the current target webpage can be accessed within the application based on the retrieved webpage address.

[0113] For example, if the webpage address "https: / / yourhost / landing.html?nfcCode=A" contains an identifier field "A", the application sends an address query request carrying the identifier field "A" to the server. The server then performs a webpage address lookup based on the identifier field "A" in a pre-established mapping table. The retrieved target webpage address is "yourapp: / / page / activity?p1=xxx". Further, a one-time random number (token) is generated using a random number generation algorithm as an access token for the target webpage. The retrieved target webpage address "yourapp: / / page / activity?p1=xxx" is concatenated with the generated random number (token) to obtain the webpage address information mapped to the identifier field "A", "yourapp: / / page / activity?p1=xxx&tk=token", which is then sent to the application.

[0114] Step S406: Return the webpage address and the access token to the application in response to the address query request.

[0115] In one optional implementation of this embodiment, returning a webpage address and an access token to an application includes: concatenating the webpage address and the access token to obtain webpage address information, and returning the webpage address information to the application; wherein the webpage address is obtained by querying a pre-established mapping table based on an identifier field.

[0116] Step S408: Use the application to access the target webpage and perform access authentication.

[0117] In the specific execution process, after the web address and access token are returned to the application, the application accesses the web page based on the web address and performs access authentication based on the access token. Specifically, the application accesses the target web page based on the web address and performs access authentication for the target web page during the web page access process. Correspondingly, this part works in conjunction with the application to access and authenticate the target web page.

[0118] Specifically, during webpage access and authentication, the application can obtain the webpage data corresponding to the webpage address from the server, that is, obtain the webpage data of the target webpage, load and execute the webpage data to obtain the target webpage, and before displaying the target webpage in the application, cooperate with the server to perform access authentication of the target webpage based on the access token. If the authentication is successful, the target webpage is displayed in the application; otherwise, if the authentication fails, an authentication failure reminder and a reminder to access the webpage again are displayed, or no action is taken.

[0119] In one optional implementation provided in this embodiment, access authentication includes:

[0120] The system checks whether the terminal information in the authentication request sent by the application is the same as the terminal information in the access record; if they are different, the authentication fails.

[0121] If they are the same, check if the access token is within its validity period. If it is, authentication is successful; otherwise, authentication is unsuccessful.

[0122] The validity period is determined based on the token generation time and the token's validity duration.

[0123] Furthermore, in scenarios where terminal information is detected during access authentication, after querying the target webpage address mapped by the identifier field and generating an access token for the target webpage, an access record of the application accessing the target webpage can be generated. This access record can then be used to detect the terminal information contained in the authentication request. In one optional implementation of this embodiment, after querying the target webpage address mapped by the identifier field and generating the access token for the target webpage, and before cooperating with the application to access the target webpage and before performing access authentication, the method further includes: generating an access record of the application accessing the target webpage; the access record includes terminal information and the token generation time.

[0124] It should be noted that steps S402 to S408 provided in this embodiment are executed by the server. The steps S402 to S408 executed by the server and steps S202 to S208 executed by the user terminal in the above embodiment can cooperate with each other during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S202 to S208 executed by the user terminal in the above method embodiment. When reading the method embodiment of steps S202 to S208 executed by the user terminal, please refer to the corresponding content of steps S402 to S408 provided in this embodiment.

[0125] The following example uses an NFC-based web page access method provided in this embodiment to illustrate its application in a web page access scenario. Figure 3 The NFC-based web page access method provided in this embodiment will be further explained below. Figure 3 An NFC-based web access method for web access scenarios includes the following steps.

[0126] Step S314: Receive an address query request carrying an identifier field sent by the application.

[0127] Step S316: Query the web address of the target webpage mapped by the identifier field in the mapping relationship table, and generate an access token for the target webpage.

[0128] Step S318: Return the web address and access token to the application in response to the address query request.

[0129] Step S326: Detect whether the terminal information contained in the authentication request sent by the application is the same as the terminal information in the access record;

[0130] If they are the same, proceed to step S328;

[0131] If they are different, the authentication has failed.

[0132] Step S328: Check if the access token is within its validity period;

[0133] If so, authentication is confirmed to be successful;

[0134] If not, the authentication has failed.

[0135] Step S330: Return the authentication result to the application.

[0136] It should be noted that any one or more of steps S302 to S312, S320 to S324, and S332 can be combined with any one or more of steps S402 to S408 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S302 to S312, S320 to S324, and S332 can be selected and combined with any one or more technical features provided in steps S402 to S408 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S302 to S312, S320 to S324, and S332 can also be replaced with any one or more technical features provided in steps S402 to S408 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0137] This specification provides an embodiment of an NFC-based web page access device as follows:

[0138] In the above embodiments, an NFC-based web page access method is provided, and correspondingly, an NFC-based web page access device is also provided, which will be described below with reference to the accompanying drawings.

[0139] Reference Figure 5 This illustration shows a schematic diagram of an embodiment of an NFC-based web page access device provided in this embodiment.

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

[0141] This embodiment provides an NFC-based web access device that operates on a user terminal. The device includes:

[0142] The address acquisition module 502 is configured to acquire web address information stored in the NFC tag; the web address information includes an address field and an identifier field;

[0143] The program startup module 504 is configured to launch the application based on the address field and pass the web page address information and startup type parameters to the application.

[0144] The startup verification module 506 is configured to verify, through the application, whether the startup type parameter corresponds to the NFC startup type;

[0145] If so, run the web access module 508;

[0146] The web page access module 508 is configured to obtain the web page address and access token mapped by the identification field from the server, perform web page access based on the web page address, and perform access authentication based on the access token.

[0147] Another embodiment of an NFC-based web access device provided in this specification is as follows:

[0148] In the above embodiments, another NFC-based web page access method is provided, and correspondingly, another NFC-based web page access device is also provided, which will be described below with reference to the accompanying drawings.

[0149] Reference Figure 6 This illustration shows a schematic diagram of an embodiment of an NFC-based web page access device provided in this embodiment.

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

[0151] This embodiment provides an NFC-based web access device, which runs on a server. The device includes:

[0152] The request receiving module 602 is configured to receive an address query request sent by an application, which carries an identification field; the identification field is obtained from the web address information stored in the NFC tag.

[0153] The address query module 604 is configured to query the web address of the target webpage mapped by the identifier field and generate an access token for the target webpage.

[0154] Address return module 606 is configured to return the web page address and the access token to the application in response to the address query request;

[0155] The web page access module 608 is configured to cooperate with the application to access and authenticate the target web page.

[0156] This specification provides an example of an NFC-based web access device as follows:

[0157] Corresponding to the NFC-based web page access method described above, and based on the same technical concept, one or more embodiments of this specification also provide an NFC-based web page access device, which is used to execute the NFC-based web page access method provided above. Figure 7 This is a schematic diagram of the structure of an NFC-based web access device provided for one or more embodiments of this specification.

[0158] This embodiment provides an NFC-based web access device, comprising:

[0159] like Figure 7 As shown, NFC-based web access devices can vary significantly due to differences in configuration or performance. They may include one or more processors 701 and memory 702, with memory 702 storing one or more applications or data. Memory 702 can be temporary or persistent storage. The applications stored in memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the NFC-based web access device. Furthermore, processor 701 may be configured to communicate with memory 702, executing the series of computer-executable instructions in memory 702 on the NFC-based web access device. NFC-based web access devices may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0160] In one specific embodiment, the NFC-based web access device 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 the NFC-based web access device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0161] Obtain the webpage address information stored in the NFC tag; the webpage address information includes an address field and an identifier field;

[0162] The application is launched based on the address field, and the webpage address information and launch type parameters are passed to the application.

[0163] The application verifies whether the startup type parameter corresponds to the NFC startup type.

[0164] If so, obtain the web address and access token mapped by the identification field from the server, access the web page based on the web address, and perform access authentication based on the access token.

[0165] Another embodiment of an NFC-based web access device provided in this specification is as follows:

[0166] Corresponding to the other NFC-based web page access method described above, based on the same technical concept, one or more embodiments of this specification also provide another NFC-based web page access device, which is used to execute the other NFC-based web page access method provided above. Figure 8 This is a schematic diagram of the structure of an NFC-based web access device provided for one or more embodiments of this specification.

[0167] Another NFC-based web access device provided in this embodiment includes:

[0168] like Figure 8 As shown, NFC-based web access devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memory 802, with memory 802 storing one or more applications or data. Memory 802 can be temporary or persistent storage. The applications stored in memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions for the NFC-based web access device. Furthermore, processor 801 may be configured to communicate with memory 802, executing the series of computer-executable instructions in memory 802 on the NFC-based web access device. NFC-based web access devices may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0169] In one specific embodiment, the NFC-based web access device 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 the NFC-based web access device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0170] Receive an address query request sent by the application, which carries an identification field; the identification field is obtained from the web address information stored in the NFC tag;

[0171] Query the webpage address of the target webpage mapped by the identifier field, and generate an access token for the target webpage;

[0172] Return the webpage address and the access token to the application in response to the address query request;

[0173] The application is used to access and authenticate the target webpage.

[0174] This specification provides an embodiment of a computer-readable storage medium as follows:

[0175] Corresponding to the NFC-based web page access method described above, and based on the same technical concept, one or more embodiments of this specification also provide a 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:

[0177] Obtain the webpage address information stored in the NFC tag; the webpage address information includes an address field and an identifier field;

[0178] The application is launched based on the address field, and the webpage address information and launch type parameters are passed to the application.

[0179] The application verifies whether the startup type parameter corresponds to the NFC startup type.

[0180] If so, obtain the web address and access token mapped by the identification field from the server, access the web page based on the web address, and perform access authentication based on the access token.

[0181] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of an NFC-based web page access method 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.

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

[0183] Corresponding to the other NFC-based web page access method described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0184] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0185] Receive an address query request sent by the application, which carries an identification field; the identification field is obtained from the web address information stored in the NFC tag;

[0186] Query the webpage address of the target webpage mapped by the identifier field, and generate an access token for the target webpage;

[0187] Return the webpage address and the access token to the application in response to the address query request;

[0188] The application is used to access and authenticate the target webpage.

[0189] It should be noted that the embodiments of another computer-readable storage medium described in this specification and the embodiments of another NFC-based web page access method 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.

[0190] This specification provides an example of a computer program product as follows:

[0191] Corresponding to the NFC-based web page access method described above, and based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0192] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps:

[0193] Obtain the webpage address information stored in the NFC tag; the webpage address information includes an address field and an identifier field;

[0194] The application is launched based on the address field, and the webpage address information and launch type parameters are passed to the application.

[0195] The application verifies whether the startup type parameter corresponds to the NFC startup type.

[0196] If so, obtain the web address and access token mapped by the identification field from the server, access the web page based on the web address, and perform access authentication based on the access token.

[0197] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of an NFC-based web page access method 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.

[0198] Another example of a computer program product provided in this specification is as follows:

[0199] Corresponding to the other NFC-based web page access method described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0200] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps:

[0201] Receive an address query request sent by the application, which carries an identification field; the identification field is obtained from the web address information stored in the NFC tag;

[0202] Query the webpage address of the target webpage mapped by the identifier field, and generate an access token for the target webpage;

[0203] Return the webpage address and the access token to the application in response to the address query request;

[0204] The application is used to access and authenticate the target webpage.

[0205] It should be noted that the embodiment of another computer program product described in this specification and the embodiment of another NFC-based web page access method 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.

[0206] 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 embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments are all similar to the method embodiments, so the descriptions are relatively simple. For reading the relevant content of the device embodiments, equipment embodiments, computer-readable storage medium embodiments, and computer program product embodiments, please refer to the description of the method embodiments.

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

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

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

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

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

[0212] 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-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0213] 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 NFC-based web access device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable NFC-based web access device, 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.

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

[0215] These computer program instructions can also be loaded onto a computer or other programmable NFC-based web access device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device 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.

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

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

[0218] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, 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.

[0219] 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 at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

[0221] 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 NFC-based webpage access method applied to a user terminal, the method comprising: obtaining webpage address information stored in an NFC tag; the webpage address information comprising an address field and an identification field; starting an application based on the address field, and transmitting the webpage address information and a start type parameter to the application; verifying whether the start type parameter corresponds to a NFC start type through the application; if yes, obtaining a webpage address and an access token mapped by the identification field from a server, obtaining webpage data corresponding to the webpage address from the server, loading and executing the webpage data to obtain a target webpage, submitting an authentication request carrying the access token to the server, and displaying the target webpage in the application if an authentication result returned by the server is authentication passed. 2.The NFC-based webpage access method according to claim 1, after the step of obtaining webpage address information stored in an NFC tag is executed, and before the step of starting an application based on the address field, and transmitting the webpage address information and a start type parameter to the application is executed, the method further comprises: detecting whether the user terminal is installed with an application corresponding to the address field; if yes, executing the step of starting an application based on the address field, and transmitting the webpage address information and a start type parameter to the application; if no, starting a browser installed in the user terminal, obtaining webpage data of a webpage corresponding to the address field from the server through the browser, and performing webpage loading and display.

3. The NFC-based web page access method of claim 2, the web page corresponding to the address field comprising: a download guide webpage for downloading the application. 4.The NFC-based webpage access method according to claim 1, the step of obtaining a webpage address and an access token mapped by the identification field from a server comprises: sending an address query request carrying the identification field to the server; receiving webpage address information mapped by the identification field returned by the server, and analyzing the received webpage address information to obtain the webpage address and the access token. 5.The NFC-based webpage access method according to claim 4, the webpage address information mapped by the identification field is obtained in the following manner: querying a webpage address of a target webpage mapped by the identification field in a pre-established mapping relationship table, and generating an access token of the target webpage; splicing the queried webpage address and the generated access token to obtain the webpage address information mapped by the identification field.

6. The NFC-based web page access method of claim 5, the target web page comprising: a webpage for service recommendation in the application. 7.The NFC-based webpage access method according to claim 1, the step of obtaining webpage address information stored in an NFC tag comprises: establishing communication with the NFC tag, and sending a query signal to the NFC tag; receiving the webpage address information returned by the NFC tag in response to the query signal. 8.A NFC-based webpage access method applied to a server, the method comprising: receiving an address query request carrying an identification field sent by an application; the identification field being obtained from webpage address information stored in an NFC tag; query a web address of a target web page mapped by the identification field, and generate an access token of the target web page; return the web address and the access token to the application in response to the address query request; cooperate with the application to perform web access and access authentication of the target web page; the access authentication comprises: detecting whether terminal information contained in an authentication request sent by the application is same as terminal information in an access record of the target web page; if not, determining that the authentication fails; if yes, detecting whether the access token is within a valid period; if yes, determining that the authentication passes; if not, determining that the authentication fails.

9. The NFC-based web page access method according to claim 8, wherein the address query request is sent in a case where a start type parameter of the application is transmitted to the application and corresponds to an NFC start type.

10. The NFC-based web page access method according to claim 8, wherein the returning of the web address and the access token to the application comprises: splicing the web address and the access token to obtain web address information, and returning the web address information to the application; wherein the web address is obtained based on the identification field in a pre-established mapping relationship table.

11. The NFC-based web page access method of claim 8, wherein the web page address information includes an address field corresponding to a web page comprising: a download guide web page for downloading the application; the target web page comprises a web page for service recommendation in the application.

12. The NFC-based web page access method according to claim 8, after the step of querying a web address of a target web page mapped by the identification field and generating an access token of the target web page is executed, and before the step of cooperating with the application to perform web access and access authentication of the target web page is executed, further comprising: generating an access record of the target web page accessed by the application; the access record comprises terminal information and token generation time.

13. The NFC-based web page access method according to claim 12, wherein the valid period is determined according to the token generation time and token valid duration.

14. An NFC-based web page access device running on a user terminal, the device comprising: an address acquisition module configured to acquire web address information stored by an NFC tag; the web address information comprises an address field and an identification field; a program start module configured to start an application based on the address field, and transmit the web address information and a start type parameter to the application; a start verification module configured to verify, by the application, whether the start type parameter corresponds to an NFC start type; if yes, run a web access module; the web access module is configured to acquire a web address and an access token mapped by the identification field from a server, acquire web page data corresponding to the web address from the server, load and execute the web page data to obtain a target web page, submit an authentication request carrying the access token to the server, and if an authentication result returned by the server is that the authentication passes, display the target web page in the application.

15. A NFC-based web page access apparatus running on a server, comprising: a request receiving module configured to receive an address query request sent by an application program and carrying an identification field; the identification field is obtained from web page address information stored in an NFC tag; an address query module configured to query a web page address of a target web page mapped by the identification field and generate an access token of the target web page; an address returning module configured to return the web page address and the access token to the application program in response to the address query request; a web page access module configured to cooperate with the application program to perform web page access and access authentication of the target web page; the access authentication comprises: detecting whether terminal information contained in an authentication request sent by the application program is same as terminal information in an access record of the target web page; if not, determining that the authentication fails; if yes, detecting whether the access token is within a valid period; if yes, determining that the authentication passes; if not, determining that the authentication fails.

16. A NFC-based web page access device, comprising: a processor; and a memory configured to store computer executable instructions which, when executed, cause the processor to: obtain web page address information stored in an NFC tag; the web page address information contains an address field and an identification field; start an application program based on the address field and input the web page address information and a start type parameter to the application program; verify, by the application program, whether the start type parameter corresponds to an NFC start type; if yes, obtain a web page address and an access token mapped by the identification field from a server, obtain web page data corresponding to the web page address from the server, load and execute the web page data to obtain a target web page, submit an authentication request carrying the access token to the server, and if an authentication result returned by the server is that the authentication passes, display the target web page in the application program.

17. A NFC-based web page access device, comprising: a processor; and a memory configured to store computer executable instructions which, when executed, cause the processor to: receive an address query request sent by an application program and carrying an identification field; the identification field is obtained from web page address information stored in an NFC tag; query a web page address of a target web page mapped by the identification field and generate an access token of the target web page; return the web page address and the access token to the application program in response to the address query request; cooperate with the application program to perform web page access and access authentication of the target web page; the access authentication comprises: detecting whether terminal information contained in an authentication request sent by the application program is same as terminal information in an access record of the target web page; if not, determining that the authentication fails; if yes, detecting whether the access token is within a valid period; if yes, determining that the authentication passes; if not, determining that the authentication fails.

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

19. A computer readable storage medium for storing computer executable instructions that, when executed, implement the steps of the method of claim 8.

Images