WO2016026399A1 - 业务处理方法、装置及服务器 - Google Patents

业务处理方法、装置及服务器 Download PDF

Info

Publication number
WO2016026399A1
WO2016026399A1 PCT/CN2015/086613 CN2015086613W WO2016026399A1 WO 2016026399 A1 WO2016026399 A1 WO 2016026399A1 CN 2015086613 W CN2015086613 W CN 2015086613W WO 2016026399 A1 WO2016026399 A1 WO 2016026399A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user
service
authority
unit
Prior art date
Application number
PCT/CN2015/086613
Other languages
English (en)
French (fr)
Inventor
陈礼军
叶玲玲
Original Assignee
阿里巴巴集团控股有限公司
陈礼军
叶玲玲
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 陈礼军, 叶玲玲 filed Critical 阿里巴巴集团控股有限公司
Priority to US15/505,400 priority Critical patent/US10389726B2/en
Priority to EP15834266.7A priority patent/EP3185513A4/en
Priority to SG11201700628SA priority patent/SG11201700628SA/en
Priority to KR1020177004748A priority patent/KR101984153B1/ko
Priority to JP2017510299A priority patent/JP6463463B2/ja
Priority to KR1020197014981A priority patent/KR102055533B1/ko
Publication of WO2016026399A1 publication Critical patent/WO2016026399A1/zh
Priority to US16/429,141 priority patent/US11005848B2/en
Priority to US17/224,199 priority patent/US11218489B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/229—Hierarchy of users of accounts
    • G06Q20/2295—Parent-child type, e.g. where parent has control on child rights
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223—Realising banking transactions through M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3674—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes involving authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service processing method, apparatus, and server.
  • the terminal user can only perform various service operations based on the own account, so the service implementation manner is relatively simple, and the interaction efficiency of the service information is not high.
  • the application provides a service processing method, a device, and a server, so as to solve the problem that the existing service implementation mode is relatively simple, and the interaction efficiency of the service information is not high.
  • a service processing method which is applied to a service processing server, and the method includes:
  • the second account information of the second account is updated according to the operation result of the service operation.
  • a service processing apparatus which is applied to a service processing server, where the apparatus includes:
  • a receiving unit configured to receive, after the first user logs in based on the first account on the client device, an operation request that the first user requests to perform a service operation
  • a searching unit configured to search for a saved account binding relationship according to the first account
  • control unit configured to allow the first user to complete the service operation by using a second account authority of the second account if a second account of the second user bound to the first account is found;
  • an updating unit configured to update second account information of the second account according to an operation result of the service operation after the first user completes the service operation by using the second account authority.
  • a server including:
  • processor a memory for storing the processor executable instructions
  • processor is configured to:
  • the second account information of the second account is updated according to the operation result of the service operation.
  • FIG. 1 is a schematic diagram of an application scenario of a service processing embodiment of the present application
  • FIG. 2 is a flow chart of an embodiment of a service processing method of the present application
  • 3A is a flow chart of another embodiment of a service processing method of the present application.
  • FIG. 3B is a schematic diagram of a selection interface of a recommended account list in the embodiment of the present application.
  • 3C is a schematic diagram of a user selecting a service operation account based on an optional account list in the embodiment of the present application;
  • FIG. 4 is a flow chart of another embodiment of a service processing method of the present application.
  • FIG. 5 is a hardware structural diagram of a server where a service processing device of the present application is located;
  • FIG. 6 is a block diagram of an embodiment of a service processing apparatus of the present application.
  • FIG. 7 is a block diagram of another embodiment of the service processing apparatus of the present application.
  • FIG. 8 is a block diagram of another embodiment of the service processing apparatus of the present application.
  • FIG. 9 is a block diagram of another embodiment of a service processing apparatus of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a schematic diagram of an application scenario of a service processing embodiment of the present application:
  • the user shown in FIG. 1 accesses the server through the network.
  • the user specifically refers to various client devices having a network connection function, such as a mobile phone, a tablet computer, etc., of course, the embodiment of the present application is not excluded from the PC. (Personal Computer, personal computer) application.
  • the first user registers the first account on the server
  • the second user registers the second account on the server
  • the server saves the correspondence between the registered account, the service password and the account information through the user account list, and the user uses the respective registered account.
  • various service operations can be completed by using the account rights of the respective accounts, and the server updates the account information of the user according to the completion result of the business operations.
  • the service implementation manner may be extended based on the intimate relationship between users, and the interaction efficiency of the service information may be improved.
  • the first user has a close relationship with the second user, and after the second user authorizes the first user to use the account rights of the second account, the server saves the binding of the first account and the second account. Relationship, the subsequent first user can directly use the account rights of the bound second account to complete various business operations, and after the business operation is completed, the second account information is directly updated by the server.
  • FIG. 2 it is a flowchart of an embodiment of a service processing method of the present application:
  • Step 201 After the first user logs in based on the first account on the client device, receive an operation request for the first user to perform a business operation.
  • the first user may log in to the server based on the first account to complete various service operations.
  • the first account is information that the server can uniquely identify the first user, and includes the user name of the first user.
  • the first account is [email protected]
  • the second account is “[email protected]”.
  • the business operation mainly refers to various application functions provided by the server to the user, for example, the payment function provided by the third-party payment server to the user for performing payment operations on the online shopping item, or the multimedia provided by the instant communication server to the user in the network storage space.
  • the file download function for downloading operations, etc.
  • Step 202 Find a saved account binding relationship according to the first account.
  • a binding relationship between a plurality of different accounts is pre-stored in the account binding relationship list of the server.
  • the server may search the account binding relationship list according to the first account to determine whether there are other accounts bound to the first account, so that the first user can pass the account rights of the other account. Complete the business operation.
  • Step 203 If the second account of the second user bound to the first account is found, the first user is allowed to complete the business operation through the second account authority of the second account.
  • the server when the server finds the second account bound to the first account in the account binding relationship list, the server may output an optional account list on the current service operation interface of the first user, where the optional account list is In addition to including the first account, the second account may also include a second account bound to the first account; if the first user selects to use the second account from the list of selectable accounts for business operations, and enters a service password; the server verifies the input When the service password is consistent with the first service password when the first user registers the first account, the first user is released to perform the business operation through the second account authority of the second account.
  • Step 204 After the first user completes the business operation through the second account authority, according to the business operation The result of the operation updates the second account information of the second account.
  • the server since the first user completes the service operation by using the second account authority, after the service operation is completed, the account information of the first account does not change, and the server can directly update the second account according to the operation result of the service operation.
  • Second account information For example, after the first user completes a certain payment operation through the payment account of the second account, the server updates the account balance in the payment account; for example, the first user accesses the storage space of the second account through the account authority of the second account. After downloading the multimedia file, the server updates the download record of the multimedia file in the storage space of the second account.
  • the server may first determine the security attributes of the service scenario corresponding to the current service operation.
  • the security attribute is secure
  • the first user may be allowed to perform the business operation by using the second account right.
  • the security attribute is insecure, the first user may be prohibited from performing the business operation through the second account right.
  • Users can only perform business operations through their first account privileges. For example, for a payment operation, when the business scenario is a domestic commodity transaction, the corresponding security attribute is security, and when the business scenario is an overseas purchasing transaction, the corresponding security attribute is unsafe.
  • the second user can authorize the first user who has a close relationship with himself to use the second account right of the second user, the first user can be made to complete each based on the account rights of the bound multiple accounts.
  • the business operation thus expanding the service implementation manner; and directly updating the second account information due to the completion of the business operation, the number of transmissions of the business data between different accounts can be reduced, thereby improving the interaction efficiency of the business information.
  • FIG. 3A it is a flowchart of another embodiment of the service processing method of the present application.
  • the embodiment details the process of binding the authorized account and releasing the account in combination with the implementation process of the service processing:
  • Step 301 The server sends a recommended account list to the second user, where the recommended account list is included An account of the user including at least one intimacy relationship value with the second user exceeding a preset relationship threshold.
  • the server may provide the user with a recommended account list according to the intimate relationship between the user and other users, where the recommended account list includes several accounts that can authorize binding of the user's account. .
  • the server may calculate the intimacy relationship between the user and other users based on various relationship indicators between the user and other users according to a preset algorithm, and add the account to the user whose intimacy relationship value is greater than the preset relationship threshold. Go to the list of recommended accounts. For example, if the second user's friend list includes several users, the server may calculate the second user and the different users according to the instant communication time, the number of instant communication messages, and the like between the second user and the different users in the friend list. Intimacy value.
  • Step 302 The second user sends an authorization message to the server, where the authorization message includes a first account selected by the second user from the recommended account list, and a used condition of the set second account authority.
  • the one or more authorized binding accounts may be selected from the account recommendation list.
  • the second user is selected from the recommended account list.
  • Account As shown in FIG. 3B, a selection interface diagram of a recommended account list is shown, in which the second user selects the first account “[email protected]” from the recommended account list as the account for authorization binding.
  • the second user may set the use condition that the first account can use the second account right, for example, for the payment type business operation, the use condition of the second account right may be adopted.
  • the second account authority performs an upper limit of the amount of the payment operation.
  • the usage condition of the second account authority may be the download time, the number of downloads, and the like of the multimedia file download using the second account authority.
  • the foregoing information may be carried in the authorization message and sent to the server.
  • the second user may not select the account to be bound by the account based on the account recommendation list, but directly send the account that wants to authorize the binding to the server through the authorization message by using the authorization condition of the account authority of the account. Correct This embodiment of the present application is not limited.
  • Step 303 The server saves the binding relationship between the first account and the second account in the account binding relationship according to the authorization message.
  • the server obtains the first account from the received authorization message, and saves the binding relationship between the first account and the second account in the account binding relationship list, and carries the authorization message.
  • the server can further save the use condition in the above binding relationship.
  • the server can use the following two methods when saving the binding relationship:
  • the server can maintain a list of account binding relationships, and each entry in the list is used to save a binding relationship between accounts, as shown in Table 1 below:
  • the server can maintain a separate account binding relationship list for each account. Each entry in the list is used to save the binding relationship between a binding account and other authorized accounts, as shown in Table 2 below.
  • Step 304 After the first user logs in based on the first account on the client device, the first user sends an operation request for performing a business operation to the server.
  • Step 305 The server searches for an account binding relationship according to the first account of the first user.
  • the server may query the account binding relationship list as described in step 303.
  • the server may search for the "Bind Account” field according to the first account "[email protected]”, and obtain and " The corresponding "authorized account” of [email protected] includes the second account "[email protected]”; or, in conjunction with the foregoing Table 2, the server can find the user1 maintained according to the first account "[email protected]".
  • the account binding relationship list directly obtains all authorized accounts of the first account [email protected] from the list, including the second account [email protected].
  • Step 306 When the server finds the second account bound to the first account, the server is allowed to complete the business operation by using the second account authority of the second account under the use condition of the second account.
  • the optional account list may be output on the current service operation interface of the first user, where the optional account list includes the first account.
  • a second account bound to the first account may also be included.
  • the server verifies that the input service password is consistent with the first service password when the first user registers the first account, and releases The first user performs a business operation through the second account authority of the second account.
  • FIG. 3C a schematic diagram for the user to select a business operation account based on the selectable account list: wherein the first user selects the second account "[email protected]" from the list of selectable accounts as the account for performing the business operation.
  • the first user may also select a plurality of other accounts from the optional account list to perform the service operation at the same time, and the multiple accounts may also include the first user itself.
  • the first account of the present application is not limited to the embodiment of the present application. For example, when the first user performs the payment operation, the funds in the payment account under the first account and the funds in the payment account under the second account can be used to complete the payment operation.
  • Step 307 After the first user completes the business operation by using the second account authority, the server updates the second account information of the second account according to the operation result of the business operation.
  • the server can directly update the second account according to the operation result of the service operation. Second account information.
  • Step 308 The second user sends an authorization release message to the server, where the authorization release message includes the first account.
  • the second user can authorize the first user to use the second account right of the second account by sending an authorization message to the server.
  • the second user can also send an authorization release message to the server.
  • the first user uses the second account rights of his second account.
  • the authorization release message carries the first account of the first user to be unbound.
  • Step 309 The server deletes the binding relationship between the first account and the second account from the account binding relationship according to the authorization release message.
  • the server may query the account binding relationship list as described in step 303.
  • the server may search for the second account “[email protected]” under the authorized account.
  • the server can find the account binding relationship list 2 maintained for user1 according to the first account "[email protected]”, and find the second account "[email protected]” from the table 2 , delete the second account "[email protected]” from Table 2.
  • the second user can authorize the first user who has a close relationship with himself to use the second account right of the second user, the first user can be made to complete each based on the account rights of the bound multiple accounts.
  • Business operation thus extending the service implementation manner; since the business operation is completed to directly update the second account information, the number of transmissions of the business data between different accounts can be reduced, thereby improving the interaction efficiency of the business information; and the user can Flexibly authorize or deauthorize other users to perform business operations using the user's account permissions as needed, thereby ensuring the security of the authorized account while extending the service implementation.
  • FIG. 4 it is a flowchart of another embodiment of the service processing method of the present application.
  • the embodiment details the account information update and service reverse operation process of the bound account in combination with the implementation process of the service processing:
  • Step 401 The first user registers the first account with the server.
  • Step 402 The server saves the correspondence between the first account and the first service password in the user account.
  • the server When the user wants to use the various services provided by the server, the user first needs to register on the server. At this time, the server outputs a registration interface to the user, and the user inputs the account name and the service password.
  • the user password is the same as the user's login password. It is also a service password that is set to be independent of the login password.
  • the embodiment of the present application is not limited. For the service passwords related to the service operations, the login passwords may be set together in the registration interface, which is not described in detail in this application.
  • the server may save the correspondence between the account and the service password when the user is registered through the user account list, and the account information of each account, as shown in Table 3 below, including the registration information of the first user and the second user.
  • User account list :
  • Step 403 After the first user logs in based on the first account on the client device, the first user sends an operation request for performing a business operation to the server.
  • Step 404 The server searches for the saved account binding relationship according to the first account.
  • Step 405 When the server finds the second account bound to the first account, the server outputs a second account as an optional account on the service operation interface of the first user.
  • the optional account list may be output on the current service operation interface of the first user, where the optional account list includes the first account.
  • other accounts bound to the first account may be included, for example, the second account in this embodiment.
  • Step 406 After the first user selects the second account to perform the business operation, the first user selects the service password input to the server.
  • Step 407 When the server verifies that the input service password is consistent with the first service password saved in the account information, the first user is released to perform the business operation through the second account authority.
  • the service password at the time of registration may still be used, and the server finds the account information of the first user from Table 3, and obtains the first account “user1@ABC.
  • the service password of com" is "user1abcde”. If the service password entered by the first user is the same as “user1abcde", the server releases the second account authority to perform the business operation of the first account.
  • Step 408 After the first user completes the business operation by using the second account authority, the server updates the second account information of the second account according to the operation result of the business operation.
  • the server can directly update the second account according to the operation result of the service operation. Second account information.
  • Step 409 The server sends a notification message to the second user to notify the second user of the updated content of the second account information.
  • the notification message sent by the server to the second user may be to send a short message to the terminal device registered by the user, or send an instant communication message to the second account.
  • Step 410 The first user sends a reverse operation request for the service operation to the server.
  • Step 411 After the reverse operation of the business operation is completed, the server updates the second account information according to the operation result of the reverse operation.
  • the first user passes the third party payment server in step 408, and uses the second account branch.
  • the payment account completes the payment operation of the purchased product
  • the first user returns the product, and the first user sends a refund request to the third-party payment server, and the third-party payment server sends the product to the third-party payment server.
  • the deducted amount is directly returned to the payment account of the second account, and after the refund is completed, the account balance information in the payment account is directly updated.
  • the second user can authorize the first user who has a close relationship with himself to use the second account right of the second user, the first user can be made to complete each based on the account rights of the bound multiple accounts.
  • Business operations thus extending the business implementation; and because the business operations and reverse business operations are completed, the second account information is directly updated, thereby reducing the number of times the business data is transmitted between different accounts, thereby improving the business information. Interaction efficiency.
  • the present application also provides an embodiment of the service processing apparatus.
  • Embodiments of the business processing apparatus of the present application can be applied to a server.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical means, the processor of the server in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • the processor of the server in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • FIG. 5 a hardware structure diagram of a server where the service processing apparatus of the present application is located, except for the processor, the memory, the network interface, and the non-volatile memory shown in FIG.
  • the server where the device is located in the embodiment may also include other hardware according to the actual function of the server, and details are not described herein again.
  • the apparatus includes: a receiving unit 610, a searching unit 620, a control unit 630, and an updating unit 640.
  • the receiving unit 610 is configured to: after the first user logs in based on the first account on the client device, receive an operation request that the first user requests to perform a service operation;
  • the searching unit 620 is configured to search for the saved account binding relationship according to the first account.
  • the control unit 630 is configured to allow the first user to complete the service operation by using the second account authority of the second account if the second account of the second user bound to the first account is found Work
  • the updating unit 640 is configured to update the second account information of the second account according to the operation result of the service operation after the first user completes the service operation by using the second account authority.
  • FIG. 7 is a block diagram of another embodiment of a service processing apparatus according to the present application.
  • the apparatus includes: a sending unit 710, a receiving unit 720, a first saving unit 730, a searching unit 740, a control unit 750, an updating unit 760, and a deleting unit 770. .
  • the sending unit 710 is configured to send a recommended account list to the second user, where the recommended account list includes at least one account of the user whose intimacy relationship value with the second user exceeds a preset relationship threshold;
  • the receiving unit 720 is configured to receive an authorization message of the second user, where the authorization message includes a first account selected by the second user from the recommended account list;
  • the first saving unit 730 is configured to save, in the account binding relationship, a binding relationship between the first account and the second account of the second user according to the authorization message;
  • the receiving unit 720 is further configured to: after the first user logs in based on the first account on the client device, receive an operation request that the first user requests to perform a service operation;
  • the searching unit 740 is configured to search for a saved account binding relationship according to the first account.
  • the control unit 750 is configured to allow the first user to complete the service operation by using the second account authority of the second account if the second account bound to the first account is found;
  • the updating unit 760 is configured to update the second account information of the second account according to the operation result of the service operation after the first user completes the service operation by using the second account authority;
  • the receiving unit 720 is further configured to receive an authorization release message sent by the second user, where the authorization release message includes the first account;
  • the deleting unit 770 is configured to delete the binding relationship between the first account and the second account from the account binding relationship according to the authorization release message.
  • the authorization message received by the receiving unit 720 may further include the second account permission. Conditions of use;
  • the control unit 750 may be specifically configured to allow the first user to complete the service operation by using the second account authority of the second account under the use condition.
  • FIG. 8 is a block diagram of another embodiment of a service processing apparatus according to the present application.
  • the apparatus includes: a second saving unit 810, a receiving unit 820, a searching unit 830, a control unit 840, an updating unit 850, and a notifying unit 860.
  • the second saving unit 810 is configured to save a correspondence between the first account and the first service password when the first user registers the first account.
  • the receiving unit 820 is configured to: after the first user logs in based on the first account on the client device, receive an operation request that the first user requests to perform a service operation;
  • the searching unit 830 is configured to search for the saved account binding relationship according to the first account.
  • the control unit 840 is configured to allow the first user to complete the service operation by using the second account authority of the second account if the second account bound to the first account is found;
  • the updating unit 850 is configured to update the second account information of the second account according to the operation result of the service operation;
  • the notification unit 860 is configured to send a notification message to the second user after updating the second account information of the second account to notify the second user of the updated content of the second account information.
  • the control unit 840 can include (not shown in Figure 8):
  • An account output subunit configured to output the second account as an optional account in a service operation interface of the first user
  • a password receiving subunit configured to receive a service password input by the first user after selecting the second account to perform a business operation
  • the privilege release sub-unit is configured to release the first user to perform a business operation by using the second account privilege when verifying that the input service password is consistent with the first service password saved in the correspondence relationship.
  • the receiving unit 820 is further configured to receive a reverse operation request sent by the first user for the service operation;
  • the updating unit 850 is further configured to: after the reverse operation of the service operation is completed, update the second account information according to the operation result of the reverse operation.
  • FIG. 9 is a block diagram of another embodiment of a service processing apparatus according to the present application.
  • the apparatus includes: a receiving unit 910, a searching unit 920, a determining unit 930, an executing unit 940, a control unit 950, and an updating unit 960.
  • the receiving unit 910 is configured to: after the first user logs in based on the first account on the client device, receive an operation request that the first user requests to perform a service operation;
  • the searching unit 920 is configured to search for a saved account binding relationship according to the first account.
  • the determining unit 930 is configured to determine a security attribute of the service scenario corresponding to the service operation if the second account bound to the first account is found;
  • the executing unit 940 is configured to: when the security attribute is secure, trigger the control unit to perform a corresponding function; when the security attribute is insecure, prohibit the first user from performing a business operation by using the second account authority .
  • the control unit 950 is configured to allow the first user to complete the service operation by using the second account authority of the second account after receiving the triggering instruction of the execution unit;
  • the updating unit 960 is configured to update the second account information of the second account according to the operation result of the service operation.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located a place, Or it can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the second user can authorize the first user who has a close relationship with himself to use the second account right of the second user, the first user can be made to complete each based on the account rights of the bound multiple accounts.
  • the business operation thus expanding the service implementation manner; and directly updating the second account information due to the completion of the business operation, the number of transmissions of the business data between different accounts can be reduced, thereby improving the interaction efficiency of the business information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Finance (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Child & Adolescent Psychology (AREA)
  • Health & Medical Sciences (AREA)
  • Multimedia (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请公开了业务处理方法、装置及服务器，所述方法包括：当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；根据所述第一账户查找已保存的账户绑定关系；如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。应用本申请实施例，可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；并且可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率。

Description

业务处理方法、装置及服务器 技术领域
本申请涉及通信技术领域，尤其涉及业务处理方法、装置及服务器。
背景技术
随着智能终端的发展和网络应用的普及，用户可以通过终端上安装的各种应用客户端实现各种业务操作，例如，社交类即时通信业务，购物支付类业务等。要实现上述业务，终端用户往往需要在服务器上注册业务账户，并基于该业务账户实现一定的业务操作。
但是，现有技术中，终端用户只能基于自身账户完成各种业务操作，因此业务实现方式比较单一，业务信息的交互效率不高。
发明内容
本申请提供业务处理方法、装置及服务器，以解决现有业务实现方式比较单一，业务信息的交互效率不高的问题。
根据本申请实施例的第一方面，提供一种业务处理方法，应用于业务处理服务器，所述方法包括：
当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
根据所述第一账户查找已保存的账户绑定关系；
如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
根据本申请实施例的第二方面，提供一种业务处理装置，应用于业务处理服务器，所述装置包括：
接收单元，用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
查找单元，用于根据所述第一账户查找已保存的账户绑定关系；
控制单元，用于如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
更新单元，用于在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
根据本申请实施例的第三方面，提供一种服务器，包括：
处理器；用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：
当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
根据所述第一账户查找已保存的账户绑定关系；
如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
应用本申请实施例提供的技术方案，当第一用户基于第一账户登录后，如果应用服务器查找到账户绑定关系中有第一账户与第二账户的绑定关系，则允许第一用户通过第二用户的第二账户权限完成业务操作，并在业务操作完成后直接更新第二账户的第二账户信息。应用本申请实施例，由于第二用户可以授权与自身具有亲密关系的第一用户使用第二用户的第二账户权限，从而可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；并且由于业务操作完成直接对第二账户信息 进行更新，因此可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1是本申请业务处理实施例的应用场景示意图；
图2是本申请业务处理方法的一个实施例流程图；
图3A是本申请业务处理方法的另一个实施例流程图；
图3B是本申请实施例中推荐账户列表的选择界面示意图；
图3C是本申请实施例中用户基于可选账户列表选择业务操作账户的示意图；
图4是本申请业务处理方法的另一个实施例流程图；
图5是本申请业务处理装置所在服务器的一种硬件结构图；
图6是本申请业务处理装置的一个实施例框图；
图7是本申请业务处理装置的另一个实施例框图；
图8是本申请业务处理装置的另一个实施例框图；
图9是本申请业务处理装置的另一个实施例框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一 些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
参见图1，是本申请业务处理实施例的应用场景示意图：
图1中示出的用户通过网络接入到服务器，本申请中用户具体指各种具有网络连接功能的客户端设备，例如，手机、平板电脑等，当然，本申请实施例也不排除在PC(Personal Computer，个人计算机)上的应用。其中，第一用户在服务器上注册第一账户，第二用户在服务器上注册第二账户，服务器通过用户账户列表保存已注册的账户、业务密码及账户信息的对应关系，用户利用各自注册的账户登录服务器后，可以利用各自账户的账户权限完成各种业务操作，服务器根据业务操作的完成结果，更新用户的账户信息。
本申请实施例中，可以基于用户之间的亲密关系，扩展业务实现方式，提高业务信息的交互效率。如图1中，第一用户与第二用户之间具有亲密关系，在第二用户授权第一用户可以使用其第二账户的账户权限后，由服务器保存第一账户与第二账户的绑定关系，后续第一用户可以直接使用绑定的第二账户的账户权限完成各种业务操作，并在业务操作完成后，由服务器直接更新第二账户信息。下面将结合附图1对本申请实施例进行详细描述。
参见图2，是本申请业务处理方法的一个实施例流程图：
步骤201：当第一用户在客户端设备上基于第一账户登录后，接收第一用户请求进行业务操作的操作请求。
本申请实施例中，第一用户在服务器上注册第一账户后，可以基于第一账户登录服务器，以完成各种业务操作。其中，第一账户是可以由服务器唯一识别第一用户的信息，其包含了第一用户的用户名，例如，第一账户为[email protected]，第二账户为“[email protected]”；业务操作主要指服务器向用户提供的各种应用功能，例如，第三方支付服务器向用户提供的对网购物品进行支付操作的支付功能，或者即时通信服务器向用户提供的对网络存储空间内的多媒体文件进行下载操作的下载功能等。
步骤202：根据第一账户查找已保存的账户绑定关系。
本申请实施例中，基于用户间的亲密关系，在服务器的账户绑定关系列表中预先保存了若干不同账户之间的绑定关系。当第一用户向服务器发送了业务操作请求时，服务器可以根据第一账户查找账户绑定关系列表，确定是否有与第一账户绑定的其他账户，以便第一用户可以通过其他账户的账户权限完成该业务操作。
步骤203：如果查找到与第一账户绑定的第二用户的第二账户，允许第一用户通过第二账户的第二账户权限完成业务操作。
本申请实施例中，当服务器在账户绑定关系列表中查找到与第一账户绑定的第二账户时，可以在第一用户当前的业务操作界面输出可选账户列表，该可选账户列表中除了包含第一账户外，还可以包含与第一账户绑定的第二账户；如果第一用户从可选账户列表中选择采用第二账户进行业务操作，并输入业务密码；服务器验证输入的业务密码与第一用户注册第一账户时的第一业务密码一致时，则放行第一用户通过第二账户的第二账户权限进行业务操作。
步骤204：在第一用户通过第二账户权限完成业务操作后，根据业务操 作的操作结果更新第二账户的第二账户信息。
本申请实施例中，由于第一用户采用第二账户权限完成业务操作，因此业务操作完成后，第一账户的账户信息不会发生变化，服务器可以根据业务操作的操作结果直接更新第二账户的第二账户信息。例如，第一用户通过第二账户的支付账户完成某笔支付操作后，服务器更新该支付账户内的账户余额；又例如，第一用户通过第二账户的账户权限从第二账户的存储空间内下载了多媒体文件后，服务器更新该第二账户的存储空间内多媒体文件的下载记录。
另外，在兼容各种业务操作的可能业务场景的同时，为了进一步提高业务操作的安全性，保证业务操作过程中绑定账户的用户信息不会被恶意第三方窃取，在上述实施例中，可以预先设置不同业务场景与业务操作的安全属性之间的对应关系，当服务器查找到与第一账户绑定的第二用户的第二账户后，可以先判断当前业务操作对应的业务场景的安全属性，当安全属性为安全时，则可以允许第一用户通过第二账户权限进行业务操作，当安全属性为不安全时，则可以禁止第一用户通过第二账户权限进行业务操作，此时第一用户仅能通过其第一账户权限进行业务操作。例如，对于支付操作，当其业务场景为国内商品交易时，则对应安全属性为安全，当其业务场景为海外代购交易时，则对应安全属性为不安全。
由上述实施例可见，由于第二用户可以授权与自身具有亲密关系的第一用户使用第二用户的第二账户权限，从而可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；并且由于业务操作完成直接对第二账户信息进行更新，因此可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率。
参见图3A，是本申请业务处理方法的另一个实施例流程图，该实施例结合业务处理的实现过程详细示出了授权账户绑定与解除账户绑定的过程：
步骤301：服务器向第二用户发送推荐账户列表，该推荐账户列表中包 含至少一个与第二用户的亲密关系值超过预设关系阈值的用户的账户。
本申请实施例中，对于每个注册用户，服务器可以根据该用户与其他用户之间的亲密关系向该用户提供推荐账户列表，该推荐账户列表中包含可以授权绑定该用户的账户的若干账户。
其中，服务器可以按照预设算法，基于该用户与其他用户之间的各种关系指标计算该用户与其他用户的亲密关系值，对于亲密关系值大于预设关系阈值的用户，则将其账户添加到推荐账户列表中。例如，第二用户的朋友列表中包含若干用户，则服务器可以根据第二用户与朋友列表中的不同用户之间的即时通信时间、即时通信消息数量等，计算第二用户与不同用户之间的亲密关系值。
步骤302：第二用户向服务器发送授权消息，该授权消息中包含第二用户从推荐账户列表中选择的第一账户，以及设置的第二账户权限的使用条件。
当第二用户接收到服务器发送的账户推荐列表后，可以从该账户推荐列表中选择一个或多个授权绑定的账户，本申请实施例中假设第二用户从推荐账户列表中选择了第一账户。如图3B，示出了推荐账户列表的选择界面示意图，其中第二用户从推荐账户列表中点选第一账户“[email protected]”作为授权绑定的账户。
进一步，第二用户可以在选择了授权绑定的第一账户后，设置第一账户能够使用第二账户权限的使用条件，例如，对于支付类业务操作，第二账户权限的使用条件可以是采用第二账户权限进行支付操作的金额上限，又例如，对于即时通信类业务操作，第二账户权限的使用条件可以是采用第二账户权限进行多媒体文件下载的下载时间、下载数量等。
在第二用户选择了第一账户，并进一步设置了第二账户权限的使用条件后，可以将上述信息携带在授权消息发送给服务器。需要说明的是，第二用户也可以不基于账户推荐列表选择授权绑定的账户，而是直接将想要授权绑定的账户，以该账户的账户权限的使用条件通过授权消息发送给服务器，对 此本申请实施例不进行限制。
步骤303：服务器根据授权消息在账户绑定关系中保存第一账户与第二账户的绑定关系。
本申请实施例中，服务器从接收到的授权消息中获得第一账户，并将第一账户与第二账户之间的绑定关系保存在账户绑定关系列表中，当授权消息中还携带了使用条件时，则服务器可以进一步在上述绑定关系中保存该使用条件。
其中，服务器在保存绑定关系时，可以采用如下两种方式：
第一种方式，服务器可以维护一张账户绑定关系列表，该列表中的每个表项用于保存一个账户之间的绑定关系，如下表1所示：
表1
授权账户 绑定账户
[email protected] [email protected]
…… ……
[email protected] [email protected]
第二种方式，服务器可以为每个账户单独维护一张账户绑定关系列表，该列表的每一个表项用于保存一个绑定账户与其他授权账户之间的绑定关系，如下表2示例了为第一用户user1维护的账户绑定关系列表：
表2
Figure PCTCN2015086613-appb-000001
步骤304：当第一用户在客户端设备上基于第一账户登录后，第一用户向服务器发送进行业务操作的操作请求。
步骤305：服务器根据第一用户的第一账户查找账户绑定关系。
本申请实施例中，服务器可以查询如步骤303中描述的账户绑定关系列表，结合前述表1，服务器可以根据第一账户“[email protected]”查找“绑定账户”字段，获得与“[email protected]”对应的“授权账户”包括第二账户“[email protected]”；或者，结合前述表2，服务器可以根据第一账户“[email protected]”查找到为user1维护的账户绑定关系列表，直接从该列表中获得第一账户[email protected]的所有授权账户，其中包括了第二账户[email protected]。
步骤306：服务器在查找到与第一账户绑定的第二账户时，允许第一用户在第二账户的使用条件下，通过第二账户的第二账户权限完成业务操作。
当服务器在账户绑定关系列表中查找到与第一账户绑定的第二账户时，可以在第一用户当前的业务操作界面输出可选账户列表，该可选账户列表中除了包含第一账户外，还可以包含与第一账户绑定的第二账户。
如果第一用户从可选账户列表中选择采用第二账户进行业务操作，并输入了业务密码，则服务器验证输入的业务密码与第一用户注册第一账户时的第一业务密码一致时，放行第一用户通过第二账户的第二账户权限进行业务操作。如图3C所示，为用户基于可选账户列表选择业务操作账户的示意图：其中第一用户从可选账户列表中点选第二账户“[email protected]”作为进行业务操作的账户。
需要说明的是，第一用户除了可以选择第二账户进行业务操作外，也可以从可选账户列表中选择多个其他账户同时进行该业务操作，该多个账户中也可以包括第一用户自身的第一账户，对此本申请实施例不进行限制。例如，第一用户在进行支付操作时，可以采用自身第一账户下的支付账户内的资金，以及第二账户下的支付账户内的资金共同完成支付操作。
步骤307：在第一用户通过第二账户权限完成业务操作后，服务器根据业务操作的操作结果更新第二账户的第二账户信息。
本申请实施例中，由于第一用户采用第二账户权限完成业务操作，因此业务操作完成后，第一账户的账户信息不会发生变化，服务器可以根据业务操作的操作结果直接更新第二账户的第二账户信息。
步骤308：第二用户向服务器发送授权解除消息，该授权解除消息中包含第一账户。
结合步骤302可知，第二用户通过向服务器发送授权消息，授权第一用户可以使用其第二账户的第二账户权限，同样本步骤中，第二用户也可以通过向服务器发送授权解除消息，禁止第一用户使用其第二账户的第二账户权限。其中，授权解除消息中携带了要解除绑定的第一用户的第一账户。
步骤309：服务器根据授权解除消息从账户绑定关系中删除第一账户与第二账户的绑定关系。
服务器接收到第二用户的授权解除消息后，可以查询如步骤303中描述的账户绑定关系列表，结合前述表1，服务器可以在授权账户下查找第二账户“[email protected]”，当查找到“[email protected]”，且其对应的授权账户为第一账户“[email protected]”时，则从表1中删除上述第一账户与第二账户之间的绑定关系；结合前述表2，服务器可以根据第一账户“[email protected]”查找到为user1维护的账户绑定关系列表2，并从该表2中查找到第二账户“[email protected]”后，从表2中删除该第二账户“[email protected]”。
由上述实施例可见，由于第二用户可以授权与自身具有亲密关系的第一用户使用第二用户的第二账户权限，从而可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；由于业务操作完成直接对第二账户信息进行更新，因此可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率；并且用户可以根据需要灵活授权或解除授权其他用户使用该用户的账户权限进行业务操作，从而可以在扩展业务实现方式的同时，保证授权账户的安全性。
参见图4，是本申请业务处理方法的另一个实施例流程图，该实施例结合业务处理的实现过程详细示出了绑定账户的账户信息更新及业务反向操作过程：
步骤401：第一用户向服务器注册第一账户。
步骤402：服务器在用户账户内保存第一账户与第一业务密码的对应关系。
当用户要使用服务器提供的各种业务时，首先需要在服务器上进行注册，此时服务器向用户输出注册界面，用户输入账户名和业务密码，需要说明的时，本申请实施例中的业务密码可以与用户的登录密码一致，也可以是独立于登录密码设置的专用于完成业务操作的业务密码，对此本申请实施例不进行限制，由于本申请实施例重点在于描述业务操作过程，因此仅描述与业务操作相关的业务密码，登录密码可以在注册界面内一并设置，对此本申请实施例不进行赘述。
本申请实施例中服务器可以通过用户账户列表保存用户注册时的账户与业务密码的对应关系，以及每个账户的账户信息，如下表3示出了包括第一用户与第二用户的注册信息的用户账户列表：
表3
账户 业务密码 账户信息
[email protected] user1abcde user1*****
[email protected] user2edcba user2*****
…… …… ……
步骤403：当第一用户在客户端设备上基于第一账户登录后，第一用户向服务器发送请求进行业务操作的操作请求。
步骤404：服务器根据第一账户查找已保存的账户绑定关系。
步骤405：服务器在查找到与第一账户绑定的第二账户时，在第一用户的业务操作界面输出作为可选账户的第二账户。
当服务器在账户绑定关系列表中查找到与第一账户绑定的第二账户时，可以在第一用户当前的业务操作界面输出可选账户列表，该可选账户列表中除了包含第一账户外，还可以包含与第一账户绑定的其他账户，例如，本实施例中的第二账户。
步骤406：第一用户选择第二账户进行业务操作后，向服务器发送输入的业务密码。
步骤407：服务器验证输入的业务密码与账户信息中保存的第一业务密码一致时，放行第一用户通过第二账户权限进行业务操作。
本步骤中，第一用户选择第二账户进行业务操作时，可以仍然使用自身注册时的业务密码，服务器从表3中查找到第一用户的账户信息，从中获取第一账户“[email protected]”的业务密码为“user1abcde”，如果第一用户输入的业务密码与“user1abcde”相同，则服务器放行第二账户权限进行第一账户的业务操作。
步骤408：在第一用户通过第二账户权限完成业务操作后，服务器根据业务操作的操作结果更新第二账户的第二账户信息。
本申请实施例中，由于第一用户采用第二账户权限完成业务操作，因此业务操作完成后，第一账户的账户信息不会发生变化，服务器可以根据业务操作的操作结果直接更新第二账户的第二账户信息。
步骤409：服务器向第二用户发送通知消息，以通知第二用户第二账户信息的更新内容。
本申请实施例中，服务器向第二用户发送的通知消息可以是向用户注册的终端设备发送短消息，或者向第二账户发送即时通信消息。
步骤410：第一用户向服务器发送针对该业务操作的反向操作请求。
步骤411：当业务操作的反向操作完成后，服务器根据反向操作的操作结果更新第二账户信息。
假设第一用户在步骤408中通过第三方支付服务器，采用第二账户的支 付账户完成购买商品的支付操作后，如果商品存在质量问题，则第一用户对该商品进行退货处理，此时第一用户向第三方支付服务器发送退款请求，由第三方支付服务器将该商品的已扣除款项直接退回给第二账户的支付账户，并在退款结束后，直接更新该支付账户内的账户余额信息。
由上述实施例可见，由于第二用户可以授权与自身具有亲密关系的第一用户使用第二用户的第二账户权限，从而可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；并且由于业务操作及反向业务操作完成均直接对第二账户信息进行更新，因此可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率。
与前述业务处理方法的实施例相对应，本申请还提供了业务处理装置的实施例。
本申请业务处理装置的实施例可以应用在服务器上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在服务器的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，如图5所示，为本申请业务处理装置所在服务器的一种硬件结构图，除了图5所示的处理器、内存、网络接口、以及非易失性存储器之外，实施例中装置所在的服务器通常根据该服务器的实际功能，还可以包括其他硬件，对此不再赘述。
参见图6，为本申请业务处理装置的一个实施例框图，该装置包括：接收单元610、查找单元620、控制单元630和更新单元640。
其中，接收单元610，用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
查找单元620，用于根据所述第一账户查找已保存的账户绑定关系；
控制单元630，用于如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操 作；
更新单元640，用于在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
参见图7，为本申请业务处理装置的另一个实施例框图，该装置包括：发送单元710、接收单元720、第一保存单元730、查找单元740、控制单元750、更新单元760和删除单元770。
其中，发送单元710，用于向第二用户发送推荐账户列表，所述推荐账户列表中包含至少一个与所述第二用户的亲密关系值超过预设关系阈值的用户的账户；
接收单元720，用于接收所述第二用户的授权消息，所述授权消息中包含所述第二用户从所述推荐账户列表中选择的第一账户；
第一保存单元730，用于根据所述授权消息在所述账户绑定关系中保存所述第一账户与所述第二用户的第二账户的绑定关系；
接收单元720，还用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
查找单元740，用于根据所述第一账户查找已保存的账户绑定关系；
控制单元750，用于如果查找到与所述第一账户绑定的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
更新单元760，用于在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息；
接收单元720，还用于接收所述第二用户发送的授权解除消息，所述授权解除消息中包含所述第一账户；
删除单元770，用于根据所述授权解除消息从所述账户绑定关系中删除所述第一账户与第二账户的绑定关系。
在一个可选的实现方式中：
所述接收单元720接收的所述授权消息中还可以包括所述第二账户权限 的使用条件；
所述控制单元750，可以具体用于允许所述第一用户在所述使用条件下，通过所述第二账户的第二账户权限完成所述业务操作。
参见图8，为本申请业务处理装置的另一个实施例框图，该装置包括：第二保存单元810、接收单元820、查找单元830、控制单元840、更新单元850和通知单元860。
其中，第二保存单元810，用于在所述第一用户注册所述第一账户时，保存所述第一账户与第一业务密码的对应关系；
接收单元820，用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
查找单元830，用于根据所述第一账户查找已保存的账户绑定关系；
控制单元840，用于如果查找到与所述第一账户绑定的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
更新单元850，用于根据所述业务操作的操作结果更新所述第二账户的第二账户信息；
通知单元860，用于在更新所述第二账户的第二账户信息后，向所述第二用户发送通知消息，以通知所述第二用户所述第二账户信息的更新内容。
在一个可选的实现方式中：
所述控制单元840可以包括(图8中未示出)：
账户输出子单元，用于在所述第一用户的业务操作界面输出作为可选账户的所述第二账户；
密码接收子单元，用于接收所述第一用户选择所述第二账户进行业务操作后，输入的业务密码；
权限放行子单元，用于当验证所述输入的业务密码与所述对应关系中保存的所述第一业务密码一致时，放行所述第一用户通过所述第二账户权限进行业务操作。
在另一个可选的实现方式中：
所述接收单元820，还可以用于接收所述第一用户发送的针对所述业务操作的反向操作请求；
所述更新单元850，还可以用于当所述业务操作的反向操作完成后，根据所述反向操作的操作结果更新所述第二账户信息。
参见图9，为本申请业务处理装置的另一个实施例框图，该装置包括：接收单元910、查找单元920、判断单元930、执行单元940、控制单元950和更新单元960。
其中，接收单元910，用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
查找单元920，用于根据所述第一账户查找已保存的账户绑定关系；
判断单元930，用于如果查找到与所述第一账户绑定的第二账户，判断所述业务操作对应的业务场景的安全属性；
执行单元940，用于当所述安全属性为安全时，触发所述控制单元执行相应功能；当所述安全属性为不安全时，禁止所述第一用户通过所述第二账户权限进行业务操作。
控制单元950，用于接收到所述执行单元的触发指令后，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
更新单元960，用于根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方， 或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
由上述实施例可见，由于第二用户可以授权与自身具有亲密关系的第一用户使用第二用户的第二账户权限，从而可以使得第一用户可以基于绑定的多个账户的账户权限完成各种业务操作，因此扩展了业务实现方式；并且由于业务操作完成直接对第二账户信息进行更新，因此可以减少业务数据在不同账户之间的传输次数，由此提高业务信息的交互效率。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (19)

  1. 一种业务处理方法，其特征在于，应用于业务处理服务器，所述方法包括：
    当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
    根据所述第一账户查找已保存的账户绑定关系；
    如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
    在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收所述第二用户的授权消息，所述授权消息中包含所述第一账户；
    根据所述授权消息在所述账户绑定关系中保存所述第一账户与所述第二用户的第二账户的绑定关系。
  3. 根据权利要求2所述的方法，其特征在于，所述授权信息中还包括：所述第二账户权限的使用条件；
    所述允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作具体为：允许所述第一用户在所述使用条件下，通过所述第二账户的第二账户权限完成所述业务操作。
  4. 根据权利要求2所述的方法，其特征在于，所述接收所述第二用户的授权消息之前，还包括：
    向所述第二用户发送推荐账户列表，所述推荐账户列表中包含至少一个与所述第二用户的亲密关系值超过预设关系阈值的用户的账户；
    所述授权消息中包含所述第一账户具体为：所述授权消息中包含所述第二用户从所述推荐账户列表中选择的第一账户。
  5. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    接收所述第二用户发送的授权解除消息，所述授权解除消息中包含所述第一账户；
    根据所述授权解除消息从所述账户绑定关系中删除所述第一账户与第二账户的绑定关系。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一用户注册所述第一账户时，保存所述第一账户与第一业务密码的对应关系；
    所述允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作，包括：
    在所述第一用户的业务操作界面输出作为可选账户的所述第二账户；
    接收所述第一用户选择所述第二账户进行业务操作后，输入的业务密码；
    当验证所述输入的业务密码与所述对应关系中保存的所述第一业务密码一致时，放行所述第一用户通过所述第二账户权限进行业务操作。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在更新所述第二账户的第二账户信息后，向所述第二用户发送通知消息，以通知所述第二用户所述第二账户信息的更新内容。
  8. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收所述第一用户发送的针对所述业务操作的反向操作请求；
    当所述业务操作的反向操作完成后，根据所述反向操作的操作结果更新所述第二账户信息。
  9. 根据权利要求1至8任一所述的方法，其特征在于，所述查找到与所述第一账户绑定的第二账户后，所述方法还包括：
    判断所述业务操作对应的业务场景的安全属性；
    当所述安全属性为安全时，执行所述允许所述第一用户通过所述第二账户的第二账户权限进行业务操作；当所述安全属性为不安全时，禁止所述第一用户通过所述第二账户的第二账户权限进行业务操作。
  10. 一种业务处理装置，其特征在于，应用于业务处理服务器，所述装置包括：
    接收单元，用于当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
    查找单元，用于根据所述第一账户查找已保存的账户绑定关系；
    控制单元，用于如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
    更新单元，用于在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
  11. 根据权利要求10所述的装置，其特征在于，
    所述接收单元，还用于接收所述第二用户的授权消息，所述授权消息中包含所述第一账户；
    所述装置还包括：
    第一保存单元，用于根据所述授权消息在所述账户绑定关系中保存所述第一账户与所述第二用户的第二账户的绑定关系。
  12. 根据权利要求11所述的装置，其特征在于，所述接收单元接收的所述授权消息中还包括所述第二账户权限的使用条件；
    所述控制单元，具体用于允许所述第一用户在所述使用条件下，通过所述第二账户的第二账户权限完成所述业务操作。
  13. 根据权利要求11所述的装置，其特征在于，所述装置还包括：
    发送单元，用于向所述第二用户发送推荐账户列表，所述推荐账户列表中包含至少一个与所述第二用户的亲密关系值超过预设关系阈值的用户的账户；
    所述接收单元接收的所述授权消息中包含所述第二用户从所述推荐账户列表中选择的第一账户。
  14. 根据权利要求11所述的装置，其特征在于，
    所述接收单元，还用于接收所述第二用户发送的授权解除消息，所述授权解除消息中包含所述第一账户；
    所述装置还包括：
    删除单元，用于根据所述授权解除消息从所述账户绑定关系中删除所述第一账户与第二账户的绑定关系。
  15. 根据权利要求10所述的装置，其特征在于，所述装置还包括
    第二保存单元，用于在所述第一用户注册所述第一账户时，保存所述第一账户与第一业务密码的对应关系；
    所述控制单元包括：
    账户输出子单元，用于在所述第一用户的业务操作界面输出作为可选账户的所述第二账户；
    密码接收子单元，用于接收所述第一用户选择所述第二账户进行业务操作后，输入的业务密码；
    权限放行子单元，用于当验证所述输入的业务密码与所述对应关系中保存的所述第一业务密码一致时，放行所述第一用户通过所述第二账户权限进行业务操作。
  16. 根据权利要求10所述的装置，其特征在于，所述装置包括：
    通知单元，用于在更新所述第二账户的第二账户信息后，向所述第二用户发送通知消息，以通知所述第二用户所述第二账户信息的更新内容。
  17. 根据权利要求10所述的装置，其特征在于，
    所述接收单元，还用于接收所述第一用户发送的针对所述业务操作的反向操作请求；
    所述更新单元，还用于当所述业务操作的反向操作完成后，根据所述反向操作的操作结果更新所述第二账户信息。
  18. 根据权利要求10至17任一所述的装置，其特征在于，所述装置还 包括：
    判断单元，用于判断所述业务操作对应的业务场景的安全属性；
    执行单元，用于当所述安全属性为安全时，触发所述控制单元执行所述允许所述第一用户通过所述第二账户的第二账户权限进行业务操作；当所述安全属性为不安全时，禁止所述第一用户通过所述第二账户的第二账户权限进行业务操作。
  19. 一种服务器，其特征在于，包括：
    处理器；用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    当第一用户在客户端设备上基于第一账户登录后，接收所述第一用户请求进行业务操作的操作请求；
    根据所述第一账户查找已保存的账户绑定关系；
    如果查找到与所述第一账户绑定的第二用户的第二账户，允许所述第一用户通过所述第二账户的第二账户权限完成所述业务操作；
    在所述第一用户通过所述第二账户权限完成所述业务操作后，根据所述业务操作的操作结果更新所述第二账户的第二账户信息。
PCT/CN2015/086613 2014-08-21 2015-08-11 业务处理方法、装置及服务器 WO2016026399A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
US15/505,400 US10389726B2 (en) 2014-08-21 2015-08-11 Service processing method, apparatus and server
EP15834266.7A EP3185513A4 (en) 2014-08-21 2015-08-11 Service processing method, apparatus and server
SG11201700628SA SG11201700628SA (en) 2014-08-21 2015-08-11 Service processing method, apparatus and server
KR1020177004748A KR101984153B1 (ko) 2014-08-21 2015-08-11 서비스 처리 방법, 장치 및 서버
JP2017510299A JP6463463B2 (ja) 2014-08-21 2015-08-11 サービス処理方法、装置、及びサーバ
KR1020197014981A KR102055533B1 (ko) 2014-08-21 2015-08-11 서비스 처리 방법, 장치 및 서버
US16/429,141 US11005848B2 (en) 2014-08-21 2019-06-03 Service processing method, apparatus and server
US17/224,199 US11218489B2 (en) 2014-08-21 2021-04-07 Service processing method, apparatus and server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410416166.1A CN105450691B (zh) 2014-08-21 2014-08-21 业务处理方法、装置及服务器
CN201410416166.1 2014-08-21

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/505,400 A-371-Of-International US10389726B2 (en) 2014-08-21 2015-08-11 Service processing method, apparatus and server
US16/429,141 Continuation US11005848B2 (en) 2014-08-21 2019-06-03 Service processing method, apparatus and server

Publications (1)

Publication Number Publication Date
WO2016026399A1 true WO2016026399A1 (zh) 2016-02-25

Family

ID=55350191

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086613 WO2016026399A1 (zh) 2014-08-21 2015-08-11 业务处理方法、装置及服务器

Country Status (8)

Country Link
US (3) US10389726B2 (zh)
EP (1) EP3185513A4 (zh)
JP (3) JP6463463B2 (zh)
KR (2) KR101984153B1 (zh)
CN (2) CN110351339B (zh)
HK (1) HK1222058A1 (zh)
SG (3) SG10202001220UA (zh)
WO (1) WO2016026399A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106600254A (zh) * 2016-12-16 2017-04-26 天脉聚源（北京）科技有限公司 用户的多帐户管理方法及装置
JP2019511755A (ja) * 2017-03-14 2019-04-25 平安科技（深▲せん▼）有限公司Ｐｉｎｇ Ａｎ Ｔｅｃｈｎｏｌｏｇｙ （Ｓｈｅｎｚｈｅｎ） Ｃｏ．，Ｌｔｄ． 金融取引管理システム、金融取引管理方法およびサーバ
CN113724897A (zh) * 2020-05-26 2021-11-30 微创在线医疗科技(上海)有限公司 信息处理方法、***及可读存储介质

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110351339B (zh) 2014-08-21 2022-05-27 创新先进技术有限公司 业务处理方法、装置及服务器
CN106875243A (zh) * 2016-06-29 2017-06-20 阿里巴巴集团控股有限公司 一种基于权限分离控制的网络交易方法及装置
CN106327286A (zh) * 2016-08-05 2017-01-11 深圳市淘淘谷信息技术有限公司 一种数据分配方法及装置
CN106372984A (zh) * 2016-08-30 2017-02-01 乐视控股（北京）有限公司 多账户的账户信息合并方法及装置
CN106529324B (zh) * 2016-09-06 2019-08-06 北京三快在线科技有限公司 一种用户身份切换方法及装置
WO2018098941A1 (zh) * 2016-11-30 2018-06-07 华为技术有限公司 一种通信标识绑定的处理方法及终端
CN108156206B (zh) * 2016-12-06 2021-12-28 腾讯科技（深圳）有限公司 一种数据转移方法、服务器、客户端以及***
CN108154375B (zh) * 2016-12-06 2019-10-15 阿里巴巴集团控股有限公司 一种业务数据处理方法及装置
CN107256484B (zh) * 2017-03-17 2021-01-15 ***股份有限公司 移动支付转授权方法、及利用该方法实现的支付***
CN107679955A (zh) * 2017-10-11 2018-02-09 掌合天下（北京）信息技术有限公司 订单处理方法及***
US11354371B2 (en) * 2017-11-07 2022-06-07 Lale Ann Gokyi{hacek over (g)}it Progressive chain network graph, map and search engine
CN110166417B (zh) * 2018-08-01 2021-10-01 腾讯科技（深圳）有限公司 任务执行方法、装置、计算机设备和存储介质
US11146657B2 (en) * 2018-08-31 2021-10-12 Latticework, Inc. Binding a public cloud user account and a personal cloud user account for a hybrid cloud environment
CN109361758A (zh) * 2018-11-09 2019-02-19 浙江数链科技有限公司 业务操作的执行方法及装置
CN109951486B (zh) * 2019-03-21 2022-03-22 网易（杭州）网络有限公司 信息处理方法、装置、存储介质和电子装置
US11699139B2 (en) * 2019-04-05 2023-07-11 Mell Innovations, LLC Interactive mobile sessions based on point-of-sale and network transactions
CN112152967A (zh) * 2019-06-27 2020-12-29 北京声智科技有限公司 一种数据存储管理的方法以及相关装置
CN110895603B (zh) * 2019-11-05 2021-11-26 泰康保险集团股份有限公司 多***账号信息整合方法和装置
CN111131420B (zh) * 2019-12-12 2022-05-31 腾讯科技（深圳）有限公司 电子资源转移方法、设备及存储介质
CN111552954A (zh) * 2020-04-27 2020-08-18 中国银行股份有限公司 账户管理方法及装置
CN113011891B (zh) * 2021-03-22 2023-03-21 支付宝（中国）网络技术有限公司 应用于关联支付的核身处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102254259A (zh) * 2010-05-21 2011-11-23 英特尔公司 用于实施信任远程支付交易的方法和设备
CN102289754A (zh) * 2011-08-08 2011-12-21 中兴通讯股份有限公司 移动终端支付方法、***及移动终端
CN102831518A (zh) * 2011-06-16 2012-12-19 同方股份有限公司 一种支持第三方授权的移动支付方法及***
US20130159173A1 (en) * 2011-12-19 2013-06-20 Sridhar Sivaraman Shared Mobile Payments

Family Cites Families (77)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7415442B1 (en) * 2000-09-26 2008-08-19 Integrated Technological Systems, Inc. Integrated technology money transfer system
JP2002215488A (ja) * 2001-01-15 2002-08-02 Toshiba Corp インターネット接続制御方法およびシステム
US6714791B2 (en) 2001-02-23 2004-03-30 Danger, Inc. System, apparatus and method for location-based instant messaging
US20020198882A1 (en) 2001-03-29 2002-12-26 Linden Gregory D. Content personalization based on actions performed during a current browsing session
KR100866570B1 (ko) * 2002-01-16 2008-11-04 주식회사 엘지이아이 디지털 텔레비전의 개인 프로파일을 이용한 사용자 관리 및 결제방법
US20040015702A1 (en) * 2002-03-01 2004-01-22 Dwayne Mercredi User login delegation
US10535049B2 (en) 2003-03-21 2020-01-14 Paypal, Inc. Payment transactions via substantially instant communication system
US7676432B2 (en) * 2003-07-08 2010-03-09 Paybyclick Corporation Methods and apparatus for transacting electronic commerce using account hierarchy and locking of accounts
US7204412B2 (en) 2003-10-14 2007-04-17 Compucredit Intellectual Property Holdings Corp. Iii Family stored value card program
JP2006239500A (ja) 2005-03-01 2006-09-14 Chiyuuden Plant Kk 爆風放散口の屋外カバー固定構造体
JP4514214B2 (ja) 2005-04-04 2010-07-28 東亜道路工業株式会社 バラスト固化層の形成方法
JP2006293500A (ja) * 2005-04-06 2006-10-26 Ntt Docomo Inc 決済サービスサーバおよび決済承認方法
US7401731B1 (en) 2005-05-27 2008-07-22 Jpmorgan Chase Bank, Na Method and system for implementing a card product with multiple customized relationships
ATE510396T1 (de) * 2006-02-01 2011-06-15 Research In Motion Ltd System und methode für die validierung eines benutzerkontos mit einer drahtlosen vorrichtung
US8662384B2 (en) 2006-02-28 2014-03-04 Google Inc. Text message payment
JP2007249912A (ja) * 2006-03-20 2007-09-27 Fujitsu Ltd 共用資源管理システム、共用資源管理方法、およびコンピュータプログラム
US8121945B2 (en) 2006-07-06 2012-02-21 Firethorn Mobile, Inc. Methods and systems for payment method selection by a payee in a mobile environment
JP2008129860A (ja) * 2006-11-21 2008-06-05 Matsushita Electric Ind Co Ltd 情報処理機器、サービス提供サーバ及び遠隔操作装置
CN107423964A (zh) * 2007-01-17 2017-12-01 阿里巴巴集团控股有限公司 一种网上支付方法、装置及***
US20080228638A1 (en) * 2007-03-14 2008-09-18 Ebay Inc. Method and system of controlling linked accounts
US20110320347A1 (en) 2007-03-30 2011-12-29 Obopay, Inc. Mobile Networked Payment System
CN101093567A (zh) * 2007-08-01 2007-12-26 中国工商银行股份有限公司 一种实现家庭账户的***及方法
WO2009027082A1 (en) * 2007-08-27 2009-03-05 Nec Europe Ltd Method and system for performing delegation of resources
JP5177505B2 (ja) 2008-02-26 2013-04-03 日本電信電話株式会社 シングルサインオンによるグループ内サービス認可方法と、その方法を用いたグループ内サービス提供システムと、それを構成する各サーバ
JP2009163706A (ja) * 2008-09-01 2009-07-23 Mekiki:Kk 属性情報認証装置、属性情報認証方法、及びコンピュータプログラム
JP2010066929A (ja) * 2008-09-09 2010-03-25 Olympus Corp サーバシステム、電子機器、通信端末及び認証方法
WO2010062699A2 (en) * 2008-10-30 2010-06-03 Socialwise, Inc. Related party payment system
US8332314B2 (en) * 2008-11-05 2012-12-11 Kent Griffin Text authorization for mobile payments
US10839384B2 (en) 2008-12-02 2020-11-17 Paypal, Inc. Mobile barcode generation and payment
US9864991B2 (en) 2009-09-22 2018-01-09 Murphy Oil Usa, Inc. Method and apparatus for secure transaction management
US20110093520A1 (en) 2009-10-20 2011-04-21 Cisco Technology, Inc.. Automatically identifying and summarizing content published by key influencers
US8424069B2 (en) * 2009-11-20 2013-04-16 Disney Enterprises, Inc. Method and system for authenticating subaccount users
US20110131077A1 (en) 2009-12-01 2011-06-02 Microsoft Corporation Context-Aware Recommendation Module Using Multiple Models
CN102164202A (zh) * 2010-02-22 2011-08-24 上海博路信息技术有限公司 一种手机扫描条码的家庭账单支付方法
JP5513270B2 (ja) * 2010-06-14 2014-06-04 日本電信電話株式会社 メッセージ共有装置、方法、およびプログラム
JP2012003359A (ja) 2010-06-15 2012-01-05 Sony Corp アイテム推薦システム、アイテム推薦方法、及びプログラム
US8417604B2 (en) * 2010-07-22 2013-04-09 Bank Of America Corporation Personal data aggregation, integration and access
US20120197754A1 (en) 2011-01-28 2012-08-02 Etsy, Inc. Systems and methods for shopping in an electronic commerce environment
US20120197794A1 (en) 2011-01-31 2012-08-02 Bank Of America Corporation Shared mobile wallet
US9047636B2 (en) 2011-02-25 2015-06-02 Bank Of America Corporation Dynamic determination of appropriate payment account
US9454753B2 (en) * 2011-03-28 2016-09-27 Paypal, Inc. Friendly funding source
JP5679890B2 (ja) 2011-04-20 2015-03-04 株式会社沖データ 画像形成装置及び認証印刷データの管理権限委譲方法
US20120330837A1 (en) * 2011-06-01 2012-12-27 Persaud Omesh A Account linking system and method
US8326769B1 (en) 2011-07-01 2012-12-04 Google Inc. Monetary transfer in a social network
CN102882903B (zh) * 2011-07-12 2017-07-28 腾讯科技（深圳）有限公司 一种多网站应用信息获取方法及***
JP2013033420A (ja) * 2011-08-03 2013-02-14 Nec Engineering Ltd 情報処理装置及びその代理アクセス権付与方法
JP2013069248A (ja) 2011-09-26 2013-04-18 Nec Corp 情報開示制御装置、情報開示制御方法及びプログラム
US8904506B1 (en) * 2011-11-23 2014-12-02 Amazon Technologies, Inc. Dynamic account throttling
US9003486B2 (en) 2012-01-17 2015-04-07 Nokia Corporation Methods and apparatus for reliable and privacy protecting identification of parties' mutual friends and common interests
EP2805568A4 (en) * 2012-01-18 2015-12-16 Kinectus LLC SYSTEMS AND METHODS FOR ESTABLISHING COMMUNICATIONS BETWEEN USERS OF MOBILE DEVICES
WO2013132995A1 (ja) 2012-03-07 2013-09-12 ソニー株式会社 決済処理システム、決済端末、通信装置、決済サーバ、及び決済処理方法
CN102710759B (zh) * 2012-05-22 2015-04-15 中国联合网络通信集团有限公司 Web服务器、业务登录方法及***
CN102833238B (zh) 2012-08-14 2016-07-27 上海聚力传媒技术有限公司 辅助网络设备进行用户验证的方法、装置、设备和***
US9582156B2 (en) 2012-11-02 2017-02-28 Amazon Technologies, Inc. Electronic publishing mechanisms
JP2014099127A (ja) * 2012-11-16 2014-05-29 Hitachi Ltd 失効機能付き認証システム
JP5989522B2 (ja) 2012-11-29 2016-09-07 株式会社日立ソリューションズ データ管理装置
US20140200909A1 (en) * 2013-01-17 2014-07-17 Citibank, N.A. Methods and systems for electronically managing healthcare expenses and payments
CN103248699B (zh) 2013-05-16 2014-07-16 广西中烟工业有限责任公司 一种单点登录信息***的多账号处理方法
US9978052B2 (en) * 2013-05-21 2018-05-22 Paypal, Inc. Multi-payer payment system
US20140379576A1 (en) * 2013-06-25 2014-12-25 Joseph A. Marx Transaction approval for shared payment account
CN104519108B (zh) * 2013-09-30 2017-11-03 腾讯科技（深圳）有限公司 推送账户信息、导入关系链的方法、装置及***
CN104519107B (zh) * 2013-09-30 2017-10-10 腾讯科技（深圳）有限公司 一种拓展联系人的方法及装置
EP3060975A1 (en) 2013-10-25 2016-08-31 Next Print Technologies APS Method of handling a guest print job for processing by an authenticated printing system and system for performing the method
CN103530766A (zh) * 2013-10-25 2014-01-22 乐视网信息技术（北京）股份有限公司 一种智能电视支付方法、装置及***
CN103616860B (zh) * 2013-11-08 2017-02-15 海信集团有限公司 一种远程控制家电设备的方法和装置
US20150142658A1 (en) * 2013-11-19 2015-05-21 Tencent Technology (Shenzhen) Company Limited Payment binding management method, payment server, client, and system
CN104683961B (zh) * 2013-11-29 2019-01-15 腾讯科技（深圳）有限公司 名片交互方法、装置和终端
US10127528B2 (en) * 2013-12-20 2018-11-13 Movocash, Inc. Financial services ecosystem
US20150178725A1 (en) * 2013-12-23 2015-06-25 Nicholas Poetsch Transaction authorization control and account linking involving multiple and singular accounts or users
CN104732376B (zh) * 2013-12-24 2020-01-24 腾讯科技（深圳）有限公司 支付密码的重置方法、终端及***
US20150254663A1 (en) * 2014-03-04 2015-09-10 Bank Of America Corporation Token usage scaling based on determined level of exposure
US9491155B1 (en) * 2014-08-13 2016-11-08 Amazon Technologies, Inc. Account generation based on external credentials
US10445739B1 (en) * 2014-08-14 2019-10-15 Wells Fargo Bank, N.A. Use limitations for secondary users of financial accounts
CN110351339B (zh) * 2014-08-21 2022-05-27 创新先进技术有限公司 业务处理方法、装置及服务器
CN105100190B (zh) * 2015-05-21 2019-05-10 小米科技有限责任公司 对账户与设备的控制关系进行管理的方法、装置和***
US10475036B2 (en) * 2016-01-08 2019-11-12 Ca, Inc. Restricting account use by controlled replenishment
SG10201800056QA (en) * 2018-01-03 2019-08-27 Mastercard International Inc Computer system and computer-implemented method for using financial assets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102254259A (zh) * 2010-05-21 2011-11-23 英特尔公司 用于实施信任远程支付交易的方法和设备
CN102831518A (zh) * 2011-06-16 2012-12-19 同方股份有限公司 一种支持第三方授权的移动支付方法及***
CN102289754A (zh) * 2011-08-08 2011-12-21 中兴通讯股份有限公司 移动终端支付方法、***及移动终端
US20130159173A1 (en) * 2011-12-19 2013-06-20 Sridhar Sivaraman Shared Mobile Payments

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3185513A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106600254A (zh) * 2016-12-16 2017-04-26 天脉聚源（北京）科技有限公司 用户的多帐户管理方法及装置
JP2019511755A (ja) * 2017-03-14 2019-04-25 平安科技（深▲せん▼）有限公司Ｐｉｎｇ Ａｎ Ｔｅｃｈｎｏｌｏｇｙ （Ｓｈｅｎｚｈｅｎ） Ｃｏ．，Ｌｔｄ． 金融取引管理システム、金融取引管理方法およびサーバ
CN113724897A (zh) * 2020-05-26 2021-11-30 微创在线医疗科技(上海)有限公司 信息处理方法、***及可读存储介质

Also Published As

Publication number Publication date
HK1222058A1 (zh) 2017-06-16
EP3185513A1 (en) 2017-06-28
JP2019075161A (ja) 2019-05-16
JP6898297B2 (ja) 2021-07-07
CN105450691B (zh) 2019-08-16
JP7093393B2 (ja) 2022-06-29
KR102055533B1 (ko) 2019-12-12
SG10202108461QA (en) 2021-09-29
US11005848B2 (en) 2021-05-11
KR20170033403A (ko) 2017-03-24
CN110351339A (zh) 2019-10-18
JP2021099795A (ja) 2021-07-01
CN105450691A (zh) 2016-03-30
CN110351339B (zh) 2022-05-27
EP3185513A4 (en) 2018-01-03
US20190289015A1 (en) 2019-09-19
US20170272447A1 (en) 2017-09-21
JP2017530448A (ja) 2017-10-12
KR20190060011A (ko) 2019-05-31
US10389726B2 (en) 2019-08-20
JP6463463B2 (ja) 2019-02-06
US11218489B2 (en) 2022-01-04
SG11201700628SA (en) 2017-03-30
KR101984153B1 (ko) 2019-05-30
US20210226958A1 (en) 2021-07-22
SG10202001220UA (en) 2020-03-30

Similar Documents

Publication Publication Date Title
WO2016026399A1 (zh) 业务处理方法、装置及服务器
US10970377B2 (en) Systems and methods for authenticating a user based on a computing device
JP6135963B2 (ja) 複数の端末が仮想ｓｉｍカードを共有するための方法、端末、サーバおよびシステム
US9754091B2 (en) Restricted accounts on a mobile platform
TWI706262B (zh) 帳戶登錄方法、設備和伺服器
CN109905398B (zh) 手机号换绑验证方法、装置、设备及存储介质
CN108540433A (zh) 用户身份校验方法及装置
WO2017197888A1 (zh) 一种数据分享方法、智能终端及***
US10846658B2 (en) Establishing a communication event
US9886685B2 (en) Distributed digital rights-managed file transfer and access control
KR102116659B1 (ko) 보안성이 강화된 데이터 제공 방법
US20130198021A1 (en) Passcode management for authorization of in-application purchases on a mobile device
US9826402B2 (en) Mobile device management
US10360553B2 (en) Mobile device management
US10657100B2 (en) File management system
CN114357421A (zh) 用于对在线事件进行安全访问的方法和装置

Legal Events

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

Ref document number: 15834266

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015834266

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017510299

Country of ref document: JP

Kind code of ref document: A

Ref document number: 20177004748

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15505400

Country of ref document: US