Login authentication system and method and electronic equipment

CN118947157APending Publication Date: 2024-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031649.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-12-30
Filing Date
2023-10-30
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In the existing technology, card-less devices cannot perform login authentication of applications, resulting in insufficient convenience and reliability of login authentication.

Method used

By realizing association with other devices in cardless devices, the SIM card information in the associated device is obtained, and the information is used for login authentication of the application, including far-field and near-field network connections to obtain and use SIM card information.

Benefits of technology

It improves the convenience and reliability of login authentication for cardless devices, ensures that application login authentication can be completed even without a SIM card, and enhances login efficiency and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947157A_ABST
    Figure CN118947157A_ABST
Patent Text Reader

Abstract

The invention provides a login authentication system and method and electronic equipment, and relates to the technical field of terminals.The system comprises a first server and first equipment, the first server is used for sending equipment information of a first equipment set to the first equipment, and the first equipment set comprises at least one piece of equipment; each device in the first device set is associated with the first device, the first device set comprises a second device, a first subscriber identity module (SIM) card is configured in the second device, and the first device is used for performing login authentication of an application program based on card information of the first SIM card. According to the technical scheme provided by the invention, the login authentication of the application program in the card-free equipment can be realized, and the convenience and reliability of the login authentication are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Login authentication system, method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 30, 2022, with application number 202211734548.X, and priority to the Chinese patent application entitled “System, method and electronic device for login authentication”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a login authentication system, method and electronic device. Background Art

[0003] With the continuous development of terminal technology, various applications can be installed in electronic devices, such as social applications, multimedia applications, shopping applications, etc. When these applications are started, the electronic device can perform login authentication for the application based on the card information of the subscriber identity module (SIM) card to ensure that the current logged-in user identity is safe and reliable.

[0004] In the prior art, electronic devices are equipped with SIM cards. The electronic device can obtain the card information of the SIM card from the electronic device itself and perform login authentication based on the card information, thereby achieving one-click login with the local phone number. However, if the electronic device is not equipped with a SIM card, that is, the electronic device is a card-free device, the application will be unable to log in.

[0005] Summary of the Invention

[0006] In view of this, the present application provides a system, method and electronic device for login authentication, which can realize login authentication of applications in cardless devices and improve the convenience and reliability of login authentication.

[0007] In order to achieve the above-mentioned objectives, in a first aspect, an embodiment of the present application provides a login authentication system, the system comprising a first server and a first device;

[0008] The first server is configured to send device information of a first device set to the first device, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where the second device is configured with a first subscriber identity module (SIM) card;

[0009] The first device is used to perform login authentication of an application based on the card information of the first SIM card.

[0010] In an embodiment of the present application, a first device can obtain device information of a first device set from a first server. Based on the device information of the first device set, the first device can determine at least one device associated with the first device, including the second device. The first device can then perform application login authentication based on the card information of the first SIM card configured in the second device, thereby improving the convenience and reliability of login authentication.

[0011] The more devices that establish associations with the first device and the more SIM cards configured in the devices associated with the first device, the more SIM card information the first device can obtain, and the better the convenience and reliability of login authentication.

[0012] In some embodiments, the association relationship between the first device and the second device may include the first device and the second device logging into the same account, such as the first account. Since the first device and the second device are associated through the same account, the type of the association relationship may be same-account association.

[0013] In some embodiments, the association relationship between the first device and the second device may include that the account logged into the first device is different from the account logged into the second device, but the account logged into the first device is associated with the account logged into the second device, that is, the second device is associated with the account logged into the first device. In some embodiments, the first device is logged into the first account, the second device is logged into the second account, and the first account is associated with the second account. In some embodiments, the association between the first account and the second account may include the first account being directly associated with the second account. In some embodiments, the association between the first account and the second account may include the first account being indirectly associated with the second account through at least one other account. For example, if the first account is associated with a third account, and the second account is also associated with the third account, then the first account is also associated with the second account. Since the first device and the second device are associated through multiple accounts, the type of the association relationship can be a multi-account association.

[0014] In some embodiments, the device information of the first device set includes identity information of each device in the first device set, thereby indicating to the first device the identity of each device associated with the first device.

[0015] In some embodiments, the device information of the first device set may include card information of SIM cards configured in at least some of the devices in the first device set, thereby directly indicating the card information of at least one SIM card to the first device. In some embodiments, the device information of the first device set may include card information of the first SIM card.

[0016] It is understandable that the device information of the first device set may further include more or less information related to at least one device in the first device set.

[0017] In some embodiments, the first device is further configured to send a first acquisition request to the first server;

[0018] The first server is further configured to send the device information of the first device set to the first device in response to the first acquisition request.

[0019] In some implementations, the first acquisition request may carry at least one of the identity information of the first device 410 and the first account logged in by the first device 410 .

[0020] In some embodiments, the first retrieval request may include at least one filtering parameter, thereby requesting device information for devices associated with the first device and matching the filtering parameter. In some embodiments, the first retrieval request may include an association type. In some embodiments, the association type includes at least one of a same-account association and a multiple-account association. In some embodiments, the first retrieval request may include a network operator.

[0021] In some implementations, the device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

[0022] Among them, the device information of the first device set includes the configuration information of each device in the first device set, that is, the first server can indicate to the first device whether each device associated with the first device is configured with a SIM card, so that the first device can select the second device among the devices configured with a SIM card more quickly and accurately, further improving the efficiency of login authentication.

[0023] In some embodiments, each device in the first set of devices is configured with a SIM card.

[0024] In some embodiments, the first server can, based on the configuration information of multiple other devices associated with the first device, retrieve devices configured with SIM cards from the multiple other devices as the first device set. That is, the first server can accurately indicate to the first device the devices associated with the first device and configured with SIM cards, further facilitating the first device's determination of the second device among the devices associated with the first device and configured with SIM cards, thereby further improving login authentication efficiency.

[0025] In some embodiments, the first device set includes at least one of a second device set and a third device set;

[0026] The second device set includes at least one device, and each device in the second device set is logged in to the same account as the first device;

[0027] The third device set includes at least one device, and each device in the third device set is associated with an account logged in by the first device.

[0028] In some embodiments, the system further includes the second device and a second server, and a far-field network connection exists between the first device and the second device;

[0029] The first device is further configured to send a first authentication request to the second device through the far-field network connection, where the first authentication request is generated by the first device based on the card information of the first SIM card, and the first authentication request is used to perform login authentication of the application;

[0030] The second device is configured to connect to a cellular mobile network through the first SIM card, and send the first authentication request to the second server through the cellular mobile network;

[0031] The second server is configured to send a first authentication result to the second device via the cellular mobile network in response to the first authentication request;

[0032] The second device is further configured to send the first authentication result to the first device through the far-field network connection.

[0033] In some implementations, it is further configured to create the far-field network connection with the second device when performing login authentication of the application; and disconnect the far-field network connection when the login authentication is completed.

[0034] When the first device uses the far-field network connection, the first device creates the far-field network connection and closes the far-field network connection when the use is finished, thereby saving power consumption of the first device and the second device.

[0035] In some embodiments, it is also used to create the far-field network connection with the second device if no near-field network connection exists between the first device and other devices when performing login authentication of the application.

[0036] When the first device performs login authentication for an application, it can determine whether there is a near-field network connection between the first device and the other device. If the near-field network connection does not exist, the first device can then establish a far-field network connection between the first device and the second device, and then access the cellular mobile network through the first SIM card of the second device, and communicate with the second server through the cellular mobile network to complete the login authentication. If the near-field network connection exists, the second SIM card of the third device can be used to access the cellular mobile network, and communicate with the second server through the cellular mobile network to complete the login authentication, without having to establish a far-field network connection, thereby improving the efficiency of login authentication.

[0037] In some embodiments, the first device is further used to, when performing login authentication of the application, create the near-field network connection with a third device if no near-field network connection exists between the first device and other devices, and create the far-field network connection between the first device and the second device, and send the first authentication request to the second device through the far-field network connection when the moment of successful creation of the far-field network connection is earlier than the moment of successful creation of the near-field network connection.

[0038] When the first device performs login authentication for an application, it may also simultaneously establish a near-field network connection between the first device and the third device 450, and a far-field network connection between the first device and the second device. When the moment when the far-field network connection is successfully established is earlier than the moment when the near-field network connection is successfully established, the first device accesses the cellular mobile network through the first SIM card of the second device, and sends a first authentication request to the second server through the cellular mobile network, thereby performing login authentication for the application based on the card information of the first SIM card; when the moment when the near-field network connection is successfully established is earlier than the moment when the far-field network connection is successfully established, the first device accesses the cellular mobile network through the second SIM card of the third device, and sends a second authentication request to the second server through the cellular mobile network, thereby performing login authentication for the application based on the card information of the second SIM card, thereby further improving the efficiency of login authentication.

[0039] In some embodiments, the first device is further configured to notify the second device to turn on the cellular mobile network through the far-field network connection, and to notify the second device to turn off the cellular mobile network through the far-field network connection.

[0040] When the first device uses the cellular mobile network of the second device, it notifies the second device to turn on the cellular mobile network, and when it is turned off, it notifies the second device to turn off the cellular mobile network. This can ensure the reliability of login authentication and save power consumption of the second device.

[0041] In some implementations, the first server is further configured to obtain device information of the second device from the second device.

[0042] In some implementations, the card information of the first SIM card in the first device comes from the second device or the first server.

[0043] In some embodiments, the device information of the first device set obtained by the first device from the first server includes the card information of the first SIM card. In some embodiments, the first device can obtain the card information of the first SIM card from the first server through other means. In some embodiments, the first device can obtain the card information of the first SIM card from the second device.

[0044] In a second aspect, an embodiment of the present application provides a login authentication method, the method comprising:

[0045] A first device obtains device information of a first device set from a first server, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where the second device is configured with a first subscriber identity module (SIM) card;

[0046] The first device performs login authentication of the application based on the card information of the first SIM card.

[0047] In some implementations, the first device obtaining device information of the first device set from the first server includes:

[0048] The first device sends a first acquisition request to the first server;

[0049] The first device receives the first device set returned by the first server in response to the first acquisition request.

[0050] In some implementations, the device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

[0051] In some embodiments, each device in the first set of devices is configured with a SIM card.

[0052] In some embodiments, the method further comprises:

[0053] The first device displays a first card set, the first card set includes at least one SIM card, and any SIM card in the first card set is configured on any device in the first device set;

[0054] The first device determines the first SIM card in the first card set.

[0055] In some embodiments, the first device set includes at least one of a second device set and a third device set;

[0056] The second device set includes at least one device, and each device in the second device set is logged in to the same account as the first device;

[0057] The third device set includes at least one device, and each device in the third device set is associated with an account logged in by the first device.

[0058] In some embodiments, the first device set includes a second device set and a third device set, and the method further includes:

[0059] The first device displays a second card set, the second card set includes at least one SIM card, and each SIM card in the second card set is configured on any device in the second device set;

[0060] If the first device determines that the second card set does not include the first SIM card, the first device displays a third card set, where the third card set includes at least one SIM card, and any SIM card in the third card set is configured on any device in the third device set;

[0061] The first device determines the first SIM card in the third card set.

[0062] In some embodiments, a far-field network connection is present between the first device and the second device, and the first device performs login authentication of the application based on the card information of the first SIM card, including:

[0063] The first device sends a first authentication request to the second device through the far-field network connection, where the first authentication request is generated by the first device based on the card information of the first SIM card, and the first authentication request is used to perform login authentication of the application;

[0064] The first device receives a first authentication result returned by the second device through the far-field network connection.

[0065] In some embodiments, the method further comprises:

[0066] When the first device performs login authentication of the application, the first device establishes a far-field network connection with the second device;

[0067] When the login authentication is completed, the first device disconnects the far-field network connection.

[0068] In some embodiments, the method further comprises:

[0069] When the first device performs login authentication for the application, if there is no near-field network connection between the first device and other devices, the first device and the second device establish the far-field network connection.

[0070] In some embodiments, the method further comprises:

[0071] When the first device performs login authentication for the application, if no near-field network connection exists between the first device and other devices, establishing the near-field network connection with a third device, and establishing the far-field network connection between the first device and the second device;

[0072] The first device sending a first authentication request to the second device through the far-field network connection includes:

[0073] When the far-field network connection is successfully established earlier than the near-field network connection, the first device sends the first authentication request to the second device through the far-field network connection.

[0074] In some embodiments, the method further comprises:

[0075] The first device notifies the second device to turn on the cellular mobile network through the far-field network connection;

[0076] The first device notifies the second device to turn off the cellular mobile network through the far-field network connection.

[0077] In some implementations, the card information of the first SIM card in the first device comes from the second device or the first server.

[0078] In a third aspect, an embodiment of the present application provides a login authentication method, the method comprising:

[0079] A first server sends device information of a first device set to a first device, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where a first user identity module SIM card is configured in the second device, and the first SIM card is used for login authentication of an application on the first device.

[0080] In some implementations, the first server sending the device information of the first device set to the first device includes:

[0081] The first server sends the device information of the first device set to the first device in response to the first acquisition request of the first device.

[0082] In some implementations, the device information of the first device set includes card information of the first SIM card.

[0083] In some embodiments, the method further comprises:

[0084] The first server obtains device information of the second device from the second device.

[0085] In some implementations, the device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

[0086] Fourthly, an embodiment of the present application provides a device for login authentication, which has the function of implementing the electronic device behavior in the above aspects and possible implementation methods of the above aspects. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a transceiver module or unit, a processing module or unit, an acquisition module or unit, etc.

[0087] In a fifth aspect, an embodiment of the present application provides an electronic device comprising: a memory and a processor, the memory being used to store a computer program; the processor being used to execute any of the methods described in the second aspect above when calling the computer program, or to execute any of the methods described in the third aspect above.

[0088] In the sixth aspect, an embodiment of the present application provides a chip system, which includes a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement any method described in the second aspect above, or executes any method described in the third aspect above.

[0089] The chip system may be a single chip or a chip module composed of multiple chips.

[0090] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, it implements the method described in any one of the second aspects above, or executes the method described in any one of the third aspects above.

[0091] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes any one of the methods described in the second aspect above, or executes any one of the methods described in the third aspect above.

[0092] It can be understood that the beneficial effects of the second to eighth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] FIG1 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0094] FIG2 is a software structure block diagram of an electronic device provided in an embodiment of the present application;

[0095] FIG3 is a flow chart of a login authentication method provided in an embodiment of the present application;

[0096] FIG4 is a schematic diagram of a login authentication scenario provided in an embodiment of the present application;

[0097] FIG5 is a schematic diagram of a communication method provided in an embodiment of the present application;

[0098] FIG6 is a flowchart of another login authentication method provided in an embodiment of the present application;

[0099] FIG7 is a flowchart of another login authentication method provided in an embodiment of the present application;

[0100] FIG8 is a flowchart of another login authentication method provided in an embodiment of the present application;

[0101] FIG9 is a schematic diagram of a display interface provided in an embodiment of the present application;

[0102] FIG10 is a schematic diagram of another display interface provided in an embodiment of the present application;

[0103] FIG11 is a schematic diagram of another display interface provided in an embodiment of the present application;

[0104] FIG12 is a schematic diagram of another display interface provided in an embodiment of the present application;

[0105] FIG13 is a flowchart of another login authentication method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0106] The login authentication method provided in the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), servers, etc. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

[0107] 1 is a schematic diagram of the structure of an electronic device 100 according to an embodiment of the present application. The electronic device 100 may include a processor 110, a memory 120, a communication module 130, and the like.

[0108] The processor 110 may include one or more processing units, and the memory 120 is used to store program codes and data. In the embodiment of the present application, the processor 110 may execute computer-executable instructions stored in the memory 120 to control and manage the actions of the electronic device 100.

[0109] The communication module 130 can be used for communication between various internal modules of the electronic device 100, or communication between the electronic device 100 and other external electronic devices. For example, if the electronic device 100 communicates with other electronic devices through a wired connection, the communication module 130 may include an interface, such as a USB interface. The USB interface may be an interface that complies with USB standard specifications, specifically a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc. For example, the communication module 130 can provide solutions for wireless communications including 2G / 3G / 4G / 5G. Exemplarily, the communication module 130 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), Ethernet, etc.

[0110] Optionally, the electronic device 100 may further include a display screen 140. The display screen 140 is used to display images, videos, etc. The display screen 140 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 140, where N is a positive integer greater than one.

[0111] Optionally, the electronic device 100 may further include a peripheral device 150 , such as a mouse, a keyboard, a speaker, a microphone, and the like.

[0112] Optionally, the electronic device 100 may further include a SIM card interface 160. The SIM card interface 160 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into or removing it from the SIM card interface 160. The electronic device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 160 may support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards may be inserted into the same SIM card interface 160 at the same time. The types of the multiple cards may be the same or different. The SIM card interface 160 may also be compatible with different types of SIM cards. The SIM card interface 160 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card may be embedded in the electronic device 100 and cannot be separated from the electronic device 100. In some embodiments, if the electronic device 100 does not include a SIM card, the electronic device 100 may be referred to as a card-less device. Correspondingly, if the electronic device includes a SIM card, the electronic device 100 may be referred to as a card-equipped device.

[0113] It should be understood that, other than the various components or modules listed in FIG1 , the embodiments of the present application do not specifically limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or combine or separate certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0114] FIG2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0115] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0116] The application layer can include a series of application packages.

[0117] As shown in FIG2 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

[0118] It should be noted that the application layer may include both system applications from electronic device manufacturers and third-party applications from software manufacturers other than electronic device manufacturers.

[0119] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0120] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0121] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0122] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0123] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0124] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0125] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0126] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0127] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for scheduling and management of the Android system.

[0128] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0129] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0130] The system library can include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0131] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0132] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0133] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0134] A 2D graphics engine is a drawing engine for 2D drawings.

[0135] In some embodiments, the system library may further include a device authentication (HI chain) module, which can ensure the secure transmission of user personal data between multiple devices and the ability to establish secure connections between devices.

[0136] In some embodiments, the system library may also include a telephony service. The telephony service provides a series of APIs for obtaining information related to cellular networks and SIM cards. Applications can call the APIs to obtain the currently registered network name, network service status, signal strength, and SIM card information. In some embodiments, applications can use the network operator's software development kit (SDK) to query the telephony service for SIM card information, request to enable or disable the cellular network, and so on.

[0137] In some embodiments, the system library may further include an account management service that can be used to manage an account logged into the operating system of the electronic device, other accounts associated with the account, and other electronic devices.

[0138] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0139] In some embodiments, the kernel layer may further include a radio interface layer (RIL), which may be used to access the wireless modem processor to obtain relevant information about the SIM card and use functions of the SIM card.

[0140] The following is an example of the workflow of the software and hardware of the electronic device 100, with reference to the application login scenario.

[0141] When an application on electronic device 100 is launched, it obtains the SIM card information from the phone service through the network operator's SDK. The SIM card can be connected to electronic device 100 via SIM card interface 160. Electronic device 100 displays this card information on display 140 for user confirmation or authorization. When electronic device 100 receives the user's confirmation or authorization, the application accesses the cellular network from the phone service through the network operator's SDK. The phone service communicates with the operator's server over this cellular network, including performing login authentication for the application based on the card information.

[0142] In order to facilitate understanding of the technical solutions in the embodiments of the present application, the application scenarios of the embodiments of the present application are first introduced below.

[0143] Currently, the variety and number of applications that can be installed on electronic devices are increasing. These applications can provide users with a variety of functions, such as entertainment, audio-visual enjoyment, social communication, financial management, and so on. To ensure the security of user data and provide users with more personalized services, more and more applications (especially third-party applications) require user identity authentication.

[0144] In some embodiments, when an application is launched on an electronic device, the application can obtain and display the card information of the SIM card in the electronic device. The user can click on the card information of the SIM card to authorize login authentication using the card information. The electronic device obtains the corresponding authentication result from the operator server based on the card information. The authentication result can be used to indicate whether the authentication is successful or failed.

[0145] Please refer to Figure 3, which shows a login authentication method provided in an embodiment of the present application.

[0146] S301: The user requests to log in to the application.

[0147] S302: The application requests the network operator's SDK to obtain the mobile phone number in the SIM card.

[0148] S303: The operator SDK returns the mobile phone number to the application.

[0149] In some implementations, the operator SDK may obtain the mobile phone number from the operator server.

[0150] S304, the application displays an authorization interface to the user.

[0151] The authorization interface may include a mobile phone number and authorization options, thereby prompting the user to authorize one-click login through the mobile phone number.

[0152] S305, user authorization.

[0153] Users can authorize by clicking on the Authorize option.

[0154] S306: The application creates an authentication request.

[0155] The application can create an authentication request using a mobile phone number.

[0156] S307: The application sends an authentication request to the operator server.

[0157] S308: The operator server performs authentication.

[0158] S309: The operator server returns the authentication result to the application.

[0159] The authentication result may include authentication success or authentication failure.

[0160] S310, the application program prompts the user that the login is successful.

[0161] The application can display the authentication result to the user. In particular, the application can prompt the user that the login is successful when the authentication is successful.

[0162] This authentication method can improve the convenience of authentication to a certain extent. However, if the electronic device does not have a SIM card, or if the SIM card information cannot be obtained due to other reasons, the login authentication of the application cannot be completed. Therefore, in order to further improve the convenience and reliability of login authentication, the embodiments of the present application provide another login authentication method and system.

[0163] Please refer to Figure 4, which is a schematic diagram of an application scenario provided by an embodiment of the present application. The scenario includes a first device 410, a first server 420, a second device 430, and a second server 440. Among them, the first device 410, the first server 420, the second device 430, and the second server 440 can be implemented by the aforementioned electronic device 100. Exemplarily, the first device 410 and the second device 430 can be mobile phones, smart watches, tablet computers, smart wearable devices, smart home devices, Internet of Things devices, etc. Exemplarily, the first server 420 can be a server of the manufacturer of the first device 410 and the second device 430.

[0164] The first device 410 may include an operating system and at least one application. In some embodiments, the at least one application includes a third-party application. In some embodiments, a user can register in the operating system to obtain an account of the user. In some embodiments, the user can log in to other devices of the same manufacturer as the first device 410 through the account, that is, multiple devices can log in to the same account, and the multiple devices are associated through the account. In some embodiments, the user can associate the account with another account logged in by other users on other devices, that is, multiple devices logged in to different accounts can be associated through the association relationship between the multiple accounts. For example, the same family includes multiple family members, each family member has a device, and has logged in an account (i.e., a member account) in the device, and the member accounts of multiple family members can be associated with the same family account. The multiple member accounts are associated through the same family account, and the devices logged in to each member account are also associated.

[0165] In some embodiments, the first device 410 is not configured with any SIM card, so the first device 410 can also be called a cardless device. In some embodiments, the first device 410 can be configured with a SIM card, but the SIM card cannot be used for login authentication of an application in the first device 410.

[0166] The second device 430 may be configured with at least one SIM card. In some embodiments, the second device 430 and the first device 410 are logged into the same account, such as the first account. In some embodiments, the account logged into the second device 430 (such as the second account) is associated with the account logged into the first device (such as the first account). In some embodiments, the account logged into the second device 430 and the account logged into the first device are associated with another account (such as a third account).

[0167] In some embodiments, multiple associated devices can trust each other. In some embodiments, a device can exchange one or more data with another associated device, such as SIM card information. In some embodiments, a device can use one or more services and functions of another associated device, such as using the cellular mobile network of the other device.

[0168] In some embodiments, a far-field network connection can be established between the first device 410 and the second device 430, so as to perform far-field communication through the far-field network connection. In some embodiments, the first device 410 and the second device 430 can establish the far-field network connection through a peer-to-peer (P2P) crossing method or a relay method. Taking the establishment of a far-field network connection in a P2P crossing method as an example, the first device 410 and the second device 430 can establish relevant entries on their respective gateways through an intermediate device, so that the data sent by the first device 410 and the second device 430 can directly penetrate the gateway of the other party and reach the other party. It is understandable that in actual applications, the first device 410 and the second device 430 can also establish the far-field network connection in other ways, and the embodiments of the present application do not limit the method for establishing the far-field network connection and the type of the far-field network connection.

[0169] The first server 420 can be used to obtain device information of any device (such as the first device 410 or the second device 430) and provide the device information of the device to other devices. The device information may include the device's identity information, configuration information, card information of the configured SIM card, logged-in account number, etc. The configuration information may be used to indicate whether the device has a SIM card. It should be noted that in actual applications, the device information may also include more or less device-related information. In some embodiments, the first server 420 can be used to manage the accounts logged in on the devices, the associations between devices, and the associations between accounts. The first server 420 can determine whether two devices are associated based on the accounts logged in on the devices, the associations between devices, and the associations between accounts. In some embodiments, the first server 420 can provide any device with device information of other devices associated with the device. In some embodiments, the first server 420 can receive the accounts logged in on the devices, the associations between devices, and the associations between accounts submitted by any device. In some implementations, the first server 420 may provide any device with other devices associated with the device and other accounts associated with the account logged in by the device.

[0170] For example, user 1 logs in to the first account on the first device 410 and logs in to the first account on the second device 430. Then the first server 420 can determine that both the first device 410 and the second device 430 are logged in to the first account.

[0171] For another example, user 1 logs in to a first account on first device 410, and user 2 logs in to a second account on second device 430. User 1 sends association request 1 to second device 430 via first device 410, requesting the establishment of an association relationship between the first account and the second account. Second device 430 receives association request 1 and displays it to user 2. When second device 430 receives user 2's authorization of association request 1, it sends the association relationship between the first account and the second account to first server 420.

[0172] For another example, user 1 logs into a first account on first device 410, and user 2 logs into a second account on second device 430. User 1 sends association request 2 to first server 420 via first device 410, requesting the establishment of an association between the first account and a third account. User 2 sends association request 3 to first server 420 via second device 430, requesting the establishment of an association between the second account and the third account. When first server 420 receives association request 2 and association request 3, it may store the association between the first account and the third account, as well as the association between the second account and the third account. Based on the third account, first server 420 may determine that the first account and the second account are also associated with each other, or first server 420 may directly store the association between the first account and the second account.

[0173] Specifically, user 1 and user 2 are family members of the same family 1. User 2 logs in to the second account and the third account on the second device 430, and sets the second account as a personal account and the third account as a family account. The first server 420 can establish an association relationship between the second account and the third account. User 1 logs in to the first account on the first device 410 and sets the first account as a personal account. User 1 requests the first server 420 to associate the first account with the third account through the first device 410. The first server 420 establishes a relationship between the first account and the third account, and can also determine that the first account and the second account are associated through the third account, that is, the personal account of user 1 and the personal account of user 2 are both logged in to the same family account, and the personal account of user 1 and the personal account of user 2 are associated through the family account.

[0174] In some embodiments, the card information of the SIM card may include at least one of a mobile subscriber number (mobile subscriber international ISDN / PSTN number) MSISDN, an international mobile subscriber identity (IMSI), and a network operator. It is understood that in actual applications, the card information may also include more or less information related to the SIM card.

[0175] The second server 440 can provide login authentication services to any device (e.g., the first device 410 or the second device 430). In some embodiments, the second server 440 can obtain an authentication request from the device and return an authentication result to the device. In some embodiments, the second server 440 can be a server of a network operator.

[0176] In some embodiments, the scenario may further include a third device 450, which may be a device located near the first device 410 and equipped with at least one SIM card. The third device 450 may be implemented by the aforementioned electronic device 100. For example, the third device 450 may be a mobile phone, a smartwatch, a tablet computer, a smart wearable device, a smart home device, an Internet of Things device, and the like.

[0177] In some embodiments, a near-field network connection can be established between the first device 410 and the third device 450 to achieve near-field communication. Exemplarily, the near-field network connection can achieve near-field communication in the form of WLAN, BT, or WiFi. It is understandable that in actual applications, the near-field network connection can also achieve near-field communication in other ways. The embodiments of the present application do not limit the method for establishing the near-field network connection, the type of the near-field network connection, and the method for near-field communication.

[0178] From the above, it can be seen that the first device 410 can be a cardless device, or it does not include a SIM card required for login authentication of a certain application. The second device 430 and the third device 450 are each configured with at least one SIM card. Therefore, the first device can obtain the card information of the SIM card in the second device 430 or the third device 450, and use the card information for login authentication of the application, thereby improving the convenience and reliability of login authentication.

[0179] In some embodiments, the first device 410 can select one of multiple other devices (such as the second device 430 and the third device 450) as the source of SIM card information. In some embodiments, since the first device 410 and the second device 430 are interrelated devices, the second device 430 has higher security and reliability than the first device 410. Therefore, the first device 410 can preferentially obtain the SIM card information from the second device 430. In some embodiments, since the first device 410 and the second device 430 can perform far-field communication, and the first device 410 and the third device 450 can perform near-field communication, that is, the first device 410 can more easily establish a connection and communicate with the third device 450, the first device 410 can preferentially obtain the SIM card information from the third device 450, thereby further improving the convenience and efficiency of login authentication.

[0180] In some embodiments, the first device 410 may select card information of one SIM card from the card information of multiple SIM cards and use the card information of the selected SIM card for login authentication of a certain application. The multiple SIM cards may be SIM cards configured in the same device or in different devices.

[0181] Please refer to FIG. 5 , which is a schematic diagram of a communication method between a first device 410 and a second device 430 provided in an embodiment of the present application.

[0182] First device 410 and second device 430 establish an association relationship through the account management service, including authentication as devices with the same account or a family account. After establishing the association relationship, first device 410 and second device 430 can establish a far-field network connection with the second device 430, and the first device 410 and second device 430 can communicate through the far-field network connection.

[0183] For example, a first device 410 uses the cellular mobile network of a second device 430 to send data. When an application on the first device 410 needs to send data, the first device 410 can send the data to the kernel layer through a network proxy, which then sends the data to the second device 430 via a far-field network connection. The second device 430 forwards the data to the kernel layer, which then controls the modem processor of the second device 430 through the RIL, connects the second device 430 to the cellular mobile network, and sends the data to a base station via the cellular mobile network. The data is then sent to other devices such as the second server 440.

[0184] The following specific embodiments are used to describe the technical solution of the present application in detail. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0185] Please refer to Figure 6, which is a flowchart of a login authentication method provided in an embodiment of the present application. It should be noted that the method is not limited to the specific sequence shown in Figure 6 and below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0186] S601: The first device 410 establishes an association relationship with the second device 430.

[0187] The first device 410 establishes an association relationship with the second device 430 , so that the first device 410 and the second device 430 are associated with each other.

[0188] In some embodiments, when the first device 410 and the second device 430 establish an association, the first device 410 and the second device 430 may trust each other. In some embodiments, when the first device 410 and the second device 430 establish an association, the first device 410 may exchange data with the second device 430. In some embodiments, when the first device 410 and the second device 430 establish an association, the first device 410 and the second device 430 may use each other's services and functions.

[0189] In some embodiments, the association relationship between the first device 410 and the second device 430 may include the first device 410 and the second device 430 logging into the same account, such as the first account. Since the first device 410 and the second device 430 are associated through the same account, the type of the association relationship may be same-account association.

[0190] For example, a user can log in to a first account on a first device 410, and the first device 410 sends the first account and the identity information of the first device 410 to the first server 420. The user can also log in to the first account on a second device 430, and the second device 430 sends the first account and the identity information of the second device 430 to the first server 420. The first server 420 receives the first account, the identity information of the first device 410, and the identity information of the second device 430, and then determines that the first device 410 and the second device 430 are both logged in to the first account, that is, the first device 410 and the second device 430 have passed the same account authentication. It is understandable that in actual applications, the first device 410 and the second device 430 can also perform the same account authentication through other methods.

[0191] In some embodiments, the association relationship between the first device 410 and the second device 430 may include the case where the account logged into the first device 410 and the account logged into the second device 430 are different, but the account logged into the first device 410 is associated with the account logged into the second device 430. In other words, the second device 430 is associated with the account logged into the first device 410. In some embodiments, the first device 410 is logged into a first account, the second device 430 is logged into a second account, and the first account is associated with the second account. In some embodiments, the association between the first account and the second account may include a direct association between the first account and the second account. In some embodiments, the association between the first account and the second account may include an indirect association between the first account and the second account through at least one other account. For example, if the first account is associated with a third account, and the second account is also associated with the third account, then the first account is also associated with the second account. Since the first device 410 and the second device 430 are associated through multiple accounts, the type of association relationship may be a multi-account association.

[0192] For example, a user can log in to a first account on a first device 410, and another user can log in to a second account on a second device 430. The first server 420 stores the identity information of the first device 410 logged in to the first account, and the identity information of the second device 430 logged in to the second account. The first device 410 sends an association request to the second device 430 via the first server 420. The association request is used to request that the first account be associated with the second account. When the second device 430 receives a confirmation operation based on the association request, it sends a successful association feedback to the first device 410. The first server 420 stores the association relationship between the first account and the second account, thereby establishing the association relationship between the first device 410 and the second device 430.

[0193] In some embodiments, the first device 410 and the second device 430 may include a device authentication module, and the first device 410 and the second device 430 may authenticate each other and establish an association relationship through the device authentication module.

[0194] It is understandable that the first device 410 and the second device 430 may establish the association relationship in advance, or the first device 410 and the second device 430 are often or always associated with each other, so S601 may be omitted.

[0195] S602 , the second device 430 sends device information of the second device 430 to the first server 420 .

[0196] In some embodiments, the device information of the second device 430 may include identity information of the second device 430. In some embodiments, the device information of the second device 430 may include configuration information of the second device 430, which may indicate whether the second device 430 is configured with a SIM card. In some embodiments, the device information of the second device 430 may include card information of the SIM card configured in the second device 430. In some embodiments, the device information of the second device 430 may include the account number logged in by the second device 430. It will be appreciated that in actual applications, the device information of the second device 430 may also include more or less information related to the second device 430.

[0197] It should be noted that the second device 430 may also send the device information of the second device 430 to the second server 440 at any other time, not limited to after the first device 410 and the second device 430 establish an association. In some embodiments, the second device 430 may send the updated device information to the first server 420 upon detecting an update to the device information of the second device 430. In some embodiments, the second device 430 may periodically synchronize information with the first server 420 so that the device information stored on the first server 420 is consistent with the actual device information of the second device 430.

[0198] S603 , the first device 410 obtains device information of the second device 430 from the first server 420 .

[0199] In some embodiments, the device information of the second device 430 obtained by the first device 410 from the first server 420 includes configuration information of the second device 430. Then, when the second device 430 is configured with a SIM card, the first device 410 can obtain the card information of the SIM card configured in the second device 430 from the first server 420 or the second device 430.

[0200] In some implementations, the device information of the second device 430 obtained by the first device 410 from the first server 420 may include card information of a SIM card configured in the second device 430 .

[0201] In some embodiments, the first device 410 may obtain the device information of the second device 430 from the first server 420 upon detecting a specific event. In some embodiments, the specific event may include detecting that an application on the first device 410 calls a cellular network-related interface such as getphoneinfo or getnetworktype, or that the first device 410 is powered on. Of course, in actual applications, the specific event may also include more or fewer events.

[0202] S604 , the first device 410 performs login authentication of the application based on the card information of the first SIM card in the second device 430 .

[0203] When the first device 410 obtains the card information of the first SIM card in the second device 430 , it can communicate with the network operator corresponding to the SIM card (such as the second server) based on the card information, thereby performing login authentication on any application in the first device 410 .

[0204] It should be noted that the embodiments of the present application limit the timing of performing application login authentication. In some embodiments, the timing can be set in advance by the developer of the application. In some embodiments, the first device 410 can perform application login authentication when detecting a specific operation such as application startup, transfer or payment.

[0205] It is also understandable that the card information of the first SIM card obtained by the first device 410 can be used for login authentication of multiple applications, and can also be used for multiple login authentications of one application.

[0206] In an embodiment of the present application, a first device 410 can establish an association with a second device 430 and obtain device information of the second device from a first server 420. Based on this device information, the first device 410 can determine whether the second device 430 is configured with a SIM card or directly determine the card information of the SIM card configured in the second device 430 based on this device information. If the second device 430 is configured with a SIM card, the first device 410 can obtain the card information of the first SIM card in the second device 430 and use this card information for login authentication of an application in the first device 410. This ensures that even if the first device 410 is not configured with a SIM card or the SIM card required for login authentication of an application is not configured, the corresponding card information can be obtained from other devices associated with the first device 410 for login authentication of the application, thereby improving the convenience and reliability of login authentication. The more devices that establish an association with the first device 410 and the more SIM cards configured in the devices associated with the first device 410, the more SIM card information the first device 410 can obtain, thereby improving the convenience and reliability of login authentication.

[0207] For example, Family 1 includes members 1, 2, and 3, each of whom owns an electronic device equipped with two SIM cards. Member 1's electronic device, 2's electronic device, and 3's electronic device can all be linked together. Therefore, each member's electronic device can access the card information of six SIM cards for application login authentication. Even if a member's electronic device becomes a cardless device due to the removal of its SIM card, it can still access the card information of the four SIM cards in the other two electronic devices, meaning that application login authentication can still be performed relatively conveniently and reliably.

[0208] In some embodiments, the first device 410 may also send device information of the first device 410 to the first server 420 , and the second device 430 may also obtain card information of the SIM card of the first device 410 and perform login authentication on the application in the second device 430 based on the card information.

[0209] In some embodiments, the first device 410, the first server 420, and the second device 430 may synchronize information, including synchronization of at least one type of information, such as device information, associations between accounts, and associations between devices. This information synchronization ensures that the information stored on the first server is consistent with the actual device information, associations between accounts, and associations between devices.

[0210] Please refer to Figure 7, which is a flowchart of a login authentication method provided in an embodiment of the present application. It should be noted that the method is not limited to the specific sequence shown in Figure 7 and below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0211] S701: The first device 410 sends a first acquisition request to the first server 420.

[0212] In some embodiments, the first acquisition request may be used to request device information of other devices associated with the first device. In some embodiments, the first acquisition request may carry at least one of the identity information of the first device 410 and the first account logged in by the first device 410.

[0213] In some embodiments, the first retrieval request may include at least one filtering parameter, thereby requesting device information for devices associated with the first device and matching the filtering parameter. In some embodiments, the first retrieval request may include an association type. In some embodiments, the association type includes at least one of a same-account association and a multiple-account association. In some embodiments, the first retrieval request may include a network operator.

[0214] S702 , the first server 420 sends device information of a first device set to the first device 410 in response to the first acquisition request, where each device in the first device set is associated with the first device, the first device set includes a second device, and the second device is configured with a first SIM card.

[0215] In some embodiments, the device information of the first device set includes configuration information of each device in the first device set, and the configuration information of each device is used to indicate whether the device is configured with a SIM card, thereby indicating to the first device which devices are associated with the first device and are configured with a SIM card. The device information of the first device set includes the configuration information of each device in the first device set, i.e., the first server 420 can indicate to the first device 410 whether each device associated with the first device 410 is configured with a SIM card, thereby facilitating the first device 410 to more quickly and accurately select a second device from among devices configured with a SIM card, further improving the efficiency of login authentication.

[0216] In some embodiments, the device information of the first device set includes identity information of each device in the first device set, thereby indicating to the first device the identity of each device associated with the first device.

[0217] In some embodiments, the device information of the first device set may include card information of SIM cards configured in at least some devices in the first device set, thereby directly indicating the card information of at least one SIM card to the first device.

[0218] It is understandable that the device information of the first device set may further include more or less information related to at least one device in the first device set.

[0219] In some embodiments, the first device set may include at least one of a second device set and a third device set. The second device set includes at least one device, and each device in the second device set is logged into the same account as the first device 410. The third device set includes at least one device, and each device in the third device set is associated with the account logged into the first device 410.

[0220] In some embodiments, each device in the first device set is configured with a SIM card. In some embodiments, the first server 420 can, based on the configuration information of multiple other devices associated with the first device 410, retrieve devices configured with SIM cards from the multiple other devices as the first device set. In other words, the first server 420 can accurately indicate to the first device 410 the devices associated with the first device 410 and configured with SIM cards, further facilitating the first device 410 to identify the second device among the devices associated with the first device and configured with SIM cards, further improving the efficiency of login authentication.

[0221] In some implementations, the first device set may include at least some devices that are not configured with a SIM card.

[0222] In some embodiments, if the first acquisition request can carry at least one filtering parameter, the first server 420 can return device information of devices associated with the first device 410 and matching the filtering parameter to the first device 410, thereby improving the accuracy of the queried device information. In some embodiments, if the association type carried in the first acquisition request includes same-account association, the first device set can include a second device set; if the association type carried in the first acquisition request is multi-account association, the first device set can include a third device set. In some embodiments, if the first acquisition request carries a network operator, the first device set can include devices associated with the first device 410 and configured with a SIM card corresponding to the network operator.

[0223] S703: The first device 410 performs login authentication on the application in the first device 410 based on the card information of the first SIM card.

[0224] In some implementations, the second device may be a device specified by a user, or the second device may be a device determined by the first device 410 from the first device set according to a preset selection method.

[0225] It should be noted that the way in which the first device 410 executes S703 may be similar to or the same as the way in which it executes S604.

[0226] In this embodiment of the present application, the first device 410 can obtain device information of the first device set from the first server 420. Based on the device information of the first device set, the first device 410 can determine at least one device associated with the first device, including the second device. The first device 410 can then perform application login authentication based on the card information of the first SIM card configured in the second device, thereby improving the convenience and reliability of login authentication.

[0227] In some implementations, S701 may be omitted, that is, the first server 420 may actively send the device information of the first device set to the first device 410 .

[0228] In some implementations, the first server 420 may send the device information of the first device set to the first device 410 upon detecting that the first device 410 has logged into the first account.

[0229] In some implementations, the first server 420 may send the device information of the first device set to the first device 410 when establishing a network connection with the first device 410 .

[0230] In some embodiments, upon detecting that the device information of the first device set stored on the first server 420 is updated, the first server 420 may send the updated device information of the first device set to the first device 410 .

[0231] Exemplarily, when the first server 420 detects that a new device associated with the first device 410 is added, a device associated with the first device 410 is reduced, or the device information of any device associated with the first device 410 changes, the first server 420 updates the device information stored in the first device set and sends the updated device information of the first device set to the first device 410.

[0232] Of course, in actual applications, the first server 420 may also actively send the device information of the first device set to the first device 410 at other times.

[0233] Please refer to Figure 8, which is a flowchart of a login authentication method provided in an embodiment of the present application. The method can be used as a detailed description of the aforementioned S604 and S703. It should be noted that the method is not limited to the specific order of Figure 8 and the following description. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0234] S801: The first device 410 obtains user authorization for a first SIM card.

[0235] The first device 410 may prompt the user to authorize the application login authentication using the card information of the first SIM card. In some embodiments, the first device 410 may display the card information of the first SIM card. If the user's authorization operation is received based on the card information of the first SIM card, it can be determined that the user's authorization for the first SIM card has been obtained.

[0236] For example, the first device 410 may display the first interface shown in FIG9 , which includes the card information of the first SIM card "+86132****1234" and a "One-click login" option. When the first device 410 receives a user click operation based on the "One-click login" option, the first device 410 obtains the user's authorization for "+86132****1234".

[0237] In some embodiments, the first device 410 may display a first card set and identify a first SIM card in the first card set, where the first card set includes at least one SIM card, and any SIM card in the first card set is configured on any device in the first device set. By displaying the first card set including at least one SIM card, the first device 410 prompts the user of the at least one SIM card that can currently be used for login authentication, facilitating the user's identification and authorization of the first SIM card in the at least one SIM card, thereby improving the reliability of login authentication.

[0238] It should be noted that any two SIM cards in the first card set can be configured on different devices or on the same device. In some embodiments, the first device 410 can obtain card information of SIM cards configured on at least some of the devices in the first device set that are configured with SIM cards, thereby obtaining the first card set.

[0239] For example, the first device 410 may display the second interface shown in FIG10 . The second interface includes card information for three SIM cards, namely, "+86132****1234," "+86132****3456," and "+86132****5678." The second interface also includes a "One-click Login" option. When the first device 410 receives a user click operation based on "+86132****3456," it determines "+86132****3456" as the card information for the first SIM card. When the first device 410 receives a user click operation based on the "One-click Login" option, the first device 410 obtains the user's authorization for "+86132****3456."

[0240] In some embodiments, the first device 410 may further display more information related to the SIM card to facilitate the user to more accurately select the first SIM card. In some embodiments, the first device 410 may further display the type of association between the device where the SIM card is located and the first device 410. In some embodiments, the first device 410 may display one or more types of device information of the device where the SIM card is located, such as identity information, network operator, etc.

[0241] For example, the first device 410 can display the third interface as shown in Figure 11. The third interface includes the card information of three SIM cards, namely "+86132****1234", "+86132****3456" and "+86132****5678". The association relationship between the devices where "+86132****1234" and "+86132****3456" are located and the first device 410 is the same account association, so the third interface also includes a "Same account device login" option. The association relationship between the device where "+86132****5678" is located and the first device 410 is a multi-account association, specifically multiple devices under the same family account, so the third interface also includes a "family account login option".

[0242] In some embodiments, the first device 410 may display a second card set, which includes at least one SIM card, each SIM card in the second card set being configured on any device in the second device set. The first device may determine the first SIM card in the second card set. If the first device 410 determines that the first SIM card is not included in the second card set, the first device 410 may display a third card set, which includes at least one SIM card, each SIM card in the third card set being configured on any device in the third device set. The first device 410 may determine the first SIM card in the third card set. Because the association type between the devices in the second device set and the first device 410 is single-account association, and the association type between the devices in the third device set and the first device 410 is multi-account association, the relationship between the devices in the second device set and the first device 410 is closer, and the level of mutual trust between the devices in the second device set and the first device 410 is higher, the second card set may be displayed first. If the card information of the first SIM card cannot be determined in the second card set, the third card set may be displayed, and the first SIM card may be determined in the third card set. This progressive display method is consistent with user habits and can also reduce the amount of information displayed to the user each time, making it easier for the user to more accurately determine the card information of the first SIM card. Of course, the first device 410 can also first display the third card set and determine the first SIM card in the third card set. If the first device 410 determines that the third card set does not include the first SIM card, the first device 410 can display the second card set and determine the first SIM card in the second card set.

[0243] In some embodiments, the first device 410 may obtain card information of SIM cards configured in at least some of the devices in the second device set that are configured with SIM cards, thereby obtaining a second card set. In some embodiments, the first device 410 may obtain card information of SIM cards configured in at least some of the devices in the third device set that are configured with SIM cards, thereby obtaining a third card set.

[0244] In some embodiments, the first device 410 may display a fourth card set, which includes at least one SIM card, with each SIM card in the fourth card set configured as a near-field device of the first device 410. The fourth card set includes a second SIM card, which is configured on a third device. A near-field device of the first device 410 may refer to a device within a specific range of the first device 410 and capable of establishing a near-field network connection with the first device 410. The first device may perform application login authentication based on the card information of the second SIM card.

[0245] In some embodiments, the first device 410 may display a fifth card set, which includes at least one SIM card, each of which is configured on the first device 410. The fifth card set includes a third SIM card. The first device 410 may perform application login authentication based on the card information of the third SIM card.

[0246] For example, the first device 410 may display the fourth interface shown in FIG12 . The fourth interface includes card information for five SIM cards: "+86132****1111," "+86132****1234," "+86132****3456," "+86132****5678," and "+86132****2222." "+86132****1111" is a SIM card in the fifth card set and is locally configured on the first device 410. Therefore, the fourth interface also includes a "Local Number Login" option. "+86132****1234" and "+86132****3456" are SIM cards in the second card set and are configured on other devices with the same account as the first device 410. Therefore, the fourth interface also includes a "Same Account Device Login" option. "+86132****5678" is a SIM card in the third card set and is configured on other devices with the same family account as the first device 410. Therefore, the fourth interface also includes a "Family Account Device Login" option. "+86132****2222" is a card in the third card set and is configured on other devices near the first device 410. Therefore, the fourth interface also includes a "Nearby Device Login" option. When the first device 410 receives a user selection operation based on any of "+86132****1234," "+86132****3456," and "+86132****5678," it determines the card information of the first SIM card based on the user's selected card information. The device where the first SIM card is located becomes the second device, and application login authentication can be performed based on this card information. When the first device 410 receives a user selection operation based on "+86132****1111," it determines the card information of the third SIM card based on "+86132****1111," and application login authentication can be performed based on this card information. When the first device 410 receives the user's selection operation based on "+86132****2222", it determines the card information of the second SIM card based on "+86132****2222". The device where the second SIM card is located is the third device, and the application login authentication can be performed based on the card information.

[0247] In some embodiments, the first device 410 may perform at least part of the operations of S801 upon detecting a specific operation such as application startup, thereby determining the first SIM card, the second SIM card, and the third SIM card, obtaining the user's authorization of the first SIM card, the second SIM card, and the third SIM card, and determining the priority of login authentication through the first SIM card, the second SIM card, and the third SIM card. In other embodiments, the first device 410 may also determine the first SIM card, the second SIM card, and the third SIM card in advance, obtain the user's authorization of the first SIM card, the second SIM card, and the third SIM card, and determine the priority of login authentication through the first SIM card, the second SIM card, and the third SIM card, so S801 may be omitted. For example, the user has determined the first SIM card, the second SIM card and the third SIM card in advance, and authorized the first SIM card, the second SIM card and the third SIM card, and set the priority of the first SIM card to be higher than the priority of the second SIM card, and the priority of the second SIM card to be higher than the priority of the third SIM card. Then, when the first device 410 detects a specific operation such as application startup, it may no longer execute S801, but directly perform login authentication of the application through the card information of the first SIM card according to the following steps. If the authentication fails, the login authentication of the application is performed through the card information of the second SIM card. If the authentication fails again, the login authentication of the application is performed through the card information of the third SIM card.

[0248] In some implementations, the first device 410 may implement S801 through an application or a network operator's SDK, thereby obtaining the user's authorization for the first SIM card.

[0249] S802: The first device 410 establishes a far-field network connection with the second device 430.

[0250] The first device 410 may establish a far-field network connection with the second device 430 when an application in the first device 410 requests login authentication through a cellular mobile network.

[0251] In some embodiments, the first device 410 and the second device 430 can establish the far-field network connection through a P2P traversal method or a relay method. Of course, in actual applications, the first device 410 and the second device 430 can also establish the far-field network connection through other methods. The embodiments of the present application do not limit the method for establishing the far-field network connection and the type of the far-field network connection.

[0252] In some implementations, the first device 410 may implement S802 through a network operator's SDK or phone service.

[0253] It should be noted that the far-field network connection between the first device 410 and the second device 430 can be used for a long time or multiple times once established, or the far-field network connection between the first device 410 and the second device 430 can exist frequently or permanently, so S802 can be omitted.

[0254] S803 , the first device 410 notifies the second device 430 to turn on the cellular mobile network.

[0255] Since the cellular mobile network in the second device 430 may not be turned on, in order to improve the reliability of login authentication, the first device 410 can notify the second device 430 to turn on the cellular mobile network.

[0256] In some embodiments, the first device 410 notifies the second device 430 to turn on the cellular mobile network, which may include notifying the second device 430 to turn on a cellular mobile network switch, or switching a dormant cellular mobile network to an active state.

[0257] In some implementations, the first device 410 may notify the second device 430 to turn on the cellular mobile network through a far-field network connection between the first device 410 and the second device 430 .

[0258] In some embodiments, the second device 430 can detect whether the current cellular mobile network is turned on. If so, it can notify the first device 410 that the cellular mobile network is turned on. Otherwise, it can turn on the cellular mobile network first and then notify the first device 410 that the cellular mobile network is turned on.

[0259] In some embodiments, the first device 410 can create a virtual network card corresponding to the first SIM card, which can serve as a network proxy. When the first device 410 receives data through the virtual network card, it actually receives the data through the first SIM card in the second device 430. When the first device 410 sends data through the virtual network card, it actually sends the data through the first SIM card in the second device 430.

[0260] In some implementations, the first device 410 may notify the second device 430 to connect to the cellular mobile network through the first SIM card.

[0261] In some implementations, the first device 410 may implement S803 through a network operator's SDK or phone service.

[0262] It should be noted that the second device 430 can open the cellular mobile network in advance without additional notification from the first device 410, so S803 can be omitted.

[0263] S804: The first device 410 generates a first authentication request based on the card information of the first SIM card.

[0264] The first authentication request may be used for login authentication of an application.

[0265] In some embodiments, the first authentication request may include one or more of the following: card information of the first SIM card, relevant information of the second device 430, and user identity information corresponding to the first SIM card or the second device 430. It is understandable that the first authentication request may also include more or less information for login authentication.

[0266] In some implementations, the first device 410 may implement S804 through an application or a network operator's SDK.

[0267] S805 , the first device 410 sends a first authentication request to the second server 440 .

[0268] In some embodiments, the first device 410 can be connected to the remote network to send a first authentication request to the second device 430. The second device 430 connects to the cellular mobile network through the first SIM card and then sends the first authentication request to the second server 440 through the cellular mobile network.

[0269] In some implementations, the first device 410 may implement S805 through a telephone service.

[0270] S806 , the second server 440 returns the first authentication result to the first device 410 .

[0271] The second server 440 performs authentication based on the first authentication request and generates a first authentication result. In some embodiments, the second server 440 can detect whether the card information of the first SIM card corresponds to the second device 430. If so, it is determined that the authentication is successful, otherwise it is determined that the authentication failed. In some embodiments, the second server 440 can detect whether the card information used by the cellular mobile network that sends the first authentication request is consistent with the card information carried by the first authentication request. If so, it is determined that the authentication is successful, otherwise it is determined that the authentication failed. Of course, in actual applications, the second server 440 can also perform authentication based on the first authentication request in other ways, and the embodiment of the present application does not limit the authentication method.

[0272] In some embodiments, the second server 440 sends the first authentication result to the second device 430 via a cellular mobile network, and the second device 430 sends the first authentication result to the first device 410 via a far-field network connection.

[0273] In some implementations, the first device 410 may prompt the user with a result of the login authentication, such as authentication success or authentication failure.

[0274] In some implementations, the first device 410 may implement S806 through a telephone service.

[0275] S807 , the first device 410 notifies the second device 430 to shut down the cellular mobile network.

[0276] In some embodiments, when the first device 410 receives the first authentication result, or when the login authentication ends, it can notify the second device 430 to turn off the cellular mobile network through the far-field network connection between the first device 410 and the second device 430 to save power consumption of the second device 430.

[0277] In some implementations, the first device 410 may implement S807 through a network operator's SDK or phone service.

[0278] It should be noted that, since the second device 430 may also need to use a cellular mobile network, S807 may be omitted.

[0279] S808 : The first device 410 closes the far-field network connection with the second device 430 .

[0280] The first device 410 may close the far-field network connection with the second device 430 when receiving the first authentication result or when the login authentication ends, thereby saving power consumption of the first device 410 and the second device 430 .

[0281] In some implementations, the first device 410 may implement S808 through a network operator's SDK or phone service.

[0282] It should be noted that S808 can be omitted.

[0283] In the embodiment of the present application, when performing login authentication for an application, the first device 410 can establish a far-field network connection with the second device 430, notify the second device 430 to open a cellular mobile network, and then communicate with the second server 440 via the cellular mobile network to complete the login authentication. Therefore, the first device 410 can complete login authentication for the application even if it is not configured with a SIM card, thereby improving the convenience and reliability of login authentication.

[0284] Please refer to Figure 13, which is a flowchart of a login authentication method provided in an embodiment of the present application. The method can be used as a detailed description of the method described in Figure 8 above. Before executing S802 to create a far-field network connection with the second device 430, the first device 410 can execute S809. It should be noted that the method is not limited to Figure 13 and the specific order described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0285] S809: The first device 410 determines whether there is a near field network connection with another device. If not, the process proceeds to S802 to S808; otherwise, the process proceeds to S810 to S814.

[0286] S810 , the first device 410 notifies the third device 450 to turn on the cellular mobile network.

[0287] The third device 450 may be any device that has a near field network connection with the first device 410 .

[0288] In some embodiments, the first device 410 can notify the third device 450 to turn on the cellular mobile network through a near field network connection. The third device 450 can turn on the cellular mobile network based on the second SIM card and notify the first device 410 that the cellular mobile network is turned on.

[0289] In some embodiments, the first device 410 can connect to the cellular mobile network through the third device 450 via the second SIM card.

[0290] It should be noted that, for reasons similar to those for omitting S803, S810 may also be omitted.

[0291] S811 , the first device 410 generates a second authentication request based on the card information of the second SIM card, where the second SIM card is configured on the third device 450 .

[0292] The second authentication request may be used for login authentication of the application.

[0293] It should be noted that the way in which the first device 410 executes S811 may be the same as or similar to the way in which the first device 410 executes S804, and will not be described in detail here.

[0294] S812 , the first device 410 sends a second authentication request to the second server 440 .

[0295] In some embodiments, the first device 410 can send a second authentication request to the third device 450 via a near-field network connection. The third device 450 connects to a cellular mobile network via a second SIM card and sends the second authentication request to the second server 440 via the cellular mobile network.

[0296] S813 , the second server 440 sends a second authentication result to the first device 410 .

[0297] In some embodiments, the second server 440 sends the second authentication result to the third device 450 via a cellular mobile network, and the third device 450 sends the second authentication result to the first device 410 via a near field network connection.

[0298] In some embodiments, the second server 440 in S812-S813 can be replaced by a third server, and the network operator of the third server can be different from the network operator of the second server 440, that is, when connecting to the cellular mobile network through different SIM cards and performing login authentication through card information of different SIM cards, the server providing login authentication services may also be different.

[0299] S814 , the first device 410 notifies the third device 450 to shut down the cellular mobile network.

[0300] It should be noted that, for reasons similar to those for omitting S807, S814 may also be omitted.

[0301] In some embodiments, the first device 410 may further close the near field network connection with the third device 450 to save power consumption of the first device 410 and the third device 450 .

[0302] It should be noted that the implementation of S810-S814 may also be the same as or similar to the implementation of the aforementioned S803-S807.

[0303] In an embodiment of the present application, when performing login authentication of an application, the first device 410 can determine whether there is a near-field network connection between the first device 410 and the other device. If the near-field network connection does not exist, the first device 410 can then establish a far-field network connection between the first device 410 and the second device 430, and then access the cellular mobile network through the first SIM card of the second device 430, and communicate with the second server 440 through the cellular mobile network to complete the login authentication. If the near-field network connection exists, the cellular mobile network can be accessed through the second SIM card of the third device 450, and the cellular mobile network can be communicated with the second server 440 through the cellular mobile network to complete the login authentication, without having to establish a far-field network connection, thereby improving the efficiency of login authentication.

[0304] In some embodiments, when performing login authentication for an application, the first device 410 may also simultaneously establish a near-field network connection between the first device 410 and the third device 450, and a far-field network connection between the first device 410 and the second device 430. When the moment when the far-field network connection is successfully established is earlier than the moment when the near-field network connection is successfully established, the first device 410 accesses the cellular mobile network through the first SIM card of the second device 430, and sends a first authentication request to the second server through the cellular mobile network, thereby performing login authentication for the application based on the card information of the first SIM card; when the moment when the near-field network connection is successfully established is earlier than the moment when the far-field network connection is successfully established, the first device 410 accesses the cellular mobile network through the second SIM card of the third device 450, and sends a second authentication request to the second server through the cellular mobile network, thereby performing login authentication for the application based on the card information of the second SIM card, thereby further improving the efficiency of login authentication.

[0305] Based on the same inventive concept, an embodiment of the present application further provides an electronic device. The electronic device provided in this embodiment includes: a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to execute the method described in the above method embodiment when calling the computer program.

[0306] The electronic device provided in this embodiment can perform the operations performed by the first device, the second device, the first server or the second server in the above method embodiment. Its implementation principles and technical effects are similar and will not be repeated here.

[0307] Based on the same inventive concept, an embodiment of the present application further provides a chip system. The chip system includes a processor coupled to a memory, and the processor executes a computer program stored in the memory to implement the operations performed by the first device, the second device, the first server, or the second server in the above method embodiment.

[0308] The chip system may be a single chip or a chip module composed of multiple chips.

[0309] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the operations performed by the first device, the second device, the first server or the second server in the above method embodiment are implemented.

[0310] An embodiment of the present application also provides a computer program product. When the computer program product is run on an electronic device, the electronic device implements the operations performed by the first device, the second device, the first server or the second server in the above method embodiment.

[0311] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may at least include: any entity or device capable of carrying computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk.

[0312] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0313] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0314] In the embodiments provided in this application, it should be understood that the disclosed devices / equipment and methods can be implemented in other ways. For example, the device / equipment embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. 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. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0315] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0316] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0317] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0318] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0319] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0320] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A login authentication system, characterized in that: The system includes a first server and a first device; The first server is configured to send device information of a first device set to the first device, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where the second device is configured with a first subscriber identity module (SIM) card; The first device is used to perform login authentication of an application based on the card information of the first SIM card.

2. The system according to claim 1, wherein: The first device is further configured to send a first acquisition request to the first server; The first server is further configured to send the device information of the first device set to the first device in response to the first acquisition request.

3. The system according to claim 1 or 2, characterized in that The device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

4. The system according to any one of claims 1 to 3, characterized in that: Each device in the first device set is equipped with a SIM card.

5. The system according to any one of claims 1 to 4, characterized in that: The first device set includes at least one of a second device set and a third device set; The second device set includes at least one device, and each device in the second device set is logged in to the same account as the first device; The third device set includes at least one device, and each device in the third device set is associated with an account logged in by the first device.

6. The system according to any one of claims 1 to 5, characterized in that: The system further includes the second device and a second server, wherein a far-field network connection exists between the first device and the second device; The first device is further configured to send a first authentication request to the second device through the far-field network connection, where the first authentication request is generated by the first device based on the card information of the first SIM card, and the first authentication request is used to perform login authentication of the application; The second device is configured to connect to a cellular mobile network through the first SIM card, and send the first authentication request to the second server through the cellular mobile network; The second server is configured to send a first authentication result to the second device via the cellular mobile network in response to the first authentication request; The second device is further configured to send the first authentication result to the first device through the far-field network connection.

7. The system according to claim 6, characterized in that The first device is further configured to establish the far-field network connection with the second device when performing login authentication of the application; and disconnect the far-field network connection when the login authentication is completed.

8. The system according to claim 6 or 7, characterized in that The first device is further configured to, when performing login authentication for the application, establish the far-field network connection with the second device if no near-field network connection exists between the first device and other devices.

9. The system according to any one of claims 6 to 8, characterized in that: The first device is further used to, when performing login authentication of the application, create the near-field network connection between the first device and the third device, and create the far-field network connection between the first device and the second device if there is no near-field network connection between the first device and the other device, and send the first authentication request to the second device through the far-field network connection when the moment of successful creation of the far-field network connection is earlier than the moment of successful creation of the near-field network connection.

10. The system according to any one of claims 6 to 9, characterized in that: The first device is further configured to notify the second device to turn on the cellular mobile network through the far-field network connection, and to notify the second device to turn off the cellular mobile network through the far-field network connection.

11. The system according to any one of claims 1 to 10, characterized in that: The first server is further configured to obtain device information of the second device from the second device.

12. The system according to any one of claims 1 to 11, characterized in that: The card information of the first SIM card in the first device comes from the second device or the first server.

13. A login authentication method, characterized in that: The method comprises: A first device obtains device information of a first device set from a first server, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where the second device is configured with a first subscriber identity module (SIM) card; The first device performs login authentication of the application based on the card information of the first SIM card.

14. The method according to claim 13, characterized in that The first device obtains device information of the first device set from the first server, including: The first device sends a first acquisition request to the first server; The first device receives the first device set returned by the first server in response to the first acquisition request.

15. The method according to claim 13 or 14, characterized in that The device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

16. The method according to any one of claims 13 to 15, characterized in that: Each device in the first device set is equipped with a SIM card.

17. The method according to any one of claims 13 to 16, characterized in that: The method further comprises: The first device displays a first card set, the first card set includes at least one SIM card, and any SIM card in the first card set is configured on any device in the first device set; The first device determines the first SIM card in the first card set.

18. The method according to any one of claims 13 to 16, characterized in that: The first device set includes at least one of a second device set and a third device set; The second device set includes at least one device, and each device in the second device set is logged in to the same account as the first device; The third device set includes at least one device, and each device in the third device set is associated with an account logged in by the first device.

19. The method according to claim 18, characterized in that The first device set includes a second device set and a third device set, and the method further includes: The first device displays a second card set, the second card set includes at least one SIM card, and each SIM card in the second card set is configured on any device in the second device set; If the first device determines that the second card set does not include the first SIM card, the first device displays a third card set, where the third card set includes at least one SIM card, and any SIM card in the third card set is configured on any device in the third device set; The first device determines the first SIM card in the third card set.

20. The method according to any one of claims 13 to 19, characterized in that: There is a far-field network connection between the first device and the second device, and the first device performs login authentication of the application based on the card information of the first SIM card, including: The first device sends a first authentication request to the second device through the far-field network connection, where the first authentication request is generated by the first device based on the card information of the first SIM card, and the first authentication request is used to perform login authentication of the application; The first device receives a first authentication result returned by the second device through the far-field network connection.

21. The method according to claim 20, characterized in that The method further comprises: When the first device performs login authentication of the application, the first device establishes a far-field network connection with the second device; When the login authentication is completed, the first device disconnects the far-field network connection.

22. The method according to claim 20 or 21, characterized in that The method further comprises: When the first device performs login authentication for the application, if there is no near-field network connection between the first device and other devices, the first device and the second device establish the far-field network connection.

23. The method according to any one of claims 20 to 22, characterized in that: The method further comprises: When the first device performs login authentication for the application, if no near-field network connection exists between the first device and other devices, establishing the near-field network connection with a third device, and establishing the far-field network connection between the first device and the second device; The first device sending a first authentication request to the second device through the far-field network connection includes: When the far-field network connection is successfully established earlier than the near-field network connection, the first device sends the first authentication request to the second device through the far-field network connection.

24. The method according to any one of claims 20 to 23, characterized in that: The method further comprises: The first device notifies the second device to turn on the cellular mobile network through the far-field network connection; The first device notifies the second device to turn off the cellular mobile network through the far-field network connection.

25. The method according to any one of claims 13 to 24, characterized in that: The card information of the first SIM card in the first device comes from the second device or the first server.

26. A login authentication method, characterized in that: The method comprises: A first server sends device information of a first device set to a first device, where the first device set includes at least one device, each device in the first device set is associated with the first device, and the first device set includes a second device, where a first user identity module SIM card is configured in the second device, and the first SIM card is used for login authentication of an application on the first device.

27. The method according to claim 26, characterized in that The first server sends device information of the first device set to the first device, including: The first server sends the device information of the first device set to the first device in response to the first acquisition request of the first device.

28. The method according to claim 26 or 27, characterized in that The device information of the first device set includes card information of the first SIM card.

29. The method according to any one of claims 26 to 28, characterized in that: The method further comprises: The first server obtains device information of the second device from the second device.

30. The method according to any one of claims 26 to 29, characterized in that: The device information of the first device set includes configuration information of each device in the first device set, where the configuration information of each device is used to indicate whether the device is configured with a SIM card.

31. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store a computer program; and the processor is used to execute the method according to any one of claims 13 to 25 when calling the computer program.

32. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 13 to 25 is implemented.

33. A computer program product, characterized in that When the computer program product is run on an electronic device, the electronic device is enabled to perform the method according to any one of claims 13 to 25.

34. An electronic device, characterized in that: include: A memory and a processor, the memory being used to store a computer program; the processor being used to execute the method according to any one of claims 26 to 30 when calling the computer program.

35. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 26 to 30 is implemented.

36. A computer program product, characterized in that When the computer program product is run on an electronic device, the electronic device is caused to execute the method according to any one of claims 26 to 30.