CN108156206B - Data transfer method, server, client and system - Google Patents

Data transfer method, server, client and system Download PDF

Info

Publication number
CN108156206B
CN108156206B CN201611110880.3A CN201611110880A CN108156206B CN 108156206 B CN108156206 B CN 108156206B CN 201611110880 A CN201611110880 A CN 201611110880A CN 108156206 B CN108156206 B CN 108156206B
Authority
CN
China
Prior art keywords
client
service account
data transfer
account
server
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201611110880.3A
Other languages
Chinese (zh)
Other versions
CN108156206A (en
Inventor
彭英
王冲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201611110880.3A priority Critical patent/CN108156206B/en
Publication of CN108156206A publication Critical patent/CN108156206A/en
Application granted granted Critical
Publication of CN108156206B publication Critical patent/CN108156206B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/563Data redirection of data network streams

Abstract

The embodiment of the invention discloses a data transfer method, a server, a client and a system, wherein the method comprises the following steps: the server determines at least one service account preset by a first client; determining a target business account in at least one business account, wherein the target business account is any one of the at least one business account; when the residual data volume of the target service account is smaller than a preset threshold value, deducting a data transfer volume from the binding account of the first client, wherein the data transfer volume is configured for the target service account by the first client; and performing service processing on the target service account based on the data transfer amount. By adopting the embodiment of the invention, at least one service account can be automatically charged through the first client, so that the convenience of operation is improved.

Description

Data transfer method, server, client and system
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a data transfer method, a server, a client, and a system.
Background
With the rapid development of internet technology, data transfer via the internet has become a lifestyle for many people. In the conventional data transfer method, a user needs to query the account balance of the user through an operator or a third-party platform and then log in the third-party platform to transfer data to the account of the user, but the user can only query the account balance of the user, cannot query the account balances of other users, cannot automatically transfer data to the accounts of all users, and reduces the convenience of user operation.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a data transfer method, a server, a client and a system, which can automatically recharge at least one service account through a first client, thereby improving the convenience of operation.
A first aspect of the present invention provides a data transfer method, including:
the server determines at least one service account preset by a first client;
the server determines a target business account in the at least one business account, wherein the target business account is any one of the at least one business account;
when the remaining data volume of the target service account is smaller than a preset threshold, the server deducts a data transfer volume from the binding account of the first client, wherein the data transfer volume is configured for the target service account by the first client;
and the server performs service processing on the target service account based on the data transfer amount.
A second aspect of the present invention provides a data transfer method, including:
a first client acquires a service account number of a second client selected by a user of the first client;
the first client sends a data transfer authorization request to a server, wherein the data transfer authorization request carries a business account number of the second client, so that the server sends authorization request information to the second client according to the business account number, when receiving data transfer authorization information generated by the second client responding to the authorization request information, the server generates authorization information, and the authorization information carries the business account number of the second client;
and when receiving the authorization information sent by the server, the first client configures the service account of the second client.
A third aspect of the present invention provides a server, comprising:
the service account determining module is used for determining at least one service account preset by the first client;
the service account determining module is further configured to determine a target service account in the at least one service account, where the target service account is any one of the at least one service account;
a transfer amount deduction module, configured to deduct a data transfer amount from a binding account of the first client when a remaining data amount of the target service account is smaller than a preset threshold, where the data transfer amount is configured for the target service account by the first client;
and the service processing module is used for carrying out service processing on the target service account based on the data transfer amount.
A fourth aspect of the present invention provides a client, including:
the service account acquisition module is used for acquiring a service account of a second client selected by a user of the client;
a request sending module, configured to send a data transfer authorization request to a server, where the data transfer authorization request carries a service account of the second client, so that the server sends authorization request information to the second client according to the service account, and when receiving data transfer authorization information generated by the second client in response to the authorization request information, generates authorization information, where the authorization information carries the service account of the second client;
and the configuration module is used for configuring the service account of the second client when the authorization information sent by the server is received.
A fifth aspect of the present invention provides a data transfer system, which includes the server according to the third aspect and the client according to the fourth aspect.
By implementing the embodiment of the invention, the server determines the target business account in the at least one business account by determining the at least one business account preset by the first client, the target business account is any one of the at least one business account, when the residual data volume of the target business account is smaller than the preset threshold value, the data transfer volume is deducted from the binding account of the first client, the data transfer volume is configured for the target business account by the first client, the target business account is subjected to business processing based on the data transfer volume, the at least one business account can be automatically recharged by the first client, and the convenience of operation is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts;
fig. 1 is a schematic structural diagram of a data transfer system provided in an embodiment of the present invention;
fig. 2 is a schematic flow chart of a data transfer method provided in an embodiment of the present invention;
FIG. 3 is a flow chart illustrating a data transfer method according to another embodiment of the present invention;
FIG. 4 is a flow chart illustrating a data transfer method according to another embodiment of the present invention;
fig. 5 is a schematic structural diagram of a server provided in an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a server provided in another embodiment of the present invention;
fig. 7 is a schematic structural diagram of a client provided in an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a client provided in another embodiment of the present invention;
FIG. 9 is a schematic diagram of a data transfer system according to another embodiment of the present invention;
fig. 10 is a schematic view of an interface provided in an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a data transfer method, wherein a server determines at least one service account preset by a first client, determines a target service account in the at least one service account, the target service account is any one of the at least one service account, and deducts a data transfer amount from a binding account of the first client when the residual data amount of the target service account is smaller than a preset threshold, wherein the data transfer amount is configured for the target service account by the first client, and performs service processing on the target service account based on the data transfer amount. Compared with the traditional method that when the client inquires that the account balance of the client is insufficient through the telephone customer service, the client is manually charged with the Internet, or the client receives prompt information in the process of establishing communication connection with other clients to prompt that the account balance of the other clients is insufficient, so that the client manually charges the other clients with the Internet.
Based on the foregoing principle, an embodiment of the present invention provides a data transfer system, which may be an internet application system such as an instant messaging application system, an SNS (Social Networking Services) application system, or a third party payment system. Referring to fig. 1, the architecture of the data transfer system includes at least: a server 101, at least one first client 102 accessing said server 101, and at least one second client 103 accessing said server 101.
The first client 102 or the second client 103 may operate in a terminal such as a notebook computer, a mobile phone, a PAD (tablet computer), a vehicle-mounted terminal, or a smart wearable device, and the first client 102 or the second client 103 may include an instant messaging client (e.g., a WeChat client or a QQ client), a live broadcast client (e.g., a pattern live broadcast client), or a video playing client (e.g., a Tencent video client). At least one type of internet application may be run in the terminal, including but not limited to: instant messaging applications, SNS applications, and the like. The user can use internet applications through the terminal, such as: the user can charge the telephone fee, charge the Q coin, pay the credit card or the QQ member renews the fee and the like on the third-party payment platform through the terminal; alternatively, the user may interact with other users in an internet application through the terminal, for example, the user may use an instant messaging application such as WeChat or QQ through the terminal, display a conversation interface with other users, the user may input social messages in the conversation interface, and the like. The server 101 may be an independent service device in the internet, or a cluster service device formed by multiple independent service devices in the internet; the server 101 may be configured to handle various requirements of the internet application in a process of implementing functions such as data transfer amount deduction, service processing, and information interaction, and the server 101 may be configured to manage related data of a user in the internet application, the user, and an interaction message between the user, for example, store a binding account of the first client 102, a service account of the second client 103, and a data transfer amount configured to the service account of the second client 102.
The service account may include a phone number, a credit card number, a game account number, a transportation card number, or a client identifier, and the client identifier may include a QQ account number or a wechat account number, which is not limited in the embodiment of the present invention.
The binding account of the first client 102 may be a smart card account, or an electronic account provided by a third-party payment platform, such as a wechat wallet, an insurance payment, a financial payment, a shanghai fast money, an online banking online payment, a first letter and easy payment, and the like, which is not limited in the embodiment of the present invention.
The remaining data amount of the service account may be a balance of the service account, such as a telephone charge balance, a credit card payment balance, a transportation card balance, a game card balance or a Q-currency balance, and the embodiment of the present invention is not limited.
The data transfer amount may also be referred to as a payment amount, and the data transfer amounts configured for different service account numbers may be the same or different, and the embodiment of the present invention is not limited.
Based on the schematic structural diagram of the data transfer system shown in fig. 1, the embodiment of the present invention discloses a schematic flow diagram of a data transfer method shown in fig. 2. As shown in fig. 2, the data transfer method may include the steps of:
s201, the server determines at least one business account preset by the first client.
The server may determine at least one service account preset by the first client, where the at least one service account may include a service account of the first client, and may also include a service account of a second client, where the second client may be any client other than the first client, and is not specifically limited by the embodiment of the present invention. In a specific implementation, the server may obtain at least one preset service account number of the first client from a local database of the server according to the client identifier of the first client, or the server may send a service account number obtaining request to the first client, and the first client may send the preset at least one service account number to the server in response to the service account number obtaining request. The client identifier of the first client may be an instant messaging account, such as a wechat account or a QQ account.
Optionally, before the server determines at least one service account preset by the first client, the server may receive a data transfer authorization request sent by the first client, where the data transfer authorization request carries a service account of the second client, the server may send authorization request information to the second client according to the service account of the second client, and when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server may store the client identifier of the first client and the service account of the second client. It should be noted that the server may send the authorization request message to the second client by short message or instant messaging (e.g., WeChat, etc.).
Taking the interface diagram shown in fig. 10 as an example, when the first client needs to perform the telephone fee recharging, the first client may enter the mobile phone recharging interface through a third party payment platform (for example, a wechat wallet, etc.), the user of the first client may send an automatic fee recharging request to the first client by clicking an "automatic fee recharging" button, and the first client may respond to the automatic fee recharging request to display the automatic fee recharging interface. The automatic charging interface may be as shown in fig. 10, the first client may display a button having a function of configuring the service account number on the automatic charging interface, for example, an "add friend" button in fig. 10, and optionally, the first client may also display a service account number previously configured by the first client on the automatic charging interface. After a user of the first client sends a service account configuration request to the first client by clicking a "add friend" button, the first client may respond to the service account configuration request to display an account list, where an interface schematic diagram of the account list may be as shown in fig. 10, contact information in the account list may be the same as contact information in an address book, and an arrangement manner of the contact information in the account list may also be the same as an arrangement manner of the contact information in the address book, so that the user may quickly find a service account to be configured. Optionally, when the same contact corresponds to multiple service accounts, after the user clicks a contact corresponding to a service account to be configured, the first client may display multiple service accounts corresponding to the contact, so as to prompt the user to select a service account to be configured from the multiple service accounts, taking the interface schematic diagram shown in fig. 10 as an example, after the user of the first client clicks "mr" of the contact, the first client determines that the contact has two telephone numbers, and then displays the two telephone numbers corresponding to the contact, and when the telephone number to be configured is 156XXXX2785, the user of the first client may click the telephone number in the two telephone numbers corresponding to the contact. The first client may respond to an operation of a user of the first client, and send a data transfer authorization request to the server, where the data transfer authorization request carries a service account number of the second client, and the service account number of the second client is a phone number 156XXXX2785, the server may send authorization request information to the second client according to the service account number of the second client, and when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server may store a client identifier of the first client and the service account number of the second client.
For example, an interface schematic diagram of the data transfer authorization interface sent by the first client may be as shown in fig. 10, the data transfer authorization request may include a client identifier (e.g., "mr."), a selected service account number (e.g., renewal phone 156XXXX2785) of the second client, a data transfer amount (e.g., 50.00 m) configured by the first client for the service account number of the second client, and optionally, the data transfer authorization request may further include a remaining data amount (e.g., 10.00 m) of the service account number of the second client. The user of the first client can click the 'invite the other party to open' button, and the first client responds to the operation and sends a data transfer authorization request to the server.
For example, the data transfer authorization interface received by the second client may be as shown in fig. 10, the authorization request information may include a client identifier (e.g., "mr. m") of the second client, a selected service account number (e.g., renewal phone 156XXXX2785) of the second client, a data transfer amount (e.g., 50.00 m) configured by the first client for the service account number of the second client, and optionally, the authorization request information may further include a remaining data amount (e.g., 10.00 m) of the service account number of the second client. The user of the second client may click the "confirm open" button, which indicates that the user of the second client allows the server to query the remaining data volume of the service account of the second client through the operator, and send the remaining data volume to the first client, and the second client may send data transfer authorization information to the server in response to the operation. Optionally, the user of the second client may click a "reject" button, and the second client may send, in response to the operation, a reject authorization message to the first client through the server, so that the first client cannot automatically renew the service account of the second client.
For example, when a first client needs to recharge a game card, the first client may enter a game card recharge interface through a third-party payment platform, a user of the first client may send an automatic recharge request to the first client, the first client may respond to the automatic recharge request to display the automatic recharge interface, the first client may display a button with a function of configuring a service account on the automatic recharge interface, the user of the first client sends a service account configuration request to the first client by clicking the button with the function of configuring the service account, and the service account configuration request may carry a game account. The first client side can respond to the operation of a user of the first client side, and sends a data transfer authorization request to the server, the data transfer authorization request carries the game account number, the server can send authorization request information to a second client side corresponding to the game account number, and when the data transfer authorization information generated by the second client side responding to the authorization request information is received, the server can store the client side identification of the first client side and the game account number. Further, the server may determine that at least one service account preset by the first client includes the game account.
Optionally, after the server sends the authorization request information to the second client according to the service account of the second client, when receiving the data transfer authorization information generated by the second client in response to the authorization request information, the server may send the authorization information to the first client, where the authorization information carries the service account of the second client, so that the first client configures the service account of the second client according to the authorization information.
Optionally, after the first client configures the service account of the second client, a deletion request for the service account of the second client may be sent to the server, and the server deletes the client identifier of the first client and the service account of the second client in the local database of the server in response to the deletion request.
S202, the server determines a target business account number in the at least one business account number, wherein the target business account number is any business account number in the at least one business account number.
After the server acquires at least one service account preset by the first client, a target service account can be determined in the at least one service account. The target service account may be any one of at least one service account, for example, the server may obtain a first service account preset by the first client, determine the first service account as the target service account, when the remaining data amount of the target service account is smaller than a preset threshold, the server deducts a data transfer amount from a binding account of the first client, and performs service processing on the target service account based on the data transfer amount. Further, the server may obtain a second service account preset by the first client, determine the second service account as a target service account, when the remaining data amount of the target service account is smaller than a preset threshold, deduct a data transfer amount from the binding account of the first client by the server, perform service processing on the target service account based on the data transfer amount until the server obtains a last service account preset by the first client, determine the last service account as the target service account, when the remaining data amount of the target service account is smaller than the preset threshold, deduct the data transfer amount from the binding account of the first client by the server, and perform service processing on the target service account based on the data transfer amount.
For example, after the server determines that at least one service account preset by the first client includes the game account, the game account may be determined as a target service account.
And S203, when the residual data volume of the target service account is smaller than a preset threshold, the server deducts a data transfer volume from the binding account of the first client, wherein the data transfer volume is configured by the first client for the target service account.
Specifically, after the server determines the target service account, the server may obtain the remaining data volume of the target service account through the operator, determine whether the remaining data volume is smaller than a preset threshold, and deduct the data transfer volume from the binding account of the first client when the remaining data volume is smaller than the preset threshold. And the data transfer amount is configured by the first client to the target service account. The preset threshold may be pre-configured by the server, or configured by the user of the first client to the target service account. Optionally, when the data amount in the binding account is smaller than the data transfer amount, the server may send a prompt message to the first client to prompt that the user fails to automatically renew the fee due to insufficient balance.
For example, after determining the game account preset by the first client as the target service account, the server may determine whether the remaining data amount of the game account is smaller than a preset threshold, and when the remaining data amount of the game account is smaller than the preset threshold, the server may deduct a data transfer amount from the binding account of the first client and perform automatic recharging on the game account, where the recharging amount is the data transfer amount deducted from the binding account of the first client.
Optionally, the server may receive a data transfer amount configured by the first client to the service account of the second client, and store the binding account of the first client, the service account of the second client, and the data transfer amount configured to the service account of the second client.
And S204, the server performs service processing on the target service account based on the data transfer amount.
After the server deducts the data transfer amount from the binding account of the first client, the server may perform service processing on the target service account based on the data transfer amount, for example, perform automatic charging on the target service account, where the charging amount is the data transfer amount deducted from the binding account of the first client.
In the embodiment of the invention, the server determines at least one service account preset by the first client, determines a target service account in the at least one service account, the target service account is any one of the at least one service account, and deducts a data transfer amount from a binding account of the first client when the residual data amount of the target service account is smaller than a preset threshold, wherein the data transfer amount is configured by the first client for the target service account, and performs service processing on the target service account based on the data transfer amount, so that the at least one service account can be automatically recharged by the first client, and the convenience of operation is improved.
Based on the schematic structural diagram of the data transfer system shown in fig. 1, the embodiment of the present invention discloses a schematic flow diagram of a data transfer method shown in fig. 3. As shown in fig. 3, the data transfer method may include the steps of:
s301, the first client acquires a business account number of the second client selected by the user of the first client.
Optionally, when receiving a service account configuration request sent by a user of the first client, the first client may display service account information, where the service account information includes at least one service account, and further receive a service account of the second client selected in the service account information by the user of the first client.
Taking the interface schematic diagram of the automatic charging interface shown in fig. 10 as an example, the first client may display a button having a function of configuring the service account number on the automatic charging interface, for example, an "add friend" button in fig. 10, and optionally, the first client may also display the service account number previously configured by the first client on the automatic charging interface. After a user of the first client sends a service account configuration request to the first client by clicking a "add friend" button, the first client may respond to the service account configuration request to display an account list, where an interface schematic diagram of the account list may be as shown in fig. 10, contact information in the account list may be the same as contact information in an address book, and an arrangement manner of the contact information in the account list may also be the same as an arrangement manner of the contact information in the address book, so that the user may quickly find a service account to be configured.
S302, the first client sends a data transfer authorization request to the server, wherein the data transfer authorization request carries a business account number of the second client, so that the server sends authorization request information to the second client according to the business account number, when receiving data transfer authorization information generated by the second client responding to the authorization request information, the server generates authorization information, and the authorization information carries the business account number of the second client.
For example, an interface schematic diagram of the data transfer authorization request sent by the first client may be as shown in fig. 10, where the data transfer authorization request may include a client identifier (e.g., "mr. m"), a selected service account number (e.g., renewal phone 156XXXX2785) of the second client, a data transfer amount (e.g., 50.00 m) configured by the first client for the service account number of the second client, and optionally, the data transfer authorization request may further include a remaining data amount (e.g., 10.00 m) of the service account number of the second client. The user of the first client can click the 'invite the other party to open' button, and the first client responds to the operation and sends a data transfer authorization request to the server.
For example, the authorization request information received by the second client may be as shown in fig. 10, where the authorization request information may include a client identifier (e.g., "mr. m") of the second client, a selected service account number (e.g., renewal phone 156XXXX2785) of the second client, a data transfer amount configured by the first client for the service account number of the second client (e.g., a renewal amount of 50.00 yuan), and optionally, the authorization request information may further include a remaining data amount (e.g., a current balance of 10.00 yuan) of the service account number of the second client. The user of the second client may click the "confirm open" button, which indicates that the user of the second client allows the server to query the remaining data volume of the service account of the second client through the operator, and send the remaining data volume to the first client, and the second client may send data transfer authorization information to the server in response to the operation. Optionally, the user of the second client may click a "reject" button, and the second client may send, in response to the operation, a reject authorization message to the first client through the server, so that the first client cannot automatically renew the service account of the second client.
And S303, when the authorization information sent by the server is received, the first client configures a service account of the second client.
Optionally, the first client may send the data transfer amount configured for the service account of the second client to the server, so that the server stores the binding account of the first client, the service account of the second client, and the data transfer amount configured for the service account of the second client.
Optionally, the first client may obtain a service account of the first client selected by a user of the first client, configure the service account of the first client, and configure a data transfer amount for the service account of the first client, so that the first client may send the service account of the first client and the data transfer amount configured for the service account of the first client to the server, so that the server stores the binding account of the first client, the service account of the first client, and the data transfer amount configured for the service account of the first client.
In the embodiment of the invention, the first client side obtains the service account number of the second client side selected by the user of the first client side, sends the data transfer authorization request to the server, and when the authorization information sent by the server is received, the first client side configures the service account number of the second client side, so that at least one service account number can be automatically charged through the first client side, and the convenience of operation is improved.
Based on the schematic structural diagram of the data transfer system shown in fig. 1, the embodiment of the present invention discloses a schematic flow diagram of a data transfer method shown in fig. 4. As shown in fig. 4, the data transfer method may include the steps of:
s401, the first client side obtains a business account number of the second client side selected by a user of the first client side.
Optionally, when receiving a service account configuration request sent by a user of the first client, the first client may display service account information, where the service account information includes at least one service account, and then the first client receives a service account of a second client selected in the service account information by the user of the first client.
Optionally, the first client may obtain a service account of the first client selected by a user of the first client, configure the service account of the first client, and configure a data transfer amount for the service account of the first client, so as to send the service account of the first client and the data transfer amount configured for the service account of the first client to the server, so that the server stores a binding account of the first client, the service account of the first client, and the data transfer amount configured for the service account of the first client.
S402, the first client sends a data transfer authorization request to the server, and the data transfer authorization request carries the business account number of the second client.
And S403, the server sends authorization request information to the second client according to the service account.
S404, when receiving the data transfer authorization information generated by the second client responding to the authorization request information, the server sends the authorization information to the first client.
Optionally, when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server may store the client identifier of the first client and the service account of the second client.
S405, the first client configures a service account of the second client.
Optionally, the first client may further configure a data transfer amount for the service account of the second client, and send the data transfer amount configured for the service account of the second client to the server, so that the server stores the binding account of the first client, the service account of the second client, and the data transfer amount configured for the service account of the second client.
S406, the server determines a target service account from the at least one service account configured by the first client, where the target service account is any one of the at least one service account.
S407, when the remaining data amount of the target service account is smaller than the preset threshold, the server deducts a data transfer amount from the binding account of the first client, where the data transfer amount is configured by the first client for the target service account.
S408, the server performs service processing on the target service account based on the data transfer amount.
In the embodiment of the invention, a first client acquires a service account number of a second client selected by a user of the first client, sends a data transfer authorization request to a server, the first client configures the service account number of the second client when receiving authorization information sent by the server, the server determines a target service account number in at least one service account number preset by the first client, deducts a data transfer amount from a binding account number of the first client when the residual data amount of the target service account number is less than a preset threshold value, performs service processing on the target service account number based on the data transfer amount, and can automatically recharge at least one service account number through the first client, thereby improving the convenience of operation.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a server provided in an embodiment of the present invention, where the server may be used to implement part or all of the steps in the method embodiments shown in fig. 2 and 4, and as shown in the figure, the server in the embodiment at least may include a service account determining module 501, a transfer amount deducting module 502, and a service processing module 503, where:
the service account determining module 501 is configured to determine at least one service account preset by the first client.
The service account determining module 501 is further configured to determine a target service account in the at least one service account, where the target service account is any one of the at least one service account.
A transfer amount deduction module 502, configured to deduct a data transfer amount from the binding account of the first client when a remaining data amount of the target service account is smaller than a preset threshold, where the data transfer amount is configured by the first client for the target service account.
A service processing module 503, configured to perform service processing on the target service account based on the data transfer amount.
Optionally, the server in the embodiment of the present invention may further include:
a receiving module 504, configured to receive a data transfer authorization request sent by the first client before the service account determining module 501 determines at least one service account preset by the first client, where the data transfer authorization request carries a service account of a second client.
And an information sending module 505, configured to send authorization request information to the second client according to the service account of the second client.
A storage module 506, configured to store the client identifier of the first client and the service account of the second client when receiving data transfer authorization information generated by the second client in response to the authorization request information.
Optionally, the server in the embodiment of the present invention may further include:
an information sending module 505, configured to send authorization information to the first client when receiving data transfer authorization information generated by the second client in response to the authorization request information after sending authorization request information to the second client according to the service account of the second client, where the authorization information carries the service account of the second client, so that the first client configures the service account of the second client according to the authorization information.
Optionally, the receiving module 504 is further configured to receive a data transfer amount configured by the first client to the service account of the second client.
Further, the storage module 506 is further configured to store the binding account of the first client, the service account of the second client, and a data transfer amount configured for the service account of the second client.
In the embodiment of the present invention, the service account determining module 501 determines at least one service account preset by the first client, determines the target service account in the at least one service account, and when the remaining data amount of the target service account is smaller than a preset threshold, the transfer amount deducting module 502 deducts the data transfer amount from the binding account of the first client, and the service processing module 503 performs service processing on the target service account based on the data transfer amount, so that the first client can automatically recharge the at least one service account, thereby improving the convenience of operation.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a server according to another embodiment of the present invention, where the server according to the embodiment of the present invention may be used to implement the method according to the embodiment of the present invention shown in fig. 2 and 4, for convenience of description, only the part related to the embodiment of the present invention is shown, and details of the specific technology are not disclosed, please refer to the embodiment of the present invention shown in fig. 2 and 4.
As shown in fig. 6, the server includes: at least one processor 601, e.g., a CPU, at least one input device 603, at least one output device 604, memory 605, at least one communication bus 602. Wherein a communication bus 602 is used to enable the connection communication between these components. The input device 603 may specifically be a network interface, and the like, and is used for performing data interaction with the first client. The output device 604 may specifically be a network interface, and is used for performing data interaction with the first client. The memory 605 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory, which is specifically configured to store the binding account number of the first client, the configured service account number of the second client, and the configured data transfer amount of the service account number of the second client. The memory 605 may optionally include at least one storage device located remotely from the processor 601. A set of program codes is stored in the memory 605 and the processor 601, input device 603, and output device 604 call the program codes stored in the memory 605 for performing the following:
the processor 601 determines at least one service account number preset by the first client.
The processor 601 determines a target business account number in the at least one business account number, where the target business account number is any one of the at least one business account number.
When the remaining data amount of the target service account is smaller than a preset threshold, the processor 601 deducts a data transfer amount from the binding account of the first client, where the data transfer amount is configured by the first client for the target service account.
The processor 601 performs service processing on the target service account based on the data transfer amount.
Optionally, before the processor 601 determines at least one service account preset by the first client, the following operations may also be performed:
the input device 603 receives a data transfer authorization request sent by the first client, where the data transfer authorization request carries a service account of a second client.
The output device 604 sends authorization request information to the second client according to the service account of the second client.
When the input device 603 receives data transfer authorization information generated by the second client in response to the authorization request information, the processor 601 stores the client identifier of the first client and the service account number of the second client.
Optionally, after the output device 604 sends the authorization request information to the second client according to the service account of the second client, the following operations may also be performed:
when the input device 603 receives data transfer authorization information generated by the second client in response to the authorization request information, the output device 604 sends authorization information to the first client, where the authorization information carries a service account of the second client, so that the first client configures the service account of the second client according to the authorization information.
Optionally, the input device 603 may further perform the following operations:
and receiving the data transfer amount configured by the first client to the service account of the second client.
Further, the processor 601 stores the binding account of the first client, the service account of the second client, and the data transfer amount configured to the service account of the second client.
Specifically, the server described in the embodiment of the present invention may be used to implement part or all of the processes in the embodiment of the method described in conjunction with fig. 2 and 4.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a client provided in an embodiment of the present invention, where the client may be used to implement part or all of the steps in the method embodiments shown in fig. 3 and 4, and as shown in the figure, the client in the embodiment at least may include a service account acquisition module 701, a request sending module 702, and a configuration module 703, where:
the service account acquiring module 701 is configured to acquire a service account of a second client selected by a user of the client.
A request sending module 702, configured to send a data transfer authorization request to a server, where the data transfer authorization request carries a service account of a second client, so that the server sends authorization request information to the second client according to the service account, and generates authorization information when receiving data transfer authorization information generated by the second client in response to the authorization request information, where the authorization information carries the service account of the second client.
A configuration module 703, configured to configure the service account of the second client when receiving the authorization information sent by the server.
Optionally, the service account number obtaining module 701 is specifically configured to:
and when a service account configuration request sent by a user of the client is received, displaying service account information, wherein the service account information comprises at least one service account.
And receiving a service account of a second client selected by the user of the client in the service account information.
Optionally, the client further includes:
a transfer amount sending module 704, configured to send the data transfer amount configured for the service account of the second client to the server, so that the server stores the binding account of the client, the service account of the second client, and the data transfer amount configured for the service account of the second client.
Optionally, the service account number obtaining module 701 is further configured to obtain a service account number of the client selected by a user of the client.
The configuration module 703 is further configured to configure the service account of the client, and configure a data transfer amount for the service account of the client.
Further, the client further includes:
a service account sending module 705, configured to send the service account of the client and the data transfer amount configured to the service account of the client to the server, so that the server stores the binding account of the client, the service account of the client, and the data transfer amount configured to the service account of the client.
In the embodiment of the present invention, a service account acquisition module 701 acquires a service account of a second client selected by a user of the client, a request sending module 702 sends a data transfer authorization request to a server, and when receiving authorization information sent by the server, a configuration module 703 configures the service account of the second client, so that at least one service account can be automatically charged by a first client, thereby improving convenience of operation.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a client according to another embodiment of the present invention, where the client according to the embodiment of the present invention can be used to implement the method according to the embodiment of the present invention shown in fig. 3 and 4, for convenience of description, only the part related to the embodiment of the present invention is shown, and details of the specific technology are not disclosed, please refer to the embodiment of the present invention shown in fig. 3 and 4.
As shown in fig. 8, the client includes: at least one processor 801, such as a CPU, at least one input device 803, at least one output device 804, memory 805, at least one communication bus 802. Wherein a communication bus 802 is used to enable connective communication between these components. The input device 803 may specifically be a network interface, etc., and is used for performing data interaction with the server. The output device 804 may specifically be a network interface, and is used for performing data interaction with a server. The memory 805 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory, specifically for storing the service account configured for the second client and the data transfer amount configured for the service account of the second client. The memory 805 may optionally include at least one memory device located remotely from the processor 801 as previously described. A set of program codes is stored in the memory 805, and the processor 801, the input device 803, and the output device 804 call the program codes stored in the memory 805 for performing the following operations:
the input device 803 obtains the service account number of the second client selected by the user of the client.
The output device 804 sends a data transfer authorization request to a server, where the data transfer authorization request carries the service account number of the second client, so that the server sends authorization request information to the second client according to the service account number, and when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server generates authorization information, where the authorization information carries the service account number of the second client.
When the input device 803 receives the authorization information sent by the server, the processor 801 configures the business account number of the second client.
Optionally, the input device 803 obtains the service account of the second client selected by the user of the client, and specifically may be:
when the input device 803 receives a service account configuration request sent by a user of the client, the client displays service account information, where the service account information includes at least one service account.
The input device 803 receives the service account of the second client selected by the user of the client in the service account information.
Optionally, the output device 804 may further send the data transfer amount configured for the service account of the second client to the server, so that the server stores the binding account of the client, the service account of the second client, and the data transfer amount configured for the service account of the second client.
Optionally, the input device 803 may further obtain a service account of the client selected by the user of the client.
The processor 801 configures the service account of the client, and configures a data transfer amount for the service account of the client.
The output device 804 sends the service account of the client and the data transfer amount configured for the service account of the client to the server, so that the server stores the binding account of the client, the service account of the client and the data transfer amount configured for the service account of the client.
Specifically, the client described in the embodiment of the present invention may be used to implement part or all of the processes in the embodiment of the method described in conjunction with fig. 3 and 4.
Referring to fig. 9, fig. 9 is a schematic structural diagram of a data transfer system according to an embodiment of the present invention. Specifically, as shown in fig. 9, the system according to the embodiment of the present invention includes a server and a client.
Specifically, the server and the client may refer to the related description of the above embodiments, which is not repeated herein.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.

Claims (19)

1. A method of data transfer, the method comprising:
the method comprises the steps that a server receives a data transfer authorization request sent by a first client, wherein the data transfer authorization request carries a business account of a second client, and a user of the first client and a user of the second client are different users;
the server sends authorization request information to the second client according to the service account of the second client;
when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server stores a client identifier of the first client and a service account of the second client;
the server determines at least one business account preset by the first client, wherein the at least one business account comprises a business account of the second client;
the server determines a first business account number in the at least one business account number as a target business account number;
when the remaining data volume of the target service account is smaller than a preset threshold, the server deducts a data transfer volume from the binding account of the first client, wherein the data transfer volume is configured for the target service account by the first client;
the server performs service processing on the target service account based on the data transfer amount;
the server determines a second service account number in the at least one service account number as a target service account number, triggers execution, when the remaining data volume of the target service account number is smaller than a preset threshold value, the server deducts a data transfer volume from a binding account number of the first client, wherein the data transfer volume is configured by the first client for the target service account number, the server performs service processing on the target service account number based on the data transfer volume until the server determines the last service account number in the at least one service account number as the target service account number, and triggers execution, when the remaining data volume of the target service account number is smaller than the preset threshold value, the server deducts the data transfer volume from the binding account number of the first client, wherein the data transfer volume is configured by the first client for the target service account number, and the server performs service processing on the target service account based on the data transfer amount.
2. The method of claim 1, wherein after the server sends the authorization request information to the second client according to the service account of the second client, the method further comprises:
when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server sends authorization information to the first client, wherein the authorization information carries a service account of the second client, so that the first client configures the service account of the second client according to the authorization information.
3. The method of claim 2, wherein the method further comprises:
the server receives a data transfer amount configured by the first client to a service account of the second client;
and the server stores the binding account of the first client, the service account of the second client and the data transfer amount configured to the service account of the second client.
4. A method of data transfer, the method comprising:
a first client acquires a service account number of a second client selected by a user of the first client, wherein the user of the first client and the user of the second client are different users;
the first client sends a data transfer authorization request to a server, wherein the data transfer authorization request carries a business account number of the second client, so that the server sends authorization request information to the second client according to the business account number, when receiving data transfer authorization information generated by the second client in response to the authorization request information, the server generates authorization information and stores the business account number of the second client, wherein the authorization information carries the business account number of the second client, the server stores at least one business account number, the at least one business account number comprises the business account number of the second client, and the at least one business account number is used for the server to execute the method according to any one of claims 1 to 3;
and when receiving the authorization information sent by the server, the first client configures the service account of the second client.
5. The method of claim 4, wherein the obtaining, by the first client, the service account number of the second client selected by the user of the first client comprises:
when a service account configuration request sent by a user of the first client is received, the first client displays service account information, wherein the service account information comprises at least one service account;
and the first client receives the service account of the second client selected in the service account information by the user of the first client.
6. The method of claim 4, wherein the method further comprises:
and the first client sends the data transfer amount configured for the service account of the second client to the server, so that the server stores the binding account of the first client, the service account of the second client and the data transfer amount configured for the service account of the second client.
7. The method of claim 4, wherein the method further comprises:
the first client acquires a business account number of the first client selected by a user of the first client;
the first client configures the service account of the first client and configures data transfer amount for the service account of the first client;
the first client sends the service account of the first client and the data transfer amount configured for the service account of the first client to the server, so that the server stores the binding account of the first client, the service account of the first client and the data transfer amount configured for the service account of the first client.
8. A server, characterized in that the server comprises:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a data transfer authorization request sent by a first client, the data transfer authorization request carries a business account number of a second client, and a user of the first client and a user of the second client are different users;
the information sending module is used for sending authorization request information to the second client according to the business account of the second client;
the storage module is used for storing the client identifier of the first client and the service account number of the second client when receiving data transfer authorization information generated by the second client in response to the authorization request information;
the service account determining module is used for determining at least one service account preset by the first client, wherein the at least one service account comprises a service account of the second client;
the service account determining module is further configured to determine a first service account of the at least one service account as a target service account;
a transfer amount deduction module, configured to deduct a data transfer amount from a binding account of the first client when a remaining data amount of the target service account is smaller than a preset threshold, where the data transfer amount is configured for the target service account by the first client;
the service processing module is used for carrying out service processing on the target service account based on the data transfer amount;
the service account determining module is further configured to determine a second service account of the at least one service account as a target service account, trigger the transfer amount deducting module to deduct a data transfer amount from a binding account of the first client when a remaining data amount of the target service account is smaller than a preset threshold, where the data transfer amount is configured by the first client for the target service account, perform service processing on the target service account based on the data transfer amount until the service account determining module determines a last service account of the at least one service account as the target service account, and trigger the transfer amount deducting module to deduct the data transfer amount from the binding account of the first client when the remaining data amount of the target service account is smaller than the preset threshold, the data transfer amount is configured by the first client to the target service account, and the service processing module performs service processing on the target service account based on the data transfer amount.
9. The server of claim 8, wherein the server further comprises:
and the information sending module is used for sending authorization information to the first client when receiving data transfer authorization information generated by the second client in response to the authorization request information after sending the authorization request information to the second client according to the business account of the second client, wherein the authorization information carries the business account of the second client, so that the first client configures the business account of the second client according to the authorization information.
10. The server according to claim 9,
the receiving module is further configured to receive a data transfer amount configured by the first client to the service account of the second client;
the storage module is further configured to store the binding account of the first client, the service account of the second client, and a data transfer amount configured to the service account of the second client.
11. A client, the client comprising:
the service account acquisition module is used for acquiring a service account of a second client selected by a user of the client, wherein the user of the first client and the user of the second client are different users;
a request sending module, configured to send a data transfer authorization request to a server, where the data transfer authorization request carries a service account of the second client, so that the server sends authorization request information to the second client according to the service account, generates authorization information when receiving data transfer authorization information generated by the second client in response to the authorization request information, and stores the service account of the second client, where the authorization information carries the service account of the second client, and the server stores at least one service account, where the at least one service account includes the service account of the second client, and is used for the server to execute the method according to any one of claims 1 to 3;
and the configuration module is used for configuring the service account of the second client when the authorization information sent by the server is received.
12. The client according to claim 11, wherein the service account number obtaining module is specifically configured to:
when a service account configuration request sent by a user of the client is received, displaying service account information, wherein the service account information comprises at least one service account;
and receiving the service account of the second client selected by the user of the client in the service account information.
13. The client of claim 11, wherein the client further comprises:
and the transfer amount sending module is used for sending the data transfer amount configured for the service account of the second client to the server so that the server stores the binding account of the client, the service account of the second client and the data transfer amount configured for the service account of the second client.
14. The client of claim 11,
the business account acquisition module is also used for acquiring the business account of the client selected by the user of the client;
the configuration module is further configured to configure the service account of the client and configure a data transfer amount for the service account of the client;
the client further comprises:
and the service account sending module is used for sending the service account of the client and the data transfer amount configured for the service account of the client to the server so that the server stores the binding account of the client, the service account of the client and the data transfer amount configured for the service account of the client.
15. A data transfer system, characterized in that the system comprises a server according to any of claims 8 to 10 and a client according to any of claims 11 to 14.
16. A server, characterized in that the server comprises:
a memory for storing program code;
a processor for calling the program code stored in the memory to perform the data transfer method of any of claims 1 to 3.
17. A client, the client comprising:
a memory for storing program code;
a processor for calling the program code stored in the memory to perform the data transfer method of any of claims 4 to 7.
18. A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a terminal, causes the terminal to execute the data transfer method according to any one of claims 1 to 3.
19. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a terminal, causes the terminal to execute the data transfer method according to any one of claims 4 to 7.
CN201611110880.3A 2016-12-06 2016-12-06 Data transfer method, server, client and system Active CN108156206B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611110880.3A CN108156206B (en) 2016-12-06 2016-12-06 Data transfer method, server, client and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611110880.3A CN108156206B (en) 2016-12-06 2016-12-06 Data transfer method, server, client and system

Publications (2)

Publication Number Publication Date
CN108156206A CN108156206A (en) 2018-06-12
CN108156206B true CN108156206B (en) 2021-12-28

Family

ID=62468293

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611110880.3A Active CN108156206B (en) 2016-12-06 2016-12-06 Data transfer method, server, client and system

Country Status (1)

Country Link
CN (1) CN108156206B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110717745B (en) * 2018-07-12 2024-01-12 腾讯科技(深圳)有限公司 Service processing method and server
CN112073486A (en) * 2020-08-28 2020-12-11 北京金山云网络技术有限公司 Resource transfer method and device, storage medium and electronic device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753910A (en) * 2013-12-31 2015-07-01 腾讯科技(深圳)有限公司 Data processing method, platform, server and system
CN105407086A (en) * 2015-10-28 2016-03-16 腾讯科技(深圳)有限公司 Temporary authorization method, client and server

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9172693B2 (en) * 2010-11-11 2015-10-27 Paypal, Inc. Quick payment using mobile device binding
CN110351339B (en) * 2014-08-21 2022-05-27 创新先进技术有限公司 Service processing method and device and server
CN104616142B (en) * 2014-09-23 2021-12-24 腾讯科技(深圳)有限公司 Data transfer method, server, mobile terminal and system
CN104463568B (en) * 2014-10-27 2017-08-25 北京金和软件股份有限公司 A kind of recharge method of virtual coin
CN104980483B (en) * 2014-12-26 2019-09-13 腾讯科技(深圳)有限公司 A kind of data transfering method, server and data transferring system
US20160300254A1 (en) * 2015-04-13 2016-10-13 Platphorm, LLC System and method for charging and compensating users for communications between the users

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104753910A (en) * 2013-12-31 2015-07-01 腾讯科技(深圳)有限公司 Data processing method, platform, server and system
CN105407086A (en) * 2015-10-28 2016-03-16 腾讯科技(深圳)有限公司 Temporary authorization method, client and server

Also Published As

Publication number Publication date
CN108156206A (en) 2018-06-12

Similar Documents

Publication Publication Date Title
CN106888203B (en) Virtual object distribution method and device based on augmented reality
US10742582B2 (en) Launching a client application based on a message
KR101821511B1 (en) Data processing method based on instant messaging or social applications, and device thereof
CN108064373B (en) Resource transfer method and device
CN106506322A (en) The implementation method of business function and device
US20190370846A1 (en) Service processing method, storage medium, and terminal
CN104616142B (en) Data transfer method, server, mobile terminal and system
CN108960839B (en) Payment method and device
CN104901994A (en) Attribute value transfer method, device and system for user in network system
WO2018184494A1 (en) Information processing method and device and storage medium
CN107635251A (en) Fiduciary network traffics concocting method
CN101329793A (en) Method and system for processing electric currency information
CN111031140A (en) Resource settlement method and device, electronic equipment and storage medium
CN105208179B (en) Telephone number identification method and system and electronic product
CN108156206B (en) Data transfer method, server, client and system
CN104955005A (en) Method and device for depositing for communication terminal
CN107679842A (en) Fiduciary virtual resource concocting method
CN104636923A (en) Information transmission method, device and system
GB2490007A (en) Tracking message responses by associating calling and recipient phone numbers with a message
CN115829556A (en) Payment method, device, apparatus, medium and product
CN115310958A (en) Payment method, device, equipment, system and medium based on 5G message application
CN111539742B (en) Information processing method, information processing device, electronic equipment and storage medium
CN112749958A (en) Resource transfer method, device, equipment and storage medium
US20160063448A1 (en) System and Method for Establishing an Open Communication Channel With an Advisor Via a Mobile Device
CN111476562A (en) Virtual resource transfer method, device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant