Webpage access method and device based on NFC

Abstract

The embodiment of the invention provides a webpage access method and device based on NFC, and the method comprises the steps: obtaining an NFC label address field and an identification field in a webpage access process, starting an application program based on the address field, and transmitting parameters to the application program, and verifying whether the introduced starting type parameter corresponds to the NFC starting type or not through the application program, if so, obtaining the webpage address and the access token mapped by the identification field from the server side, and performing webpage access based on the webpage address and performing access authentication based on the access token, thereby realizing webpage access in the application program through communication with the NFC tag.

Description

Technical Field

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

[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 through the scan function of the application installed on the terminal device to access the web page, or click on the hyperlink to access the web page, or "stick" NFC (Near Field Communication) tags to access the web page. However, many actual scenarios have put forward higher requirements on the security of web page access. Summary of the invention

[0003] One or more embodiments of the present specification provide a web page access method based on NFC, which is applied to a user terminal, and the method includes: obtaining web page address information stored in an NFC tag. The web page address information includes an address field and an identification field. An application is started based on the address field, and the web page address information and a startup type parameter are passed to the application. The startup type parameter is verified by the application to see whether it corresponds to the NFC startup type. If so, the web page address and access token mapped by the identification field are obtained from the server, and the web page is accessed based on the web page address and access authentication is performed based on the access token.

[0004] One or more embodiments of the present specification provide another NFC-based web page access method, which is applied to a server, and the method includes: receiving an address query request carrying an identification field sent by an application. The identification field is obtained from the address information stored in the NFC tag. Querying the web page address of the target web page mapped by the identification field, and generating an access token for the target web page. Returning the web page address and the access token to the application in response to the address query request. Cooperating with the application to perform web page access and access authentication for the target web page.

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

[0006] One or more embodiments of the present specification provide another NFC-based web page access device, which runs on a server side, and the device includes: a request receiving module, which is configured to receive an address query request carrying an identification field sent by an application. The identification field is obtained from the address information stored in the NFC tag. The address query module is 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. The address return module is configured to return the web page address and the access token to the application in response to the address query request. The web page access module is configured to cooperate with the application to perform web page access and access authentication for the target web page.

[0007] One or more embodiments of the present specification provide an NFC-based web page access device, including: a processor; and a memory configured to store computer executable instructions, wherein the computer executable instructions, when executed, cause the processor to: obtain web page address information stored in an NFC tag. The web page address information includes an address field and an identification field. An application is started based on the address field, and the web page address information and startup type parameters are passed to the application. The startup type parameter is verified by the application to see whether it corresponds to the NFC startup type. If so, the web page address and access token mapped by the identification field are obtained from the server, and web page access is performed based on the web page address and access authentication is performed based on the access token.

[0008] One or more embodiments of the present specification provide another NFC-based web page access device, including: 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 the address information stored in the NFC tag. 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. Return the web page address and the access token to the application in response to the address query request. Cooperate with the application to perform web page access and access authentication for the target web page.

[0009] One or more embodiments of the present specification provide a computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: obtain web page address information stored in an NFC tag. The web page address information includes an address field and an identification field. Start an application based on the address field, and pass the web page address information and startup type parameters to the application. Verify through the application whether the startup type parameter corresponds to the NFC startup type. If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

[0010] One or more embodiments of the present specification provide another computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: receiving an address query request carrying an identification field sent by an application. The identification field is obtained from the address information stored in the NFC tag. 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. Return the web page address and the access token to the application in response to the address query request. Cooperate with the application to perform web page access and access authentication for the target web page. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 A schematic diagram of an implementation environment of an NFC-based web page access method provided for one or more embodiments of this specification; Figure 2A processing flow chart of a web page access method based on NFC provided in one or more embodiments of this specification; Figure 3 A processing sequence diagram of a web page access method based on NFC applied to a web page access scenario provided in one or more embodiments of this specification; Figure 4 A schematic diagram of another implementation environment of an NFC-based web page access method provided for one or more embodiments of this specification; Figure 5 A schematic diagram of an embodiment of an NFC-based web page access device provided in one or more embodiments of this specification; Figure 6 A schematic diagram of another embodiment of an NFC-based webpage access device provided in one or more embodiments of this specification; Figure 7 A schematic diagram of the structure of a web page access device based on NFC provided in one or more embodiments of this specification; Figure 8 A schematic diagram of the structure of another NFC-based web page access device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0012] In order 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 in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0013] The NFC-based web page access method provided in one or more embodiments of this specification can be applied to the implementation environment of web page access. Figure 1 , the implementation environment at least includes: NFC tag 101, user terminal 102 and server 103; Wherein, the NFC tag 101 is used to store web page address information including an address field and an identification field; The user terminal 102 is installed with an application 102-1 and an NFC service 102-2. The NFC service 102-2 is used to communicate with the NFC tag 101. The application 102-1 cooperates with the server 103 to access a web page within the application 102-1. The user terminal 102 may be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality), a vehicle terminal, an IoT device, a wearable smart device, a laptop computer, a desktop computer, etc. The server 103 is used to cooperate with the application 102-1 to access the web page and perform access authentication during the web page access process.

[0014] In this implementation environment, after the NFC service 102-2 installed in the user terminal 102 establishes communication with the NFC tag 101, it obtains the web page address information including the address field and the identification field from the NFC tag 101. After obtaining the address field and the identification field, the user terminal 102 starts the application 102-1 based on the address field, and transmits the web page address information and the startup type parameter to the application 102-1. The application 102-1 verifies whether the transmitted startup type parameter corresponds to the NFC startup type. If it corresponds, the application 102-1 obtains the web page address and access token mapped by the identification field from the server 103 according to the transmitted identification field, accesses the web page based on the obtained web page address, and cooperates with the server 103 to perform access authentication of the access token, thereby avoiding the risk that the target web page can be directly accessed through the address field stored in the NFC tag 101, ensuring that the web page can be accessed in the application 102-1 only through communication with the NFC tag 101, thereby improving the security of web page access in the application 102-1.

[0015] One or more embodiments of a web page access method based on NFC provided in this specification are as follows: Reference Figure 2 The NFC-based web page access method provided in this embodiment can be applied to a user terminal. The method specifically includes steps S202 to S208.

[0016] Step S202, obtaining the web page address information stored in the NFC tag.

[0017] The NFC tag described in this embodiment refers to an NFC material or an NFC device used for accessing a web page, and the NFC tag stores web page address information; the web page address information refers to information related to web page access, and optionally, the web page address information includes an address field and an identification field; Among them, the identification field records the web page identification, and the web page corresponding to the web page identification refers to the target web page to be accessed currently. Optionally, the target web page includes a web page embedded in the application; optionally, the target web page can be a web page for service recommendation in the application; the application can be a third-party application other than the browser, such as a payment application, etc. In order to avoid the web page address information stored in the NFC tag from being leaked, which leads to the web page address of the target web page being leaked, this embodiment does not record the web page address of the target web page in the web page address information, but only indicates through the identification field that the web page to be accessed currently is the target web page corresponding to the identification field.

[0018] In this embodiment, in order to avoid the risk that the webpage address information stored in the NFC tag is leaked and the target webpage can be directly accessed 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 directly accessed 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 started in the user terminal, that is, the address field can be used to determine in which application to access the webpage; Specifically, the address recorded in the address field can be understood as an address field that can avoid directly accessing the target web page through the address field. Specifically, the address recorded in the address field can be the web page address of other web pages other than the target web page, and the address field is used to guide to other web pages to avoid directly accessing the target web page 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 web page address obtained by encrypting or masking the web page address of the target web page by technical means. In this case, the address recorded in the address field can be understood as the encrypted web page address of the target web page.

[0019] In actual applications, when the address field contained in the web page address information cannot directly access the target web page, the address recorded in the address field can be used to divert the application to increase the access traffic of the application. Specifically, the address field contained in the web page address information can be set to the web page address used to divert the application. Accordingly, the web page corresponding to the address field contained in the web page address information can be a diversion web page for diverting the application; optionally, the web page corresponding to the address field includes: a download guide web page for downloading the application.

[0020] In this embodiment, on the basis that the web page address information includes the address field and the identification field, the web page address information may also include an access type field, that is, the web page address information includes the address field, the identification field and the access type field; the access type field is used to indicate that the current web page access is a type field for accessing the web page through an NFC tag.

[0021] For example, the web page address information stored in the NFC tag is “https: / / yourhost / landing.html?nfcCode=A”, which consists of three parts: address field, identification field and access type field; The field “https: / / yourhost / landing.html” is an address field, which is the web address of the download guide web page of the application; The "nfcCode" field is the access type field, indicating that the web page is accessed through an NFC tag; The "A" field is an identification field, indicating the web page identification of the target web page of the application.

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

[0023] As described above, the function of the address field included in the web address information is to determine the application to be started on the user terminal, that is, the address field can be used to determine in which application the web page is accessed. In actual scenarios, when the user terminal obtains the web page address information stored in the NFC tag to access the web page, there may be a situation where the user terminal has installed the application corresponding to the address field. In this case, the application corresponding to the address field is started and the web page is accessed through the application. In addition, there may also be a situation where the user terminal does not have the application corresponding to the address field installed. In this case, the web page cannot be accessed through the application. In this case, the application can also be diverted through the address recorded in the address field to increase the access traffic of the application. Specifically, the webpage address information includes an address field to detect whether the user terminal has installed the application corresponding to the address field. If installed, the webpage access process is performed in the application corresponding to the address field through subsequent processing; if not, the corresponding webpage for diversion can be accessed with the help of the browser installed on the user terminal; Specifically, in an optional implementation provided by this embodiment, it is detected whether the user terminal has installed the application corresponding to the address field; If yes, execute the following step S204 to start the application based on the address field, and pass the webpage address information and the startup type parameter to the application; If not, start the browser installed in the user terminal, obtain the web page data of the web page corresponding to the address field from the server through the browser, and load and display the web page.

[0024] In addition, on the basis that the web address information includes the address field, the identification field and the access type field, in order to ensure that the web page can be accessed within the designated application of the user terminal only through the communication between the user terminal and the NFC tag, thereby further improving the security of web page access, in an optional implementation manner provided by this embodiment, after obtaining the web page address information stored in the NFC tag, it is also possible to determine whether the access type field contained in the web page address information is a preset type field, for example, determine whether the access type field contained in the web page address information stored in the NFC tag is the access type field of "nfcCode", and if so, execute step S204 or execute the above-mentioned operation of detecting whether the user terminal has installed the application corresponding to the address field; if not, generate an access failure reminder or do not process it; or, it is also possible to determine whether the web page address information contains the access type field, and if so, execute step S204 or execute the above-mentioned operation of detecting whether the user terminal has installed the application corresponding to the address field; if not, generate an access failure reminder or do not process it.

[0025] Step S204: starting an application based on the address field, and passing the webpage address information and startup type parameters to the application.

[0026] After obtaining the web page address information stored in the NFC tag as mentioned above, the web page address information can be parsed, and the address field and identification field contained in the web page address information can be extracted according to the parsing results, or the address field, identification field and access type field contained in the web page address information can be extracted according to the parsing results for subsequent web page access processing based on the address field and identification field, or subsequent web page access processing can be performed based on the address field, identification field and access type field.

[0027] In specific implementation, in the process of starting an application according to the address field, the started application may be the application corresponding to the address field, that is, the application corresponding to the address field is started, and specifically the application corresponding to the application identifier may be started according to the application identifier contained in the address field. After the application is started, the web page address information and the startup type parameter are passed to the started application for accessing the web page within the application; in addition, the identification field and the startup type parameter may be passed to the application, or the identification field, the access type field and the startup type parameter may be passed to the application.

[0028] The startup type parameter is generated by the operating system of the user terminal. Specifically, when the operating system of the user terminal detects that the service of the application startup is the NFC service startup of the user terminal, it generates a startup type parameter corresponding to the NFC service.

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

[0030] Step S206: Verify, by the application program, whether the startup type parameter corresponds to the NFC startup type.

[0031] During the specific execution process, on the basis of starting the application and passing the web page address information and the startup type parameter to the application, the application accesses the web page according to the passed web page address information and the startup type parameter. Specifically, during the web page access process, in order to ensure that the web page access can be performed in the application only through the communication between the user terminal and the NFC tag, here, by verifying whether the startup type parameter corresponds to the NFC startup type, it is verified whether the web page access currently performed in the application is a web page access triggered by interaction with the NFC tag; If the startup type parameter corresponds to the NFC startup type, it indicates that the current web page access in the application is a web page access triggered by interaction with the NFC tag, and the following step S208 is executed to perform corresponding web page access processing in the application; If the startup type parameter does not correspond to the NFC startup type, it indicates that the current web page access in the application is not triggered by interaction with the NFC tag. In order to ensure that the web page can be accessed in the application only through communication between the user terminal and the NFC tag, in this case, an access failure reminder can be generated or no processing can be performed.

[0032] It should be noted that, when the web page address information includes an address field, an identification field, and an access type field, in order to ensure that the web page can be accessed within the designated application of the user terminal only through communication between the user terminal and the NFC tag, thereby improving the security of web page access, in an optional implementation manner provided in this embodiment, before verifying whether the startup type parameter corresponds to the NFC startup type through the application, the application can also determine whether the access type field contained in the web page address information is a preset type field, for example, determine whether the access type field contained in the web page address information stored from the NFC tag is the access type field of "nfcCode", and if so, execute the verification through the application whether the startup type parameter corresponds to the NFC startup type operation; if not, generate an access failure reminder or do not process it; or, the application can determine whether the web page address information contains an access type field, and if so, verify whether the startup type parameter corresponds to the NFC startup type operation through the application; if not, generate an access failure reminder or do not process it.

[0033] Step S208, obtaining the web page address and access token mapped by the identification field from the server, accessing the web page based on the web page address, and performing access authentication based on the access token.

[0034] During the process of accessing a web page within an application, in order to ensure that the web page can be accessed within the application only through communication between the user terminal and the NFC tag, the application verifies whether the startup type parameter corresponds to the NFC startup type to verify whether the current web page access within the application is the web page access performed through communication with the NFC tag. When the startup type parameter corresponds to the NFC startup type, that is, when the current web page access within the application is the web page access performed through communication with the NFC tag, the application obtains the web page address and access token mapped by the identification field from the server, accesses the web page based on the web page address, and performs access authentication based on the access token.

[0035] In specific implementation, in the process of obtaining the web page address and access token mapped by the identification field from the server, the application can request the web page address and access token from the server by sending the identification field to the server or sending an address query request carrying the identification field. After receiving the identification field, the server queries the web page address mapped by the identification field according to the mapping relationship table and generates an access token, and returns the web page address and access token to the application.

[0036] In an optional implementation manner provided by this embodiment, obtaining the webpage address and access token mapped by the identification field from the server includes: Send an address query request with an identification field to the server; Receive the web page address information mapped by the identification field returned by the server, and parse the received web page address information to obtain the web page address and access token.

[0037] Optionally, the web page address information of the identification field mapping is obtained in the following manner: Querying the webpage address of the target webpage mapped by the identification field in the pre-established mapping relationship table, and generating an access token for the target webpage; The queried web page address is concatenated with the generated access token to obtain the web page address information mapped by the identification field.

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

[0039] Continuing with the above example, the webpage address information "https: / / yourhost / landing.html?nfcCode=A" contains the identification field "A". After the application sends the address query request carrying the identification field "A" to the server, the server performs a webpage address query in the pre-established mapping relationship table according to the identification field "A". The webpage address of the queried target webpage is: "yourapp: / / page / activity?p1=xxx"; further, a one-time random number (token) is generated through a random number generation algorithm as an access token for accessing the target webpage, and the webpage address of the queried target webpage "yourapp: / / page / activity?p1=xxx" is concatenated with the generated random number (token) to obtain the webpage address information "yourapp: / / page / activity?p1=xxx&tk=token" mapped by the identification field "A", and the webpage address information is sent to the application.

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

[0041] In the process of web page access and access authentication, the application can obtain the web page data corresponding to the web page address from the server, that is, obtain the web page data of the target web page, load and execute the web page data to obtain the target web page, and cooperate with the server to perform access authentication of the target web page based on the access token before displaying the target web page in the application. If the authentication is successful, the target web page is displayed in the application; otherwise, if the authentication fails, an authentication failure reminder, a web page re-access reminder or no processing is performed.

[0042] In an optional implementation manner provided by this embodiment, web page access is performed based on the web page address and access authentication is performed based on the access token, including: Obtain web page data corresponding to the web page address from the server, load and execute the web page data to obtain the target web page; Submit an authentication request with an access token to the server; If the authentication result returned by the server is authentication passed, the target web page is displayed in the application.

[0043] During the specific execution process, after receiving the authentication request carrying the access token, the server performs access authentication of the access token. The access authentication of the access token performed by the server can be implemented in the following ways: Check whether the terminal information included in the authentication request is the same as the terminal information in the access record; if not, determine that the authentication has failed; If they are the same, check whether the access token is within the validity period. If so, determine that the authentication is successful. If not, determine that the authentication is not successful. Optionally, the validity period is determined based on the token generation time and the token validity period. Terminal information refers to the terminal device information of the user terminal, such as the model information and / or operating system information of the user terminal.

[0044] To summarize, the NFC-based web page access method provided in the present embodiment stores web page address information including an address field and an identification field in an NFC tag, where the address field may be a hidden address, a proxy address or an encrypted web page address, thereby avoiding the risk of the web page address of the target web page being leaked due to the storage of the web page address in the NFC tag. Based on this, in the process of accessing the web page based on communication with the NFC tag, the web page address information is obtained from the NFC tag, the application is started based on the address field contained in the web page address information, and the web page address information and the startup type parameter are transmitted to the application. The application verifies whether the current web page access in the application is a web page access performed through communication with the NFC tag by verifying whether the startup type parameter corresponds to the NFC startup type. If the startup type parameter corresponds to the NFC startup type, the web page address and the access token mapped by the identification field are obtained from the server, and the web page access is performed based on the web page address and the access authentication is performed based on the access token, thereby ensuring that the web page access in the application can only be performed through communication with the NFC tag, thereby improving the security of web page access performed through communication with the NFC tag.

[0045] The following takes the application of an NFC-based web page access method provided in this embodiment in a web page access scenario as an example, combined with Figure 3 , the NFC-based web page access method provided in this embodiment is further described, see Figure 3 , an NFC-based web page access method applied to a web page access scenario, specifically includes the following steps.

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

[0047] Step S304: receiving the webpage address information returned by the NFC tag in response to the query signal.

[0048] The web page address information includes an address field and an identification field.

[0049] Step S306, detecting whether the user terminal has installed the application corresponding to the address field; If yes, execute the following steps S308 to S310; If not, start the browser installed in the user terminal, obtain 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.

[0050] Step S308: starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application.

[0051] Step S310, verifying through the application whether the activation type parameter corresponds to the NFC activation type; If yes, execute the following step S312; If not, generate an access failure reminder or do nothing.

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

[0053] Step S320, receiving the web page address and access token returned by the server.

[0054] Step S322, obtaining web page data corresponding to the web page address from the server, loading and executing the web page data to obtain the target web page.

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

[0056] Step S332: If the authentication result returned by the server is that the authentication is passed, the target web page is displayed in the application.

[0057] The above-mentioned steps S302 to S312, steps S320 to S324 and step S332 provided in this embodiment are executed by the user terminal. It should be noted that the above-mentioned steps S302 to S312, steps S320 to S324 and step S332 executed by the user terminal and steps S314 to S318 and steps S326 to S330 executed by the server in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S314 to S318 and steps S326 to S330 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S302 to S312, steps S320 to S324 and step S332 provided in this embodiment.

[0058] It should be noted that any one or any combination of steps in steps S302 to S312, steps S320 to S324 and step S332 can be combined with any one or any combination of steps in the above steps S202 to S208 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S302 to S312, steps S320 to S324 and step S332 can be selected and combined with any one or more technical features provided in the above steps S202 to S208 to form a new implementation method; or, any one or any combination of technical features in steps S302 to S312, steps S320 to S324 and step S332 can be replaced with any one or more technical features provided in the above steps S202 to S208 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0059] One or more embodiments of another NFC-based web page access method provided in this specification are as follows: Reference Figure 4 The NFC-based web page access method provided in this embodiment can be applied to the server, and the method specifically includes steps S402 to S408.

[0060] Step S402: receiving an address query request carrying an identification field sent by an application.

[0061] In this embodiment, the identification field can be obtained from the web page address information stored in the NFC tag. The NFC tag refers to an NFC material or NFC device used to access a web page, and the NFC tag stores the web page address information; the web page address information refers to information related to web page access, and optionally, the web page address information includes an address field and an identification field; Among them, the identification field records the web page identification, and the web page corresponding to the web page identification refers to the target web page to be accessed currently. Optionally, the target web page includes a web page embedded in the application; optionally, the target web page can be a web page for service recommendation in the application; the application can be a third-party application other than the browser, such as a payment application, etc. In order to avoid the web page address information stored in the NFC tag from being leaked, which leads to the web page address of the target web page being leaked, this embodiment does not record the web page address of the target web page in the web page address information, but only indicates through the identification field that the web page to be accessed currently is the target web page corresponding to the identification field.

[0062] In this embodiment, in order to avoid the risk that the webpage address information stored in the NFC tag is leaked and the target webpage can be directly accessed 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 directly accessed 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 started in the user terminal, that is, the address field can be used to determine in which application to access the webpage; Specifically, the address recorded in the address field can be understood as an address field that can avoid directly accessing the target web page through the address field. Specifically, the address recorded in the address field can be the web page address of other web pages other than the target web page, and the address field is used to guide to other web pages to avoid directly accessing the target web page 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 web page address obtained by encrypting or masking the web page address of the target web page by technical means. In this case, the address recorded in the address field can be understood as the encrypted web page address of the target web page.

[0063] In actual applications, when the address field contained in the web page address information cannot directly access the target web page, the address recorded in the address field can be used to divert the application to increase the access traffic of the application. Specifically, the address field contained in the web page address information can be set to the web page address used to divert the application. Accordingly, the web page corresponding to the address field contained in the web page address information can be a diversion web page for diverting the application; optionally, the web page corresponding to the address field includes: a download guide web page for downloading the application.

[0064] In this embodiment, on the basis that the web page address information includes the address field and the identification field, the web page address information may also include an access type field, that is, the web page address information includes the address field, the identification field and the access type field; the access type field is used to indicate that the current web page access is a type field for accessing the web page through an NFC tag.

[0065] For example, the web page address information stored in the NFC tag is "https: / / yourhost / landing.html?nfcCode=A", which consists of three parts: address field, identification field and access type field; among them, the field "https: / / yourhost / landing.html" is the address field, which is the web address of the download guide web page of the application; the field "nfcCode" is the access type field, which is used to characterize web page access through the NFC tag; the field "A" is the identification field, which indicates the web page identification of the target web page of the application.

[0066] In specific implementation, during the process of accessing a web page by communicating with an NFC tag, the user terminal first obtains the web page address information stored in the NFC tag, the obtained web page address information includes an address field and an identification field, the application is started based on the address field, and the web page address information and startup type parameters are passed to the application; the application verifies whether the passed-in startup type parameters correspond to the NFC startup type, and if the passed-in startup type parameters correspond to the NFC startup type, the web page address and access token mapped by the identification field are obtained from the server, specifically by sending an address query request carrying the identification field to obtain the web page address and access token mapped by the identification field.

[0067] Optionally, the address query request is sent when the startup type parameter passed into the application corresponds to the NFC startup type. The startup type parameter corresponds to the NFC startup type, which can be determined after the user terminal starts the application based on the address field included in the web address information and passes the web address information and the startup type parameter to the application.

[0068] In the specific execution process, the application to be started may be the application corresponding to the address field, that is, the application corresponding to the address field is started, and the application corresponding to the application identifier may be started according to the application identifier contained in the address field. After the application is started, the web page address information and the startup type parameter are passed to the started application for accessing the web page within the application; in addition, the identification field and the startup type parameter may be passed to the application, or the identification field, the access type field and the startup type parameter may be passed to the application.

[0069] The startup type parameter is generated by the operating system of the user terminal. Specifically, when the operating system of the user terminal detects that the service of the application startup is the NFC service startup of the user terminal, it generates a startup type parameter corresponding to the NFC service.

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

[0071] Step S404, querying the webpage address of the target webpage mapped by the identification field, and generating an access token of the target webpage.

[0072] In specific implementation, in the process of querying the webpage address of the target webpage mapped by the identification field, the webpage address mapped by the identification field can be queried from the mapping relationship table, that is, the webpage address can be queried in the pre-established mapping relationship table based on the identification field. Among them, the mapping relationship table refers to a pre-established data table for recording the mapping relationship between the webpage identification and the webpage address. The webpage address recorded in the mapping relationship table is the real webpage address of the webpage. After the webpage address of the target webpage is queried from the mapping relationship table, the current target webpage can be accessed in the application based on the queried webpage address.

[0073] For example, the web address information "https: / / yourhost / landing.html?nfcCode=A" contains the identification field "A". After the application sends the address query request carrying the identification field "A" to the server, the server performs a web address query in the pre-established mapping relationship table according to the identification field "A", and the web address of the queried target web page is: "yourapp: / / page / activity?p1=xxx"; further, a one-time random number (token) is generated through a random number generation algorithm as an access token for accessing the target web page, and the web address of the queried target web page "yourapp: / / page / activity?p1=xxx" is concatenated with the generated random number (token) to obtain the web address information "yourapp: / / page / activity?p1=xxx&tk=token" mapped by the identification field "A", and the web address information is sent to the application.

[0074] Step S406: Return the web page address and the access token to the application program in response to the address query request.

[0075] In an optional implementation provided by this embodiment, a web page address and an access token are returned to an application, including: concatenating the web page address and the access token to obtain web page address information, and returning the web page address information to the application; wherein the web page address is obtained by querying a pre-established mapping relationship table based on an identification field.

[0076] Step S408: Cooperate with the application program to access the target web page and perform access authentication.

[0077] During the specific execution process, after the web page address and access token are returned to the application, the application accesses the web page based on the web page address and performs access authentication based on the access token. Specifically, web page access to the target web page is performed within the application based on the web page address, and access authentication to the target web page is performed during the web page access process. Accordingly, here, the application is cooperated to perform web page access and access authentication of the target web page.

[0078] Specifically, during the process of web page access and access authentication, the application can obtain the web page data corresponding to the web page address from the server, that is, obtain the web page data of the target web page, load and execute the web page data to obtain the target web page, and cooperate with the server to perform access authentication of the target web page based on the access token before displaying the target web page in the application. If the authentication is successful, the target web page is displayed in the application; otherwise, if the authentication fails, an authentication failure reminder, a web page re-access reminder, or no processing is performed.

[0079] In an optional implementation manner provided in this embodiment, access authentication includes: Check whether the terminal information contained in the authentication request sent by the application is the same as the terminal information in the access record; if not, determine that the authentication has failed; If they are the same, check whether the access token is within the validity period. If so, determine that the authentication is successful; if not, determine that the authentication is not successful; The validity period is determined based on the token generation time and the token validity period.

[0080] In addition, in the scenario where terminal information is detected during access authentication, after the web page address of the target web page mapped by the above-mentioned query identification field is queried and an access token for the target web page is generated, an access record of the application accessing the target web page can be generated, so as to detect the terminal information contained in the authentication request with the help of the generated access record. In an optional implementation provided by this embodiment, after the above-mentioned query of the web page address of the target web page mapped by the identification field is executed and the access token for the target web page is generated, and before the above-mentioned cooperation with the application to access the target web page and the access authentication is executed, it also includes: generating an access record of the application accessing the target web page; the access record includes terminal information and token generation time.

[0081] It should be noted that the above-mentioned steps S402 to S408 provided in this embodiment are executed by the server, and the above-mentioned steps S402 to S408 executed by the server and the steps S202 to S208 executed by the user terminal in the above-mentioned embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding content of steps S202 to S208 executed by the user terminal provided in the above-mentioned method embodiment, and 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.

[0082] The following takes the application of an NFC-based web page access method provided in this embodiment in a web page access scenario as an example, combined with Figure 3 , the NFC-based web page access method provided in this embodiment is further described, see Figure 3 , an NFC-based web page access method applied to a web page access scenario, specifically includes the following steps.

[0083] Step S314: receiving an address query request carrying an identification field sent by an application.

[0084] Step S316: query the webpage address of the target webpage mapped to the identification field in the mapping relationship table, and generate an access token for the target webpage.

[0085] Step S318, returning the web page address and access token to the application in response to the address query request.

[0086] Step S326, detecting whether the terminal information included in the authentication request sent by the application is the same as the terminal information in the access record; If they are the same, execute step S328; If they are different, it is determined that the authentication has failed.

[0087] Step S328, detecting whether the access token is within the validity period; If so, confirm that the authentication is successful; If not, it is determined that the authentication has not passed.

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

[0089] It should be noted that any one or any combination of steps in steps S302 to S312, steps S320 to S324 and step S332 can be combined with any one or any combination of steps in the above steps S402 to S408 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S302 to S312, steps S320 to S324 and step S332 can be selected and combined with any one or more technical features provided in the above steps S402 to S408 to form a new implementation method; or, any one or any combination of technical features in steps S302 to S312, steps S320 to S324 and step S332 can be replaced with any one or more technical features provided in the above steps S402 to S408 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0090] An embodiment of a web page access device based on NFC provided in this specification is as follows: In the above-mentioned embodiment, a web page access method based on NFC is provided, and correspondingly, a web page access device based on NFC is also provided, which is described below with reference to the accompanying drawings.

[0091] Reference Figure 5 , which shows a schematic diagram of an NFC-based web page access device embodiment provided in this embodiment.

[0092] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0093] This embodiment provides an NFC-based webpage access device, which runs on a user terminal, and includes: The address acquisition module 502 is configured to acquire the webpage address information stored in the NFC tag; the webpage address information includes an address field and an identification field; A program startup module 504 is configured to start the application based on the address field and pass the webpage address information and startup type parameters to the application; A startup verification module 506 is configured to verify whether the startup type parameter corresponds to the NFC startup type through the application program; If yes, run the web page access module 508; 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, access the web page based on the web page address, and perform access authentication based on the access token.

[0094] Another embodiment of a web page access device based on NFC provided in this specification is as follows: In the above-mentioned embodiment, another NFC-based web page access method is provided, and correspondingly, another NFC-based web page access device is also provided, which is described below with reference to the accompanying drawings.

[0095] Reference Figure 6 , which shows a schematic diagram of an NFC-based web page access device embodiment provided in this embodiment.

[0096] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0097] This embodiment provides an NFC-based web page access device, which runs on a server, and includes: The request receiving module 602 is configured to receive an address query request carrying an identification field sent by an application; the identification field is obtained from the web page address information stored in the NFC tag; An address query module 604 is configured to query the webpage address of the target webpage mapped by the identification field and generate an access token of the target webpage; An address returning module 606, configured to return the webpage address and the access token to the application in response to the address query request; The web page access module 608 is configured to cooperate with the application program to perform web page access and access authentication of the target web page.

[0098] An embodiment of a web page access device based on NFC provided in this specification is as follows: Corresponding to the NFC-based web page access method described above, 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 A schematic diagram of the structure of an NFC-based web page access device provided in one or more embodiments of this specification.

[0099] This embodiment provides an NFC-based web page access device, including: like Figure 7 As shown, the NFC-based web page access device may have relatively large differences due to different configurations or performances, and may include one or more processors 701 and memory 702, and the memory 702 may store one or more storage applications or data. Among them, the memory 702 may be a temporary storage or a permanent storage. The application stored in the memory 702 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the NFC-based web page access device. Furthermore, the processor 701 may be configured to communicate with the memory 702 to execute a series of computer executable instructions in the memory 702 on the NFC-based web page access device. The NFC-based web page access device 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.

[0100] In a specific embodiment, the NFC-based webpage 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 webpage access device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: Acquire web page address information stored in the NFC tag; the web page address information includes an address field and an identification field; Starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application; Verifying, by the application, whether the activation type parameter corresponds to the NFC activation type; If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

[0101] Another embodiment of a web page access device based on NFC provided in this specification is as follows: Corresponding to the another 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 another NFC-based web page access method provided above. Figure 8 A schematic diagram of the structure of an NFC-based web page access device provided in another one or more embodiments of this specification.

[0102] Another NFC-based webpage access device provided in this embodiment includes: like Figure 8 As shown, the NFC-based web page access device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and the memory 802 may store one or more storage applications or data. Among them, the memory 802 may be a temporary storage or a permanent storage. The application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the NFC-based web page access device. Furthermore, the processor 801 may be configured to communicate with the memory 802 to execute a series of computer executable instructions in the memory 802 on the NFC-based web page access device. The NFC-based web page access device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0103] In a specific embodiment, the NFC-based webpage 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 webpage access device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: Receiving an address query request carrying an identification field sent by an application; the identification field is obtained from the web page address information stored in the NFC tag; Querying the webpage address of the target webpage mapped by the identification field, and generating an access token for the target webpage; Returning the webpage address and the access token to the application 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.

[0104] An embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the NFC-based web page access method described above, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0105] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, and the computer-executable instructions implement the following process when executed: Acquire web page address information stored in the NFC tag; the web page address information includes an address field and an identification field; Starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application; Verifying, by the application, whether the activation type parameter corresponds to the NFC activation type; If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

[0106] It should be noted that an embodiment of a computer-readable storage medium in this specification and an embodiment of a web page access method based on NFC in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0107] Another computer-readable storage medium embodiment provided in this specification is as follows: 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 computer-readable storage medium.

[0108] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, and the computer-executable instructions implement the following process when executed: Receiving an address query request carrying an identification field sent by an application; the identification field is obtained from the web page address information stored in the NFC tag; Querying the webpage address of the target webpage mapped by the identification field, and generating an access token for the target webpage; Returning the webpage address and the access token to the application 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.

[0109] It should be noted that the embodiment of another computer-readable storage medium in this specification and the embodiment of another NFC-based web page access method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0110] An embodiment of a computer program product provided in this specification is as follows: Corresponding to the NFC-based web page access method described above, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0111] A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the following steps: Acquire web page address information stored in the NFC tag; the web page address information includes an address field and an identification field; Starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application; Verifying, by the application, whether the activation type parameter corresponds to the NFC activation type; If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

[0112] It should be noted that an embodiment of a computer program product in this specification and an embodiment of a web page access method based on NFC in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0113] Another computer program product embodiment provided in this specification is as follows: 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 computer program product.

[0114] A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the following steps: Receiving an address query request carrying an identification field sent by an application; the identification field is obtained from the web page address information stored in the NFC tag; Querying the webpage address of the target webpage mapped by the identification field, and generating an access token for the target webpage; Returning the webpage address and the access token to the application 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.

[0115] It should be noted that an embodiment of another computer program product in this specification and an embodiment of another NFC-based web page access method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0116] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For example, the device embodiment, equipment embodiment, computer-readable storage medium embodiment, and computer program product embodiment are similar to the method embodiment, so the description is relatively simple. To read the relevant contents of the device embodiment, equipment embodiment, computer-readable storage medium embodiment, and computer program product embodiment, please refer to the partial description of the method embodiment.

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

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

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

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

[0121] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0122] It should be understood by those skilled in the art that one or more embodiments of the present specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present specification may take the form of a computer program product implemented 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.

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

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

[0125] These computer program instructions can also be loaded onto a computer or other programmable NFC-based web access device, so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

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

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

[0128] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer-readable storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

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

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

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

Claims

1. A webpage access method based on NFC, applied to a user terminal, the method comprising: Get the web page address information stored in the NFC tag; The webpage address information includes an address field and an identification field; Starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application; Verifying, by the application, whether the activation type parameter corresponds to the NFC activation type; If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

2. The NFC-based web page access method according to claim 1, after the step of obtaining the web page address information stored in the NFC tag is executed, and before the step of starting the application based on the address field and transmitting the web page address information and the startup type parameter to the application is executed, further comprising: Detecting whether the user terminal has installed the application corresponding to the address field; If yes, executing the step of starting the application based on the address field and passing the webpage address information and the startup type parameter to the application; If not, start the browser installed in the user terminal, obtain the web page data of the web page corresponding to the address field from the server through the browser, and load and display the web page.

3. The NFC-based webpage access method according to claim 2, wherein the webpage corresponding to the address field comprises: A download guide web page for downloading the application.

4. According to the NFC-based webpage access method of claim 1, the step of obtaining the webpage address and access token mapped by the identification field from the server comprises: Sending an address query request carrying the identification field to the server; Receive the web page address information mapped by the identification field returned by the server, and parse the received web page address information to obtain the web page address and the access token.

5. According to the NFC-based webpage access method of claim 4, the webpage address information mapped by the identification field is obtained in the following manner: Querying the webpage address of the target webpage mapped by the identification field in a pre-established mapping relationship table, and generating an access token for the target webpage; The queried web page address is concatenated with the generated access token to obtain the web page address information mapped by the identification field.

6. The NFC-based webpage access method according to claim 5, wherein the target webpage comprises: A web page that makes service recommendations within the application.

7. The NFC-based webpage access method according to claim 1, wherein the webpage access based on the webpage address and the access authentication based on the access token comprise: Obtaining web page data corresponding to the web page address from the server, loading and executing the web page data to obtain a target web page; Submitting an authentication request carrying the access token to the server; If the authentication result returned by the server is that the authentication is passed, the target webpage is displayed in the application.

8. The NFC-based webpage access method according to claim 1, wherein obtaining the webpage address information stored in the NFC tag comprises: Establishing communication with the NFC tag and sending a query signal to the NFC tag; The webpage address information returned by the NFC tag in response to the query signal is received.

9. A webpage access method based on NFC, applied to a server, the method comprising: receiving an address query request carrying an identification field sent by an application; The identification field is obtained from the web page address information stored in the NFC tag; Querying the webpage address of the target webpage mapped by the identification field, and generating an access token for the target webpage; Returning the webpage address and the access token to the application 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.

10. The NFC-based webpage access method according to claim 9, wherein the address query request is sent when a startup type parameter passed into the application corresponds to an NFC startup type.

11. The NFC-based webpage access method according to claim 9, wherein the step of returning the webpage address and the access token to the application comprises: Concatenate the web page address and the access token to obtain web page address information, and return the web page address information to the application; The webpage address is obtained by searching a pre-established mapping relationship table based on the identification field.

12. The NFC-based webpage access method according to claim 9, wherein the webpage corresponding to the address field contained in the webpage address information comprises: A download guide webpage for downloading the application; The target web page includes: a web page for service recommendation in the application program.

13. The NFC-based webpage access method according to claim 9, after the step of querying the webpage address of the target webpage mapped by the identification field and generating an access token for the target webpage is performed, and before the step of cooperating with the application to perform webpage access to the target webpage and access authentication is performed, further comprising: Generate an access record of the application program accessing the target webpage; the access record includes terminal information and token generation time.

14. The NFC-based webpage access method according to claim 13, wherein the access authentication comprises: Detecting whether the terminal information included in the authentication request sent by the application is the same as the terminal information in the access record; If they are not the same, it is determined that the authentication has not passed; If they are the same, detecting whether the access token is within the validity period, if so, determining that the authentication is passed; if not, determining that the authentication is not passed; The validity period is determined according to the token generation time and the token validity period.

15. A webpage access device based on NFC, running on a user terminal, the device comprising: An address acquisition module is configured to acquire web page address information stored in the NFC tag; The webpage address information includes an address field and an identification field; A program startup module, configured to start the application based on the address field, and to pass the webpage address information and startup type parameters to the application; A startup verification module, configured to verify whether the startup type parameter corresponds to the NFC startup type through the application; If yes, run the web page access module; The web page access module is configured to obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

16. A webpage access device based on NFC, running on a server, the device comprising: 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 the web page address information stored in the NFC tag; An address query module is configured to query the webpage address of the target webpage mapped by the identification field and generate an access token of the target webpage; an address returning module, configured to return the webpage address and the access token to the application program in response to the address query request; The web page access module is configured to cooperate with the application program to perform web page access and access authentication of the target web page.

17. A web page access device based on NFC, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Acquire web page address information stored in the NFC tag; the web page address information includes an address field and an identification field; Starting the application based on the address field, and passing the webpage address information and the startup type parameter to the application; Verifying, by the application, whether the activation type parameter corresponds to the NFC activation type; If so, obtain the web page address and access token mapped by the identification field from the server, access the web page based on the web page address, and perform access authentication based on the access token.

18. A web page access device based on NFC, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Receiving an address query request carrying an identification field sent by an application; the identification field is obtained from the web page address information stored in the NFC tag; Querying the webpage address of the target webpage mapped by the identification field, and generating an access token for the target webpage; Returning the webpage address and the access token to the application 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.

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

20. A computer-readable storage medium for storing computer-executable instructions, wherein the computer-executable instructions implement the steps of the method of claim 9 when executed.

Images