CN105868351B - Access authentication page skipping method based on browser and user terminal - Google Patents
Access authentication page skipping method based on browser and user terminal Download PDFInfo
- Publication number
- CN105868351B CN105868351B CN201610185888.XA CN201610185888A CN105868351B CN 105868351 B CN105868351 B CN 105868351B CN 201610185888 A CN201610185888 A CN 201610185888A CN 105868351 B CN105868351 B CN 105868351B
- Authority
- CN
- China
- Prior art keywords
- browser
- page
- access authentication
- favorite
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/954—Navigation, e.g. using categorised browsing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides an access authentication page skipping method based on a browser, which comprises the following steps: the user terminal operates a programming language server webpage or a hypertext script inserted into the access authentication page; setting the access authentication page as a home page and/or a favorite of the browser; and when the internet is required to be logged off, switching the current interface to the browser, and skipping the home page and/or the favorite of the browser to the access authentication page. Therefore, when a user needs to log off the internet, the home page of the browser automatically jumps to the page with successful access authentication or the favorite of the browser jumps to the page with successful access authentication, and the log-off button is pressed in the page with successful access authentication to log off, so that the method is convenient and quick, improves the user experience, reduces the charging error, and avoids the embarrassing situation of searching the page with successful authentication back and forth.
Description
Technical Field
The invention relates to the technical field of access authentication page skipping, in particular to an access authentication page skipping method based on a browser and a user terminal.
Background
At present, wireless coverage is more and more, and mobile terminal equipment such as mobile phones and the like are used more and more. Portal authentication is one of popular technologies of wireless network access authentication, and when a user accesses a certain wireless network, a Portal page can be automatically popped up to prompt the user to input account information to complete access authentication. At present, Portal authentication is mainly completed based on Web pages, no matter whether a wireless terminal automatically pops up the Portal page or a user manually opens the Portal page, the Portal page is substantially popped up by means of a local browser of the wireless terminal, and when the user completes Portal authentication, the Internet access permission can be obtained. When a user needs to actively log out, sometimes it is difficult to find a page (possibly too many pages or inadvertently close the page) when the initial authentication is successful, and at this time, the user can only realize passive log out by closing the wireless of the terminal and by time-out. However, this operation method is cumbersome, user experience is poor, and a certain internet traffic or a charging error of a duration may be caused.
And prompting a user to keep the Portal authentication page in the system background through the Portal authentication success page without closing the Portal authentication page so as to avoid the situation that the active log-out function cannot be completed. When the user needs to log out, the original Portal page is searched and switched to, and the log-out is finished after clicking a log-out button. In practical application, the user may have misoperation, and the Portal authentication page is easy to close, thereby causing functional failure. On the other hand, the user switches back and forth to search a plurality of pages in the background, the efficiency is low, the user experience is poor, and particularly when the number of pages opened by the user is large, the function has little value.
Disclosure of Invention
In view of this, the present invention provides an access authentication page hopping method based on a browser, where the method includes:
the user terminal operates a programming language server webpage or a hypertext script inserted into the access authentication page;
setting the access authentication page as a home page and/or a favorite of the browser;
and when the internet is required to be logged off, switching the current interface to the browser, and skipping the home page and/or the favorite of the browser to the access authentication page.
Further, the setting the access authentication page as a home page and/or a favorite of a browser specifically includes:
setting the access authentication page into a home page and a favorite of the browser, and if the home page and the favorite of the browser fail to be set, prompting a user to set the access authentication page into the home page and the favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page into a home page and a favorite of the browser, and if the home page or the favorite of the browser fails to be set, prompting a user to set the access authentication page into the home page or the favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page as a home page of the browser, and if the home page setting of the browser fails, setting the access authentication page in a favorite of the browser; if the favorite setup of the browser fails, prompting a user to set the access authentication page as a home page or in a favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page as a favorite of the browser, and if the favorite of the browser fails to be set, setting the access authentication page as a home page of the browser; and if the setting of the home page of the browser fails, prompting a user to set the access authentication page into the home page or the favorite of the browser.
Further, after the current interface is switched to the browser and the home page and/or the favorite of the browser jump to the access authentication page, the method further comprises:
the user terminal automatically logs in the access authentication page through the user identity stored in the browser;
and sending a request to an access server to refresh the access authentication page so that the access server judges whether the user is successfully accessed and authenticated according to the sending request.
Further, after sending a request to refresh the access authentication page to the access server, the method further includes:
if the user access authentication is successful, the user terminal receives an access authentication success message and a page refreshing message sent by the access server; the refreshing page message is the remaining internet surfing duration of the user or the remaining user flow;
and if the user does not perform access authentication or fails, the user terminal receives a re-authentication message sent by the access server.
Further, after the user terminal receives the page refreshing message sent by the access server, the method further includes:
and the user terminal refreshes the access authentication page and prompts whether the user needs to log off the Internet.
The present invention also provides a user terminal, which includes:
the operation module is used for operating the programming language server webpage or the hypertext script inserted into the access authentication page;
the setting module is used for setting the access authentication page as a home page and/or a favorite of the browser;
and the switching and skipping module is used for switching the current interface to the browser, and skipping to the access authentication page in the home page and/or the favorite of the browser.
Further, the setting module includes:
the first setting submodule is used for setting the access authentication page into a home page and a favorite of the browser;
the first prompting sub-module is used for prompting a user to set the access authentication page as the home page and the favorite of the browser when the home page and the favorite of the browser are both failed to be set;
the second setting submodule is used for setting the access authentication page into a home page and a favorite of the browser;
the second prompting sub-module is used for prompting a user to set the access authentication page as the home page or the favorite of the browser when the home page or the favorite of the browser fails to be set;
a third setting submodule, configured to set the access authentication page as a home page of the browser;
the fourth setting submodule is used for setting the access authentication page in the favorite of the browser when the setting of the home page of the browser fails;
the third prompting sub-module is used for prompting a user to set the access authentication page as a home page or in a favorite of the browser when the favorite of the browser fails to be set;
a fifth setting submodule, configured to set the access authentication page as a favorite of the browser;
a sixth setting submodule, configured to set the access authentication page as a home page of the browser when the favorite setting of the browser fails;
and the fourth prompting sub-module is used for prompting the user to set the access authentication page as the home page or the favorite of the browser when the home page setting of the browser fails.
Further, the user terminal further includes:
the login module is used for automatically logging in the access authentication page through the user identity stored in the browser after the current interface is switched to the browser by the switching and skipping module and the home page and/or the favorite of the browser skip to the access authentication page;
and the sending module is used for sending a request to an access server to refresh the access authentication page so that the access server can judge whether the user is successfully accessed and authenticated according to the sending request.
Further, the user terminal further includes:
a receiving module, configured to receive an access authentication success message and a refresh page message sent by an access server when the user access authentication succeeds after the sending module sends a request to refresh the access authentication page to the access server; when the user does not perform access authentication or fails to perform the access authentication, receiving a re-authentication message sent by the access server; the page refreshing message is the remaining internet surfing duration of the user or the remaining user traffic.
Further, the user terminal further includes:
and the refreshing prompting module is used for refreshing the access authentication page after the receiving module receives the page refreshing message sent by the access server, and prompting whether the user needs to log off the internet.
The invention operates a programming language server webpage or a hypertext script inserted into an access authentication page through a user terminal; setting the access authentication page as a home page and/or a favorite of the browser; and when the internet is required to be logged off, switching the current interface to the browser, and skipping the home page and/or the favorite of the browser to the access authentication page. Therefore, when a user needs to log off the internet, the home page of the browser automatically jumps to the page with successful access authentication or the favorite of the browser jumps to the page with successful access authentication, and the log-off button is pressed in the page with successful access authentication to log off, so that the method is convenient and quick, improves the user experience, reduces the charging error, and avoids the embarrassing situation of searching the page with successful authentication back and forth.
Drawings
FIG. 1 is a flowchart illustrating an embodiment of a browser-based access authentication page hopping method according to the present invention;
FIG. 2 is a flowchart illustrating an embodiment of a method for setting an access authentication page as a home page and/or a favorite of a browser in the browser-based access authentication page hopping method according to the present invention;
FIG. 3 is a flowchart illustrating another embodiment of a method for setting an access authentication page as a home page and/or a favorite of a browser in a browser-based access authentication page hopping method according to the present invention;
FIG. 4 is a flowchart illustrating another embodiment of a method for setting an access authentication page as a home page and/or a favorite of a browser in a browser-based access authentication page hopping method according to the present invention;
FIG. 5 is a flowchart illustrating another embodiment of a method for setting an access authentication page as a home page and/or a favorite of a browser in a browser-based access authentication page hopping method according to the present invention;
FIG. 6 is a flowchart illustrating a browser-based access authentication page hopping method according to another embodiment of the present invention;
FIG. 7 is a flowchart illustrating a browser-based access authentication page hopping method according to another embodiment of the present invention;
FIG. 8 is a flowchart illustrating a browser-based access authentication page hopping method according to another embodiment of the present invention;
FIG. 9 is a block diagram of one embodiment of a user terminal of the present invention;
FIG. 10 is a block diagram of one embodiment of a setup module in a user terminal of the present invention;
FIG. 11 is a block diagram of another embodiment of a user terminal of the present invention;
fig. 12 is a block diagram of another embodiment of a user terminal of the present invention;
fig. 13 is a block diagram of another embodiment of a user terminal of the present invention;
fig. 14 is a block diagram of an embodiment of a user terminal in a system application according to the present invention.
Detailed Description
The technical scheme of the invention is that a user terminal runs a programming language server webpage or a hypertext script inserted into an access authentication page; setting the access authentication page as a home page and/or a favorite of the browser; and when the internet is required to be logged off, switching the current interface to the browser, and skipping the home page and/or the favorite of the browser to the access authentication page.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings by way of examples.
Fig. 1 is a flowchart of an embodiment of a browser-based access authentication page hopping method of the present invention, and the specific flow is as follows:
step S101, a user terminal runs a programming language server webpage or a hypertext script inserted into an access authentication page;
specifically, the programming language Server webpage JSP (JSP is named Java Server Pages in full, and Chinese is named Java Server Pages; Java is an object-oriented programming language capable of writing cross-platform application programs), and the hypertext script is an HTML script (the hypertext script refers to that non-character elements such as pictures, links, even music and programs can be contained in the page).
Step S102, setting the access authentication page as a home page and/or a favorite of a browser;
specifically, the access authentication page is set as a home page and/or a favorite of the browser, that is, the access authentication page is added to the home page and/or the favorite of the browser.
And step S103, when the internet is required to be logged off, switching the current interface to the browser, and skipping the home page and/or the favorite of the browser to the access authentication page.
Specifically, a user clicks a 'browser access authentication' button in a task bar of a current interface, after receiving a switching instruction of 'browser access authentication' of the user, a user terminal switches the current interface to a browser, and a home page of the browser jumps to an access authentication page and/or a favorite of the browser jumps to the access authentication page;
the access authentication page comprises the remaining internet surfing duration and a log-off login button, and when the user needs to log off the internet surfing, the user can click the log-off button.
In step S102, the step of setting the access authentication page as a home page and/or favorite of the browser is shown in fig. 2, and the specific steps are as follows:
step S201, setting the access authentication page as a home page and a favorite of the browser;
specifically, an access authentication page is set in both a home page and a favorite of the browser, and when the failure of displaying the access authentication page on the home page of the browser comprises unsuccessful home page setting and unsuccessful display of the browser, the access authentication page is displayed through the favorite of the browser; or when the failure of displaying the access authentication page by the favorite of the browser comprises unsuccessful favorite setting and unsuccessful display of the browser, displaying the access authentication page by the browser home page.
Step S202, if the settings of the home page and the favorite of the browser fail, prompting a user to set the access authentication page as the home page and the favorite of the browser.
Specifically, when the settings of the home page and the favorite of the browser fail to include unsuccessful setting and unsuccessful display, that is, when neither the home page nor the favorite of the browser can display the access authentication page, the user is prompted to set the access authentication page as the home page and the favorite of the browser, that is, the user needs to manually input the access authentication page.
Step S102 is to set the access authentication page as a home page and/or favorite of the browser, as further shown in fig. 3, and includes the following specific steps:
step S301, setting the access authentication page into a home page and a favorite of the browser;
specifically, an access authentication page is set in both a home page and a favorite of the browser, and when the failure of displaying the access authentication page on the home page of the browser comprises unsuccessful home page setting and unsuccessful display of the browser, the access authentication page is displayed through the favorite of the browser; or when the failure of displaying the access authentication page by the favorite of the browser comprises unsuccessful favorite setting and unsuccessful display of the browser, displaying the access authentication page by the browser home page.
Step S302, if the setting of the home page or the favorite of the browser fails, prompting a user to set the access authentication page into the home page or the favorite of the browser.
Specifically, when the setting failure of the home page or the favorite of the browser includes unsuccessful setting and unsuccessful display, that is, when the home page or the favorite of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as the home page or the favorite of the browser, that is, the user needs to manually input the access authentication page.
Step S102 is to set the access authentication page as a home page and/or favorite of the browser, as further shown in fig. 4, and includes the following specific steps:
step S401, setting the access authentication page as a home page of the browser;
specifically, the user terminal may set only the access authentication page as a home page of the browser, and display the access authentication page through the home page of the browser.
Step S402, if the setting of the home page of the browser fails, setting the access authentication page in a favorite of the browser;
specifically, when the setting failure of the home page of the browser includes unsuccessful setting and unsuccessful displaying of the home page of the browser, the access authentication page may be set in a favorite of the browser, and the access authentication page is displayed through the favorite of the browser.
Step S403, if the favorite setup of the browser fails, prompting the user to set the access authentication page as the home page or in the favorite of the browser.
Specifically, when the failure in setting the favorite folder of the browser includes unsuccessful setting and unsuccessful displaying of the favorite folder of the browser, that is, when the favorite of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as a home page or a favorite of the browser.
Step S102 is to set the access authentication page as a home page and/or favorite of the browser, as further shown in fig. 5, and includes the following specific steps:
step S501, setting the access authentication page into a favorite of the browser;
specifically, the user terminal may set only the access authentication page as a favorite of the browser, and display the access authentication page through the favorite of the browser.
Step S502, if the favorite setup of the browser fails, setting the access authentication page as the home page of the browser;
specifically, when the favorite setting failure of the browser includes unsuccessful favorite setting and unsuccessful display of the browser, the access authentication page may be set in a home page of the browser, and the access authentication page is displayed through the home page of the browser.
Step S503, if the setting of the home page of the browser fails, prompting the user to set the access authentication page as the home page or the favorite of the browser.
Specifically, when the setting failure of the home page of the browser includes unsuccessful setting and unsuccessful displaying of the home page of the browser, that is, when the home page of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as the home page or the favorite of the browser.
In step S103, after the current interface is switched to the browser and the home page and/or the favorite of the browser jump to the access authentication page, the method further processes as shown in fig. 6, and the specific steps are as follows:
step S601, the user terminal automatically logs in the access authentication page through the user identity stored in the browser;
specifically, the browser Cookie (data) holds the user identity, which includes a username and password.
Step S602, sending a request to an access server to refresh the access authentication page;
specifically, the purpose of sending a request to the access server to refresh the access authentication page is: and the access server judges whether the access authentication of the user is successful according to the sending request.
In step S602, after sending a request to the access server to refresh the access authentication page, the method further processes as shown in fig. 7, and specifically includes the following steps:
step S701, if the user access authentication is successful, the user terminal receives an access authentication success message and a page refreshing message sent by the access server;
specifically, the page refreshing message is the remaining internet surfing duration of the user or the remaining traffic of the user.
Step S702, if the user does not perform access authentication or fails, the user terminal receives a re-authentication message sent by the access server.
Specifically, the access authentication failure includes unsuccessful access authentication setting or unsuccessful access authentication display.
After the user terminal receives the page refreshing message sent by the access server in step S701, the method further processes as shown in fig. 8, and specifically includes the following steps:
step S801, the user terminal refreshes the access authentication page;
specifically, the access authentication page is refreshed, that is, the internet surfing time of the user terminal is refreshed, so that the remaining internet surfing time is displayed to the user.
Step S802, prompting whether the user needs to log off the Internet.
Specifically, after the user terminal refreshes the access authentication page, a logout button is displayed on the access authentication page, and the logout of the internet is prompted to be carried out by pressing the logout button.
In summary, after the user access authentication is successful, the user terminal executes the JSP or HTML script inserted in the page with successful authentication, and sets the page with successful authentication as the home page of the browser or adds the page into the favorite; then the user switches the APP to surf the Internet normally, when the user needs to actively log off and log off, the browser is opened again, the home page and/or the favorite of the browser are/is jumped to a Portal (access) authentication success page, and the user surfing information (such as the remaining time or the flow) is automatically refreshed; when the user needs to log off the internet, the user clicks a 'log-off' button in the authentication success page, and the user can log off the internet.
Before the access authentication of the user terminal is successful, the following specific processing is performed:
step one, the wireless access point hijacks an access authentication request of a user terminal;
specifically, the wireless access point monitors a local 80 port (open port), and hijacks an access authentication Request (a first HTTP Request internet access Request) of the user terminal;
before the access authentication request of the user terminal is hijacked, the user terminal associates a certain SSID (service set identifier) of the wireless access point, a wireless local area network is divided into a plurality of sub-networks (each sub-network has one SSID) which need different identity verifications, each sub-network needs independent identity verification, only the user who passes the identity verification can enter the corresponding sub-network, and the unauthorized user is prevented from entering the network.
Step two, redirecting the response message of the access authentication request to the network address of the access authentication page;
specifically, redirection (Redirect) is to Redirect various network requests to other locations by various methods (e.g., redirection of web page, redirection of domain name, change of routing is also a kind of redirection of data message via path);
the access authentication page is a page designated by the access server, and the network address is a URL (universal resource locator) (WWW) address.
Step three, the user terminal acquires the network address of the redirected access authentication page;
specifically, after the user terminal receives the website of the access authentication page, the access authentication page is opened according to the network address of the access authentication page;
after an access authentication page is opened, a user terminal inputs a user name and a password in the access authentication page, an access authentication request is sent to an access server, the access server verifies the user name and the password, and when the verification is passed, the access authentication is indicated to be successful; otherwise, the access authentication is failed;
after the audit, the access server sends the audit result and the internet access duration of the user terminal to the user terminal; when the access result is that the verification is passed, displaying a prompt for allowing the user to surf the Internet through the user terminal, and sending an access authentication success message to the wireless access point; and when the access result is not approved, prompting the user to re-input the user name and/or the password through the user terminal.
When the verification is passed, the information of successful access authentication is sent to the wireless access point;
the access authentication request refers to a request for confirming whether the access authentication is successful or not, which is sent to the access server by the user terminal on the access authentication page.
Step four, after the wireless access point receives the successful message of the access authentication, the internet access authority of the user is opened;
specifically, the access right refers to a certain subnet SSID (service set identifier) that the user terminal can access the wireless access point, and the access duration/traffic of the user terminal.
And step five, after receiving the access authentication success message sent by the access server, the user terminal opens an access authentication success page, prompts the user that the access authentication is successful, and displays the remaining internet surfing duration of the user.
Fig. 9 is a block diagram of an embodiment of a ue in the present invention, where the ue 900 includes an operation module 901, a setting module 902 and a handover skip module 903,
an operation module 901, configured to operate a programming language server webpage or a hypertext script inserted in the access authentication page;
specifically, the programming language server side webpage JSP and the hypertext script are HTML scripts.
A setting module 902, configured to set the access authentication page as a home page and/or a favorite of a browser;
specifically, the access authentication page is set as a home page and/or a favorite of the browser, that is, the access authentication page is added to the home page and/or the favorite of the browser.
And a switching skip module 903, configured to switch the current interface to the browser, and skip to the access authentication page in the home page and/or the favorite of the browser.
Specifically, a user clicks a 'browser access authentication' button in a task bar of a current interface, after receiving a switching instruction of 'browser access authentication' of the user, a user terminal switches the current interface to a browser, and a home page of the browser jumps to an access authentication page and/or a favorite of the browser jumps to the access authentication page;
the access authentication page comprises the remaining internet surfing duration and a log-off login button, and when the user needs to log off the internet surfing, the user can click the log-off button.
Wherein, the specific structure of the setting module 902 is as shown in fig. 10, the setting module 902 includes a first setting submodule 9021, a first prompt submodule 9022, a second setting submodule 9023, a second prompt submodule 9024, a third setting submodule 9025, a fourth setting submodule 9026, a third prompt submodule 9027, a fifth setting submodule 9028, a sixth setting submodule 9029 and a fourth prompt submodule 9030,
the first setting sub-module 9021 is configured to set the access authentication page as a home page and a favorite of the browser;
specifically, an access authentication page is set in both a home page and a favorite of the browser, and when the failure of displaying the access authentication page on the home page of the browser comprises unsuccessful home page setting and unsuccessful display of the browser, the access authentication page is displayed through the favorite of the browser; or when the failure of displaying the access authentication page by the favorite of the browser comprises unsuccessful favorite setting and unsuccessful display of the browser, displaying the access authentication page by the browser home page.
A first prompt sub-module 9022, configured to prompt the user to set the access authentication page as the home page and the favorite of the browser when both the home page and the favorite of the browser are failed to be set;
specifically, when the settings of the home page and the favorite of the browser fail to include unsuccessful setting and unsuccessful display, that is, when neither the home page nor the favorite of the browser can display the access authentication page, the user is prompted to set the access authentication page as the home page and the favorite of the browser, that is, the user needs to manually input the access authentication page.
A second setting sub-module 9023, configured to set the access authentication page as a home page and a favorite of the browser;
specifically, an access authentication page is set in both a home page and a favorite of the browser, and when the failure of displaying the access authentication page on the home page of the browser comprises unsuccessful home page setting and unsuccessful display of the browser, the access authentication page is displayed through the favorite of the browser; or when the failure of displaying the access authentication page by the favorite of the browser comprises unsuccessful favorite setting and unsuccessful display of the browser, displaying the access authentication page by the browser home page.
A second prompt sub-module 9024, configured to prompt the user to set the access authentication page as the home page or the favorite of the browser when the home page or the favorite of the browser fails to be set;
specifically, when the setting failure of the home page or the favorite of the browser includes unsuccessful setting and unsuccessful display, that is, when the home page or the favorite of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as the home page or the favorite of the browser, that is, the user needs to manually input the access authentication page.
A third setting sub-module 9025, configured to set the access authentication page as a home page of the browser;
specifically, the user terminal may set only the access authentication page as a home page of the browser, and display the access authentication page through the home page of the browser.
A fourth setting sub-module 9026, configured to set the access authentication page in the favorite of the browser when the setting of the home page of the browser fails;
specifically, when the setting failure of the home page of the browser includes unsuccessful setting and unsuccessful displaying of the home page of the browser, the access authentication page may be set in a favorite of the browser, and the access authentication page is displayed through the favorite of the browser.
A third prompting sub-module 9027, configured to prompt the user to set the access authentication page as a home page or in a favorite of the browser when the favorite of the browser is set to be failed;
specifically, when the failure in setting the favorite folder of the browser includes unsuccessful setting and unsuccessful displaying of the favorite folder of the browser, that is, when the favorite of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as a home page or a favorite of the browser.
A fifth setting sub-module 9028, configured to set the access authentication page as a favorite of the browser;
specifically, the user terminal may set only the access authentication page as a favorite of the browser, and display the access authentication page through the favorite of the browser.
A sixth setting sub-module 9029, configured to set the access authentication page as a home page of the browser when the setting of the favorite of the browser fails;
specifically, when the favorite setting failure of the browser includes unsuccessful favorite setting and unsuccessful display of the browser, the access authentication page may be set in a home page of the browser, and the access authentication page is displayed through the home page of the browser.
A fourth prompting sub-module 9030, configured to prompt the user to set the access authentication page as the home page or the favorite of the browser when the setting of the home page of the browser fails.
Specifically, when the setting failure of the home page of the browser includes unsuccessful setting and unsuccessful displaying of the home page of the browser, that is, when the home page of the browser cannot display the access authentication page, the user is prompted to set the access authentication page as the home page or the favorite of the browser.
Fig. 11 is a structural diagram of another embodiment of the user terminal of the present invention, and the user terminal 900 includes an operation module 901, a setting module 902, a handover skip module 903, a login module 904, and a sending module 905, where the operation module 901, the setting module 902, and the handover skip module 903 are shown in fig. 9,
a login module 904, configured to automatically log in the access authentication page through the user identity stored in the browser after the switching skip module switches the current interface to the browser and the home page and/or the favorite of the browser skip to the access authentication page;
specifically, the browser Cookie stores a user identity, which includes a username and password.
A sending module 905, configured to send a request to an access server to refresh the access authentication page, so that the access server determines whether the user is successfully authenticated according to the sending request.
Specifically, the purpose of sending a request to the access server to refresh the access authentication page is: and the access server judges whether the access authentication of the user is successful according to the sending request.
Fig. 12 is a structural diagram of another embodiment of the ue of the present invention, in which the ue 900 includes an operation module 901, a setting module 902, a handover module 903, a login module 904, a sending module 905, and a receiving module 906, where the operation module 901, the setting module 902, and the handover module 903 are shown in fig. 11 as the login module 904 and the sending module 905,
a receiving module 906, configured to receive an access authentication success message and a refresh page message sent by an access server when the user access authentication succeeds after the sending module sends a request to refresh the access authentication page to the access server; when the user does not perform access authentication or fails to perform the access authentication, receiving a re-authentication message sent by the access server; the page refreshing message is the remaining internet surfing duration of the user or the remaining user traffic.
Specifically, the page refreshing message is the remaining internet surfing duration of the user or the remaining traffic of the user, and the access authentication failure includes unsuccessful access authentication setting or unsuccessful access authentication display.
Fig. 13 is a structural diagram of another embodiment of the ue of the present invention, in which the ue 900 includes an operation module 901, a setting module 902, a switch skip module 903, a login module 904, a sending module 905, a receiving module 906, and a refresh prompt module 907, where the operation module 901, the setting module 902, and the switch skip module 903 are shown in fig. 12,
the refresh prompt module 907 is configured to refresh the access authentication page after the receiving module receives the page refresh message sent by the access server, and prompt the user whether to log off the internet.
Specifically, after the user terminal refreshes the access authentication page, a logout button is displayed on the access authentication page, and the logout of the internet is prompted to be carried out by pressing the logout button.
Fig. 14 is a block diagram of an embodiment of a user terminal in a system application of the present invention, the system comprising a user terminal 900 and an access server 1401,
the user terminal 900 is used for running a programming language server webpage or a hypertext script inserted into the access authentication page; setting the access authentication page as a home page and/or a favorite of the browser; when the internet is required to be logged off, switching a current interface to the browser, and skipping a home page and/or a favorite of the browser to the access authentication page;
the user terminal 900 is further configured to switch a current interface to the browser, and after a home page and/or a favorite of the browser jump to the access authentication page, automatically log in the access authentication page through a user identity stored in the browser; and sends a request to the access server 1401 to refresh the access authentication page, so that the access server 1401 judges whether the user is successfully authenticated according to the sending request.
The user terminal 900 is further configured to send a request to refresh the access authentication page to the access server 1401, and then receive an access authentication success message and a refresh page message sent by the access server 1401 if the user access authentication is successful; the refreshing page message is the remaining internet surfing duration of the user or the remaining user flow; if the user does not perform access authentication or fails, receiving a re-authentication message sent by the access server 1401;
the user terminal 900 is further configured to refresh the access authentication page after receiving the page refresh message sent by the access server 1401, and prompt the user whether to log off the internet.
The access server 1401 receives a request for refreshing the access authentication page sent by the user terminal 900, and judges whether the user is successfully authenticated according to the request for refreshing the access authentication page; if the access authentication is successful, sending an access authentication success message and a page refreshing message to the user terminal 900; if the user does not perform access authentication or fails, a re-authentication message is sent to the user terminal 900.
It should be understood that the functional modules of the user terminal 900 provided in the present embodiment may be software modules or a combination of software and hardware modules, which can be executed by a processor to implement the functions described above. In addition, the user terminal 900 may further have other functional modules to implement various specific steps of conveniently and quickly logging off the internet, and reference may be made to the corresponding description of the above method embodiment.
In addition, those skilled in the art will understand that: all or part of the steps of implementing the above method embodiments may be implemented by hardware related to program instructions, the program may be stored in a computer readable storage medium and executed by a processor in the computer readable storage medium, and the processor may execute all or part of the steps including the above method embodiments when the program is executed. Wherein the processor may be implemented as one or more processor chips or may be part of one or more Application Specific Integrated Circuits (ASICs); and the aforementioned storage media may include, but are not limited to, the following types of storage media: flash Memory (Flash Memory), Memory (ROM), Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A browser-based access authentication page jump method is characterized by comprising the following steps:
the user terminal operates a programming language server webpage or a hypertext script inserted into the access authentication page;
setting the access authentication page as a home page and/or a favorite of the browser;
when the user needs to log off the internet, the current interface is switched to the browser, the home page and/or the favorite of the browser skip to the access authentication page, specifically, the user clicks a 'browser access authentication' button in a task bar of the current interface, after the terminal receives a switching instruction of 'browser access authentication' of the user, the current interface is switched to the browser, the home page of the browser skips to the access authentication page and/or the favorite of the browser skips to the access authentication page, the access authentication page comprises the remaining internet surfing duration and a 'log-off' login button, and when the user needs to log off the internet, the user can click the 'log-off' button.
2. The method according to claim 1, wherein the setting the access authentication page as a home page and/or a favorite of a browser specifically includes:
setting the access authentication page into a home page and a favorite of the browser, and if the home page and the favorite of the browser fail to be set, prompting a user to set the access authentication page into the home page and the favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page into a home page and a favorite of the browser, and if the home page or the favorite of the browser fails to be set, prompting a user to set the access authentication page into the home page or the favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page as a home page of the browser, and if the home page setting of the browser fails, setting the access authentication page in a favorite of the browser; if the favorite setup of the browser fails, prompting a user to set the access authentication page as a home page or in a favorite of the browser; alternatively, the first and second electrodes may be,
setting the access authentication page as a favorite of the browser, and if the favorite of the browser fails to be set, setting the access authentication page as a home page of the browser; and if the setting of the home page of the browser fails, prompting a user to set the access authentication page into the home page or the favorite of the browser.
3. The method of claim 1, wherein switching a current interface to the browser, after jumping to the access authentication page by a home page and/or favorites of the browser, the method further comprises:
the user terminal automatically logs in the access authentication page through the user identity stored in the browser;
and sending a request to an access server to refresh the access authentication page so that the access server judges whether the user is successfully accessed and authenticated according to the sending request.
4. The method of claim 3, wherein after sending a request to an access server to refresh the access authentication page, the method further comprises:
if the user access authentication is successful, the user terminal receives an access authentication success message and a page refreshing message sent by the access server; the refreshing page message is the remaining internet surfing duration of the user or the remaining user flow;
and if the user does not perform access authentication or fails, the user terminal receives a re-authentication message sent by the access server.
5. The method of claim 4, wherein after the user terminal receives the refresh page message sent by the access server, the method further comprises:
and the user terminal refreshes the access authentication page and prompts whether the user needs to log off the Internet.
6. A user terminal, characterized in that the user terminal comprises:
the operation module is used for operating the programming language server webpage or the hypertext script inserted into the access authentication page;
the setting module is used for setting the access authentication page as a home page and/or a favorite of the browser; the switching and skipping module is used for switching a current interface to the browser, skipping to the access authentication page in a home page and/or a favorite of the browser, specifically, clicking a browser access authentication button in a task bar of the current interface by a user, switching the current interface to the browser after the terminal receives a switching instruction of browser access authentication of the user, skipping to the access authentication page by the home page of the browser and/or skipping to the access authentication page by the favorite of the browser, wherein the access authentication page comprises a remaining internet surfing duration and a logout login button, and when the user needs to logout, the user can click the logout button.
7. The user terminal of claim 6, wherein the setup module comprises:
the first setting submodule is used for setting the access authentication page into a home page and a favorite of the browser;
the first prompting sub-module is used for prompting a user to set the access authentication page as the home page and the favorite of the browser when the home page and the favorite of the browser are both failed to be set;
the second setting submodule is used for setting the access authentication page into a home page and a favorite of the browser;
the second prompting sub-module is used for prompting a user to set the access authentication page as the home page or the favorite of the browser when the home page or the favorite of the browser fails to be set;
a third setting submodule, configured to set the access authentication page as a home page of the browser;
the fourth setting submodule is used for setting the access authentication page in the favorite of the browser when the setting of the home page of the browser fails;
the third prompting sub-module is used for prompting a user to set the access authentication page as a home page or in a favorite of the browser when the favorite of the browser fails to be set;
a fifth setting submodule, configured to set the access authentication page as a favorite of the browser;
a sixth setting submodule, configured to set the access authentication page as a home page of the browser when the favorite setting of the browser fails;
and the fourth prompting sub-module is used for prompting the user to set the access authentication page as the home page or the favorite of the browser when the home page setting of the browser fails.
8. The user terminal of claim 6, wherein the user terminal further comprises:
the login module is used for automatically logging in the access authentication page through the user identity stored in the browser after the current interface is switched to the browser by the switching and skipping module and the home page and/or the favorite of the browser skip to the access authentication page;
and the sending module is used for sending a request to an access server to refresh the access authentication page so that the access server can judge whether the user is successfully accessed and authenticated according to the sending request.
9. The user terminal of claim 8, wherein the user terminal further comprises:
a receiving module, configured to receive an access authentication success message and a refresh page message sent by an access server when the user access authentication succeeds after the sending module sends a request to refresh the access authentication page to the access server;
when the user does not perform access authentication or fails to perform the access authentication, receiving a re-authentication message sent by the access server; the page refreshing message is the remaining internet surfing duration of the user or the remaining user traffic.
10. The user terminal of claim 9, wherein the user terminal further comprises:
and the refreshing prompting module is used for refreshing the access authentication page after the receiving module receives the page refreshing message sent by the access server, and prompting whether the user needs to log off the internet.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610185888.XA CN105868351B (en) | 2016-03-29 | 2016-03-29 | Access authentication page skipping method based on browser and user terminal |
| PCT/CN2016/103900 WO2017166806A1 (en) | 2016-03-29 | 2016-10-29 | Browser-based method for jumping to access authentication page, and user terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610185888.XA CN105868351B (en) | 2016-03-29 | 2016-03-29 | Access authentication page skipping method based on browser and user terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105868351A CN105868351A (en) | 2016-08-17 |
| CN105868351B true CN105868351B (en) | 2020-03-20 |
Family
ID=56626275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610185888.XA Active CN105868351B (en) | 2016-03-29 | 2016-03-29 | Access authentication page skipping method based on browser and user terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105868351B (en) |
| WO (1) | WO2017166806A1 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105868351B (en) * | 2016-03-29 | 2020-03-20 | 上海斐讯数据通信技术有限公司 | Access authentication page skipping method based on browser and user terminal |
| CN107454592B (en) * | 2017-07-14 | 2020-11-27 | 台州市吉吉知识产权运营有限公司 | Method and system for preventing automatic Portal pop-up during application program authentication |
| CN108092974B (en) * | 2017-12-14 | 2021-05-28 | 杭州迪普科技股份有限公司 | Internet access authentication method and device |
| CN109871499A (en) * | 2019-01-16 | 2019-06-11 | 中国平安财产保险股份有限公司 | Page loading method and client |
| CN112269954B (en) * | 2020-10-28 | 2024-05-03 | 连尚(北京)网络科技有限公司 | Page use time length determining method and device |
| CN112714123A (en) * | 2020-12-27 | 2021-04-27 | 杭州迪普科技股份有限公司 | Internet surfing method and device and electronic equipment |
| CN112751844B (en) * | 2020-12-28 | 2022-11-01 | 杭州迪普科技股份有限公司 | Portal authentication method and device and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789351A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for switching browsed interfaces |
| CN103761123A (en) * | 2013-12-31 | 2014-04-30 | 广州华多网络科技有限公司 | Method and device for function starting and terminal |
| CN104361004A (en) * | 2014-10-11 | 2015-02-18 | 北京奇虎科技有限公司 | Browser favorite data processing method and browser |
| CN104484165A (en) * | 2014-11-24 | 2015-04-01 | 北京奇虎科技有限公司 | Browser favorites data processing method, browser client and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101399724B (en) * | 2007-09-28 | 2011-11-30 | 中国电信股份有限公司 | Disposal authentication method for network access and service application oriented to user |
| CN103856458B (en) * | 2012-12-04 | 2018-12-11 | 腾讯科技（深圳）有限公司 | Page authentication method and device |
| CN104811462B (en) * | 2014-01-26 | 2018-05-18 | 中国移动通信集团北京有限公司 | A kind of access gateway reorientation method and access gateway |
| CN105868351B (en) * | 2016-03-29 | 2020-03-20 | 上海斐讯数据通信技术有限公司 | Access authentication page skipping method based on browser and user terminal |
-
2016
- 2016-03-29 CN CN201610185888.XA patent/CN105868351B/en active Active
- 2016-10-29 WO PCT/CN2016/103900 patent/WO2017166806A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789351A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for switching browsed interfaces |
| CN103761123A (en) * | 2013-12-31 | 2014-04-30 | 广州华多网络科技有限公司 | Method and device for function starting and terminal |
| CN104361004A (en) * | 2014-10-11 | 2015-02-18 | 北京奇虎科技有限公司 | Browser favorite data processing method and browser |
| CN104484165A (en) * | 2014-11-24 | 2015-04-01 | 北京奇虎科技有限公司 | Browser favorites data processing method, browser client and system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017166806A1 (en) | 2017-10-05 |
| CN105868351A (en) | 2016-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105868351B (en) | Access authentication page skipping method based on browser and user terminal | |
| US11716324B2 (en) | Systems and methods for location-based authentication | |
| CN106131079B (en) | Authentication method, system and proxy server | |
| US8448233B2 (en) | Dealing with web attacks using cryptographically signed HTTP cookies | |
| US9923897B2 (en) | Edge server selection for enhanced services network | |
| US10491685B2 (en) | Session transfer between resources | |
| EP3120591B1 (en) | User identifier based device, identity and activity management system | |
| CN104735066A (en) | Single sign-on method, device and system oriented to web page applications | |
| CN105873053B (en) | Method and system for embedding access authentication page into webpage and wireless access point | |
| US9509691B2 (en) | Secure transfer of web application client persistent state information into a new domain | |
| US11916905B2 (en) | Secure identity provider authentication for native application to access web service | |
| US10382305B2 (en) | Applying sequenced instructions to connect through captive portals | |
| EP3525411B1 (en) | Terminal authentication method and device | |
| CN114338078B (en) | CS client login method and device | |
| CN108933794B (en) | Method, device, equipment and server for joining enterprise policy | |
| CN114095483A (en) | Password substitution filling method and device, electronic equipment and storage medium | |
| EP2961125B1 (en) | Method for enhancing captive portal service | |
| CN113207123B (en) | Wireless network access method and device based on browser, storage medium and terminal | |
| CN113518091B (en) | Multi-user authentication method, device, system and storage medium | |
| US20230319025A1 (en) | Methods and systems for implementing unique session number sharing to ensure traceability | |
| CN117596015A (en) | Access method and device for network resources |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201112 Address after: Room 10242, No. 260, Jiangshu Road, Xixing street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. Address before: 201616 Shanghai city Songjiang District Sixian Road No. 3666 Patentee before: Phicomm (Shanghai) Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230327 Address after: 605, Floor 6, Building 1, Yard 3, Boda Road, Chaoyang District, Beijing, 100020 Patentee after: Beijing Sifang Hengtong Network Information Co.,Ltd. Address before: Room 10242, No. 260, Jiangshu Road, Xixing street, Binjiang District, Hangzhou City, Zhejiang Province Patentee before: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. |
|
| TR01 | Transfer of patent right |