WO2019011187A1

WO2019011187A1 - Method, device, and apparatus for loss reporting, removing loss report, and service management of electronic account

Info

Publication number: WO2019011187A1
Application number: PCT/CN2018/094785
Authority: WO
Inventors: 黄孟俊
Original assignee: 阿里巴巴集团控股有限公司; 黄孟俊
Priority date: 2017-07-11
Filing date: 2018-07-06
Publication date: 2019-01-17
Also published as: CN107464121A; TW201909072A

Abstract

Provided in the description of the present application are a method, device and apparatus for loss reporting, removing a loss report, and service management of an electronic account, the loss reporting method comprising: setting a second account as an associated account of a first account on the basis of identity authentication information of each account; when receiving a loss reporting request for the first account, performing identity authentication on the first account and the second account according to the identity authentication information; if the first account and the second account pass the identity authentication, reporting a loss for the first account. By implementing the embodiments of the present description, a loss may be promptly reported for an account by means of an associated account, which ensures the timeliness of the loss reporting process.

Description

Loss, unhook, business management methods, devices and devices for electronic accounts

Technical field

The present specification relates to the field of computer technology, and in particular, to reporting, reporting, and management methods, devices, and devices for electronic accounts.

Background technique

At present, the use of many electronic accounts provides the function of reporting loss and unloading. When a user loses a device such as a mobile phone, there is still the possibility of being logged in and operating an electronic account on the lost device. In order to improve security, it is necessary to provide some new electronic account loss reporting and solution solutions.

Summary of the invention

In view of this, the present specification provides a method for reporting loss, cancellation, service management, device and computer device of an electronic account.

According to a first aspect of the embodiments of the present specification, a method for reporting loss of an electronic account is provided, including the steps of:

Setting the second account as the associated account of the first account based on the authentication information of each account;

Upon receiving the request for loss reporting on the first account, authenticating the first account and the second account according to the identity verification information;

If the first account and the second account are authenticated, the first account is reported for loss.

According to a second aspect of the embodiments of the present specification, a method for reporting loss of an electronic account is provided, including the steps of:

If the first account and the second account are authenticated, the first account is reported for loss;

When receiving the request for unpacking the first account, the first account is authenticated according to the unchecked verification information, and if the identity verification of the first account is passed, the first account is unlinked.

According to a third aspect of the embodiments of the present specification, a method for managing an electronic account is provided, including the steps of:

And when receiving the service management request for the first account, performing identity verification on the first account and the second account according to the identity verification information;

If the first account and the second account authentication pass, the service management for the first account is performed.

According to a fourth aspect of the embodiments of the present disclosure, a device for reporting loss of an electronic account includes:

An account association module, configured to set a second account as an associated account of the first account based on the identity verification information of each account;

a report of the first account and the second account according to the identity verification information, when the request for loss reporting of the first account is received;

The account loss reporting module is configured to report the first account after the first account and the second account are authenticated.

According to a fifth aspect of the embodiments of the present disclosure, a device for reporting loss of an electronic account includes:

An account loss reporting module, configured to report the first account after the first account and the second account are authenticated;

The unpacking verification module is configured to perform identity verification on the first account according to the unchecked verification information when receiving the request for unpacking the first account;

The account unplugging module is configured to unmount the first account after the identity verification of the first account is passed.

According to a sixth aspect of the embodiments of the present disclosure, a service management apparatus for an electronic account is provided, including:

a management verification module, configured to perform identity verification on the first account and the second account according to the identity verification information when receiving a service management request for the first account;

The service management module is configured to perform service management for the first account if the first account and the second account are authenticated.

According to a seventh aspect of the embodiments of the present specification, a computer device is provided, including:

processor;

a memory that stores processor executable instructions;

The processor is coupled to the memory for reading program instructions stored in the memory, and in response, performing the following operations:

According to an eighth aspect of the embodiments of the present specification, a computer device is provided, including:

processor;

a memory that stores processor executable instructions;

According to a ninth aspect of the embodiments of the present specification, a computer device is provided, including:

processor;

a memory that stores processor executable instructions;

When the embodiment provided by the present specification is implemented, when the related account setting request is received, another account is set as the associated account of the account, and the associated account can be ensured that the related account is not involved in illegal misappropriation; in the future, when the loss is reported, the account can be utilized in time. The associated account is reported as a loss of the account, which guarantees the timeliness of the loss reporting process.

In addition, by setting another account to become the associated account of the account, it is also possible to verify the account and the associated account when there is a need to manage the account, such as loss reporting, password modification, payment, etc., to achieve timely and secure account management.

DRAWINGS

1 is an architectural diagram of a system for implementing loss reporting/unwrapping/account management of an electronic account, according to an exemplary embodiment of the present specification;

2 is a flowchart of a method for reporting loss of an electronic account according to an exemplary embodiment of the present specification;

3 is a sequence diagram of a method for reporting loss of an electronic account according to an exemplary embodiment of the present specification;

4 is a sequence diagram of a method for reporting loss of an electronic account according to another exemplary embodiment of the present specification;

FIG. 5 is a flowchart of a method for reporting loss reporting of an electronic account according to an exemplary embodiment of the present specification; FIG.

6 is a sequence diagram of a method for reporting loss reporting of an electronic account according to an exemplary embodiment of the present specification;

FIG. 7 is a flowchart of a service management method of an electronic account according to an exemplary embodiment of the present specification; FIG.

FIG. 8 is a logic block diagram of a report loss device of an electronic account according to an exemplary embodiment of the present specification; FIG.

9 is a logic block diagram of a loss reporting device of an electronic account shown in an exemplary embodiment of the present specification;

10 is a logic block diagram of a service management apparatus of an electronic account shown in an exemplary embodiment of the present specification;

FIG. 11 is a hardware structural diagram of a computer device where the loss/lost cancellation/service management device of the electronic account is shown in an exemplary embodiment of the present specification.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Instead, they are merely examples of devices and methods consistent with aspects of the present specification as detailed in the appended claims.

The terminology used in the description is for the purpose of describing particular embodiments, and is not intended to be limiting. The singular forms "a", "the" and "the" It will also be understood that the term "and/or" used in the specification means and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information without departing from the scope of the present description. Similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determination."

Referring to Figure 1, there is shown a networked environment 100 of various embodiments. Networked environment 100 may include an operations server 105 that communicates data with one or more clients 106 via network 112, and a computing environment 103 that may be integrated with or independent of operations server 105. Network 112 may include, for example, the Internet, an intranet, an extranet, a wide area network (WAN), a local area network (LAN), a wired network, a wireless network, or other suitable network, or the like, or any combination of two or more such networks. Throughout the discussion of the exemplary embodiments, it is to be understood that the terms "data" and "information" are used interchangeably throughout the specification to refer to text, images, audio, video or any other that may be present in a computer-based environment. Formal information.

The operational server 105 can include commercially available Hypertext Transfer Protocol (HTTP) server applications such as an HTTP server, Internet Information Services (IIS), and/or other servers.

Client 106 can be a network device with an application installed. Such network devices may include hardware from a desktop computer, laptop computer, tablet computer, smart phone, handheld computer, personal digital assistant ("PDA"), or any other wired or wireless processor driven device. From the system software, it may be an operating system integrated with a web browser, or an operating system installed with a dedicated application; such an operating system may be a Windows series operating system or a Linux operating system, or may be a mobile platform. Android, IOS, etc.

Once the user uses the client 106 and initiates a registration request to the operations server 105 over the network 112, the operations server 105 can record the registration information for the user and open an account with the preset rights in the operations server 105 in accordance with the registration request. In addition, an account registered by each user, various passwords (login passwords and/or business processing passwords, etc.) of each account, and authentication information uploaded when the user registers may be stored.

Each time the user accesses the corresponding content through the client 106, and the access to the operation server 105 occurs, the operation server 105 can know and record the identifier indicating the user identity based on the user ID carried in the information at each access. Access. In particular, the access time of the user may be recorded, optionally, the IP address at the time of access, or the type of hardware of the network device used, or the version of the operating system on which the client version/client is based may be recorded. One or more. In particular, for access to a specific operation, such as changing a password, adding a friend, transferring or transferring an available resource, reporting a lost account, and unregistering the account, the operation server 105 can record the operation access and execute the corresponding internal or external The user is given a specific response after processing. In general, all operational requests and general access will leave a corresponding record in the operational server 105. The operations server 105 can classify all operations of different users according to the user ID. For the operation of the interaction behavior, for example, the interaction between different registered users, it is also possible to classify and constitute the collection according to the above user ID.

The operations server 105 can use the database 115 to store the above user access information. In addition, data that can also be stored in the database 115 includes, for example, application requirement data, business rules, client capability data, application market data, customer data, and the like. Applications in database 115 may correspond to those applications that have been provided by the developer for inclusion in the application marketplace. Applications may include, for example, mobile applications, Hypertext Markup Language 5 (HTML5) applications, desktop applications, and/or other applications.

Computing environment 103 may include, for example, a server computer or any other system that provides computing power. Alternatively, one or more computing devices may be employed in computing environment 103, which may be arranged, for example, as one or more server groups or groups of computers or other devices. For example, multiple computing devices can collectively constitute a cloud computing resource, a grid computing resource, and/or any other distributed computing device. The various method embodiments of the present specification described below can be performed under the control of one or more computing devices configured with executable instructions.

Various applications and/or other functionality may be performed in computing environment 103, in accordance with various embodiments. Components executed on computing environment 103 include, for example, access data import services, access data analysis services, application data import services, application data analysis services, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein.

Additionally, various data may be obtained by computing environment 103, such as from database 115 described above. As can be appreciated, database 115 can represent a plurality of databases 115. The data stored in database 115 is associated, for example, with the operations of the various embodiments described below.

In the process of data related to the mobile Internet, the mobile terminal may interact with the operation server 105 under the control of the terminal user to complete service management such as associated account setting, account loss reporting, loss reporting, password modification, etc., which is provided by the payment service provider. The payment platform is taken as an example to describe the technical solution for setting the associated account under the payment platform in this specification. The payment service provider may be a third-party payment service provider such as Alipay or WeChat, or may be a bank, and the payment service provider may set up its own website or provide a server for the payment platform dedicated to payment. In this way, the user can complete the associated account setup through the services provided on the payment platform. The mobile terminal and/or the fixed terminal can access the payment platform provided by the payment service provider via the Internet, and use the payment platform to complete the specific process involved in the associated account setting. Moreover, for convenience and some security considerations, the mobile terminal and/or the fixed terminal may install a dedicated client (one of which is an application), such as an application provided by the payment service provider. In either case, the payment platform provided by the payment service provider needs to obtain the identity verification information of the relevant user in the process of setting the associated account involved in this specification. The following uses a server to represent a platform including a payment platform, unless otherwise specified.

In a practical application, a client 106 in the networked environment 100 can be a first client, and the client can be installed in a device held by the first user (which may be referred to as a first client device) in a networked environment. Another client 106 in 100 is a second client, which may be installed in a device (which may be referred to as a second client device) held by the second user, where the client 106 may be a payment service provider The payment APP or payment webpage provided may also be an instant messaging APP or a time communication webpage provided by the instant messaging service provider, or may be a mobile banking APP or online banking provided by the bank, and in other embodiments, may also be other electronic For the client that the account is logged in, the embodiment of the present specification does not limit this.

The associated account is set in the embodiment of the present specification, considering that many services of the client 106 are strongly bound to devices (such as mobile phones) held by the user, such as Alipay, WeChat, and the like, and the payment service provider allows When paying, the user performs a passwordless payment transaction (such as face-to-face payment, applepay, etc.), or allows the user to change some important account information, such as payment password, login password, etc., by means of a verification code (such as a mobile phone verification code). Although these services provide users with convenience, they also bring certain hidden dangers of illegal use. If the equipment held by the user is lost, others may use the equipment of the owner to conduct various transactions in a short period of time. In other words, other people can use the device of the owner to reset or change the account password of the owner through the verification code, which poses a great threat to the user's funds. When the user loses the device, it needs to be in the shortest possible time. The electronic account is reported to be lost, that is, the function of the electronic account is suspended, and the loss can be resumed after the loss is reported in the future.

In order to report the electronic account in the shortest possible time after the loss of the device held by the user, or to perform other business management, the associated second account may be set for the first account of the first client, and then the associated account may be associated. The second account sets the service management of the loss, cancellation, and password modification of the first account.

When the associated account is actually set, the first user who logs in to the first client can select the trusted second user, such as his or her friends and relatives, and then set the second account of the second user in the second client as the associated account of the account, wherein, the second The client that the user logs in to is the second client.

The setting of the associated account may be initiated by the first user or the second user, and the first user may send a request for setting the second account to its associated account through the first client that the user logs in, and after receiving the request, the server receives the request. The instructions may be sent to the first client and the second client respectively, indicating that the first user and the second user respectively provide the identity information of the respective account, or may collect the current identity information of the two accounts by themselves, and then the server collects the The identity information provided by the two users matches the stored authentication information; if the two match, the verification is passed, and the second account is set as the associated account of the first account. If not, the associated account setting fails, and A message that the associated account setup failed may be sent to the first user and the second user.

In some cases, the authentication information may be an account identity and a verification password, and the identity may be a certificate number, an account number, an account name, a bound mobile phone number, a bound mailbox, a binding question, etc., verification The password may be consistent with another service password such as a login password and a payment password of the account corresponding to the verification password, for example, one of the historical login passwords of the account corresponding to the verification password, or a historical payment password of the account corresponding to the verification password. one of the. In addition, the verification password may also be an additional password set by the user different from the service password such as the login password and the service password. In this case, the identity information may be sent by the first user and the second user to the server through the client that is logged in. When the identity verification is performed, if the identity information received by the server is inconsistent with the pre-stored identity verification information, the two are determined. If there is no match, if the match is made, the match is determined. In other examples, whether the identity information provided by the two users matches the authentication information stored by the server is determined by other methods, which is not limited in this embodiment.

In other cases, the authentication information may also be an account transaction record, an account credit score, an account search record, an account environment information, etc. The records mentioned herein may be recent records in the history, such as nearly one month. The internal information may be the IP address, geographic location information, magnetic field fingerprint, WIFI fingerprint, environmental audio, etc. of the first user and/or the second user when logging in. The geographical location information may be the geographical name, latitude and longitude, etc. of the login location. The magnetic field fingerprint may be the magnetic field strength of the registered place, the WIFI fingerprint may be the intensity of the WIFI signal of the registered place, and the ambient audio may be the audio of the sound collected at the login. In this situation, the identity information can be actively collected by the server. When performing identity verification, it is determined that the identity information collected by the server is inconsistent with the pre-stored identity verification information. If the identity is consistent, for example, 70% of the transaction records of the two users in the past month. The trading locations are consistent, then the match is determined, and the inconsistency is determined, and the mismatch is determined. In other examples, it is also possible to determine whether the identity information provided by the two users matches the authentication information stored by the server, and the embodiment of the present specification does not limit this.

In other cases, the authentication information may also be status information indicating that the first and/or second account are in a secure state, and the identity information may be current status information of the first and/or second account, when performing authentication, the server The current identity information of the first and/or second account may be actively searched, and if the current identity information is status information indicating that the first and/or second account are in a secure state, determining the first and/or second accounts Verification passed. The identity information of the first and/or second account may be updated by the server according to the environmental information of the first and/or second account, for example, at 8:00 every morning, the transaction record of the previous day and the transaction record of the previous month are determined. The degree of matching, if the degree of matching exceeds 60%, determines that the status information of today is status information indicating that the first and/or second account are in a secure state.

In addition, in addition to the above verification, the random verification code can be further sent to the device held by the user by means of a short message, an email, or the like. When the random verification code fed back by the client corresponding to the account is also correct, the authentication of the first account and the second account is passed, and if the random verification code of the feedback is incorrect, the authentication of the first account and the second account does not pass.

After completing the associated account settings, the server can store the associated account table. The associated account table may include a first account, an associated account of the first account (second account), and authentication information of the first account and its associated account.

In other embodiments, the first user may also set an associated account by other means, such as a telephone customer service. For example, the customer service is provided with the identity information of the account of the second user by telephone communication, and then the customer service determines whether the identity verification is passed by querying the identity verification information stored by the server, and stores the associated account table in the server after the identity verification is passed.

After setting the associated account, in the future, when the service management such as loss reporting, unhooking, and password modification is performed, the first user can use the associated account in time to perform corresponding business management on the account, so even if the device held by the user is lost, the user can be timely The electronic account that is logged in on the device performs business management such as loss reporting, unhooking, and password modification. Hereinafter, the process of reporting, unregistering and business management of the electronic account of the present specification will be described in detail with reference to FIG.

Referring to FIG. 2, FIG. 2 is a flowchart of a method for reporting loss of an electronic account according to an exemplary embodiment of the present disclosure. The embodiment can be applied to a server, and may include the following steps S201-S203:

Step S201: Set the second account as the associated account of the first account based on the identity verification information of each account.

Step S202: When receiving the request for reporting the loss of the first account, performing identity verification on the first account and the second account according to the identity verification information.

Step S203: If the first account and the second account are authenticated, the first account is lost.

In the embodiment of the present specification, the process of setting the associated account in the embodiment corresponding to FIG. 1 may be referred to in step S201, and the technical content involved is not described herein.

The associated account setting request may be initiated by the first client to the server to set the second account as the associated account, or the second client may initiate a request to the server to set the associated account of the first account. After receiving the request, the server may adopt the process of setting the associated account in the embodiment corresponding to FIG. 1, and the verification method involved, and performing identity verification on the first account and the second account.

In order to avoid theft of the pirate of the device held by the user, before the associated account is set through the first account or the second account, the first account or the second account may be authenticated to the server after passing the security status verification (a type of authentication). The associated account setting request, after receiving the request, the server only authenticates another account, and if the verification is passed, it is determined that the identity verification of the first account and the second account is passed, and the associated account is set.

In other examples, the server may detect whether the first account and the second account are in a secure state when receiving the associated account setting request, in order to prevent the pirate from setting the associated account through the first account or the second account, and if in a secure state, Determining the authentication pass, instructing the user to input the authentication information as the authentication basis when the subsequent service management is performed, for example, the identity verification information mentioned above may be the identity identifier and the verification password of the account; or the identity verification information when the account is directly registered, As the authentication basis for subsequent business management, such as the transaction record of the account mentioned above, the credit score of the account, the search record of the account, the environmental information of the account, etc., when the scenario of setting the associated account is different, the specific implementation manner is different. The embodiment of the present specification does not limit this.

If the contact account is requested by telephone customer service or other means, it is necessary to verify the identity of the respective account of the first user and the second user and the verification password, and the verification password can be the login password, other service password and the additional account of the user's respective account. At least one of the passwords is consistent, and the business password is a payment password.

In some examples, in order to prevent the user other than the owner from changing the account password or other service password after the client device (such as the mobile phone) is lost, the verification password may be set as the real-time password or historical password of the account corresponding to the verification password. One of them.

After the associated account is set, if the client device of the first user is lost, or the client device is not lost, but the first user thinks that the electronic account has security risks, the first user can use the corresponding customer service, webpage, and self. The client device (applicable to the case where the client device is not lost) or the client device of the user corresponding to the associated account initiates a request for the loss of the first account. The customer service personnel or the server may notify the user corresponding to the first account and its associated account to provide identity information, or collect identity information of the first account and/or the second account, and then compare the identity information provided by the user or collected by itself to the associated account. The stored authentication information is compared. If it does not match, the report fails. If it matches, the first account is reported by verifying the identity. For the specific authentication method, the corresponding manner mentioned in the above setting of the associated account may be adopted, and the embodiment of the present specification does not limit this. Other users than the user corresponding to the first account or the second account are difficult to authenticate the information of the first account and the second account. Therefore, it is difficult for other users to report the first account by the associated account.

In addition, after the first account is reported to be lost, other users other than the owner can obtain the identity verification information for the account to be revoked through the device that the owner holds, and in the embodiment of the present specification, while reporting the first account, An unmount password (unlock password) for unmounting the first account can be generated. The unlock password can only be known to the user who has lost the first account through the associated account. Therefore, even if the user other than the owner loses the identity verification information for unregistering the account through the device that the owner has lost, it is also difficult to report the loss. The first account is unlinked. Therefore, the solution of this specification can further ensure the security of the unpacking process and provide more comprehensive security protection for the electronic account.

In an actual application, if the request for reporting the loss of the first account is initiated by the second account, the server may send the unlock password to the client of the second account. So that the first user records the unlock password, and provides the unlock password to complete the unpacking when the first account is unlinked. The undo password can be pre-set by the designer of this specification, and generated by the server according to the generation rule.

In some examples, if the unattached password is a fixed or fixed-rule unpacked password, other users may steal the unlocked password, such as by eavesdropping on a large number of users' account unwrapping processes, and analyzing Unlock the password, and then, after the first user reports the first account, the first account is unlocked by the stolen password, which poses a threat to account security. In order to avoid the occurrence of the situation, the unattached password is a one-time password, and is temporarily randomly generated by the server when receiving the request for reporting the loss of the first account.

The following describes the specific process of reporting loss through the telephone customer service and reporting the loss through the client, respectively, with reference to FIGS. 3 and 4:

Referring to FIG. 3, in this embodiment, the first client device is a device held by the first user, and the first client is running in the device. After the first client is started, the first user can obtain the registration by using the first client. The first account and the login password are logged in to the server; the second client device is a device held by the second user, the second client is running in the device, and the second user can pass the registration after the second client is started. The obtained second account and login password are logged into the server. The first account and the second account may be third party payment accounts.

The first user sets the second account as the associated account of the first account based on the identity verification information of each account. In this example, the identity verification information herein may be the account number and payment password of the respective accounts of the first user and the second user. .

After the first client device held by the first user is lost, the first user may initiate a request for the first account loss report to the server by using the second client that is logged in by the second user (step S301), where the first user may The first account is selected in the second client, and then the associated account loss report is initiated, and the account number of the first account and the second account may be carried in the request.

After receiving the request for the loss of the first account, the server then sends a notification to the second client to input the identity information (step S302).

The first user and the second user may respectively send the identity information of the respective account to the server through the second client (step S303). Since the previously sent request already includes the respective account number, only the payment password of the respective account may be sent at this time. .

After receiving the payment passwords of the first account and the second account, the server searches for the payment passwords corresponding to the first account and the second account, and then compares the stored payment passwords with the received payment passwords (step S304), if they are consistent, Then, step S305 to step S306 are performed, and if they are not identical, step S307 may be selected to be performed.

Step S305: Generate and store an unlock password for unregistering the first account.

Step S306: Send the unlock password to the second client.

Step S307: Send a loss alarm to the second client device, prompting the second user that the account has a security risk.

Referring to FIG. 4, in the embodiment, the first client device is a device held by the first user, and the first client is run in the device. After the first client is started, the first user can obtain the registration by using the first client. The first account and the login password are logged in to the server; the second client device is a device held by the second user, the second client is running in the device, and the second user can pass the registration after the second client is started. The obtained second account and login password are logged into the server. The first account and the second account may be bank online banking accounts or mobile banking accounts. The customer service device is a device held by the customer service personnel of the bank hotline. The customer service client is running inside the device. After the customer service client is opened, the customer service personnel can log in to the server through the customer service account and login password obtained during registration, and can also pass the The client device answers the user's hotline.

The first user sets the second account as the associated account of the first account based on the identity verification information of each account, where the identity verification information may be the account number and login password of the first user and the second user respectively.

After the first client device held by the first user is lost, the first user can call the bank's customer service hotline through the second client device that the second user logs in, and initiate a report loss to the first account to the customer service personnel who answer the hotline. The request (step S401), the account number of the first account may be carried in the request.

After receiving the request for the loss of the first account, the customer service personnel notifies the first user of the notification of the identity information of the account and its associated account through the client device (step S402).

The first user can provide the customer service personnel with the identity information of the account of the first user and the second user through the customer service hotline (step S403). Since the previously sent request already includes the account number of the first user, only the first one can be provided at this time. The payment password for the account, the account number for the second account, and the payment password.

After receiving the payment password and the account number of the first account and the second account, the customer service personnel may request the server to store the payment password and the account number corresponding to the first account and the second account through the client device (step S404), and the server searches Returning to the client device (step S405), then the agent compares the server and the account number and payment password provided by the first user (step S406). If they are all consistent, step S407 to step S408 are performed, if not, then Hanging up the hotline and reporting the loss of the first account failed.

Step S407: The customer service personnel requests the server to cancel the unlocked password for the first account through the client device.

Step S408: After receiving the request, the server generates and stores an unattached password for unmounting the first account.

Step S409, the server sends the unlock password to the client device.

In step S410, the customer service personnel provides the unlocking password to the first user through the hotline.

In other examples, other ways can also be used to report the user's electronic account.

After completing the loss of the electronic account, if the user retrieves the lost mobile phone, reissues the SIM card, or thinks that his electronic account no longer has security risks, he can apply for the release of his electronic account. The specific unpacking process can refer to the figure. 5 is a flowchart of a method for reporting loss reporting of an electronic account according to an exemplary embodiment of the present specification. The embodiment can be applied to a server, and may include the following steps S501-S505:

Step S501: Set the second account as the associated account of the first account based on the identity verification information of each account.

Step S502: When receiving the request for reporting the loss of the first account, performing identity verification on the first account and the second account according to the identity verification information.

Step S503: If the first account and the second account are authenticated, the first account is reported for loss.

Step S504: When receiving the request for unpacking the first account, perform identity verification on the first account based on the unchecked verification information.

Step S505: If the identity verification of the first account is passed, the first account is unlinked.

The technical content involved in the steps S501 to S503 of the embodiment of the present specification corresponds to the technical content of the embodiment corresponding to FIG. 1 to FIG. 4, and details are not described herein again.

In actual application, if the user wants to unregister the electronic account that was previously reported lost, the user can initiate the cancellation of the electronic account through the telephone service of the corresponding service, the client of the first account, or the client of the associated account (second account). Request.

If the unregistered password is not generated when the report is lost, the verification information is the authentication information of the first account or the authentication information of the first account and the second account, and the customer service or the server may notify the user to provide the identity information of the first account. Or, the user corresponding to the associated account may be notified to provide the identity information of the respective account, and then the identity information provided is compared with the identity information stored when the account is registered, or the identity information provided is compared with the identity stored when the associated account is set. The verification information is compared. If it does not match, the unmounting fails. If it matches, the unmounting is completed. For the specific authentication method, the corresponding manner mentioned above may be adopted, and the embodiment of the present specification does not limit this.

If the decryption password is generated before the report is lost, the undo verification information includes the unattached password, and in some cases, the authentication information of the first account may be included, or the authentication information of the first account and the second account may be included.

When the verification information is included, the customer service or the server may notify the user to provide a password for unlocking. If the password provided by the user is consistent with the unlock password, the identity verification of the first account is passed, and the first account is performed. Solutions Hanging. If it is inconsistent, it is determined that the authentication fails, and the first account is prohibited from being unlinked.

When the verification information includes the unlocking password and the authentication information of the first account, the agent or the server may notify the user to provide the identity information of the first account, and then compare the identity information provided and the identity information stored when the account is registered, or The identity information provided by the comparison is compared with the authentication information stored when the associated account is set. If it does not match, the unmounting fails, and if it matches, the unmounting is completed. For the specific authentication method, the corresponding manner mentioned above may be adopted, and the embodiment of the present specification does not limit this.

When the verification information includes the unlocking password and the authentication information of the first account, the customer service personnel or the server may also notify the user and the user corresponding to the associated account to provide the identity information of the respective account, and then compare the provided identity information with the registered account. The stored identity information, or the identity information provided by the comparison is compared with the authentication information stored when the associated account is set. If it does not match, the unmounting fails, and if it matches, the unmounting is completed. For the specific authentication method, the corresponding manner mentioned above may be adopted, and the embodiment of the present specification does not limit this.

In addition, after receiving the request for the first account to be revoked by the client of the second account, the server may send a random verification code to the terminal device bound to the second account, in order to further avoid the security risk of the unattached. The verification verification information may further include a random verification code returned by the client of the second account, and if the password for the unpacking and the random verification code sent by the client of the second account are received within the predetermined time period, the received judgment is determined. Whether the random verification code is consistent with the issued random verification code. If they are consistent, it is judged whether the received password is consistent with the unattached password. If they are consistent, the first account is unlinked, and in other cases, the suspension is prohibited.

The following describes the specific process of reporting the loss of the client through the associated account by referring to FIG. 6 respectively:

Referring to FIG. 6, in this embodiment, the first client device is a device held by the first user, and the first client is run in the device. After the first client is started, the first user can obtain the registration by using the first client. The first account and the login password are logged in to the server; the second client device is a device held by the second user, the second client is running in the device, and the second user can pass the registration after the second client is started. The obtained second account and login password are logged into the server. The first account and the second account may be third party payment accounts.

The first user sets the second account as the associated account of the first account based on the authentication information of each account, where the authentication information may be the account number and the payment password of the respective accounts of the first user and the second user.

When the first user considers that there is a security risk in the first account, the first account is lost through the loss reporting method of the electronic account involved in any of FIG. 2 to FIG. 4, and the first client is suspended. Now that the security risk of the account is eliminated, and the user wants to unregister the previously lost account, the first user can initiate a request for the first account to be undone to the server through the second client logged in by the second user (step S601), the first user. The first account may be selected in the second client, and then the associated account unmounting request may be initiated, and the account number of the first account and the second account may be carried in the request.

After receiving the request for unpacking the first account, the server then sends an identity information input notification to the second client to notify the first user and the second user to input the identity information (step S602).

The first user and the second user may respectively send the identity information of the respective account to the server through the second client (step S603). Since the previously sent request already includes the respective account number, only the payment password of the respective account may be sent at this time. .

After receiving the payment passwords of the first account and the second account, the server searches for the payment passwords corresponding to the first account and the second account, and then compares the stored payment passwords with the received payment passwords (step S604), if they are consistent, Then, step S605 is performed. If not, step S608 may be selected to be performed.

Step S605: Send an unlock password input notification to the second client to notify the user to provide a password for unpacking.

Step S606: The first user sends a password for unpacking to the server through the second client.

Step S607: After receiving the password for unmounting, the server searches for the unattached passwords corresponding to the first account and the second account, and compares the received passwords for unmounting and the unlocked passwords. If they are consistent, step S608 is performed. If not, you may choose to perform step S609.

Step S608: The server unmounts the first account, and then the first user can re-enable the first client to be enabled.

Step S609: The server sends a loss alarm to the second client device, prompting the second user that the account has a security risk.

In other embodiments, the first user may also unmount the first account that was reported before the first client in the first client device, and may be based on the unchecked verification information that only contains the unattached password. An account is authenticated, and the first account can also be authenticated based on the unpacking information including the unlocked password, the first account, and the second account's identity information.

In addition to the loss and cancellation of the electronic account by setting the authentication information saved when the associated account is set, the scheme of the present specification can also perform other business management such as password modification on the electronic account, which will be described below with reference to FIG. 7 .

Please refer to FIG. 7. FIG. 7 is a flowchart of a method for managing a service of an electronic account according to an exemplary embodiment of the present disclosure. The embodiment can be applied to the server shown in FIG. 1, and may include the following steps S701-S703:

Step S701: Set the second account as the associated account of the first account based on the identity verification information of each account.

Step S702: When receiving the service management request for the first account, perform identity verification on the first account and the second account according to the identity verification information.

Step S703: If the first account and the second account identity pass, the service management for the first account is performed.

The technical content of the step S701 to the step S703 in the embodiment of the present specification corresponds to the technical content of the embodiment corresponding to FIG. 1 to FIG. 6, and details are not described herein again.

In an actual application, the service management request may be a password modification request, a payment request, a loss report, an unmount request, and the like. The password here can be a payment password, a login password or another business password.

In some examples, when the service management request is a report loss request, the service management method of the electronic account in this embodiment may further include:

Generate and store an unattached password for unmounting the first account.

In another example, the service management request is a request for unmounting, and the service management method of the electronic account in this embodiment may further include:

Determining whether the received password is consistent with the unlock password;

When the first account and the second account are authenticated and the received password is consistent with the unlock password, the service management for the first account is performed.

Corresponding to the embodiments of the foregoing methods, the present specification also provides an embodiment of the apparatus.

Referring to FIG. 8, FIG. 8 is a logic block diagram of a report loss reporting device for an electronic account according to an exemplary embodiment of the present disclosure. The device may include an account association module 810, a report loss verification module 820, and an account loss reporting module 830.

The account association module 810 is configured to set the second account as the associated account of the first account based on the identity verification information of each account.

The report loss verification module 820 is configured to perform identity verification on the first account and the second account according to the identity verification information when receiving the request for reporting the loss of the first account.

The account loss reporting module 830 is configured to report the loss of the first account when the first account and the second account are authenticated.

In some examples, the authentication information includes at least one of the following:

The transaction record of the account, the credit score of the account, the environmental information of the account, and the search record of the account.

In other examples, the authentication information includes an identity of the account and a verification password.

As an example, the verification password is consistent with a login password or a payment password of an account corresponding to the verification password.

As an example, the verification password is one of a historical login password of an account corresponding to the verification password, or one of historical payment passwords of an account corresponding to the verification password.

In other examples, the request to report the loss of the first account is issued by the client of the second account.

In other examples, the reporting device of the electronic account of the embodiment may further include:

The unlocking password generating module is configured to generate and store an unattached password for unmounting the first account when the first account is reported for loss.

As an example, the unlock password is a one-time password.

As an example, the reporting device of the electronic account of this embodiment may further include:

The unpacking password sending module is configured to send the unlock password to the client of the second account.

Referring to FIG. 9, FIG. 9 is a logic block diagram of an apparatus for reporting loss reporting of an electronic account according to an exemplary embodiment of the present disclosure. The apparatus may include: an account association module 910, a report loss verification module 920, an account loss reporting module 930, and an unauthentication verification. Module 940 and account unpacking module 950.

The account association module 910 is configured to set the second account as the associated account of the first account based on the identity verification information of each account.

The report loss verification module 920 is configured to perform identity verification on the first account and the second account according to the identity verification information when receiving the request for reporting the loss of the first account.

The account loss reporting module 930 is configured to report the loss of the first account when the first account and the second account are authenticated.

The unpacking verification module 940 is configured to perform identity verification on the first account based on the unchecked verification information when receiving the request for unmounting the first account.

The account unpacking module 950 is configured to unpack the first account when the identity verification of the first account is passed.

In another example, the loss reporting device of the electronic account in this embodiment may further include:

As an example, the unlock password is a one-time password.

As an example, the device for reporting the loss of the electronic account of the embodiment may further include:

As an example, the undo checksum information includes the unlock password.

In other examples, the request to unattach the first account is issued by the client of the second account.

a verification code sending module, configured to send a random verification code to the terminal device bound to the second account when receiving the request for unpacking the first account;

The undo verification information further includes a random verification code returned by the client of the second account.

In another example, the undo verification information includes the authentication information of each account, and the undo verification module further includes:

a dual account verification module, configured to perform identity verification on the first account and the second account respectively according to the authentication information of each account;

The account loss reporting module is further configured to report the first account after the identity verification of the first account and the second account is passed.

In another example, the undoing verification information includes the unlocking password, and the unpacking verification module further includes:

The password verification module is configured to determine whether the received password is consistent with the unlock password;

The identity determining module is configured to determine, when the received password is consistent with the unlock password, that the identity verification of the first account is passed.

Referring to FIG. 10, FIG. 10 is a logic block diagram of a service management apparatus for an electronic account according to an exemplary embodiment of the present specification. The apparatus may include an account association module 1010, a management verification module 1020, and a service management module 1030.

The account association module 1010 is configured to set the second account as the associated account of the first account based on the identity verification information of each account.

The management verification module 1020 is configured to perform identity verification on the first account and the second account according to the identity verification information when receiving a service management request for the first account.

The service management module 1030 is configured to perform service management for the first account when the authentication of the first account and the second account is passed.

In some examples, the business management request is one of the following:

Password modification request, payment request, loss report, and unmount request.

In another example, the service management request is a report loss request, and the service management device of the electronic account in this embodiment may further include:

The unlocking password generating module is configured to generate and store an unlocking password for unmounting the first account.

As an example, the service management request is an unmounting request, and the service management is unattached. The service management device of the electronic account in this embodiment may further include:

The service management module is further configured to perform service management for the first account when the first account and the second account are authenticated and the received password is consistent with the unlocked password.

The implementation process of the functions and functions of each unit (or module) in the above device is specifically described in the implementation process of the corresponding steps in the foregoing method, and details are not described herein again.

For the device embodiment, since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment. The device embodiments described above are merely illustrative, wherein the units or modules described as separate components may or may not be physically separate, and the components displayed as units or modules may or may not be physical units. Or modules, which can be located in one place, or distributed to multiple network units or modules. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present specification. Those of ordinary skill in the art can understand and implement without any creative effort.

Embodiments of the apparatus of the present specification can be applied to a computer device. This can be implemented by a computer chip or an entity, or by a product having a certain function. In a typical implementation, the computer device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a personal digital assistant, a media player, or a combination of any of these devices.

The device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking a software implementation as an example, as a logical means, a processor of a computer device in which it is located reads a corresponding computer program instruction in a readable medium such as a non-volatile memory into a memory. From a hardware level, as shown in FIG. 11, a hardware structure diagram of a computer device in which the device is installed, except for the processor, memory, network interface, and non-volatile memory shown in FIG. The computer device in which the device is located may also include other hardware according to the actual function of the computer device, and details are not described herein.

In one example, the memory of the computer device can store processor executable program instructions; the processor can couple the memory for reading the program instructions stored by the memory and, in response, perform the following operations: authentication based on each account The information sets the second account as the associated account of the first account; upon receiving the request for the loss of the first account, authenticating the first account and the second account according to the identity verification information; if the first account And the second account authentication is passed, the first account is reported for loss.

In another example, the memory of the computer device can store processor executable program instructions; the processor can couple the memory for reading the program instructions stored by the memory and, in response, perform the following operations: based on the identity of each account The verification information sets the second account as the associated account of the first account; when receiving the request for the loss of the first account, the first account and the second account are authenticated according to the identity verification information; If the account and the second account are authenticated, the first account is reported for loss; when the request for the first account is received, the first account is authenticated based on the unchecked verification information, and if the verification is passed, The first account is unlinked.

In another example, the memory of the computer device can store processor executable program instructions; the processor can couple the memory for reading the program instructions stored by the memory and, in response, perform the following operations: based on the identity of each account The verification information sets the second account as the associated account of the first account; upon receiving the service management request for the first account, the first account and the second account are authenticated according to the identity verification information; When one account and the second account are authenticated, the service management for the first account is performed.

In other embodiments, the operations performed by the processor may be referred to the related description in the foregoing method embodiments, and details are not described herein.

The foregoing description of the specific embodiments of the specification has been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the embodiments and still achieve the desired results. In addition, the processes depicted in the figures are not necessarily in a particular order or in a sequential order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The above description is only the preferred embodiment of the present specification, and is not intended to limit the description. Any modifications, equivalent substitutions, improvements, etc., which are included in the present specification, should be included in the present specification. Within the scope of protection.

Claims

A method for reporting loss of an electronic account, comprising the steps of:

Setting the second account as the associated account of the first account based on the authentication information of each account;

Upon receiving the request for loss reporting on the first account, authenticating the first account and the second account according to the identity verification information;

If the first account and the second account are authenticated, the first account is reported for loss.
The method of claim 1, the authentication information comprising at least one of the following:

The transaction record of the account, the credit score of the account, the environmental information of the account, and the search record of the account.
The method of claim 1 wherein the authentication information comprises an identity of the account and a verification password.
The method according to claim 3, wherein the verification password is consistent with a login password or a payment password of an account corresponding to the verification password.
The method according to claim 4, wherein the verification password is one of a historical login password of an account corresponding to the verification password, or one of historical payment passwords of an account corresponding to the verification password.
The method of claim 1 wherein the request to report the loss of the first account is issued by a client of the second account.
The method according to claim 1, wherein when the first account is reported for loss, the method further comprises the following steps:

Generate and store an unattached password for unmounting the first account.
The method of claim 7 further comprising the steps of:

Sending the unlock password to the client of the second account.
The method of claim 7, the unlock password being a one-time password.
A method for reporting loss reporting of an electronic account, comprising the steps of:

Setting the second account as the associated account of the first account based on the authentication information of each account;

Upon receiving the request for loss reporting on the first account, authenticating the first account and the second account according to the identity verification information;

If the first account and the second account are authenticated, the first account is reported for loss;

When receiving the request for unpacking the first account, the first account is authenticated according to the unchecked verification information, and if the identity verification of the first account is passed, the first account is unlinked.
The method of claim 10, the authentication information comprising at least one of the following:

The transaction record of the account, the credit score of the account, the environmental information of the account, and the search record of the account.
The method of claim 10, the authentication information comprising an identity of the account and a verification password.
The method according to claim 12, wherein the verification password is consistent with a login password or a payment password of an account corresponding to the verification password.
The method according to claim 13, wherein the verification password is one of a historical login password of an account corresponding to the verification password, or one of historical payment passwords of an account corresponding to the verification password.
The method of claim 10, wherein the request to report the loss of the first account is issued by a client of the second account.
The method according to claim 10, wherein when the first account is reported for loss, the method further comprises the following steps:

Generate and store an unattached password for unmounting the first account.
The method of claim 16 further comprising the steps of:

Sending the unlock password to the client of the second account.
The method of claim 16 wherein the unlock password is a one-time password.
The method of claim 16 wherein said undoing verification information comprises said unattached password.
The method of claim 10 or 16, wherein the request to unattach the first account is issued by a client of the second account.
The method of claim 20, wherein upon receiving the request to unattach the first account, the method further comprises the steps of:

Sending a random verification code to the terminal device bound to the second account;

The undo verification information further includes a random verification code returned by the client of the second account.
The method according to claim 20, wherein the undo verification information includes identity verification information of each account, and the authenticating the first account according to the undo verification information comprises:

Performing identity verification on the first account and the second account according to the authentication information of each account;

The step of reporting the loss of the first account is performed after the authentication of the first account and the second account is passed.
The method of claim 20, wherein the undoing verification information comprises the unattached password, and the authenticating the first account according to the undoing verification information comprises:

Determining whether the received password is consistent with the unlock password;

If they are consistent, it is determined that the authentication of the first account is passed.
A business management method for an electronic account, comprising the steps of:

Setting the second account as the associated account of the first account based on the authentication information of each account;

And when receiving the service management request for the first account, performing identity verification on the first account and the second account according to the identity verification information;

If the first account and the second account authentication pass, the service management for the first account is performed.
The method of claim 24, wherein the service management request is any of the following:

Password modification request, payment request, loss report, and unmount request.
The method of claim 24, wherein the service management request is a loss report, the method further comprising the steps of:

Generate and store an unattached password for unmounting the first account.
The method according to claim 26, wherein the service management request is an unmounting request, and the service management is unattached, and the method further comprises the following steps:

Determining whether the received password is consistent with the unlock password;

When the first account and the second account are authenticated and the received password is consistent with the unlock password, the service management for the first account is performed.
A loss reporting device for an electronic account, comprising:

An account association module, configured to set a second account as an associated account of the first account based on the identity verification information of each account;

a report of the first account and the second account according to the identity verification information, when the request for loss reporting of the first account is received;

The account loss reporting module is configured to report the first account after the first account and the second account are authenticated.
The apparatus of claim 28, the authentication information comprising at least one of the following:

The transaction record of the account, the credit score of the account, the environmental information of the account, and the search record of the account.
The apparatus of claim 28, the authentication information comprising an identity of the account and a verification password.
The apparatus according to claim 30, wherein the verification password is identical to a login password or a payment password of an account corresponding to the verification password.
The device according to claim 31, wherein the verification password is one of a historical login password of an account corresponding to the verification password, or one of historical payment passwords of an account corresponding to the verification password.
The apparatus of claim 28, the request for loss of the first account is issued by a client of the second account.
The device of claim 28, the device further comprising:

The unlocking password generating module is configured to generate and store an unattached password for unmounting the first account when the first account is reported for loss.
The apparatus of claim 34, wherein the unlock password is a one-time password.
The device of claim 34, the device further comprising:

The unpacking password sending module is configured to send the unlock password to the client of the second account.
A loss reporting device for an electronic account, comprising:

An account association module, configured to set a second account as an associated account of the first account based on the identity verification information of each account;

a report of the first account and the second account according to the identity verification information, when the request for loss reporting of the first account is received;

An account loss reporting module, configured to report the first account after the first account and the second account are authenticated;

The unpacking verification module is configured to perform identity verification on the first account according to the unchecked verification information when receiving the request for unpacking the first account;

The account unplugging module is configured to unmount the first account after the identity verification of the first account is passed.
The apparatus according to claim 37, wherein said authentication information comprises at least one of the following:

The transaction record of the account, the credit score of the account, the environmental information of the account, and the search record of the account.
The apparatus of claim 37, the authentication information comprising an identity of the account and a verification password.
The apparatus according to claim 39, wherein the verification password is identical to a login password or a payment password of an account corresponding to the verification password.
The device according to claim 40, wherein the verification password is one of a historical login password of an account corresponding to the verification password, or one of historical payment passwords of an account corresponding to the verification password.
The apparatus of claim 37, the request for loss of the first account is issued by a client of the second account.
The device of claim 37, the device further comprising:

The unlocking password generating module is configured to generate and store an unattached password for unmounting the first account when the first account is reported for loss.
The apparatus of claim 43, the unlock password is a one-time password.
The apparatus of claim 43 further comprising:

The unpacking password sending module is configured to send the unlock password to the client of the second account.
The apparatus of claim 43, the unpacking verification information comprising the unlock password.
The apparatus of claim 37 or 43, wherein the request to unattach the first account is issued by a client of the second account.
The device of claim 47, the device further comprising:

a verification code sending module, configured to send a random verification code to the terminal device bound to the second account when receiving the request for unpacking the first account;

The undo verification information further includes a random verification code returned by the client of the second account.
The device according to claim 47, wherein the undo verification information includes identity verification information of each account, and the unblocking verification module further includes:

a dual account verification module, configured to perform identity verification on the first account and the second account respectively according to the authentication information of each account;

The account loss reporting module is further configured to report the first account after the identity verification of the first account and the second account is passed.
The device of claim 47, the undoing verification information includes the unattached password, and the unblocking verification module further comprises:

The password verification module is configured to determine whether the received password is consistent with the unlock password;

The identity determining module is configured to determine, when the received password is consistent with the unlock password, that the identity verification of the first account is passed.
A business management device for an electronic account, comprising:

An account association module, configured to set a second account as an associated account of the first account based on the identity verification information of each account;

a management verification module, configured to perform identity verification on the first account and the second account according to the identity verification information when receiving a service management request for the first account;

The service management module is configured to perform service management for the first account if the first account and the second account are authenticated.
The apparatus according to claim 51, wherein said service management request is any of the following:

Password modification request, payment request, loss report, and unmount request.
The device of claim 51, wherein the service management request is a report loss request, the device further comprising:

The unlocking password generating module is configured to generate and store an unlocking password for unmounting the first account.
The device according to claim 53, wherein the service management request is an unmounting request, and the service management is unattached, the device further comprising:

The password verification module is configured to determine whether the received password is consistent with the unlock password;

The service management module is further configured to perform service management for the first account when the first account and the second account are authenticated and the received password is consistent with the unlocked password.
A computer device comprising:

processor;

a memory that stores processor executable instructions;

The processor is coupled to the memory for reading program instructions stored in the memory, and in response, performing the following operations:

Setting the second account as the associated account of the first account based on the authentication information of each account;

Upon receiving the request for loss reporting on the first account, authenticating the first account and the second account according to the identity verification information;

If the first account and the second account are authenticated, the first account is reported for loss.
A computer device comprising:

processor;

a memory that stores processor executable instructions;

The processor is coupled to the memory for reading program instructions stored in the memory, and in response, performing the following operations:

Setting the second account as the associated account of the first account based on the authentication information of each account;

Upon receiving the request for loss reporting on the first account, authenticating the first account and the second account according to the identity verification information;

If the first account and the second account are authenticated, the first account is reported for loss;

When receiving the request for unpacking the first account, the first account is authenticated according to the unchecked verification information, and if the identity verification of the first account is passed, the first account is unlinked.
A computer device comprising:

processor;

a memory that stores processor executable instructions;

The processor is coupled to the memory for reading program instructions stored in the memory, and in response, performing the following operations:

Setting the second account as the associated account of the first account based on the authentication information of each account;

And when receiving the service management request for the first account, performing identity verification on the first account and the second account according to the identity verification information;

If the first account and the second account authentication pass, the service management for the first account is performed.