CN110599184A - Method and device for network service account transaction, server and storage medium - Google Patents
Method and device for network service account transaction, server and storage medium Download PDFInfo
- Publication number
- CN110599184A CN110599184A CN201910938359.6A CN201910938359A CN110599184A CN 110599184 A CN110599184 A CN 110599184A CN 201910938359 A CN201910938359 A CN 201910938359A CN 110599184 A CN110599184 A CN 110599184A
- Authority
- CN
- China
- Prior art keywords
- account
- network service
- transaction
- information
- user terminal
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000004891 communication Methods 0.000 claims abstract description 52
- 230000004044 response Effects 0.000 claims abstract description 16
- 238000012545 processing Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 12
- 230000009471 action Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Classifications
-
- 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/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
The invention relates to a method and a device for network service account transaction, a server and a computer readable storage medium. The method comprises the following steps: receiving an account selling request from a first user terminal through a communication interface, wherein the account selling request at least comprises an account of a network service, a password associated with the account and a selling price; in response to an account selling request, creating a first block in a block chain to record account information; generating display information, wherein the display information comprises the name, account number and selling price of the network service; and publishing the presentation information via the communication interface so that the presentation information can be displayed by each user terminal. This helps to improve the security of the transaction information.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for network service account transaction, a server and a computer-readable storage medium.
Background
With the popularity and development of the internet, users often own accounts for various network services (e.g., network games, social software, etc.). Some of these network service accounts may relate to virtual property, such as account levels of game accounts, character equipment and virtual currency, and honor titles of social accounts, among others, so that these accounts have transactional value. The user may choose to sell these accounts when they are no longer in use, or the user may buy a certain account on his demand.
Currently, such account transactions are typically conducted on third party transaction platforms. The user issues the account number on the platform, and the platform processes the transaction information of the account number. The buyer then contacts the platform to buy the account number and the seller contacts the platform to collect the amount of the sale. However, in such a transaction manner, various account information and transaction data are completely stored and maintained by the third party transaction platform, which may cause a data security hazard, for example, data loss due to platform failure, data tampering due to malicious intrusion, and the like. In addition, such third party transaction platforms often do not get authenticated and authorized by the network service provider, which may increase the risk of the account information of the user being revealed.
Disclosure of Invention
It would be advantageous to provide a mechanism that may alleviate, reduce or even eliminate one or more of the above-mentioned problems.
According to some embodiments of the invention, there is provided a method for network service account transactions, comprising: receiving an account selling request from a first user terminal through a communication interface, wherein the account selling request at least comprises an account of a network service, a password associated with the account and a selling price; in response to the account selling request, creating a first block in a block chain to record account information; generating display information, wherein the display information comprises the name of the network service, the account number and the selling price; and publishing the presentation information via the communication interface so that the presentation information can be displayed by each user terminal.
In some embodiments, the method further comprises: receiving, via the communications interface, an account buy request from a second user terminal and a message indicating that the second user terminal has successfully paid the ask price for the account; registering a new password associated with the account number with a service provider providing the network service; creating a second block in the block chain to record the transaction history of the account number; generating transaction receipt information, wherein the transaction receipt information includes the new password; and sending the transaction receipt information to the second user terminal via the communication interface.
In some embodiments, registering the account associated new password with the service provider comprises: requesting the service provider to modify the password associated with the account number to the new password, wherein the new password is randomly generated by the service provider.
In some embodiments, creating a second chunk in the chain of chunks comprises: and generating a hash value corresponding to the second block according to a preset hash algorithm.
In some embodiments, the transaction history includes a number of times the account number has been currently transacted, and the generating transaction response piece information includes: in response to the transaction history indicating that the account number has been currently transacted more than 0 times, further including the hash value in the transaction receipt information, such that the hash value is included in an account number sell request for creating a next first chunk when the account number is sold next time.
In some embodiments, the transaction history further comprises at least one of: the current price or time of transaction of the account number.
In some embodiments, the transaction receipt information further comprises at least one of: a name of the network service, a type of the network service, the account number, a price at which the account number is currently traded, or a time of transaction.
In some embodiments, the method further comprises: and paying the amount corresponding to the selling price to the first user terminal through the communication interface.
In some embodiments, the method further comprises: verifying the validity of the account number selling request based on the account number and the password included in the account number selling request before creating a first block in a block chain, wherein the first block is created in response to the account number selling request being valid.
In some embodiments, the account information includes a name of the network service, the account, and a password associated with the account.
According to some embodiments of the invention, there is provided an apparatus for network service account transactions, comprising: the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is configured to receive an account selling request from a first user terminal through a communication interface, and the account selling request at least comprises an account of a network service, a password associated with the account and a selling price; the block creating module is configured to respond to the account selling request, and create a first block in a block chain to record account information; an information generation module configured to generate presentation information, wherein the presentation information includes a name of the network service, the account number, and the ask price; and a sending module configured to publish the presentation information via the communication interface so that the presentation information can be displayed by each user terminal.
According to some embodiments of the invention, there is provided a server comprising: a communication interface; a processor; and a memory having instructions stored thereon, which when executed on the processor, cause the processor to perform any of the methods described above.
According to some embodiments of the invention, there is provided a computer-readable storage medium having stored thereon instructions which, when executed on a processor, cause the processor to perform any of the methods described above.
Embodiments of the present invention provide various advantages. By virtue of the properties of the blockchain (e.g., distributed data storage and encryption algorithms, etc.), the security of the transaction process is improved, and the risk of data loss, data tampering, etc. is avoided or at least substantially reduced. In addition, in some embodiments, mechanisms such as verifying the validity of the account number and password with the network service provider, registering a new password associated with the account number, etc. require that the participant in the transaction process be authenticated or authorized by the corresponding network service provider, thereby further enhancing the security of the transaction process.
Drawings
Further details, features and advantages of the invention are disclosed in the following description of exemplary embodiments with reference to the accompanying drawings, in which:
fig. 1 is a flowchart illustrating a typical network service account transaction method in the related art;
FIG. 2 illustrates a schematic diagram of an example system in which various methods described herein may be implemented, according to an embodiment of the invention;
FIG. 3 shows a flow diagram of an example method performed in a network service account transaction, according to an embodiment of the invention;
FIG. 4 illustrates an exemplary and schematic block diagram of the web service account transaction platform server of FIG. 2 in greater detail;
FIG. 5 shows a schematic diagram of a blockchain according to an embodiment of the invention;
FIGS. 6A-6D are diagrams illustrating an example user interface displayed at a terminal device according to an embodiment of the present invention; and is
FIG. 7 shows a schematic block diagram of an example computing device that represents the web service account transaction platform server of FIG. 2.
Detailed Description
Before describing embodiments of the present invention, several terms referred to herein are first explained.
1. Block chain
A blockchain is essentially a decentralized database, a string of data blocks that are generated in association using cryptography, where each data block is referred to as a block.
2. Hash value
The hash value is usually represented by a short string of random letters and numbers, and is a "data fingerprint" obtained by a hash algorithm on input information of any length. If a piece of plain text is converted into a hash value by a hash algorithm, even if only any one letter in the plain text is changed, the obtained hash value will be different. The hash algorithm has two important properties-irreversibility and output value uniqueness and unpredictability.
Embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Fig. 1 shows a flow chart of a typical network service account transaction method 100 in the related art. As shown in fig. 1, in the method 100, a seller contacts a transaction platform and provides information such as an account number and an account password to be sold. The platform presents the account information that can be opened out (e.g., name of web service, account number rating, virtual props, honor title, etc.) and waits for the buyer to appear. And the buyer selects an account number of the heart instrument through browsing the account number information displayed by the platform and makes a purchase by contacting the platform so as to carry out account number transaction. The platform completes the transaction and assists in completing the account change binding operation, and finally delivers the transaction amount to the seller (e.g., after a few days).
In the process shown in fig. 1, data information such as account number and password is stored on the transaction platform, and data such as transaction records is only maintained by the transaction platform. If the transaction platform itself fails or is illegally hacked, the security of the account number and the transaction data may be threatened. In some cases, internal camera operations of the transaction platform or violation operations of transaction participants may infringe upon the rights of the seller or buyer. At the same time, such transaction platforms are often third party platforms independent of the network service provider and not under the supervision of the network service provider, which may exacerbate the above-mentioned risks.
FIG. 2 shows a schematic diagram of an example system 200 in which various methods described herein may be implemented, according to an embodiment of the invention. Referring to FIG. 2, the example system 200 includes a first user terminal 210 (i.e., a seller device), a second user terminal 220 (i.e., a buyer device), a web services account transaction platform server 230, a web services provider server 240, a blockchain system 250, and a network 260.
The first user terminal 210 includes a display screen 214 and a first terminal application 212 that interacts with a first user (i.e., a vendor user) via the display screen 214. The second user terminal 220 comprises a display screen 224 and a second terminal application 222 for interacting with the second user, i.e. the buyer user, via the display screen 224. The first terminal application 212 and the second terminal application 222 may be the same or different applications. As will be described later, the first and second user terminals 210 and 220 may be used to interact with the web service account transaction platform server 230, for example, to send requests to and receive data from the web service account transaction platform server 230. The first terminal application 212 may be a terminal application provided by a network service account transaction platform or a network service provider or an applet (LiteApp) that is a lightweight application. In the case where the first terminal application 212 is an application that needs to be installed, the first terminal application 212 may be installed in the first user terminal 210. In the case where the first terminal application 212 is an applet, the first terminal application 212 may be directly opened on the first user terminal 210 by searching related information of the first terminal application 212 (such as a name of the first terminal application 212, etc.), scanning a graphic code (such as a barcode, a two-dimensional code, etc.) of the first terminal application 212, etc., without installing the first terminal application 212. The above description of the first terminal application 212 applies equally to the second terminal application 222 and is not repeated for the sake of brevity.
The first and second user terminals 210, 220 may be any type of mobile computing device, including a mobile computer or mobile computing device (e.g., Microsoft Surface devices, Personal Digital Assistants (PDAs), laptop computer, notebook computer, such as Apple iPad @ TMTablet computer, netbook, etc.), a mobile phone (e.g., a cellular phone, a smart phone such as Microsoft Windows phone, Apple iPhone, a phone that implements the Google Android operating system, a Palm device, a Blackberry device, etc.), a wearable computing device (e.g., a smart watch, a head mounted device, including smart glasses, such as Google Glass), or other types of mobile devices. In some embodiments, the first user terminal 210 and the second user terminal 220 may also be stationary computing devices. Further, the first user terminal 210 and the second user terminal 220 may be the same or different types of computing devices.
The web service account transaction platform server 230 may be a single server or a cluster of servers on which a web service account transaction application (described in detail below) may run. The web service account transaction application may interact with the first terminal application 212 at the first user terminal 210, the second terminal application 222 at the second user terminal 220, the blockchain system 250, and optionally the web service provider server 240 to perform the web service account transaction.
The network service provider server 240 may be the same or different single server or cluster of servers as the network service account transaction platform server 230. In some embodiments, the network service account transaction service may be provided directly by a network service provider (e.g., a game provider), as part of a network service (e.g., a network game) or as an additional service beyond a network service. In an alternative embodiment, the network service account transaction service may be provided by a third party authenticated or authorized by the network service provider as an intermediary service independent of the network service. For example, where the network service is a network game, the game account transaction may be a function embedded in the network game or may be a function in a standalone application. The standalone application may be provided by an online game provider or may be provided by a third party authenticated or authorized by the online game provider.
The network service account transaction platform server 230 and the network service provider server 240 are typically server computers with substantial memory and processor resources, but other embodiments are possible.
The blockchain system 250 may be a public chain, a private chain, or a federation chain. The network service account transaction platform server 230 may serve as a node of the blockchain system 250, and may write or read blockchain data to store account information, transaction history information, and other data in the blockchain system 250, or use the data in the blockchain system 250 to verify validity of a transaction account, validity of a transaction, and other data.
Examples of network 260 include a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), and/or a combination of communication networks such as the Internet. Each of the first user terminal 210, the second user terminal 220, the web service account transaction platform server 230, the web service provider server 240 may include at least one communication interface (not shown) capable of communicating over the network 260. Such communication interfaces may be one or more of the following: any type of network interface (e.g., a Network Interface Card (NIC)), wired or wireless (such as IEEE 802.11 wireless lan (wlan)) wireless interface, a global microwave access interoperability (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth. Further examples of communication interfaces are described elsewhere herein.
FIG. 3 illustrates a flow diagram of an example method 300 performed in a network service account transaction, according to an embodiment of the invention. The system 200 of fig. 2 may operate in accordance with the method 300.
Fig. 4 shows an exemplary and schematic block diagram of the web service account transaction platform server 230 of fig. 2 in more detail. As shown in fig. 4, the network service account transaction platform server 230 includes a communication interface 232 and a network service account transaction application 234. The web service account transaction application 234 includes a receiving module 234a, a sending module 234b, a block creating module 234c, an information generating module 234d, a password management module 234e, and a verification module 234 f.
Fig. 5 shows a schematic diagram of a blockchain 500 according to an embodiment of the invention. For simplicity, only two blocks 510 and 520 are shown in fig. 5. Block 510 includes a block header 512 and a block body 514, and block 520 includes a block header 522 and a block body 524. The block headers 512 and 522 record metadata for the respective blocks 510 and 520, and the block blocks 514 and 524 record actual data for the respective blocks 510 and 520. The metadata in the chunk header contains various pieces of information about the chunk, such as the generation time, the hash value of the actual data (i.e., the chunk), and the hash value of the last chunk.
Fig. 6A to 6D show schematic diagrams of example user interfaces 601 to 604 displayed at the first user terminal 210 or the second user terminal 220, respectively, according to embodiments of the present invention.
For illustrative purposes, the method 300 is described below with reference to FIGS. 2-5, 6A-6D.
At step 301, a first user terminal sends an account sell request to a network services account trading platform. The account selling request at least comprises an account of the network service, a password associated with the account and a selling price. In the event that the account is not the first transaction, the account sell request also includes a Hash value (Hash) provided in the transaction receipt of the last transaction. In the case where the network service account transaction service is provided by a third party as a mediating service, the account sell request may further include the name of the network service. Further, the account sell request may include account related data such as account level, rare properties owned by the account, honor title, and the like.
In one embodiment, the seller user sends an account sell request on the first user terminal 210 to the web services account trading platform server 230 through the first terminal application 212. For example, the seller user may fill out the relevant information contained in the account selling request on an account selling interface 601 as shown in fig. 6A. As shown in fig. 6A, the seller user needs to fill in the account number to be sold, the password of the account number, the amount of money to be sold, and the name of the network service (e.g., the name of the network game or the social software) corresponding to the account number. The amount may be settled in any variety of currencies, including various real and virtual currencies. In addition, in the case that the account number that the seller user wants to sell is not a first transaction, that is, in the case that the seller user is not an initial owner of the account number but obtains the account number by a transaction manner, it is also required to fill in the hash value generated by the last transaction. The seller user may then submit the filled-in content by clicking on the "submit" button to send an account sell request. Alternatively, the seller user may cancel the operation on the current interface by clicking a "cancel" button and return to the previously viewed interface. Optionally, the seller user may also fill out account related data (not shown) on the account selling interface 601 that the seller user deems important, such as account rating, rare props owned by the account, honor title, and the like.
At step 302, the network service account trading platform verifies the validity of the account selling request based on the account and password information contained in the account selling request. In one embodiment, the authentication module 234f of the network service account trading platform server 230 may attempt to log in the corresponding network service by using the account and the password included in the account selling request, and if the log-in is successful, the account selling request is determined to be valid. In the case where the network service account transaction platform server 230 and the network service provider server 240 are the same server, the verification module 234f may directly verify the validity of the account number and the password.
And when the account is not transacted for the first time, the network service account transaction platform can also verify the validity of the account selling request according to the hash value contained in the received account selling request. In one embodiment, the verification module 234f can query the relevant blocks in the blockchain system 250 according to the received hash value, compare the data contained in the received account number sell request with the transaction history data recorded in the queried relevant blocks to verify whether a historical transaction really exists, whether the seller user is the holder of the recorded account number, and the like.
At step 303, in response to the account sell request being valid, the network service account transaction platform creates a first block in the block chain to record account information. The account information may include, for example, the name of the network service, the account number, and a password associated with the account number. In one embodiment, the receiving module 234a of the web services account transaction platform server 230 receives an account sell request from the first user terminal 210 via the communication interface 232. Then, if the verification module 234f determines that the account sell request is valid, the blockchain creation module 234c of the web services account transaction platform server 230 creates a first block 510 on the blockchain 500 in the blockchain system 250. The block header 512 of the first block 510 may include a hash value of a previous block (not shown), a hash value of a current block, a timestamp, and the like. Block 514 of the first block 510 may include information of the account number to be transacted, such as the name of the network service, account number, password, etc. The hash value for the chunk may be generated according to a predetermined hash algorithm, which may be any known or future occurrence of a hash algorithm (e.g., SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, etc.).
At step 304, the network service account transaction platform generates presentation information. The display information includes the name, account number, selling price, etc. of the network service. The presentation information may also include account transaction history, such as number of transactions, time of last transaction, amount of last transaction, etc. The presentation information may also include account related data such as account rating, rare items owned by the account, honor title, etc. This information may help the buyer assess the value of the account being presented and make a decision whether to buy or not.
In one embodiment, the information generating module 234d of the network service account trading platform server 230 generates the above-mentioned display information according to the received account selling request. In another embodiment, the information generating module 234d further generates the above-mentioned display information according to the transaction history queried in the blockchain system 250. Alternatively or additionally, in yet another embodiment, the sending module 234b may send an account data query request to the network service provider server 240 via the communication interface 232 to obtain the account-related data. In the case that the network service account transaction platform server 230 and the network service provider server 240 are the same server, the information generating module 234d may directly access the account related data and generate the above-mentioned presentation information.
At step 305, the web service account transaction platform publishes the presentation information via the communication interface so that the presentation information can be displayed by each user terminal. In one embodiment, the sending module 234b of the web service account transaction platform server 230 publishes the presentation information generated at step 304 via the communication interface 232. The network service account transaction platform can issue the presentation information in various ways. For example, the network service account transaction platform may actively push a message containing the presentation information to the user terminal. Alternatively or additionally, the network service account transaction platform may link the presentation information to a publicly accessible or within a certain range accessible network address (e.g., a URL address) that the user may access using the user terminal to obtain the presentation information.
Fig. 6B schematically illustrates an interface 602 presenting information displayed on a user terminal. As shown in fig. 6B, the interface 602 may include the amount of the account number, an approximate transaction (e.g., number of transactions), and may include a link to a detailed transaction. The buyer user may access detailed transaction history information, such as historical transaction time, historical transaction amount, etc., by clicking on the link. Interface 602 may also include data for network services associated with the account number, such as the current level of the account number, what props are owned, the level of props owned, what title is owned, and the like. The buyer user can determine whether to purchase the account through the information. If the "buy" button is clicked, a purchase operation is performed. If the "back" button is clicked, the previously browsed interface is returned.
At step 306, the second user terminal performs a buy and pay action. In one embodiment, the buyer user browses the account presentation interface 602 on the second user terminal 220 and clicks the "buy" button. In response, interface 602 may jump to a payment interface or pop-up payment window to indicate to the purchaser user that payment is complete. The payment interface or window may be generated and provided by an internal transaction module of the web services account transaction platform, or may be provided by a third party payment platform (e.g., WeChat Payment, Payment Bay, hundred wallet, Bank APP, etc.). The buyer can complete the payment by using real money or virtual money approved by the network service account transaction platform. The amount paid by the buyer can be the amount to be sold by the seller, or the amount to be sold by the seller plus the service fee charged by the network service account transaction platform. Alternatively or additionally, the network services account transaction platform may charge the buyer user or the seller user for the service fee alone.
At step 307, the network services account transaction platform receives an account buy request from the second user terminal and a message indicating that the second user terminal has successfully paid a sell price for the account via the communication interface. In one embodiment, the receiving module 234a of the web service account transaction platform server 230 receives a message via the communication interface 232 that the purchaser user has performed a purchase operation on the second user terminal 220 through the second terminal application 222 and has completed the payment. The message indicating that the purchaser user has completed payment may come from an internal transaction module of the network service account transaction platform or may be payment credentials from a third party payment platform.
Then, the network service account number transaction platform registers a new password associated with the account number with a service provider providing the network service. This may be accomplished by, for example, steps 308 through 310.
At step 308, the web service account transaction platform sends a password modification request to the web service provider via the communication interface. In one embodiment, the password management module 234e of the web service account transaction platform server 230 generates a password modification request and the transmission module 234b of the web service account transaction platform server 230 transmits the password modification request to the web service provider server 240 via the communication interface 232. The network service account number transaction platform can be a platform authenticated by a network service provider, and the network service provider opens an interface for modifying the password so as to facilitate the operation of modifying the password. In this way, the password can be always managed by the network service provider and is not exposed to the network service account transaction platform, so that the risk of password leakage is reduced. In this case, the network service account transaction platform may request modification of the account password through an interface provided by the network service provider using the account number and the current password. However, in the case where the network service account transaction platform server 230 is the same server as the network service provider server 240, this step 308 may be omitted.
At step 309, the network service provider modifies the account password. In one embodiment, in response to the received account modification request, the network service provider server 240 resets the password of the corresponding account. The reset password may be a password randomly generated by the network service provider server 240. In the case where the network service account transaction platform server 230 is the same server as the network service provider server 240, the password management module 234e directly resets the account password in response to the received account buy request and the message indicating that the second user terminal has successfully paid the sell price for the account.
At step 310, the network service provider sends the modified new password to the network service account transaction platform. In one embodiment, the receiving module 234a of the web service account transaction platform server 230 receives the new password transmitted by the web service provider server 240 via the communication interface 232, and the received new password is saved by the password management module 234 e. In the case where the network service account transaction platform server 230 is the same server as the network service provider server 240, this step 310 may be omitted.
At step 311, the network service account transaction platform creates a second block in the blockchain to record the transaction history of the account. In one embodiment, the block creation module 234c of the web services account transaction platform server 230 creates the second block 520 in the block chain system 250. The second block 520 may be directly linked to the first block 510, and other intermediate blocks may also be present. Similar to the first block 510, the second block 520 includes a block head 522 and a block body 524. The chunk header 522 may include a hash value of a previous chunk (not shown), a hash value of a current chunk, a timestamp, and the like. Block 524 may include transaction history information for the account number, where the transaction history includes the number of times the account number has been transacted. In some embodiments, the transaction history also includes the price or time of the deal at which the account number is currently being traded, and possibly information about both parties to the trade, etc. The information data can be stored for subsequent query, and due to the inherent distributed storage property of the block chain, the safety of the recorded information data is guaranteed, and the information data can be effectively prevented from being lost or tampered.
At step 312, the network service account transaction platform generates transaction receipt information, which includes the new password. In one embodiment, the information generation module 234d of the web service account transaction platform server 130 obtains the new password from the password management module 234e and generates transaction receipt information containing the new password. Further, the information generating module 234d may also generate transaction receipt information from the account information, the transaction history information, and the like, to include one or more of the name of the network service, the type of the network service, the account number, the price at which the account number is currently traded, the transaction time, and the like in the transaction receipt information.
In addition, the information generating module 234d may include the hash value of the block (i.e., the second block 520) corresponding to the current transaction in the transaction receipt information, so that the hash value may be provided in the account selling request when the buyer user subsequently intends to sell the current account, thereby smoothly creating the next first block. After the transaction is completed, for example, when the seller user maliciously retrieves the sold account or other users steal the account, the buyer user can use the hash value to mention complaints from the transaction platform. This helps to improve the security of the buy account and allows the buyer user to protect his rightful interests in a convenient manner.
At step 313, the web service account transaction platform sends the transaction receipt information to the second user terminal via the communication interface. In one embodiment, the sending module 234b of the web services account transaction platform server 230 sends the transaction receipt information to the second user terminal 220 via the communication interface 232, which the buyer user can view on the second user terminal 220 through the second terminal application 222.
Fig. 6C schematically shows a transaction receipt interface 603 displayed on the user terminal. As shown in fig. 6C, transaction receipt interface 603 may include information such as an account number, a password (e.g., a new password randomly generated by a network service provider), a service name, a next transaction Hash, a time of transaction, an amount of transaction, etc.
At step 314, the network service account transaction platform pays an amount corresponding to the ask price to the first user terminal via the communication interface. In one embodiment, the network service account transaction platform server 230 may pay the seller user an amount corresponding to the selling price through an internal transaction module or a third party transaction platform. The amount may be settled in real currency or virtual currency. The "amount corresponding to the sold price" may be an amount actually paid by the purchaser user, or may be an amount obtained by deducting a service fee of the network service account transaction platform from an amount actually paid by the purchaser user. Alternatively or additionally, the network services account transaction platform may charge the buyer user or the seller user for the service fee alone.
At step 315, the network service account number transaction platform generates sell-back information, where the sell-back information includes an amount of money the network service account number transaction platform paid to the first user terminal. In one embodiment, the information generating module 234d of the network service account transaction platform server 130 generates the sold receipt information, which may include the transaction time, transaction amount, service fee, amount actually paid to the seller, etc. of the account, so as to inform the seller that the transaction is completed and facilitate the seller to view the information related to the transaction.
At step 316, the network service account transaction platform sends the sell response piece information to the first user terminal via the communication interface. In one embodiment, the sending module 234b of the web services account transaction platform server 230 sends the sell response piece information to the first user terminal 210 via the communication interface 232, and the seller user may view the sell response piece information on the first user terminal 210 through the first terminal application 212.
Fig. 6D schematically illustrates a sell response piece interface 604 displayed on the user terminal. As shown in FIG. 6D, sell response-piece interface 604 may include the time of the deal ("9.9.2019"), the service fee ("80.00"), the amount ultimately received ("720.00"), and the amount of the deal ("800.00").
Advantageously, by virtue of the characteristics of the blockchain (e.g., distributed data storage, data non-tamperable, etc.), the risk of transaction data being lost or tampered with is avoided or substantially reduced. Also, in a blockchain system, each access node maintains information for the entire blockchain, so that the entire transaction history can be traced back from any one access node.
Although the operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, nor that all illustrated operations be performed, to achieve desirable results. For example, steps 302, 315, and 316 may be optional in some embodiments.
Additionally, while particular functionality is discussed above with reference to particular modules, it should be noted that the functionality of the various modules discussed herein may be separated into multiple modules and/or at least some of the functionality of multiple modules may be combined into a single module. Additionally, a particular module performing an action discussed herein includes the particular module itself performing the action, or alternatively the particular module invoking or otherwise accessing another component or module that performs the action (or performs the action in conjunction with the particular module). Thus, a particular module that performs an action can include the particular module that performs the action itself and/or another module that the particular module that performs the action calls or otherwise accesses. For example, receive module 234 a/transmit module 234b, described above as program modules, may in alternative embodiments include corresponding instructions that control communication interface 232 to perform transmit/receive functions and corresponding hardware elements of communication interface 232 to perform transmit/receive actions.
More generally, various techniques may be described herein in the general context of software hardware elements or program modules. The various modules described above with respect to fig. 4 may be implemented in hardware or in hardware in combination with software and/or firmware. For example, the modules may be implemented as computer program code/instructions configured to be executed in one or more processors and stored in a computer-readable storage medium. Alternatively, the modules may be implemented as hardware logic/circuitry. For example, in an embodiment, one or more of the receiving module 234a, the transmitting module 234b, the chunk creating module 234c, the information generating module 234d, the password managing module 234e, and the verifying module 234f may be implemented together in a system on a chip (SoC). The SoC may include an integrated circuit chip including one or more components of a processor (e.g., a Central Processing Unit (CPU), microcontroller, microprocessor, Digital Signal Processor (DSP), etc.), memory, one or more communication interfaces, and/or other circuitry, and may optionally execute received program code and/or include embedded firmware to perform functions. The features of the techniques described herein are carrier-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.
FIG. 7 shows a schematic block diagram of an example computing device 700 that represents the web service account transaction platform server 230 of FIG. 2.
Computing device 700 may be a variety of different types of devices, such as a server computer, a device associated with a client (e.g., a client device), a system on a chip, and/or any other suitable computing device or computing system.
Computing device 700 may include at least one processor 702, memory 704, communication interface(s) 706, presentation device 708, other input/output (I/O) devices 710, and one or more mass storage devices 712, which may be capable of communicating with each other, such as through system bus 714 or other suitable connection.
The processor 702 may be a single processing unit or multiple processing units, all of which may include single or multiple computing units or multiple cores. The processor 702 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitry, and/or any devices that manipulate signals based on operational instructions. The processor 702 may be configured to retrieve and execute, among other capabilities, computer readable instructions stored in the memory 704, mass storage device 712, or other computer readable medium, such as program code for an operating system 716, program code for an application program 718, program code for other programs 720, etc., to implement the network service account transaction method provided by embodiments of the present invention.
Memory 704 and mass storage device 712 are examples of computer storage media for storing instructions that are executed by processor 702 to implement the various functions described above. By way of example, memory 704 may generally include both volatile and nonvolatile memory (e.g., RAM, ROM, and the like). In addition, mass storage device 712 may generally include a hard disk drive, a solid state drive, removable media, including external and removable drives, memory cards, flash memory, floppy disks, optical disks (e.g., CDs, DVDs), storage arrays, network attached storage, storage area networks, and the like. Memory 704 and mass storage 712 may both be referred to herein collectively as memory or computer storage media, and may be non-transitory media capable of storing computer-readable, processor-executable program instructions as computer program code that may be executed by processor 702 as a particular machine configured to implement the operations and functions described in the examples herein.
A number of program modules may be stored on the mass storage device 712. These programs include an operating system 716, one or more application programs 718, other programs 720, and program data 722, which can be loaded into memory 704 for execution. Examples of such applications or program modules may include, for instance, computer program logic (e.g., computer program code or instructions) for implementing the following components/functions: a receiving module 234a, a sending module 234b, a chunk creating module 234c, an information generating module 234d, a password management module 234e, and an authentication module 234f, and/or further embodiments described herein.
Although illustrated in fig. 7 as being stored in memory 704 of computing device 700, modules 716, 718, 720, and 722, or portions thereof, may be implemented using any form of computer-readable media that is accessible by computing device 700. As used herein, "computer-readable media" includes at least two types of computer-readable media, namely computer storage media and communication media.
Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device.
In contrast, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism. Computer storage media, as defined herein, does not include communication media.
Computing device 700 may also include one or more communication interfaces 706 for exchanging data with other devices, such as over a network, direct connection, or the like, as previously discussed. The one or more communication interfaces 706 are examples of the communication interfaces 232 shown in fig. 4. The communication interface 706 may facilitate communications within a variety of networks and protocol types, including wired networks (e.g., LAN, cable, etc.) and wireless networks (e.g., WLAN, cellular, satellite, etc.), the Internet, and so forth. The communication interface 706 may also provide for communication with external storage devices (not shown), such as in storage arrays, network attached storage, storage area networks, and so forth.
In some examples, a display device 708, such as a monitor, may be included for displaying information and images. Other I/O devices 710 may be devices that receive various inputs from a user and provide various outputs to the user, and may include touch input devices, gesture input devices, cameras, keyboards, remote controls, mice, printers, audio input/output devices, and so forth.
Variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed subject matter, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, the indefinite article "a" or "an" does not exclude a plurality, and "a plurality" means two or more. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Claims (13)
1. A method for network service account transactions, comprising:
receiving an account selling request from a first user terminal through a communication interface, wherein the account selling request at least comprises an account of a network service, a password associated with the account and a selling price;
in response to the account selling request, creating a first block in a block chain to record account information;
generating display information, wherein the display information comprises the name of the network service, the account number and the selling price; and is
And issuing the display information through the communication interface so that the display information can be displayed by each user terminal.
2. The method of claim 1, further comprising:
receiving, via the communications interface, an account buy request from a second user terminal and a message indicating that the second user terminal has successfully paid the ask price for the account;
registering a new password associated with the account number with a service provider providing the network service;
creating a second block in the block chain to record the transaction history of the account number;
generating transaction receipt information, wherein the transaction receipt information includes the new password; and is
Sending the transaction receipt information to the second user terminal via the communication interface.
3. The method of claim 2, wherein registering the account-associated new password with a service provider comprises: requesting the service provider to modify the password associated with the account number to the new password, wherein the new password is randomly generated by the service provider.
4. The method of claim 2, wherein creating a second chunk in the blockchain comprises: and generating a hash value corresponding to the second block according to a preset hash algorithm.
5. The method of claim 4, wherein the first and second light sources are selected from the group consisting of a red light source, a green light source, and a blue light source,
wherein the transaction history includes a number of times the account number has been currently transacted, an
Wherein the generating transaction receipt information comprises: in response to the transaction history indicating that the account number has been currently transacted more than 0 times, further including the hash value in the transaction receipt information, such that the hash value is included in an account number sell request for creating a next first chunk when the account number is sold next time.
6. The method of claim 5, wherein the transaction history further comprises at least one of: the current price or time of transaction of the account number.
7. The method of claim 2, wherein the transaction receipt information further comprises at least one of: a name of the network service, a type of the network service, the account number, a price at which the account number is currently traded, or a time of transaction.
8. The method of claim 2, further comprising: and paying the amount corresponding to the selling price to the first user terminal through the communication interface.
9. The method of any of claims 1-8, further comprising:
verifying the validity of the account sell request based on the account and the password included in the account sell request before creating a first block in the blockchain,
wherein the first tile is created in response to the account sell request being valid.
10. The method of any of claims 1-8, wherein the account information includes a name of the network service, the account, and a password associated with the account.
11. An apparatus for network service account transactions, comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is configured to receive an account selling request from a first user terminal through a communication interface, and the account selling request at least comprises an account of a network service, a password associated with the account and a selling price;
the block creating module is configured to respond to the account selling request, and create a first block in a block chain to record account information;
an information generation module configured to generate presentation information, wherein the presentation information includes a name of the network service, the account number, and the ask price; and
a sending module configured to publish the presentation information via the communication interface so that the presentation information can be displayed by each user terminal.
12. A server, comprising:
a communication interface;
a processor; and
a memory having instructions stored thereon that, when executed on the processor, cause the processor to perform the method of any of claims 1-10.
13. A computer-readable storage medium having stored thereon instructions that, when executed on a processor, cause the processor to perform the method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910938359.6A CN110599184A (en) | 2019-09-30 | 2019-09-30 | Method and device for network service account transaction, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910938359.6A CN110599184A (en) | 2019-09-30 | 2019-09-30 | Method and device for network service account transaction, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110599184A true CN110599184A (en) | 2019-12-20 |
Family
ID=68864904
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910938359.6A Pending CN110599184A (en) | 2019-09-30 | 2019-09-30 | Method and device for network service account transaction, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110599184A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111210217A (en) * | 2020-01-02 | 2020-05-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108596578A (en) * | 2018-04-25 | 2018-09-28 | 合肥上城信息技术有限公司 | A kind of displaying transaction system and method for integrating virtual equipment in various game |
| CN109432784A (en) * | 2018-11-07 | 2019-03-08 | 四川长虹电器股份有限公司 | A kind of account transaction processing method and device based on block chain |
| CN109493019A (en) * | 2018-11-07 | 2019-03-19 | 四川长虹电器股份有限公司 | A kind of account method of commerce and device based on block chain |
| CN109636362A (en) * | 2018-11-14 | 2019-04-16 | 深圳前海达闼云端智能科技有限公司 | Virtual asset transaction method and device and block chain network node |
-
2019
- 2019-09-30 CN CN201910938359.6A patent/CN110599184A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108596578A (en) * | 2018-04-25 | 2018-09-28 | 合肥上城信息技术有限公司 | A kind of displaying transaction system and method for integrating virtual equipment in various game |
| CN109432784A (en) * | 2018-11-07 | 2019-03-08 | 四川长虹电器股份有限公司 | A kind of account transaction processing method and device based on block chain |
| CN109493019A (en) * | 2018-11-07 | 2019-03-19 | 四川长虹电器股份有限公司 | A kind of account method of commerce and device based on block chain |
| CN109636362A (en) * | 2018-11-14 | 2019-04-16 | 深圳前海达闼云端智能科技有限公司 | Virtual asset transaction method and device and block chain network node |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111210217A (en) * | 2020-01-02 | 2020-05-29 | 腾讯科技（深圳）有限公司 | Data processing method, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11956243B2 (en) | Unified identity verification | |
| US11546332B2 (en) | User ID codes for online verification | |
| US20210065267A1 (en) | Eligibility for access to restricted goods and services using zero-knowledge proofs | |
| US20180357683A1 (en) | Rating data management | |
| US11050749B2 (en) | Credential storage manager for protecting credential security during delegated account use | |
| US11568401B2 (en) | Digital payment system | |
| US20150262151A1 (en) | Access Control System for Online Content | |
| CN104254862A (en) | Content purchasing | |
| WO2015116998A2 (en) | Electronic transfer and obligation enforcement system | |
| KR20130084671A (en) | Application usage policy enforcement | |
| US20230108366A1 (en) | Systems for encryption using blockchain distributed ledgers | |
| US20230298001A1 (en) | Non-fungible token (nft) purchase and transfer system | |
| CN117616410A (en) | Multiparty computing in a computer slicing environment | |
| JP6434086B1 (en) | Real estate brokerage system having real estate brokerage setting function, real estate brokerage method, and real estate brokerage program | |
| JP2021505049A (en) | Payment card verification | |
| CN110599184A (en) | Method and device for network service account transaction, server and storage medium | |
| JP2023510320A (en) | Systems and Methods for Secure Peer-to-Peer Transmission of Content in Distributed Ledger Networks | |
| US20240015030A1 (en) | Methods and systems for authorizing transactions based on a derived public key | |
| CN110689412A (en) | Method, device, server and storage medium for game virtual article transaction based on block chain | |
| CN110599176A (en) | Data processing method and device based on block chain, storage medium and node equipment | |
| KR20200119671A (en) | method of distributing digital content by the amount of issuance, server performing the method, and computer program | |
| CN115131034A (en) | Block chain-based rights and interests digital collection verification method and equipment | |
| JP2019040621A (en) | Transaction mediation system, transaction mediation method, and transaction mediation program | |
| KR20230052782A (en) | Method and apparatus for managing digital object ownership | |
| KR102205765B1 (en) | Method And Apparatus for Providing Wallet for Enhancing Security And keeping Crypto-currency |
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 |