Login request processing method, mobile device and intelligent hardware device

文档序号:1046448 发布日期:2020-10-09 浏览:12次 中文

阅读说明:本技术 登录请求处理方法、移动设备及智能硬件设备 (Login request processing method, mobile device and intelligent hardware device ) 是由 蔡伟杰 戴福玲 唐显锭 刘衡峰 杨鑫 郭超 杜家成 于 2019-03-26 设计创作,主要内容包括:本发明公开了一种登录请求处理方法、移动设备及智能硬件设备。该登录请求处理方法包括:在第一网络环境中接收到第一设备发起的登录请求;获取与第一网络环境相关联的至少一个已登录的账号的活跃度信息;以及基于所述活跃度信息,确定潜在登录账号,其中,所述潜在登录账号是在所述第一网络环境中发生过历史登录行为的账号。(The invention discloses a login request processing method, mobile equipment and intelligent hardware equipment. The login request processing method comprises the following steps: receiving a login request initiated by a first device in a first network environment; acquiring activity information of at least one logged account associated with a first network environment; and determining a potential login account number based on the activity information, wherein the potential login account number is an account number in which historical login behaviors occur in the first network environment.)

1. A method for login request processing, comprising:

receiving a login request initiated by a first device in a first network environment;

acquiring activity information of at least one logged account associated with a first network environment; and

determining a potential login account number based on the activity information, wherein the potential login account number is an account number in which historical login behaviors occur in the first network environment.

2. The login request processing method according to claim 1, further comprising:

logging in the potential login account on the first device without user interaction or without user password entry interaction.

3. A login request processing method according to claim 2, wherein the potential login account is an account for which a historical login behavior occurred using a second device in the first network environment, and the first device and the second device are small-screen devices.

4. A login request processing method according to claim 2, wherein said potential login account is an account for which a historical login behavior has occurred using a second device in said first network environment, and the first device is a large-screen device and the second device is a small-screen device.

5. The login request processing method of claim 4, wherein the small-screen device comprises at least one of a smartphone, a tablet computer, and a notebook computer, and the large-screen device comprises at least one of a television, a kiosk, a set-top box, and a projector.

6. The login request processing method according to claim 1, further comprising:

determining whether the first network environment is secure; and

logging in the potential login account on the first device without requiring user interaction or without requiring user input of a password in the event that the first network environment is secure.

7. The login request processing method according to claim 1, wherein obtaining activity information of at least one logged-in account associated with the first network environment further comprises:

the activity information is obtained based on a service set identifier SSID and/or a basic service set identifier BSSID of the first device currently performing the login.

8. The login request processing method according to claim 1, wherein obtaining activity information of at least one logged-in account associated with the first network environment further comprises:

obtaining cumulative liveness information of at least one logged-in account, an

Wherein determining a potential login account based on the liveness information further comprises:

and determining the potential login account with higher activity based on the accumulated activity information.

9. The login request processing method of claim 1, wherein determining a potential login account based on the liveness information further comprises:

determining a potential login account based on at least one of an asset status and an account rating of at least one logged in account and based on the liveness information.

10. The login request processing method of claim 1, wherein determining a potential login account based on the liveness information further comprises:

determining that a small-screen device which is active at one time is currently in a first network environment; and

and taking the login account used by the small screen device which is active once as the potential login account.

11. A mobile device, comprising:

the mobile device comprises a receiving component and a processing component, wherein the receiving component is used for receiving information of a potential login account, and the potential login account is an account in which historical login behaviors occur in a first network environment where the mobile device is currently located;

a processing component to log in the potential login account on the mobile device.

12. The mobile device of claim 11, wherein the processing component is to log in the potential login account directly on the mobile device without user interaction.

13. The mobile device of claim 11, further comprising:

a display component for displaying the potential login account; and

an input component for inputting a selection of the displayed potential login account;

wherein the processing component is configured to log in the potential login account on the mobile device based on the selection without requiring user interaction to enter a password.

14. The mobile device of claim 11, wherein the potential login account is determined based on liveness information of at least one logged-in account associated with the first network environment.

15. The mobile device of claim 11, wherein the processing component is further configured to determine whether the first network environment is a secure network environment and, if the first network environment is a secure network environment, to re-execute the operation of logging into the potential login account on the mobile device.

16. The mobile device of claim 15, wherein the secure network environment is a home network environment and the mobile device is a cell phone or a tablet computer.

17. The mobile device of claim 15, wherein the potential login account is an account that is not recorded in the mobile device.

18. An intelligent hardware device, comprising:

the receiving component is used for receiving information of a potential login account, wherein the potential login account is an account in which historical login behaviors occur in a first network environment where the intelligent hardware device is currently located; and

a processing component configured to log in the potential login account on the intelligent hardware device.

19. The intelligent hardware device of claim 18 wherein the processing component is configured to log in the potential login account directly on the intelligent hardware device without user interaction.

20. The intelligent hardware device of claim 18, further comprising:

a display component for displaying the potential login account; and

an input component for inputting a selection of the displayed potential login account;

wherein the processing component is configured to log in the potential login account on the smart hardware device based on the selection without requiring a user to input a password for interactive operation.

Technical Field

The present invention relates to login of a large screen device, and more particularly, to a method, a mobile device, and an intelligent hardware device for processing a login request.

Background

Electronic devices of users can be divided into large-screen devices and small-screen devices according to screen sizes. Large screen devices and small screen devices are relative. The screen of a large screen device is larger than that of a small screen device. For example, a large screen device refers to a television, a device with an android system (such as a kiosk, an internet set-top box, a projector, etc.). The small screen includes, for example, a mobile phone device, a tablet computer, and the like.

Generally, after a user purchases a large-screen device (such as a television, etc.), or after the user installs corresponding software on his/her large-screen device (such as a kiosk, a projector, etc.), the user can watch video content on the large-screen device. If a user wishes to obtain a better quality, customized service (such as 4k definition, dolby sound, membership advertisement free, membership free, etc.), the user typically needs to log in using an account provided by the content provider. After the user logs in the account through the large-screen device or corresponding software in the large-screen device, the content provider identifies the user identity and the member rights and interests of the user according to the account.

Generally speaking, it is inconvenient to input information in large-screen devices such as televisions and projectors compared with small-screen devices such as mobile phones and tablet computers. In order to help a user log in a large-screen device, there are several common login solutions in the industry.

1. Two-dimensional code mode

First, an operator (user) who is to use a large-screen device scans a two-dimensional code on a screen of the large-screen device using a small-screen device such as a mobile phone. And the user logs in an account on the small-screen device and synchronizes the account login condition of the mobile phone to the large-screen device.

2. Mobile phone number login

First, the user inputs a mobile phone number on the television using the remote controller, and the server transmits a verification code to the user's mobile phone. And the user checks the verification code on the mobile phone and inputs the verification code on the television by using the remote controller for logging in.

3. Scenarios for re-login

Large screen devices such as televisions record account information that the user has last logged in. The user selects the account information to log in.

In the login mode in the prior art, the operation steps of a user are long, and large-screen equipment and small-screen equipment are required to carry out interactive operation. In the context of a home application, the operator of a large screen device may be a number of family members, i.e. may be elderly or young. Therefore, the current technical solutions have the following problems.

1. For a login operation on a large screen device, a newly logged-in user may encounter the following problems: 1) the operator may not be familiar with the operation of the digital product, so that he does not perform a login operation; 2) if the account needing to be logged in is the account of the child who may not be around, the old person cannot be informed of the short message verification code or help him to log in; 3) when a user logs in through an account of a mobile phone, if the account needing to be logged in is an account of other family members, the user may not know the password of the account, or the user may forget the password when logging in the account of the user, so that the login process on the mobile phone is interrupted, and the login on a television is terminated; 4) in the login mode in the prior art, a user needs to use keys of a remote controller to input information, and the operation is inconvenient; 5) each login behavior of a user includes the whole process from request login to final login success, which takes a long time and causes a large number of factors for login suspension or login failure, which results in a poor user experience and makes the user unable to enjoy a better service.

2. A user logging on again on a large screen device may encounter the following problems: 1) in the method of recording the historical login account, the user is required to log in successfully once, and if the user modifies the account password at other terminals, the login on the large-screen device fails; 2) if the large-screen device restores factory settings or resets the system, the historical login account number will be lost.

Therefore, it is desirable to provide a new technical solution, which is improved in view of at least one of the technical problems in the prior art.

Disclosure of Invention

It is an object of the present invention to provide a new solution for login request handling.

According to a first aspect of the present invention, there is provided a method for login request processing, comprising: receiving a login request initiated by a first device in a first network environment; acquiring activity information of at least one logged account associated with a first network environment; and determining a potential login account number based on the activity information, wherein the potential login account number is an account number in which historical login behaviors occur in the first network environment.

According to a second aspect of the present invention, there is provided a mobile device comprising: a receiving component, configured to receive information of a potential login account, where the potential login account is an account in which a historical login behavior occurs in a first network environment in which a mobile device is currently located, and the potential login account is an account that is not recorded in the mobile device; and a processing component for logging in the potential login account on the mobile device.

According to a third aspect of the invention, there is provided an intelligent hardware device comprising: the receiving component is used for receiving information of a potential login account, wherein the potential login account is an account in which historical login behaviors occur in a first network environment where the intelligent hardware device is currently located; and a processing component for logging in the potential login account on the intelligent hardware device.

According to the embodiment of the invention, the login processing can be simplified, so that the use experience of the user during login is improved.

Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.

FIG. 1 shows a schematic block diagram of a cloud system that may be used to implement embodiments of the invention.

Fig. 2 shows a schematic flow chart of a login method according to an embodiment of the invention.

Fig. 3-6 show prior art login procedures.

FIG. 7 is a flow diagram of a process flow according to one example of the invention.

Fig. 8-13 show a specific example according to the present invention.

Fig. 14-16 show an example of a mobile device according to the invention.

Fig. 17 shows an example of an intelligent hardware device according to the invention.

Detailed Description

Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.

In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

Various embodiments and examples according to the present invention are described below with reference to the accompanying drawings.

< hardware configuration >

Fig. 1 is a schematic diagram showing a cloud system that may be used to implement embodiments of the present disclosure.

As shown in fig. 1, the cloud system includes a cloud infrastructure 1100 and home network environments 1300, 1400, and the like.

A plurality of cloud servers 1200 are included in the cloud infrastructure 1100. The cloud server 1200 includes, for example, a processor 1201 and a memory 1202.

The home network environment 1300, 1400 is connected to the cloud infrastructure 1100 through a wired network and/or a wireless network, and acquires data and/or services from the cloud.

For example, the home network environment 1300, 1400 includes access points 1301, 1401. The access points 1301, 1401 may be connected to the cloud infrastructure 1100 by wire, wirelessly, or a combination of both. The home network environment 1300, 1400 also includes, for example, large-screen devices 1302, 1402 such as television sets and small-screen devices 1303, 1403 such as cell phones. Fig. 1 shows large screen devices 1302, 1402 and small screen devices 1303, 1403 connected to access points 1301, 1401 by wireless means. However, it will be understood by those skilled in the art that the large screen devices 1302, 1402 and the small screen devices 1303, 1403 may also be connected to the access points 1301, 1401 by wire.

Users 1304, 1404 can log in to accounts stored in cloud infrastructure 1100 through large-screen devices 1302, 1402 and small-screen devices 1303, 1403, and obtain data and services from cloud infrastructure 1100.

The cloud system shown in fig. 1 is merely illustrative and is in no way intended to limit the present invention, its applications, or uses.

< method >

Fig. 2 is a schematic flow diagram of a login method according to an embodiment of the present invention.

As shown in fig. 2, a login request initiated by a first device is received in a first network environment at step S2100.

At step S2200, activity information of at least one logged-in account associated with the first network environment is acquired.

In step S2300, a potential login account is determined based on the activity information, wherein the potential login account is an account in which historical login behavior occurred in the first network environment.

For example, the first network environment may be defined by a service set identifier SSID and/or a basic service set identifier BSSID. The first network environment is, for example, the home network environment 1300, 1400 shown in fig. 1.

In this embodiment, the interactive flow of the user for logging in can be simplified. For example, in the same network environment, when logging in on another device using account information once, the server at the back end may directly recommend account information required for logging in to the current user. In this case, the user can use the account information to log in directly on the current device. For example, a user may select a login account from a plurality of potential login accounts to log in without manually entering a username and password. In this way, the user simplifies the interaction between different devices at login.

In one example, after determining the potential login account, the account may be automatically logged in through the first device. For example, the potential login account may be directly logged in on the first device without requiring interaction by the user. The interaction here is for login processing, and when performing other processing, interaction between the user and the electronic device may be required. Generally, the interactive operation at login includes: inputting a user name, inputting a password, inputting a mobile phone number or inputting an authentication code and the like. Optionally, the potential login account may also be logged in on the first device without requiring user interaction to enter a password.

For example, the potential login account is an account for which historical login behavior occurred using a second device in the first network environment, and the first device and the second device are small-screen devices.

Advantageously, the first device is a large screen device and the second device is a small screen device. The small-screen device may include at least one of a smartphone, a tablet computer, and a laptop computer. The large screen device may include at least one of a television, a kiosk, a set-top box, and a projector. Small screen devices are referred to as large screen devices. Small-screen devices have a smaller screen overall than large-screen devices. For example, the screen of a cell phone is typically smaller than the screen of a television.

In another example, to ensure the security of the login operation, login may be allowed in an interactive login-free manner only if the network environment is secure. For example, it may be determined whether the first network environment is secure. Logging in the potential login account on the first device without requiring user interaction or without requiring user input of a password in the event that the first network environment is secure. For example, a home network environment may be considered secure. The network condition (first network environment) of the first device can be judged through the network security type and/or the network identification information of the network environment, so that whether the account provided for the user is safe or not is determined. When the network security type acquired by the cloud server is a home network, the cloud server may directly provide the account information to the user. Since the main application scenario of entertainment devices such as televisions is the home environment, this approach can be applied to most application scenarios. This is simple, effective and safe.

In embodiments of the present disclosure, the server may automatically provide account information to the user based on historical login conditions. The first device may automatically use the account information to log in, or the user may select corresponding account information to log in. This is particularly convenient for the elderly and children.

In this embodiment, the cloud server may determine to provide the account information to the user for the user to log in based on the activity information of the logged-in account. In this process, even if the user has never logged in using the current device, the user does not have to perform a difficult input operation using the remote controller. The user can log in the current equipment more conveniently, and the use experience of the user can be greatly improved.

In this manner, a user logging on to the first device may not need to obtain or otherwise know the specific content of the account information, but may only use content that is permitted by the account information. Therefore, this approach is more secure for the account information itself.

The potential login account may be account information of an account currently online and an active account that has historically kept logged in and actively logged in the first network environment. Both of these situations indicate that the potential login account is currently in a valid, active state and that it is appropriate for the user to login using that account.

Here, there may also be multiple potential login accounts that are valid. In this case, the plurality of potential login accounts may also be ranked based on at least one of user usage liveness and equity of the plurality of potential login accounts; and presenting the ranked plurality of potential login accounts to the user on the first device for the user to login on the first device. In this way, more choices can be provided to the user, which is more advantageous for the user's use.

In addition, the device (second device) that has used the potential login account to perform historical login behavior in the first network environment may be notified of the login situation of the first device, so as to further improve security. For example, login information of a user logging in at a first device using a potential login account may be recorded; and sending the login information to the device which has performed the historical login behavior so as to inform the user of the second device of the login on the first device. The login information includes, for example, information such as a device identifier of the first device, an account number used for login, and the like.

In this case, the second device may cancel the login of the first device if the second device considers the login of the first device to be inappropriate. For example, the server may receive a message from the second device to cancel the login status on the first device.

For example, the first network environment may be a wireless network.

Here, active login behavior may be determined to provide a potential login account. For example, a login account with active login behavior in the first network environment is determined as the potential login account for the current user to log in for use. Generally speaking, the active login behavior of a user in a network environment indicates the trust of the user in the network environment. Therefore, the login of the active login is provided for other devices in the same network environment, which is more consistent with the use situation of the general user, and the mode is relatively safe.

< apparatus >

Those skilled in the art will appreciate that in the field of electronics, the above-described methods may be embodied in articles of manufacture by software, hardware, and combinations of software and hardware. The person skilled in the art will easily be able to produce a logging device based on the above disclosed method, comprising means for performing the steps of the above described method.

Further, for example, the technical solution according to the present disclosure may be implemented by an electronic device such as the computing system described in fig. 1. For example, the technical solution may be embodied by a program written based on a language such as C language, Java language. Instructions of the program are stored, for example, in the non-removable, non-volatile memory 1141 or the removable, non-volatile memory, and when executed by the computing system, are read into the system memory 1130, which when executed by the processor 1120, cause the processor 1120 to implement the described techniques.

The described solution may be implemented in one computing device or may be distributed among a plurality of computing devices.

Hence, here, also an electronic device for logging in may be realized, comprising a memory storing instructions and a processor, wherein the instructions, when executed by the processor, cause the processor to perform the steps of the above-described method. For example, the electronic device is a server or the like.

< example >

First, a login request processing method according to the related art will be described with reference to fig. 3 to 6, and then, a login request processing method according to the present invention will be explained with reference to fig. 7 to 13. Fig. 14-15 show examples of application of the invention on a mobile device.

When a user wishes to obtain the service of the content provider, the user can log in the server system of the content provider through a mobile phone, or can log in the server system of the content provider through a television through a remote controller. Fig. 3-6 illustrate several prior art login request processing approaches. Fig. 3 to 5 show a case where the user logs in through the television for the first time, and fig. 6 shows a case where the user logs in again in a case where the user has logged in using the television once.

As shown in fig. 3, in step S101, the user turns on the television, and the television establishes a connection with the server system through the network and enters a login interface in the television. In step S102, the user inputs a user name in the login interface. Next, in step S103, the user inputs a password in the login interface. In step S104, the television transmits the user name and the password to the server to complete login. The user may then use the services provided by the content provider.

As shown in fig. 4, in step S201, the user turns on the television, and the television establishes a connection with the server system through the network and enters a login interface in the television. In step S202, the two-dimensional code is displayed in the login interface, and the user scans the two-dimensional code on the screen of the television using the mobile phone. In step S203, the mobile phone obtains a login interface based on the two-dimensional code, and the user outputs a user name and the two-dimensional code on the login interface of the mobile phone. In step S204, the mobile phone sends the user name and the password to the server to complete the login. After the login is completed, the television enters a content page, and the user can use the service provided by the content provider through the television.

As shown in fig. 5, in step S301, the user turns on the television, and the television establishes a connection with the server system through the network and enters a login interface in the television. In step S302, the user inputs his/her mobile phone number on the login interface of the television using the remote controller. In step S303, the tv sends the mobile phone number to the server, and the server sends the verification code to the mobile phone, for example, by SMS message. In step S304, the user views the authentication code on the mobile phone and then inputs the authentication code into the television using the remote controller. In step S305, the television transmits the authentication code to the server to complete the login. After the login is completed, the television enters a content page, and the user can use the service provided by the content provider through the television.

In fig. 6, the user has previously performed a login using the television, and the television records the user name and password of the user login. In step S401, the user turns on the television, and the television establishes a connection with the server system through the network and enters a login interface in the television. Since the user has previously performed a login, the television records the username and password of the previously logged-in account. The accounts may be presented in a list in a login interface. In step S402, the user selects an account that was logged in from the login interface. In step S403, the user name and password of the account saved in the television are sent to the server to complete login. After the login is completed, the television enters a content page, and the user can use the service provided by the content provider through the television.

In the prior art, unless the user has already performed login in the television and there is no change in the account that was logged in, the user needs to perform a complicated input operation to log in. On one hand, the user experience is not good; on the other hand, these operations may present difficulties for certain family members, for example, for the elderly and children.

Fig. 7 shows an example of a login request process according to the present disclosure. In the example of fig. 7, as shown in block 520, even if the user has not logged in using the tv, the tv does not store the user name and password of the user account, and the tv can automatically recommend the account to the user for the user to select, thereby simplifying the user operation during login.

As shown in fig. 7, in step 501, a user opens a large-screen device, the large-screen device establishes a connection with a server, and requests login. And the large-screen equipment sends a login request to the server. The large screen device is for example a television set.

At step 502, the server detects whether there is a historical login account on the large screen device.

If there is a history login account, in step 511, a history login account list is displayed on the large screen device for the user to select. In step 512, the user selects a historical login account in the list of historical login accounts, thereby completing the login on the large screen device.

If there is no historical login account, then at step 521, it is identified whether there is a recommended account. Whether there is a recommended account can be determined by the method disclosed in the embodiments herein through the environmental information.

If there are recommended accounts, then at step 522, a list of recommended accounts is displayed on the large screen device for selection by the user. The recommended account may be determined in the manner described above, that is, the activity information of at least one logged account associated with the current network environment is obtained, and the recommended account is determined based on the activity information. The recommended account is an account for which historical login behavior has occurred in the current network environment.

Here, the liveness information may be acquired based on network environment information. For example, the network environment where the television is located is determined based on the SSID and/or BSSID of the large-screen device currently performing login, and thus the account number and the activity information thereof that have been logged in the network environment are acquired. The recommended account is an account that is active in the current network environment and that has actively initiated historical login behavior through a small-screen device, such as a cell phone.

In addition, the accumulated activity information of the logged account can be obtained, and the recommended account with higher activity can be determined based on the accumulated activity information. The cumulative liveness represents, for example, a number of times and/or a length of time that the account number has been logged in cumulatively over a period of time.

In addition, the recommended account may be determined based on at least one of an asset status and an account rating of the at least one logged-in account and based on the liveness information.

When the large-screen device requests login, the small-screen device which has performed the historical login behavior before may be in the current network environment or may not be in the current network environment. For example, when a large-screen device initiates a login request in a current network environment, the small-screen device is in a different network environment from the current network environment or is not connected to the network.

Advantageously, small-screen devices that have previously undergone historical login behavior are also currently located in the same current network environment as large-screen devices. In this case, it may also be determined that the small-screen device that was active is now in the current network environment. And taking the login account used by the small-screen device which is active once as the recommended account. Since both the large screen device and the small screen device are in the current network, the manner of providing the login account in this situation is more secure.

In step 523, the user selects a recommended account in the recommended account list, thereby completing login on the large-screen device. Alternatively, a login account may be automatically used on a large screen device for login.

If no account is recommended, operation may proceed in the prior art manner. At step 530, the default login method is displayed on the large screen device.

For example, in the first approach, the user enters a phone number in the large screen device using a remote control, step 531. And then, the user receives the short message verification code through the small-screen device and continues to input the short message verification code by using the remote controller so as to log in. At step 532, login on the large screen device is completed.

In the second approach, the user logs in using the small screen device at step 541. At step 542, after the user completes the login using the small-screen device, the login on the small-screen device is synchronized to the large-screen device. At step 543, the login on the large screen device is completed.

Here, the identification method and login interaction for recommending the account number to the large-screen device can be simplified. For example, in a home scenario, a user may own multiple small-screen devices (e.g., cell phones) and large-screen devices (e.g., televisions). These devices are all active in the same network environment. When a user uses an account on a client of the small-screen device in the network environment, the server can collect and record login account information of the user and corresponding environment information, including network environment information, device information, current login state and other information.

In the above examples, the embodiments according to the present disclosure have been described with a large-screen device as the first device and a small-screen device as the second device. Further, the first device and the second device may both be small-screen devices or large-screen devices. The current network environment in which the first device is located is the first network environment. As long as there is a device that has experienced historical login behavior in the current network environment, according to embodiments of the present disclosure, the login process for the user may be simplified. Advantageously, when the step in block 520 of fig. 7 is applied, it may be determined that the current network environment is a secure network environment, for example, a home network environment.

Fig. 8-13 are schematic diagrams of an example according to the present invention. In this example, fig. 8 to 10 show a case where the user logs in using the television set 3000 as a large-screen device, and fig. 11 to 13 show a case where the user monitors the login of the large-screen device using the cellular phone 4000 as a small-screen device.

As shown in fig. 8, the user performs login using the television set 3000. An entry 3100 for the user to log in an account is displayed on the screen of the television 3000.

After the user clicks on the portal 3100, the television 3000 displays the interface of fig. 9. A plurality of potential login accounts 3201, 3202, 3203, 3204 are provided in the interface of fig. 9 for user login use. The potential login account is an account for which historical login behavior occurred in the first network environment. The plurality of account information 3201, 3202, 3203, 3204 is provided to the user based on the manner described in the foregoing embodiment. For example, liveness information of at least one logged-in account associated with a first network environment may be first obtained; and determining potential login accounts 3201, 3202, 3203, 3204 based on the liveness information. For example, in fig. 9, the user has selected the first login account 3201. Alternatively, a login account may be automatically selected for the user.

As shown in fig. 9, login is performed using a potential login account 3201. Block 3300 of FIG. 10 shows the user having completed logging in, and returns to the previous portal interface, where the user account that has logged in is displayed at block 3300.

After the login is completed on the television 3000, the corresponding mobile phone user may be notified of the login situation in various ways. Various ways of notifying the user are shown in fig. 11-12, and fig. 13 shows the process after the user receives the notification.

For example, as shown in fig. 11, the user of the cellular phone 4000 may be notified of the login on the television 3000 by a system message method 4100.

For example, as shown in fig. 12, the user of the cellular phone 4000 may be notified of the login on the television 3000 by a short message 4200.

After receiving the notification, the user can manage login on the television 3000 via the mobile phone. For example, as shown in fig. 13, for a user login on the television 3000, the user may select a corresponding management item 4300 in the cell phone 4000. When the user selects the management item 4300, an option may be provided for the user to delete the login on the television 3000.

When a user initiates a login request using a large-screen device in the network environment, the server may first determine whether the network environment is a secure environment, for example, a home environment. Here, non-home network environments, office network environments, shopping mall network environments, and the like may be excluded, and the identification recommendation of the account is not performed for these network environments. Secondly, in this case, the server may provide the user with the recommended account information according to a certain policy. For example, the server may recommend a plurality of "currently online account" and "active account that has historically kept logged in and actively logged in under the WIFI" according to SSID information of a wireless network, MAC address information of a wireless gateway, identification information of the current device, and other information transmitted by the large-screen device. In this case, some abnormal account information, for example, account information that has expired, account information that has not been used for a long time, and the like, may be deleted based on security considerations. The filtered account information may then be prioritized for display on the interface of the large screen device according to rules such as user activity, equity level, and the like. The user can select a desired account number from the interface of the large-screen device, so as to perform login operation.

Here, when making an account identification recommendation, it may not be required that "a small-screen device to be registered and a large-screen device must be currently in the same network environment". This solution is particularly advantageous in the case of children who are not near the elderly.

In addition, in this scheme, the security type of the network can be identified, so that "the user remembers the account password or sets account password information in advance on a designated page" is not required. Such automated processing may enhance the user experience.

Generally, when a large-screen device and a small-screen device are in the same network, network environment information, gateway information, device information, and the like of the network are passively exposed in a local area network. Therefore, in the embodiment, the user does not need to additionally perform special authority authorization. The user may not experience the identification process of the server, thereby improving the user experience.

After the user finishes logging in by using the large-screen device, the logging record can be returned to the server, and the server can process the logging record so as to continuously learn and optimize the security model and the recommendation strategy algorithm model of the account of the server. After the user finishes logging in on the large-screen device, the server can send a mobile phone short message and a mobile phone client system message to the user of the account logged in on the large-screen device so as to remind the user of the logging-in condition on the large-screen device. If the user does not wish to recommend the account on the large screen device, or if the user wishes to be in a non-login state on the large screen device, the user may operate on a small screen device, such as a cell phone, to cancel the login state of the account on the large screen device (e.g., as shown in the "login device management" interface in fig. 8).

In embodiments of the present disclosure, the user's interaction behavior may be simplified. For example, a user selects "login" on a large screen device (e.g., as shown in FIG. 3); the large screen device displays an account recommendation page (e.g., as shown in fig. 4); the user presses a key on the remote control to select an account number, thereby completing a large screen login (e.g., as shown in fig. 5). In the large-screen equipment login operation in the prior art, complicated large-screen equipment and small-screen equipment login interaction is required, and the large-screen equipment and the small-screen equipment are required to be beside an operator at the same time; however, in the embodiment of the present disclosure, the login operation of the large-screen device is greatly simplified, and the user only needs to perform a simple key selection operation by using the remote controller to complete the login. Embodiments of the present disclosure enable a "N to 1" simplification of the operational steps.

In the account identification scheme in the embodiment of the disclosure, when a user initiates a login request on a certain large-screen device, the server may screen accounts according to SSID information of a wireless network, MAC information of a wireless gateway, current device information and other information transmitted by the large-screen device. Such screening may take account of account security, for example. For example, it may be determined whether the environment of the currently logged-in device is secure. By determining the information of the network environment, the operating system environment, the login position and the like of the current user, whether the current environment of the user is safe can be identified. For example, it may also be determined whether the user's account is secure, i.e., the account's account status (e.g., theft risk index, number of account shares, number of account offsite logins). From this information, it can be determined whether the account is allowed to automatically log in. For example, the accounts recommended on the large-screen device may be filtered through the following rules:

1. according to the SSID, BSSID and the like of the large-screen equipment which is logged in at present, the small-screen equipment is determined to use the account number to conduct active login behavior in the same network environment;

2. screening out user accounts with higher liveness according to the recent accumulated liveness of the accounts in the current network environment;

3. screening out user accounts with higher value according to the asset condition and the user level of the account; and

4. and according to whether the small-screen device corresponding to the account is currently in the current network environment.

The account numbers can be screened based on the above rules and preferentially recommended to the user who uses the large-screen device, so that the safety and the user experience are both considered.

Furthermore, the present invention can also be directly applied to mobile devices. When the mobile device enters the current network environment, the potential login account can be automatically recommended to the mobile device, so that the trouble that the new mobile device needs to be manually logged in when entering the current network environment is avoided. Fig. 14-16 show such an example. The mobile device 5000 shown in fig. 14-16 is a cell phone. Furthermore, the mobile device may also be a tablet computer or the like.

When a user wishes to log on to a system of a content provider using the cellular phone 5000 in a new network environment, the user opens a corresponding application on the cellular phone 5000. The cell phone 5000 communicates with a server on the network and receives a potential login account number for login. As shown in fig. 14, potential login accounts 5100-a, 5100-b, 5100-c, 5100-d, and the like are displayed on the screen of the mobile phone 5000. The potential login accounts 5100-a, 5100-b, 5100-c, 5100-d are accounts for which historical login behavior has occurred in the new network environment in which the handset 5000 is currently located. The potential login account is an account that is not recorded in the handset 5000. In other words, the cell phone has not logged in using the potential login accounts 5100-a, 5100-b, 5100-c, 5100-d.

For example, the user selects the potential login account 5100-a. The handset 5000 automatically logs in an interaction-free manner. As shown in fig. 15, the account 5200-a that has been logged in is displayed in the upper part of the screen, and the video 5300 enjoyed by the account 5200-a is played in the middle part of the screen. In addition, other service content 5400 enjoyed by the account 5200-a may also be displayed.

Fig. 16 shows a block diagram of the mobile device 5000 implementing the above-described scheme. As shown in fig. 16, the mobile device 5000 includes a receiving component 5001 and a processing component 5004. The receiving component 5001 is configured to receive information of potential login accounts that have experienced login behavior in a first network environment in which the mobile device is currently located. The processing component 5004 is for logging into the potential login account on the mobile device.

The processing component 5004 may log into the potential login account directly on the mobile device 5000 without requiring interaction by the user. In this case, the user may not feel the processing of the login operation.

Alternatively, the login may also be based on a user selection of an account listed on the screen. The mobile device 5000 can also include a display component 5002 and an input component 5003, for example. A display component 5002 is used to display the potential login account. The input component 5003 is used to input a selection of the displayed potential login account. The processing component 5004 is configured to log in the potential login account on the mobile device based on the selection without requiring user interaction to enter a password. In this case, the cumbersome operation of the user to input the user name and password can be omitted.

As previously described, the potential login accounts are determined based on liveness information of at least one logged-in account associated with the first network environment.

Here, in order to secure the account application, the processing component 5004 is further configured to determine whether the first network environment is a secure network environment, and if the first network environment is a secure network environment, perform the operation of logging in the potential login account on the mobile device. For example, the secure network environment is a home network environment.

For example, the potential login account is an account that is not recorded in the mobile device.

The receiving component 5001, the displaying component 5002, the inputting component 5003 and the processing component 5004 may be implemented by software, hardware, or a combination of software and hardware. For example, the mobile device 5000 can include a memory and a processor that store instructions that, when executed by the processor, cause the processor to perform the functions of the receiving component 5001, the displaying component 5002, the inputting component 5003, and the processing component 5004 described above.

Fig. 17 shows a schematic block diagram of an intelligent hardware device according to the invention. The intelligent hardware device 6000 may be, for example, a television set as shown in fig. 8 to 10, or may also be various television boxes such as an Android TV box or Apple TV, or may also be a projector.

As shown in fig. 17, intelligent hardware device 6000 includes a receiving component 6001 and a processing component 6004. The receiving component 6001 is configured to receive information of a potential login account, where the potential login account is an account in which a historical login behavior occurs in a first network environment in which the smart hardware device 6000 is currently located. The processing component 6004 is configured to log in the potential login account on the smart hardware device 6000.

The processing component 6004 may log into the potential login account directly on the smart hardware device 6000 without requiring interaction by the user. In this case, the user may not feel the processing of the login operation.

Alternatively, the login may also be based on a user selection of an account listed on the screen of the smart hardware device 6000. For example, the intelligent hardware device 6000 may also include a display component 6002 and an input component 6003. A display component 6002 is configured to display the potential login account number. An input component 6003 is used to enter a selection of a displayed potential login account. The input component 6003 comprises, for example, a remote control. The processing component 6004 is configured to log in the potential login account on the smart hardware device 6000 based on the selection without requiring a user to input a password for interaction. In this case, the cumbersome operation of the user to input the user name and password can be omitted.

As previously described, the potential login accounts are determined based on liveness information of at least one logged-in account associated with the first network environment.

Here, in order to ensure the security of the account application, the processing component 6004 is further configured to determine whether the first network environment is a secure network environment, and if the first network environment is a secure network environment, perform the operation of logging in the potential login account on the smart hardware device 6000. For example, the secure network environment is a home network environment.

For example, the potential login account is an account that is not recorded in the smart hardware device.

The receiving component 6001, the displaying component 6002, the inputting component 6003, and the processing component 6004 can be implemented in software, hardware, and a combination of software and hardware. For example, the intelligent hardware device 6000 can include a memory storing instructions that, when executed by the processor, cause the processor to perform the functions of the receiving component 6001, the display component 6002, the input component 6003, and the processing component 6004, described above.

The present invention may be an apparatus, method and/or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therewith for causing a processor to implement various aspects of the present invention.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present invention may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, by software, and by a combination of software and hardware are equivalent.

Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.

24页详细技术资料下载
上一篇:一种医用注射器针头装配设备
下一篇:数据处理方法、装置、设备和系统

网友询问留言

已有0条留言

还没有人留言评论。精彩留言会获得点赞!

精彩留言,会给你点赞!

技术分类