WO2020020203A1 - 业务数据的共享实现方法、装置、设备和存储介质 - Google Patents

业务数据的共享实现方法、装置、设备和存储介质 Download PDF

Info

Publication number
WO2020020203A1
WO2020020203A1 PCT/CN2019/097423 CN2019097423W WO2020020203A1 WO 2020020203 A1 WO2020020203 A1 WO 2020020203A1 CN 2019097423 W CN2019097423 W CN 2019097423W WO 2020020203 A1 WO2020020203 A1 WO 2020020203A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user information
application
virtual account
service platform
Prior art date
Application number
PCT/CN2019/097423
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 WO2020020203A1 publication Critical patent/WO2020020203A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • Embodiments of the present disclosure relate to Internet data processing technologies, for example, to a method, an apparatus, a device, and a storage medium for implementing sharing of business data.
  • Embodiments of the present disclosure provide a method, an apparatus, a device, and a storage medium for realizing the sharing of business data, so as to realize the sharing of business data between different applications.
  • an embodiment of the present disclosure provides a method for implementing sharing of service data, including:
  • the first application service platform sends a business data sharing request to the second application service platform through the inter-platform interface;
  • the first application service platform receives the business data fed back by the second application service platform through the interface between the platforms;
  • the first application service platform establishes a virtual account for the user who owns the business data, and stores the business data in the business data space of the virtual account;
  • the first application service platform pushes user information of the virtual account and business data corresponding to the virtual account through the first application client.
  • an embodiment of the present disclosure provides a device for realizing sharing of business data, which is configured on a first application service platform.
  • the device includes:
  • a sharing request sending module configured to send a business data sharing request to a second application service platform through an interface between platforms
  • a business data receiving module configured to receive business data fed back by a second application service platform through an interface between platforms
  • the virtual account creation module is configured to establish a virtual account for a user who owns the business data, and store the business data in the business data space of the virtual account;
  • the business data push module is configured to push user information of the virtual account and business data corresponding to the virtual account through the first application client.
  • an embodiment of the present disclosure further provides a computer 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 one or more processors, so that the one or more processors implement a method for sharing service data as described in the embodiments of the present disclosure.
  • the embodiment of the present disclosure further provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program is implemented as described in the embodiment of the present disclosure. Implementation method for sharing business data.
  • FIG. 1 is a flowchart of a method for implementing sharing of service data according to Embodiment 1 of the present disclosure
  • FIG. 2 is a flowchart of a method for implementing sharing of service data provided in Embodiment 2 of the present disclosure
  • FIG. 3 is a flowchart of a method for implementing sharing of service data according to Embodiment 3 of the present disclosure
  • FIG. 4 is a schematic structural diagram of an apparatus for implementing sharing of service data according to a fourth embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a computer device according to a fifth 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 realizing the sharing of business data according to the first embodiment of the present disclosure.
  • This embodiment can solve the related arts, such as public advertisements and documents, and social applications that mainly reflect personal personality. Of users, the problem is not high. For example, personal Weibo articles, users may want to see personalized Weibos written by their favorite stars. Limited by the application's user information management mechanism, it is difficult to transfer business information of other application users to another application across applications, because the user information managed by the application itself has a confidentiality agreement, and users cannot be easily transferred Information is transferred to other applications, and it is difficult to log in as a user of a new application when the user is not following the new application.
  • This embodiment may be applicable to a case where business data is shared between different applications.
  • the method may be executed by a device for sharing business data.
  • the device may be implemented in software and / or hardware. Generally, the device may be integrated in an application such as an application. Computer equipment such as program service platform.
  • Step 110 The first application service platform sends a business data sharing request to the second application service platform through the inter-platform interface.
  • the first application service platform may be a server capable of providing services to the first application client.
  • the second application service platform may be a server capable of providing services to the second application client.
  • the first application and the second application may be applications installed on the terminal device.
  • An interface can be a standard for data interaction between two parties (may be systems, modules, services, etc.).
  • the inter-platform interface may be a standard for data interaction between the first application service platform and the second application service platform.
  • the first application service platform and the second application service platform perform data interaction in a wireless manner or a wired manner through an interface between the platforms.
  • Business data can be related data generated by users performing business operations on applications.
  • business data can be articles, photos posted by users on the application.
  • Business data can be stored in the database of the application service platform corresponding to the application.
  • the business data of the second application is stored in a database of the second application service platform.
  • a business data sharing request is sent to the second application service platform through the inter-platform interface. The business data sharing request is used to request to obtain business data of the second application program.
  • Step 120 The first application service platform receives service data fed back by the second application service platform through an interface between the platforms.
  • the second application service platform after receiving the business data sharing request sent by the first application service platform, obtains the business data of the second application program from the database according to the business data sharing request, and sends the data to the first application service platform through the interface between the platforms. Send business data for the second application.
  • the first application service platform receives business data fed back by the second application service platform through an interface between the platforms.
  • Step 130 The first application service platform establishes a virtual account for the user who owns the business data, and stores the business data in the business data space of the virtual account.
  • the first application service platform establishes a virtual account for a user who owns the business data, and stores the business data in the business data space of the virtual account.
  • the business data space is a storage space dedicated to storing user's business data on the service platform.
  • the business data space of the virtual account is used to store data related to the virtual account.
  • the first application service platform establishes a virtual account for the user who owns the business data, stores the business data in the business data space of the virtual account, and associates the virtual account with the business data, so that the business data can be controlled through the virtual account.
  • the user of the business data is the user of the second application, not the user of the first application, and has no regular account with the first application.
  • 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 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.
  • the user can log in to the account and perform business operations on the application through the account.
  • the business data space of a conventional account is set to store business data generated by a user's business operations.
  • the virtual account is an account on the application used to manage business data shared by other applications.
  • 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. In one embodiment, a login operation cannot be performed through a virtual account.
  • the conventional account of the first application may be an account registered and used by the user on the first application, and the conventional account of the first application may also be a virtual account associated with the account of the second application.
  • the account obtained by the change is an account obtained by changing the virtual account associated with the account of the second application when the registration procedure is omitted.
  • Those skilled in the art can understand that, whether it is a conventional account obtained through registration or a changed conventional account, it can be an account that meets preset requirements (such as registration requirements), that is, a conventional account can be understood as meeting registration The required account.
  • Step 140 The first application service platform pushes user information of the virtual account and business data corresponding to the virtual account through the first application client.
  • the first application service platform pushes the user information of the virtual account and the business data corresponding to the virtual account through the first application client, so that the interface of the first application client can display the business data corresponding to the virtual account and display User information for the virtual account.
  • the business data corresponding to the virtual account is an article published by the user on the second application
  • the user information of the virtual account is the user name and user avatar of the user to which the article belongs.
  • the first application service platform pushes the user information of the virtual account and the business data corresponding to the virtual account on the first application client.
  • the user can browse the articles published by the user on the second application on the interface of the first application client, and can see the user name and user avatar of the user to which the article belongs.
  • the technical solution of this embodiment after sending a business data sharing request to the second application service platform through the inter-platform interface through the first application service platform, the business data fed back by the second application service platform is received, and the user of the business data is established.
  • the virtual account stores business data in the business data space of the virtual account, and pushes the user information of the virtual account and the business data corresponding to the virtual account through the first application client, which solves the problem that related technologies are limited by applications.
  • User information management mechanism the problem that it is difficult to transfer the business information of other application users to another application across applications, and can share business data between different applications, which can increase the update of information in new applications Volume to attract users.
  • FIG. 2 is a flowchart of a method for implementing sharing of service data provided in Embodiment 2 of the present disclosure.
  • the first application service platform to establish a virtual account for the user of the business data includes: the first application service platform receives user information corresponding to the user of the business data from the second application service platform; the first application service platform converts the user The account ID of the information is directly created as the account ID of the virtual account, and the user information is assigned as the user information of the virtual account.
  • the method further includes: the second application service platform inquires the user through the application client whether to allow service sharing and obtains the user's Business sharing authorization.
  • the method includes the following steps:
  • Step 210 The first application service platform sends a business data sharing request to the second application service platform through the inter-platform interface.
  • Step 220 The second application service platform inquires the user whether to allow service sharing through the second application client and obtains the user's service sharing authorization.
  • the second application service platform after receiving the business data sharing request sent by the first application service platform, the second application service platform asks the user through the second application client according to the business data sharing request whether to allow service sharing.
  • the second application service platform invokes the interface of the second application client according to the business data sharing request, displays the business sharing inquiry information to the user of the business data, and displays the business sharing consent option and the business sharing rejection option.
  • the service sharing query information is used to inquire whether the user can allow service sharing. The user enters the reply information by clicking the business sharing consent option or the business sharing rejection option.
  • the service sharing consent option it is determined that the user is allowed to perform service sharing, obtain the user's service sharing authorization, and continue to the next step; if the user clicks the service sharing rejection option, it is determined that the user is not allowed to perform service sharing. Service sharing authorization, no further operation is required.
  • Step 230 The first application service platform receives service data fed back by the second application service platform through an interface between the platforms.
  • Step 240 The first application service platform receives user information of the user corresponding to the business data from the second application service platform.
  • the first application service platform receives and acquires user information of the user corresponding to the business data from the second application service platform through the inter-platform interface.
  • the user information may include a user name, a user avatar, and the like.
  • Step 250 The first application service platform creates the account ID of the user information as the account ID of the virtual account, assigns the user information as the user information of the virtual account, and stores the business data in the business data space of the virtual account.
  • the account of the application has a unique account ID.
  • the account ID is used to distinguish each account.
  • the first application service platform may obtain the account ID corresponding to the user to which the business data belongs according to the received user information, directly create the account ID of the user information as the account ID of the virtual account, assign the user information as the user information of the virtual account, and perform business The data is stored in the business data space of the virtual account.
  • the business data space of the virtual account is stored consistent with the business data space of the regular account of the first application; the user information of the virtual account and the regular account is stored in a separate space.
  • the business data space of the virtual account stores the business data in the same storage manner as the business data space of the regular account of the first application. Because virtual accounts are not the same as regular accounts. User information can be personal information submitted by users.
  • 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. Therefore, the first application service platform stores the user information of the virtual account and the regular account in different data spaces.
  • Step 260 The first application service platform pushes user information of the virtual account and business data corresponding to the virtual account through the first application client.
  • the user is asked through the first application service platform whether service sharing is allowed and the user's service sharing authorization is obtained; and the user information is directly assigned to the account ID of the virtual account by assigning the user information
  • the user information of the virtual account establishing a virtual account for the user who owns the business data can improve the data security in the data sharing process, protect the privacy of the user, and create a virtual account more conveniently.
  • FIG. 3 is a flowchart of a method for implementing sharing of service data provided in Embodiment 3 of the present disclosure.
  • the first application service platform to establish a virtual account for the user of the business data includes: the first application service platform receives user information of the user corresponding to the business data from the second application service platform; the first application service platform is based on the user The information establishes a virtual account associated with the user information, and assigns the user information as the user information of the virtual account.
  • the method further includes: when the first application service platform receives an account registration request or an authorized login request based on the second application account; if the user information of the account registration request or the authorized login request matches the user information of the virtual account, Then the user information and business data space of the virtual account are associated with the account for which the account registration request or authorization login request is made.
  • the method includes the following steps:
  • Step 310 The first application service platform sends a business data sharing request to the second application service platform through the interface between the platforms.
  • Step 320 The second application service platform asks the user through the second application client whether to allow service sharing, and obtains the user's service sharing authorization.
  • Step 330 The first application service platform receives service data fed back by the second application service platform through the interface between the platforms.
  • Step 340 The first application service platform receives user information of the user corresponding to the business data from the second application service platform.
  • Step 350 The first application service platform establishes a virtual account associated with the user information according to the user information, assigns the user information as the user information of the virtual account, and stores the business data in the business data space of the virtual account.
  • the first application service platform creates an account identifier of the virtual account according to the user information.
  • the account ID of the created virtual account is different from the account ID corresponding to the user to which the business data belongs, and is the new account ID.
  • the user information is assigned as the user information of the virtual account, and the business data is stored in the business data space of the virtual account.
  • Step 360 The first application service platform pushes the user information of the virtual account and the business data corresponding to the virtual account through the first application client.
  • Step 370 The first application service platform receives an account registration request or an authorization login request based on a second application account.
  • the new user enters registration information on the first application client, and when performing account registration, the first application client transmits an account registration request to the first application service platform.
  • the account registration request is used to request the first application service platform to establish a corresponding new account.
  • the first application service platform receives an account registration request sent by a new user through the first application client.
  • the user of the second application may choose to log in to the first application client through the account of the second application.
  • the first application client transmits an authorization login request based on the second application account to the first application service platform .
  • the authorization login request is used for the first application to request to log in through the account of the second application.
  • the first application service platform receives an authorized login request based on the second application account.
  • Step 380 In response to the user information of the account registration request or the authorized login request being matched with the user information of the virtual account, the user information and the business data space of the virtual account are associated with the account of the account registration request or the authorized login request.
  • the first application service platform receives an account registration request sent by a new user through the first application client, obtains the user information corresponding to the account registration request according to the account registration request, and stores the user information corresponding to the account registration request and the stored information in the database. The user information of the virtual account is matched.
  • the user information of the account registration request matches the user information of the virtual account, it indicates that the corresponding user of the account registration request has authorized the first application to perform service sharing. If there is a corresponding virtual account in the first application, the corresponding virtual The user information and business data space of the account are associated with the account requested by the account registration. In an embodiment, if the user information of the account registration request matches the user information of the virtual account, the virtual account is changed to a regular account of the first application, and the obtained regular account is used as the first application service platform to register according to the account. The requested new account is fed back to the first application client. The user information of the new account is the user information requested by the account registration.
  • the business data space of the new account stores the business data that the user once authorized the first application to perform service sharing. The user can log in to the new account and perform business operations on the first application through the new account.
  • the service platform directly establishes a corresponding new account according to the account registration request, and feeds it back to the first application client.
  • the first application service platform receives the authorization login request based on the second application account sent by the user through the first application client, obtains the user information corresponding to the authorization login request according to the authorization login request based on the second application account, and The user information corresponding to the authorized login request of the second application account is matched with the user information of the virtual account stored in the database.
  • the user information of the authorized login request matches the user information of the virtual account, it indicates that the corresponding user of the authorized login request has authorized the first application to perform service sharing. If there is a corresponding virtual account in the first application, the corresponding virtual The user information and business data space of the account are associated with the account that authorized the login request. In an embodiment, if the user information of the authorized login request matches the user information of the virtual account, the virtual account is changed to the regular account of the first application, and the obtained regular account is fed back to the first application client. The user can log in to the first application through the conventional account and perform business operations on the first application.
  • the first application establishes an associated first application account according to the second application account in the account login request, and feeds back the first application account to the first application client for a login operation.
  • the technical solution of this embodiment establishes an associated virtual account according to the user information through the first application service platform; and receives the user's account registration request or the authorization login request based on the second application account and the virtual account on the first application service platform
  • the user information and business data space of the virtual account are associated with the account for which the account registration request or authorized login request is made.
  • the account ID can be used to distinguish the original account and virtual account of the user who owns the business data. Sharing historical behaviors provides services to improve user experience.
  • FIG. 4 is a schematic structural diagram of a service data sharing implementation device provided in Embodiment 4 of the present disclosure. This embodiment is applicable to a case where service data is shared.
  • the apparatus may be implemented in a software and / or hardware manner, and may generally be configured in a computer device such as a first application service platform. As shown in FIG. 4, the device includes a sharing request sending module 401, a service data receiving module 402, a virtual account establishing module 403, and a service data pushing module 404.
  • the sharing request sending module 401 is configured to send a business data sharing request to a second application service platform through an inter-platform interface;
  • the business data receiving module 402 is configured to receive business data fed back by the second application service platform through an inter-platform interface;
  • the virtual account creation module 403 is configured to create a virtual account for the user who owns the business data and store the business data in the business data space of the virtual account;
  • the business data push module 404 is configured to set the user information of the virtual account and the corresponding virtual account. Business data is pushed through the first application client.
  • the technical solution of this embodiment after sending a business data sharing request to the second application service platform through the inter-platform interface through the first application service platform, the business data fed back by the second application service platform is received, and the user of the business data is established.
  • the virtual account stores business data in the business data space of the virtual account, and pushes the user information of the virtual account and the business data corresponding to the virtual account through the first application client, which solves the problem that related technologies are limited by applications.
  • User information management mechanism the problem that it is difficult to transfer the business information of other application users to another application across applications, and can share business data between different applications, which can increase the update of information in new applications Volume to attract users.
  • the virtual account establishment module 403 may include:
  • a first information receiving unit configured to receive user information of a user corresponding to business data from a second application service platform
  • the first account creation unit is configured to create an account identifier of the user information as an account identifier of the virtual account, and assign the user information as the user information of the virtual account.
  • the virtual account establishment module 403 may include:
  • a second information receiving unit configured to receive user information of a user corresponding to business data from a second application service platform
  • the second account creation unit is configured to establish a virtual account associated with the user information according to the user information, and assign the user information as the user information of the virtual account.
  • the business data space of the virtual account is stored consistent with the business data space of the regular account of the first application; the user information of the virtual account and the regular account is stored in a separate space.
  • a corresponding device may be configured in the second application service platform, and the device may include: an authorization acquisition module configured to query the user through the second application client Whether to allow service sharing and obtain user service sharing authorization.
  • the device configured on the first application service platform may further include:
  • the request receiving module is configured to receive a user account registration request or an authorization login request based on a second application account;
  • the account association module is configured to associate the user information and the business data space of the virtual account with the account of the account registration request or the authorized login request if the user information of the account registration request or the authorized login request matches the user information of the virtual account.
  • the account association module may include:
  • the first account association unit is configured to change the virtual account to a regular account of the first application if the user information requested by the account registration matches the user information of the virtual account, and use the obtained regular account as the first application service platform.
  • the new account created by the account registration request is fed back to the first application client.
  • the account association module may include:
  • the second account association unit is configured to change the virtual account to a regular account of the first application if the user information of the authorized login request matches the user information of the virtual account, and feedback the obtained regular account to the first application client end.
  • the service data sharing implementation device provided by the embodiment of the present disclosure can execute the service data sharing implementation method provided by any embodiment of the present disclosure, and has function modules and effects corresponding to the execution method.
  • FIG. 5 is a schematic structural diagram of a computer device according to a fifth embodiment of the present disclosure.
  • FIG. 5 illustrates a block diagram of an exemplary computer device 512 suitable for use in implementing embodiments of the present disclosure.
  • the computer device 512 shown in FIG. 5 is merely an example.
  • the computer device 512 is represented in the form of a general-purpose computing device.
  • the components of the computer device 512 may include: one or more processors or processing units 516, a system memory 528, and a bus 518 connecting different system components (including the system memory 528 and the processing unit 516).
  • the bus 518 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.
  • ISA Industry Standard Architecture
  • MCA Micro Channel Architecture
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnect
  • Computer device 512 includes a variety of computer system-readable media. These media can be a variety of available media that can be accessed by the computer device 512, including volatile and non-volatile media, removable and non-removable media.
  • the system memory 528 may include a computer system readable medium in the form of volatile memory, such as a Random Access Memory (RAM) 530 and / or a cache 532.
  • Computer device 512 may include other removable / non-removable, volatile / nonvolatile computer system storage media.
  • the storage system 534 may be configured to read and write non-removable, non-volatile magnetic media (not shown in FIG. 5 and is commonly referred to as a "hard drive").
  • each drive may be connected to the bus 518 through one or more data medium interfaces.
  • the memory 528 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 540 having a set (at least one) of program modules 542 may be stored in, for example, the memory 528.
  • a program module 542 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 542 generally performs functions and / or methods in the embodiments described in the present disclosure.
  • the computer device 512 may also communicate with one or more external devices 514 (such as a keyboard, pointing device, display 524, etc.), and may also communicate with one or more devices that enable a user to interact with the computer device 512, and / or with A device (eg, a network card, modem, etc.) that enables the computer device 512 to communicate with one or more other computing devices. This communication can be performed through an input / output (I / O) interface 522.
  • the computer device 512 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 520.
  • 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 520 communicates with other modules of the computer device 512 through the bus 518. It should be understood that although not shown in FIG. 5, other hardware and / or software modules may be used in conjunction with the computer device 512, 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 Drives
  • the processing unit 516 executes a variety of functional applications and data processing by running a program stored in the system memory 528, for example, implementing a method for sharing business data provided by the embodiments of the present disclosure. That is, the first application service platform sends a business data sharing request to the second application service platform through the inter-platform interface; the first application service platform receives the business data fed back by the second application service platform through the inter-platform interface; the first application service platform To establish a virtual account for the user who owns the business data, and store the business data in the business data space of the virtual account; the first application service platform performs the user information of the virtual account and the business data corresponding to the virtual account through the first application client Push.
  • Embodiment 6 of the present disclosure also provides a computer-readable storage medium on which a computer program is stored.
  • a method for implementing sharing of service data as provided in the embodiment of the present disclosure is provided.
  • the method may include: the first application service platform sends a business data sharing request to the second application service platform through the inter-platform interface; the first application service platform receives the business data fed back by the second application service platform through the inter-platform interface; the first application service platform To establish a virtual account for the user who owns the business data, and store the business data in the business data space of the virtual account; the first application service platform performs the user information of the virtual account and the business data corresponding to the virtual account through the first application client Push.
  • 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 any suitable combination of the foregoing.
  • 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 can take a variety of forms, including electromagnetic signals, optical signals, or a 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 any 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本文公开了一种业务数据的共享实现方法、装置、设备和存储介质。其中，该方法包括：第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求；第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据；第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至所述虚拟账号的业务数据空间中；第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。

Description

业务数据的共享实现方法、装置、设备和存储介质
本申请要求在2018年7月27日提交中国专利局、申请号为201810846837.6的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开实施例涉及互联网数据处理技术，例如涉及一种业务数据的共享实现方法、装置、设备和存储介质。
背景技术
随着互联网和智能终端的发展，应用程序(Application，APP)增多，当一个应用程序新推出时，例如以社交为主的应用程序，会因为用户数量少、用户分享信息少而使得应用程序的使用体验不佳，由此又导致用户更不容易聚集，恶性循环。
相关技术中存在一种解决方案，即从其他网站、应用程序等数据源链接一些广告、公开文献(如新闻等)进行转发分享，从而增加新应用程序中的信息更新量，吸引用户。
但是，公共性质的广告、文献，对以体现私人个性为主的社交类应用程序的用户来说，匹配度并不高。
发明内容
本公开实施例提供一种业务数据的共享实现方法、装置、设备和存储介质，以实现业务数据在不同应用程序之间的共享。
在一实施例中，本公开实施例提供了一种业务数据的共享实现方法，包括：
第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求；
第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据；
第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存 储至虚拟账号的业务数据空间中；
第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
在一实施例中，本公开实施例提供了一种业务数据的共享实现装置，配置于第一应用服务平台，所述装置包括：
共享请求发送模块，设置为通过平台间接口，向第二应用服务平台发送业务数据共享请求；
业务数据接收模块，设置为接收第二应用服务平台通过平台间接口反馈的业务数据；
虚拟账号建立模块，设置为为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中；
业务数据推送模块，设置为将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
在一实施例中，本公开实施例还提供了一种计算机设备，包括：
一个或多个处理器；
存储器，设置为存储一个或多个程序；
一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现如本公开实施例所述的业务数据的共享实现方法。
在一实施例中，本公开实施例还提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现如本公开实施例所述的业务数据的共享实现方法。
附图说明
图1为本公开实施例一提供的一种业务数据的共享实现方法的流程图；
图2为本公开实施例二提供的一种业务数据的共享实现方法的流程图；
图3为本公开实施例三提供的一种业务数据的共享实现方法的流程图；
图4为本公开实施例四提供的一种业务数据的共享实现装置的结构示意图；
图5为本公开实施例五提供的一种计算机设备的结构示意图。
具体实施方式
下面结合附图和实施例对本公开进行说明。此处所描述的具体实施例仅仅用于解释本公开，而非对本公开的限定。
为了便于描述，附图中仅示出了与本公开相关的部分而非全部结构。在更加详细地讨论示例性实施例之前应当提到的是，一些示例性实施例被描述成作为流程图描绘的处理或方法。虽然流程图将多项操作(或步骤)描述成顺序的处理，但是其中的许多操作可以被并行地、并发地或者同时实施。此外，一项或多项操作的顺序可以被重新安排。当其操作完成时所述处理可以被终止，但是还可以具有未包括在附图中的附加步骤。所述处理可以对应于方法、函数、规程、子例程、子程序等等。
下述多个实施例中，每个实施例中同时提供了可选特征和示例，实施例中记载的多个特征可进行组合，形成多个可选方案，不应将每个编号的实施例仅视为一个技术方案。
实施例一
图1为本公开实施例一提供的一种业务数据的共享实现方法的流程图，本实施例可解决相关技术中，公共性质的广告、文献，对以体现私人个性为主的社交类应用程序的用户来说，匹配度并不高的问题。例如个人微博文章，可能用户会希望看到自己喜欢的明星所撰写的个性化微博。受限于应用程序的用户信息管理机制，难以跨应用程序将其他应用程序用户的业务信息转移到另一应用程序中，因为应用程序自身所管理的用户信息是有保密协议的，不能轻易将用户信息转移给其他应用程序，而在用户不关注新应用程序时，也难以登录成为新应用程序的用户。本实施例可适用于在不同应用程序之间共享业务数据的情况，该方法可以由业务数据的共享实现装置来执行，该装置可以采用软件和/或硬件的方式实现，一般可集成在诸如应用程序服务平台等计算机设备中。该方法包括如下步骤：
步骤110、第一应用服务平台通过平台间接口，向第二应用服务平台发送业 务数据共享请求。
其中，第一应用服务平台可以是能够向第一应用程序客户端提供服务的服务器。第二应用服务平台可以是能够向第二应用程序客户端提供服务的服务器。第一应用程序和第二应用程序可以为安装于终端设备上的应用程序。
接口可以是双方(可能是系统、模块、服务等)之间数据交互的一个标准。平台间接口可以为第一应用服务平台与第二应用服务平台之间进行数据交互的标准。第一应用服务平台与第二应用服务平台通过平台间接口进行无线方式或有线方式的数据交互。
业务数据可以是用户在应用程序上进行业务操作所产生的相关数据。例如，业务数据可以为用户在应用程序上发布的文章、照片。业务数据可以存储在应用程序对应的应用服务平台的数据库中。例如，第二应用程序的业务数据存储在第二应用服务平台的数据库中。当第一应用程序需要共享第二应用程序的业务数据时，通过平台间接口，向第二应用服务平台发送业务数据共享请求。业务数据共享请求用于请求获取第二应用程序的业务数据。
步骤120、第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据。
其中，第二应用服务平台接收第一应用服务平台发送的业务数据共享请求后，根据业务数据共享请求从数据库中获取第二应用程序的业务数据，并通过平台间接口，向第一应用服务平台发送第二应用程序的业务数据。第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据。
步骤130、第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中。
其中，第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中。业务数据空间是服务平台上专用于存储用户的业务数据的存储空间。虚拟账号的业务数据空间用于存储与虚拟账号相关的数据。第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间，使虚拟账号与业务数据相关，从而可以通过虚拟账号对业务数据进行控制。
业务数据的所属用户为第二应用程序的用户，不是第一应用程序的用户，没有与第一应用程序的常规账号。虚拟账号与常规账号并不相同。常规账号通常为用户在应用程序上注册并使用的账号。常规账号包括用户信息和业务数据空间。用户信息可以为用户提交的个人信息。用户信息可以包括用户名称、用户头像等。用户可以登录账号，并通过账号在应用程序上进行业务操作。常规账号的业务数据空间设置为存储用户进行业务操作所产生的业务数据。而虚拟账号为应用程序上用于管理其他应用程序共享的业务数据的账号。虚拟账号包括用户信息和业务数据空间。虚拟账号的业务数据空间设置为存储其他应用程序共享的业务数据。虚拟账号的用户信息为根据业务数据的所属用户对应的用户信息生成的用户信息。在一实施例中，无法通过虚拟账户进行登录操作。
在一实施例中，第一应用程序的的常规账号可以为用户在第一应用程序上注册并使用的账号，第一应用端的常规账号也可以为对与第二应用程序的账号关联的虚拟账号进行变更得到的账号，即在省略了注册程序的情况下，通过对与第二应用程序的账号关联的虚拟账号进行变更得到的账号。本领域技术人员可以理解的是，无论是注册得到的常规账号，还是变更得到的常规账号，均可以是符合预设要求(例如注册要求)的账号，也就是说，常规账号可以理解为符合注册要求的账号。
步骤140、第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
其中，第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送，以使第一应用程序客户端的界面可以显示虚拟账号对应的业务数据，并显示虚拟账号的用户信息。
例如，虚拟账号对应的业务数据为用户在第二应用程序上发布的文章，虚拟账号的用户信息为文章所属用户的用户名称和用户头像。第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据在第一应用程序客户端进行推送。用户可以在第一应用程序客户端的界面上浏览用户在第二应用程序上发布的文章，并可以看到文章所属用户的用户名称和用户头像。
本实施例的技术方案，通过第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求后，接收第二应用服务平台通反馈的业务数 据，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中，并将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送，解决了相关技术受限于应用程序的用户信息管理机制，难以跨应用程序将其他应用程序用户的业务信息转移到另一应用程序中的问题，可以实现业务数据在不同应用程序之间的共享，从而可以增加新应用程序中的信息更新量，吸引用户。
实施例二
图2为本公开实施例二提供的一种业务数据的共享实现方法的流程图。本实施例可以与上述实施例中的可选方案相互结合。在本实施例中，第一应用服务平台，为业务数据的所属用户建立虚拟账号包括：第一应用服务平台从第二应用服务平台接收业务数据对应用户的用户信息；第一应用服务平台将用户信息的账号标识直接创建为虚拟账号的账号标识，将用户信息赋值作为虚拟账号的用户信息。
可选的，第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据之前，还包括：第二应用服务平台通过应用客户端向用户询问是否允许进行业务共享，并获取用户的业务共享授权。
如图2所示，该方法包括如下步骤：
步骤210、第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求。
步骤220、第二应用服务平台通过第二应用程序客户端向用户询问是否允许进行业务共享，并获取用户的业务共享授权。
其中，第二应用服务平台接收第一应用服务平台发送的业务数据共享请求后，根据业务数据共享请求通过第二应用程序客户端向用户询问是否允许进行业务共享。在一实施例中，第二应用服务平台根据业务数据共享请求调用第二应用程序客户端的界面，向业务数据的所属用户显示业务共享询问信息，并显示业务共享同意选项和业务共享拒绝选项。业务共享询问信息用于询问用户可以是否允许进行业务共享。用户通过点击业务共享同意选项或业务共享拒绝选 项，输入回复信息。如果用户点击业务共享同意选项，则确定用户允许进行业务共享，获取用户的业务共享授权，继续进行下一步操作；如果用户点击业务共享拒绝选项，则确定用户不允许进行业务共享，未获取用户的业务共享授权，不再进行下一步操作。
步骤230、第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据。
步骤240、第一应用服务平台从第二应用服务平台接收业务数据对应用户的用户信息。
其中，第一应用服务平台通过平台间接口从第二应用服务平台接收与获取的业务数据对应用户的用户信息。用户信息可以包括用户名称、用户头像等。
步骤250、第一应用服务平台将用户信息的账号标识创建为虚拟账号的账号标识，将用户信息赋值作为虚拟账号的用户信息，将业务数据存储至虚拟账号的业务数据空间中。
其中，应用程序的账号有唯一对应的账号标识。账号标识用于区别每一个账号。第一应用服务平台可以根据接收的用户信息获取业务数据的所属用户对应的账号标识，将用户信息的账号标识直接创建为虚拟账号的账号标识，将用户信息赋值作为虚拟账号的用户信息，将业务数据存储至虚拟账号的业务数据空间中。
可选的，虚拟账号的业务数据空间与第一应用程序的常规账号的业务数据空间保持一致存储；虚拟账号和常规账号的用户信息区别空间存储。
其中，虚拟账号的业务数据空间与第一应用程序的常规账号的业务数据空间采用同样的存储方式对业务数据进行存储。由于虚拟账号与常规账号并不相同。用户信息可以为用户提交的个人信息。虚拟账号的用户信息为根据业务数据的所属用户对应的用户信息生成的用户信息。因此，第一应用服务平台将虚拟账号和常规账号的用户信息存储在不同的数据空间中。
步骤260、第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
本实施例的技术方案，通过第一应用服务平台向用户询问是否允许进行业 务共享，获取用户的业务共享授权；并通过将用户信息的账号标识直接创建为虚拟账号的账号标识，将用户信息赋值作为虚拟账号的用户信息，为业务数据的所属用户建立虚拟账号，可以提高数据共享过程中的数据安全性，保护用户的隐私，可以更便捷地建立虚拟账户。
实施例三
图3为本公开实施例三提供的一种业务数据的共享实现方法的流程图。本实施例可以与上述实施例中的可选方案相互结合。在本实施例中，第一应用服务平台，为业务数据的所属用户建立虚拟账号包括：第一应用服务平台从第二应用服务平台接收业务数据对应用户的用户信息；第一应用服务平台根据用户信息建立与用户信息关联的虚拟账号，将用户信息赋值作为虚拟账号的用户信息。
可选的，该方法还包括：第一应用服务平台接收账号注册请求或基于第二应用程序账号的授权登录请求时；如果账号注册请求或授权登录请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号的用户信息和业务数据空间与账号注册请求或授权登录请求的账号进行关联。
如图3所示，该方法包括如下步骤：
步骤310、第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求。
步骤320、第二应用服务平台通过第二应用程序客户端向用户询问是否允许进行业务共享，并获取用户的业务共享授权。
步骤330、第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据。
步骤340、第一应用服务平台从第二应用服务平台接收业务数据对应用户的用户信息。
步骤350、第一应用服务平台根据用户信息建立与用户信息关联的虚拟账号，将用户信息赋值作为虚拟账号的用户信息，将业务数据存储至虚拟账号的业务数据空间中。
其中，第一应用服务平台根据用户信息创建虚拟账号的账号标识。创建的虚拟账号的账号标识与业务数据的所属用户对应的账号标识不同，为新的账户标识。将用户信息赋值作为虚拟账号的用户信息，将业务数据存储至虚拟账号的业务数据空间中。
步骤360、第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
步骤370、第一应用服务平台接收账号注册请求或基于第二应用程序账号的授权登录请求。
其中，新用户在第一应用程序客户端上输入注册信息，进行账号注册时，通过第一应用程序客户端向第一应用服务平台传输账号注册请求。账号注册请求用于请求第一应用服务平台建立对应的新账号。第一应用服务平台接收新用户通过第一应用程序客户端发送的账号注册请求。
第二应用程序的用户可以选择通过第二应用程序的账号登录第一应用程序客户端。当用户在第一应用程序客户端的界面中，选择了通过第二应用程序的账号进行登录的方式时，第一应用程序客户端向第一应用服务平台传输基于第二应用程序账号的授权登录请求。授权登录请求用于第一应用程序请求通过第二应用程序的账号进行登录。第一应用服务平台接收基于第二应用程序账号的授权登录请求。
步骤380、响应于账号注册请求或授权登录请求的用户信息与虚拟账号的用户信息匹配，将虚拟账号的用户信息和业务数据空间与账号注册请求或授权登录请求的账号进行关联。
其中，第一应用服务平台接收新用户通过第一应用程序客户端发送的账号注册请求，根据账号注册请求获取账号注册请求对应的用户信息，并将账号注册请求对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。
如果账号注册请求的用户信息与虚拟账号的用户信息匹配，表明账号注册请求的对应的用户曾经授权第一应用程序进行业务共享，在第一应用程序中有对应的虚拟账号，则将对应的虚拟账号的用户信息和业务数据空间与账号注册请求的账号进行关联。在一实施例中，如果账号注册请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号变更为第一应用程序的常规账号，并将得到 的常规账号作为第一应用服务平台根据账号注册请求建立的新账号，反馈至第一应用程序客户端。新账号的用户信息即为账号注册请求的用户信息，新账号的业务数据空间中存储着用户曾经授权第一应用程序进行业务共享的业务数据。用户可以登录新账号，并通过新账号在第一应用程序上进行业务操作。
如果账号注册请求的用户信息与虚拟账号的用户信息不匹配，表明账号注册请求的对应的用户未授权第一应用程序进行业务共享，在第一应用程序中没有对应的虚拟账号，则第一应用服务平台直接根据账号注册请求建立一个对应的新账号，反馈至第一应用程序客户端。
第一应用服务平台接收用户通过第一应用程序客户端发送的基于第二应用程序账号的授权登录请求，根据基于第二应用程序账号的授权登录请求获取授权登录请求对应的用户信息，并将基于第二应用程序账号的授权登录请求对应的用户信息与数据库中存储的虚拟账号的用户信息进行匹配。
如果授权登录请求的用户信息与虚拟账号的用户信息匹配，表明授权登录请求的对应的用户曾经授权第一应用程序进行业务共享，在第一应用程序中有对应的虚拟账号，则将对应的虚拟账号的用户信息和业务数据空间与授权登录请求的账号进行关联。在一实施例中，如果授权登录请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号变更为第一应用程序的常规账号，并将得到的常规账号反馈给第一应用程序客户端。用户可以通过该常规账号登录第一应用程序，并在第一应用程序上进行业务操作。
如果授权登录请求的用户信息与虚拟账号的用户信息不匹配，表明授权登录请求的对应的用户未授权第一应用程序进行业务共享，在第一应用程序中没有对应的虚拟账号，则第一应用服务平台根据账号登录请求中的第二应用程序账号建立关联的第一应用程序账号，将第一应用程序账号反馈给第一应用程序客户端进行登录操作。
本实施例的技术方案，通过第一应用服务平台根据用户信息建立关联的虚拟账号；并在第一应用服务平台接收用户的账号注册请求或基于第二应用程序账号的授权登录请求与虚拟账号的用户信息匹配时，将虚拟账号的用户信息和业务数据空间与账号注册请求或授权登录请求的账号进行关联，可以通过账户标识区别业务数据的所属用户的原账户和虚拟账户，可以根据用户的数据共享 历史行为提供服务，提高用户体验。
实施例四
图4为本公开实施例四提供的一种业务数据的共享实现装置的结构示意图，本实施例可适用于共享业务数据的情况。该装置可以采用软件和/或硬件的方式实现，一般可配置在诸如第一应用服务平台的计算机设备中。如图4所示，该装置包括：共享请求发送模块401、业务数据接收模块402、虚拟账号建立模块403和业务数据推送模块404。
其中，共享请求发送模块401，设置为通过平台间接口，向第二应用服务平台发送业务数据共享请求；业务数据接收模块402，设置为接收第二应用服务平台通过平台间接口反馈的业务数据；虚拟账号建立模块403，设置为为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中；业务数据推送模块404，设置为将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
本实施例的技术方案，通过第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求后，接收第二应用服务平台通反馈的业务数据，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中，并将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送，解决了相关技术受限于应用程序的用户信息管理机制，难以跨应用程序将其他应用程序用户的业务信息转移到另一应用程序中的问题，可以实现业务数据在不同应用程序之间的共享，从而可以增加新应用程序中的信息更新量，吸引用户。
可选的，在上述技术方案中可选方案的基础上，虚拟账号建立模块403可以包括：
第一信息接收单元，设置为从第二应用服务平台接收业务数据对应用户的用户信息；
第一账号创建单元，设置为将用户信息的账号标识创建为虚拟账号的账号标识，将用户信息赋值作为虚拟账号的用户信息。
可选的，在上述技术方案中可选方案的基础上，虚拟账号建立模块403可以包括：
第二信息接收单元，设置为从第二应用服务平台接收业务数据对应用户的用户信息；
第二账号创建单元，设置为根据用户信息建立与用户信息关联的虚拟账号，将用户信息赋值作为虚拟账号的用户信息。
可选的，在上述技术方案中可选方案的基础上，虚拟账号的业务数据空间与第一应用程序的常规账号的业务数据空间保持一致存储；虚拟账号和常规账号的用户信息区别空间存储。
可选的，在上述技术方案中可选方案的基础上，可以在第二应用服务平台中配置对应的装置，该装置可包括：授权获取模块，设置为通过第二应用程序客户端向用户询问是否允许进行业务共享，并获取用户的业务共享授权。
可选的，在上述技术方案中可选方案的基础上，配置在第一应用服务平台的装置可以还包括：
请求接收模块，设置为接收用户的账号注册请求或基于第二应用程序账号的授权登录请求；
账号关联模块，设置为如果账号注册请求或授权登录请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号的用户信息和业务数据空间与账号注册请求或授权登录请求的账号进行关联。
可选的，在上述技术方案中可选方案的基础上，账号关联模块可以包括：
第一账号关联单元，设置为如果账号注册请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号变更为第一应用程序的常规账号，并将得到的常规账号作为第一应用服务平台根据账号注册请求建立的新账号，反馈至第一应用程序客户端。
可选的，在上述技术方案中可选方案的基础上，账号关联模块可以包括：
第二账号关联单元，设置为如果授权登录请求的用户信息与虚拟账号的用户信息匹配，则将虚拟账号变更为第一应用程序的常规账号，并将得到的常规账号反馈给第一应用程序客户端。
本公开实施例所提供的业务数据的共享实现装置可执行本公开任意实施例所提供的业务数据的共享实现方法，具备执行方法相应的功能模块和效果。
实施例五
图5为本公开实施例五提供的一种计算机设备的结构示意图。图5示出了适于用来实现本公开实施方式的示例性计算机设备512的框图。图5显示的计算机设备512仅仅是一个示例。
如图5所示，计算机设备512以通用计算设备的形式表现。计算机设备512的组件可以包括：一个或者多个处理器或者处理单元516，系统存储器528，连接不同系统组件(包括系统存储器528和处理单元516)的总线518。
总线518表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，外围总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。举例来说，这些体系结构包括工业标准体系结构(Industry Standard Architecture，ISA)总线，微通道体系结构(MicroChannel Architecture，MCA)总线，增强型ISA总线、视频电子标准协会(Video Electronics Standard Association，VESA)局域总线以及外围组件互连(Peripheral Component Interconnect，PCI)总线。
计算机设备512包括多种计算机系统可读介质。这些介质可以是多种能够被计算机设备512访问的可用介质，包括易失性和非易失性介质，可移动的和不可移动的介质。
系统存储器528可以包括易失性存储器形式的计算机系统可读介质，例如随机存取存储器(Random Access Memory，RAM)530和/或高速缓存532。计算机设备512可以包括其它可移动/不可移动的、易失性/非易失性计算机系统存储介质。仅作为举例，存储系统534可以设置为读写不可移动的、非易失性磁介质(图5未显示，通常称为“硬盘驱动器”)。尽管图5中未示出，可以提供用于对可移动非易失性磁盘(例如“软盘”)读写的磁盘驱动器，以及对可移动非易失性光盘(例如便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)，数字视盘(Digital Video Disc-Read Only Memory，DVD-ROM)或者其它光介质)读写的光盘驱动器。在这些情况下，每个驱动器 可以通过一个或者多个数据介质接口与总线518相连。存储器528可以包括至少一个程序产品，该程序产品具有一组(例如至少一个)程序模块，这些程序模块被配置以执行本公开一个或多个实施例的功能。
具有一组(至少一个)程序模块542的程序/实用工具540，可以存储在例如存储器528中，这样的程序模块542包括操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。程序模块542通常执行本公开所描述的实施例中的功能和/或方法。
计算机设备512也可以与一个或多个外部设备514(例如键盘、指向设备、显示器524等)通信，还可与一个或者多个使得用户能与该计算机设备512交互的设备通信，和/或与使得该计算机设备512能与一个或多个其它计算设备进行通信的设备(例如网卡，调制解调器等等)通信。这种通信可以通过输入/输出(Input/Output，I/O)接口522进行。并且，计算机设备512还可以通过网络适配器520与一个或者多个网络(例如局域网(Local Area Network，LAN)，广域网(Wide Area Network，WAN)和/或公共网络，例如因特网)通信。如图所示，网络适配器520通过总线518与计算机设备512的其它模块通信。应当明白，尽管图5中未示出，可以结合计算机设备512使用其它硬件和/或软件模块，包括：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、磁盘阵列(Redundant Arrays of Independent Drives，RAID)系统、磁带驱动器以及数据备份存储系统等。
处理单元516通过运行存储在系统存储器528中的程序，从而执行多种功能应用以及数据处理，例如实现本公开实施例所提供的业务数据的共享实现方法。也即，第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求；第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据；第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中；第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
实施例六
本公开实施例六还提供了一种计算机可读存储介质，其上存储有计算机程 序，该程序被处理器执行时实现如本公开实施例所提供的一种业务数据的共享实现方法，该方法可以包括：第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求；第一应用服务平台接收第二应用服务平台通过平台间接口反馈的业务数据；第一应用服务平台，为业务数据的所属用户建立虚拟账号，将业务数据存储至虚拟账号的业务数据空间中；第一应用服务平台将虚拟账号的用户信息以及虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
本公开实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、RAM、只读存储器(Read-Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable ROM，EPROM)或闪存、光纤、CD-ROM、光存储器件、磁存储器件、或者上述的任意合适的组合。在本文件中，计算机可读存储介质可以是包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括电磁信号、光信号或上述的合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用适当的介质传输，包括无线、电线、光缆、射频(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++、Ruby、Go，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地 在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络—包括LAN或WAN—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。

Claims (12)

  1. 一种业务数据的共享实现方法，包括：
    第一应用服务平台通过平台间接口，向第二应用服务平台发送业务数据共享请求；
    所述第一应用服务平台接收所述第二应用服务平台通过所述平台间接口反馈的业务数据；
    所述第一应用服务平台，为所述业务数据的所属用户建立虚拟账号，将所述业务数据存储至所述虚拟账号的业务数据空间中；
    所述第一应用服务平台将所述虚拟账号的用户信息以及所述虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
  2. 根据权利要求1所述的方法，其中，所述第一应用服务平台，为所述业务数据的所属用户建立虚拟账号包括：
    所述第一应用服务平台从所述第二应用服务平台接收所述业务数据对应用户的用户信息；
    所述第一应用服务平台将所述用户信息的账号标识创建为虚拟账号的账号标识，将所述用户信息赋值作为所述虚拟账号的用户信息。
  3. 根据权利要求1所述的方法，其中，所述第一应用服务平台，为所述业务数据的所属用户建立虚拟账号包括：
    所述第一应用服务平台从所述第二应用服务平台接收所述业务数据对应用户的用户信息；
    所述第一应用服务平台根据所述用户信息建立与所述用户信息关联的虚拟账号，将所述用户信息赋值作为所述虚拟账号的用户信息。
  4. 根据权利要求1所述的方法，其中：
    所述虚拟账号的业务数据空间与第一应用程序的常规账号的业务数据空间保持一致存储；
    所述虚拟账号的用户信息和所述常规账号的用户信息区别空间存储。
  5. 根据权利要求1所述的方法，所述第一应用服务平台接收所述第二应用服务平台通过所述平台间接口反馈的业务数据，包括：
    在所述第二应用服务平台通过第二应用程序客户端向用户询问是否允许进行业务共享，并获取用户的业务共享授权的情况下，所述第一应用服务平台接收所述第二应用服务平台通过所述平台间接口反馈的业务数据。
  6. 根据权利要求1-5任一项所述的方法，还包括：
    所述第一应用服务平台接收账号注册请求或基于第二应用程序的账号的授权登录请求；
    响应于所述账号注册请求或所述授权登录请求的用户信息与所述虚拟账号的用户信息匹配，将所述虚拟账号的用户信息和业务数据空间与所述账号注册请求或所述授权登录请求的账号进行关联。
  7. 根据权利要求6所述的方法，其中，所述响应于所述账号注册请求的用户信息与所述虚拟账号的用户信息匹配，将所述虚拟账号的用户信息和业务数据空间与所述账号注册请求的账号进行关联，包括：
    响应于所述账号注册请求的用户信息与所述虚拟账号的用户信息匹配，将所述虚拟账号变更为第一应用程序的常规账号，并将得到的所述常规账号作为所述第一应用服务平台根据所述账号注册请求建立的新账号，反馈至所述第一应用程序客户端。
  8. 根据权利要求6所述的方法，其中，所述响应于所述授权登录请求的用户信息与所述虚拟账号的用户信息匹配，将所述虚拟账号的用户信息和业务数据空间与所述授权登录请求的账号进行关联，包括：
    响应于所述授权登录请求的用户信息与所述虚拟账号的用户信息匹配，将所述虚拟账号变更为第一应用程序的常规账号，并将得到的所述常规账号反馈给所述第一应用程序客户端。
  9. 一种业务数据的共享实现装置，配置于第一应用服务平台，包括：
    共享请求发送模块，设置为通过平台间接口，向第二应用服务平台发送业务数据共享请求；
    业务数据接收模块，设置为接收所述第二应用服务平台通过所述平台间接口反馈的业务数据；
    虚拟账号建立模块，设置为为所述业务数据的所属用户建立虚拟账号，将 所述业务数据存储至所述虚拟账号的业务数据空间中；
    业务数据推送模块，设置为将所述虚拟账号的用户信息以及所述虚拟账号对应的业务数据通过第一应用程序客户端进行推送。
  10. 根据权利要求9所述的装置，其中，所述虚拟账号建立模块包括：
    第一信息接收单元，设置为从所述第二应用服务平台接收所述业务数据对应用户的用户信息；
    第一账号创建单元，设置为将所述用户信息的账号标识直接创建为虚拟账号的账号标识，将所述用户信息赋值作为所述虚拟账号的用户信息。
  11. 一种计算机设备，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-8任一项所述的方法。
  12. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-8任一项所述的方法。
PCT/CN2019/097423 2018-07-27 2019-07-24 业务数据的共享实现方法、装置、设备和存储介质 WO2020020203A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810846837.6 2018-07-27
CN201810846837.6A CN109600349B (zh) 2018-07-27 2018-07-27 一种业务数据的共享实现方法、装置、设备和介质

Publications (1)

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

Family

ID=65956423

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/097423 WO2020020203A1 (zh) 2018-07-27 2019-07-24 业务数据的共享实现方法、装置、设备和存储介质

Country Status (2)

Country Link
CN (1) CN109600349B (zh)
WO (1) WO2020020203A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112190951A (zh) * 2020-10-28 2021-01-08 网易（杭州）网络有限公司 运营数据迁移方法、装置、设备及存储介质
CN113254969A (zh) * 2021-06-08 2021-08-13 挂号网（杭州）科技有限公司 业务数据处理方法、装置、电子设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600349B (zh) * 2018-07-27 2020-01-17 北京字节跳动网络技术有限公司 一种业务数据的共享实现方法、装置、设备和介质
CN110287255A (zh) * 2019-05-23 2019-09-27 深圳壹账通智能科技有限公司 基于用户行为的数据共享方法、装置及计算机设备
CN110719343B (zh) * 2019-09-12 2022-04-22 厦门网宿有限公司 业务加速处理方法及系统、入口及出口网络设备
CN113313597B (zh) * 2020-02-26 2023-09-26 京东科技控股股份有限公司 产品组合的推荐方法、装置及系统、存储介质、电子装置
CN113242310B (zh) * 2020-06-30 2024-04-12 浙江口碑网络技术有限公司 基于小程序实现服务的方法及装置
CN113507464B (zh) * 2021-07-06 2023-10-13 深圳市吉芯微半导体有限公司 基于虚拟设备的数据访问方法、装置、设备及存储介质
CN116913491B (zh) * 2023-07-20 2024-09-03 苏州市立医院 一种慢性创面修复医联体信息服务平台及控制方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103384237A (zh) * 2012-05-04 2013-11-06 华为技术有限公司 一种共享IaaS业务云账号的方法、及共享平台和网络装置
US20140081909A1 (en) * 2012-09-14 2014-03-20 Salesforce.Com, Inc. Linking social media posts to a customers account
CN104348895A (zh) * 2013-08-09 2015-02-11 腾讯科技（深圳）有限公司 移动终端中程序间共享数据的方法及装置
CN106033312A (zh) * 2015-03-12 2016-10-19 宏碁股份有限公司 应用程序分享方法及电子装置
CN109600349A (zh) * 2018-07-27 2019-04-09 北京字节跳动网络技术有限公司 一种业务数据的共享实现方法、装置、设备和介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101751435A (zh) * 2008-12-17 2010-06-23 北京市电力公司 用于电力系统的数据交换系统及方法
CN105100878B (zh) * 2014-05-08 2018-07-17 Tcl集团股份有限公司 一种电视节目分享方法及系统
CN104539639A (zh) * 2014-10-20 2015-04-22 小米科技有限责任公司 用户信息采集方法和装置
CN105897726A (zh) * 2016-05-09 2016-08-24 深圳市永兴元科技有限公司 关联账号数据共享方法和装置
CN105869092A (zh) * 2016-05-26 2016-08-17 湖南洋达信息科技有限公司 智能化校园管理平台
US10409816B2 (en) * 2016-08-23 2019-09-10 Salesforce.Com, Inc. Accessing and displaying shared data
CN107038078A (zh) * 2017-03-13 2017-08-11 联想(北京)有限公司 一种信息分享方法及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103384237A (zh) * 2012-05-04 2013-11-06 华为技术有限公司 一种共享IaaS业务云账号的方法、及共享平台和网络装置
US20140081909A1 (en) * 2012-09-14 2014-03-20 Salesforce.Com, Inc. Linking social media posts to a customers account
CN104348895A (zh) * 2013-08-09 2015-02-11 腾讯科技（深圳）有限公司 移动终端中程序间共享数据的方法及装置
CN106033312A (zh) * 2015-03-12 2016-10-19 宏碁股份有限公司 应用程序分享方法及电子装置
CN109600349A (zh) * 2018-07-27 2019-04-09 北京字节跳动网络技术有限公司 一种业务数据的共享实现方法、装置、设备和介质

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112190951A (zh) * 2020-10-28 2021-01-08 网易（杭州）网络有限公司 运营数据迁移方法、装置、设备及存储介质
CN112190951B (zh) * 2020-10-28 2024-02-09 网易（杭州）网络有限公司 运营数据迁移方法、装置、设备及存储介质
CN113254969A (zh) * 2021-06-08 2021-08-13 挂号网（杭州）科技有限公司 业务数据处理方法、装置、电子设备及存储介质
CN113254969B (zh) * 2021-06-08 2022-10-11 挂号网（杭州）科技有限公司 业务数据处理方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN109600349A (zh) 2019-04-09
CN109600349B (zh) 2020-01-17

Similar Documents

Publication Publication Date Title
WO2020020203A1 (zh) 业务数据的共享实现方法、装置、设备和存储介质
US10412061B2 (en) Method and system for encrypted communications
US10505982B2 (en) Managing security agents in a distributed environment
CN111541768B (zh) 企业系统中的设备上的应用的统一供应
US10963945B2 (en) Method and server for registering a customized device
US20210014061A1 (en) Identity proofing offering for customers and non-customers
KR20180115937A (ko) 대화형 콘텐츠 제공 시스템
US9753786B2 (en) Client server communication system
WO2020020202A1 (zh) 应用程序的账号管理方法、装置、设备和介质
JP6882924B2 (ja) 互いに異なるユーザ識別体系を利用して登録されたユーザを識別するサーバ間のサービス連動方法、システムおよびコンピュータプログラム
US10003969B2 (en) Communication between mobile devices and mobile wallet architectures
CN109154968B (zh) 用于组织内的安全且高效的通信的系统和方法
US10908970B1 (en) Data interface for secure analytic data system integration
US11082813B2 (en) Message-based management service enrollment
US20180337922A1 (en) Method and device for controlling smart device, server and storage medium
CN103997482A (zh) 桌面云业务中用户登录的方法、系统
US9641512B2 (en) Identity protocol translation gateway
US9760412B2 (en) Client server communication system
US10482397B2 (en) Managing identifiers
US9159078B2 (en) Managing identifiers
CN113641966B (zh) 一种应用集成方法、系统、设备及介质
US20210303655A1 (en) Real-time equivalent user interaction generation
TW201915916A (zh) 提供保險服務的方法及保險服務系統
KR20150115237A (ko) 클라우드 컴퓨팅 방법, 이를 수행하는 클라우드 컴퓨팅 서버 및 이를 저장하는 기록매체

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: 19840684

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 1205 DATED 14/05/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19840684

Country of ref document: EP

Kind code of ref document: A1