Method, device and storage medium for accessing a web management page of a router

Abstract

The application relates to the technical field of communication, and provides a router web management page access method, equipment and a storage medium. The method applied to the router side comprises the following steps: in the case that the router has connected an external network, receiving a password-free login instruction for accessing a router web management page sent by a second user terminal; when the second user terminal does not exist in a password-free access white list, sending a network request to a cloud platform to drive the cloud platform to send login audit information to a first user terminal serving as a router side administrator; receiving reply information fed back by the first user terminal; the reply information comprises rejection, single-time consent or multiple-time consent; and when the reply information is multiple-time consent, adding the second user terminal to the password-free access white list. According to the application, the router web access white list is managed and maintained by the administrator equipment, so that the second user terminal which does not originally exist in the white list can also realize password-free access to the router web page and can realize multiple-time access, and the interactive process is simplified.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a router web management page access method, device and storage medium. BACKGROUND

[0002] Generally, a home user uses a router to surf the Internet, modify wifi, select a channel, and the like, which needs the following steps: first, obtaining the IP address of the lan port of the router, then accessing the IP through a browser, then logging in a username and a password, and finally configuring in the form of a web menu.

[0003] The default web password of the router is a random combination of letters / numbers and special characters, which is pasted on the back of the nameplate. On the one hand, the nameplate information will be worn out over time, resulting in the loss of the factory password. On the other hand, since the use scenario of the web page is less and the login frequency is low, the user often forgets the username and password after modifying them, and thus cannot log in. Although the original nameplate password can be reset by restoring the factory settings of the device, the user's other configuration information will also be deleted. SUMMARY

[0004] The router web management page access method, device and storage medium provided by the embodiments of the present application solve the technical problem that the password is easily forgotten or lost when accessing the router web page.

[0005] In a first aspect, the embodiments of the present application provide a router web management page access method applied to the router side, comprising: in the scenario that the router has connected to the external network, receiving the password-free login instruction for accessing the router web management page sent by a second user terminal; when the second user terminal does not exist in the password-free access whitelist, sending a network request to a cloud platform; the network request is used to drive the cloud platform to send login audit information to a first user terminal as the administrator of the router side; receiving the reply information fed back by the first user terminal based on the login audit information through the cloud platform; wherein the reply information includes rejection, single-time consent or multiple-time consent; when the reply information is rejection, the current password-free access of the second user terminal is not allowed; when the reply information is single-time consent, the current password-free access of the second user terminal is allowed, but the second user terminal is not added to the password-free access whitelist; when the reply information is multiple-time consent, the current password-free access of the second user terminal is allowed, and the second user terminal is added to the password-free access whitelist.

[0006] In one embodiment, the passwordless access whitelist is a MAC address whitelist; after receiving the passwordless login instruction sent by the second user terminal to access the router's web management page, the method includes: obtaining the MAC address of the second user terminal by parsing the passwordless login instruction; comparing the MAC address of the second user terminal with the MAC address whitelist; and determining that the second user terminal does not exist in the passwordless access whitelist when the MAC address of the second user terminal does not match the MAC address whitelist.

[0007] In one embodiment, the method further includes: receiving a passwordless login instruction sent by a third user terminal to access the router's web management page; obtaining the MAC address of the third user terminal by parsing the passwordless login instruction; comparing the MAC address of the third user terminal with a MAC address whitelist; determining that the second user terminal does not exist in the passwordless access whitelist when the MAC address of the second user terminal matches the MAC address whitelist; and allowing passwordless access for the third user terminal.

[0008] In one embodiment, allowing the second user terminal to access the page without a password includes: determining the device type of the second user terminal; wherein the device type includes a computer and a mobile device; adaptively adjusting the URL path of the page access according to the device type; and adaptively adjusting the front-end template of the page access according to the device type.

[0009] In one embodiment, the router and the cloud platform establish an IoT long-term connection via the Internet; and / or, the router and any user terminal communicate via a local short-range protocol.

[0010] Secondly, embodiments of this application provide a method for accessing a router's web management page, applied to a first user terminal acting as a router administrator. The method includes: receiving login verification information sent by a cloud platform when the router is connected to the external network; wherein the login verification information is generated by the cloud platform in response to a network request; the network request is generated by the router in response to a passwordless login command issued by a second user terminal; the second user terminal is not on the router's passwordless access whitelist; responding to the login verification information, sending feedback information to the cloud platform; wherein the feedback information includes rejection, single-time approval, or multiple-time approval; when the feedback information is rejection, the router does not allow the second user terminal to access the router's web management page passwordless for this instance; when the feedback information is single-time approval, the router allows the second user terminal to access the router's web management page passwordless for this instance, but does not add the second user terminal to the passwordless access whitelist; when the feedback information is multiple-time approval, the router allows the second user terminal to access the router passwordless for this instance and adds the second user terminal to the passwordless access whitelist.

[0011] Thirdly, embodiments of this application provide a method for accessing a router web management page, applied to a second user terminal, comprising: in a scenario where the router is connected to the external network, sending a passwordless login instruction to the router side to access the router web management page; wherein the passwordless login instruction is used to drive the router side to send a network request to the cloud platform; the network request is used to drive the cloud platform to send login verification information to a first user terminal acting as the router side administrator; the second user terminal is not present in the passwordless access whitelist on the router side; receiving the passwordless login result fed back by the router side; wherein the passwordless login result includes rejection, single approval, or multiple approvals; when the passwordless login result is rejection, the current passwordless login fails; when the passwordless login result is single approval, the current passwordless login succeeds; when the passwordless login result is multiple approvals, the current passwordless login succeeds and is added to the passwordless access whitelist.

[0012] Fourthly, this application provides a method for accessing a router's web management page, applied to a cloud platform, comprising: receiving a network request sent by the router in a scenario where the router is connected to the external network; wherein the network request is generated by the router in response to a passwordless login command issued by a second user terminal; the second user terminal is not in the router's passwordless access whitelist; generating login verification information in response to the network request, and sending the login verification information to a first user terminal acting as the router's administrator; receiving feedback response information from the first user terminal; wherein the response information includes rejection, single-time agreement, or multiple-time agreement; forwarding the response information to the router so that the router generates a passwordless login result; when the response information is rejection, the router does not allow the second user terminal to access the router's web management page passwordless this time; when the response information is single-time agreement, the router allows the second user terminal to access the router's web management page passwordless this time, but does not add the second user terminal to the passwordless access whitelist; when the response information is multiple-time agreement, the router adds the second user terminal to the passwordless access whitelist.

[0013] Fifthly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the router web management page access method described in the first to fourth aspects.

[0014] Sixthly, embodiments of this application provide a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for accessing a router web management page as described in the first to fourth aspects.

[0015] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the router web management page access method described in the first to fourth aspects.

[0016] The router web management page access method, device, and storage medium provided in this application, applied to the router side, include: receiving a passwordless login command from a second user terminal to access the router's web management page when the router is connected to the external network; when the second user terminal is not in the passwordless access whitelist, sending a network request to the cloud platform to drive the cloud platform to send login verification information to the first user terminal, which is the router administrator; receiving a response from the first user terminal based on the login verification information through the cloud platform; disallowing the second user terminal's current passwordless access when the response is a denial; allowing the second user terminal's current passwordless access when the response is a single agreement, but not adding the second user terminal to the passwordless access whitelist; allowing the second user terminal's current passwordless access when the response is multiple agreements, and adding the second user terminal to the passwordless access whitelist. Through the above methods, this application enables second user terminals that are not originally on the whitelist to achieve passwordless access to the router's web page and can achieve multiple accesses by managing and maintaining the router's web access whitelist through the administrator device, eliminating the need for login usernames and passwords, avoiding scenarios such as users forgetting or losing passwords, and simplifying the interaction process. Attached Figure Description

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

[0018] Figure 1 This is one of the flowcharts illustrating the method for accessing a router web management page provided in an embodiment of this application;

[0019] Figure 2 This is a schematic diagram illustrating the process of adapting a web front-end page to the device type, as provided in an embodiment of this application.

[0020] Figure 3 This is a second flowchart illustrating the method for accessing the router's web management page provided in this application embodiment;

[0021] Figure 4 This is the third flowchart illustrating the method for accessing the router's web management page provided in this application embodiment;

[0022] Figure 5 This is the fourth flowchart illustrating the method for accessing the router web management page provided in this application embodiment;

[0023] Figure 6 This is a schematic diagram of device interaction on the router web management page provided in an embodiment of this application;

[0024] Figure 7 This is a schematic diagram of the physical structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0026] In order to enable users to configure routers more quickly and conveniently, some methods are provided in related technologies. For example, accessing the configuration request through a browser can directly open the configuration page of the WIFI router. However, this method does not verify and distinguish users, which poses a security risk. In addition, users cannot manage and maintain the router access permission list, and cannot achieve administrator privileges.

[0027] Based on this, this application provides a method for accessing a router's web management page. Please refer to... Figure 1 , Figure 1 This is one of the flowcharts illustrating a method for accessing a router's web management page provided in this application embodiment. The method for accessing a router's web management page in this embodiment is applied to the router side and includes steps S110 to S130, each step of which is detailed below:

[0028] S110: In scenarios where the router is already connected to the external network, receive passwordless login commands from a second user terminal to access the router's web management page.

[0029] S120: When the second user terminal is not in the passwordless access whitelist, send a network request to the cloud platform.

[0030] S130: Receives response information from the first user terminal based on login verification information via the cloud platform.

[0031] In the router web management page access method of this embodiment, the execution entities involved may include the router side, the first user terminal, the second user terminal, and the cloud platform (device server side). In other embodiments, other connected STA terminals and third user terminals may also be involved.

[0032] It should be noted that, in the definition of this embodiment, the first user terminal is a router-side administrator, who can exist in the router-side passwordless access whitelist and can manage the passwordless access whitelist; the second user terminal in the initial state does not exist in the router-side passwordless access whitelist, but can perform single or multiple passwordless accesses based on the reply information from the first user terminal; the third user terminal is an ordinary user who exists in the router-side passwordless access whitelist but does not have management functions.

[0033] When a second user terminal performs a single passwordless access, the router does not need to add the second user terminal to the passwordless access whitelist. When the second user terminal needs to perform passwordless access again, the first user terminal still needs to verify and confirm.

[0034] When a second user terminal makes multiple passwordless access attempts, the router can add the second user terminal to the passwordless access whitelist. When the second user terminal needs to make a passwordless access attempt again, the first user terminal will not need to verify or confirm the request.

[0035] Furthermore, multiple passwordless accesses can include permanent passwordless access or passwordless access with time limits or frequency limits.

[0036] Among them, the network request is used to drive the cloud platform to send login verification information to the first user terminal, which is the router-side administrator.

[0037] Optionally, the router and the cloud platform establish a long-lived IoT connection via the Internet; and / or, the router and any user terminal communicate via a local short-range protocol without relying on the Internet.

[0038] The response message can be either "deny," "one-time consent," or "multiple consents." When the response message is "deny," the second user terminal's current passwordless access is not permitted. When the response message is "one-time consent," the second user terminal's current passwordless access is permitted, but the second user terminal is not added to the passwordless access whitelist. When the response message is "multiple consents," the second user terminal's current passwordless access is permitted, and the second user terminal is added to the passwordless access whitelist.

[0039] This embodiment provides a method for accessing a router's web management page, applied to the router side. The method includes: when the router is connected to the external network, receiving a passwordless login command from a second user terminal to access the router's web management page; when the second user terminal is not on the passwordless access whitelist, sending a network request to the cloud platform to drive the cloud platform to send login verification information to a first user terminal acting as the router administrator; receiving a response from the first user terminal based on the login verification information through the cloud platform; when the response is "reject," disallowing the second user terminal's current passwordless access; when the response is "one-time agreement," allowing the second user terminal's current passwordless access, but not adding the second user terminal to the passwordless access whitelist; when the response is "multiple agreements," allowing the second user terminal's current passwordless access, and adding the second user terminal to the passwordless access whitelist. Through this method, this embodiment enables second user terminals that are not originally on the whitelist to achieve passwordless access to the router's web page and can achieve multiple accesses, eliminating the need for login usernames and passwords, avoiding scenarios where users forget or lose their passwords, and simplifying the interaction process.

[0040] In one embodiment, the passwordless access whitelist is a MAC address whitelist; after receiving the passwordless login instruction sent by the second user terminal to access the router's web management page, the method includes: obtaining the MAC address of the second user terminal by parsing the passwordless login instruction; comparing the MAC address of the second user terminal with the MAC address whitelist; and determining that the second user terminal does not exist in the passwordless access whitelist when the MAC address of the second user terminal does not match the MAC address whitelist.

[0041] In one embodiment, the method further includes: receiving a passwordless login instruction sent by a third user terminal to access the router's web management page; obtaining the MAC address of the third user terminal by parsing the passwordless login instruction; comparing the MAC address of the third user terminal with a MAC address whitelist; determining that the second user terminal does not exist in the passwordless access whitelist when the MAC address of the second user terminal matches the MAC address whitelist; and allowing passwordless access for the third user terminal.

[0042] Optionally, the user terminal in this embodiment can be regarded as a client with a preset APP installed.

[0043] Any user terminal can connect to the home router's Wi-Fi and bind to the home router via a local short-range protocol (such as CoAP / MQTT) and a private interface. During binding, its MAC address is automatically synchronized to the router.

[0044] The router can be configured with a MAC address whitelist. For example, the MAC address of the device where the app is located can be saved locally and added to the web access whitelist. Only the specified device MAC address can directly access the router's web page without a password.

[0045] When a user accesses the router's web page through the terminal where the app is located, the router parses and identifies the source MAC address of the packet and compares it with the MAC address whitelist. If the MAC address matches, the user can directly access the router's web page without needing to log in with an account and password.

[0046] When a user accesses the router's web page using another terminal (such as sta_unbind), the MAC address whitelist fails, and the user is redirected to the web login page, which displays the username and password input fields, as well as a "Passwordless Login" button.

[0047] It should be noted that in scenarios where the router has no external network access, the "Password-free login" button is grayed out, requiring non-app-bound terminals to pass strong password verification.

[0048] For example, in a scenario where the router is connected to the external network, the access process includes:

[0049] 1) Users can click the "Password-free Login" button, and the router sends a network request to the cloud platform. The cloud platform then pushes messages to the user's app based on the binding relationship.

[0050] 2) The user app selects whether to agree to "passwordless login". If "deny" is selected, a message is pushed to the router through the platform, and the web page displays "passwordless login failed".

[0051] 3) If "Always Agree" is selected, the app sends a message to the cloud platform, updates the MAC address book in the cloud, adds the MAC address, and pushes the message to the router.

[0052] Upon receiving the message, the router responds with `sta_unbind` to redirect to the management page; simultaneously, it saves the device's MAC address to local flash memory and updates the MAC address book. Subsequently, the device can directly access the router's web page without a password.

[0053] 4) If "Agree Once" is selected, the app sends a message to the cloud platform and then pushes it to the router. The router redirects to the management page but does not add its MAC address.

[0054] In summary, the router web management page access method provided in this embodiment enables seamless, passwordless access to the web management page within the intranet environment, whether the router is not connected to the external network or is already connected. This is achieved by binding user app actions and automatically synchronizing the user's MAC address to the web whitelist, based on a local short-range protocol. When the router is connected to the external network, the user can manage and maintain the router's web access whitelist through the app, dynamically adding and deleting other connected terminals to determine whether a device can log in to the router's web page without a password. Therefore, user terminals can access the router's web page without a password, eliminating the need for usernames and passwords and avoiding scenarios where users forget or lose their passwords, thus simplifying the interaction process. Furthermore, the router uses MAC address filtering rules to implement the web access whitelist, ensuring the security of passwordless login.

[0055] In one embodiment, allowing the second user terminal to access the page without a password includes: determining the device type of the second user terminal; wherein the device type includes a computer and a mobile device; adaptively adjusting the URL path of the page access according to the device type; and adaptively adjusting the front-end template of the page access according to the device type.

[0056] Router web pages are designed for PCs by default and are not well-suited for mobile browsing. With the increasing prevalence and development of mobile internet, more and more users are accustomed to browsing the internet on mobile devices, and the system has not considered users accessing web pages and configuring routers on mobile devices. Given the distinct characteristics of mobile and PC interfaces and the wide variety of mobile devices, there is currently no universally compatible interface that can adapt to both.

[0057] Some solutions have been proposed in related technologies, such as reusing a set of web pages for PC and mobile devices. However, this may lead to problems in layout, page design, and SEO, resulting in a poor user experience. Another solution is to convert a PC page to a mobile page, but this will lead to longer page loading time and decreased performance.

[0058] The adaptive router web front-end page solution proposed in this embodiment is designed to optimize and improve mobile devices' access to the router's web page via wireless means. It intelligently determines the device type through multiple methods, thereby confirming different URL paths and deploying multiple web front-end templates to achieve adaptive adaptation for both mobile and PC front-ends.

[0059] Please see Figure 2 , Figure 2 This is a schematic diagram of the process for adapting a web front-end page to the device type according to an embodiment of this application. This embodiment includes steps S210 to S250, each step as follows:

[0060] S210: User terminal accesses the router's web page.

[0061] In this embodiment, the user terminal can be any one of a first user terminal, a second user terminal, or a third user terminal.

[0062] S220: Determine the device type of the user terminal.

[0063] Optionally, the type of the connected STA device can be identified by: obtaining the hostname that comes with the device when it connects (if none, it will be the default; if it does, it will contain fields such as "phone", "desktop", or "PC"); and resolving option 12 based on the OPTION in the DHCP protocol to obtain the type of the connected device (Statype).

[0064] Alternatively, the IP address range can be used to determine this: the PC connects via wired Ethernet (usually LAN1-LAN4 ports), while the mobile device connects via Wi-Fi (RA0 / RAW). Different LAN ports correspond to their respective IP address ranges; therefore, the PC and mobile device will be assigned different IP address ranges.

[0065] Optionally, different terminal types can be identified by obtaining the IP address of the connected terminal, combining it with querying the LAN port IP address range configuration, and comparing it with the IP address range of the PC and mobile terminal.

[0066] Optionally, User Agent detection can be used to determine the device type: examining the User Agent header of the user's HTTP request to obtain device type information, thereby determining the device type and operating system. For example, common User Agents for PCs might include keywords such as "Windows" or "Macintosh," while those for mobile devices might include keywords such as "Android" or "iOS." By analyzing the User Agent, it can be determined whether the user is accessing the webpage from a PC or a mobile device.

[0067] Alternatively, device resolution can be used to determine the type of device: PCs and mobile devices typically have different screen resolutions and display characteristics. PCs usually have higher resolutions, such as 1920x1080, while mobile devices typically have lower resolutions, such as 800x480. Routers can distinguish device types based on the screen resolution information carried in the request from the connected device.

[0068] S230: Adaptively modify URL path.

[0069] In some embodiments, the default access path is / pc. When the system intelligently identifies the device as a mobile device, the default / pc in the path is changed to / mobile.

[0070] S240: Access different front-end templates on the router.

[0071] S250: Router Web page response.

[0072] This embodiment deploys different front-end templates and intelligently identifies different terminal device types and adds URL paths to differentiate access to the front-end, thereby achieving adaptive web page design. By combining multiple methods, it intelligently identifies different terminal device types, and the web management page adapts to both PC and mobile devices, effectively distinguishing different terminals and providing users with similar layouts, navigation, and functions, thereby reducing user learning costs and confusion.

[0073] Please see Figure 3 , Figure 3 This is the second flowchart illustrating the method for accessing a router web management page provided in this application embodiment. The method for accessing a router web management page in this embodiment is applied to a first user terminal acting as a router administrator, and includes steps S310 to S320, each step of which is detailed below:

[0074] S310: When the router is connected to the external network, it receives login verification information sent by the cloud platform.

[0075] The login verification information is generated by the cloud platform in response to the network request; the network request is generated by the router in response to the passwordless login command issued by the second user terminal; the second user terminal does not exist in the passwordless access whitelist on the router side.

[0076] S320: In response to login verification information, send a reply message to the cloud platform.

[0077] The response information includes denial, one-time consent, or multiple consents. When the response is denial, the router does not allow the second user terminal to access the router's web management page without a password for this time. When the response is one-time consent, the router allows the second user terminal to access the router's web management page without a password for this time, but does not add the second user terminal to the passwordless access whitelist. When the response is multiple consents, the router allows the second user terminal to access the router without a password for this time, and adds the second user terminal to the passwordless access whitelist.

[0078] Please see Figure 4 , Figure 4 This is the third flowchart illustrating the method for accessing a router web management page provided in this application embodiment. The method for accessing a router web management page in this embodiment is applied to a second user terminal and includes steps S410 to S420, each step of which is detailed below:

[0079] S410: In scenarios where the router is already connected to the external network, send a passwordless login command to the router to access the router's web management page.

[0080] The passwordless login command is used to drive the router to send a network request to the cloud platform; the network request is used to drive the cloud platform to send login verification information to the first user terminal, which is the router administrator; the second user terminal does not exist in the passwordless access whitelist on the router side.

[0081] S420: Receives the passwordless login result from the router.

[0082] The passwordless login result includes rejection, single consent, or multiple consents. When the passwordless login result is rejection, the passwordless login fails. When the passwordless login result is single consent, the passwordless login succeeds. When the passwordless login result is multiple consents, the passwordless login succeeds and the user is added to the passwordless access whitelist.

[0083] Please see Figure 5 , Figure 5 This is the fourth flowchart illustrating the method for accessing a router's web management page provided in this application embodiment. The method for accessing a router's web management page in this embodiment is applied to a cloud platform and includes steps S510 to S540, each step of which is detailed below:

[0084] S510: When the router is already connected to the external network, it receives network requests sent by the router.

[0085] The network request is generated by the router in response to the passwordless login command issued by the second user terminal; the second user terminal is not in the passwordless access whitelist on the router side.

[0086] S520: In response to a network request, it generates login verification information and sends the login verification information to the first user terminal that acts as the router-side administrator.

[0087] S530: Receives feedback and response information from the first user terminal.

[0088] The response information includes rejection, single consent, or multiple consent.

[0089] S540: Forwards the reply information to the router side so that the router side can generate a passwordless login result.

[0090] When the response is "deny", the router does not allow the second user terminal to access the router's web management page without a password for this time; when the response is "one-time consent", the router allows the second user terminal to access the router's web management page without a password for this time, but does not add the second user terminal to the passwordless access whitelist; when the response is "multiple consents", the router adds the second user terminal to the passwordless access whitelist.

[0091] Please see Figure 6 , Figure 6 This is a schematic diagram of device interaction on the router web management page provided in an embodiment of this application.

[0092] In this embodiment, the devices that interact include the APP (administrator, equivalent to the first user terminal), the router, and other terminals (ordinary users, equivalent to the second user terminal).

[0093] The app requests binding with the router. The router saves the corresponding MAC address and returns a binding success message to the app. The app accesses the router's web page, and the router's MAC whitelist (equivalent to a passwordless access whitelist) verifies the MAC address. Therefore, the app can achieve seamless passwordless login and directly jump to the management page.

[0094] When other devices access the router's web page and the router's whitelist verification fails, the router needs to request verification from the app and push the message to the app. At this time, the app administrator selects permissions, such as deny, temporarily agree, or permanently agree, and is redirected to the management page.

[0095] In addition, during routine maintenance, the APP administrator can add / delete MAC addresses to update the whitelist. Once the update is successful, the router will send a message back to the APP.

[0096] On the other hand, embodiments of this application also provide an electronic device. Figure 7 This is a schematic diagram of the physical structure of the electronic device provided in the embodiments of this application, such as... Figure 7 As shown, the electronic device may include: a memory 720, a processor 710, and a computer program stored in the memory 720 and executable on the processor 710. When the processor 710 executes the program, it implements the methods for accessing the router web management page provided by the methods described above.

[0097] Optionally, the electronic device may further include a communication bus 730 and a communication interface 740, wherein the processor 710, the communication interface 740, and the memory 720 communicate with each other through the communication bus 730. The processor 710 can call a computer program in the memory 720 to execute a method for accessing the router's web management page, as detailed in the above embodiments.

[0098] Furthermore, the logical instructions in the aforementioned memory 720 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0099] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the router web management page access method provided in the above embodiments. The steps and principles of the method have been described in detail in the above methods and will not be repeated here.

[0100] On the other hand, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the access method for the router web management page provided by the above methods. The steps and principles of the access method have been described in detail in the above methods and will not be repeated here.

[0101] Non-transitory computer-readable storage media can be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0102] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0103] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0104] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for accessing a router's web management page, characterized in that, Applied to the router side, including: In scenarios where the router is already connected to the external network, receive a passwordless login command from a second user terminal to access the router's web management page; When the second user terminal is not in the passwordless access whitelist, a network request is sent to the cloud platform; the network request is used to drive the cloud platform to send login verification information to the first user terminal, which is the router-side administrator. The cloud platform receives response information from the first user terminal based on the login verification information; wherein the response information includes rejection, single consent, or multiple consent. When the response message is "deny", the second user terminal is not allowed to access the passwordless device for this time; when the response message is "one-time consent", the second user terminal is allowed to access the passwordless device for this time, but the second user terminal is not added to the passwordless access whitelist; when the response message is "multiple consents", the second user terminal is allowed to access the passwordless device for this time, and the second user terminal is added to the passwordless access whitelist.

2. The method for accessing the router web management page according to claim 1, characterized in that, The passwordless access whitelist is a MAC address whitelist; after receiving the passwordless login command sent by the second user terminal to access the router's web management page, the process includes: The MAC address of the second user terminal is obtained by parsing the passwordless login command; Compare the MAC address of the second user terminal with the MAC address whitelist; When the MAC address of the second user terminal does not match the MAC address whitelist, it is determined that the second user terminal does not exist in the passwordless access whitelist.

3. The method for accessing the router web management page according to claim 2, characterized in that, Also includes: Receive passwordless login instructions sent by a third-party user terminal to access the router's web management page; The MAC address of the third user terminal is obtained by parsing the passwordless login command; Compare the MAC address of the third user terminal with the MAC address whitelist; When the MAC address of the second user terminal matches the MAC address whitelist, it is determined that the second user terminal does not exist in the passwordless access whitelist. Passwordless access is permitted for the third user terminal.

4. The method for accessing the router web management page according to claim 1, characterized in that, The permission granted to the second user terminal for this passwordless access includes: Determine the device type of the second user terminal; wherein the device type includes computer and mobile terminal. The URL path for page access is adaptively adjusted based on the device type. The front-end template for page access is adaptively adjusted based on the device type.

5. The method for accessing a router web management page according to any one of claims 1-4, characterized in that, The router and the cloud platform establish an IoT long connection via the Internet; and / or, the router and any user terminal communicate via a local short-range protocol.

6. A method for accessing a router's web management page, characterized in that, Applied to the first user terminal used by the router administrator, including: In a scenario where the router is already connected to the external network, login verification information is received from the cloud platform; wherein the login verification information is generated by the cloud platform in response to a network request; the network request is generated by the router in response to a passwordless login command issued by the second user terminal; the second user terminal is not in the passwordless access whitelist on the router side; In response to the login verification information, a reply message is sent to the cloud platform; wherein the reply message includes rejection, single consent, or multiple consents. When the response message is "deny", the router does not allow the second user terminal to access the router's web management page without a password for this instance; when the response message is "one-time consent", the router allows the second user terminal to access the router's web management page without a password for this instance, but does not add the second user terminal to the passwordless access whitelist; when the response message is "multiple consents", the router allows the second user terminal to access the router without a password for this instance, and adds the second user terminal to the passwordless access whitelist.

7. A method for accessing a router's web management page, characterized in that, Applied to second user terminals, including: In a scenario where the router is already connected to the external network, a passwordless login command to access the router's web management page is sent to the router side; wherein the passwordless login command is used to drive the router side to send a network request to the cloud platform; the network request is used to drive the cloud platform to send login verification information to the first user terminal, which is the router side administrator; the second user terminal is not present in the passwordless access whitelist on the router side. Receive the passwordless login result fed back from the router side; wherein the passwordless login result includes rejection, single consent, or multiple consent; When the passwordless login result is "rejected", the passwordless login fails; when the passwordless login result is "one-time consent", the passwordless login succeeds; when the passwordless login result is "multiple consents", the passwordless login succeeds and is added to the passwordless access whitelist.

8. A method for accessing a router's web management page, characterized in that, Applied to cloud platforms, including: In a scenario where the router is already connected to the external network, a network request is received from the router side; wherein the network request is generated by the router side in response to a passwordless login command issued by the second user terminal; and the second user terminal is not in the passwordless access whitelist of the router side. In response to the network request, login verification information is generated and sent to the first user terminal acting as the router-side administrator; Receive feedback information from the first user terminal; wherein the feedback information includes rejection, single consent, or multiple consents. The reply information is forwarded to the router so that the router generates a passwordless login result. When the response message is "deny", the router does not allow the second user terminal to access the router's web management page without a password for this time; when the response message is "one-time consent", the router allows the second user terminal to access the router's web management page without a password for this time, but does not add the second user terminal to the passwordless access whitelist; when the response message is "multiple consents", the router adds the second user terminal to the passwordless access whitelist.

9. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the method for accessing the router web management page as described in any one of claims 1 to 8.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for accessing the router web management page as described in any one of claims 1 to 8.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for accessing the router web management page as described in any one of claims 1 to 8.

Images