WO2020020202A1 - 应用程序的账号管理方法、装置、设备和介质 - Google Patents

应用程序的账号管理方法、装置、设备和介质 Download PDF

Info

Publication number
WO2020020202A1
WO2020020202A1 PCT/CN2019/097422 CN2019097422W WO2020020202A1 WO 2020020202 A1 WO2020020202 A1 WO 2020020202A1 CN 2019097422 W CN2019097422 W CN 2019097422W WO 2020020202 A1 WO2020020202 A1 WO 2020020202A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
application
virtual
virtual account
business data
Prior art date
Application number
PCT/CN2019/097422
Other languages
English (en)
French (fr)
Inventor
张煜卿
Original Assignee
北京字节跳动网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京字节跳动网络技术有限公司 filed Critical 北京字节跳动网络技术有限公司
Publication of WO2020020202A1 publication Critical patent/WO2020020202A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management

Definitions

  • Embodiments of the present disclosure relate to Internet data processing technologies, for example, to an account management method, device, device, and medium of an application program.
  • Embodiments of the present disclosure provide an account management method, device, device, and medium for an application program, so as to implement sharing of business data between different application programs.
  • an embodiment of the present disclosure provides an account management method for an application, including:
  • the first application receives an account operation request, and the account operation request carries a second application account;
  • the first application querying whether the second application account has an associated virtual account in the first application
  • the first application end processes the business data of the virtual account in response to the existence of the virtual account associated with the second application account.
  • an embodiment of the present disclosure provides an account management device for an application program, which is configured on a first application end and includes:
  • the request receiving module is configured to receive an account operation request, and the account operation request carries a second application account;
  • the account query module is configured to query whether the second application account has an associated virtual account in the first application end;
  • the data processing module is configured to process service data of the virtual account in response to the virtual account associated with the second application account.
  • an electronic device including:
  • One or more processors are One or more processors;
  • Memory set to store one or more programs
  • the one or more programs are executed by the one or more processors, so that the one or more processors implement an account management method for an application program according to an embodiment of the present disclosure.
  • the embodiment of the present disclosure further provides a computer-readable storage medium.
  • a computer program is stored on the storage medium, and when the computer program is executed by a processor, the application program according to the embodiment of the present disclosure is implemented. Account management methods.
  • FIG. 1 is a flowchart of an account management method for an application provided by Embodiment 1 of the present disclosure
  • FIG. 2 is a flowchart of an account management method for an application provided by Embodiment 2 of the present disclosure
  • FIG. 3 is a flowchart of an account management method for an application provided by Embodiment 3 of the present disclosure
  • FIG. 4 is a flowchart of an account management method for an application according to a fourth embodiment of the present disclosure.
  • FIG. 5 is a flowchart of an account management method for an application provided by Embodiment 5 of the present disclosure
  • FIG. 6 is a schematic structural diagram of an account management device for an application program according to Embodiment 6 of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an electronic device according to a seventh embodiment of the present disclosure.
  • each embodiment provides optional features and examples at the same time.
  • the multiple features described in the embodiments can be combined to form multiple optional solutions.
  • Each numbered embodiment should not be used. Only considered as a technical solution.
  • FIG. 1 is a flowchart of a method for managing an account of an application provided by Embodiment 1 of the present disclosure. This embodiment is applicable to a case where an account of an application is managed when business data is shared between different applications.
  • the method may be executed by an account management device of an application, which may be implemented in software and / or hardware, and may generally be integrated in a terminal device or an electronic device such as an application service platform.
  • the method includes the following steps:
  • Step 110 The first application receives an account operation request, and the account operation request carries a second application account.
  • the first application end may be an application client of the first application installed on the terminal device, or an application service platform capable of providing services to the first application client.
  • the account operation request is a request to perform an operation based on the second application account.
  • the account operation request carries a second application account.
  • the user can perform authorized login on the first application program based on the second application account, can bind the second application account to the first application account, establish a binding relationship, and can also link the second application account with the first application account. The binding relationship between them is released and changed.
  • the first application account is the account of the first application.
  • the second application account is the account of the second application.
  • the user may enter an account operation request on the interface of the application client.
  • the first application is an application service platform that provides services to the first application client
  • the user may enter an account operation request on the interface of the first application client, and the first application client operates the account The request is transmitted to the first application.
  • Step 120 The first application queries whether the second application account has an associated virtual account in the first application.
  • the virtual account is an account created by the application for the user who owns the business data according to the user information of the user corresponding to the business data after obtaining the business data shared by other applications.
  • the user information may include a user name, a user avatar, and the like.
  • the virtual account includes user information and business data space.
  • the business data space is a storage space dedicated to storing a user's business data.
  • the first application terminal After receiving the account operation request, the first application terminal obtains the second application account in the account operation request, queries the second application account in the account operation request, and whether there is an associated virtual account in the first application terminal.
  • the first application terminal obtains the user information corresponding to the second application account according to the second application account, and matches the user information corresponding to the second application account with the user information of the virtual account stored in the database. If the user information corresponding to the second application account matches the user information of the virtual account, it indicates that the second application account in the account operation request has an associated virtual account in the first application; if the user information corresponding to the second application account is The user information of the virtual account does not match, indicating that the second application account in the account operation request does not have an associated virtual account in the first application.
  • Step 130 The first application terminal processes the service data of the virtual account in response to the virtual account associated with the second application account.
  • the business data stored in the business data space of the virtual account is the business data associated with the second application account.
  • Business data for processing In one embodiment, according to the operation performed by the user based on the second application account, the virtual account can be changed to a regular account on the first application side, the business data of the virtual account can be migrated, and the business data of the virtual account can be published. Disable processing, you can also delete the virtual account and the business data corresponding to the virtual account.
  • the service data includes at least one of the following: text, pictures, audio or video posted by the user on the first application end or the second application end, user portraits, and user behavior data.
  • the business data is stored in the business data space of the virtual account, and the real user is simulated, and the business data is published on the first application side.
  • the text is stored in the business data space of the virtual account, and the real user is simulated, and the text is published on the first application to make the first application Of users can browse to the text.
  • the business data of the virtual account in the database need not be processed according to the operation performed by the user based on the second application account.
  • an account operation request is received by the first application terminal, and a second application account in the account operation request is queried. Is there an associated virtual account in the first application terminal? If it is determined that there is a second application account association Virtual account, the business data of the virtual account is processed. When business data is shared between different applications, the account of the application can be managed to provide services based on the user's data sharing historical behavior and improve the user experience.
  • FIG. 2 is a flowchart of a method for managing an account of an application program provided in Embodiment 2 of the present disclosure.
  • the account operation request is an authorized login request to log in to the first application based on the second application account. If there is a virtual account associated with the second application account, processing the business data of the virtual account includes: The virtual account associated with the application account changes the virtual account to a regular account on the first application side.
  • the method includes the following steps:
  • Step 210 The first application receives an account operation request, and the account operation request carries a second application account.
  • the account operation request is an authorized login request to log in to the first application terminal based on the second application account.
  • the user of the second application may choose to log in to the first application through the second application account.
  • Step 220 The first application queries whether the second application account has an associated virtual account in the first application.
  • the first application terminal receives an authorized login request to log in to the first application terminal based on the second application account, obtains the second application account according to the authorized login request, and obtains user information corresponding to the second application account according to the second application account. Match the user information corresponding to the second application account with the user information of the virtual account stored in the database.
  • Step 230 The first application end responds to the existence of a virtual account associated with the second application account, and changes the virtual account to a conventional account of the first application end.
  • changing the virtual account to a regular account of the first application may be to migrate the user information of the virtual account to In the user information storage space of a regular account, or change the tag attribute of the virtual account to a regular account.
  • the user can log in to the first application terminal through the conventional account, browse the business data and operation behavior data related to the business data on the first application terminal, and perform business operations on the first application terminal.
  • Virtual accounts are not the same as regular accounts.
  • a regular account is usually an account registered and used by a user on an application.
  • the virtual account is an account on the application used to manage business data shared by other applications.
  • the regular account includes user information and business data space.
  • User information can be personal information submitted by users.
  • the user information may include a user name, a user avatar, and the like. Users can log in to regular accounts and perform business operations on applications through regular accounts.
  • the business data space of a conventional account is set to store business data generated by a user's business operations.
  • the virtual account includes user information and business data space.
  • the business data space of the virtual account is set to store business data shared by other applications.
  • the user information of the virtual account is user information generated according to the user information corresponding to the user to which the service data belongs.
  • the conventional account of the first application may be an account registered and used by the user on the first application.
  • the conventional account of the first application is the first application account, and the conventional account of the first application may also be the same.
  • the account obtained by changing the virtual account associated with the second application account that is, the account obtained by changing the virtual account associated with the second application account when the registration process is omitted.
  • both the conventional account obtained through registration and the conventional account obtained through modification can be accounts that meet preset requirements (such as registration requirements), that is, conventional accounts can be understood as meeting registration The required account.
  • FIG. 3 is a flowchart of an account management method for an application provided by Embodiment 3 of the present disclosure.
  • the account operation request is an account binding request that binds the first application account and the second application account. If a virtual account associated with the second application account exists, processing the business data of the virtual account includes: : If a virtual account associated with the second application account exists, the first application end binds the virtual account to the first application account, and migrates the business data of the virtual account to the business data space of the first application account.
  • the method includes the following steps:
  • Step 310 The first application receives an account operation request, and the account operation request carries a second application account.
  • the account operation request is an account binding request that binds the first application account and the second application account.
  • Step 320 The first application queries whether the second application account has an associated virtual account in the first application.
  • the first application end receives an account binding request for binding the first application account and the second application account, obtains user information corresponding to the second application account according to the account binding request, and binds the user corresponding to the second application account.
  • the information is matched with the user information of the virtual account stored in the database.
  • Step 330 In response to the virtual account associated with the second application account, the first application end binds the virtual account to the first application account, and migrates the business data of the virtual account to the business data space of the first application account.
  • the first application binds the virtual account to the first application account, and establishes the virtual account and the first application account. Binding relationship, and migrate the business data of the virtual account to the business data space of the first application account, and then bind the first application account and the second application account.
  • the first application binds the virtual account to the first application account, which can be understood as the first
  • the application side binds the virtual account to the first application account corresponding to the virtual account.
  • the business data of the virtual account in the database need not be processed according to the user's operation based on the second application account, and the first application account and the second application account are directly processed. Binding.
  • the first application Whether there is an associated virtual account in the client, if there is a virtual account associated with the second application account, bind the virtual account to the first application account, and migrate the business data of the virtual account to the business data space of the first application account.
  • FIG. 4 is a flowchart of an account management method for an application program according to Embodiment 4 of the present disclosure.
  • the account operation request is an account unbinding request to unbind the first application account from the second application account. If there is a virtual account associated with the second application account, the business data of the virtual account is processed. Including: if there is a virtual account associated with the second application account, the first application end disables the publishing function of the business data of the virtual account, or deletes the virtual account and the business data corresponding to the virtual account.
  • the method includes the following steps:
  • Step 410 The first application receives an account operation request, and the account operation request carries a second application account.
  • the account operation request is an account unbinding request that unbinds the first application account from the second application account.
  • Step 420 The first application queries whether the second application account has an associated virtual account in the first application.
  • the first application end receives an account unbinding request for unbinding the first application account from the second application account, obtains user information corresponding to the second application account according to the account unbinding request, and assigns the second application account corresponding to The user information is matched with the user information of the virtual account stored in the database.
  • Step 430 The first application end, in response to the existence of the virtual account associated with the second application account, disables the publishing function of the business data of the virtual account, or deletes the virtual account and the business data corresponding to the virtual account.
  • the first application side disables the publishing function of the business data of the virtual account and releases the binding relationship between the first application account and the second application account. After the publishing function is disabled, the first application no longer simulates a real user and publishes business data of a virtual account. Alternatively, the first application side deletes the virtual account and its corresponding service data, and releases the binding relationship between the first application account and the second application account.
  • the business data of the virtual account in the database need not be processed according to the operation performed by the user based on the second application account, and the first application account and the second application account are directly released. Binding relationship.
  • the account operation request is an account unbinding request that unbinds the first application account from the second application account
  • the second application account in the account operation request is queried. Whether there is an associated virtual account in the application. If there is a virtual account associated with the second application account, the first application will disable the publishing function of the virtual account's business data, or delete the virtual account and the business data corresponding to the virtual account.
  • the account unbinding service is provided for the user according to the user's data sharing historical behavior, thereby improving the user experience.
  • FIG. 5 is a flowchart of an account management method for an application provided by Embodiment 5 of the present disclosure. This embodiment may be combined with the optional solutions in the foregoing embodiments.
  • the account operation request is an account binding replacement request that binds and replaces the first application account with two second application accounts. If there is a virtual account associated with the second application account, the service for the virtual account is performed.
  • the data processing includes: if a virtual account associated with the second application account exists, the first application side adjusts the binding relationship between the virtual account corresponding to each of the two second application accounts and the first application account, and binds the adjusted account
  • the business data of the virtual account corresponding to the second application account is migrated to the business data space of the first application account, and the publishing function of the business data of the virtual account corresponding to the unbound second application account is disabled or the virtual account is deleted. And business data corresponding to the virtual account.
  • the method includes the following steps:
  • Step 510 The first application receives an account operation request, and the account operation request carries a second application account.
  • the account operation request is an account binding replacement request that binds and replaces the first application account with two second application accounts. That is, requesting to unbind the first application account from the second application account to be unbound from the two second application accounts, and to establish the binding between the first application account and the second application account to be bound relationship.
  • Step 520 The first application queries whether the second application account has an associated virtual account in the first application.
  • the first application end receives an account binding replacement request that binds and replaces the first application account with two second application accounts, obtains user information corresponding to the two second application accounts according to the account binding replacement request, and The user information corresponding to the two second application accounts is respectively matched with the user information of the virtual account stored in the database.
  • Step 530 In response to the existence of the virtual account associated with the second application account, the first application adjusts the binding relationship between the virtual account corresponding to each of the two second application accounts and the first application account respectively, and adjusts the bound first
  • the business data of the virtual account corresponding to the second application account is migrated to the business data space of the first application account, and the release of the business data of the virtual account corresponding to the unbound second application account is disabled, or the virtual account and the virtual account are deleted.
  • the binding relationship between the first application account and the second application account to be unbound from the two second application accounts is released, and Publishing service data of the virtual account corresponding to the second application account to disable the publishing function or delete the virtual account and its corresponding business data; and establishing a binding relationship between the first application account and another second application account to be bound, The business data of the virtual account corresponding to the bound second application account is migrated to the business data space of the first application account.
  • the first application account and the two second application accounts to be unbound are unbound.
  • the binding relationship of the determined second application account disabling the publishing function for the business data of the virtual account corresponding to the second application account after unbinding, or deleting the virtual account and its corresponding business data; and directly establishing the first A binding relationship between an application account and another second application account to be bound.
  • the unbound second application account does not have an associated virtual account, and another unused second application account has an associated virtual account, the first application account and the two second application accounts to be unreleased are directly released.
  • a binding relationship between the bound second application account; and establishing a binding relationship between the first application account and another second application account to be bound, and migrating business data of the virtual account corresponding to the bound second application account To the business data space of the first application account.
  • the binding relationship between the first application account and the second application account to be unbound from the two second application accounts is directly released, and the first application is established.
  • the binding relationship between the account and another second application account to be bound is directly released, and the first application is established.
  • the first application adjusts the binding relationship between the virtual account corresponding to each of the two second application accounts and the first application account, and The business data of the virtual account corresponding to the second application account bound after the adjustment is migrated to the business data space of the first application account, and the publishing function of the virtual data corresponding to the unbound second application account is disabled or disabled.
  • FIG. 6 is a schematic structural diagram of an account management apparatus for an application provided in Embodiment 6 of the present disclosure. This embodiment is applicable to a case where an account of an application is managed when business data is shared between different applications.
  • the device may be implemented in a software and / or hardware manner, and may generally be integrated in a terminal device or an electronic device such as an application service platform. As shown in FIG. 6, the device includes a request receiving module 601, an account query module 602, and a data processing module 603.
  • the request receiving module 601 is configured to receive an account operation request, and the account operation request carries a second application account;
  • the account query module 602 is configured to query whether the second application account has an associated virtual account in the first application;
  • data The processing module 603 is configured to process service data of the virtual account if an associated virtual account exists.
  • an account operation request is received by the first application terminal, and a second application account in the account operation request is queried. Is there an associated virtual account in the first application terminal? If it is determined that there is a second application account association Virtual account, the business data of the virtual account is processed. When business data is shared between different applications, the account of the application can be managed to provide services based on the user's data sharing historical behavior and improve the user experience.
  • the account operation request is an authorized login request to log in to the first application based on the second application account
  • the data processing module 603 includes:
  • the account change module is configured to change the virtual account to a regular account on the first application side if a virtual account associated with the second application account exists.
  • the account operation request is an account binding request that binds the first application account and the second application account
  • the data processing module 603 is set to:
  • the virtual account is bound to the first application account, and the business data of the virtual account is migrated to the business data space of the first application account.
  • the account operation request is an account unbinding request that unbinds the first application account from the second application account
  • the data processing module 603 is configured to:
  • the publishing function is disabled for the business data of the virtual account, or the virtual account and the business data corresponding to the virtual account are deleted.
  • the account operation request is an account binding replacement request that binds and replaces the first application account with two second application accounts
  • the data processing module 603 is set for:
  • the business data of the first application account is migrated to the business data space of the first application account, and the publishing function of the virtual account corresponding to the unbound second application account is disabled for processing or the virtual account and its corresponding business data are deleted.
  • the business data includes at least one of the following: text, pictures, audio or video posted by the user on the first or second application end, user portraits, and User behavior data.
  • the account management device for an application provided in an embodiment of the present disclosure can execute the account management method for an application provided in any embodiment of the present disclosure, and has function modules and effects corresponding to the execution method.
  • FIG. 7 is a schematic structural diagram of an electronic device according to a seventh embodiment of the present disclosure.
  • FIG. 7 illustrates a block diagram of an exemplary electronic device 712 suitable for use in implementing embodiments of the present disclosure.
  • the electronic device 712 shown in Fig. 7 is only an example.
  • the electronic device 712 is expressed in the form of a general-purpose computing device.
  • the components of the electronic device 712 may include one or more processors or processing units 716, a system memory 728, and a bus 718 connecting different system components (including the system memory 728 and the processing unit 716).
  • the bus 718 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local area bus using any of a variety of bus structures.
  • these architectures include the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MCA) bus, the enhanced ISA bus, and the Video Electronics Standards Association (VESA) Local area bus and Peripheral Component Interconnect (PCI) bus.
  • the electronic device 712 includes a variety of computer system-readable media. These media can be a variety of available media that can be accessed by the electronic device 712, including volatile and non-volatile media, removable and non-removable media.
  • the system memory 728 may include a computer system readable medium in the form of volatile memory, such as Random Access Memory (RAM) 730 and / or cache 732.
  • RAM Random Access Memory
  • the electronic device 712 may include other removable / non-removable, volatile / nonvolatile computer system storage media.
  • the storage system 734 may be configured to read and write non-removable, non-volatile magnetic media (not shown in FIG. 7, commonly referred to as a “hard drive”).
  • FIG. 7 non-removable, non-volatile magnetic media
  • each drive may be connected to the bus 718 through one or more data medium interfaces.
  • the memory 728 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of one or more embodiments of the present disclosure.
  • a program / utility tool 740 having a set (at least one) of program modules 742 may be stored in, for example, the memory 728.
  • a program module 742 includes an operating system, one or more application programs, other program modules, and program data. These examples Each or some combination may include an implementation of the network environment.
  • the program module 742 generally performs functions and / or methods in the embodiments described in the present disclosure.
  • the electronic device 712 may also communicate with one or more external devices 714 (such as a keyboard, pointing device, display 724, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 712, and / or with A device (eg, a network card, modem, etc.) that enables the electronic device 712 to communicate with one or more other computing devices.
  • This communication can be performed through an input / output (I / O) interface 722.
  • the electronic device 712 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 720.
  • networks such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet
  • the network adapter 720 communicates with other modules of the electronic device 712 through the bus 718. It should be understood that although not shown in FIG. 7, other hardware and / or software modules may be used in conjunction with the electronic device 712, including: microcode, device drivers, redundant processing units, external disk drive arrays, and disk arrays (Redundant Arrays of Independent). Drives (RAID) systems, tape drives, and data backup storage systems.
  • RAID Redundant Arrays of Independent
  • the processing unit 716 executes a variety of functional applications and data processing by running a program stored in the system memory 728, for example, implementing an account management method for an application provided by an embodiment of the present disclosure.
  • the method may include: the first application receives an account operation request, and the account operation request carries a second application account; the first application queries whether the second application account has an associated virtual account in the first application; if there is a second The virtual account associated with the application account processes the business data of the virtual account.
  • the eighth embodiment of the present disclosure also provides a computer-readable storage medium on which a computer program is stored.
  • the account management method for an application program provided by the embodiment of the present disclosure is implemented.
  • the method It may include: the first application receives an account operation request, and the account operation request carries a second application account; the first application queries whether the second application account has an associated virtual account in the first application; if a second application account exists The associated virtual account processes the business data of the virtual account.
  • the computer storage medium of the embodiment of the present disclosure may adopt a combination of one or more computer-readable media.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • the computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, RAM, read-only memory (ROM), Erasable Programmable ROM (EPROM) or flash memory, optical fiber, CD-ROM, optical storage device, magnetic storage device, or a suitable combination of the above.
  • a computer-readable storage medium may be a tangible medium that contains or stores a program that can be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable signal medium may include a data signal in baseband or propagated as part of a carrier wave, which carries a computer-readable program code. This transmitted data signal may take a variety of forms, including electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be a computer-readable medium other than a computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.
  • the program code contained on the computer-readable medium may be transmitted using an appropriate medium, including wireless, wire, optical cable, radio frequency (RF), or the like, or a suitable combination of the foregoing.
  • RF radio frequency
  • Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including programming languages such as Java, Smalltalk, C ++, Ruby, Go, It also includes regular procedural programming languages—such as "C" or similar programming languages.
  • the program code can be executed entirely on the user's computer, partly on the user's computer, as an independent software package, partly on the user's computer, partly on a remote computer, or entirely on a remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network, including a LAN or WAN, or it can be connected to an external computer (for example, through an Internet connection using an Internet service provider).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本文公开了一种应用程序的账号管理方法、装置、设备和介质。其中，该方法包括：第一应用端接收账号操作请求，该账号操作请求携带第二应用账号；第一应用端查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号；如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理。

Description

应用程序的账号管理方法、装置、设备和介质
本申请要求在2018年7月27日提交中国专利局、申请号为201810846824.9的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开实施例涉及互联网数据处理技术，例如涉及一种应用程序的账号管理方法、装置、设备和介质。
背景技术
随着互联网和智能终端的发展，应用程序(Application，APP)增多，当一个应用程序新推出时，例如以社交为主的应用程序，会因为用户数量少、用户分享信息少而使得应用程序的使用体验不佳，由此又导致用户更不容易聚集，恶性循环。
受限于应用程序各自的用户管理规则以及隐私性要求，使得应用程序的用户数据和业务数据之间难以实现共享。
发明内容
本公开实施例提供一种应用程序的账号管理方法、装置、设备和介质，以实现业务数据在不同应用程序之间的共享。
在一实施例中，本公开实施例提供了一种应用程序的账号管理方法，包括：
第一应用端接收账号操作请求，该账号操作请求携带第二应用账号；
第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号；
第一应用端响应于存在所述第二应用账号关联的虚拟账号，对虚拟账号的业务数据进行处理。
在一实施例中，本公开实施例提供了一种应用程序的账号管理装置，配置于第一应用端，包括：
请求接收模块，设置为接收账号操作请求，该账号操作请求携带第二应用 账号；
账号查询模块，设置为查询第二应用账号在第一应用端中是否存在关联的虚拟账号；
数据处理模块，设置为响应于存在所述第二应用账号关联的虚拟账号，对虚拟账号的业务数据进行处理。
在一实施例中，本公开实施例提供了一种电子设备，包括：
一个或多个处理器；
存储器，设置为存储一个或多个程序；
所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本公开实施例所述的应用程序的账号管理方法。
在一实施例中，本公开实施例还提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，该计算机程序被处理器执行时实现如本公开实施例所述的应用程序的账号管理方法。
附图说明
图1为本公开实施例一提供的一种应用程序的账号管理方法的流程图；
图2为本公开实施例二提供的一种应用程序的账号管理方法的流程图；
图3为本公开实施例三提供的一种应用程序的账号管理方法的流程图；
图4为本公开实施例四提供的一种应用程序的账号管理方法的流程图；
图5为本公开实施例五提供的一种应用程序的账号管理方法的流程图；
图6为本公开实施例六提供的一种应用程序的账号管理装置的结构示意图；
图7为本公开实施例七提供的一种电子设备的结构示意图。
具体实施方式
下面结合附图和实施例对本公开进行说明。此处所描述的具体实施例仅仅用于解释本公开，而非对本公开的限定。
为了便于描述，附图中仅示出了与本公开相关的部分而非全部结构。在更 加详细地讨论示例性实施例之前应当提到的是，一些示例性实施例被描述成作为流程图描绘的处理或方法。虽然流程图将多项操作(或步骤)描述成顺序的处理，但是其中的许多操作可以被并行地、并发地或者同时实施。此外，一项或多项操作的顺序可以被重新安排。当其操作完成时所述处理可以被终止，但是还可以具有未包括在附图中的附加步骤。所述处理可以对应于方法、函数、规程、子例程、子程序等等。
下述多个实施例中，每个实施例中同时提供了可选特征和示例，实施例中记载的多个特征可进行组合，形成多个可选方案，不应将每个编号的实施例仅视为一个技术方案。
针对不同应用程序之间共享业务数据的需求，为了兼顾应用程序的用户管理规则以及隐私性要求，可以尝试为应用程序创建一些非用户控制的站外账号，也可以视为虚拟账号，即这些站外账号并不是真实登录该应用程序的用户，而是登录其他应用程序的用户。新应用程序可以在权限控制下借用其他应用程序中用户的部分信息。并在新应用程序中模拟真实用户的存在而发布一些业务数据、推送一些广告等。但是，上述方案也存在一些弊端，打破了业务数据与用户账号的对应关系，不利于持续性发展。例如，随着新应用程序的推广，可能出现在其他应用程序真实存在的该用户，会授权登录或直接登录到新应用程序的情况，此时若按照正常登录程序，则需要为用户创建新的账号，存储用户数据。但是这样操作，该用户无法了解以往发布的业务数据，或者无法根据历史行为得到一些服务，显然用户体验不佳，上述方案在应用程序的不同推广阶段不具有无缝衔接的连续性。
实施例一
图1为本公开实施例一提供的一种应用程序的账号管理方法的流程图，本实施例可适用于在不同应用程序之间共享业务数据时，对应用程序的账号进行管理的情况，该方法可以由应用程序的账号管理装置来执行，该装置可以采用软件和/或硬件的方式实现，一般可集成在终端设备或诸如应用程序服务平台等电子设备中。该方法包括如下步骤：
步骤110、第一应用端接收账号操作请求，该账号操作请求携带第二应用账号。
其中，第一应用端可以是安装于终端设备上的第一应用程序的应用程序客户端，或者是能够向第一应用程序客户端提供服务的应用程序服务平台。
账号操作请求是基于第二应用账号进行操作的请求。该账号操作请求携带第二应用账号。用户可以基于第二应用账号在第一应用程序上进行授权登录，可以将第二应用账号与第一应用账号进行绑定，建立绑定关系，还可以对第二应用账号与第一应用账号之间的绑定关系进行解除和变更。第一应用账号即为第一应用程序的账号。第二应用账号即为第二应用程序的账号。
当第一应用端为第一应用程序的应用程序客户端时，用户可以在应用程序客户端的界面上输入账号操作请求。或者当第一应用端为向第一应用程序客户端提供服务的应用程序服务平台时，用户可以在第一应用程序客户端的界面上输入账号操作请求，然后由第一应用程序客户端将账号操作请求传输至第一应用端。
步骤120、第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号。
其中，虚拟账号为应用程序获取其他应用程序共享的业务数据后，根据业务数据对应用户的用户信息，为业务数据的所属用户建立的账号。用户信息可以包括用户名称、用户头像等。虚拟账号包括用户信息和业务数据空间。业务数据空间是专用于存储用户的业务数据的存储空间。建立虚拟账号时，将用户信息赋值作为虚拟账号的用户信息，将业务数据存储至虚拟账号的业务数据空间中。
第一应用端接收账号操作请求后，获取账号操作请求中的第二应用账号，查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号。在一实施例中，第一应用端根据第二应用账号获取第二应用账号对应的用户信息，并将第二应用账号对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。如果第二应用账号对应的用户信息与虚拟账号的用户信息匹配，表明账号操作请求中的第二应用账号，在第一应用端中存在关联的虚拟账号；如果第二应用账号对应的用户信息与虚拟账号的用户信息不匹配，表明账号操作请求中的第二应用账号，在第一应用端中不存在关联的虚拟账号。
步骤130、第一应用端响应于存在第二应用账号关联的虚拟账号，对虚拟账 号的业务数据进行处理。
其中，如果存在第二应用账号关联的虚拟账号，则虚拟账号的业务数据空间存储的业务数据为与第二应用账号关联的业务数据，根据用户基于第二应用账号进行的操作，对虚拟账号的业务数据进行处理。在一实施例中，根据用户基于第二应用账号进行的操作，可以将虚拟账号变更为第一应用端的常规账号，可以对虚拟账号的业务数据进行迁移，可以对虚拟账号的业务数据进行发布功能禁用处理，还可以删除虚拟账号及该虚拟账号对应的业务数据。
可选的，业务数据包括下述至少一项：用户在第一应用端或第二应用端发布的文字、图片、音频或视频，用户画像，以及用户行为数据。
其中，第一应用程序获取第二应用程序共享的业务数据后，将业务数据存储至虚拟账号的业务数据空间中，还会模拟真实用户，在第一应用端发布业务数据。例如，第一应用程序获取用户在第二应用端发布的文字后，将文字存储至虚拟账号的业务数据空间中，并模拟真实用户，在第一应用端发布该文字，以使第一应用程序的用户可以浏览到该文字。
如果不存在关联的虚拟账号，则不需要根据用户基于第二应用账号进行的操作，对数据库中的虚拟账号的业务数据进行处理。
本实施例的技术方案，通过第一应用端接收账号操作请求，并查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果确定存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理，可以在不同应用程序之间共享业务数据时，对应用程序的账号进行管理，实现根据用户的数据共享历史行为提供服务，提高用户体验。
实施例二
图2为本公开实施例二提供的一种应用程序的账号管理方法的流程图。本实施例可以与上述实施例中的可选方案相互结合。在本实施例中，账号操作请求为基于第二应用账号登录第一应用端的授权登录请求，如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理包括：如果存在第二应用账号关联的虚拟账号，则将虚拟账号变更为第一应用端的常规账号。
如图2所示，该方法包括如下步骤：
步骤210、第一应用端接收账号操作请求，该账号操作请求携带第二应用账号。
其中，账号操作请求为基于第二应用账号登录第一应用端的授权登录请求。第二应用程序的用户可以选择通过第二应用账号登录第一应用端。
步骤220、第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号。
其中，第一应用端接收基于第二应用账号登录第一应用端的授权登录请求，根据授权登录请求获取第二应用账号，并根据第二应用账号获取第二应用账号对应的用户信息。将第二应用账号对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。
步骤230、第一应用端响应于存在第二应用账号关联的虚拟账号，将虚拟账号变更为第一应用端的常规账号。
其中，如果账号操作请求中的第二应用账号，在第一应用端中存在关联的虚拟账号，则将虚拟账号变更为第一应用程序的常规账号，可以是将虚拟账号的用户信息，迁移至常规账号的用户信息存储空间中，或者将虚拟账号的标签属性变更为常规账号。用户可以通过该常规账号登录第一应用端，在第一应用端浏览业务数据以及与业务数据相关的操作行为数据，并在第一应用端上进行业务操作。
虚拟账号与常规账号并不相同。常规账号通常为用户在应用程序上注册并使用的账号。而虚拟账号为应用程序上用于管理其他应用程序共享的业务数据的账号。常规账号包括用户信息和业务数据空间。用户信息可以为用户提交的个人信息。用户信息可以包括用户名称、用户头像等。用户可以登录常规账号，并通过常规账号在应用程序上进行业务操作。常规账号的业务数据空间设置为存储用户进行业务操作所产生的业务数据。虚拟账号包括用户信息和业务数据空间。虚拟账号的业务数据空间设置为存储其他应用程序共享的业务数据。虚拟账号的用户信息为根据业务数据的所属用户对应的用户信息生成的用户信息。
在一实施例中，第一应用端的常规账号可以为用户在第一应用程序上注册 并使用的账号，例如第一应用端的常规账号为第一应用账号，第一应用端的常规账号也可以为对与第二应用账号关联的虚拟账号进行变更得到的账号，即在省略了注册程序的情况下，通过对与第二应用账号关联的虚拟账号进行变更得到的账号。本领域技术人员可以理解的是，无论是注册得到的常规账号，还是变更得到的常规账号，可以均是符合预设要求(例如注册要求)的账号，也就是说，常规账号可以理解为符合注册要求的账号。
如果不存在第二应用账号关联的虚拟账号，则不需要根据用户基于第二应用账号进行的操作，对数据库中的虚拟账号的业务数据进行处理，直接根据用户基于第二应用账号登录第一应用端的授权登录请求，进行登录。
本实施例的技术方案，通过在账号操作请求为基于第二应用账号登录第一应用端的授权登录请求的情况下，查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果存在第二应用账号关联的虚拟账号，则将虚拟账号变更为第一应用端的常规账号，可以在不同应用程序之间进行授权登录时，根据用户的数据共享历史行为提供服务，提高用户体验。
实施例三
图3为本公开实施例三提供的一种应用程序的账号管理方法的流程图。本实施例可以与上述实施例中的可选方案相互结合。在本实施例中，账号操作请求为将第一应用账号与第二应用账号进行绑定的账号绑定请求，如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理包括：如果存在第二应用账号关联的虚拟账号，则第一应用端将虚拟账号与第一应用账号进行绑定，并将虚拟账号的业务数据迁移至第一应用账号的业务数据空间。
如图3所示，该方法包括如下步骤：
步骤310、第一应用端接收账号操作请求，该账号操作请求携带第二应用账号。
其中，账号操作请求为将第一应用账号与第二应用账号进行绑定的账号绑定请求。
步骤320、第一应用端查询第二应用账号在第一应用端中是否存在关联的虚 拟账号。
其中，第一应用端接收将第一应用账号与第二应用账号进行绑定的账号绑定请求，根据账号绑定请求获取第二应用账号对应的用户信息，并将第二应用账号对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。
步骤330、第一应用端响应于存在第二应用账号关联的虚拟账号，将虚拟账号与第一应用账号进行绑定，并将虚拟账号的业务数据迁移至第一应用账号的业务数据空间。
其中，如果账号操作请求中的第二应用账号，在第一应用端中存在关联的虚拟账号，则第一应用端将虚拟账号与第一应用账号进行绑定，建立虚拟账号与第一应用账号的绑定关系，并将虚拟账号的业务数据迁移至第一应用账号的业务数据空间，然后将第一应用账号与第二应用账号进行绑定。在一实施例中，虚拟账号和第一应用账号之间存在对应关系，不同的虚拟账号可以对应不同的第一应用账号，例如，虚拟账号A和第一应用账号A之间存在对应关系，虚拟账号B和第一应用账号B之间存在对应关系。也就是说，如果账号操作请求中的第二应用账号，在第一应用端中存在关联的虚拟账号，则第一应用端将虚拟账号与第一应用账号进行绑定，可以理解为，第一应用端将虚拟账号和与该虚拟账号对应的第一应用账号进行绑定。
如果不存在第二应用账号关联的虚拟账号，则不需要根据用户基于第二应用账号进行的操作，对数据库中的虚拟账号的业务数据进行处理，直接将第一应用账号与第二应用账号进行绑定。
本实施例的技术方案，通过在账号操作请求为将第一应用账号与第二应用账号进行绑定的账号绑定请求的情况下，查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果存在第二应用账号关联的虚拟账号，则将虚拟账号与第一应用账号进行绑定，并将虚拟账号的业务数据迁移至第一应用账号的业务数据空间，可以在不同应用程序的账号之间建立绑定关系时，根据用户的数据共享历史行为提供服务，提高用户体验。
实施例四
图4为本公开实施例四提供的一种应用程序的账号管理方法的流程图。本实施例可以与上述实施例中的可选方案相互结合。在本实施例中，账号操作请求为将第一应用账号与第二应用账号进行绑定解除的账号解绑请求，如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理包括：如果存在第二应用账号关联的虚拟账号，则第一应用端对虚拟账号的业务数据进行发布功能禁用处理，或删除虚拟账号及该虚拟账号对应的业务数据。
如图4所示，该方法包括如下步骤：
步骤410、第一应用端接收账号操作请求，该账号操作请求携带第二应用账号。
其中，账号操作请求为将第一应用账号与第二应用账号进行绑定解除的账号解绑请求。
步骤420、第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号。
其中，第一应用端接收将第一应用账号与第二应用账号进行绑定解除的账号解绑请求，根据账号解绑请求获取第二应用账号对应的用户信息，并将第二应用账号对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。
步骤430、第一应用端响应于存在第二应用账号关联的虚拟账号，对虚拟账号的业务数据进行发布功能禁用处理，或删除虚拟账号及该虚拟账号对应的业务数据。
其中，如果存在关联的虚拟账号，则第一应用端对虚拟账号的业务数据进行发布功能禁用处理，并解除第一应用账号与第二应用账号之间的绑定关系。进行发布功能禁用处理后，第一应用端不再模拟真实用户，发布虚拟账号的业务数据。或者，第一应用端删除虚拟账号及其对应的业务数据，并解除第一应用账号与第二应用账号之间的绑定关系。
如果不存在第二应用账号关联的虚拟账号，则不需要根据用户基于第二应用账号进行的操作，对数据库中的虚拟账号的业务数据进行处理，直接解除第一应用账号与第二应用账号之间的绑定关系。
本实施例的技术方案，通过在账号操作请求为将第一应用账号与第二应用 账号进行绑定解除的账号解绑请求的情况下，查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果存在第二应用账号关联的虚拟账号，则第一应用端对虚拟账号的业务数据进行发布功能禁用处理，或删除虚拟账号及该虚拟账号对应的业务数据，可以在不同应用程序的账号之间解除绑定关系时，根据用户的数据共享历史行为为用户提供账号解除绑定服务，提高用户体验。
实施例五
图5为本公开实施例五提供的一种应用程序的账号管理方法的流程图。本实施例可以与上述实施例为中的可选方案相互结合。在本实施例中，账号操作请求为将第一应用账号与两个第二应用账号进行绑定更换的账号绑定更换请求，如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理包括：如果存在第二应用账号关联的虚拟账号，则第一应用端调整两个第二应用账号各自对应的虚拟账号分别与第一应用账号的绑定关系，并将调整后绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间，并对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号以及该虚拟账号对应的业务数据。
如图5所示，该方法包括如下步骤：
步骤510、第一应用端接收账号操作请求，该账号操作请求携带第二应用账号。
其中，账号操作请求为将第一应用账号与两个第二应用账号进行绑定更换的账号绑定更换请求。即请求解除第一应用账号与两个第二应用账号中的待解除绑定的第二应用账号的绑定关系，并建立第一应用账号与另一个待绑定的第二应用账号的绑定关系。
步骤520、第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号。
其中，第一应用端接收将第一应用账号与两个第二应用账号进行绑定更换的账号绑定更换请求，根据账号绑定更换请求获取两个第二应用账号对应的用 户信息，并将两个第二应用账号对应的用户信息分别与数据库中存储的虚拟账号的用户信息进行匹配。
步骤530、第一应用端响应于存在第二应用账号关联的虚拟账号，调整两个第二应用账号各自对应的虚拟账号分别与第一应用账号的绑定关系，并将调整后绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间，并对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号及该虚拟账号对应的业务数据。
其中，如果两个第二应用账号都存在关联的虚拟账号，则解除第一应用账号与两个第二应用账号中的待解除绑定的第二应用账号的绑定关系，对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号及其对应的业务数据；并建立第一应用账号与另一个待绑定的第二应用账号的绑定关系，将绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间。
如果解除绑定的第二应用账号存在关联的虚拟账号，另一个待绑定的第二应用账号不存在关联的虚拟账号，则解除第一应用账号与两个第二应用账号中的待解除绑定的第二应用账号的绑定关系，对解除绑定后的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号及其对应的业务数据；并直接建立第一应用账号与另一个待绑定的第二应用账号的绑定关系。
如果解除绑定的第二应用账号不存在关联的虚拟账号，另一个待绑定的第二应用账号存在关联的虚拟账号，则直接解除第一应用账号与两个第二应用账号中的待解除绑定的第二应用账号的绑定关系；并建立第一应用账号与另一个待绑定的第二应用账号的绑定关系，将绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间。
如果两个第二应用账号都不存在关联的虚拟账号，则直接解除第一应用账号与两个第二应用账号中的待解除绑定的第二应用账号的绑定关系，并建立第一应用账号与另一个待绑定的第二应用账号的绑定关系。
本实施例的技术方案，通过在账号操作请求为将第一应用账号与两个第二应用账号进行绑定更换的账号绑定更换请求的情况下，查询账号操作请求中的 第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果存在关联的虚拟账号，则第一应用端调整两个第二应用账号各自对应的虚拟账号分别与第一应用账号的绑定关系，并将调整后绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间，并对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号及该虚拟账号对应的数据，可以在不同应用程序的账号之间调整绑定关系时，根据用户的数据共享历史行为提供服务，提高用户体验。
实施例六
图6为本公开实施例六提供的一种应用程序的账号管理装置的结构示意图，本实施例可适用于在不同应用程序之间共享业务数据时，对应用程序的账号进行管理的情况。该装置可以采用软件和/或硬件的方式实现，一般可集成在终端设备或诸如应用程序服务平台等电子设备中。如图6所示，该装置包括：请求接收模块601、账号查询模块602和数据处理模块603。
其中，请求接收模块601，设置为接收账号操作请求，该账号操作请求携带第二应用账号；账号查询模块602，设置为查询第二应用账号在第一应用端中是否存在关联的虚拟账号；数据处理模块603，设置为如果存在关联的虚拟账号，则对虚拟账号的业务数据进行处理。
本实施例的技术方案，通过第一应用端接收账号操作请求，并查询账号操作请求中的第二应用账号，在第一应用端中是否存在关联的虚拟账号，如果确定存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理，可以在不同应用程序之间共享业务数据时，对应用程序的账号进行管理，实现根据用户的数据共享历史行为提供服务，提高用户体验。
可选的，在上述技术方案中可选方案的基础上，账号操作请求为基于第二应用账号登录第一应用端的授权登录请求，则数据处理模块603包括：
账号变更模块，设置为如果存在第二应用账号关联的虚拟账号，则将虚拟账号变更为第一应用端的常规账号。
可选的，在上述技术方案中可选方案的基础上，账号操作请求为将第一应用账号与第二应用账号进行绑定的账号绑定请求，则数据处理模块603是设置为：
如果存在第二应用账号关联的虚拟账号，则将虚拟账号与第一应用账号进行绑定，并将虚拟账号的业务数据迁移至第一应用账号的业务数据空间。
可选的，在上述技术方案中可选方案的基础上，账号操作请求为将第一应用账号与第二应用账号进行绑定解除的账号解绑请求，则数据处理模块603是设置为：
如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行发布功能禁用处理，或删除虚拟账号及该虚拟账号对应的业务数据。
可选的，在上述技术方案中可选方案的基础上，账号操作请求为将第一应用账号与两个第二应用账号进行绑定更换的账号绑定更换请求，则数据处理模块603是设置为：
如果存在第二应用账号关联的虚拟账号，则调整两个第二应用账号各自对应的虚拟账号分别与第一应用账号的绑定关系，并将调整后绑定的第二应用账号对应的虚拟账号的业务数据迁移至第一应用账号的业务数据空间，并对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除该虚拟账号及其对应的业务数据。
可选的，在上述技术方案中可选方案的基础上，业务数据包括下述至少一项：用户在第一应用端或第二应用端发布的文字、图片、音频或视频，用户画像，以及用户行为数据。
在一实施例中，虚拟账号和第一应用账号之间存在对应关系。
本公开实施例所提供的应用程序的账号管理装置可执行本公开任意实施例所提供的应用程序的账号管理方法，具备执行方法相应的功能模块和效果。
实施例七
图7为本公开实施例七提供的一种电子设备的结构示意图。图7示出了适于用来实现本公开实施方式的示例性电子设备712的框图。图7显示的电子设 备712仅仅是一个示例。
如图7所示，电子设备712以通用计算设备的形式表现。电子设备712的组件可以包括：一个或者多个处理器或者处理单元716，***存储器728，连接不同***组件(包括***存储器728和处理单元716)的总线718。
总线718表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，***总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。举例来说，这些体系结构包括工业标准体系结构(Industry Standard Architecture，ISA)总线，微通道体系结构(MicroChannel Architecture，MCA)总线，增强型ISA总线、视频电子标准协会(Video Electronics Standard Association，VESA)局域总线以及***组件互连(Peripheral Component Interconnect，PCI)总线。
电子设备712包括多种计算机***可读介质。这些介质可以是多种能够被电子设备712访问的可用介质，包括易失性和非易失性介质，可移动的和不可移动的介质。
***存储器728可以包括易失性存储器形式的计算机***可读介质，例如随机存取存储器(Random Access Memory，RAM)730和/或高速缓存732。电子设备712可以包括其它可移动/不可移动的、易失性/非易失性计算机***存储介质。仅作为举例，存储***734可以设置为读写不可移动的、非易失性磁介质(图7未显示，通常称为“硬盘驱动器”)。尽管图7中未示出，可以提供用于对可移动非易失性磁盘(例如“软盘”)读写的磁盘驱动器，以及对可移动非易失性光盘(例如便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)，数字视盘(Digital Video Disc-Read Only Memory，DVD-ROM)或者其它光介质)读写的光盘驱动器。在这些情况下，每个驱动器可以通过一个或者多个数据介质接口与总线718相连。存储器728可以包括至少一个程序产品，该程序产品具有一组(例如至少一个)程序模块，这些程序模块被配置以执行本公开一个或多个实施例的功能。
具有一组(至少一个)程序模块742的程序/实用工具740，可以存储在例如存储器728中，这样的程序模块742包括操作***、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络 环境的实现。程序模块742通常执行本公开所描述的实施例中的功能和/或方法。
电子设备712也可以与一个或多个外部设备714(例如键盘、指向设备、显示器724等)通信，还可与一个或者多个使得用户能与该电子设备712交互的设备通信，和/或与使得该电子设备712能与一个或多个其它计算设备进行通信的设备(例如网卡，调制解调器等等)通信。这种通信可以通过输入/输出(Input/Output，I/O)接口722进行。并且，电子设备712还可以通过网络适配器720与一个或者多个网络(例如局域网(Local Area Network，LAN)，广域网(Wide Area Network，WAN)和/或公共网络，例如因特网)通信。如图所示，网络适配器720通过总线718与电子设备712的其它模块通信。应当明白，尽管图7中未示出，可以结合电子设备712使用其它硬件和/或软件模块，包括：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、磁盘阵列(Redundant Arrays of Independent Drives，RAID)***、磁带驱动器以及数据备份存储***等。
处理单元716通过运行存储在***存储器728中的程序，从而执行多种功能应用以及数据处理，例如实现本公开实施例所提供的一种应用程序的账号管理方法。该方法可以包括：第一应用端接收账号操作请求，该账号操作请求携带第二应用账号；第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号；如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理。
实施例八
本公开实施例八还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如本公开实施例所提供的一种应用程序的账号管理方法，该方法可以包括：第一应用端接收账号操作请求，该账号操作请求携带第二应用账号；第一应用端查询第二应用账号在第一应用端中是否存在关联的虚拟账号；如果存在第二应用账号关联的虚拟账号，则对虚拟账号的业务数据进行处理。
本公开实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。 计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、RAM、只读存储器(Read-Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable ROM，EPROM)或闪存、光纤、CD-ROM、光存储器件、磁存储器件、或者上述的合适的组合。在本文件中，计算机可读存储介质可以是包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用适当的介质传输，包括无线、电线、光缆、射频(Radio Frequency，RF)等等，或者上述的合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++、Ruby、Go，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络—包括LAN或WAN—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。

Claims (11)

  1. 一种应用程序的账号管理方法，包括：
    第一应用端接收账号操作请求，所述账号操作请求携带第二应用账号；
    所述第一应用端查询所述第二应用账号在所述第一应用端中是否存在关联的虚拟账号；
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理。
  2. 根据权利要求1所述的方法，其中，所述账号操作请求为基于所述第二应用账号登录所述第一应用端的授权登录请求；
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理包括：
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，将所述虚拟账号变更为所述第一应用端的常规账号。
  3. 根据权利要求1所述的方法，其中，所述账号操作请求为将第一应用账号与所述第二应用账号进行绑定的账号绑定请求；
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理包括：
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，将所述虚拟账号与所述第一应用账号进行绑定，并将虚拟账号的业务数据迁移至所述第一应用账号的业务数据空间。
  4. 根据权利要求1所述的方法，其中，所述账号操作请求为将第一应用账号与所述第二应用账号进行绑定解除的账号解绑请求；
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理包括：
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行发布功能禁用处理，或删除所述虚拟账号及所述虚拟账号对应的业务数据。
  5. 根据权利要求1所述的方法，其中，所述账号操作请求为将第一应用账 号与两个所述第二应用账号进行绑定更换的账号绑定更换请求；
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理包括：
    所述第一应用端响应于存在所述第二应用账号关联的虚拟账号，调整所述两个第二应用账号各自对应的虚拟账号分别与所述第一应用账号的绑定关系，并将调整后绑定的第二应用账号对应的虚拟账号的业务数据迁移至所述第一应用账号的业务数据空间，并对解除绑定的第二应用账号对应的虚拟账号的业务数据进行发布功能禁用处理或者删除所述虚拟账号及所述虚拟账号对应的业务数据。
  6. 根据权利要求1所述的方法，其中，所述业务数据包括下述至少一项：用户在所述第一应用端或第二应用端发布的文字、图片、音频或视频，用户画像，以及用户行为数据。
  7. 根据权利要求1所述的方法，其中，所述虚拟账号与第一应用账号存在对应关系。
  8. 一种应用程序的账号管理装置，配置于第一应用端，包括：
    请求接收模块，设置为接收账号操作请求，所述账号操作请求携带第二应用账号；
    账号查询模块，设置为查询所述第二应用账号在所述第一应用端中是否存在关联的虚拟账号；
    数据处理模块，设置为响应于存在所述第二应用账号关联的虚拟账号，对所述虚拟账号的业务数据进行处理。
  9. 根据权利要求8所述的装置，其中，所述账号操作请求为基于所述第二应用账号登录所述第一应用端的授权登录请求；
    所述数据处理模块包括：
    账号变更模块，设置为响应于存在所述第二应用账号关联的虚拟账号，将所述虚拟账号变更为所述第一应用端的常规账号。
  10. 一种电子设备，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-7任一项所述的方法。
  11. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-7任一项所述的方法。
PCT/CN2019/097422 2018-07-27 2019-07-24 应用程序的账号管理方法、装置、设备和介质 WO2020020202A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810846824.9A CN109597640B (zh) 2018-07-27 2018-07-27 一种应用程序的账号管理方法、装置、设备和介质
CN201810846824.9 2018-07-27

Publications (1)

Publication Number Publication Date
WO2020020202A1 true WO2020020202A1 (zh) 2020-01-30

Family

ID=65956917

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097422 WO2020020202A1 (zh) 2018-07-27 2019-07-24 应用程序的账号管理方法、装置、设备和介质

Country Status (2)

Country Link
CN (1) CN109597640B (zh)
WO (1) WO2020020202A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109597640B (zh) * 2018-07-27 2020-01-17 北京字节跳动网络技术有限公司 一种应用程序的账号管理方法、装置、设备和介质
CN110704501B (zh) * 2019-09-11 2022-07-12 上海易点时空网络有限公司 用户账号关联方法及装置
CN111310006B (zh) * 2020-02-10 2021-06-04 腾讯科技（深圳）有限公司 账号绑定方法、装置、终端设备及计算机可读存储介质
CN111339418B (zh) * 2020-02-26 2023-07-18 抖音视界有限公司 页面展示方法、装置、电子设备和计算机可读介质
CN113242310B (zh) * 2020-06-30 2024-04-12 浙江口碑网络技术有限公司 基于小程序实现服务的方法及装置
CN113742667B (zh) * 2021-08-06 2024-06-21 杭州群核信息技术有限公司 账号信息处理方法和装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160364703A1 (en) * 2015-06-09 2016-12-15 Mastercard International Incorporated Systems and Methods for Verifying Users, in Connection With Transactions Using Payment Devices
CN107104923A (zh) * 2016-02-22 2017-08-29 阿里巴巴集团控股有限公司 一种账号绑定和业务处理的方法及装置
CN107528830A (zh) * 2017-08-03 2017-12-29 携程旅游信息技术（上海）有限公司 账号登陆方法、***及存储介质
CN109597640A (zh) * 2018-07-27 2019-04-09 北京字节跳动网络技术有限公司 一种应用程序的账号管理方法、装置、设备和介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9311457B1 (en) * 2011-11-02 2016-04-12 Google Inc. Platform for cloud application software
US9298796B2 (en) * 2014-08-01 2016-03-29 Veeva Systems Inc. System and method for enterprise data management
CN104917670B (zh) * 2015-06-09 2018-05-08 北京北信源软件股份有限公司 一种支持多应用用户标识关联的即时通信***及方法
US10158632B2 (en) * 2016-01-20 2018-12-18 Under Armour, Inc. Methods and apparatus for account linking
US10341360B2 (en) * 2016-03-07 2019-07-02 Arris Enterprises Llc Method and apparatus for user and entity access management for code signing one or more of a plurality of devices
US10565638B2 (en) * 2016-07-28 2020-02-18 International Business Machines Corporation Selectively shared account access
CN108205630A (zh) * 2016-12-20 2018-06-26 ***通信有限公司研究院 一种多用户下基于SeLinux的资源访问方法及装置
CN107645486B (zh) * 2016-12-28 2018-08-21 平安科技（深圳）有限公司 登录认证方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160364703A1 (en) * 2015-06-09 2016-12-15 Mastercard International Incorporated Systems and Methods for Verifying Users, in Connection With Transactions Using Payment Devices
CN107104923A (zh) * 2016-02-22 2017-08-29 阿里巴巴集团控股有限公司 一种账号绑定和业务处理的方法及装置
CN107528830A (zh) * 2017-08-03 2017-12-29 携程旅游信息技术（上海）有限公司 账号登陆方法、***及存储介质
CN109597640A (zh) * 2018-07-27 2019-04-09 北京字节跳动网络技术有限公司 一种应用程序的账号管理方法、装置、设备和介质

Also Published As

Publication number Publication date
CN109597640B (zh) 2020-01-17
CN109597640A (zh) 2019-04-09

Similar Documents

Publication Publication Date Title
WO2020020202A1 (zh) 应用程序的账号管理方法、装置、设备和介质
WO2020221190A1 (zh) 小程序状态同步方法、设备和计算机存储介质
US10445491B2 (en) Confirming the identity of integrator applications
WO2018188437A1 (zh) 一种多租户数据隔离方法、装置及***
CN105359105B (zh) 通过网络文件访问协议的高效编程存储器访问
WO2020020203A1 (zh) 业务数据的共享实现方法、装置、设备和存储介质
US20140259028A1 (en) Mechanism for establishing temporary background communication between applications
CN105683896A (zh) 跨多个虚拟机共享虚拟硬盘
US9830099B1 (en) Secure erase of storage devices
WO2021013242A1 (zh) 一种启动小程序的方法、设备和计算机存储介质
US20110283002A1 (en) Selectively Communicating Data Of A Peripheral Device To Plural Sending Computers
WO2020015448A1 (zh) 一种区块链网络的账号处理方法、装置、设备及存储介质
CN104603762A (zh) 利用并行文件访问协议的自动校准以及元数据管理支持对文件***的共享存储的协调访问
CN111163096B (zh) 提供数据接口服务的方法、装置、电子设备、存储介质
KR20180124582A (ko) 모바일 클라우드 시스템 및 그 동작 방법
WO2023193572A1 (zh) 一种数据管理方法、装置、服务器和存储介质
CN114201317A (zh) 数据传输方法、装置、存储介质及电子设备
CN113515395B (zh) 一种基于多云管理平台的应用接入方法及装置
US20220138220A1 (en) Dedicated replication channels for replicating records between regions
CN106161501A (zh) 虚拟桌面的数据共享方法和装置
WO2020173381A1 (zh) 数据互通方法、装置、终端及存储介质
CN110008186A (zh) 针对多ftp数据源的文件管理方法、装置、终端和介质
US20140279990A1 (en) Managing identifiers
CN113641966B (zh) 一种应用集成方法、***、设备及介质
US9159078B2 (en) Managing identifiers

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19841799

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17.05.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19841799

Country of ref document: EP

Kind code of ref document: A1