Method, device and medium for managing associated accounts

Abstract

The application relates to the field of account data processing, and specifically discloses a management method and device for associated accounts, equipment and medium. In response to a cross-market account association operation request, a main market corresponding to the cross-market account association operation request is determined. The cross-market account association operation request is an operation request for performing an association behavior related operation on a first account and a second account. The first account and the second account are accounts of a same user in different transaction markets. Bidirectional conflict checking is performed on the first account and the second account through the main market. If the bidirectional conflict checking is passed, the cross-market account association operation request is executed through the main market, and data records corresponding to the cross-market account association operation request are respectively created for the first account and the second account. The application can establish an account association relationship between different transaction markets and guarantee data consistency and concurrent safety of the account association operation.

Description

Technical Field

[0001] This disclosure generally relates to the field of account data processing, and specifically to a method, apparatus, device, and medium for managing associated accounts. Background Technology

[0002] In the fintech sector, a single account may open multiple accounts across different brokerage markets. To provide unified account services and management, it is necessary to link these account records from different markets. However, cross-market account linking involves multiple independent data systems, presenting complex issues such as data consistency, concurrency security, and access control. Summary of the Invention

[0003] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a method, apparatus, device and medium for managing linked accounts, which can establish account association relationships between different trading markets and ensure data consistency and concurrent security of account association operations.

[0004] In a first aspect, embodiments of this application provide a method for managing associated accounts, including: In response to a cross-market account association operation request, the primary market corresponding to the cross-market account association operation request is determined; the cross-market account association operation is an operation request for performing operations related to association behavior on the first account and the second account; the first account and the second account are accounts of the same user in different trading markets; A two-way conflict check is performed on the first account and the second account through the main market; If the bidirectional conflict check passes, the cross-market account association operation request is executed through the main market, and data records corresponding to the cross-market account association operation request are created for the first account and the second account respectively.

[0005] Secondly, embodiments of this application provide a management device for associated accounts, including: The response module is used to respond to a cross-market account association operation request and determine the primary market corresponding to the cross-market account association operation request; the cross-market account association operation is an operation request to perform operations related to association behavior on a first account and a second account; the first account and the second account are accounts of the same user in different trading markets; The inspection module is used to perform a two-way conflict check on the first account and the second account through the main market; The association module is used to execute the cross-market account association operation request through the main market if the bidirectional conflict check passes, and to create data records corresponding to the cross-market account association operation request for the first account and the second account respectively.

[0006] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in embodiments of this application.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in embodiments of this application.

[0008] Fifthly, embodiments of this application provide a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, it implements the method described in embodiments of this application.

[0009] The method, apparatus, device, and medium for managing associated accounts proposed in this application respond to a cross-market account association operation request, determine the main market corresponding to the cross-market account association operation request, and perform a two-way conflict check on the first account and the second account in different trading markets through the main market. If the two-way conflict check passes, the cross-market account association operation request is executed through the main market, and data records corresponding to the cross-market account association operation request are created for the first account and the second account respectively. On the basis of effectively realizing cross-market account association, it can effectively ensure the data consistency and concurrent security of cross-market account association operations.

[0010] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0011] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This paper illustrates the implementation environment architecture of the method for managing associated accounts provided in an embodiment of this application; Figure 2 A flowchart illustrating a method for managing associated accounts according to an embodiment of this application is shown; Figure 3 A flowchart illustrating a method for managing associated accounts according to another embodiment of this application is shown; Figure 4 A flowchart illustrating a method for managing associated accounts according to an embodiment of this application is shown; Figure 5 This illustration shows a schematic diagram of the structure of a management device for associated accounts provided in an embodiment of this application; Figure 6A schematic diagram of the structure of a computer system suitable for implementing an electronic device or server according to embodiments of this application is shown. Detailed Implementation

[0012] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0013] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0014] For the specific implementation environment of the management method for related accounts proposed in this application, please refer to [link / reference needed]. Figure 1 . Figure 1 This diagram illustrates the implementation environment architecture of the associated account management method provided in this application embodiment.

[0015] like Figure 1 As shown, the implementation environment architecture includes: terminal device 101 and market server 102.

[0016] Terminal device 101 is used to run the application account client and provide an interactive interface to the user. Terminal device 101 can be a desktop computer, laptop computer, smartphone, tablet computer, e-book reader, smart glasses, smartwatch, in-vehicle device, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), augmented reality (AR), virtual reality (VR) device, etc., but is not limited to these. Market server 102 is used to respond to cross-market account association operation requests by performing request verification, conflict checking, and executing cross-market account association operation requests.

[0017] Market server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0018] Terminal device 101 is directly or indirectly connected to market server 102 and to market server 102 via wired or wireless communication. Optionally, the aforementioned wireless or wired network uses standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to any combination of Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless network, private network, or virtual private network.

[0019] The method for managing associated accounts proposed in this application can be implemented by a management device for associated accounts, which can be installed on a terminal device or a server.

[0020] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation instruction steps as shown in the following embodiments or drawings, the method may include more or fewer operation instruction steps based on conventional or non-creative effort. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.

[0021] It should be noted that the acquisition or use of data in the embodiments of this application requires the user's consent. The relevant data can only be obtained after the user's authorization and permission, and the acquisition or use of the data complies with the laws and regulations of the relevant regions.

[0022] Please refer to Figure 2 , Figure 2 A flowchart illustrating a method for managing associated accounts according to an embodiment of this application is shown. Figure 2 As shown, the method includes: Step 201: In response to the cross-market account association operation request, determine the primary market corresponding to the cross-market account association operation request; the cross-market account association operation is an operation request used to perform operations related to the association behavior on the first account and the second account; the first account and the second account are accounts of the same user in different trading markets.

[0023] It should be noted that cross-market account linking requests are user-initiated requests related to linking a first account and a second account, including but not limited to requests to add a link, modify a link, and unlink an account. A request to add a link could be a user requesting to establish a link between a first account in the first trading market and a second account in the second trading market. A request to modify a link could be a user requesting to change the link between a first account in the first trading market and other trading accounts in the second trading market to a link between the first account and the second account in the second trading market. A request to unlink an account could be a user requesting to sever the link between a first account in the first trading market and a second account in the second trading market.

[0024] In one feasible embodiment, the cross-market account association operation request can also be an association operation request with association strength, such as strong association and weak association, which can be set according to the actual situation. This application does not make specific limitations in this regard.

[0025] Wherein, the first account is the trading account that initiates the cross-market account association operation request, and the second account is the trading account that is associated in the cross-market account association operation. Furthermore, the first trading market and the second trading market are not the same market; optionally, the first trading market and the second trading market can be trading markets in different regions, for example, the first trading market is a securities trading market in region A, and the second trading market is a securities trading market in region B.

[0026] The primary market is the trading market with higher priority, determined based on the first and second trading markets. For example, it is the trading market where the user's main trading activities occur. This can be determined through account settings.

[0027] In a feasible embodiment, after obtaining the cross-market account association operation request, the cross-market account association operation request is parsed to obtain the first trading market corresponding to the first account and the second trading market corresponding to the second account in the cross-market account association operation. Then, the main market in the first trading market and the second trading market is determined according to the preset market priority relationship.

[0028] In another feasible embodiment, after receiving a cross-market account association operation request, the market server corresponding to the first trading market determines whether it is the primary market corresponding to the cross-market account association operation request. If the first trading market corresponding to the first account is not the primary market, the cross-market account association operation request is sent to the market server corresponding to the second trading market through the market server corresponding to the first trading market. That is, if the first trading market receiving the cross-market account association operation request is not the primary market, the second trading market is directly confirmed as the primary market corresponding to the cross-market account association operation request.

[0029] Specifically, after receiving the cross-market account association operation request, the market server of the first trading market corresponding to the first account that initiated the cross-market account association operation request calls the main market determination tool to determine whether the current market is the main market corresponding to the cross-market account association operation request. If so, the cross-market account association operation request is executed. If not, the second trading market is determined to be the main market corresponding to the cross-market account association operation request, and the cross-market account association operation request is sent to the market server of the second trading market so that the cross-market account association operation request can be executed through the market server of the second trading market.

[0030] For example, the main market determination tool stores the priority configuration information of each trading market; after receiving a cross-market account association operation request, the market server of the first trading market can call the main market determination tool to obtain the market priority information of the current trading market (i.e., the first trading market) and the market priority information of the second trading market through the main market determination tool, and then determine the main market from the first trading market and the second trading market according to the market priority relationship.

[0031] It should be understood that when forwarding a cross-market account association request to a second trading market through the first trading market, the forwarded content can be the parsed content of the cross-market account association request, which must at least include the initiator's customer information, the associated party's customer information, and account information. The initiator's customer information must include at least the trading market identifier, customer identifier, customer name, and follow-up information, while the account information includes the customer identifier, account source, follow-up information, and pre-assigned group.

[0032] In one specific embodiment, cross-market account association requests can be sent from a first trading market to a second trading market via data synchronization. Specifically, as shown below... Figure 3 As shown, the data service synchronization tool (canal) of both the first and / or second trading markets listens for cross-market account association operation requests and sends these requests to a message queue. The customer service tool of the main market obtains the cross-market account association operation requests through the message queue, then implements the cross-market account association operation by modifying the account association information table, and synchronizes the account association information table to non-main markets through a scheduled synchronization task.

[0033] In other words, in this embodiment of the application, regardless of whether it is the first trading market or the second trading market, by sending the monitored cross-market account association operation request to the message queue, the customer service tool of the main market can obtain the cross-market account association operation request through the message queue, thereby achieving the purpose of sending the cross-market account association operation request to the main market.

[0034] Therefore, by automatically forwarding cross-market account association operation requests from non-main markets to the main market for unified processing, this application can effectively simplify the system architecture, ensure the centralization and consistency of data processing, and at the same time, carry complete customer and account information through the forwarding mechanism to ensure the integrity of the operation.

[0035] Furthermore, before determining the primary market corresponding to the cross-market account association operation request, the method also includes: in response to the cross-market account association operation request, performing a two-way formal verification on the cross-market account association operation request.

[0036] It should be noted that the two-way formal verification includes local verification and cross-market verification. That is, after receiving a cross-market account association operation request, the first trading market not only needs to verify the cross-market account association operation request based on the relevant information stored locally, but also needs to call the verification interface of the second trading market to verify the cross-market account association operation request based on the relevant information stored in the second trading market.

[0037] The two-way formal verification includes, but is not limited to, parameter verification and permission verification. In some embodiments, the two-way formal verification may include data verification, which is not specifically limited in this application.

[0038] Specifically, after receiving a cross-market account association operation request, the market server of the first trading market first performs parameter validation on the request, such as verifying the completeness and format validity of required fields (e.g., the standardized format of customer identifiers and market identifiers). If the cross-market account association operation request passes parameter validation, it further performs permission validation. For example, based on the request, it retrieves the follow-up person information and co-management expert information corresponding to the initiating account (i.e., the first account), and uses the locally stored customer follow-up person table and co-management expert table to perform permission validation on the follow-up person information and co-management expert information. Simultaneously, based on the request, it retrieves the second trading market and its permission validation interface. The market server of the first trading market then calls the permission validation interface of the corresponding market server in the second trading market to perform permission validation on the follow-up person information and co-management expert information using the second trading market's customer follow-up person table and co-management expert table. If the cross-market account association operation request passes the permission verification, then the cross-market account association operation request will be further verified. For example, the data information of the initiating account (i.e., the first account) in the cross-market account association operation request will be verified in the database of the first trading market, and the data information of the associated account (i.e., the second account) will be verified in the database of the second trading market.

[0039] It should be understood that cross-market account association operation requests that have undergone two-way formal verification meet the formal conditions for execution, such as structure, permissions, and data, and can be further judged for substantive execution conditions.

[0040] Therefore, the method for managing associated accounts provided in this application, after obtaining a cross-market account association operation request, can effectively ensure that the cross-market account association operation request to be executed is a request that meets the formal requirements and has the necessary permissions by performing bidirectional formal verification on the cross-market account association operation, thereby improving the reliability of associated account association.

[0041] Step 202: Perform a two-way conflict check on the first and second accounts through the main market.

[0042] It should be noted that the two-way conflict check is a check for substantial conflicts in the execution of cross-market account association operation requests. In this embodiment, the two-way conflict check includes approval process conflict check and existing association conflict check. Specifically, the approval process conflict check checks whether either the first account or the second account is currently in the process of conducting other cross-market association approval processes, and the existing association conflict check checks whether an association relationship already exists between the first account and the second account.

[0043] Specifically, a two-way conflict check is performed on the first account and the second account through the market server corresponding to the main market. This includes checking whether the first account and the second account are participating in other cross-market account association operations, or whether there is already an association relationship between the first account and the second account corresponding to the cross-market account association operation request. If the first account or the second account is participating in other cross-market account association operations, or there is already an association relationship between the first account and the second account, then a conflict is determined to exist.

[0044] In other words, it is determined whether the first account and the second account are currently involved in other cross-market account association operations. If either the first account or the second account is involved in other cross-market account association operations, the current cross-market account association operation is considered to be in conflict and cannot be executed. Alternatively, if the first account and the second account already had a relationship before receiving the current cross-market account association operation request, the current market account association operation is considered to be in conflict and cannot be executed.

[0045] It should be understood that during the two-way inspection process, if a cross-market account association operation request has either an approval process conflict or an existing relationship conflict, then the cross-market account association operation request is determined to have a two-way conflict and cannot be executed.

[0046] In a preferred embodiment, to prevent concurrent operation conflicts, this application acquires distributed locks for the first account and the second account respectively through the market server corresponding to the main market before performing bidirectional conflict checks on the first account and the second account; and releases the distributed locks for the first account and the second account when the bidirectional conflict check passes.

[0047] It should be noted that, in this embodiment of the application, the distributed locks acquired by the market server corresponding to the first trading market for the first account and the second account are time-limited locks. That is, the distributed locks are automatically released after a preset time. Therefore, if the bidirectional conflict check fails, the distributed locks of the first account and the second account can be released after the preset time. The preset time can be based on the time required to complete the operation; for example, in this embodiment, the expiration time of the distributed lock can be 10 seconds.

[0048] Specifically, the market server corresponding to the first trading market generates unique Redis keys for the first account and the second account respectively, with the following format: crm:cross_assoc_customer:{market}:{customerId} Use Redis's EXPIRE command to set the lock's expiration time to 10 seconds to prevent it from locking up. After the cross-market account association operation is completed, use the DEL command to release the lock for the first and second accounts.

[0049] In a preferred embodiment, if acquiring the lock fails, the cross-market account association operation will be rejected, and an error message will be sent to the first account to prompt the user to try again later. Alternatively, if acquiring the lock fails, the user will enter a waiting queue, and the distributed lock will be acquired in sequence after the previous cross-market account association operation requests to release the lock, thereby effectively reducing the user's waiting time.

[0050] It should be understood that distributed locks are used in this application embodiment to ensure the reliability and data consistency of cross-market account association operations. Therefore, other distributed locks, such as ZooKeeper or etcd, can also be used in practical applications.

[0051] Therefore, this application effectively avoids operational conflicts through distributed locks and performs substantive conflict checks through bidirectional conflict checking, ensuring the legality and uniqueness of cross-market account association operations. This achieves multiple checks on cross-market account association operations, thereby improving the reliability of account association. Furthermore, by acquiring distributed locks for the first and second accounts corresponding to the cross-market account association operation request, and setting the expiration time of the distributed locks to 10 seconds, it effectively prevents data inconsistency issues caused by concurrent operations and ensures that only one association operation can be performed by the same customer at a time. This forms a conflict-complementing mechanism with the approval process, further improving the reliability of cross-market account association operations.

[0052] Step 203: If the two-way conflict check passes, create an association between the first account and the second account through the main market, and create corresponding association data for the first account and the second account respectively.

[0053] It should be noted that during the aforementioned two-way conflict checking, for existing conflicting relationships, a two-way check is required. This check must be performed on both the first account in the first trading market and the second account in the second trading market. Therefore, to avoid table scans during the two-way check and reduce query efficiency from O(n) to O(1), this application proposes creating separate associated data for the first and second accounts.

[0054] Specifically, for the first account in the first trading market, the associated data created includes: (market1, customerId1, market2, customerId2, customerName2_masked) For a second account in the second trading market, the following associated data is created: (market2, customerId2, market1, customerId1, customerName1_masked) Here, market1 and market2 represent the first and second trading markets, respectively. customerId1 represents the unique identifier of the first account, and customerId2 represents the unique identifier of the second account. customerName1_masked and customerName2_masked represent the customer characteristic information of the customer corresponding to the first account in the first trading market and the customer characteristic information of the customer corresponding to the second account in the second trading market, respectively. These are used to identify the specific customer corresponding to the account. Specifically, the customer characteristic information can be obtained by serializing and hashing the customer information corresponding to the first account. It is understandable that, based on customerName1_masked or customerName2_masked, the market server can quickly locate the corresponding customer's account in other trading markets outside this market without the risk of information leakage.

[0055] As can be seen, when the market server or business service corresponding to the main market performs an existing relationship query on the first account (customerId1) in the first trading market (market1) based on the database of the first trading market, it can directly query the associated account in the second trading market (market2), i.e., the second account (customerId2), through the associated data. Similarly, when the market server or business service corresponding to the main market performs an existing relationship query on the second account (customerId2) in the second trading market (market2) based on the database of the second trading market, it can directly query the associated account in the first trading market (market1), i.e., the first account (customerId1), through the associated data.

[0056] It should be understood that this application adopts a bidirectional association data storage mechanism, which enables each cross-market account association to store two symmetrical records in the database, thereby effectively ensuring that association information can be quickly queried from either side, reducing the query efficiency from O(n) to O(1), while ensuring data consistency through a unique index.

[0057] In one feasible implementation, a graph database (such as Neo4j) can be used to store the created associated data to improve the query speed of associated data. Specifically, the unique identifier of the account can be used to generate account entity nodes, and at the same time, attribute entity nodes can be generated based on information such as the trading market where the account is located and the customer characteristic information corresponding to the account. Then, based on the above associated data, the associated edges of different entity nodes are created. Finally, based on the account entity nodes, attribute entity nodes, and associated edges, an account topology graph is generated.

[0058] The associated edges can include attribute-related edges, explicit associated edges, and implicit associated edges. Taking the aforementioned associated data (market1, customerId1, market2, customerId2, customerName2_masked) as an example, the market server can generate entity nodes for the first account and the second account respectively based on the unique identifiers of the first and second accounts, and generate attribute entity nodes for the first and second trading markets respectively based on the first trading market (market1) where the first account is located and the second trading market (market2) where the second account is located. Furthermore, attribute-related edges can be generated between the first trading market attribute entity node and the first account entity node, and between the second trading market attribute entity node and the second account entity node. Simultaneously, based on the second account... The account feature information customerName2_masked is used to generate feature attribute entity nodes for the second account. Attribute association edges can be generated between the feature attribute entity nodes of the second account and the second account entity node. After obtaining the association data, implicit association edges can be generated between the feature attribute entity nodes of the second account and the first account entity node, and explicit association edges can be generated between the first account entity node and the second account entity node. Finally, an account topology graph is generated based on the first account entity node, the second account entity node, the first transaction market attribute entity node, the second transaction market attribute entity node, the feature attribute entity node of the second account, and each attribute association edge, explicit association edge, and implicit association edge.

[0059] It is understandable that when the market server or business service corresponding to the main market performs a query on the existing relationships of the first account (customerId1) in the first trading market (market1) based on the database of the first trading market, it can locate the corresponding account entity node in the account topology graph based on the market information and the unique identifier corresponding to the account. Then, based on the connectivity between the account entity node and other entity nodes (including account entity nodes or attribute entity nodes), it can quickly query the related accounts in the target trading market, such as the related accounts in the second trading market (market2).

[0060] In some embodiments, checking whether there is already an association relationship between the first account and the second account corresponding to the cross-market account association operation request includes: based on the association edges between entity nodes in the account topology graph, taking the entity node corresponding to the first account as the starting point, obtaining at least one candidate account entity node under the search path; the candidate account entity node refers to the account entity node found for the first time through the search path and is under the second trading market; wherein, the search path is composed of different association edges; comparing at least one candidate account entity node, verifying whether the account entity node found under at least one search path is the same account entity node, if so, determining that the searched account entity node is the associated account of the second trading market.

[0061] In one embodiment, during the process of querying the existing association relationships of the first account (customerId1) in the first trading market (market1) under the second trading market based on the database of the first trading market, the market server or business service corresponding to the main market can locate the corresponding account entity node in the account topology graph based on the market information and the unique identifier corresponding to the account. Then, based on the association edges between various entity nodes (including account entity nodes or attribute entity nodes) in the account topology graph, taking the account entity node as the starting point, and using different association edges as search paths, candidate account entity nodes are obtained through at least one search path. The candidate account entity node refers to the account entity node found for the first time through different search paths and is under the second trading market. By comparing different candidate account entity nodes, it is verified whether the account entity nodes found under different search paths are the same account entity node. If so, it can be determined that the searched account entity node is an associated account of the second trading market.

[0062] For example, starting with the first account entity node (customerId1), the search path can follow the explicit association edge to directly find the connected second account entity node (customerId2). Simultaneously, the search path can also follow the implicit association edge between it and the second account's feature attribute entity node (customerName2_masked), and the attribute association edge between the second account's feature attribute entity node and the second account entity node. By using multiple search paths, the search can find the same account entity node in the second trading market, i.e., the second account entity node, thus confirming that the found account entity node is a related account. Through parallel searching using multiple search paths and performing intersection operations on the search results, a deep traversal of the entire graph is avoided, significantly reducing computational complexity while maintaining accuracy.

[0063] It should be understood that databases need to version control related data and record historical changes to relationships in order to facilitate rollback and auditing of relationships.

[0064] In one feasible embodiment, to ensure the reliability of cross-market account association operations, these operations require an approval process. Specifically, the main market creates an association relationship between the first and second accounts, and corresponding association data is created for each account. This includes: establishing an approval task node based on the cross-market account association operation request through the main market; invoking the approval service component to update the approval task node to "under approval" and approving the cross-market account association operation request; and if the approval is successful, creating association data for the two accounts corresponding to the cross-market account association operation request.

[0065] In other words, when a cross-market account association operation request passes the two-way conflict check, an approval task node is established for the cross-market account association operation request through the main market. The approval task node varies depending on the type of cross-market account association operation request. For example, when the cross-market account association operation request is an Add-Date (ADD) operation request, an approval process for creating a new cross-market association is created; when the cross-market account association operation request is an Update-Date (UPDATE) operation request, an approval process for modifying an existing cross-market association (i.e., deleting the old association first and then creating a new one) is created; and when the cross-market account association operation request is a Remove-Date (REMOVE) operation request, an approval process for deleting an existing cross-market association is created.

[0066] It should be noted that after creating the approval task node, its status is initially set to INIT, indicating that the approval flow has been created and is awaiting approval. Then, the approval service component is called to update the approval task node to PENDING, indicating that the approval has been initiated and is awaiting the result. At this point, the approval service component approves the cross-market account association request. If the approval is successful, the status of the approval task node is changed to PASSED, indicating that the cross-market account association operation will be executed. If the approval fails, the status of the approval task node is changed to REJECTED, indicating that the approval has been rejected and the cross-market account association operation will not be executed.

[0067] Therefore, this application embodiment incorporates cross-market account association operations into the approval process management, supports three operation types: adding, modifying, and canceling, and ensures business compliance and operational traceability through approval status management.

[0068] Therefore, the method for managing associated accounts proposed in this application, in response to a cross-market account association operation request, determines the main market corresponding to the cross-market account association operation request, performs a two-way conflict check on the first account and the second account in different trading markets through the main market, and if the two-way conflict check passes, executes the cross-market account association operation request through the main market, and creates data records corresponding to the cross-market account association operation request for the first account and the second account respectively. On the basis of effectively realizing cross-market account association, it can effectively ensure the data consistency and concurrent security of cross-market account association operations.

[0069] In one specific embodiment, such as Figure 4 As shown, taking a non-main market receiving a cross-market account association operation request as an example, the non-main market receives the request and performs parameter verification, permission verification, and data verification. The permission and data verification require verification of both markets involved in the cross-market account association operation request (the main market and the non-main market separately) to improve the reliability of the request's execution. If the cross-market account operation request passes the verification, it is further determined whether the current market is the main market. In this embodiment, the determination result is negative, and the non-main market sends the complete customer information and account information from the cross-market account association operation request to the main market. The main market's market server, based on the received complete customer information and account information, acquires distributed locks for the two accounts involved in the cross-market account association operation, and then performs bidirectional conflict checks on the two accounts. If either of the two accounts is currently performing another cross-market account association operation, or if a relationship already exists between the two accounts, it is determined that the cross-market account association operation request is conflicting and cannot be executed. If neither account has any other ongoing cross-market account association operations and there is no association relationship between the two accounts, then the cross-market account association operation request passes the two-way conflict check and can be executed. In this case, an approval process is created for the cross-market account association operation request through the main market's market server. The approval service component is invoked to approve the request. After approval, association data is created for both accounts in the main market's database and the non-main market's database, respectively.

[0070] It should be noted that although the operation of the method of the present invention is described in a specific order in the accompanying drawings, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed in order to achieve the desired result.

[0071] Figure 5 A schematic diagram of the structure of a management device for associated accounts provided in an embodiment of this application is shown.

[0072] like Figure 5As shown, the management device 10 for the associated account includes: Response module 11 is used to respond to a cross-market account association operation request and determine the main market corresponding to the cross-market account association operation request; the cross-market account association operation is an operation request to perform operations related to association behavior on the first account and the second account; the first account and the second account are accounts of the same user in different trading markets; Inspection module 12 is used to perform a two-way conflict check on the first account and the second account through the main market; The association module 13 is used to execute the cross-market account association operation request through the main market if the bidirectional conflict check passes, and to create data records corresponding to the cross-market account association operation request for the first account and the second account respectively.

[0073] In some embodiments, the response module 11 is further configured to: When the first trading market corresponding to the first account is not the main market, the cross-market account association operation request is sent to the second trading market corresponding to the second account through the first trading market.

[0074] In some embodiments, the response module 11 is further configured to: Before performing a bidirectional conflict check on the first account and the second account through the main market, a distributed lock is acquired for the first account and the second account respectively through the main market; and When the bidirectional conflict check passes, the distributed lock is released for both the first account and the second account.

[0075] In some embodiments, the inspection module 12 is specifically used for: The main market is used to check whether the first account and the second account are participating in other cross-market account association operations, or whether there is already an association relationship between the first account and the second account corresponding to the cross-market account association operation request. If the first account or the second account is participating in other cross-market account association operations, or if there is already an association relationship between the first account and the second account, then a conflict is determined to exist.

[0076] In some embodiments, the association module 13 is specifically used for: An approval task node is established through the main market based on the cross-market account association operation request; The approval service component is invoked to update the approval task node to "under approval" and to approve the cross-market account association operation request. If the approval is granted, association data will be created for the two accounts corresponding to the cross-market account association operation request.

[0077] In some embodiments, the response module 11 is further configured to: In response to the cross-market account association operation request, a two-way formal verification is performed on the cross-market account association operation request.

[0078] In some embodiments, the inspection module 12 is specifically used for: Based on the association edges between entity nodes in the account topology graph, taking the entity node corresponding to the first account as the starting point, at least one candidate account entity node under the search path is obtained; the candidate account entity node refers to the account entity node found for the first time through the search path and is under the second trading market; wherein, the search path is composed of different association edges; By comparing at least one of the candidate account entity nodes, it is verified whether the account entity nodes searched under at least one of the search paths are the same account entity node. If so, it is determined that the searched account entity node is an associated account of the second trading market.

[0079] It should be understood that the modules or modules described in the management device 10 for associated accounts are related to the reference. Figure 2 The steps in the described method correspond to each other. Therefore, the operations and features described above for the method are also applicable to the associated account management device 10 and the modules contained therein, and will not be repeated here. The associated account management device 10 can be pre-implemented in the browser or other security applications of the electronic device, or it can be loaded into the browser or other security applications of the electronic device by means of downloading. The corresponding modules in the associated account management device 10 can cooperate with the modules in the electronic device to implement the solution of the embodiments of this application.

[0080] The division of modules or units mentioned in the detailed description above is not mandatory. In fact, according to the embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0081] The following is for reference. Figure 6 , Figure 6 A schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application is shown. like Figure 6As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. RAM 603 also stores various programs and data required for the system's operating instructions. CPU 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.

[0082] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0083] Specifically, according to embodiments of this application, the flowchart above refers to... Figure 2 The described process can be implemented as a computer software program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program contains program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined in the system of this application.

[0084] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0085] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operational instructions of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two connected blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified functions or operational instructions, or using a combination of dedicated hardware and computer instructions.

[0086] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be housed in a processor; for example, a processor can be described as including a response module, a checking module, and an association module. The names of these units or modules do not necessarily limit the specific unit or module itself. For example, a response module can also be described as "responding to a cross-market account association operation request, determining the primary market corresponding to the cross-market account association operation request; the cross-market account association operation is an operation request for performing operations related to association behavior on a first account and a second account; the first account and the second account are accounts of the same user in different trading markets."

[0087] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments, or may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the associated account management method described in this application.

[0088] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the foregoing disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for managing associated accounts, characterized in that, include: In response to a cross-market account association operation request, determine the primary market corresponding to the cross-market account association operation request; The cross-market account association operation is used to request operations related to association behavior on the first account and the second account. The first account and the second account are the same user's accounts in different trading markets; A two-way conflict check is performed on the first account and the second account through the main market; If the bidirectional conflict check passes, the cross-market account association operation request is executed through the main market, and data records corresponding to the cross-market account association operation request are created for the first account and the second account respectively.

2. The method for managing associated accounts according to claim 1, characterized in that, Also includes: When the first trading market corresponding to the first account is not the main market, the cross-market account association operation request is sent to the second trading market corresponding to the second account through the first trading market.

3. The method for managing associated accounts according to claim 1, characterized in that, Also includes: Before performing bidirectional conflict checks on the first account and the second account through the main market, a distributed lock is acquired for the first account and the second account respectively through the main market. as well as When the bidirectional conflict check passes, the distributed lock is released for both the first account and the second account.

4. The method for managing associated accounts according to claim 1, characterized in that, The bidirectional conflict check performed on the first account and the second account through the main market includes: The main market is used to check whether the first account and the second account are participating in other cross-market account association operations, or whether there is already an association relationship between the first account and the second account corresponding to the cross-market account association operation request. If the first account or the second account is participating in other cross-market account association operations, or if there is already an association relationship between the first account and the second account, then a conflict is determined to exist.

5. The method for managing associated accounts according to claim 1, characterized in that, The step of creating an association between the first account and the second account through the main market, and creating corresponding association data for the first account and the second account respectively, includes: An approval task node is established through the main market based on the cross-market account association operation request; The approval service component is invoked to update the approval task node to "under approval" and to approve the cross-market account association operation request. If the approval is granted, association data will be created for the two accounts corresponding to the cross-market account association operation request.

6. The method for managing associated accounts according to claim 1, characterized in that, Before determining the primary market corresponding to the cross-market account association operation request, the method further includes: In response to the cross-market account association operation request, a two-way formal verification is performed on the cross-market account association operation request.

7. The method for managing associated accounts according to claim 4, characterized in that, Checking whether an association relationship already exists between the first account and the second account corresponding to the cross-market account association operation request, including: Based on the association edges between entity nodes in the account topology graph, taking the entity node corresponding to the first account as the starting point, at least one candidate account entity node under the search path is obtained; the candidate account entity node refers to the account entity node found for the first time through the search path and is under the second trading market; wherein, the search path is composed of different association edges; By comparing at least one of the candidate account entity nodes, it is verified whether the account entity nodes searched under at least one of the search paths are the same account entity node. If so, it is determined that the searched account entity node is an associated account of the second trading market.

8. A management device for associated accounts, characterized in that, include: The response module is used to respond to a cross-market account association operation request and determine the primary market corresponding to the cross-market account association operation request. The cross-market account association operation is used to request operations related to association behavior on the first account and the second account. The first account and the second account are the same user's accounts in different trading markets; The inspection module is used to perform a two-way conflict check on the first account and the second account through the main market; The association module is used to execute the cross-market account association operation request through the main market if the bidirectional conflict check passes, and to create data records corresponding to the cross-market account association operation request for the first account and the second account respectively.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method for managing associated accounts as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the method for managing associated accounts as described in any one of claims 1-7.

11. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the method for managing associated accounts as described in any one of claims 1-7.

Images