An automatic login method, device and storage medium

Abstract

Embodiments of the present application disclose an automatic login method, device and storage medium. The method comprises: in the case that a gateway device is powered on and enters a network, calling a trusted authentication module plug-in to initiate a negotiation request to a trusted authentication platform; wherein the negotiation request carries gateway information; if the trusted authentication platform verifies the gateway information, receiving negotiation key association parameters sent by the trusted authentication platform, and generating a negotiation key based on the negotiation key association parameters; receiving an automatic login request sent by an electronic device; and if the automatic login request is authenticated, issuing an authentication token for automatic login for application software of the electronic device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an automatic login method, device and storage medium. Background Technology

[0002] With the increasing prevalence of electronic devices such as smart home devices, smart home devices that can provide multimedia content are gradually becoming the first type of smart devices that many families choose. These devices require account login before users can access the corresponding multimedia resources.

[0003] Currently, the login process uses SMS verification codes to access smart home devices. However, this method makes the SMS verification codes vulnerable to theft by SMS malware, posing a security risk. Summary of the Invention

[0004] This application aims to provide an automatic login method to address the security risks associated with smart home devices logging in via SMS verification codes, which are vulnerable to SMS Trojan viruses. This application uses the authentication negotiation result of the gateway device, i.e., the authentication token, as the root of trust for authentication of application software on connected electronic devices in the home network. This method features that the root of trust does not leave the gateway device, is not transmitted over the public network, and cannot be easily cracked by the operator's home gateway device, thus providing high security.

[0005] The technical solution of this application is implemented as follows:

[0006] An automatic login method, applied to a gateway device, the method comprising:

[0007] When the gateway device is powered on and connected to the network, the trusted authentication module plugin is invoked to initiate a negotiation request to the trusted authentication platform; wherein, the negotiation request carries gateway information;

[0008] If the trusted authentication platform verifies the gateway information, it receives the negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on the negotiation key association parameters;

[0009] Receive automatic login requests sent by electronic devices;

[0010] If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device.

[0011] An automatic login method, applied to an electronic device, the method comprising:

[0012] The application software calls the trusted authentication interface to send an automatic login request to the gateway device.

[0013] If the automatic login request is successfully authenticated, the gateway device receives an authentication token for automatic login issued by the gateway device for the application software; wherein, the authentication token is generated by authentication negotiation between the gateway device and the trusted authentication platform.

[0014] A gateway device, the gateway device comprising:

[0015] A trusted authentication module plugin is used to initiate a negotiation request to the trusted authentication platform when the gateway device is powered on and connected to the network; wherein the negotiation request carries gateway information.

[0016] The first receiving module is used to receive the negotiation key association parameters sent by the trusted authentication platform if the trusted authentication platform verifies the gateway information.

[0017] The trusted authentication module plugin is used to generate a negotiation key based on the negotiation key association parameters;

[0018] The first receiving module is used to receive an automatic login request sent by an electronic device;

[0019] The trusted authentication module plugin is used to issue an authentication token for automatic login to the application software of the electronic device if the automatic login request is successfully authenticated.

[0020] An electronic device, the electronic device comprising:

[0021] Application software used to call the trusted authentication interface to send automatic login requests to the gateway device;

[0022] The second receiving module is configured to receive an authentication token for automatic login issued by the gateway device for the application software if the automatic login request is successfully authenticated; wherein the authentication token is generated by authentication negotiation between the gateway device and the trusted authentication platform.

[0023] A gateway device / electronic device, the gateway device / electronic device comprising: a processor, a memory, and a communication bus;

[0024] The communication bus is used to realize the communication connection between the processor and the memory;

[0025] The processor is used to execute the automatic login program stored in the memory to implement the steps of the automatic login method described above.

[0026] A storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the automatic login method described above.

[0027] The automatic login method provided in this application involves, when the gateway device is powered on and connected to the network, invoking a trusted authentication module plugin to initiate a negotiation request to a trusted authentication platform. The negotiation request carries gateway information. If the trusted authentication platform verifies the gateway information, the method receives negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on these parameters. It also receives an automatic login request sent by an electronic device. If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device. This application uses the authentication negotiation result of the gateway device, i.e., the authentication token, as the root of trust for authentication of application software on connected electronic devices in the home network. This method possesses the characteristics that the root of trust does not leave the gateway device, is not transmitted over the public network, and cannot be easily cracked by the operator's home gateway device, thus exhibiting high security. Attached Figure Description

[0028] Figure 1 A flowchart illustrating the automatic login method provided in this application embodiment. Figure 1 ;

[0029] Figure 2 A flowchart illustrating the automatic login method provided in this application embodiment. Figure 2 ;

[0030] Figure 3 A schematic diagram of the gateway negotiation process provided in an embodiment of this application;

[0031] Figure 4 A flowchart illustrating the automatic login method provided in this application embodiment. Figure 3 ;

[0032] Figure 5 A flowchart illustrating the automatic login method provided in this application embodiment. Figure 4 ;

[0033] Figure 6 A schematic diagram illustrating the automatic login process of the application software of the electronic device provided in the embodiments of this application;

[0034] Figure 7 A schematic diagram illustrating the automatic binding of the device to the broadband main account as provided in this embodiment of the application;

[0035] Figure 8 This is a schematic diagram of the virtual structure of a gateway device provided in an embodiment of this application;

[0036] Figure 9 A virtual structural diagram of an electronic device provided in an embodiment of this application;

[0037] Figure 10 This is a schematic diagram of the physical structure of a gateway device provided in an embodiment of this application;

[0038] Figure 11 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0039] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0040] It should be understood that the phrases "embodiments of this application" or "foreign embodiments" throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "embodiments of this application" or "in the foreign embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0041] This application provides an automatic login method applied to a gateway device, as described in the following embodiments. Figure 1 As shown, the method includes the following steps:

[0042] Step 101: When the gateway device is powered on and connected to the network, call the trusted authentication module plugin to initiate a negotiation request to the trusted authentication platform.

[0043] The negotiation request includes gateway information. This gateway information includes the gateway network access identifier; of course, it may also include other information, such as gateway device information.

[0044] The gateway device in this application embodiment, also known as a smart gateway device, refers to an intelligent gateway unit provided by the operator when accessing the fiber optic network, connecting the home network and the external network. The smart gateway device can connect to the access node / access network through various network-side interfaces and to user-side electronic devices through user-side interfaces or user-side adapters. The trusted authentication module in the gateway device can be a native software module or a plug-in. User-side adapters include, but are not limited to, set-top boxes and speakers. User-side electronic devices include, but are not limited to, user terminal devices and smart home devices.

[0045] Step 102: If the trusted authentication platform verifies the gateway information, receive the negotiation key association parameters sent by the trusted authentication platform, and generate a negotiation key based on the negotiation key association parameters.

[0046] In this embodiment, the trusted authentication platform initiates a negotiation request to the digital home management platform based on gateway information. Upon successful authentication, the digital home management platform generates a negotiation key and allocates home bandwidth information, such as a home broadband identifier, and returns a successful authentication result to the trusted authentication platform. The trusted authentication platform can complete gateway negotiation authentication and generate authentication credentials. The digital home management platform can complete the activation, registration, and network access authentication of smart gateway devices.

[0047] In this embodiment, after the trusted authentication platform verifies the gateway information, the gateway device receives negotiation key association parameters sent by the trusted authentication platform. These parameters can be stored in a negotiation key (keystore, KS) file. Further, the gateway device generates a negotiation key based on the negotiation key association parameters. Here, the negotiation key association parameters are factors used to generate the negotiation key. The generated negotiation key is cached in the gateway device's local storage space.

[0048] Step 103: Receive the automatic login request sent by the electronic device.

[0049] In this application embodiment, when the electronic device is a smart home device, it includes, but is not limited to, smart home devices such as smart TVs, set-top boxes, speakers, and other smart home devices that provide multimedia information content.

[0050] In this embodiment, the automatic login request can be a request generated when a user launches an application software while using an electronic device. The automatic login request is used to request automatic login to the application software on the electronic device.

[0051] Step 104: If the automatic login request is successfully authenticated, issue an authentication token for automatic login to the application software of the electronic device.

[0052] In this embodiment, the gateway device determines the authentication status of the automatic login request based on the locally cached negotiation key. If the automatic login request is successfully authenticated, it issues an authentication token for automatic login to the application software of the electronic device. The authentication token is generated through authentication negotiation between the gateway device and the trusted authentication platform. Therefore, this embodiment uses the authentication negotiation result of the gateway device, i.e., the authentication token, as the root of trust for authentication of application software on connected electronic devices in the home network. This method possesses the characteristics that the root of trust does not leave the gateway device, is not transmitted over the public network, and cannot be easily cracked by the operator's home gateway device, thus providing high security.

[0053] The automatic login method provided in this application involves, when the gateway device is powered on and connected to the network, invoking a trusted authentication module plugin to initiate a negotiation request to a trusted authentication platform. This negotiation request carries gateway information. If the trusted authentication platform verifies the gateway information, the method receives negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on these parameters. It also receives an automatic login request from an electronic device. If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device. This application uses the authentication negotiation result of the gateway device, i.e., the authentication token, as the root of trust for authentication of application software on connected electronic devices in the home network. This method possesses the characteristics of the root of trust not leaving the gateway device, not being transmitted over the public network, and the operator's home gateway device being difficult to crack, thus providing high security.

[0054] This application provides an automatic login method, referring to... Figure 2 As shown, applied to gateway devices, the method includes the following steps:

[0055] Step 201: When the gateway device is powered on and connected to the network, call the trusted authentication module plugin to initiate a negotiation request to the trusted authentication platform.

[0056] The negotiation request carries gateway information. In this embodiment, the trusted authentication module plugin is referred to as the trusted authentication module.

[0057] Step 202: If the trusted authentication platform verifies the gateway information, receive the negotiation key association parameters sent by the trusted authentication platform, and generate a negotiation key based on the negotiation key association parameters.

[0058] If the trusted authentication platform verifies the gateway information in step 202 above, it can also receive the home broadband information assigned to the gateway device by the trusted authentication platform.

[0059] Home broadband information includes home broadband identifiers, such as broadband account numbers.

[0060] Step 203: Encrypt the character sequence composed of gateway information and application software business identifier based on the negotiated key to obtain the authentication token.

[0061] In this embodiment, an authentication token is generated and cached in local storage. The caching duration of the authentication token can also be set based on the configuration policy feedback from the trusted authentication platform, i.e., the validity period of the authentication token is configured. If the authentication token expires, the gateway device and the trusted authentication platform re-negotiate authentication to generate a new authentication token, further improving the security of automatic login.

[0062] Step 204: Receive the automatic login request sent by the electronic device.

[0063] Step 205: Check the negotiated key and generate the check result.

[0064] The inspection results include whether the negotiation key exists locally on the gateway device and / or whether the status of the negotiation key is in the preset state.

[0065] In this embodiment of the application, the preset state includes, but is not limited to, the negotiation key being valid.

[0066] Step 206: If the check result indicates that the gateway device has a negotiation key locally and the status of the negotiation key is the preset status, then the automatic login request authentication is confirmed to be successful.

[0067] Step 207: If the automatic login request is successfully authenticated, issue an authentication token for automatic login to the application software of the electronic device.

[0068] In an feasible gateway negotiation process, see [link to relevant documentation]. Figure 3 As shown,

[0069] Step 301: After the gateway device completes power-on and network access, it invokes the trusted authentication module plugin integrated in the gateway device to perform gateway authentication and transmits the gateway access identifier and gateway information assigned after successful gateway access.

[0070] Gateway authentication includes legitimacy verification and / or authorization of transmitted information. The gateway access identifier and gateway information assigned to the gateway device after successful network access are provided by the digital home management platform. The digital home management platform is also known as an optical line terminal (OLT) or digital home management platform.

[0071] Step 302: The gateway device calls the trusted authentication module plugin to preprocess the gateway information, and then establishes a secure connection with the trusted authentication platform to initiate the negotiation process.

[0072] In this embodiment, the preprocessing of gateway information includes, but is not limited to, data assembly and encryption of the gateway information. Gateway information includes, but is not limited to, serial number (SN) and media access control (MAC) address.

[0073] Step 303: Based on the parameter information passed from the trusted authentication module plugin, the trusted authentication platform sends a request to the digital home management platform to verify the gateway information.

[0074] Step 304: If the digital home management platform completes the verification of the gateway information, the authentication is successful, a KS is generated, and network access information such as the home broadband identifier is assigned. The authentication success result is returned to the trusted authentication platform. If the authentication fails, the authentication process ends.

[0075] Step 305: The gateway device calls the trusted authentication module plugin, receives the KS association parameters returned by the trusted authentication platform, calculates and generates the KS locally, caches it, and sets the cache duration of the KS according to the policy returned at the same time.

[0076] The gateway device that has successfully completed the authentication negotiation can issue the token required for automatic login capability to application software installed on electronic devices within the local area network, such as a home network. It can also serve as a transfer center when new devices access authentication.

[0077] This application provides an automatic login method, referring to... Figure 4 As shown, applied to electronic devices, the method includes the following steps:

[0078] Step 401: Send an automatic login request to the gateway device by calling the trusted authentication interface through the application software.

[0079] In this embodiment, "electronic device" refers to a user-side electronic device, including but not limited to user terminal devices. User terminal devices can be smart terminals, such as mobile phones, tablets, laptops, and other mobile terminal devices with wireless communication capabilities, or desktop computers and other inconveniently portable smart terminal devices; they can also be smart home devices. Smart home devices include home smart devices or networking devices with integrated trusted authentication and automatic login capabilities.

[0080] Among them, trusted authentication interfaces include, but are not limited to, software development kit (SDK) interfaces.

[0081] Step 402: If the automatic login request is successfully authenticated, receive the authentication token issued by the gateway device for automatic login to the application software.

[0082] The authentication token is generated during authentication negotiation between the gateway device and the trusted authentication platform.

[0083] The automatic login method provided in this application embodiment sends an automatic login request to the gateway device by calling a trusted authentication interface through application software. If the automatic login request is successfully authenticated, the application software receives an authentication token issued by the gateway device for automatic login. The authentication token is generated through authentication negotiation between the gateway device and the trusted authentication platform. In other words, this application uses the authentication negotiation result of the gateway device, i.e., the authentication token, as the root of trust for authentication of application software of connected electronic devices in the home network. It has the characteristics that the root of trust does not leave the gateway device, is not transmitted on the public network, and cannot be easily cracked by the operator's home gateway device, thus possessing high security.

[0084] This application provides an automatic login method, referring to... Figure 5 As shown, applied to electronic devices, the method includes the following steps:

[0085] Step 501: Send an automatic login request to the gateway device by calling the trusted authentication interface through the application software.

[0086] Step 502: If the automatic login request is successfully authenticated, receive the authentication token issued by the gateway device for automatic login to the application software.

[0087] The authentication token is generated during authentication negotiation between the gateway device and the trusted authentication platform.

[0088] Step 503: Initiate a login verification request to the business platform so that the business platform can forward the login verification request to the trusted authentication platform with the authentication token.

[0089] The login verification request carries an authentication token. The business platform is a service platform that provides services to smart home devices. Here, the login verification request may also carry a business identifier.

[0090] Step 504: Receive the home broadband information sent by the service platform, i.e., the synchronization login result.

[0091] Among them, the home broadband information is the information that the trusted authentication platform sends back to the business platform after the login verification request has been verified.

[0092] Step 505: Access the login success page based on home broadband information.

[0093] In this embodiment, electronic devices can directly access the login success page based on home broadband information. For home network scenarios, this provides maximum process simplification for users using various smart home device applications that require login authentication, minimizing the intervention and reliance of other devices or applications during the login authentication process.

[0094] In some embodiments of this application, the login verification request carries a service identifier, and step 505, which proceeds to the login success page based on home broadband information, can be implemented through the following steps:

[0095] First, if the priority of the business identifier meets the preset priority, the login authentication entry corresponding to the business identifier is displayed. The business identifier represents the security level requirement of the corresponding business; for example, the higher the security level requirement, the higher the priority of the business identifier. For instance, the business identifier of a payment application has a higher priority than that of a reading application.

[0096] Secondly, it receives a confirmation request for the login authentication entry and enters the login success page based on the home broadband information.

[0097] This application embodiment covers various usage scenarios in a home network environment, including smart home devices requiring user authentication and login confirmation, mobile / tablet applications, and personal computer (PC) applications. A unified login authentication entry point is provided for home-shared services using home broadband information, such as a unified broadband account.

[0098] In this embodiment, the electronic device can access the login success page based on home broadband information and the user's confirmation operation. In the context of home network scenarios, this not only reduces the intervention and reliance of other devices or applications during the login authentication process when users use various smart home device applications that require login authentication, but also further improves the security of login.

[0099] In the process of automatic login for application software on an achievable electronic device, see [link / reference]. Figure 6 As shown,

[0100] Step 601: The electronic device starts the application software. Under the premise that the network status is normal, the application software calls the trusted authentication SDK interface to send an automatic login SDK request to the gateway device. The authentication SDK and the gateway establish a communication channel.

[0101] Step 602: After receiving the SDK request, the gateway device calls the trusted authentication module plugin to check whether the local KS status is normal (including whether there is a security risk). If there is an abnormality, the negotiation process is re-initiated; otherwise, a Token is issued based on the business identifier and gateway information and returned to the application software of the electronic device.

[0102] Step 603: The electronic device calls the application software to make a login verification request to the business platform based on the token. The business platform sends a verification request to the trusted authentication platform with the gateway authentication token.

[0103] If the verification fails, the application software on the electronic device will be notified, and a prompt message will be displayed reminding the user to log in using an alternative method.

[0104] Step 604: If the verification is successful, the relevant broadband information is returned to the service platform. Once the service platform receives the successful authentication result, it synchronizes the login result to the application software of the electronic device, which then directly enters the login success page.

[0105] As can be seen from the above, this application uses the operator's home gateway as the central hub for home device authentication, providing a secure, unified, and efficient authentication method.

[0106] In a process that can automatically bind the device to the broadband main account, see [link to documentation]. Figure 7 As shown:

[0107] Step 701: Power on the smart terminal and automatically connect to the dedicated service set identifier (SSID) for the network.

[0108] The smart terminal is equipped with a unified terminal SDK, which is used to connect to a dedicated hidden SSID.

[0109] Step 702: The smart terminal reports authentication information and device information to its own networking equipment.

[0110] Among them, the self-owned networking equipment is equipped with a unified networking plugin, which can open the dedicated SSID for the distribution network, and can also synchronize passwords and reconnect to smart terminal devices.

[0111] Step 703: Verify the legality of the smart terminal using the self-owned networking equipment.

[0112] Among them, the smart terminal has pre-installed convenient authentication information, and the self-organizing network equipment can automatically complete local legal verification and network information synchronization.

[0113] Step 704: The self-contained networking device sends a network configuration confirmation request to the smart gateway device.

[0114] Specifically, if the user has already used the Hejiaqin service provided by China Mobile's unified authentication cloud platform, the Hejiaqin service will confirm their identity. If the user has not used the Hejiaqin service, the Subscriber Identification Module (SIM) will provide quick confirmation or SMS confirmation.

[0115] Of course, when the application software automatically logs in based on the broadband account and detects device usage, it can generate and output a reminder message to automatically prompt the user for confirmation. The application software has a synchronized binding relationship with the unified authentication cloud platform based on the broadband account.

[0116] Step 705: The smart gateway device issues a token to the smart terminal.

[0117] Step 706: The self-owned networking equipment issues a Token to the smart terminal and sends the networking name and password.

[0118] Step 707: The smart terminal connects to the internet, carries the token, and initiates device binding.

[0119] Based on this, the smart terminal automatically completes the binding between the device and the broadband host account.

[0120] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0121] Embodiments of this application provide a gateway device that can be applied to... Figure 1 In a corresponding embodiment of an automatic login method, refer to Figure 8 As shown, the gateway device 800 includes:

[0122] Trusted authentication module plug-in 801 is used to initiate a negotiation request to the trusted authentication platform when the gateway device is powered on and connected to the network; the negotiation request carries gateway information.

[0123] The first receiving module 802 is used to receive the negotiation key association parameters sent by the trusted authentication platform if the trusted authentication platform verifies the gateway information.

[0124] Trusted authentication module plugin 801 is used to generate a negotiation key based on the negotiation key association parameters;

[0125] The first receiving module 802 is used to receive automatic login requests sent by electronic devices;

[0126] Trusted Authentication Module Plug-in 801 is used to issue authentication tokens for automatic login to application software of electronic devices if the automatic login request is successfully authenticated.

[0127] In some embodiments of this application, the trusted authentication module plugin 801 is used to encrypt a character sequence composed of gateway information and the service identifier of the application software based on the negotiated key to obtain an authentication token.

[0128] In some embodiments of this application, the trusted authentication module plugin 801 is used to check the negotiated key and generate a check result; wherein, the check result includes whether the negotiated key exists locally on the gateway device and / or whether the state of the negotiated key is a preset state; if the check result indicates that the negotiated key exists locally on the gateway device and the state of the negotiated key is a preset state, it is determined that the automatic login request authentication is successful.

[0129] In some embodiments of this application, the first receiving module 802 is used to receive home broadband information allocated to the gateway device by the trusted authentication platform if the trusted authentication platform verifies the gateway information.

[0130] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0131] Embodiments of this application provide an electronic device that can be applied to... Figure 4 In a corresponding embodiment of an automatic login method, refer to Figure 9 As shown, the electronic device 900 includes:

[0132] Application software 901 is used to call the trusted authentication interface to send an automatic login request to the gateway device;

[0133] The second receiving module 902 is used to receive an authentication token for automatic login issued by the gateway device for the application software if the automatic login request is successfully authenticated; wherein, the authentication token is generated by the authentication negotiation between the gateway device and the trusted authentication platform.

[0134] In some embodiments of this application, application software 901 is used to initiate a login verification request to a business platform, so that the business platform carries an authentication token and forwards the login verification request to a trusted authentication platform; wherein, the login verification request carries an authentication token.

[0135] The second receiving module 902 is used to receive home broadband information sent by the service platform; wherein, the home broadband information is the information fed back to the service platform by the trusted authentication platform after the login verification request is verified.

[0136] Application software 901 is used to access the login success page based on home broadband information.

[0137] In some embodiments of this application, the login verification request carries a business identifier. The application software 901 is used to display the login authentication entry corresponding to the business identifier if the priority of the business identifier meets the preset priority.

[0138] The second receiving module 902 is used to receive confirmation operations for the login authentication entry.

[0139] Application software 901 is used to access the login success page based on home broadband information.

[0140] Embodiments of this application provide a gateway device that can be applied to... Figure 1 In a corresponding embodiment of an automatic login method, refer to Figure 10 As shown, the gateway device 1000 ( Figure 10In this context, gateway device 1000 is the physical device on the gateway side. Figure 8 The gateway device 800 (a virtual device on the gateway side) includes: a first processor 1001, a first memory 1002 and a first communication bus 1003, wherein: the first communication bus 1003 is used to realize the communication connection between the first processor 1001 and the first memory 1002.

[0141] The first processor 1001 is used to execute the automatic login program stored in the first memory 1002 to achieve the following steps: when the gateway device is powered on and connected to the network, the trusted authentication module plug-in is invoked to initiate a negotiation request to the trusted authentication platform; wherein, the negotiation request carries gateway information;

[0142] If the trusted authentication platform verifies the gateway information, it receives the negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on the negotiation key association parameters;

[0143] Receive automatic login requests sent by electronic devices;

[0144] If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device.

[0145] In some embodiments of this application, the first processor 1001 is used to execute the automatic login program stored in the first memory 1002 to implement the following steps: encrypting a character sequence composed of gateway information and the service identifier of the application software based on the negotiated key to obtain an authentication token.

[0146] In some embodiments of this application, the first processor 1001 is used to execute an automatic login program stored in the first memory 1002 to implement the following steps: checking the negotiation key and generating a check result; wherein, the check result includes whether the negotiation key exists locally on the gateway device and / or whether the status of the negotiation key is a preset state;

[0147] If the check results indicate that the gateway device has a negotiation key locally, and the negotiation key is in the preset state, then the automatic login request authentication is successful.

[0148] In some embodiments of this application, the first processor 1001 is used to execute the automatic login program stored in the first memory 1002 to implement the following steps: if the trusted authentication platform verifies the gateway information, receive the home broadband information allocated by the trusted authentication platform to the gateway device.

[0149] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0150] Embodiments of this application provide an electronic device that can be applied to... Figure 4 In a corresponding embodiment of an automatic login method, refer to Figure 11 As shown, the electronic device 1100 ( Figure 11 Electronic device 1100 is a physical device on the user side. Figure 9 The electronic device 900 (a virtual device on the user side) includes: a second processor 1101, a second memory 1102, and a second communication bus 1103, wherein: the second communication bus 1103 is used to realize the communication connection between the second processor 1101 and the second memory 1102.

[0151] The second processor 1101 is used to execute the automatic login program stored in the second memory 1102 to achieve the following steps: sending an automatic login request to the gateway device by calling the trusted authentication interface through application software;

[0152] If the automatic login request is successfully authenticated, the gateway device will receive an authentication token for automatic login issued by the application software; the authentication token is generated through authentication negotiation between the gateway device and the trusted authentication platform.

[0153] In some embodiments of this application, the second processor 1101 is used to execute an automatic login program stored in the second memory 1102 to implement the following steps: initiating a login verification request to the business platform, so that the business platform carries an authentication token to forward the login verification request to the trusted authentication platform; wherein, the login verification request carries an authentication token;

[0154] Receive home broadband information sent by the service platform; the home broadband information is the information fed back to the service platform by the trusted authentication platform after the login verification request is verified.

[0155] The login page was successfully accessed based on the home broadband information.

[0156] In some embodiments of this application, the second processor 1101 is used to execute the automatic login program stored in the second memory 1102 to implement the following steps: if the priority of the service identifier meets the preset priority, display the login authentication entry corresponding to the service identifier;

[0157] Receive confirmation for login authentication and access the login success page based on your home broadband information.

[0158] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0159] Embodiments of this application provide a computer storage medium storing one or more programs, which can be executed by one or more processors to perform the following steps:

[0160] When the gateway device is powered on and connected to the network, the trusted authentication module plugin is invoked to initiate a negotiation request to the trusted authentication platform; the negotiation request carries gateway information.

[0161] If the trusted authentication platform verifies the gateway information, it receives the negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on the negotiation key association parameters;

[0162] Receive automatic login requests sent by electronic devices;

[0163] If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device.

[0164] In some embodiments of this application, the one or more programs may be executed by one or more processors to perform the following steps: encrypting a character sequence composed of gateway information and the service identifier of the application software based on the negotiated key to obtain an authentication token.

[0165] In some embodiments of this application, the one or more programs may be executed by one or more processors to perform the following steps: checking the negotiation key and generating a check result; wherein, the check result includes whether the negotiation key exists locally on the gateway device and / or whether the status of the negotiation key is a preset state;

[0166] If the check results indicate that the gateway device has a negotiation key locally, and the negotiation key is in the preset state, then the automatic login request authentication is successful.

[0167] In some embodiments of this application, the one or more programs may be executed by one or more processors to achieve the following steps: if the trusted authentication platform verifies the gateway information, receive the home broadband information allocated by the trusted authentication platform to the gateway device.

[0168] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0169] Embodiments of this application provide a computer storage medium storing one or more programs, which can be executed by one or more processors to perform the following steps:

[0170] The application software calls the trusted authentication interface to send an automatic login request to the gateway device.

[0171] If the automatic login request is successfully authenticated, the gateway device will receive an authentication token for automatic login issued by the application software; the authentication token is generated through authentication negotiation between the gateway device and the trusted authentication platform.

[0172] In some embodiments of this application, the one or more programs may be executed by one or more processors to perform the following steps: initiating a login verification request to the business platform, so that the business platform carries an authentication token and forwards the login verification request to the trusted authentication platform; wherein, the login verification request carries an authentication token;

[0173] Receive home broadband information sent by the service platform; the home broadband information is the information fed back to the service platform by the trusted authentication platform after the login verification request is verified.

[0174] The login page was successfully accessed based on the home broadband information.

[0175] In some embodiments of this application, the login verification request carries a business identifier. The one or more programs can be executed by one or more processors to achieve the following steps: if the priority of the business identifier meets the preset priority, the login authentication entry corresponding to the business identifier is displayed.

[0176] Receive confirmation for login authentication and access the login success page based on your home broadband information.

[0177] It should be noted that the descriptions of the same steps and contents as in other embodiments in this embodiment can be found in the descriptions in other embodiments, and will not be repeated here.

[0178] It should be noted that the aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; it can also be various terminals that include one or any combination of the above-mentioned memory, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0179] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0180] The units described above 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 units may be selected to achieve the purpose of this embodiment according to actual needs.

[0181] Furthermore, in the various embodiments of this application, all functional units can be integrated into one processing module, or each unit can be a separate unit, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units. Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0182] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0183] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0184] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0185] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An automatic login method, characterized in that, Applied to a gateway device, wherein the gateway device is an intelligent gateway unit provided by an operator for connecting a home network and an external network when the fiber optic cable is brought into the network, the method includes: When the gateway device is powered on and connected to the network, the trusted authentication module plugin is invoked to initiate a negotiation request to the trusted authentication platform; wherein, the negotiation request carries gateway information; If the trusted authentication platform verifies the gateway information, the gateway receives the negotiation key association parameters sent by the trusted authentication platform and generates a negotiation key based on the negotiation key association parameters; the generated negotiation key is cached in the local storage space of the gateway device. Receive automatic login requests sent by electronic devices; The authentication status of the automatic login request is determined based on the negotiation key cached locally by the gateway device. If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device.

2. The method according to claim 1, characterized in that, After generating the negotiation key based on the negotiation key association parameters, the method further includes: The authentication token is obtained by encrypting a character sequence consisting of gateway information and the service identifier of the application software based on the negotiation key.

3. The method according to claim 1 or 2, characterized in that, After receiving the automatic login request sent by the electronic device, the method further includes: Check the negotiation key and generate a check result; wherein, the check result includes whether the negotiation key exists locally on the gateway device and / or whether the status of the negotiation key is a preset status; If the inspection result indicates that the negotiation key exists locally on the gateway device and the status of the negotiation key is the preset status, then the automatic login request authentication is successful.

4. The method according to claim 2, characterized in that, The method further includes: If the trusted authentication platform verifies the gateway information, it receives the home broadband information assigned to the gateway device by the trusted authentication platform.

5. An automatic login method, characterized in that, Applied to electronic devices, including: The application software calls the trusted authentication interface to send an automatic login request to the gateway device; the gateway device is an intelligent gateway unit provided by the operator when fiber optic network access connects the home network and the external network. If the automatic login request is successfully authenticated, the gateway device receives an authentication token for automatic login issued by the gateway device for the application software; wherein the authentication token is generated by authentication negotiation between the gateway device and the trusted authentication platform; the gateway device is used to execute the method of any one of claims 1 to 4.

6. The method according to claim 5, characterized in that, The method further includes: A login verification request is initiated to the business platform, so that the business platform forwards the login verification request to the trusted authentication platform carrying the authentication token; wherein, the login verification request carries the authentication token; Receive home broadband information sent by the service platform; wherein, the home broadband information is the information fed back to the service platform by the trusted authentication platform after the login verification request has been verified and passed. Based on the aforementioned home broadband information, the user was redirected to a successful login page.

7. The method according to claim 6, characterized in that, The login verification request carries a service identifier, and the step of entering the login success page based on the home broadband information includes: If the priority of the service identifier meets the preset priority, the login authentication entry corresponding to the service identifier will be displayed; The system receives a confirmation request for the login authentication entry and then accesses the login success page based on the home broadband information.

8. A gateway device, characterized in that, The gateway device is an intelligent gateway unit provided by the operator when fiber optic network access connects the home network and the external network. The gateway device includes: A trusted authentication module plugin is used to initiate a negotiation request to the trusted authentication platform when the gateway device is powered on and connected to the network; wherein the negotiation request carries gateway information. The first receiving module is used to receive the negotiation key association parameters sent by the trusted authentication platform if the trusted authentication platform verifies the gateway information. The trusted authentication module plugin is used to generate a negotiation key based on the negotiation key association parameters; the generated negotiation key is cached in the local storage space of the gateway device. The first receiving module is used to receive an automatic login request sent by an electronic device; The trusted authentication module plugin is used to determine the authentication status of the automatic login request based on the negotiation key cached locally by the gateway device. If the automatic login request is successfully authenticated, an authentication token for automatic login is issued to the application software of the electronic device.

9. An electronic device, characterized in that, The electronic device includes: The application software is used to call the trusted authentication interface to send an automatic login request to the gateway device; the gateway device is an intelligent gateway unit provided by the operator when fiber optic network access connects the home network and the external network. The second receiving module is configured to receive an authentication token for automatic login issued by the gateway device for the application software if the automatic login request is successfully authenticated; wherein the authentication token is generated by authentication negotiation between the gateway device and the trusted authentication platform; the gateway device is configured to execute the method of any one of claims 1 to 4.

10. A storage medium, characterized in that, The device stores executable instructions that, when executed, cause the processor to perform the automatic login method as described in any one of claims 1 to 4 or 5 to 7.

Images