A user registration method, apparatus, storage medium, and server

Abstract

This invention discloses a user registration method, apparatus, storage medium, and server, applicable to the field of communication technology. When an application terminal requests a transaction from an application server for a target object involving objects on a third-party server, the application server is triggered to pre-register user information with the third-party server. This allows the third-party server to associate the processing results of the relevant objects with the registered user information when the user further initiates other requests for the target object set through the application terminal. This enables accurate location of the processing results for the relevant objects, preventing call failures and improving user experience. Furthermore, since the application server's processing of the target transaction request is simpler than its processing of other requests, triggering user information registration based on the target transaction request does not significantly impact the processing steps of the target transaction request itself or the user information registration steps.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a user registration method, apparatus, storage medium, and server. Background Technology

[0002] Smart TVs are now offering users an increasingly rich variety of video content. Users can register their information with video servers through their smart TVs. In this way, the video servers can store the video access information of users on their smart TVs and recommend relevant video content to users, thus providing them with greater convenience in choosing videos.

[0003] Users can also purchase specific video content provided by video servers or by third-party servers associated with video servers through smart TVs. However, when users purchase specific video content through smart TVs and then view and manage the purchase information, if the specific video content comes from a third-party server, the process of accessing the purchase information for that specific video content often fails, severely impacting the user experience. Summary of the Invention

[0004] This invention provides a user registration method, apparatus, storage medium, and server, enabling user registration during the target transaction process.

[0005] One embodiment of the present invention provides a user registration method, including:

[0006] Receive a target transaction request sent by the application terminal, the target transaction request being used to request a transaction on a target object;

[0007] Determine the set of parties to which the target object set corresponding to the target transaction object belongs based on the target transaction request;

[0008] If the set of parties includes a third-party server, obtain the user information corresponding to the target transaction request;

[0009] The user information is registered with the third-party server by calling the communication interface of the third-party server through the communication interface.

[0010] Another embodiment of the present invention provides a user registration device, comprising:

[0011] A request receiving unit is used to receive a target transaction request sent by an application terminal, wherein the target transaction request is used to request a transaction to a target object;

[0012] The ownership determination unit is used to determine the ownership set of the target object set corresponding to the target transaction request based on the target transaction request;

[0013] The user acquisition unit is used to acquire user information corresponding to the target transaction request if the set of parties includes a third-party server.

[0014] The registration unit is used to call the communication interface of the third-party server and register the user information to the third-party server through the communication interface.

[0015] Another aspect of the present invention provides a computer-readable storage medium storing a plurality of computer programs adapted for loading by a processor and executing the user registration method as described in one aspect of the present invention.

[0016] Another embodiment of the present invention provides a server, including a processor and a memory;

[0017] The memory is used to store multiple computer programs, which are loaded and executed by a processor as described in one aspect of the user registration method of the present invention; the processor is used to implement each of the multiple computer programs.

[0018] As can be seen, in the method of this embodiment, after receiving a target transaction request for a target object, if the set of parties to which the target object set corresponding to the target transaction request belongs includes a third-party server, the application server obtains the user information corresponding to the target transaction request and calls the communication interface of the third-party server to register the obtained user information with the third-party server through the communication interface. Thus, when a user requests a transaction for a target object from the application server via the application terminal that involves objects on the third server (including those in the target object set), the application server is triggered to pre-register the user information with the third-party server. This allows the third-party server to associate the processing results based on the relevant objects with the registered user information when the user further initiates a request for the target object set via the application terminal, thereby accurately locating the processing results for the relevant objects without call failure, improving user experience. Furthermore, since the processing of target transaction requests by the application server is simpler than the processing of other requests (such as payment requests), the registration of user information triggered based on the target transaction request does not significantly affect the processing steps of the target transaction request itself or the user information registration steps, ensuring the processing performance of each step. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of a user registration method provided in an embodiment of the present invention;

[0021] Figure 2 This is a flowchart of a user registration method provided in one embodiment of the present invention;

[0022] Figure 3a This is a schematic diagram of the video information interface displayed on the application terminal in one embodiment of the present invention;

[0023] Figure 3b This is a schematic diagram of the user interface displayed on the application terminal in one embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of a system in which the user registration method provided in one application embodiment of the present invention is applied;

[0025] Figure 5 This is a flowchart of a user registration method provided in one application embodiment of the present invention;

[0026] Figure 6 This is a schematic diagram of a distributed system to which the information processing method of this invention is applied in another application embodiment of the invention;

[0027] Figure 7 This is a schematic diagram of the block structure in another application embodiment of the present invention;

[0028] Figure 8 This is a schematic diagram of the logical structure of a user registration device provided in an embodiment of the present invention;

[0029] Figure 9 This is a schematic diagram of the logical structure of a server provided in an embodiment of the present invention. Detailed Implementation

[0030] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0031] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] This invention provides a user registration method, which can be mainly applied to, for example... Figure 1 The system shown includes: an application terminal 10, an application server 11, and a third-party server 12, wherein:

[0033] Application terminal 10 provides a registration interface, allowing users to register their information (including user ID, password, and other user attributes) with application server 11. Furthermore, application terminal 10 also provides an interaction interface for users, enabling them to initiate requests for accessing multimedia content, multimedia content transactions, and certain service transactions. Based on these user requests, the application terminal accesses application server 11 and displays multimedia content, such as video and audio data, provided by application server 11. These requests can originate from users already registered with application server 11 or from unregistered users (guests).

[0034] Application terminal 10 may include, but is not limited to, electronic devices such as smart TVs, smartphones, or tablets.

[0035] Application server 11 is used to provide multimedia content, such as video data, audio data, or news data, to application terminal 10, and to provide services related to the multimedia content, such as membership services, hereinafter referred to as the first service. Application server 11 may specifically include, but is not limited to, video server, self-media server, game server, or cloud server.

[0036] In a specific application, the application server 11 may include an object service module 110 and a user service module 111. The object service module 110 is used to provide multimedia content and related services to the application terminal 10, and the user service module 111 is used to store and manage user information registered by users through the application terminal 10. The object service module 110 and the user service module 111 may be deployed on the same physical device or on different physical devices.

[0037] Third-party server 12 is used to provide other content and services that are different from those provided by application server 11, such as cloud storage, bandwidth, online courses, or game currency, which will be referred to as second content and second service, respectively. Third-party server 12 may specifically include, but is not limited to, video servers, social media servers, game servers, or cloud servers, and is a different server from the aforementioned application server 11.

[0038] The third-party server 12 can associate its second content and second services with the application server 11. The application server 11 does not store the specific content and services themselves, but only their identifiers and transaction amounts. This allows users to initiate transaction requests for the second content and services through the application terminal 10, enabling users accessing the application server 11 to purchase not only the content and services provided by the application server 11, but also the content and services provided by the third-party server 12.

[0039] Specifically, the application server 11 in the system can implement user registration on the third-party server using the following steps:

[0040] The object service module 110 in the application server 11 receives a target transaction request sent by the application terminal 10. The target transaction request is used to request a transaction on a target object. The object service module 110 determines the ownership set of at least one target object set corresponding to the target transaction request based on the target transaction request. If the ownership set includes a third-party server 12, the object service module 110 notifies the user service module 111 to obtain the user information corresponding to the target transaction request. The user service module 111 calls the communication interface of the third-party server 12 and registers the user information with the third-party server 12 through the communication interface.

[0041] In this way, when a user requests a transaction for a target object from the application server via the application terminal, and the transaction involves objects on a third server (including those in the target object set), the application server is triggered to pre-register the user information with the third-party server. This allows the third-party server to associate the processing results based on the relevant objects with the registered user information when the user further initiates other requests for the target object set via the application terminal. This enables the server to accurately locate the processing results for the relevant objects without causing call failures, thus improving the user experience. Furthermore, since the application server's processing of target transaction requests is simpler than its processing of other requests (such as payment requests), the registration of user information triggered based on the target transaction request does not significantly affect the processing steps of the target transaction request itself or the user information registration steps, ensuring the processing performance of each step.

[0042] One embodiment of the present invention provides a user registration method, which is mainly the method executed by the aforementioned application server, and the flowchart is as follows. Figure 2 As shown, it includes:

[0043] Step 101: Receive the target transaction request sent by the application terminal. The target transaction request is used to request a transaction on the target object.

[0044] It is understandable that if a user wants to purchase multimedia content or certain services provided by an application server, they can first initiate a target transaction request for a certain service or multimedia content through the interactive interface provided by the application terminal, and send the target transaction request to the application server. The target transaction request may include the identification information of the target object, and may also include the user identifier of the user who initiated the request, etc. The target object may include multimedia content or services provided by the application server.

[0045] When the application server receives a target transaction request, it can return transaction information for at least one set of target objects, such as transaction amount information, to the application terminal. The application terminal will then display the transaction information for at least one set of target objects through a user interface, which may also include a payment interface. When the user interacts with this payment interface, the application terminal will initiate payment requests for each set of target objects. These payment requests request the payment of the corresponding transaction amount to acquire the set of target objects, and thus, the payment for the set of target objects can be completed according to the payment requests, thereby realizing the purchase of the target objects.

[0046] In this embodiment of the invention, after the application server receives the target transaction request, it can also initiate the user registration process of this embodiment and execute the following steps 102 to 104.

[0047] Step 102: Determine the ownership set of at least one set of target objects corresponding to the target transaction request based on the target transaction request. The ownership set may include at least one owner.

[0048] Here, any set of target objects may specifically include the target object, or include the target object and at least one associated object. The target object is provided by the application server, while other associated objects in the set of target objects may be provided by a third-party server. The owner refers to the server that can provide each object in the set of target objects, such as the application server or the third-party server mentioned above.

[0049] Specifically, the application server pre-stores the association relationships between each object in the target object set and its owner. The server providing these objects to the user can be the aforementioned application server or a third-party server. Specifically, the application server stores the correspondence between the identification information of each object and the information of its owner. Thus, when the process of this embodiment is initiated, in one scenario, if the target object set includes the aforementioned target objects, the application server can find the owner corresponding to the aforementioned target object based on the identification information of the target object in the target transaction request and the pre-set association relationships between each object and its owner.

[0050] In another scenario, the aforementioned set of target objects may include a target object and at least one associated object. When the application server executes step 102, it can find the owner corresponding to the target object and at least one associated object based on the identification information of the target object in the target transaction request and the pre-defined association relationship between each object and its owner.

[0051] For example Figure 3a The image shows the video information interface displayed on the application terminal. This interface includes links to multiple videos and a "Purchase Membership" button. When the user clicks the "Purchase Membership" button, the application terminal sends a target transaction request. This request is used to request a transaction for the target item, "Video Membership." When the application server receives the target transaction request, since the video membership service on the application server is associated with third-party services (such as network traffic or cloud storage), the application server returns the transaction amount information corresponding to the video membership and the third-party service to the application terminal for display. Figure 3bAs shown, the application terminal displays the transaction amounts corresponding to various video memberships and their associated cloud storage services on the user interface. These are three sets of target objects: one set includes "one-month membership" and "1GB cloud storage"; another set includes "six-month membership" and "2GB cloud storage"; and yet another set includes "one-year membership" and "3GB cloud storage". In this embodiment of the invention, the application server obtains the ownership information for each of the various video memberships and their associated cloud storage services.

[0052] Step 103: If the set of parties includes a third-party server, obtain the user information corresponding to the target transaction request.

[0053] In one scenario, when the application server determines that the set of parties to which the above-determined ownership includes a third-party server, it can directly obtain user information and execute the following step 104.

[0054] In another scenario, the application server can first determine whether the user information corresponding to the target transaction request has been registered in the third-party server. If not, the user information needs to be obtained first before proceeding to step 104. If it has been registered, the user information does not need to be obtained, nor does step 104 need to be performed.

[0055] Step 104: Call the communication interface of the third-party server and register the user information with the third-party server through the communication interface.

[0056] In one scenario, when the target transaction request is initiated based on a user identifier registered with the application server, the target transaction request may include the user identifier, and the application server also stores registered user information, such as the user's age, occupation, email address, phone number, etc. Thus, when the process of this embodiment is initiated, the application server can directly obtain the registered user information based on the user identifier in the target transaction request and register the user information with a third-party server.

[0057] In another scenario, when the target transaction request is initiated by a user not registered with the application server, the target transaction request will not include a user identifier, and the application server will not store user information such as age, occupation, email, phone number, etc. In this case, when initiating the process of this embodiment, the application server can provide a user registration interface to the application terminal during this step. This user registration interface includes input interfaces for various dimensions of information. After receiving the user registration interface, the application terminal displays it. When the user inputs the corresponding user information through the input interfaces displayed on the application terminal, the application terminal sends the input user information to the application server. When the application server receives the user information input by the user through the aforementioned user registration interface, it registers the user information with a third-party server and also registers the received user information with the current application server. In this case, when a user initiates a target transaction request as a guest through the application terminal, they need to register with the application server first, and then register with the third-party server.

[0058] In other embodiments, if the target transaction request does not include a user identifier and the application server does not store user information, when initiating the process of this embodiment, the application server can provide a user selection interface to the application terminal during this step. This user selection interface includes selection interfaces for other applications, where "other applications" refers to applications outside the current application server, such as instant messaging applications. The application terminal receives and displays the user selection interface. When the user selects a target application through the user selection interface displayed on the application terminal, the application terminal sends the information of the selected target application to the application server. When the application server receives the information from the application terminal regarding the target application selected by the user through the aforementioned selection interface, it obtains the user information registered by the user in the target application's system and registers this user information with a third-party server. In this case, when a user initiates a target transaction request as a guest through the application terminal, they can log in to the application server using the user information registered in the target application's (user-selected) system, and then send that user information to the third-party server.

[0059] It should be further explained that when the application server receives the target transaction request and returns transaction information, such as the transaction amount, to the application terminal for at least one set of target objects, if the owner of each object in the target object set includes a third-party server, the user information is registered in the third-party server through the process of steps 101 to 104 above.

[0060] Furthermore, after a user pays the corresponding transaction amount for each object in the target object set through the application terminal, the application server stores the correspondence between user information and the payment information of the target objects in the target object set. Meanwhile, the third-party server can also store the correspondence between user information and the payment information of associated objects in the target object set. Thus, when a user initiates a request through the application terminal to view and manage the payment information of the target objects and associated objects, such as sending a shipping reminder to each object in the target object set, this request is sent to the third-party server through the application server. The third-party server can determine, based on the stored correspondence, which user initiated the payment management for which associated object in which target object set, and then returns the processing result to the application terminal. In this process, because user information is pre-registered in the third-party server, the processing of a specific associated object can be accurately located based on the application terminal's request, preventing failures in accessing the payment details of the target object.

[0061] As can be seen, in the method of this embodiment, after receiving a target transaction request for a target object, if the set of parties to which the target object set corresponding to the target transaction request belongs includes a third-party server, the application server obtains the user information corresponding to the target transaction request and calls the communication interface of the third-party server to register the obtained user information with the third-party server through the communication interface. Thus, when a user requests a transaction for a target object from the application server via the application terminal that involves objects on the third server (including those in the target object set), the application server is triggered to pre-register the user information with the third-party server. This allows the third-party server to associate the processing results based on the relevant objects with the registered user information when the user further initiates other requests for objects in the target object set via the application terminal. This enables accurate location of the processing results for the relevant objects without call failure, improving user experience. Furthermore, since the application server's processing of target transaction requests is simpler than its processing of other requests (such as payment requests), the registration of user information triggered based on the target transaction request does not significantly affect the processing steps of the target transaction request itself or the user information registration steps, ensuring the processing performance of each step.

[0062] The following is a specific application example to illustrate the user registration method of the present invention. The method in this embodiment can be applied to the above-mentioned... Figure 4 The system shown may include: a smart TV 20, a video sub-server 21, a user sub-server 22, and a third-party server 23, wherein:

[0063] The smart TV 20 is the application terminal mentioned above; the video sub-server 21 is used to provide video and video-related services such as membership services to the smart TV; the user sub-server 22 is used to store and manage user information of each user. The video sub-server 21 and the user sub-server 22 are the object service module and the user service module mentioned above, respectively.

[0064] Specifically, such as Figure 5 As shown, user registration can be achieved through the following steps in this embodiment:

[0065] Step 201: The user can control the smart TV 20 with the remote control to open the video details page. The video details page can include the video description information and the purchase interface of the service related to the video, such as the "Member Purchase" button. When the user clicks the "Member Purchase" button, the smart TV 20 will send a target transaction request to the video sub-server 21. The target transaction request is used to request a transaction on the target object.

[0066] Step 202: The video sub-server 21 receives the target transaction request sent by the smart TV 20, and returns the transaction amount information of the target object set to the smart TV 20 for display according to the target transaction request. The target object set will include the target object "Member Service" and other related objects, and triggers the following step 203.

[0067] Step 203: The video sub-server 21 determines the set of owners of the target object set corresponding to the target transaction request based on the target transaction request.

[0068] Step 204: If the set of parties includes a third-party server 23, the video sub-server 21 determines whether the user information corresponding to the target transaction request has been registered in the third-party server 23. If it has been registered, the process ends; if it has not been registered, the following step 205 is executed.

[0069] Step 205: The video sub-server 21 sends a message queue (MQ) to the user sub-server 22. This MQ message is used to notify the user sub-server 22 to register the user information with the third-party server 23.

[0070] Step 206: User sub-server 22 obtains user information based on MQ message and calls the communication interface of third-party server 23 to register the user information with third-party server 23.

[0071] The user information may be user information already registered in the user sub-server 22, or user information registered in the system of other applications selected by the user (such as instant messaging applications). Furthermore, the third-party server 23 may also execute step 207.

[0072] In step 207, after receiving the user information, the third-party server 23 can assign a user identifier supported by the third-party server 23 to the user information and associate the assigned user identifier with other user information. The third-party server 23 will also return the assigned user identifier to the user sub-server 22.

[0073] In step 208, after receiving the user identifier returned by the third-party server 23, the user sub-server 22 can also associate the user identifier with the user information currently stored in the user sub-server 22.

[0074] As can be seen, the user registration method in this embodiment is a lightweight user registration method. That is, when the application terminal 20 initiates a target transaction request, it triggers the registration of user information to the third-party server 23, rather than registering user information when the application terminal 20 initiates other requests. Since the processing of the target transaction request is simpler than the processing of other requests, when the user information registration is triggered based on the target transaction request, there will be no significant impact on the processing steps of the target transaction request itself and the user information registration steps, thus ensuring the processing performance of each step.

[0075] The following uses another specific application example to illustrate the user registration method in this invention. The user registration device in this embodiment is mainly a distributed system 100. The distributed system may include a client 300 and multiple nodes 200 (any form of computing device in the network, such as a server or user terminal). The client 300 and the nodes 200 are connected through network communication.

[0076] Taking a distributed system as an example, see blockchain system. Figure 6 This is an optional structural diagram of the distributed system 100 provided in this embodiment of the invention applied to a blockchain system. It consists of multiple nodes 200 (any form of computing device connected to the network, such as servers or user terminals) and clients 300. The nodes form a peer-to-peer (P2P) network. The P2P protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP). In the distributed system, any machine, such as a server or terminal, can join and become a node. A node includes a hardware layer, a middleware layer, an operating system layer, and an application layer.

[0077] See Figure 6 The functions of each node in the blockchain system shown include:

[0078] 1) Routing: A basic function of nodes used to support communication between nodes.

[0079] In addition to routing capabilities, nodes can also have the following functions:

[0080] 2) Applications are deployed in the blockchain to implement specific business needs. They record data related to the implementation of functions to form record data, carry digital signatures in the record data to indicate the source of the task data, and send the record data to other nodes in the blockchain system. When other nodes successfully verify the source and integrity of the record data, they add the record data to the temporary block.

[0081] For example, the application's business logic includes: code implementing the user registration function, which mainly includes:

[0082] The system receives a target transaction request sent by an application terminal, the target transaction request being used to request a transaction on a target object; determines the ownership set of the target object set corresponding to the target transaction request based on the target transaction request; if the ownership set includes a third-party server, obtains the user information corresponding to the target transaction request; and calls the communication interface of the third-party server to register the user information with the third-party server through the communication interface.

[0083] 3) A blockchain consists of a series of blocks that are sequentially generated. Once a new block is added to the blockchain, it will not be removed. The blocks contain the data submitted by the nodes in the blockchain system.

[0084] See Figure 7 This is an optional schematic diagram of the block structure provided in an embodiment of the present invention. Each block includes the hash value of the transaction records stored in this block (the hash value of this block) and the hash value of the previous block. The blocks are connected through their hash values ​​to form a blockchain. Additionally, the block may include information such as a timestamp when it was generated. A blockchain is essentially a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains relevant information used to verify the validity of the information (anti-counterfeiting) and to generate the next block.

[0085] This invention also provides a user registration device, such as the application server described above, the structural diagram of which is shown below. Figure 8 As shown, it can specifically include:

[0086] The request receiving unit 30 is used to receive a target transaction request sent by the application terminal, wherein the target transaction request is used to request a transaction to a target object.

[0087] The ownership determination unit 31 is used to determine the ownership set of the target object set corresponding to the target transaction request based on the target transaction request received by the request receiving unit 30.

[0088] The affiliation determination unit 31 is specifically used to find the affiliation corresponding to the target object if the target object set includes the target object, based on the identification information of the target object and the preset association relationship between each object and its affiliation.

[0089] Alternatively, the owner determination unit 31 is specifically used to find the owner corresponding to the target object and at least one associated object respectively, based on the identification information of the target object and the preset association relationship between each object and its owner, if the target object includes a target object and at least one associated object.

[0090] User acquisition unit 32 is used to acquire user information corresponding to the target transaction request if the set of owners determined by the owner determination unit 31 includes a third-party server.

[0091] User acquisition unit 32 is specifically used to provide a user selection interface to the application terminal if the target transaction request does not include a user identifier, the user selection interface including selection interfaces for other applications; receive information from the application terminal about the target application selected by the user through the selection interface, and obtain user information registered by the user in the system of the target application.

[0092] Alternatively, user acquisition unit 32 is specifically used to provide a user registration interface to the application terminal if the target transaction request does not include a user identifier. The user registration interface includes input interfaces for various dimensions of information; and to receive user information input by the user through the input interfaces sent by the application terminal.

[0093] Furthermore, the user acquisition unit 32 is specifically used to acquire the user information corresponding to the target transaction request when it is determined that the user information corresponding to the target transaction request has not been registered in the third-party server.

[0094] The registration unit 33 is used to call the communication interface of the third-party server and register the user information obtained by the user acquisition unit 32 into the third-party server through the communication interface.

[0095] In this way, when a user requests a transaction involving a target object from the user registration device of this embodiment via an application terminal, and the transaction involves an object on a third-party server, the user registration device is triggered to pre-register the user information with the third-party server. This allows the third-party server to associate the processing results of the relevant objects with the registered user information when the user further initiates other requests for each object in the target object set via the application terminal. This enables the server to accurately locate the processing results of the relevant objects without causing call failures, thus improving the user experience. Furthermore, since the processing of the target transaction request by the user registration device is simpler than the processing of other requests (such as payment requests), the registration of user information based on the target transaction request does not significantly affect the processing steps of the target transaction request itself or the registration steps of the user information, ensuring the processing performance of each step.

[0096] This invention also provides a server, the structural diagram of which is shown below. Figure 9 As shown, the server can vary considerably depending on its configuration or performance, and may include one or more central processing units (CPUs) 40 (e.g., one or more processors) and memory 41, and one or more storage media 42 (e.g., one or more mass storage devices) for storing application programs 421 or data 422. The memory 41 and storage media 42 can be temporary or persistent storage. The program stored in the storage media 42 may include one or more modules (not shown in the figure), each module including a series of instruction operations on the server. Furthermore, the CPU 40 may be configured to communicate with the storage media 42 and execute the series of instruction operations in the storage media 42 on the server.

[0097] Specifically, the application 421 stored in the storage medium 42 includes user-registered applications, and these applications may include the request receiving unit 30, the owner determination unit 31, the user acquisition unit 32, and the registration unit 33 in the aforementioned user registration device, which will not be elaborated upon here. Furthermore, the central processing unit 40 may be configured to communicate with the storage medium 42 and execute a series of operations corresponding to the user-registered applications stored in the storage medium 42 on a server.

[0098] The server may also include one or more power supplies 43, one or more wired or wireless network interfaces 44, one or more input / output interfaces 45, and / or one or more operating systems 423, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0099] The steps performed by the user registration device in the above method embodiments can be based on this. Figure 9 The server structure is shown.

[0100] This invention also provides a computer-readable storage medium storing a plurality of computer programs adapted for loading by a processor and executing a user registration method as described in the user registration system above.

[0101] This invention also provides a server, including a processor and a memory;

[0102] The memory is used to store multiple computer programs, which are loaded by a processor and executed as in the user registration method performed by the user registration system described above; the processor is used to implement each of the multiple computer programs.

[0103] Additionally, according to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the user registration method provided in the various optional implementations described above.

[0104] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0105] The foregoing has provided a detailed description of a user registration method, apparatus, storage medium, and server provided by embodiments of the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A user registration method, characterized in that, Used in application servers, including: Receive a target transaction request sent by the application terminal, the target transaction request being used to request a transaction on a target object; Determine the ownership set of at least one set of target objects corresponding to the target transaction request based on the target transaction request; If the set of parties includes a third-party server, obtain the user information corresponding to the target transaction request; The user information is registered with the third-party server by calling the communication interface of the third-party server through the communication interface. Wherein, when the target transaction request is a request initiated based on a registered user identifier, the target transaction request includes the registered user identifier, and registering the user information to the third-party server includes: obtaining the user information corresponding to the registered user identifier according to the registered user identifier in the target transaction request, and registering the user information to the third-party server.

2. The method as described in claim 1, characterized in that, The target transaction request includes the identification information of the target object, and the target object set includes the target object. Therefore, determining the set of owners of at least one target object set corresponding to the target transaction request specifically includes: Based on the identification information of the target object and the pre-defined association between each object and its owner, the owner corresponding to the target object is found.

3. The method as described in claim 1, characterized in that, The target object includes a target object and at least one associated object. The step of determining the set of parties to which the target object belongs, based on the target transaction request, specifically includes: Based on the identification information of the target object and the pre-defined associations between each object and its owner, the owner corresponding to the target object and at least one associated object is found.

4. The method according to any one of claims 1 to 3, characterized in that, If the target transaction request does not include a user identifier, then obtaining the user information corresponding to the target transaction request specifically includes: Provide a user selection interface to the application terminal, the user selection interface including selection interfaces for other applications; The system receives information from the application terminal about the target application selected by the user through the selection interface, and obtains user information registered by the user in the system of the target application.

5. The method according to any one of claims 1 to 3, characterized in that, If the target transaction request does not include a user identifier, then obtaining the user information corresponding to the target transaction request specifically includes: Provide a user registration interface to the application terminal, the user registration interface including input interfaces for various dimensions of information; Receive user information input by the user through the input interface, sent by the application terminal.

6. The method according to any one of claims 1 to 3, characterized in that, The step of obtaining the user information corresponding to the target transaction request specifically includes: If it is determined that the user information corresponding to the target transaction request is not registered in the third-party server, then the user information corresponding to the target transaction request is obtained.

7. A user registration device, characterized in that, Used in application servers, including: A request receiving unit is used to receive a target transaction request sent by an application terminal, wherein the target transaction request is used to request a transaction to a target object; The ownership determination unit is used to determine the ownership set of the target object set corresponding to the target transaction request based on the target transaction request; The user acquisition unit is used to acquire user information corresponding to the target transaction request if the set of parties includes a third-party server. The registration unit is used to call the communication interface of the third-party server and register the user information to the third-party server through the communication interface; Wherein, when the target transaction request is a request initiated based on a registered user identifier, the target transaction request includes the registered user identifier, and registering the user information to the third-party server includes: obtaining the user information corresponding to the registered user identifier according to the registered user identifier in the target transaction request, and registering the user information to the third-party server.

8. The apparatus as claimed in claim 7, characterized in that, The ownership determination unit is specifically used to find the ownership corresponding to the target object and at least one associated object respectively, based on the identification information of the target object and the preset association relationship between each object and its ownership, if the target transaction request includes the identification information of the target object and the target object set includes the target object and at least one associated object.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of computer programs adapted to be loaded by a processor and executed as described in any one of claims 1 to 6.

10. A server, characterized in that, Including processor and memory; The memory is used to store a plurality of computer programs, which are loaded by a processor and executed as described in any one of claims 1 to 6; the processor is used to implement each of the plurality of computer programs.

Images