Account change notification method, server, and system

Abstract

Disclosed are an account change notification method, a server, and a system, relating to the technical field of terminals. The method comprises: receiving a first message sent by a second server, the first message indicating that account information of a first account has been changed, the second server being used for managing account information of a plurality of accounts, and the plurality of accounts including the first account; and in response to receiving the first message, sending an account information change notification to a first electronic device, the account information change notification being used for indicating that the account information of the first account has been changed, and the first electronic device being a device on which the first account has been logged in and which has subscribed to the account information change notification. By introducing a first server, when users change accounts, the first server can accurately send an account information change notification to devices on which a first account has been logged in and which have subscribed to the account information change notification, thereby reducing information redundancy and improving user experience.

Description

Account change notification methods, servers and systems

[0001] This application claims priority to Chinese patent application filed on August 29, 2024, with application number 202411208731.5 and title "Method, Server and System for Notifying Account Changes", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to an account change notification method, server, and system. Background Technology

[0003] With the development of terminal technology, users own more and more electronic devices. Many of these devices have the same applications installed, which can be different versions of the same application, thus meeting users' needs to use the same application functions on different devices. For example, users can use the same account to log in to the same application on different electronic devices, enabling data synchronization of the same application across different devices. For instance, among multiple applications logged into with the same account, if one application detects a change in user account information, it can send an account information change notification to the account server. Correspondingly, other applications within the multiple applications, if they have subscribed to notifications in advance, can receive the account information change notification sent by the account server via broadcast. For example, if one device detects a user changing their application account password, other devices logged into that application account can receive the password change notification, instructing the corresponding application to log out of the current account and prompting the user to log in again.

[0004] As can be seen, while subscription to message notifications can synchronize account-related information between different applications, the broadcast method for sending account information change notifications limits this functionality. Other applications that have subscribed to the notifications but are not logged into the same account can also receive the same account information change notification broadcast by the account server. This results in redundancy in the account information change notifications received by the applications, and poses a risk of privacy breaches related to user account changes. Summary of the Invention

[0005] To address the aforementioned technical issues, this application provides a method, server, and system for notifying users of account changes. The technical solution provided by this application introduces a first server to perform dual verification of authorized login relationships and subscription account information change notifications, thereby accurately sending account information change notifications to the application, improving account security and user experience.

[0006] To achieve the above-mentioned technical objectives, the embodiments of this application provide the following technical solutions:

[0007] Firstly, an account change notification method is provided. Applied to a first server, the method includes: receiving a first message sent by a second server, the first message indicating that the account information of a first account has changed; the second server is used to manage the account information of multiple accounts, including the first account. In response to receiving the first message, an account information change notification is sent to a first electronic device, the account information change notification indicating that the account information of the first account has changed; the first electronic device is a device that has logged into the first account and subscribed to account information change notifications.

[0008] Thus, by introducing a primary server, when a user changes their account information, the primary server can accurately send account information change notifications to devices that have logged into the primary account and subscribed to account information change notifications. This reduces information redundancy and improves the user experience.

[0009] One possible implementation involves a first message including a change type and changed account information, where the changed account information indicates the account whose information has changed. In response to receiving the first message, an account information change notification is sent to a first electronic device, including: in response to receiving the change type and changed account information, obtaining the first electronic device based on the changed account information; and sending the account information change notification corresponding to the change type to the first electronic device.

[0010] Thus, upon receiving the initial message about an account change, the system queries and identifies the first electronic device that has logged into the first account and subscribed to account change notifications, based on the changed account information in the message. Once the first electronic device to which the account change notification should be sent is determined, the corresponding account change notification is sent to it according to the type of account change. By precisely sending account change notifications, information redundancy is reduced. Furthermore, accurately sending account change notifications to the first electronic device avoids exposing the account change activity, thereby improving account security.

[0011] Another possible implementation method is to change the type of account, including at least one of freezing the account, changing the password, or canceling the account.

[0012] Another possible implementation of the account change notification method of this application includes, before receiving the first message sent by the second server, obtaining the authorization login relationship sent by the second electronic device, wherein the authorization login relationship is used to indicate that the first electronic device has logged into the first account.

[0013] In this way, by obtaining the authorized login relationship, after receiving the first information, the first verification can be performed based on the obtained authorized login relationship to filter out the first electronic device that has logged into the first account, so as to send an account information change notification.

[0014] Another possible implementation of the account change notification method of this application includes, before receiving the first message sent by the second server, obtaining subscribed notification information sent by the third server, wherein the subscribed notification information is used to indicate the subscribed account information change notification, and the third server is used to manage multiple applications.

[0015] Thus, by obtaining the subscribed notification information, after receiving the first information, a second verification can be performed based on the obtained subscribed notification information to filter out the first electronic device that has subscribed to account information change notifications, so as to send account information change notifications.

[0016] Another possible implementation is that the subscribed notification information includes: change notification type and Uniform Resource Locator URL.

[0017] The notification type indicates the type of account information change notification that needs to be sent, and the URL indicates the receiving address for the account information change notification. By adding the notification type and URL to the subscribed notification information, the first server can accurately send the account information change notification corresponding to the notification type to the first electronic device based on the URL, thus achieving precise delivery of account information change notifications.

[0018] Another possible implementation is that the first electronic device is a device that has logged into the first account and subscribed to account information change notifications, including: the first application in the first electronic device has subscribed to account information change notifications and the first application has logged into the first account.

[0019] Another possible implementation is that the second application corresponding to the first message is the same application as the first application or a different application.

[0020] Secondly, a method for notifying users of account changes is provided. Applied to a second server, the method includes: receiving a second message sent by a second electronic device, the second message indicating edited account information of a first account; the second server managing account information for multiple accounts, including the first account; and responding to the received second message by sending a first message to a first server, the first message indicating that the account information of the first account has changed, the first message instructing the first server to send an account change notification to a first electronic device, the first electronic device being a device that has logged into the first account and subscribed to account information change notifications.

[0021] One possible implementation involves sending a first message to a first server in response to a received second message, including: updating the account information of the first account stored in the second server based on the second message. This involves sending the first message to the first server. When a user changes their account information, the second server will promptly update the account information stored in the second server according to the second message, ensuring that the account information stored in the second server is always up-to-date.

[0022] Thirdly, an account change notification system is provided, comprising: a first electronic device, a second electronic device, a first server, and a second server; the second electronic device is configured to: receive a first operation from a user, the first operation being used to edit the account information of a first account logged in on the second electronic device; in response to the first operation, send a second message to the second server, the second message indicating the edited account information of the first account; the second server is configured to manage the account information of multiple accounts, including the first account. The second server is configured to: in response to the received second message, send a first message to the first server, the first message indicating that the account information of the first account has been changed. The first server is configured to: in response to the received first message, acquire the first electronic device, the first electronic device being a device that has logged in to the first account and subscribed to account information change notifications; and send an account information change notification to the first electronic device, the account information change notification indicating that the account information of the first account logged in by the first electronic device has been changed.

[0023] Thus, by introducing a primary server into the account change notification system, when a user changes their account, the primary server performs dual verification based on authorized login relationships and subscription to account information change notifications. This allows the primary server to accurately send account information change notifications to devices that have logged into the primary account and subscribed to account information change notifications. This reduces information redundancy and improves the user experience.

[0024] In another possible implementation, the first electronic device is further configured to: in response to a received account information change notification, process the account of a second application in the first electronic device, wherein the second application is configured to indicate an application that has logged into the first account and subscribed to account information change notifications. Upon receiving an account information change notification, processing the account of the second application based on the notification ensures that the first account logged into by the second application is updated promptly with the user's changes, thereby improving account security and enhancing the user experience.

[0025] Another possible implementation method is that account handling includes at least one of logging out of the account, deleting user data, and deleting business data.

[0026] Fourthly, a first server is provided, comprising: a processor and a memory; the memory is coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, wherein when the processor reads the computer instructions from the memory, the first server performs the following actions: receiving a first message sent by a second server, the first message indicating that the account information of a first account has changed, the second server being used to manage the account information of multiple accounts, including the first account; and in response to receiving the first message, sending an account information change notification to a first electronic device, the account information change notification indicating that the account information of the first account has changed, the first electronic device being a device that has logged into the first account and subscribed to account information change notifications.

[0027] One possible implementation involves a first message including a change type and changed account information, where the changed account information indicates the account whose information has changed. In response to receiving the first message, an account information change notification is sent to a first electronic device, including: in response to receiving the change type and changed account information, obtaining the first electronic device based on the changed account information; and sending the account information change notification corresponding to the change type to the first electronic device.

[0028] Another possible implementation method is to change the type of account, including at least one of freezing the account, changing the password, or canceling the account.

[0029] In another possible implementation, when the processor reads the computer instructions from the memory, it also causes the first server to execute: obtain an authorized login relationship, the authorized login relationship being used to indicate that the first electronic device has logged into the first account.

[0030] In another possible implementation, when the processor reads the computer instructions from the memory, it also causes the first server to execute: obtaining subscribed notification information sent by the third server, the subscribed notification information being used to indicate changes in subscribed account information, the third server being used to manage multiple applications.

[0031] Another possible implementation is that the subscribed notification information includes: change notification type and Uniform Resource Locator URL.

[0032] Another possible implementation is that the first electronic device is a device that has logged into the first account and subscribed to account information change notifications, including: the first application in the first electronic device has subscribed to account information change notifications and the first application has logged into the first account.

[0033] Another possible implementation is that the second application corresponding to the first message is the same application as the first application or a different application.

[0034] Fifthly, a second server is provided, comprising: a processor and a memory; the memory is coupled to the processor, the memory storing computer program code including computer instructions, wherein when the processor reads the computer instructions from the memory, the second server executes: receiving a second message sent by a second electronic device, the second message indicating edited account information of a first account, the second server managing account information of multiple accounts, including the first account. In response to the received second message, sending a first message to a first server, the first message indicating that the account information of the first account has changed, the first message instructing the first server to send an account change notification to a first electronic device, the first electronic device being a device that has logged into the first account and subscribed to account information change notifications.

[0035] One possible implementation involves sending a first message to a first server in response to a received second message, including: updating the account information of the first account stored in the second server based on the second message in response to the received second message; and sending the first message to the first server.

[0036] Sixthly, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (also referred to as instructions or code), at least one computer program being loaded by a processor and executing the method of the first aspect or any embodiment of the first aspect; or executing the method of the second aspect or any embodiment of the second aspect.

[0037] For the technical effects of the sixth aspect and any of its implementations, please refer to the technical effects of the first aspect and any of its implementations mentioned above; they will not be repeated here.

[0038] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to perform the method of the first aspect or any one of the embodiments of the first aspect; or causes the computer to perform the method of the second aspect or any one of the embodiments of the second aspect.

[0039] The technical effects of the seventh aspect and any implementation thereof can be found in the first aspect and any implementation thereof, and will not be repeated here.

[0040] Eighthly, embodiments of this application provide a circuit system including a processing circuit configured to perform the method of the first aspect or any embodiment of the first aspect; or, the processing circuit configured to perform the method of the second aspect or any embodiment of the second aspect.

[0041] The technical effects of the eighth aspect and any of its implementations can be found in the first aspect and any of its implementations, and will not be repeated here.

[0042] Ninthly, embodiments of this application provide a chip system including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes the method of the first aspect or any one of the embodiments of the first aspect; or, the at least one processor executes the method of the second aspect or any one of the embodiments of the second aspect.

[0043] The technical effects of the ninth aspect and any implementation thereof can be found in the first aspect and any implementation thereof, and will not be repeated here. Attached Figure Description

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

[0045] Figure 1A is a schematic diagram of a subscription account information change notification provided in an exemplary embodiment of this application;

[0046] Figure 1B is a schematic diagram of sending an account information change notification provided in an exemplary embodiment of this application;

[0047] Figure 2A is a schematic diagram illustrating the authorization of the scope of information acquisition provided in an exemplary embodiment of this application;

[0048] Figure 2B is a schematic diagram of sending an account information change notification provided in an exemplary embodiment of this application;

[0049] Figure 3 is a schematic diagram of a communication system in which the account change notification method provided in an exemplary embodiment of this application is applied;

[0050] Figure 4A is a schematic diagram of the structure of a first or second electronic device provided in an exemplary embodiment of this application;

[0051] Figure 4B is a software structure block diagram of a first electronic device or a second electronic device provided in an exemplary embodiment of this application;

[0052] Figure 4C is a schematic diagram of the structure of a first server or a second server provided in an exemplary embodiment of this application;

[0053] Figure 5 is a flowchart illustrating an exemplary embodiment of the account change notification method provided in this application;

[0054] Figure 6 is a schematic diagram of the subscription account information change notification process provided in an exemplary embodiment of this application;

[0055] Figure 7 is a schematic diagram of the interface for notification of changes to subscription account information provided in an exemplary embodiment of this application;

[0056] Figure 8 is a schematic diagram of the configuration interface for account information change notification provided in an exemplary embodiment of this application;

[0057] Figure 9 is a schematic diagram of the process for obtaining an authorized login relationship provided in an exemplary embodiment of this application;

[0058] Figure 10 is a schematic diagram of the process of sending an account information change notification according to an exemplary embodiment of this application;

[0059] Figure 11 is a flowchart illustrating an exemplary embodiment of the account change notification method provided in this application;

[0060] Figure 12 is a schematic diagram of the structure of a first server provided in an exemplary embodiment of this application;

[0061] Figure 13 is a schematic diagram of the structure of a second server provided in an exemplary embodiment of this application. Detailed Implementation

[0062] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one or more (including two).

[0063] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of 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 "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0064] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0065] It should be noted that all information (including but not limited to device information, personal information of the subject), data (including but not limited to data used for analysis, stored data, and displayed data), and signals involved in this application have been authorized by the subject or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the first and second information involved in this application were obtained with full authorization.

[0066] To send account information change notifications to applications, the industry commonly uses two methods, which are briefly described below.

[0067] Method 1: Applications can subscribe to notification functionality on the account server. When an account changes on the account server, the server will broadcast the account information change notification to all applications that have subscribed to the notification functionality. This process can be divided into two parts. The first part is illustrated in Figure 1A, showing the subscription for account information change notifications. Applications A and B subscribe to the notification functionality on the account server and set a Uniform Resource Locator (URL) to receive account information change notifications. Application C does not subscribe to the notification functionality on the account server. Optionally, applications A, B, and C can be the same application installed on different electronic devices (such as mobile phones, tablets, etc.), and these "same" applications may be the same or different versions.

[0068] The second part, as shown in Figure 1B, illustrates the process of sending account information change notifications. When a user makes changes to their account, the account server generates an account information change notification and broadcasts it to all applications that have subscribed to the notification function. In other words, since applications A and B have subscribed to the notification function, they will receive the account information change notification and take appropriate action based on its content (e.g., forced logout, user notification, etc.). However, application C, which has not subscribed to the notification function, will not receive the account information change notification.

[0069] However, while this method can send account information change notifications to applications that have subscribed to notification functions, it also leads to redundancy in the account information change notifications received by those applications. Furthermore, receiving all account information change notifications sent by the account server also poses a privacy risk regarding user account changes. For example, if a user changes the account (account 1) logged into the target application, both application A (login account 1) and application B (login account 2) can receive the account information change notification sent by the account server via broadcast messages. Therefore, the account information change notification received by application B (login account 2) is redundant and could lead to a privacy risk related to the target application's account change behavior. It should be understood that the target application, application A, application B, and application C are the same application installed on different electronic devices, and the account server is used to maintain this same application. Different account servers can be used to maintain different applications.

[0070] Method 2: After subscribing to notification functionality on the account server, the application also needs to request and obtain permission to receive notifications within a fixed scope. For example, the application might only receive notifications about account information changes corresponding to changes in account 1. Upon authorization, and if an account changes on the account server, the account server will send the account information change notification to the application that subscribed to notification functionality and obtained the permission to receive the fixed scope information. For instance, application A requests and obtains permission to receive notifications about account information changes corresponding to changes in account 1, and application B requests and obtains permission to receive notifications about account information changes corresponding to changes in account 2. If a user changes the account 1 logged into the target application, application A can receive the account information change notification sent by the account server. Since application B does not have permission to access account 1 information, application B cannot receive the account information change notification sent by the account server.

[0071] The process can be divided into three parts. The first part is shown in Figure 1A, which is a schematic diagram of subscribing to account information change notifications. Application A and Application B subscribe to the message notification function from the account server and set a URL to receive account information change notifications. Application C does not subscribe to the message notification function from the account server.

[0072] Part Two, as shown in Figure 2A, illustrates the authorization process for accessing a specific information scope. Step 201: Application A requests authorization to access a specific information scope. Application A requests authorization to access a specific information scope from the account server. Step 202: The account server requests user authorization for the information scope to be granted to Application A. The account server forwards Application A's request for authorization to access a specific information scope to the user, thus completing the user's authorization for Application A to access the information scope. Step 203: Application A's authorization is granted. The user authorizes Application A to receive information within the specified scope. Step 204: Application A's authorization is complete. Similarly, the steps for Application C to request authorization to access a specific information scope are the same as those for Application A, and will not be repeated here. The steps for Application C to request authorization to access a specific information scope can be found in steps 205 to 208. Step 205: Application C requests authorization to access a specific information scope. Step 206: The account server requests user authorization for the information scope to be granted to Application C. Step 207: Application C's authorization is granted. Step 208: Application C's authorization is complete. Application B did not request authorization to access a specific information scope.

[0073] The second part, as shown in Figure 2B, illustrates the process of sending account information change notifications. When a user makes changes to their account, the account server generates an account information change notification. Since application A has subscribed to the notification function and obtained the information scope authorization from the user, it can receive the account information change notification sent by the account server. After receiving the notification, application A takes appropriate action based on its content (e.g., forced logout, prompting the user, etc.). Although application B has also subscribed to the notification function, it has not requested information scope authorization, therefore application B will not receive the account information change notification. Similarly, although application C has obtained the information scope authorization from the user, it has not subscribed to the notification function and therefore will not receive the account information change notification.

[0074] However, while this method can reduce the number of account information change notifications and prevent the application from receiving redundant account information change notifications, it is only applicable to new applications, i.e., applications with the function of requesting information access scope. It is not applicable to applications that have already connected to the account server. This requires the redevelopment and maintenance of applications that have already connected to the account server, which is not conducive to the expansion and maintenance of applications that have already connected to the account server.

[0075] Based on this, this application provides an account change notification method. By introducing a first server, the method performs dual verification of authorized login relationships and subscription to account information change notifications. When a user changes their account, the first server can accurately send the account information change notification to devices that have logged into the first account and subscribed to account information change notifications. This reduces information redundancy and improves the user experience.

[0076] Figure 3 is a schematic diagram of the communication system used in the account change notification method provided in this application embodiment. As shown in Figure 3, the communication system includes a first electronic device 100, a second electronic device 200, a first server 300, and a second server 400.

[0077] Optionally, the first electronic device 100 or the second electronic device 200 may be a terminal device such as a mobile phone, tablet computer, laptop computer, ultra-mobile personal computer (UMPC), smart screen, netbook, personal digital assistant (PDA), wearable device, artificial intelligence (AI) device, etc. The operating system installed on the first electronic device 100 or the second electronic device 200 includes, but is not limited to, Alternatively, other operating systems may be used. This application does not limit the specific type of the first electronic device 100 or the second electronic device 200, or the operating system installed thereon.

[0078] Optionally, the first server 300 or the second server 400 can be a cloud server or a network server, or other devices or network devices with computing capabilities. The first server 300 or the second server 400 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0079] In some examples, the second electronic device 200 has an account client (such as a second application) installed for account changes, and the first electronic device 100 has a first application installed for account login. Optionally, the first application and the second application can be the same application, or the versions of the first application and the second application can be the same or different. Alternatively, the first application and the second application can be different applications. Optionally, the number of the first electronic device 100 or the second electronic device 200 can be one or more.

[0080] In some examples, the first electronic device 100 and the second electronic device 200 form a trusted network. Electronic devices in the trusted network can identify other electronic devices as trusted devices. Optionally, electronic devices in the trusted network log in to the same account; or, electronic devices in the trusted network can search for other electronic devices through a terminal application.

[0081] Optionally, the first electronic device 100 can also establish a trusted network through tap-to-tap, Bluetooth, device-to-device (D2D) or other means.

[0082] For example, Figure 4A shows a schematic diagram of the structure of a first electronic device 100 or a second electronic device 200.

[0083] The first electronic device 100 or the second electronic device 200 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0084] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the first electronic device 100 or the second electronic device 200. In other embodiments of this application, the first electronic device 100 or the second electronic device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0085] For example, if the first electronic device 100 is a PC, the first electronic device 100 may not include the mobile communication module 150 and the SIM card interface 195.

[0086] Processor 110 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0087] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0088] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge the first electronic device 100 or the second electronic device 200, and can also be used for data transfer between the first electronic device 100 or the second electronic device 200 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0089] The charging management module 140 receives charging input from a charger, which can be a wireless charger or a wired charger. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0090] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0091] The wireless communication function of the first electronic device 100 or the second electronic device 200 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0092] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the first electronic device 100 or the second electronic device 200 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0093] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the first electronic device 100 or the second electronic device 200. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0094] The wireless communication module 160 can provide solutions for wireless communication applications on the first electronic device 100 or the second electronic device 200, 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), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0095] In some embodiments, antenna 1 of the first electronic device 100 or the second electronic device 200 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling the first electronic device 100 or the second electronic device 200 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0096] The first electronic device 100 or the second electronic device 200 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0097] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be manufactured using a liquid crystal display (LCD), such as an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the first electronic device 100 or the second electronic device 200 may include one or N displays 194, where N is a positive integer greater than 1.

[0098] The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0099] A touch sensor, also known as a "touch device," can be located on the display screen 194. The touch sensor and the display screen 194 together form a touchscreen, also known as a "touchscreen." The touch sensor detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor may also be located on the surface of the first electronic device 100 or the second electronic device 200, in a different position than the display screen 194.

[0100] The software system of the first electronic device 100 or the second electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to exemplify the software structure of the first electronic device 100 and the second electronic device 200.

[0101] Figure 4B is a software structure block diagram of the first electronic device 100 and the second electronic device 200 according to an embodiment of this application.

[0102] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

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

[0104] As shown in Figure 4B, the application package may include applications such as app store, camera, calendar, music, gallery, map, call, and video.

[0105] Optionally, as shown in Figure 4B, the first electronic device 100 has a first application installed, and the second electronic device 200 has a second application installed.

[0106] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0107] As shown in Figure 4B, the application framework layer may include content providers, resource managers, view systems, etc.

[0108] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0109] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0110] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0111] Optionally, as shown in Figure 4B, the application framework layer of the first electronic device 100 may also include, for example, a distributed device management system (DMS) and an application management service (AMS).

[0112] In some examples, the first electronic device 100 can obtain information about electronic devices in the trusted network through DMS. Optionally, after determining that it is necessary to log in to the first application through the second application, the first electronic device 100 can query the trusted devices (such as the second electronic device 200) with the second application installed in the trusted network through DMS.

[0113] In some examples, after determining that the trusted device used for login authentication of the first application is the second electronic device 200, the first electronic device 100 initiates the login authentication interface of the second application through AMS. Subsequently, during the login authentication process of the first application in the first electronic device 100 through the second application in the second electronic device 200, the first electronic device 100 can manage the lifecycle of the second application through AMS.

[0114] Optionally, as shown in Figure 4B, the application framework layer of the second electronic device 200 may also include, for example, a package manager service (PMS) and an application management system (AMS).

[0115] The Android Runtime consists of core libraries and a virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system.

[0116] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0117] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0118] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0119] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0120] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0124] For example, the first server 300 or the second server 400 can be a device or server with computing capabilities, such as a cloud server or a network server. The aforementioned server can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0125] For example, taking the hardware structure shown in Figure 4C as an example, the hardware structure shown in Figure 4C will be described.

[0126] The first server 300 or the second server 400 includes at least one processor 201, a communication line 202, a memory 203, and at least one communication interface 204. The memory 203 may also be included within the processor 201.

[0127] The processor 201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0128] Communication line 202 may include a path for transmitting information between the aforementioned components.

[0129] Communication interface 204 is used for communication with other devices. In this embodiment, the communication interface can be a module, circuit, bus, interface, transceiver, or other device capable of communication functions, used for communication with other devices. Optionally, when the communication interface is a transceiver, the transceiver can be a separately configured transmitter used to send information to other devices, or it can be a separately configured receiver used to receive information from other devices. The transceiver can also be a component that integrates sending and receiving information functions; this embodiment does not limit the specific implementation of the transceiver.

[0130] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 202. The memory may also be integrated with the processor.

[0131] The memory 203 stores computer execution instructions for implementing the solution of this application, and its execution is controlled by the processor 201. The processor 201 executes the computer execution instructions stored in the memory 203, thereby implementing the account change notification method provided in the following embodiments of this application.

[0132] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, instructions, computer program or other names, and the embodiments of this application do not specifically limit them.

[0133] In a specific implementation, as one embodiment, processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG4C.

[0134] In a specific implementation, as one embodiment, the first server 300 or the second server 400 may include multiple processors, such as processor 201 and processor 207 in FIG. 4C. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0135] In a specific implementation, as one embodiment, the first server 300 or the second server 400 may further include an output device 205 and an input device 206. The output device 205 communicates with the processor 201 and can display information in various ways. For example, the output device 205 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 206 communicates with the processor 201 and can receive user input in various ways. For example, the input device 206 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0136] It is understood that the structure illustrated in FIG. 4C of this application embodiment does not constitute the only limitation on the structural implementation of the first server 300 or the second server 400. In other embodiments of this application, the first server 300 or the second server 400 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0137] The following uses the first electronic device 100 as the first electronic device, the second electronic device 200 as the second electronic device, the first server 300 as the first server, and the second server 400 as the second server as the second server as examples to illustrate the account change notification method provided in the embodiments of this application.

[0138] For example, Figure 5 is a flowchart illustrating an account change notification method provided in an embodiment of this application. As shown in Figure 5, the method includes the following steps.

[0139] Step 501: The first server obtains information about the applications that have subscribed to notification information.

[0140] For example, the first server acquires and stores subscribed notification information. Optionally, the first server may be, for example, an OAuth server, which can be used to maintain information about the applications that have subscribed to the notifications, facilitating the subsequent sending of account message change notifications to that application.

[0141] The "Subscribed Notifications" information indicates that the user has subscribed to account information change notifications. Alternatively, it describes that the electronic device or an application within the electronic device has subscribed to message notification functionality.

[0142] The subscribed notification information is sent by a third-party server. Alternatively, the subscribed notification information is sent by the third-party server corresponding to the app store platform after the developer subscribes on the app store platform on the electronic device.

[0143] Optionally, the subscribed notification information includes at least one of the following: change notification type and URL, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0144] The change notification type indicates the type of change for which an account information change notification needs to be sent, and the URL indicates the address for receiving account information change notifications.

[0145] For example, Figure 6 shows a flowchart illustrating the subscription process for account information change notifications. During application development, the developer logs into a page provided by a third server using an electronic device (such as a first electronic device, a second electronic device, or other electronic devices) to complete the relevant settings for the application to be uploaded. For example, the third server provides a page for subscribing to notification information and, based on the developer's settings, obtains the developer's instruction to enable subscription to account information change notifications, i.e., executes step 601. The third server manages multiple applications, and at least one application can be subscribed to for account information change notifications through the third server. Optionally, during the subscription process, the third server can obtain information such as the change type and URL of the account information change notification based on the developer's actions. The URL in this information points to the application that has subscribed to the notification information. Optionally, after obtaining this information, the third server can send it to the first server. For example, the third server sends the change notification type and URL to the first server, i.e., executes step 602. Correspondingly, upon receiving the change notification type and URL, the first server stores the change notification type and URL, i.e., executes step 603. After the first server stores the change notification type and URL, it sends a subscription completion notification to the third server, indicating that it has obtained the change notification type and URL, i.e., proceeding to step 604. Thus, by adding the change notification type and URL to the subscribed notification information, the first server can accurately send the account information change notification corresponding to the change notification type to the first electronic device based on the URL, achieving precise delivery of account information change notifications.

[0146] It should be understood that during the notification subscription process, developers can configure the notification type and / or URL, as well as other settings. The above example, using the developer's configuration of the notification type and URL, illustrates the interaction process between the third-party server and the first-party server, but does not impose any restrictions on the content of the notification subscription.

[0147] The URL (or simply address) is a concise and unique representation of the location where account information change notifications are received. For example, configuring the URL of application A on a third-party server obtains the URL or port on which application A receives account information change notifications. Optionally, the URL corresponding to application A will not change even after application A is installed on different electronic devices.

[0148] Optionally, the change type includes at least one of freezing the account, changing the account password, and canceling the account, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0149] For example, to more clearly describe the process of subscribing to account information change notifications, Figure 7 shows a schematic diagram of the interface for subscribing to account information change notifications. After the electronic device logs into the URL provided by the third server, the interface shown in Figure 7 is displayed. This interface can display the functions that the currently developed application can obtain after subscribing to account information change notifications, such as receiving notification messages after an account-related abnormal event occurs. In response to the developer's operation of the enable control, the electronic device can send an enable instruction to the third server, which is used to instruct the user to enable the subscription to account information change notifications. Subsequently, the third server can send relevant information about the account information change notification configuration interface to the electronic device to trigger the electronic device to display the configuration interface shown in Figure 8. Accordingly, after displaying the configuration interface, the electronic device can receive the developer's editing operations on the configuration interface for relevant configuration information such as application ID, URL, and change notification type. In response to the developer's configuration completion operation (such as the operation of the submit control), the electronic device sends a configuration completion instruction to the third server, which carries the relevant configuration information of the account information change notification edited by the developer. Then, after receiving the configuration completion instruction, the third server can obtain the relevant configuration information, such as the change notification type and URL.

[0150] Step 502: The first electronic device logs into the first account according to the user's operation.

[0151] In some embodiments, the first electronic device has a first application installed that can be used to log in to a first account. Optionally, there may be one or more first applications. For example, the first electronic device may have a video application installed that can log in to a user's video account. Alternatively, the first electronic device may have an app store application, a smart living application, etc., which can log in to a user's account.

[0152] In some embodiments, after logging into a first account based on user operation, the first electronic device can obtain authorization for the first account. Optionally, after logging into the first account through a first application, the first electronic device can obtain authorization for the first account of the first application. Optionally, after the first account authorization is completed, if the first account in other electronic devices changes subsequently, the first electronic device that has subscribed to notification messages and has authorized the first account can receive an account information change notification. The specific account information change notification interaction process is detailed in the relevant descriptions of the following steps.

[0153] Optionally, if there are multiple first applications, the first account can obtain authorization after any first application logs in to the first account.

[0154] In some embodiments, the first electronic device can complete login authorization by interacting with the application server corresponding to the first application currently requesting login. Optionally, the first server can obtain an authorization login indication sent by the application server, which indicates that the first electronic device has completed authorization login for the first account of the first application. Optionally, the authorization login indication may include, for example, the identifier of the first application, the first account, and the identifier of the first electronic device.

[0155] For example, Figure 9 shows a flowchart illustrating the process of obtaining an authorized login relationship. Step 901: The first electronic device logs into the first account based on user operation. For example, after the first electronic device responds to the user's trigger operation on the login control, it triggers account login authorization. The first electronic device requests login to the first account from the application server corresponding to the first application, i.e., step 902 is executed. After receiving the login request, the application server sends corresponding information to the first electronic device to trigger the display of the account and password input interface on the interface of the first electronic device. After obtaining the account and password input by the user in the input interface, the first electronic device sends the account and password to the application server to realize the login of the first account on the first electronic device. After obtaining the login of the first account by the first electronic device, the application server can send an authorized login instruction to the first server to indicate that the first electronic device has completed the login of the first account, i.e., step 903 is executed.

[0156] Step 503: The first server obtains the authorized login relationship.

[0157] The authorized login relationship is used to indicate that the first account has been logged in on the first electronic device.

[0158] In some embodiments, after obtaining the authorized login relationship, the first server may store the authorized login relationship. Optionally, after the first electronic device logs in to the first account, the first server may obtain the authorized login relationship corresponding to the first account of the first electronic device. For example, the first server obtains the authorized login relationship based on an authorized login instruction received from the application server or the first electronic device.

[0159] For example, as shown in Figure 9, the process of obtaining the authorized login relationship is illustrated as follows: After receiving the authorized login instruction, the first server obtains the authorized login relationship based on the information carried in the instruction, such as the identifier of the first application, the first account, and the identifier of the first electronic device. Subsequently, the first server stores the authorized login relationship, i.e., executes step 904. After storing the authorized login relationship, the first server sends a storage completion notification to the application server, i.e., executes step 905. After receiving the storage completion notification from the first server, the application server sends a login completion notification to the first electronic device, allowing the user to know from the first electronic device that the first account login is complete, i.e., executes step 906. By storing the authorized login relationship on the first server, the first server can perform a first-level verification based on the authorized login relationship, thereby filtering out the first electronic devices that have logged into the first account, in order to send account information change notifications.

[0160] In some embodiments, the step of subscribing to notification information in step 501 and the steps of obtaining authorized login relationship in steps 502 and 503 are not sequentially limited. That is, in practical applications, the step of subscribing to notification information can be performed first, followed by the step of obtaining authorized login relationship; or, the step of obtaining authorized login relationship can be performed first, followed by the step of subscribing to notification information; or, they can be performed simultaneously. This application embodiment does not specifically limit this.

[0161] Step 504: The second electronic device detects the user's first operation of changing the first account.

[0162] The second electronic device is a different device from the first electronic device that is already logged into the first account. For example, the second electronic device is the user's mobile phone, currently logged into the first account. The first electronic device is the user's tablet, which has previously been logged into the first account.

[0163] In some embodiments, after logging into the first account, the second electronic device can change the first account based on the user's first operation.

[0164] Optionally, the first operation includes at least one of freezing the first account, changing the password of the first account, and canceling the first account, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0165] For example, the second electronic device receives a first operation from the user, the first operation being used to edit the account information of the first account logged in on the second electronic device.

[0166] Step 505: The second electronic device sends a second message to the second server.

[0167] The second message indicates the edited account information of the first account.

[0168] The second server (also known as an account server) is used to manage account information for multiple accounts, including the first account. Alternatively, the second server is a server used to store and manage account information.

[0169] For example, in response to the first operation, the second electronic device sends a second message to the second server to indicate the account change required by the current user.

[0170] Step 506: The second server sends the first message to the first server.

[0171] The first message indicates that the account information of the first account has been changed.

[0172] In some embodiments, the second server sends a first message to the first server in response to the received second message.

[0173] In some embodiments, the second server stores account information for multiple accounts. Optionally, after receiving a second message from the second electronic device, the second server may update the stored account information for the first account.

[0174] For example, in response to the received second message, the second server updates the account information of the first account stored in the second server based on the second message; and sends the first message to the first server. That is, after the user changes the account information of the first account, the second server updates the originally stored account information based on the changed account information, ensuring that the account information stored in the second server is up-to-date. After updating the account information stored in the second server, the first message is sent to the first server. Alternatively, the second server may first send the first message to the first server, and then update the stored account information of the first account.

[0175] For example, the first message includes the change type and the changed account information, whereby the changed account information indicates the account whose account information has been changed.

[0176] Change type refers to the type of operation a user performs on their account.

[0177] Optionally, the change type includes at least one of freezing the account, changing the account password, and canceling the account, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0178] Step 507: The first server sends an account message change notification to the first electronic device.

[0179] The first server is used to verify the authorized login relationship of the account and / or subscription to account information change notifications. Optionally, as described above, the authorized login relationship is used to describe whether the electronic device or application has obtained account login authorization. Or, the authorized login relationship is used to describe whether the electronic device or application has logged into the first account.

[0180] Referring to steps 501-503 above, the first electronic device is one that has logged into the first account and subscribed to account information change notifications. The first application within the first electronic device has subscribed to account information change notifications and has logged into the first account.

[0181] In some embodiments, the first server, in response to a received first message, acquires the first electronic device. The first server sends an account information change notification to the first electronic device. Optionally, the first server sends the account information change notification to a designated first electronic device according to the service protocol, domain name, and port in the URL. Alternatively, the first server sends the account information change notification to a designated application in the first electronic device according to the transport protocol, domain name, and port in the URL.

[0182] Optionally, the account information change notification is used to indicate that the account information of the first account that the first electronic device has logged into has changed.

[0183] Optionally, the display format of the account information change notification may include at least one of SMS and information pop-up, but is not limited thereto, and the embodiments of this application do not specifically limit it.

[0184] In some embodiments, in response to receiving the change type and changed account information in the first message, the first server retrieves the first electronic device that has logged into the first account from the device list stored in the first server, based on the changed account information. After determining the first electronic device, the first server sends an account information change notification corresponding to the change type to the first electronic device. By accurately sending the account information change notification, information redundancy is reduced. Furthermore, accurately sending the account information change notification to the first electronic device also avoids the exposure of the account change behavior, thereby improving account security.

[0185] Optionally, in response to receiving the change type and changed account information, the first server performs a double verification. First verification: Based on the changed account information, the first server retrieves the first electronic device that has logged into the first account from the device list stored on the first server. Second verification: After identifying the first electronic device, the first server verifies whether these first electronic devices have subscribed to account information change notifications. After the first server performs both verifications, it sends the account information change notification corresponding to the change type to all first electronic devices that have both logged into the first account and subscribed to account information change notifications.

[0186] The order in which the first server performs dual verification is not specifically limited in the embodiments of this application.

[0187] In some embodiments, in step 504, the second electronic device that obtains the change of the first account and the first electronic device are devices logged into the same account; or, the application in the second electronic device and the application in the first electronic device are both logged into the same account; or, the application in the second electronic device and the application in the first electronic device have previously logged into the same account. That is, if the first account logged into the second electronic device changes, the first electronic device will receive an account information change notification. Or, if the first account logged into the second application in the second electronic device changes, the first application that has previously logged into the first account in the first electronic device will also receive an account information change notification. Optionally, the second application corresponding to the first message may be the same application as the first application or a different application.

[0188] Optionally, the first electronic device and the second electronic device may be the same device or they may not be the same device. This application does not specifically limit this.

[0189] For example, the first electronic device and the second electronic device may be different devices, such as the first electronic device being a user's mobile phone and the second electronic device being a user's tablet. Both the phone and tablet have video applications installed and are logged into the same video account. If the video account on the tablet changes due to user actions, the phone can obtain the change information. As another example, the first electronic device and the second electronic device may be the same device, such as the first electronic device being a user's mobile phone. The phone has a smart living application and an e-commerce application installed, and both are logged into the same account. If the phone changes the account through the smart living application based on user actions, the e-commerce application on the phone can also receive the account change information. It should be understood that the applications in the aforementioned examples have all subscribed to message notifications and have authorized account access.

[0190] In some embodiments, the first electronic device performs account processing in response to a received account information change notification.

[0191] Optionally, account processing includes at least one of logging out of the account, deleting user data, and deleting business data, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0192] Optionally, in response to the received account information change notification, the first electronic device performs account processing on at least one first application in the first electronic device.

[0193] The first application is used to indicate the application in the first electronic device that has logged into the first account and subscribed to account information change notifications. Optionally, the first application in the first electronic device and the second application in the second device whose account has been changed can be the same application or different applications.

[0194] For example, Figure 10 shows a flowchart illustrating the process of sending account information change notifications. The second electronic device responds to the user's change operation on the first account by modifying the first account, i.e., executing step 1001, taking changing the password of the first account as an example. After the user changes the password of the first account on the second electronic device, the second electronic device sends the modified account information to the second server, i.e., executing step 1002, whereby the second electronic device sends a second message to the second server. After receiving the second message, the second server updates the account information of the first account stored in the second server based on the modified password. In other words, after the user changes the password of the first account, the second server updates the previously stored password of the first account based on the second message, i.e., executing step 1003. After updating the password of the first account stored in the second server, the second server sends first information to the first server, i.e., sending the change type and changed account information of the first account, i.e., executing step 1004. After receiving the change type and changed account information, the first server performs dual verification of the authorized login relationship and the subscription to the account information change notification. First verification: Based on the changed account information, the first server retrieves the first electronic device that has logged into the first account from the device list stored in the first server. Second verification: After identifying the first electronic device, the first server verifies whether these first electronic devices have subscribed to account information change notifications. After the first server performs both verifications, it obtains the first electronic device that has both logged into the first account and subscribed to account information change notifications, i.e., proceeds to step 1005. Then, the first server sends an account information change notification corresponding to the password of the first account to the first electronic device that has both logged into the first account and subscribed to account information change notifications, i.e., proceeds to step 1006. After receiving the account information change notification, the first electronic device performs account processing, for example, displaying "Account password has been changed, please log in again" on the interface of the first electronic device; or displaying it in the notification message of the first application; or displaying it on the first electronic device in the form of an SMS, i.e., proceeding to step 1007.

[0195] In summary, the technical solution provided in this application, by introducing a first server and performing dual verification of authorized login relationships and subscription account information change notifications on the first server, ensures that when a user changes their account, the first server can accurately send account information change notifications to devices that have logged into the first account and subscribed to account information change notifications. This ensures accurate delivery of account information change notifications to the application, reduces information redundancy, and improves account security and user experience. Furthermore, the technical solution provided in this application allows for expansion of the account information change notification function on both newly connected electronic devices and existing connected electronic devices. It only requires enabling the subscription storage of subscribed notification information and obtaining authorized login relationships on the first server, eliminating the need for secondary development of the electronic devices or applications. This significantly improves access efficiency and reduces development and maintenance costs.

[0196] To better understand the relationships between various devices during the execution of the account change notification method, the account change notification method provided in this application embodiment is described in detail below with reference to Figure 11.

[0197] For example, Figure 11 is a flowchart illustrating an account change notification method provided in an embodiment of this application. As shown in Figure 11, the method includes the following steps.

[0198] Step 1101: The first server obtains information about the applications that have subscribed to notification information.

[0199] For example, during application development, the electronic device corresponding to the third server displays the details page of the application for which account information change notifications are to be subscribed. The details page allows subscription to account information change notifications. During the process of enabling subscription to account information change notifications through the details page, the third server can configure the subscribed notifications according to the developer's actions, such as configuring the notification type and URL. After configuring the notification type and URL, the third server sends them to the first server. The first server responds by receiving the notification type and URL and stores them. After the first server stores the notification type and URL, the subscription is complete.

[0200] Step 1102: Obtain login authorization relationship.

[0201] For example, a first electronic device logs into a first account based on a user's operation. Upon receiving a login control trigger, the first electronic device authorizes account login. The first electronic device then requests login access to the first account from the application server corresponding to the first application. Upon receiving the login request, the application server displays an input interface for the username and password. Specifically, in response to the login access trigger, the first electronic device requests login access to the first account from the application server, and the application server displays an input interface for the username and password on the first electronic device's screen.

[0202] The first electronic device receives the user's username and password. After the user completes the username and password input, the application server sends an authorization login instruction to the first server. Upon receiving the authorization login instruction, the first server determines the authorization login relationship based on the information carried in the instruction, such as the identifier of the first application, the first account, and the identifier of the first electronic device. The first server then stores the authorization login relationship. After storing the authorization login relationship, the first server sends a login completion notification to the first electronic device, allowing the user to be notified on the first electronic device that the first account login is complete.

[0203] The user actions include: triggering the login button and then authorizing account login.

[0204] Optionally, the triggering operation includes at least one of single-click, double-click, and triple-click, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0205] Step 1103: The second electronic device detects the user's first operation of changing the first account.

[0206] For example, the second electronic device detects that the user has changed the account information of the first account through the first operation.

[0207] Optionally, the first operation includes at least one of freezing the first account, changing the password of the first account, and canceling the first account, but is not limited thereto, and the embodiments of this application do not specifically limit this.

[0208] Step 1104: The second electronic device sends a second message to the second server.

[0209] For example, after the second electronic device detects the user's first operation on the first account, the second electronic device sends the changed account information of the first account to the second server, that is, sends the second message.

[0210] Step 1105: The second server sends the first message to the first server.

[0211] For example, after receiving the second message, the second server updates the account information of the first account stored in the second server based on the second message. After updating the account information stored in the second server, the second server sends the first message to the first server.

[0212] For example, the first message includes a change type and changed account information, whereby the changed account information indicates the account whose account information has been changed. The change type refers to the type of operation performed by the user on the account.

[0213] Step 1106: The first server sends an account message change notification to the first electronic device.

[0214] For example, after receiving the first message, the first server performs a double verification based on the change type and changed account information in the first message. First verification: Based on the changed account information, the first server retrieves the first electronic device that has logged into the first account from the device list stored on the first server. Second verification: After identifying the first electronic device, the first server verifies whether these first electronic devices have subscribed to account information change notifications. After the first server performs both verifications, it sends the account information change notification corresponding to the change type to the first electronic devices that have both logged into the first account and subscribed to account information change notifications.

[0215] In some embodiments, the order in which the first server performs dual verification is not specifically limited in this application.

[0216] In summary, the technical solution provided in this application introduces a first server to perform dual verification of authorized login relationships and subscription account information change notifications. When a user changes their account, the first server can accurately send the account information change notification to devices that have logged into the first account and subscribed to account information change notifications. This ensures that the account information change notification is accurately sent to the application, reducing information redundancy and improving account security and user experience.

[0217] The account change notification method provided in this application embodiment has been described in detail above with reference to Figures 5-11. The server provided in this application embodiment will be described in detail below with reference to Figure 12.

[0218] In one possible design, Figure 12 is a schematic diagram of the structure of a first server provided in an embodiment of this application. As shown in Figure 12, the first server may include a transceiver unit 1201 and a processing unit 1202. The first server can be used to implement the functions of the first server involved in the above method embodiments.

[0219] Optionally, the transceiver unit 1201 is used to support the first server in executing steps 501, 503, and 507 in Figure 5.

[0220] Optionally, the processing unit 1202 is used to support the first server in executing steps 1101 and 1106 in FIG11.

[0221] The transceiver unit may include a receiving unit and a sending unit, and may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver module. The operation and / or function of each unit in the first server are respectively to implement the corresponding process of the account change notification method described in the above method embodiments. All relevant content of each step involved in the above method embodiments can be referred to the functional description of the corresponding functional unit, and for the sake of brevity, it will not be repeated here.

[0222] Optionally, the first server shown in FIG12 may further include a storage unit (not shown in FIG12) storing programs or instructions. When the transceiver unit 1201 and the processing unit 1202 execute the program or instructions, the first server shown in FIG12 can execute the account change notification method described in the above method embodiments.

[0223] The technical effect of the first server shown in Figure 12 can be referred to the technical effect of the account change notification method described in the above method embodiments, and will not be repeated here.

[0224] In addition to being a first server, the technical solution provided in this application can also be a functional unit or chip in the first server, or a device used in conjunction with the first server.

[0225] In one possible design, Figure 13 is a schematic diagram of the structure of the second server provided in an embodiment of this application. As shown in Figure 13, the second server may include a transceiver unit 1301 and a processing unit 1302. The second server can be used to implement the functions of the second electronic device involved in the above method embodiments.

[0226] Optionally, the transceiver unit 1301 is used to support the second server in performing step 506 in Figure 5.

[0227] Optionally, the processing unit 1302 is configured to support the second server in performing step 1003 in FIG10.

[0228] The transceiver unit may include a receiving unit and a sending unit, and may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver module. The operation and / or function of each unit in the second server are respectively to implement the corresponding process of the account change notification method described in the above method embodiments. All relevant content of each step involved in the above method embodiments can be referred to the functional description of the corresponding functional unit, and for the sake of brevity, it will not be repeated here.

[0229] Optionally, the second server shown in FIG13 may also include a storage unit (not shown in FIG13) in which programs or instructions are stored.

[0230] The technical effect of the second server shown in Figure 13 can be referred to the technical effect of the account change notification method described in the above method embodiments, and will not be repeated here.

[0231] In addition to being a second server, the technical solution provided in this application can also be a functional unit or chip in a second server, or a device used in conjunction with a second server.

[0232] This application also provides a chip system, including: a processor coupled to a memory, the memory being used to store programs or instructions, wherein when the program or instructions are executed by the processor, the chip system implements the methods in any of the above method embodiments.

[0233] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0234] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application embodiment does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application embodiment does not specifically limit the type of memory or the arrangement of the memory and processor.

[0235] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0236] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0237] This application also provides a computer-readable storage medium storing a computer program. When the computer program is run on a computer, it causes the computer to perform the aforementioned steps to implement the account change notification method in the above embodiments.

[0238] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the account change notification method described in the above embodiments.

[0239] Additionally, this application also provides an apparatus. Specifically, the apparatus may be a component or module, and may include one or more processors and a memory connected together. The memory stores a computer program. When the computer program is executed by one or more processors, the apparatus performs the account change notification method described in the above method embodiments.

[0240] The apparatus, computer-readable storage medium, computer program product, or chip provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0241] The steps of the methods or algorithms described in conjunction with the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC).

[0242] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, the division of the above functional modules is only used as an example. In practical applications, the above functions can be assigned to different functional modules as needed; that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

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

[0244] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0245] Computer-readable storage media include, but are not limited to, any of the following: USB flash drive, portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media capable of storing program code.

[0246] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for notifying users of account changes, characterized in that, Applied to a first server, the method includes: The system receives a first message from a second server, indicating that the account information of the first account has been changed. The second server is used to manage the account information of multiple accounts, including the first account. In response to receiving the first message, an account information change notification is sent to the first electronic device. The account information change notification is used to indicate that the account information of the first account has been changed. The first electronic device is a device that has logged into the first account and subscribed to account information change notifications.

2. The method according to claim 1, characterized in that, The first message includes the change type and the changed account information, wherein the changed account information is used to indicate the account whose account information has been changed; The response to receiving the first message, sending an account information change notification to the first electronic device, includes: In response to receiving the change type and the changed account information, the first electronic device is obtained based on the changed account information; Send the account information change notification corresponding to the change type to the first electronic device.

3. The method according to claim 2, characterized in that, The change type includes at least one of the following: freezing the account, changing the account password, and canceling the account.

4. The method according to any one of claims 1 to 3, characterized in that, Before receiving the first message sent by the second server, the method further includes: Obtain the authorized login relationship, which is used to indicate that the first account has been logged in on the first electronic device.

5. The method according to any one of claims 1 to 3, characterized in that, Before receiving the first message sent by the second server, the method further includes: Obtain subscribed notification information sent by a third server. The subscribed notification information is used to indicate that account information change notifications have been subscribed to. The third server is used to manage multiple applications.

6. The method according to claim 5, characterized in that, The subscribed notification information includes: change notification type and Uniform Resource Locator URL; The change notification type indicates the type of change for which the account information change notification needs to be sent, and the URL indicates the address for receiving the account information change notification.

7. The method according to any one of claims 1 to 6, characterized in that, The first electronic device is a device that has logged into the first account and subscribed to account information change notifications, including: The first application in the first electronic device has subscribed to the account information change notification, and the first application has logged into the first account.

8. The method according to claim 7, characterized in that, The second application corresponding to the first message is either the same application as the first application or a different application.

9. A method for notifying users of account changes, characterized in that, Applied to a second server, the method includes: The server receives a second message from a second electronic device, the second message indicating the edited account information of the first account; the second server is used to manage the account information of multiple accounts, the multiple accounts including the first account. In response to the received second message, a first message is sent to the first server. The first message indicates that the account information of the first account has been changed. The first message is used to instruct the first server to send an account change notification to the first electronic device, which is a device that has logged into the first account and subscribed to account information change notifications.

10. The method according to claim 9, characterized in that, The step of sending a first message to the first server in response to the received second message includes: In response to the received second message, update the account information of the first account stored in the second server; Send the first message to the first server.

11. An account change notification system, characterized in that, The system includes: a first electronic device, a second electronic device, a first server, and a second server; The second electronic device is used for: The system receives a first operation from the user, which is used to edit the account information of the first account logged in by the second electronic device. In response to the first operation, a second message is sent to the second server, the second message indicating the edited account information of the first account, the second server being used to manage the account information of multiple accounts, the multiple accounts including the first account; The second server is configured to: in response to the received second message, send a first message to the first server, the first message indicating that the account information of the first account has been changed; The first server is used for: In response to the received first message, the first electronic device is obtained, wherein the first electronic device is a device that has logged into the first account and subscribed to account information change notifications; Send an account information change notification to the first electronic device, the account information change notification being used to indicate that the account information of the first account that the first electronic device has logged into has changed.

12. The system according to claim 11, characterized in that, The first electronic device is further configured to: in response to the received account information change notification, process the account information of the first electronic device.

13. The system according to claim 12, characterized in that, The account processing includes at least one of logging out of the account, deleting user data, and deleting business data.

14. A first server, characterized in that, include: Processor and memory; The memory is coupled to the processor and is used to store computer program code, the computer program code including computer instructions, which, when the processor reads the computer instructions from the memory, cause the first server to implement the method as described in any one of claims 1-8.

15. A second server, characterized in that, include: Processor and memory; The memory is coupled to the processor and is used to store computer program code, the computer program code including computer instructions, which, when the processor reads the computer instructions from the memory, cause the second server to implement the method as described in claim 9 or 10.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to implement the account change notification method as described in any one of claims 1 to 8; or to implement the method as described in claim 9 or 10.

17. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-8; or, causes the computer to perform the method as described in claim 9 or 10.

Images