CN116702104A

CN116702104A - Method, device, equipment and storage medium for associating account information

Info

Publication number: CN116702104A
Application number: CN202310989263.9A
Authority: CN
Inventors: 吕晓宁; 王野; 刘俊岭
Original assignee: Ali Health Technology China Co ltd
Current assignee: Ali Health Technology China Co ltd
Priority date: 2023-08-08
Filing date: 2023-08-08
Publication date: 2023-09-05
Anticipated expiration: 2043-08-08
Also published as: CN116702104B

Abstract

The embodiment of the application provides a method, a device, equipment and a storage medium for associating account information. The method comprises the following steps: receiving feedback information generated after the first system newly adds first account information in the associated account set of the designated account; the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the association account set comprises account information of at least one account which has association relation with the appointed account; acquiring second account information of the target user in a second system; and storing the first account information and the second account information in an associated mode. And receiving feedback information generated after the first account information is newly added in the association account set of the designated account, and acquiring the first account information from the feedback information, so that the first account information and the second account information are stored in an association manner, and the association of account information of the same user in different systems is realized.

Description

Method, device, equipment and storage medium for associating account information

Technical Field

The embodiment of the application relates to the technical field of computer networks, in particular to a method, a device, equipment and a storage medium for associating account information.

Background

With the development of internet technology, users can conveniently use different internet services. However, the systems providing different internet services may be different. In particular, different systems may belong to different vendors. The user needs to register the account number of the corresponding internet service when using different internet services. In some cases, when the user performs some matters, the user may operate multiple systems, and the user accounts between the multiple systems are independent, so that the user is required to operate for each system separately. The user's operations in each system are relatively independent, so that the user's operations may be cumbersome.

Disclosure of Invention

In view of this, various embodiments of the present application are directed to providing a method, apparatus, device, and storage medium for associating account information, which can improve the convenience of associating operations of users in a plurality of systems to a certain extent.

The application provides a method for associating account information, which comprises the following steps: receiving feedback information generated after the first system newly adds first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the association account set comprises account information of at least one account which has association relation with the appointed account; acquiring second account information of the target user in a second system; and storing the first account information and the second account information in an associated mode.

One embodiment of the present application provides an apparatus for associating account information, the apparatus including: the receiving module is used for receiving feedback information generated after the first system newly adds the first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the association account set comprises account information of at least one account which has association relation with the appointed account; the acquisition module is used for acquiring second account information of the target user in a second system; and the association module is used for associating and storing the first account information and the second account information.

The embodiment of the application provides a computer device, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to realize the method in the embodiment.

Embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the method described in the above embodiments.

According to the embodiments provided by the application, the association relation between the account information corresponding to the same user account in different systems can be constructed by receiving the feedback information including the first account information fed back by the first system and acquiring the second account information of the same target user corresponding to the first account information in the second system, and further carrying out association storage on the first account information and the second account information. The feedback information may be data generated by the first system after adding the first account information in an associated account set of the designated account, where the associated account set may include account information of at least one account having an association relationship with the designated account. Therefore, by means of the feedback information corresponding to the designated account, the first account information of the target user in the first system can be obtained more conveniently, and the account information of the same user in different systems can be associated. Furthermore, in the subsequent use process, the functional interaction can be performed for the association operation between different systems based on the account with association, so that the convenience is improved.

Drawings

Fig. 1 is a schematic diagram of interactions between different ends of an account information association system according to an embodiment of the present application.

Fig. 2 is a flowchart of a method for associating account information according to an embodiment of the present application.

Fig. 3 is a schematic diagram of an apparatus for associating account information according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a computer device according to an embodiment of the present application.

Detailed Description

In the related art, a user can conveniently use different internet services. However, the home parties of the systems providing different internet services may be different. Thus, it is more difficult to get through data in different internet services from a business perspective. Or, from the data security perspective, it is difficult to achieve data sharing between different internet services.

Therefore, it is necessary to provide a method, an apparatus, a device, and a storage medium for associating and storing first account information and second account information by combining feedback information including the first account information, which is received from a first system, with second account information of the same target user corresponding to the first account information in an acquired second system. The feedback information may be data generated by the first system after adding the first account information in an associated account set of the designated account, and the associated account set may include account information of at least one account having an association relationship with the designated account. Therefore, by means of the feedback information corresponding to the designated account, the first account information of the target user in the first system can be obtained more conveniently, and therefore association of account information of the same user in different systems is achieved, functional interaction can be conducted for association operation among different systems based on the account with association in a subsequent use process, and convenience is improved.

Referring to fig. 1, an application scenario example of an account information association system is provided in the present application.

The association system of account information may involve a first system, a second system, and a server running an association method of account information. The first system can provide instant communication service for a plurality of user accounts. The second system may provide online medication purchase services for the user account. The same user has different user accounts in the first system and the second system. The account information corresponding to the same user in the first system and the second system is at least partially different.

The user of the associated system of account information may be a service operator of a service provided by means of the first system and the second system. A designated account for the corresponding service operator may be included in the first system. The designated account may also be referred to as an operational account. A business operator may wish to follow up in real time the condition of a diabetic patient. In particular, diabetics may also be users of the first and second systems. A business operator may wish to follow up with the patient's condition by data generated by diabetics in the first and second systems. However, the account of the diabetic patient in the first system and the account of the second system are independent of each other, and data communication cannot be achieved. That is, it is difficult for the business operator to distinguish whether one account in the first system and one account in the second system correspond to the same diabetic patient. Therefore, the service operator may wish to correlate the account information corresponding to the same diabetic patient in the first system and the second system through the account information correlation system, so as to count the data generated by the same diabetic patient in different systems, achieve more accurate acquisition of the change of the diabetes patient condition, and provide condition control advice for the diabetes patient in a targeted manner.

The server may place a short link for the diabetic to direct the diabetic to add an operating account of the operator using the user account in the first system. Specifically, the server may first obtain a record of the purchase of the drug by the user in the second system. For a user who purchased a diabetic drug, the user can be identified as a diabetic. Then, the server may use the identity of the account of the user in the second system and the service identifier corresponding to diabetes to invoke the short link generation service to construct a specified short link corresponding to the user. The domain name of the designated short link may point to the server, and the path of the designated short link may be formed by the short link parameter. The short link parameters may include an identity of the user in the second system, a business identity indicating diabetes, etc. The short links corresponding to different users may be different.

The server can send the appointed short link to the corresponding user in a short message mode. The user's terminal may receive the corresponding designated short link.

The target user may click on the received specified short link at the corresponding terminal. The terminal may issue an access request to the server based on the specified short link. After receiving the access request sent by the terminal, the server can analyze the identity of the account of the target user in the second system and the service identifier corresponding to the target user in the designated short link. The account of the target user in the second system may be a second account. Further, the server may obtain, in the operation account set, an account identifier corresponding to the operation account of the diabetic patient according to the service identifier. Then, the server may invoke the graphic code generating service of the first system, and use the identity of the second account of the target user and the account identifier of the operation account as input of the graphic code generating service to generate the graphic code of the account identifier of the corresponding operation account. The graphic code can be a two-dimensional code and can be used for adding an operation account to an account in the first system. The graphic code may also carry an identity of the target user in the second system. After the server obtains the graphic code, the graphic code can be used for responding to the access request of the target user and feeding back the graphic code to the terminal corresponding to the target user.

The target user can scan the graphic code at the terminal and jump to a friend adding interface aiming at the operation account in the client side of the first system. The client of the first system may also log in to a user account of the target user. The account of the target user in the first system may be a first account. And the target user can click a friend adding control in the friend adding interface at the terminal, and send a friend adding request aiming at the operation account to the first system. The friend addition request may be an association request for an operation account, for requesting establishment of an association relationship between the first account and the operation account. The terminal can also send the identity of the second account of the target user in the second system carried by the graphic code to the first system as an attached parameter of the friend adding request. After receiving the friend adding request, the first system can add the first account information of the first account of the target user into the associated account set corresponding to the operation account so as to establish the instant messaging relationship between the first account and the operation account. I.e. the first account and the operational account are added as friends.

After the first account information is newly added in the associated account set of the operation account, the first system can generate feedback information based on data related to the friend adding request and send the feedback information to the address of the designated server in the operation account. The feedback information may include first account information of the target user and an identity of a second account of the target user in the second system, which is carried by the graphic code.

After receiving the feedback information provided by the first system, the server can identify the identity of the second account of the target user in the second system and the first account information. The server may then request the second account information of the target user in the second system from the second system by the identity of the target user in the second system. The second system may send second account information of a second account of the target user in the second system to the server in response to the acquisition request of the server. After the server acquires the first account information and the second account information of the target user, a mapping relationship between the first account information and the second account information can be established and stored in a memory of the server.

In the following process of the diabetes patient, the server can inquire the frequency of purchasing medicines in the second account of the target user in the second system, and according to the frequency of purchasing medicines in the second account, diabetes control suggestions corresponding to the target user can be generated. Further, the diabetes control advice can be sent to the first account of the target user through the operation account in the first system, so that convenience and user experience of receiving the advice by the target user are improved.

The embodiment of the application provides an account information association system. The association system of account information may involve a first system and a second system. The association system of account information may include a terminal and at least one server. The server side of the first system and the second system can be deployed in a server. The clients of the first system and the second system may be installed at the terminal.

The terminal may be an electronic device having network access capabilities. Specifically, for example, the terminal may be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, a shopping terminal, a television, a smart speaker, a microphone, and the like. Wherein, intelligent wearable equipment includes but is not limited to intelligent bracelet, intelligent wrist-watch, intelligent glasses, intelligent helmet, intelligent necklace etc..

The server may be an electronic device with some arithmetic processing capability. Which may have a network communication module, a processor, memory, and the like. Of course, the server may also refer to software running in the electronic device. The server may also be a distributed server, and may be a system having a plurality of processors, memories, network communication modules, etc. operating in concert. Alternatively, the server may be a server cluster formed for several servers. Or, with the development of science and technology, the server may also be a new technical means capable of realizing the corresponding functions of the embodiment of the specification. For example, a new form of "server" based on quantum computing implementation may be possible.

Referring to fig. 2, an embodiment of the present application provides a method for associating account information. The association method of the account information can be applied to a server. The association method of account information may include the following steps.

Step S110: receiving feedback information generated after the first system newly adds first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the associated account set comprises account information of at least one account which has an association relationship with the designated account.

In some cases, the first system may generate feedback information corresponding to the newly added behavior after newly adding account information in the associated account set of the designated account. The server may determine the newly added account information according to the feedback information, and further, may further match the account information with account information of the same user in the second system.

In this embodiment, the first system may represent software, hardware, or an entirety of software and hardware capable of providing the first service. Where the first service may represent the ability of the first system to provide certain functions, resources, or information to other applications or users. The first system can be deployed on a server to which the association method of account information is applied, and can also be deployed on other servers.

In this embodiment, the first system may maintain account information for a plurality of user accounts. The designated account may be one of a plurality of user accounts maintained by the first system. Wherein each user account may be maintained with a corresponding set of associated accounts. The associated account set may include account information of an account having an association relationship with the corresponding user account. An account having an association with a corresponding user account may be an associated account of the corresponding user account. Accordingly, the set of associated accounts may represent a collection of account information for the associated account of the user account. By adding account information in the associated account set, an association relationship between the corresponding user accounts can be established. For example, after the account information of the user a is added to the associated account set corresponding to the user B, an association relationship between the user a and the user B may be established. According to the first service provided by the first system, rights of using the specified functions provided by the first service can be obtained between user accounts with an association relationship.

Specifically, for example, the first system may be instant messaging software, and may provide the user with a first service for sending messages in real time between specified user accounts. For example, the first system may be software with a network short message sending function, or may be an application program with a chat function such as a nail. Accordingly, the associated account set maintained in the instant messaging software for each user account may represent other user accounts that are capable of communicating between the user accounts. For example, for a pinned application, the user account in the set of associated accounts may represent friends of the user account. The set of associated accounts may correspond to a buddy list of the user account. Accordingly, newly adding a user account in the set of associated accounts may represent adding friends. For software with a network short message sending function, the associated account set may also represent an object capable of sending a network short message through a corresponding user account. For example, software with a network sms sending function may have a limitation on the receiving party of the network sms, and the user account may only send the network sms for other user accounts joining in the associated account set. Accordingly, adding a user account to the set of associated accounts may represent adding objects that can be sent.

In some embodiments, the first system may also be life service class software. The lifestyle software may present store information for the user for each store and score the store. For example, a given mall may add a store in the life service class software where the mall resides to be presented to the store in the user's mall and to score a mall account maintained by the corresponding life service class software. The account information in the associated account set to which the mall account may correspond may represent a store that is affiliated with the mall. The newly added account information in the associated account set may represent a store newly added at the mall.

In this embodiment, the designated account may represent a user account in which an action of newly adding account information occurs. The designated account may be an account in the first system. The newly added account information in the first system may be used as the first account information. The account number newly added in the first system may be a first account. The first account information may be account information of a first account. The user corresponding to the first account information is a target user. The first account information may only be able to characterize the target user at the first system. In some cases, the same account information as the first account information may also be present in other systems, but the user that the account information characterizes may not be the target user in other systems.

In this embodiment, the first system may send feedback information to the server after newly adding the first account information in the associated account set of the designated account. Specifically, the first system may feed back the feedback information to the designated account. Of course, the first system may also feed back feedback information to the specified feedback address set by the specified account. In some embodiments, the specified feedback address may point to the server.

In this embodiment, the feedback information may include data related to one action of adding the first account information. Specifically, the feedback information may include an account identifier of the designated account, newly added first account information, time of newly added first account information, information carried by the first account information when requesting to be newly added to an associated account set of the designated account, and the like. For example, the information carried when requesting an associated account set that is newly added to the designated account may include the identity of the target user at the second system. In some embodiments, the feedback information may also include account information specifying an account, and the like.

In this embodiment, the method for receiving feedback information generated after the first system newly adds the first account information in the associated account set of the designated account may be that the first system automatically sends the feedback information to the designated account or the designated feedback address after triggering the action of newly adding the first account information in the associated account set of the designated account. Of course, the method for receiving the feedback information generated by the first system after the first account information is newly added in the associated account set of the designated account may also be that the server actively obtains the feedback information from the first system. The actively acquired server may be a server pointed by a designated feedback address, or may be acquired from the first system after other servers acquire the acquisition authority of the feedback information according to the designated key.

Step S120: and acquiring second account information of the target user in a second system.

In some cases, after the feedback information of the first system is obtained, the newly added first account information may be identified. Further, second account information of the same user corresponding to the first account information in the second system can be stored in an associated mode, so that an association relationship between the first account information and the second account information is built.

In the present embodiment, the second system may be represented by software, hardware, or a combination of software and hardware that can provide the second service. The second service may represent the ability of the second system to provide certain functions, resources, or information to other applications or users. The second system may also be deployed on a server to which the method of associating account information applies, or on other servers.

Wherein the second system may be different from the first system. In particular, for example, the services provided by the second system and the first system may be different, or the maintainers of the second system and the first system may be different.

In this embodiment, the second system may maintain account information of a plurality of user accounts. The account information corresponding to the same user in the first system and the second system may be at least partially different.

In some implementations, the second system may be an e-commerce shopping platform that may provide online shopping for the user. Alternatively, the second system may also provide news software. The preferences of different user accounts in the news-like software for the news of interest may be different. Accordingly, account information for different user accounts in the second system may be different.

In this embodiment, the second account information may be account information of an account of the target user in the second system. The account of the target user in the second system may be the second account. The second account information may only be able to characterize the target user in the second system. In some cases, the same account information as the second account information may also be present in other systems, but the user that the account information characterizes may not be the target user in other systems.

In this embodiment, the second system may provide account information of the user. The method for obtaining the second account information of the target user in the second system may be that the second account information of the target user is queried by calling an interface provided by the second system through the identity of the target user. In some embodiments, the method of associating account information may be applied to a second system. The server has access to a database of the second system. Correspondingly, the method for obtaining the second account information of the target user in the second system may be that the second account information of the target user is queried in a database of the second system.

Step S130: and storing the first account information and the second account information in an associated mode.

In some cases, the first account information and the second account information corresponding to the target user are stored in an associated mode, so that an association relationship can be established among a plurality of accounts corresponding to the same user in different systems, and the communication of data in the different systems is facilitated.

In this embodiment, the method for storing the first account information and the second account information in an associated manner may store the first account identifier of the first account and the second account identifier of the second account in an associated manner, so as to indicate an association relationship between the first account information and the second account information. The first account identifier and the second account identifier may indicate the first account information and the second account information, respectively, by the user. Specifically, for example, in a data table, there may be a plurality of fields. Each field may correspond to an account identification indicating account information in one system. Correspondingly, in the data table for storing the first account identifier and the second account identifier in an associated manner, the fields can comprise a first field for storing the first account identifier and a second field for storing the second account identifier, and the first account identifier and the second account identifier which are in the same record can represent an associated relationship. In some embodiments, the method for storing the first account information and the second account information in an associated manner may also be to store the associated first account information and the second account in two storage areas adjacent to each other according to the memory address.

In some cases, the account of the target user in the first system is taken as a first account; the first system adds the first account information in the association account set after receiving the association request for the designated account sent by the first account; the feedback information comprises request parameters carried by the association request; the request parameters comprise account identifiers of the designated accounts and an acquisition mode of acquiring the account identifiers by the first accounts; the association method of account information may further include: and executing the step of acquiring the second account information of the target user in a second system and storing the first account information and the second account information in a correlated manner under the condition that the acquisition mode meets the specified condition.

In some cases, the first system may not add the first account information in the set of associated accounts of the specified account until after the first account issues an association request for the specified account. The feedback information may include an association request with a request parameter. The request parameters may include the first account obtaining account information of the designated account. Therefore, by judging whether the acquisition mode meets the specified condition, the waste of the calculation force of the server can be reduced to a certain extent.

In this embodiment, the first account may represent an account of the target user in the first system.

In this embodiment, the association request may represent a request sent by a first account in the first system to the first system, where the request is used to request that first account information be newly added in the association account set of the designated account. Specifically, for example, in the case where the first system is instant messaging software, the association request may indicate that the first account requests to establish the communication authority with the designated account. The request to establish communication rights with the specified account may indicate that the specified account adds the first account as a friend. Of course, in the case that the first system is life service software, and the designated account may represent a store where the life service software is resident, the first account may represent a store where the store is resident, and the association request may represent that the first account requests the first system to incorporate the first system into an association account set corresponding to the store.

In this embodiment, the association request may carry a request parameter. The request parameters may include data of a requester of the association request, data of a designated account for which the association request is directed, data generated by the requester in a process of issuing the association request, and the like. Specifically, for example, the request parameter may include an account identifier of the designated account, account information of the first account, a type of the association request, custom data added by the first account in the association request, and so on. And the first system can identify the first account and a designated account corresponding to the associated account set which is requested to be added by the first account according to the request parameters. And, the first system may also generate feedback information to be fed back to the server according to the request parameter.

In this embodiment, the feedback information may include the request parameter. Specifically, the feedback information may also include account identification of the designated account, account information of the first account, a type of the association request, custom data added in the association request by the first account, and the like.

In some cases, the first account may need to obtain an account identification for the specified account before an association request for the specified account may be sent to the first system. Specifically, for example, in instant messaging software, the first account needs not to add friends with the designated account until after the account ID, the mobile phone number, or the account nickname of the designated account are identified.

In this embodiment, the account identifier of the designated account may be represented in various forms. For example, the account identification of the specified account may be a user identification (User Identification, UID) of the specified account. Or, the account identifier of the designated account may also be the mobile phone number, name, etc. corresponding to the designated account.

In this embodiment, the request parameter may further include an acquisition manner of the account identifier. There may be a plurality of ways in which the first account obtains the account identifier of the designated account. Specifically, for example, the server may send, to the user, an account identifier of the designated account, such as a mobile phone number corresponding to the designated account or a user identification of the designated account through a short message. The user can input the mobile phone number or the user identification corresponding to the appointed account on the corresponding terminal through the account searching service provided by the client of the second system, inquire to obtain the appointed account, and display the association request page of the appointed account on the terminal. The user may make the association request through an association request page. Or the first system can also provide the graphic code to the user, and the user can scan the graphic code through the terminal to obtain the account identification of the designated account. Meanwhile, the terminal can automatically jump to the association request page of the designated account after the graphic code is scanned.

In this embodiment, the terminal may identify the acquisition method by specifying the identifier, and when the user issues the association request, the terminal may attach the acquisition method to the association request. Of course, in some cases the terminal may not recognize the partial acquisition mode. Accordingly, the terminal may use the designated symbol to indicate that the partial acquisition mode cannot be recognized.

In some cases, only by obtaining the account identifier of the designated account in a qualified obtaining manner and sending an association request based on the account identifier, the server can identify the account of the target user in the second system and the account in the first system, so that the first account information and the second account information are associated and stored. Specifically, when the association request is sent out, the acquiring mode meeting the condition can enable the association request to carry the identification of the account of the target user in the second system. The identity of the account of the target user in the second system may be or correspond to the identity of the target user. Specifically, for example, the server may encode the account identifier of the designated account number and the identity identifier of the target user in the second system to form a section of encoded instruction text through a short message. The user may copy the encoded instruction text on the terminal. Correspondingly, when the user opens the client of the second system, the client can analyze the identity of the account identification target user of the appointed account in the second system in the coding instruction. And, when the user issues an association request, the client of the second system may carry information in the encoded instruction in the association request. Furthermore, the first system can also generate feedback information according to the information in the coding instruction and send the feedback information to the server. The server can identify a first account of the target user in the first system and a second account of the target user in the second system by analyzing the feedback information, so that the first account information and the second account information are stored in an associated mode. Therefore, in this embodiment, the feedback information may include an acquisition method. The server may perform the step of acquiring the second account information of the target user in the second system and the step of storing the first account information and the second account information in association with each other, if the acquisition mode is identified to meet the specified condition.

In some embodiments, the acquiring manner meeting the specified condition may include: the account identification is obtained by scanning the graphic code of the designated account according to the terminal corresponding to the first account.

In this embodiment, the graphic code may be a graphic bar code obtained by specifying the encoding method. The graphic code can be a one-dimensional code or a two-dimensional code. The graphic code can be generated according to an account identifier of a designated account in the first system. Accordingly, the graphic code may represent an account identification of the designated account. Of course, the graphic code may also be generated together according to the account identifier of the designated account and the identity identifier of the target user in the second system. In some real-time modes, the graphic codes can be pre-generated and stored in a server, and are delivered to users at appointed time according to service requirements. Of course, the graphic code can also generate feedback to the user in real time after the user triggers the specified behavior.

In some embodiments, the graphic code may be a terminal provided by the server to the target user, or may be a terminal provided by the first system to the target user.

In some implementations, the graphical code may be generated by any device. Specifically, for example, the graphic code may be a server build generation deployed by an association method of account information. Of course, the graphics code may also be generated by the server invoking an interface of the graphics code generation service provided by the first system. Alternatively, the graphic may be generated by an interface of the server calling a graphic code generation service provided by the second system.

The account identification of the appointed account can be conveniently provided for the user through the graphic code, and data needed on the service can be flexibly encoded into the graphic code, so that the service can be conveniently developed. For example, the identity of the target user in the second system may be encoded therein.

In some embodiments, the acquiring manner meeting the specified condition may further include: and analyzing the code instruction text generated according to the identity of the target account in the second system and the account identification of the designated account by the terminal.

In some embodiments, the method for associating account information may further include: constructing a designated short link for associating the designated account; wherein the designated short link includes a short link parameter representing an account identification of the designated account; the appointed short link is put in a terminal corresponding to the target user; under the condition that the terminal sends an access request aiming at the short link, analyzing account identification in the short link parameter; invoking a graphic code generation service of the first system to generate the graphic code corresponding to the account identifier; the graphic code is provided to the terminal to display the graphic code at the terminal.

In some cases, the target user may associate a first account of the target user in the first system with the designated account only after obtaining the account identification of the designated account. That is, account information of the first account is newly added to the associated account set of the designated account. Therefore, the server may provide the account identification of the designated account to the terminal corresponding to the user in advance.

In this embodiment, the designated interface can be accessed by constructing a short link. The server puts short links into the user and provides information related to account identification in the appointed interface, so that a channel for associating own accounts with the appointed accounts can be provided for the user efficiently and conveniently.

In this embodiment, the designated short link may be used to associate a first account of the target user in the first system with a designated account in the first system. Specifically, the user may jump to the designated interface after the terminal clicks the designated short link. The graphic code corresponding to the account identification of the designated account can be provided through the designated interface, and the user can execute the operation of associating the account with the designated account according to the content provided by the designated interface. The designated interface may be an interface provided by a browser, or may be an interface provided by an applet or a terminal application.

In this embodiment, the short link may include a domain name and a short link parameter. Wherein the short link domain name may point to the server. The short link parameter of the short link may be a short link path, or the short link parameter may be encoded to form a short link path. The short link parameters of the short link may represent information carried by the short link. For example, the short link parameter may include a name of a user targeted for delivery, a mobile phone number, a service identifier of a delivery service corresponding to the short link, an identifier of a main body executing the service, and the like.

In this embodiment, the method for constructing the specified short link for associating the specified account may be that the server first splices the pre-specified long link address and the short link parameter specified for the short link. Then, the spliced sequences can be encoded into shorter sequences by using a designated encoding mode, and the shorter sequences can be used as paths of short links. The short link path may be generated by combining the short link path with a domain name specified by the server. In some embodiments, the spliced sequence can also be directly used as a path of the short link, and the specified short link is formed by combining with a domain name specified by the server.

In some embodiments, the short link parameter may further include an identity of the target user in a second system.

In this embodiment, after the specified short link is built, the specified short link may be put into a terminal corresponding to the target user. The method of delivering to the terminal corresponding to the target user can be sent to the target user in a short message mode, or can be displayed to the target user by being embedded in an application program appointed by the target user terminal. For example, it may be embedded in the news software or social software of the target user.

In this embodiment, account identification of a designated account may be used to refer to the designated account. In some embodiments, the designated account may represent an operational account of a business operator. In some cases, there may be multiple operating accounts for the same service. Accordingly, the account number identification of the designated account may also be used to indicate the identification that the plurality of operating accounts form the operating account set. Wherein, the identification of the operation account set can be the same as or similar to the identification of the corresponding service.

In this embodiment, the designating short link may be a server in which an association method of account information is deployed. Accordingly, after the terminal clicks the designated short link, the user may send an access request to the server. The server may analyze the account identifier in the short link parameter after receiving the access request sent by the terminal for the short link. Of course, the server may also parse other information included in the short link parameters. Aiming at the short link parameters coded by the appointed coding mode, the short link parameters can be decoded by the corresponding decryption mode. Or, for the short link formed by splicing the short link parameters only, the analysis method can identify the parameters of the designated position through the separator of the splicing process, and confirm the account identification of the designated account.

In this embodiment, the first system may be provided with a graphic code generation service. After the account identifier of the designated account is obtained, the server can call a graphic code generating service of the first system to generate the graphic code corresponding to the account identifier. Wherein the server may take the account identification of the designated account as input to the graphical code generation service. Accordingly, the graphic code may be used to represent a designated account in the first system. Further, the server may provide the graphic code to the terminal to present the graphic code at the terminal.

In this embodiment, the user may scan the graphic code through the terminal to identify the designated account in the first system. Further, the user may associate a self account in the first system with a designated account in the first system. Accordingly, the first system may receive an association request for the specified account. Specifically, for example, a user may scan a graphic code through a terminal. The terminal can identify the account identification of the designated account after scanning the graphic code and display the associated page of the designated account. According to the operation of the user on the association page, the user can associate the designated account in the first system with the account of the user. For example, for instant messaging software, the graphical code may be a friend two-dimensional code. The association page displayed after the terminal scans the graphic code can be a confirmation page added by friends. For life service class software. The graphic code may be a mall account of a mall. The association page displayed after the terminal scans the graphic code can be a request page for requesting to join the association account set corresponding to the mall.

In some embodiments, the request parameter may further include an identity indicative of the target user; the step of obtaining the second account information of the target user in the second system comprises the following steps: and acquiring second account information matched with the identity in the second system.

In some cases, after the first system adds the first account information in the associated account set of the designated account, feedback information may be sent to a feedback address preset in the designated account. Wherein the feedback information may include a plurality of feedback items. Wherein the information content carried by each feedback item may be different. The information content carried by the feedback item can comprise default content of the first system, and also can comprise content set by a designated account. For example, the designated account may set the request parameters carried by the association request as the content of the feedback information. The request parameters of the association request may further include an identity that indicates the target user. Further, the server can be matched with a second account of the target user in the second system through the identity, so that the first account information and the second account information are stored in an associated mode.

In this embodiment, the identity may be used to determine account information of the target user in the second system. Specifically, the identification mark may be an account mark of the user on the second account of the second system, or may be other marks indicating the user. Specifically, for example, the identity identifier may also be a mobile phone number, a nickname, etc. of the user. When the user sends out the association request, the user can be required to input the mobile phone number before the first account of the user can be further associated with the designated account. Correspondingly, the server can be matched with a corresponding second account in the second system through the mobile phone number.

In some cases, the user may register with different phone numbers in different systems, thereby making it impossible to associate with the phone numbers. Thus, the identity may also be a user identification of the second account. After the user identification can be put into the user terminal through a short link or other modes, the user identification is automatically carried in the request when the user sends out the association request. Correspondingly, the feedback information can also comprise the user identification of the second account. The server can then match the second account in the second system through the user identification, thereby improving the success rate and accuracy of associating the first account information with the second account information.

In some embodiments, the identity is formed by splicing a check sequence and an identification sequence; the step of obtaining the account information matched with the identity in the second system comprises the following steps: and under the condition that the verification sequence is successfully verified, providing the identification sequence for the second system to obtain the second account information fed back by the second system.

In some cases, different service principals may all use the identity to match to the second account information, but the identity of the second account used by the different service principals may be different. Or, the feedback item storing the identity identifier in the feedback information can also be used for storing other information. In order to more accurately identify the identity, a verification sequence can be added in the identity, when the identity is used, verification can be performed through the verification sequence, and the identity sequence is provided for the second system only when the verification sequence is verified successfully, so that the second account information fed back by the second system is obtained.

In this embodiment, the verification sequence may be a fixed sequence for verification. The verification sequence can be used for verifying the accuracy of the identification sequence, identifying the source of the identification sequence and the like. The identification sequence may represent the target user or a second account of the target user with the second system.

In some embodiments, the account of the target user in the first system is taken as a first account; the first system is provided with instant messaging service; the step of adding the first account information in the associated account set of the designated account represents: establishing instant communication permission between the appointed account and the first account; the second system provides purchasing service of resources; and taking the account of the target user in the second system as a second account.

Specifically, for example, the first system is software such as nails that can implement instant messaging between users. The second system may be an e-commerce platform such as a panda, or the like.

In some embodiments, the account of the target user in the second system may be a second account; the association method of account information may further include: and in the case that the first account in the first system is detected to have the mention action for the specified resource, the second system is instructed to push the specified resource for the second account.

In some cases, the target user may mention the specified resource in the first system. Correspondingly, after the first account and the second account of the target user are associated, the designated resources can be pushed in the second account of the target user in the second system, so that convenience of the user is improved. In particular, for example, the target user may be mentioned in the first system that the latest glycemic index is high. Accordingly, the server may instruct the second system to push the hypoglycemic agent to the second account of the target user.

In some implementations, the target user may mention the specified resources for the specified account. In particular, for example, a designated account may have business capabilities in terms of medical consultation or medical consultation. The target user may consult the designated account for a diabetes-related condition through the first account. For example, the user may ask "I am now blood glucose 14, praise" to the designated account. Accordingly, after the designated account answers and recognizes that the blood glucose is high, the second system may be instructed to push the blood glucose-lowering medication to the second account of the target user. The method for pushing the medicine for reducing blood sugar to the second account by the second system can be that the second system actively sends the recommended information of the medicine to the terminal corresponding to the target user, or can display the medicine in the recommended column or display the medicine in a popup window mode in the client of the second system logged in by the second account.

In this embodiment, the specified resource may refer to any item in the real world. For example, the specified resource may refer to an electronic product, a pharmaceutical, a property, and the like. Of course, the specified resource may also refer to any item in the virtual world. Such as game gear, etc.

In some embodiments, the account of the target user in the second system is a second account; the association method of the account information further comprises the following steps: and under the condition that the second account in the second system is detected to generate purchasing behavior aiming at the appointed resource, the first system is instructed to send the resource information of the appointed resource to the first account through the appointed account.

In some cases, the target user may have purchased the specified resource in the second system. Accordingly, the server may instruct the first system to send the resource information of the specified resource to the target user through the specified account. Specifically, for example, the target user may purchase the electronic product in an e-commerce platform. Accordingly, the server may instruct the first system to send the specification of the electronic product to the target user through the designated account. Of course, the target user may purchase the drug at the e-commerce platform, and accordingly, the server may instruct the first system to send the drug instructions, and the disease-related advice, to the target user via the designated account.

In some embodiments, the first system may be a lifestyle service-like software, and correspondingly, the second system may also be an e-commerce platform. Specifically, for example, the designated account may be an account of a mall designated in the first system. Staff at the mall can maintain the account of the mall and manage the account of the store in the living service class software. The drainage may be performed by exposing store information contained in the store in the lifestyle service-like software. A store hosting the mall may request to join a corresponding set of store accounts for the mall. The store may score the store to adjust the order in which the store is presented in the living service class software. However, many stores may be online on an e-commerce platform, and the sales of online stores is also an important factor in scoring stores. Mall accounts are difficult to manage data to online stores and thus cannot be scored accurately. Therefore, by the account information association method, the account information of the store in the life service software and the account information of the store in the e-commerce platform can be associated. The store account can rank stores more accurately and comprehensively by capturing data such as the attention degree of the same store in the living service software, the sales volume in the e-commerce platform and the like.

In some embodiments, data is isolated between the first system and the second system. In particular, for example, the first system and the second system may be provided and maintained by different providers. Thus, the account information of the users of the two are data isolated. That is, the account information in the first system and the account information in the second system do not interfere with each other or affect each other, and are not associated with each other or correspond to ss during the operation of the respective systems.

Therefore, by the method for associating account information provided by the embodiment of the application, after the account information of the first system and the account information of the second system are associated with the account information of the same user, data are communicated to a certain extent, and a comprehensive and consistent data view is formed, so that the effects of improving service decision efficiency, reducing data redundancy to a certain extent, improving user experience and the like are achieved.

Referring to fig. 3, an embodiment of the present application further provides an apparatus for associating account information. The association device of the account information can comprise a receiving module, an obtaining module and an association module.

The receiving module is used for receiving feedback information generated after the first system newly adds the first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the associated account set comprises account information of at least one account which has an association relationship with the designated account.

And the acquisition module is used for acquiring the second account information of the target user in a second system.

And the association module is used for associating and storing the first account information and the second account information.

Specific functions and effects achieved by the account information association device can be explained in reference to other embodiments of the present application, and are not described herein. The various modules in the means for associating account information may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in hardware or independent of a processor in the computer equipment, and can also be stored in a memory in the computer equipment in a software mode, so that the processor can call and execute the operations corresponding to the modules.

Referring to fig. 4, an embodiment of the present application further provides a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the method for associating account information in any of the above embodiments when executing the computer program.

The embodiment of the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a computer, causes the computer to perform the method for associating account information in any of the above embodiments.

The present application also provides a computer program product containing instructions which, when executed by a computer, cause the computer to perform the method for associating account information in any of the above embodiments.

User information or user account information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, etc.) involved in various embodiments of the present application are information and data that are authorized by a user or sufficiently authorized by parties, and the collection, use and processing of relevant data is required to comply with relevant legal regulations and standards of relevant countries and regions, and is provided with corresponding operation portals for the user to select authorization or denial.

It will be appreciated that the specific examples herein are intended only to assist those skilled in the art in better understanding the embodiments of the application and are not intended to limit the scope of the application.

It should be understood that, in various embodiments of the present application, the sequence number of each process does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiments of the present application.

It will be appreciated that the various embodiments described in the present application may be implemented either alone or in combination, and that the embodiments of the present application are not limited in this regard.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to limit the scope of the present application. The term "and/or" as used herein includes any and all combinations of one or more of the associated listed items. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It will be appreciated that the processor of an embodiment of the application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital signal processor (Digital SignalProcessor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware decoding processor for execution, or in a combination of hardware and software modules in a decoding processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory, among others. The volatile memory may be Random Access Memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and unit may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for associating account information, comprising:

receiving feedback information generated after the first system newly adds first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the association account set comprises account information of at least one account which has association relation with the appointed account;

acquiring second account information of the target user in a second system;

and storing the first account information and the second account information in an associated mode.

2. The method of claim 1, wherein the account of the target user in the first system is a first account; the first system adds the first account information in the association account set after receiving the association request for the designated account sent by the first account; the feedback information comprises request parameters carried by the association request; the request parameters comprise the acquisition mode of the account identifier; the method further comprises the steps of:

and executing the step of acquiring the second account information of the target user in a second system and storing the first account information and the second account information in a correlated manner under the condition that the acquisition mode meets the specified condition.

3. The method of claim 2, wherein the obtaining means that meets the specified condition comprises: the account identification is obtained by scanning the graphic code of the designated account according to the terminal corresponding to the first account.

4. A method according to claim 3, characterized in that the method further comprises:

constructing a designated short link for associating the designated account; wherein the designated short link includes a short link parameter representing an account identification of the designated account;

the appointed short link is put in a terminal corresponding to the target user;

under the condition that the terminal sends an access request aiming at the appointed short link, analyzing account identification in the short link parameter;

invoking a graphic code generation service of the first system to generate the graphic code corresponding to the account identifier;

the graphic code is provided to the terminal to display the graphic code at the terminal.

5. The method of claim 2, wherein the request parameters further comprise an identity indicative of the target user; the step of obtaining the second account information of the target user in the second system comprises the following steps:

And acquiring second account information matched with the identity in the second system.

6. The method of claim 5, wherein the identity is formed by concatenating a verification sequence and an identification sequence; the step of obtaining the account information matched with the identity in the second system comprises the following steps:

and under the condition that the verification sequence is successfully verified, providing the identification sequence for the second system to obtain the second account information fed back by the second system.

7. The method of claim 1, wherein the account of the target user in the first system is a first account; the first system is provided with instant messaging service; the step of adding the first account information in the associated account set of the designated account represents: establishing instant communication permission between the appointed account and the first account; the second system provides purchasing service of resources; and taking the account of the target user in the second system as a second account.

8. The method of claim 7, wherein the account of the target user in the second system is a second account; the method further comprises the steps of:

And in the case that the first account in the first system is detected to have the mention action for the specified resource, the second system is instructed to push the specified resource for the second account.

9. The method of claim 7, wherein the account of the target user in the second system is a second account; the method further comprises the steps of:

and under the condition that the second account in the second system is detected to generate purchasing behavior aiming at the appointed resource, the first system is instructed to send the resource information of the appointed resource to the first account through the appointed account.

10. The method of claim 1, wherein data is isolated between the first system and the second system.

11. An account information associating apparatus, comprising:

the receiving module is used for receiving feedback information generated after the first system newly adds the first account information in the associated account set of the designated account; wherein the feedback information comprises the first account information; the first account information is account information of a target user in the first system; the association account set comprises account information of at least one account which has association relation with the appointed account;

The acquisition module is used for acquiring second account information of the target user in a second system;

12. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the method of any one of claims 1 to 9 when executing the computer program.

13. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any one of claims 1 to 9.