CN110351284B

CN110351284B - Resource sharing method, resource sharing device, storage medium and equipment

Info

Publication number: CN110351284B
Application number: CN201910641630.XA
Authority: CN
Inventors: 汤晨韵; 苏凌枫; 石琳; 武敦亮; 侯维苇; 王子豪; 杨小伟
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2018-01-31
Filing date: 2018-01-31
Publication date: 2021-01-15
Anticipated expiration: 2038-01-31
Also published as: CN108322465A; CN108322465B; CN110351284A

Abstract

The application relates to a resource sharing method, a resource sharing device, a storage medium and equipment, wherein the method comprises the following steps: displaying the resource sharing entry when playing the resource request media data in the social session; entering a resource sharing page from a resource sharing entry for resource sharing; acquiring a current login user identifier as a resource sharing party identifier; acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data; correspondingly sending the resource request media data identification, the session identification, the resource sharing party identification, the resource requesting party identification and the resource sharing share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by the block chain nodes. The scheme provided by the application improves the resource sharing efficiency and ensures the safety and reliability of resource sharing.

Description

Resource sharing method, resource sharing device, storage medium and equipment

The present application is a divisional application entitled "resource sharing, requesting, processing method, apparatus, storage medium, and device" filed by the chinese patent office on 31/1/2018 with application number 2018100989731, the entire contents of which are incorporated herein by reference.

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a resource sharing method, a resource sharing apparatus, a storage medium, and a device.

Background

With the development of computer technology, people can share resources not only in a offline manner but also in a network through a terminal. The shared resources include, but are not limited to, virtual red packs, electronic coupons, loyalty coupons, points, electronic vouchers, gaming chips, virtual items, and the like.

However, in the process of sharing resources through a network, a terminal needs to enter a session interface first, then a toolbar is expanded in the session interface, and then enters a resource sharing interface according to a tool item in the toolbar, so that resource sharing can be set for resource sharing, and the process is complicated, so that the resource sharing efficiency is low.

Disclosure of Invention

Therefore, it is necessary to provide a resource sharing method, a resource requesting method, a resource processing method, a resource sharing apparatus, a resource requesting method, a resource processing apparatus, a storage medium, and a resource sharing device, which are directed to the problem that the resource sharing efficiency is low at present.

A method of resource sharing, comprising:

displaying the resource sharing entry when playing the resource request media data in the social session;

entering a resource sharing page from the resource sharing entry for resource sharing;

acquiring a current login user identifier as a resource sharing party identifier;

acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data;

correspondingly sending the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier and the resource sharing share to a plurality of block link points to generate resource sharing records;

the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by each block chain node.

A resource sharing apparatus, comprising:

the display module is used for displaying the resource sharing entrance when the media data of the resource request is played in the social conversation;

the sharing module is used for entering a resource sharing page from the resource sharing entry to share the resource;

the verification module is used for acquiring the current login user identification as the resource sharing party identification; acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data; correspondingly sending the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier and the resource sharing share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by each block chain node.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of:

According to the resource sharing method, the resource sharing device, the storage medium and the computer equipment, the resource sharing entrance is displayed when the resource request media data are played in the social session, and the resource can be locally and directly shared by entering the resource sharing page through the entrance, so that the resource sharing efficiency is improved. Because the resource sharing information is also recorded in the blockchain, the resource sharing result can be detected through the recorded resource sharing record in the blockchain when being tampered, and the safety and the reliability of resource sharing are ensured.

Drawings

FIG. 1 is a diagram of an application environment of a resource sharing method in one embodiment;

FIG. 2 is a flow diagram illustrating a method for resource sharing in one embodiment;

FIG. 3 is a diagram of a social session interface in one embodiment;

FIG. 4 is a diagram illustrating an interface for playing media data requested by a resource in one embodiment;

FIG. 5 is a schematic diagram of an interface of a resource sharing page in one embodiment;

FIG. 6 is a schematic diagram of a payment interface in one embodiment;

FIG. 7 is a diagram illustrating an interface of a social session in another embodiment;

FIG. 8 is a timing diagram illustrating terminal interaction with a server in one embodiment;

FIG. 9 is a timing diagram of terminal interaction with a server in another embodiment;

FIG. 10 is a diagram illustrating a resource sharing result view portal, under an embodiment;

FIG. 11 is a diagram illustrating resource sharing results in one embodiment;

FIG. 12 is an interface diagram that illustrates a list of social sessions, in one embodiment;

FIG. 13 is a diagram of a social session interface in another embodiment;

FIG. 14 is a schematic diagram of a media data recording interface in accordance with one embodiment;

FIG. 15 is a schematic diagram of a media data recording interface in accordance with another embodiment;

FIG. 16 is a diagram illustrating a media data recording interface according to another embodiment;

FIG. 17 is a flowchart illustrating a method for requesting resources according to one embodiment;

FIG. 18 is a diagram of a social session interface in another embodiment;

FIG. 19 is a diagram illustrating an interface for playing media data requested by a resource in another embodiment;

FIG. 20 is a diagram illustrating an interface for requesting media data from a playback resource in accordance with another embodiment;

FIG. 21 is a diagram illustrating resource sharing result display in accordance with another embodiment;

FIG. 22 is a diagram illustrating resource sharing result display in accordance with another embodiment;

FIG. 23 is a timing diagram of terminal interaction with a server in another embodiment;

FIG. 24 is a flowchart illustrating a resource request method according to another embodiment;

FIG. 25 is a flowchart illustrating a method for resource handling in one embodiment;

FIG. 26 is a block diagram of a resource sharing apparatus in accordance with one embodiment;

FIG. 27 is a block diagram of a resource sharing apparatus according to another embodiment;

FIG. 28 is a block diagram of a resource request device in one embodiment;

FIG. 29 is a block diagram showing a construction of a resource request apparatus in another embodiment;

FIG. 30 is a block diagram showing a construction of a resource request apparatus in another embodiment;

FIG. 31 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

FIG. 1 is a diagram of an application environment of a resource sharing method in one embodiment. Referring to fig. 1, the resource sharing method is applied to a resource sharing system. The resource sharing system includes a terminal 110 and a server 120. The terminal 110 includes at least a first terminal 111 and a second terminal 112. The first terminal 111 may be configured to receive the resource request message sent by the second terminal 112, so as to execute the resource sharing method. The first terminal 111 may also be configured to send a resource request message to the second terminal 112, and the second terminal 112 executes the resource sharing method. In one embodiment, the resource request method may also be used in the application environment shown in FIG. 1. The terminal sending the resource request message is used for executing the resource request method. The terminal 110 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The server 120 may be an independent server, or may be a server cluster formed by a plurality of independent servers. When the server 120 is a server cluster composed of a plurality of independent servers, it may include a resource management server, a storage server, a message management server, and the like.

It will be understood that, as used herein, the terms "first" and "second," etc. may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, the first terminal and the second terminal are both terminals, but they are not the same terminal.

Fig. 2 is a flowchart illustrating a resource sharing method according to an embodiment. The embodiment is mainly illustrated by applying the method to the first terminal 111 in fig. 1. Referring to fig. 2, the resource sharing method specifically includes the following steps:

s202, receiving a resource request message in the social session.

Wherein the social session is an interactive process between at least one member and other members. The users can log in the social application through the social account number and then perform social conversation. The resource request message is used for requesting to acquire a resource message. The resource request message may be a message body generated according to a preset message format.

Specifically, the first terminal can establish a social session with a second user identifier logged in the second terminal through a first user identifier logged in locally. In this way, when the first terminal is connected with the second terminal in a peer-to-peer manner, the first terminal may directly receive the resource request message sent by the second terminal in the social session through the peer-to-peer connection, so that the first terminal receives the resource request message in the social session. When the first terminal and the second terminal are connected in a non-point-to-point mode, the first terminal can receive the resource request message forwarded by the server and initiated by the second terminal in the social session, and therefore the first terminal receives the resource request message in the social session. Wherein the user identifier is used for uniquely identifying a user. The user identification may specifically be a social account number of a social application, etc.

S204, the resource request media data corresponding to the resource request message is played.

Wherein the resource request media data is media data for requesting acquisition of a resource. The media data may include at least one of text data, picture data, audio data, or video data. The picture data may include moving picture data and still picture data. The resource request media data may be resource request text, resource request animation, resource request audio, or resource request video, etc.

Specifically, the resource request message may specifically include the resource request media data itself, so that the first terminal may, after receiving the resource request message, automatically or according to a user instruction, obtain and play the resource request media data in the resource request message.

In one embodiment, after receiving the resource request message, the terminal may generate an abbreviated display message corresponding to the resource request message to be displayed in a message container of the social session. And when the terminal detects the triggering operation corresponding to the abbreviated display message, acquiring the resource request media data in the resource request message and playing the resource request media data. The thumbnail display message may be a message content thumbnail generated according to the resource request media data. The trigger operation is a single-click operation, a double-click operation, a touch operation, a slide operation, a multi-touch operation, or the like.

For example, FIG. 3 shows a schematic diagram of a social session interface in one embodiment. Referring to fig. 3, the interface includes a message container 310 of the social conversation, and a message content thumbnail 311 presented in the message container 310 and generated from the resource request media data.

In one embodiment, the resource request media data may not include the resource request media data itself, but include a storage location identifier corresponding to the resource request media data, so that the first terminal may download the resource request media data according to the storage location identifier in the resource request message after receiving the resource request message, thereby automatically playing the resource request media data, or playing the resource request media data according to a user instruction. Wherein the storage location identification is used to identify a storage location on the computer device where the resource request media data is stored. The computer device for storing the resource request media data may be a server, and may specifically be a storage server, and the terminal that generates the resource request media data uploads the resource request media data to the storage server for storage. The storage server may be a server for storing the resource request media data.

In one embodiment, the resource request media data may be original media data, or original media data associated with the decoration element, or media data obtained by fusing the original media data and the decoration element. When the resource request media data is the original media data associated with the decoration element, it can be understood that playing the resource request media data is to correspondingly display the associated decoration element when playing the original media data.

Wherein the decoration element is data for decoration which can be displayed in a visual form. Such as data displayed on a video frame to modify the video content. The decorative elements may be, for example, masks, armors, colored ribbons, blue sky or white clouds, and the type of the decorative elements is not limited in the embodiment of the present invention. The raw media data may be media data that has not been associated or fused with the decoration element after being captured, but does not exclude other processing, such as white balance adjustment of video or pictures.

S206, when the media data of the resource request is played, the resource sharing entrance is displayed.

The resource sharing entry is used for triggering entry into a resource sharing page so as to complete necessary operations for resource sharing. Resource sharing in can be represented in the form of icons, controls, hyperlinks, or buttons. Specifically, the terminal may display the resource sharing entry when playing the resource request media data.

It can be understood that, when the resource request media data is a resource request animation or a resource request video, the first terminal plays the resource request media data, that is, renders the resource request media data on the first terminal view layer to form a picture. In the embodiment of the present invention, the size of the frame is not limited, and the position relationship between the resource sharing entry and the frame is also not limited. For example, the terminal may play the requested video in a full screen mode, and display the resource sharing entry in a certain area of the video picture. For example, FIG. 4 is a diagram illustrating an interface for playing media data requested by a resource in one embodiment. Referring to fig. 4, the interface includes a frame 410 obtained by rendering a view layer when playing a resource request media data, and a resource sharing entry 420 displayed on the frame 410.

S208, detecting the operation of the resource sharing entrance, and entering a resource sharing page.

Specifically, the first terminal detects a predefined operation acting on the resource sharing entry, and if the predefined operation is detected, the first terminal enters a resource sharing page. The resource sharing page can be in the form of a floating layer or a window. Such as a single-click operation, a double-click operation, a touch operation, a slide operation, or a multi-touch operation.

For example, the terminal may detect an operation of the user with respect to the resource sharing portal 420 shown in fig. 4, and enter the page shown in fig. 5 after detecting the operation. FIG. 5 illustrates an interface diagram of a resource sharing page in one embodiment.

S210, obtaining the resource requester ID appointed by the resource request message.

The resource requester identifier is used for identifying a user requesting to acquire the resource or a user requesting to share the resource. The resource requester identity may be a user identity currently logged in when the terminal generates the resource request media data. The resource requester identifier may also be a user identifier of a user that is designated by the terminal to receive the shared resource when generating the resource request media data.

Specifically, the resource request message may include a resource requester identifier, so that the first terminal may obtain the resource requester identifier in the resource request message after receiving the resource request message.

In an embodiment, the second terminal (message sending end) may generate a resource request message of a preset message structure according to a preset message structure and the resource requester identifier; correspondingly, the first terminal (message receiving end) can analyze the resource request message according to the preset message structure, and obtain the resource requester identifier from the resource request message. The preset message structure may adopt a JSON format, an XML format, or other custom message formats.

It is to be understood that, here, S210 is not limited to be executed after S208, and after receiving the resource request message, the first terminal may execute S210 before performing resource sharing on the resource sharing page.

And S212, sharing resources on the resource sharing page according to the resource requester identifier.

Specifically, the resource sharing page may provide one or more configuration items and a confirmation entry for the user to configure resource sharing, and after configuration is completed and confirmed, resource sharing may be performed. The configuration items may include share configuration items configuring shares of the shared resources, or resource category configuration items configuring categories of the shared resources, and the like.

For example, with continued reference to FIG. 5, the interface includes a resource requestor identification 510, a share of the resource 520, a share modification entry 530, and a confirmation entry 540. The user can modify shares of the shared resource through share modification entry 530 and after configuration is complete, confirm the sharing through confirmation entry 540.

Further, after the resource sharing configuration is completed, the first terminal may initiate a payment request corresponding to the configured share, and receive a payment result corresponding to the payment request.

The first terminal may enter the payment page shown in fig. 6, obtain data required for payment, generate a payment request according to the data required for payment, send the payment request to the server or the third-party payment platform, process the payment request by the server or the third-party payment platform, and return a payment result to the first terminal.

Specifically, the first terminal may obtain an account identifier of the payer and a payment amount corresponding to the share, generate a payment request carrying the account identifier of the resource requester, the account identifier of the payer and the payment amount, and send the payment request to the server or the third party payment platform. And the server or the third party payment platform subtracts the payment amount from the payment account corresponding to the payer account identifier according to the payment request, adds the payment amount to the collection account corresponding to the resource requester identifier, completes the payment and returns a result of successful payment to the first terminal. And after the first terminal receives the result of the payment failure, prompting the user of the payment failure and guiding the user to pay again.

In one embodiment, the first terminal may display the resource sharing animation after completing the resource sharing. Such as a red envelope fly-out animation, etc.

In one embodiment, after the first terminal finishes playing the resource request media data, the resource sharing message may be displayed in a message container of the social session. For example, FIG. 7 illustrates an interface diagram of a social session in one embodiment. The interface includes a message container 710 and a resource sharing message 711 shown in the message container 710.

According to the resource sharing method, after the resource request message is received in the social session, the resource request media data corresponding to the resource request message can be played, and the resource sharing entry is displayed when the resource request media data is played, namely, a quick entry for resource sharing is provided when the content of the output message is, so that the resource can be locally and directly shared by entering the resource sharing page through the quick entry, and the resource sharing efficiency is improved. In addition, the received resource request message is assigned with the resource requester identifier, namely, the resource receiver, so that the resource can be shared locally without selecting the resource receiver through additional operation, and the resource sharing efficiency is further improved.

In one embodiment, S204 includes: extracting a storage location identification from the resource request message; and downloading the resource request media data according to the storage position identification and playing the media data. The resource sharing method further comprises the following steps: extracting a first hash value corresponding to the resource request media data from the resource request message; generating a second hash value according to the downloaded resource request media data; and when the first hash value is consistent with the second hash value, executing a step of resource sharing on the resource sharing page according to the resource requester identifier.

The storage location identifier may be a complete storage address for locating the corresponding resource request media data on the server, or may be an identification number of the resource request media data on the server.

The hash value is a value obtained by mapping data from a domain to a smaller domain than the domain using a hash function. Such as MD5(MessageDigestAlgorithmMD5, fifth version of the message digest algorithm) values or SHA (SecureHashAlgorithm) values, etc.

Specifically, the second terminal (message sending end) may obtain, after generating the resource request media data, the currently logged user identifier as a resource requester identifier, generate a first hash value of the resource request media data, and generate the resource request media data identifier according to the resource requester identifier and the first hash value. And the second terminal uploads the resource request media data to the server, so that the server receives the resource request media data and then stores the resource request media data, generates a storage position identifier and feeds the storage position identifier back to the second terminal. And the second terminal generates a resource request message according to the resource request media data identifier and the storage position identifier and sends the resource request message to the first terminal.

Thus, after receiving the resource request message, the first terminal can analyze the resource request message to obtain the resource request media data identifier and the storage location identifier, and analyze the resource request media data identifier to obtain the resource requester identifier and the first hash value. The first terminal downloads the resource request media data according to the storage position identification and plays the media data.

Further, the first terminal generates a second hash value according to the downloaded resource request media data, and compares the second hash value with the first hash value obtained by analysis. And when the first hash value is consistent with the second hash value, judging that the downloaded resource request media data is consistent with the resource request media data corresponding to the resource request message, and executing a step of resource sharing on a resource sharing page according to the resource requester identifier. When the first hash value is inconsistent with the second hash value, the downloaded resource request media data is judged to be inconsistent with the resource request media data corresponding to the resource request message, the resource request message may be tampered, and in order to avoid resource sharing errors, subsequent operations of resource sharing are not executed.

In this embodiment, after receiving the resource request message, the local device downloads the resource request media data according to the storage location identifier in the resource request message, and generates a hash value corresponding to the downloaded resource request media data; and then, a hash value corresponding to the resource request media data is extracted from the resource request message, whether resource sharing is continued or not is determined through consistency check of the two hash values locally, and subsequent operation is continued only when the two hash values are consistent, so that the resource sharing safety is ensured to a certain extent.

FIG. 8 shows a timing diagram of terminal interaction with a server in one embodiment. Referring to fig. 8, after the second terminal generates the resource request media data, it locally identifies UIN (currently logged-in user identifier) and hash value MD5 of the resource request media data according to the resource requester₁Generating a resource request media data identifier MID of the resource request media data; the resource request media data is then uploaded to the server. And after the server finishes storing the resource request media data, returning the storage position identifier UUID of the resource request media data. And the second terminal generates a resource request message according to the MID and the UUID and sends the resource request message to the server, and the resource request message is forwarded to the first terminal by the server.

After receiving the resource request message, the first terminal analyzes the resource request message to obtain the UIN and the MD5₁And UUID, downloading the resource request media data from the server according to the UUID, and generating a hash value MD5 of the downloaded resource request media data₂Checking MD5 locally₁And MD5₂At MD5₁And MD5₂And when the resource sharing is consistent, judging that the verification is passed so as to carry out subsequent resource sharing. At MD5₁And MD5₂And when the resource sharing is inconsistent, judging that the verification is not passed and not carrying out subsequent resource sharing.

In one embodiment, S204 includes: extracting a storage location identification from the resource request message; and downloading the resource request media data from the server according to the storage position identification and playing the media data. Acquiring the resource requester identifier specified by the resource request message, including: extracting a ciphertext from the downloaded resource request media data; the ciphertext is obtained by encrypting the resource request media data identifier corresponding to the resource request media data; sending the extracted ciphertext to a server; and receiving the resource request party identifier returned by the server after the check ciphertext passes.

Specifically, the second terminal (message sending end) may obtain, after generating the resource request media data, the currently logged user identifier as a resource requester identifier, generate a hash value of the resource request media data, and generate the resource request media data identifier according to the resource requester identifier and the hash value. The second terminal can obtain a ciphertext after encrypting the resource request media data identifier, and directly stores the ciphertext in the resource request media data and uploads the ciphertext to the server, so that the server receives the resource request media data and then stores the resource request media data and generates a storage position identifier to feed back the storage position identifier to the second terminal. For example, when the media data requested by the asset is a video file, the ciphertext may be stored in an attribute of the video file (i.e., the metadate field in the MP4 format).

And the second terminal generates a resource request message according to the ciphertext and the storage position identifier, sends the resource request message to the server, and forwards the resource request message to the first terminal by the server. When the server forwards the resource request message, the ciphertext in the resource request message is cached on the server.

Therefore, after receiving the resource request message, the first terminal can analyze the resource request message to obtain the storage position identification, and then download the resource request media data according to the storage position identification. The first terminal then analyzes the downloaded resource request media data to obtain a ciphertext stored in the resource request media data, and sends the ciphertext obtained by analysis to the server.

And after receiving the ciphertext, the server compares the received ciphertext with the cached ciphertext. When the server has a ciphertext which is consistent with the received ciphertext, judging that the ciphertext is valid, continuously decrypting the received ciphertext and the cached ciphertext which is consistent with the ciphertext, and when the hash values of the ciphertext and the received ciphertext after decryption are consistent, judging that the downloaded resource request media data are consistent with the resource request media data corresponding to the resource request message, and feeding back a resource requester identifier obtained by decrypting the ciphertext to the first terminal, so that the first terminal can continuously perform candidate resource sharing operation. When the ciphertext consistent with the received ciphertext is not cached or the hash value included after the consistent ciphertext is decrypted is consistent, the downloaded resource request media data is judged to be inconsistent with the resource request media data corresponding to the resource request message, the resource request message may be tampered, and in order to avoid resource sharing errors, the resource requester identifier obtained by decrypting the ciphertext is not fed back to the first terminal, so that the first terminal cannot continue to perform subsequent resource sharing.

The terminal can use the asymmetric public key to encrypt the resource request media data identifier, and the server uses the asymmetric private key to decrypt. The private key is only stored on the server and is used for ensuring data security. In other embodiments, other checking algorithms, such as parity checking, Cyclic Redundancy Check (CRC), etc., may be used.

In this embodiment, after receiving the resource request message, the local device downloads the resource request media data according to the storage location identifier in the resource request message, and analyzes to obtain a ciphertext included in the downloaded resource request media data; and uploading the ciphertext to a server for inspection, and obtaining the resource requester identifier for subsequent resource sharing when the verification is passed, so that the security of resource sharing is ensured to a certain extent.

FIG. 9 shows a timing diagram of terminal interaction with a server in one embodiment. Referring to fig. 9, after the second terminal generates the resource request media data, it locally identifies UIN (currently logged-in user identifier) and hash value MD5 of the resource request media data according to the resource requester₁And generating a resource request media data identifier MID of the resource request media data, encrypting the MID by using a public key, storing the encrypted MID on the resource request media data, and uploading the resource request media data to a server. Server storing resource requestAnd after the media data is solved, returning the storage position identifier UUID of the media data requested by the resource. The second terminal generates a resource request message according to the encrypted MID and UUID, sends the resource request message to the server, and forwards the resource request message to the first terminal by the server. The server may cache the MID when forwarding the resource request message.

The first terminal analyzes the resource request message to obtain encrypted MID and UUID after receiving the resource request message, downloads the resource request media data from the server according to the UUID, and extracts the encrypted MID from the downloaded resource request media data₂Encrypted MID₂And uploading to a server for verification. The server finds the MID cached and encrypted₂When the MIDs are consistent, the encrypted MIDs are judged₂And if the two are valid, continuously comparing whether the MD5 is consistent or not after decrypting the two, and judging that the verification is carried out through feeding back the UIN to the first terminal for subsequent resource sharing when the MD5 is consistent. In the MID for finding and encryption₂And when the consistent MID or the two obtained MDs 5 after decryption are inconsistent, judging that the verification fails and feeding back the UIN no longer to finish resource sharing.

In one embodiment, S212 includes: acquiring shares configured on a resource sharing page; generating a resource sharing message according to the resource requester identifier and the share; sending a resource sharing message in a social session; and updating the resource sharing entry into a resource sharing result viewing entry.

The resource sharing entry is used for triggering resource sharing operation. And the resource sharing result viewing entry is used for triggering the viewing of the resource sharing result. The resource sharing message is used for triggering the action of acquiring the resource. Specifically, the first terminal may generate the resource sharing message according to the resource sharing message template, the resource requester identifier, and the share, so that the generated resource sharing message has a function of acquiring the resource corresponding to the share.

For example, FIG. 10 shows a diagram that illustrates a resource sharing result view portal, in one embodiment. Referring to fig. 10, the interface renders a screen 1010 obtained by rendering a view layer when playing the resource request media data, and a resource sharing result viewing entry 1020 displayed on the screen 1010. It can be understood that after the payment interface shown in fig. 6 is completed, that is, resource sharing is completed, that is, the interface shown in fig. 10 is jumped to, at this time, the resource sharing entry is no longer displayed, but the resource sharing result viewing entry is displayed.

In this embodiment, after the resource sharing is completed, the resource sharing entry is updated to the resource sharing result viewing entry, and the user can view the resource sharing result through the resource sharing result viewing entry to know the resource sharing process.

In one embodiment, the resource sharing method further includes: detecting a trigger operation on a resource sharing result viewing entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

Specifically, the first terminal detects a predefined operation acting on the resource sharing result viewing entry, and sends a session identifier of a current social session, a resource request media data identifier of currently played resource request media data, and a resource requester identifier to the server if the predefined operation is detected. The server can search share of shared resources corresponding to the session identifier, the resource request media data identifier and the resource requester identifier. The first terminal thus presents the obtained shares. Wherein the predefined operation is a single click operation, a double click operation, a touch operation, a slide operation or a multi-touch operation.

The data fed back to the first terminal by the server may further include other resource sharing party identifiers. When the first terminal is displaying, the resource sharing party identifier and the share of the shared resource through the resource sharing party identifier can be correspondingly displayed. The first terminal can also collect the shares to obtain the total share of the resource obtained by the resource requester identification. In the embodiment of the present invention, how the share of the shared resource is displayed is not limited.

For example, when the current session is a group session, the data fed back to the first terminal by the server may be members sharing resources for the resource requester corresponding to the resource request media data in the group session, and shares shared by the members.

It can be understood that session isolation and resource request media data isolation are performed on the resource sharing result in the embodiment. That is to say, when the resource request messages corresponding to the same resource request media data are sent in different social sessions, when the member belonging to one of the social sessions views the resource sharing result corresponding to the resource request media data, the member belonging to the current social session can only view the share of the resource requester shared resource corresponding to the resource request media data. If the resource requests that the media data is sent in the social session for multiple times, the resource sharing result may be a result of summarizing shares of the resource shared by multiple messages, or a result of summarizing shares of the resource shared by a single message.

It will also be appreciated that the resource request message may be forwarded, but the resource requestor identity does not change from one user identity to another through which the forwarding is passed. The resource requestor identity is always the resource requestor identity specified by the forwarded original resource request message. The resource requester identifier may specifically be an identifier of a producer of the resource request media data, or may also be a user identifier specified by the producer of the resource request media data.

For example, fig. 11 shows a schematic diagram of resource sharing result presentation in one embodiment. Referring to FIG. 11, the interface includes a resource requestor identification 1110, a total share of the resource 1120, a resource sharer identification 1130, and shares shared by resource sharers 1140.

In this embodiment, after the resource sharing is completed, the resource sharing result can be checked through the resource sharing result checking entry, and the resource sharing process can be known in real time. Moreover, the viewed resource sharing result is only the share of the shared resource in the current social session corresponding to the resource request media data and according to the resource requester identifier, on one hand, only the data related to the currently viewed user is displayed, so that the privacy and the security of other data are ensured, and the content which the currently viewed user does not want to view is prevented from being displayed too much.

In one embodiment, the resource sharing method further includes: acquiring a current login user identifier as a resource sharing party identifier; acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data; correspondingly sending the resource request media data identification, the session identification, the resource sharing party identification, the resource requesting party identification and the share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by the block chain nodes.

The block chain nodes are distributed computer nodes for data recording. The plurality of block chain nodes may belong to the same block chain or may belong to different block chains. The resource sharing record is the saved resource sharing event details. For example, the resource sharing record indicates that the user a transfers the resource to the user D through the resource request message corresponding to the resource request media data C in the social session B, and the share of the transferred resource is D.

Specifically, after receiving a resource sharing success notification fed back by a server, a first terminal can acquire a currently logged-in user identifier as a resource sharing party identifier, acquire a session identifier corresponding to a social session and a resource request media data identifier corresponding to resource request media data, and correspondingly transmit the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier and shares to a plurality of block link points to generate resource sharing records. That is, the resource sharing result is determined to be accurate only when the resource sharing records generated by the link points of each block are consistent.

In this embodiment, since the resource sharing information is also recorded in the blockchain, the resource sharing result can be detected through the recorded resource sharing record in the blockchain even when the resource sharing result is tampered, so that the security and reliability of resource sharing are ensured.

It is to be understood that the above steps of correspondingly sending the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier, and the share to the plurality of block link points to generate the resource sharing record may also be executed by the server.

Further, in order to ensure the security of data storage on the blockchain node, the operation authority of storing data on the blockchain node, such as only reading and writing, can be limited, and cannot be modified.

In one embodiment, S212 includes: inquiring a resource identifier appointed by the resource request media data during generation; acquiring a resource corresponding to the resource identifier; and sharing the acquired resources on the resource sharing page according to the resource requester identifier.

Wherein the resource identifier is used for uniquely identifying one resource. A resource is an item that can acquire ownership over a network. Resources can be classified into virtual resources and physical resources according to attributes. Virtual resources such as account numbers, avatar products, virtual rechargeable cards, gaming accessories, virtual currency, and the like. The entity resource can be any article with a practical form, such as an electronic product, a toy, an artwork or a signature photo, which can be owned by a user.

Specifically, the second terminal (message sending end) may specify a resource identifier corresponding to a resource requested to be shared when generating the resource request media data, and generate a resource request message according to the resource request media data and send the resource request message to the first terminal. Therefore, after receiving the resource request message, the first terminal can query the resource identifier specified by the resource request media data during generation, so as to obtain the resource corresponding to the resource identifier, and share the obtained resource on the resource sharing page according to the identifier of the resource requester.

The resource identifier specified during the generation of the resource request media data may be one or more, and when the specified resource identifiers are multiple, the first terminal may determine the resource identifier selected through a user instruction, and share the resource corresponding to the resource identifier to the resource requester.

The second terminal (message sending end) specifies the resource identifier corresponding to the resource requested to be shared when generating the resource request media data, which may be specified by voice. For example, the media data requested at the recording resource is recorded voice data "i take ten QQ coins". The second terminal (message sending end) specifies a resource identifier corresponding to the resource requested to be shared when generating the resource request media data, and may add the resource identifier in the video picture. Such as adding a resource picture, a resource name, or a resource purchase link to the video frame. The second terminal (message sending end) specifies the resource identifier corresponding to the resource requested to be shared when generating the resource request media data, or associates the specified resource identifier after generating the resource request media data.

In this embodiment, the resource requesting party may specify the requested resource identifier when generating the resource request media data, so that the resource sharing party may directly share the resource requested by the resource requesting party to the other party in the current social session, thereby improving the resource sharing efficiency.

In one embodiment, the generating of the resource request media data comprises: detecting a trigger operation acting on a media data recording entrance; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

Specifically, the terminal may display the media data recording entry in a session interface corresponding to the social session, or may display the media data recording entry in a social session list interface, where a display position of the media data recording entry is not limited. The media data recording entry is used for triggering the media data recording resource sharing configuration to be carried out and can be represented in the form of an icon, a hyperlink or a button.

In one embodiment, the second terminal may display a media data recording entry in a message container of the social session after receiving the resource request message; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

For example, after receiving the resource request message, the terminal may generate an abbreviated display message corresponding to the resource request message to display in a message container of the social session. Wherein the abbreviated presentation message may include a media data recording entry. The terminal may detect an action on the media data recording entry to continue to perform the step of generating the resource request media data when the trigger operation is detected. For example, referring again to fig. 3, the interface also includes a media data recording portal 312.

In this embodiment, a fast entry for recording media data is provided in a message container of a social session, so that the resource sharing efficiency can be further improved.

In one embodiment, the second terminal may generate the resource request media data according to the user instruction, regardless of whether the resource request message is received, so that the second terminal may also generate the resource request message according to the generated resource request media data to request to acquire the resource.

For example, the terminal may display a media data recording entry 1201 on the social session list interface shown in fig. 12, call up a presentation toolbar 1202 through the media data recording entry 1201, present a jump entry 1203 in the toolbar 1202, and jump to a media data recording page shown in fig. 14 through the jump entry 1203. The terminal may also display a media data recording entry 1301 in a session interface corresponding to the social session shown in fig. 13, and directly jump to a media data recording page shown in fig. 14 through the media data recording entry 1301.

Further, the terminal may detect a trigger operation applied to the media data recording entry, and enter the media data recording page after detecting the trigger operation. The terminal can specifically display the decoration element identifier list display triggering control in the page, when the operation of the decoration element identifier list display triggering control is detected, the decoration element identifier list is triggered to be displayed, and after the selection operation of the decoration element identifier list is received, the decoration element identifier is selected according to the selection operation. Referring to FIG. 14, the interface includes a decorative element identification list presentation trigger control 1401. When the terminal detects the operation of the decoration element identification list display trigger control, the terminal enters an interface shown in fig. 15 to display a decoration element identification list 1501.

And the terminal receives a media data acquisition instruction after the decoration element identifier is selected according to the selection operation. After receiving the media data acquisition instruction, an image acquisition device such as a camera is called to acquire an image frame sequence to obtain video data, or a sound acquisition device such as a microphone is called to acquire environmental sound to obtain audio data. The user can speak or use other vocalizable instruments to make sound, so that the sound collection device collects the voice of the user or other sounds made by the user.

When the terminal collects the video data, the decoration elements corresponding to the decoration element identifications selected according to the selection operation can be correspondingly displayed. And correspondingly displaying the decoration elements, namely controlling the decoration elements to synchronously and dynamically move along with corresponding reference objects in the video acquisition interface. The corresponding reference object of the decoration element is the object for decoration of the decoration element. For example, the reference object corresponding to the head decoration element is the image head area. And correspondingly displaying the head decoration element, namely controlling the head decoration element to synchronously and dynamically move along with the image head area in the video acquisition interface.

Further, a user can touch the position of the touch display screen of the terminal, where the media data acquisition trigger control is displayed, to trigger the media data acquisition instruction, the user keeps pressing the media data acquisition trigger control, and the user triggers the acquisition stop instruction when the pressing of the media data acquisition trigger control is cancelled. Or, the user can touch the position of the media data acquisition triggering control displayed on the touch display screen of the mobile phone once to trigger the media data acquisition instruction, and the user touches the touch display screen again to trigger the acquisition stopping instruction. By way of example, fig. 16 shows a schematic diagram of a media data recording interface in one embodiment, which includes a media data capture trigger control 1610.

When the terminal records the media data, the resource request media data can be generated according to the media data and the decoration elements. Specifically, when the terminal records video data, the collected image frames and the correspondingly displayed decorative elements can be fused to generate resource request image frames, so that resource request video data are formed. The terminal can also fuse the decoration elements with the collected image frames frame by frame to obtain the resource request media data after the media data recording is finished. If the terminal records only audio data, the decoration element can be associated with the audio data so as to display the decoration element when the audio data is played.

In one embodiment, the media data recording page may provide a message sending entry, and the terminal may detect a trigger operation acting on the message sending entry, to generate a resource request message according to the generated resource request media data after detecting the trigger operation, and send the resource request message in the current social session; the user can also jump to a social session selected page to select a social session so as to send the resource request message, or a social session is newly established in the social session selected page so as to send the resource request message.

In the above embodiment, the user can record the media data to generate the resource request media data while selecting the decoration element, so that the message receiving end can play the recorded media data and display the decoration element after receiving the resource request message generated according to the resource request media data. Therefore, the message sent by the user at one time can not only transmit the information expressed by the decorative element, but also transmit the information transmitted by the media data, so that the information quantity which can be transmitted by sending the message at one time is increased, and the efficiency of resource request and resource sharing is improved.

In one embodiment, playing the resource request media data corresponding to the resource request message includes: extracting a decoration element identifier and a storage position identifier from the resource request message; acquiring decorative elements corresponding to the decorative element identifiers; downloading the media data of the resource request according to the storage position identification; and playing the media data requested by the resource and correspondingly displaying the decorative elements.

Specifically, the resource request media data corresponding to the resource request message may be media data that is not fused with the decoration element. The second terminal (message sending end) can encapsulate the decoration element identifier and the storage position identifier in the resource request message, so that the first terminal can extract the decoration element identifier and the storage position identifier from the resource request message, then acquire the decoration element corresponding to the decoration element identifier, and download the resource request media data according to the storage position identifier.

Therefore, the first terminal can correspondingly display the decorative elements when playing the media data requested by the resource. Wherein, when the media data of the resource request is audio data, the decorative elements can be directly displayed. When the media data of the resource request is video data, the decoration elements are controlled to move dynamically in the video pictures synchronously with the corresponding reference objects.

In this embodiment, it is not necessary to fuse the recorded media resource and the decoration element to form new media data, and the decoration element identifier is specified when the resource request message is sent, so that the workload of data processing is reduced, and the efficiency of resource request and resource sharing is improved.

FIG. 17 is a flowchart illustrating a method for requesting resources according to an embodiment. The embodiment is mainly illustrated by applying the method to the second terminal 112 in fig. 1. Referring to fig. 17, the resource request method specifically includes the following steps:

s1702, acquiring the current login user identifier as the resource requester identifier.

Specifically, the second terminal may read a currently logged-in user identifier, and use the user identifier as a resource requester identifier. The second terminal may obtain a user identifier specified by the user instruction, and use the user identifier as the resource requester identifier.

S1704, the resource request media data is obtained.

Specifically, the second terminal may select one resource request media data from the resource request media data recorded in advance, or may record the media data in real time to generate the resource request media data.

S1706, a resource request message is generated according to the resource request party identification and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier.

Specifically, the second terminal may directly generate the resource request message according to the resource requester identifier and the resource request media data, where the resource request message thus generated includes the resource request media data itself, so that the first terminal may play the resource request media data after receiving the resource request message, and share the resource according to the resource requester identifier. The second terminal can also upload the generated resource request media data to the server to obtain the storage position identification of the resource request media data fed back by the server, and the second terminal generates the resource request message according to the resource requester identification and the storage position identification, so that the first terminal can download and play the resource request media data according to the storage position identification after receiving the resource request message, and share the resource according to the resource requester identification.

For example, the first terminal may splice information such as the identifier of the resource requesting party, the MD5 value of the resource request video, and the sending time of the video as the resource request video ID, then upload the resource request video to the server for storage, receive the storage location identifier UUID returned by the server, and then generate and send the resource request message according to the resource request video ID and the storage location identifier UUID.

The server stores the resource request media data with timeliness, and deletes the resource request media data to balance the storage space after the storage reaches a certain time. Therefore, the server can manage the stored media data of each resource request according to the sending time and delete the expired media data of the resource request after the cache deadline is reached.

S1708, sending the resource request message in a social session.

Specifically, the second terminal may send the resource request message in the social session, and after sending the resource request message, may generate an abbreviated presentation message corresponding to the resource request message to be presented in a message container of the social session. The thumbnail display message may be a message content thumbnail generated according to the resource request media data. For example, FIG. 18 shows a schematic diagram of a social session interface in one embodiment. Referring to fig. 18, the interface includes a message container 1810 of the social conversation, and a message content thumbnail 1811 presented in the message container 1810 and generated from the resource request media data.

S1710, playing the resource request media data, and displaying a resource sharing result viewing entry; and the resource sharing result viewing entry is used for triggering the result of displaying the shared resource.

In particular, the second terminal may detect a predefined operation, such as detecting a trigger operation corresponding to the abbreviated presentation message. And when the second terminal detects the predefined operation, playing the resource request media data corresponding to the resource request message, and displaying the resource sharing result viewing entry. The trigger operation is a single-click operation, a double-click operation, a touch operation, a slide operation, a multi-touch operation, or the like.

For example, FIG. 19 shows a schematic interface diagram for playing the asset request media data in one embodiment. Referring to fig. 19, the interface includes a screen 1910 obtained by rendering the view layer when the resource requests media data, and a resource sharing result viewing entry 1920 displayed on the screen 1910.

According to the resource request method, after the user identification and the resource request media data which are logged in at present are obtained, the user identification can be used as the resource request party identification, and the resource request message is generated according to the resource request party identification and the resource request media data and then sent. The resource request message designates the resource requester identifier, namely the resource receiver, so that the message receiving end can share the resource without selecting the resource receiver through additional operation, and the resource sharing efficiency is improved. And the local can also play the media data of the resource request, and display the resource sharing result viewing entry, so that the resource sharing result is triggered to be viewed through the resource sharing result viewing entry, and the resource request and the resource sharing dynamic are known in real time.

In one embodiment, the second terminal may receive the resource sharing message fed back by the server, display the resource sharing message in a message container of the social session, and retrieve the resource according to the resource sharing message. And the second terminal shares the resource with the resource requester identifier through the logged-in resource sharing identifier. When the social conversation is a group conversation, the resource request party identification correspondingly has the authority of getting the resource according to the resource sharing message.

In one embodiment, obtaining resource request media data comprises: detecting a trigger operation acting on a media data recording entrance; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

It can be understood that the process of generating the media data for the resource request in this embodiment is described in the foregoing embodiment, and therefore is not described herein again.

In one embodiment, S1710 includes: playing the resource request media data; when a resource sharing message corresponding to the resource request message is not received, directly displaying a resource sharing result viewing entry; and when a resource sharing message corresponding to the resource request message is received, adding a resource request success decoration element in the displayed resource sharing result viewing entry.

Wherein the resource request success decoration element is a decoration element for indicating that the resource request is successful. Whether the resource request is successful or not is reflected in a visual mode through the existence of the successful decoration element of the resource request.

For example, when a resource sharing message corresponding to the resource request message is not received, the resource sharing result viewing entry is directly displayed, that is, the user interface UI of the resource sharing result viewing entry 1920 shown in fig. 19 may be an empty red envelope. When a resource sharing message corresponding to the resource request message is received, a resource request success decoration element is added in the displayed resource sharing result viewing entry as shown in fig. 20. At this time, the user interface UI of the resource sharing result viewing portal 2020 may be a red envelope filled with gold ingots.

In the embodiment, the resource sharing result viewing entry is added with the resource request success decoration element to remind the user of the resource, so that the timeliness of the user obtaining the resource request success message is improved.

In one embodiment, the resource request method further comprises: detecting a trigger operation acting on a resource sharing result viewing entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

Specifically, the second terminal detects a predefined operation acting on the resource sharing result viewing entry, and sends the session identifier of the current social session, the resource request media data identifier of the currently played resource request media data, and the resource requester identifier to the server if the predefined operation is detected. The server can search share of shared resources corresponding to the session identifier, the resource request media data identifier and the resource requester identifier. The second terminal thus presents the obtained shares. Wherein the predefined operation is a single click operation, a double click operation, a touch operation, a slide operation or a multi-touch operation.

The data fed back to the second terminal by the server may further include other resource sharing party identifiers. When the second terminal is displaying, the resource sharing party identifier and the share of the shared resource through the resource sharing party identifier can be correspondingly displayed. The second terminal can also collect the shares to obtain the total share of the resource obtained by the resource requester identification. In the embodiment of the present invention, how the share of the shared resource is displayed is not limited.

For example, the terminal may detect an operation performed on the resource sharing result viewing portal 1920 and enter an interface as shown in fig. 21. Since the user does not receive the resources shared by other users at this time, the share of the shared resources is zero. The terminal may detect an operation on the resource sharing result viewing portal 2020 and enter an interface as shown in fig. 22. At this time, if the user receives the resource shared by other users, the interface includes a resource requester identifier 2210, a total share of the shared resource 2220, a resource sharer identifier 2230, and shares shared by resource sharers 2240.

In this embodiment, after the resource request is sent, the resource sharing result can be checked through the resource sharing result checking entry, and the resource sharing process can be known in real time. Moreover, the viewed resource sharing result is only the share of the shared resource in the current social session corresponding to the resource request media data and according to the resource requester identifier, on one hand, only the data related to the currently viewed user is displayed, so that the privacy and the security of other data are ensured, and the content which the currently viewed user does not want to view is prevented from being displayed too much.

In one embodiment, after receiving the resource sharing message, the second terminal may display the resource sharing message in a message container of the social session, and retrieve the resource according to the resource sharing message.

It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the sub-steps or the stages of other steps.

FIG. 23 is a timing diagram that illustrates interactions between a terminal and a server, according to one embodiment. Wherein the terminal comprises a first terminal (message receiving end) and a second terminal (message sending end).

And the second terminal acquires the current login user identification as the resource requester identification after generating the resource request media data according to the acquired media data and the selected decorative element, and generates the resource request media data identification according to the resource requester identification and the hash value of the resource request media data. The second terminal can upload the resource request media data to the server and receive the storage location identification returned by the server. And the second terminal generates a resource request message according to the resource request media data identifier and the storage position identifier, sends the resource request message to the server, and forwards the resource request message to the first terminal by the server.

After receiving the resource request message, the first terminal can extract the resource request media data identifier and the storage position identifier, obtain the resource requester identifier according to the resource request media data identifier, and download and play the resource request media data from the server according to the storage position identifier. And when the media data requested by the resources are played, the resource sharing entrance is displayed.

The first terminal can detect the operation on the resource sharing entrance, enter the resource sharing page, and further generate a resource sharing message on the resource sharing page according to the resource requester identifier and send the resource sharing message for resource sharing. And after the resource sharing is finished, updating the resource sharing entry into a resource sharing result viewing entry, and continuously detecting the triggering operation of the resource sharing result viewing entry, so that share of the shared resource in the social session, which corresponds to the resource request media data and is identified according to the resource requester, is obtained according to the triggering operation, and the obtained share is displayed.

And the second terminal can also play the resource request media data after sending the resource request message, and directly display the resource sharing result viewing entry when not receiving the resource sharing message corresponding to the resource request message. And when a resource sharing message corresponding to the resource request message is received, adding a resource request success decoration element in the displayed resource sharing result viewing entry. The second terminal can also detect a trigger operation acting on the resource sharing result viewing entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

FIG. 24 is a flowchart illustrating a resource request method according to another embodiment. The embodiment is mainly illustrated by applying the method to the second terminal 112 in fig. 1. Referring to fig. 24, the resource request method specifically includes the following steps:

s2402, detecting a trigger operation applied to the media data recording entry.

S2404, displaying the candidate decoration element identification according to the triggering operation.

S2406, determining the decoration element identifier selected from the displayed decoration element identifiers through the selection operation.

S2408, when the decoration element corresponding to the selected decoration element identification belongs to the resource request class, generating resource request media data according to the collected media data and the decoration element.

And the decoration element belonging to the resource request class represents that the decoration element is used for generating the resource request media data together with the collected media data.

Specifically, the second terminal may classify the decoration elements in advance according to the information reflected by the content, to obtain the decoration elements belonging to the resource request class. The content of the decoration elements belonging to the resource request class may reflect the resource request information. Decorative elements belonging to the resource request class such as pictures including the character string "local tyrant red envelope", etc. The second terminal or server may also directly specify the decorative elements belonging to the resource request class. For example, some of the decoration elements are randomly designated as decoration elements belonging to the resource request class.

Therefore, the second terminal can judge whether the generated resource request media data or the common media data is generated according to whether the decoration element selected by the user belongs to the resource request class. Wherein, the common media data does not have the ability to request the sharing of the resource.

S2410, acquiring the current login user identification as the resource requester identification.

S2412, generating a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier.

S2414, sending a resource request message.

Specifically, the terminal may send the resource request message when generating the resource request message. The terminal may specifically send the resource request message in the social session, and may also publish the resource request message on the information publishing platform. The information publishing platform comprises a microblog publishing platform or a wechat friend circle publishing platform and the like.

According to the resource request method, the selection of the decorative element and the collection of the media data are triggered locally through the media data recording inlet, and when the selected decorative element belongs to the resource request class, the resource request media data are automatically generated according to the collected media data and the selected decorative element, so that the currently logged user identifier can be locally obtained to serve as the identifier of the resource requester, and the resource request message is generated according to the identifier of the resource requester and the resource request media data, so that the identification degree of the resource request message is improved, the resource receiver is appointed through the resource request message, and the message receiving end can share the resource without selecting the resource receiver through extra operation, and the resource sharing efficiency is improved.

FIG. 25 is a flowchart illustrating a resource handling method according to an embodiment. The present embodiment can be applied to the application environment of fig. 1. Referring to fig. 25, the resource processing method specifically includes the following steps:

s2502, the second terminal obtains the media data of the resource request.

The resource request media data may be resource request media data generated in advance according to the collected media data and the selected decorative element, or resource request media data generated by real-time recorded media data and the selected decorative element.

S2504, the second terminal obtains the currently logged second user identifier as the resource requester identifier, and generates a resource request message according to the resource requester identifier and the resource request media data.

Specifically, the second terminal is a resource request message sending terminal, and the second user identifier is a currently logged-in user identifier, and is used for identifying a producer of the resource request media data and is a resource requester identifier.

S2506, the second terminal sends the resource request message to the server through the social session.

S2508, the server acquires the first user identification participating in the social conversation and sends the resource request message to the first terminal corresponding to the first user identification.

The social session may be a double-person session or a group session. Specifically, when the social conversation is a double conversation, the server acquires another user identifier participating in the double conversation, and sends the resource request message to the terminal corresponding to the user identifier. And when the social conversation is a group conversation, the server acquires all the user identifications participating in the group conversation except the second user identification, and sends the resource request message to the terminals corresponding to the user identifications.

S2510, the first terminal receives the resource request message.

S2512, the first terminal plays the resource request media data corresponding to the resource request message, and displays the resource sharing entry when playing the resource request media data.

S2514, the first terminal enters the resource sharing page according to the operation on the resource sharing entry, and performs resource sharing on the resource sharing page according to the resource requester identifier specified by the resource request message.

According to the resource processing method, the second terminal generates the resource request message of the appointed resource receiver according to the current login user identification and the acquired resource request media data, and publishes the resource request message in the social session. Therefore, the server can send the resource request message to the first terminal corresponding to the other user identifiers participating in the social conversation. After receiving the resource request message, the first terminal can play the resource request media data corresponding to the resource request message, and display the resource sharing entry when playing the resource request media data, that is, a fast entry for resource sharing is provided when the content of the output message is, so that the first terminal can locally and directly enter a resource sharing page through the fast entry to share the resource, and the resource sharing efficiency is improved. In addition, the resource request party identification, namely the resource receiver, is appointed in the received resource request message, so that the resource sharing can be performed locally without selecting the resource receiver through extra operation, and the resource sharing efficiency is further improved.

In one embodiment, the social session is a group session; the number of first subscriber identities is more than one. The resource processing method further comprises the following steps: the server receives resource sharing messages which are respectively fed back in the group session through the first user identifications and correspond to the resource request messages; and the server allocates the resources specified by the resource sharing messages to the resource requester identifiers.

Specifically, when the social session is a group session and the server sends the resource request message to the terminals corresponding to the other user identifiers participating in the group session, the server may receive the resource sharing messages, which are sent by the user identifiers in the group session and correspond to the resource request feedback, and allocate the resources specified by the resource sharing messages to the resource requester identifiers.

For example, assuming that a user a, a user B, a user C, and a user D participate in a group session H together, A, B, C and D may all send a resource request message in the group session H, and if a sends a resource request message N in the group session H, the server may send the resource request message N to B, C and D, so B, C and D may both feed back a resource sharing message corresponding to the resource request message N in the group session H, and thus the server may allocate resources specified by the resource sharing messages to a.

In this embodiment, a resource processing manner when resource sharing is requested in a group session is provided, so that accuracy in resource sharing by multiple persons is ensured.

In one embodiment, the number of social sessions is more than one. The resource energy processing method further comprises the following steps: the server receives a resource sharing result viewing request initiated through the user identification; the user identification is a first user identification or a second user identification; the server determines a social session through which the resource sharing result viewing request is initiated, and searches a result of resource sharing corresponding to the resource request media data in the determined social session; and the server feeds back the searched result to the terminal corresponding to the user identifier.

Specifically, the second terminal may send the resource request message in a plurality of social sessions after generating the resource request message. The second terminal plays the resource request media data in one social session, after the resource sharing result viewing request is triggered through the displayed resource sharing result viewing entry, the server can determine the social session through which the resource sharing result viewing request is initiated, and only the result of resource sharing corresponding to the resource request media data in the determined social session is searched and fed back to the terminal corresponding to the user identifier.

For example, assume that user a is participating in

social sessions

1, 2, and 3. If the resource sharing result viewing request is initiated in one social conversation, such as the social conversation 1, after the resource request messages are sent in the

social conversations

1, 2 and 3, the server only feeds back the result of resource sharing in the social conversation 1 to the server A, and resource sharing result isolation in different social conversations is achieved.

In this embodiment, after the resource sharing is completed, the resource sharing result can be viewed, and the resource sharing process can be known in real time. Moreover, the viewed resource sharing result is only the share of the shared resource in the current social session corresponding to the resource request media data and according to the resource requester identifier, on one hand, only the data related to the currently viewed user is displayed, so that the privacy and the security of other data are ensured, and the content which the currently viewed user does not want to view is prevented from being displayed too much. It can be understood that the first terminal for executing the resource sharing method in the foregoing embodiment is the first terminal in this embodiment, the second terminal for executing the resource requesting method in the foregoing embodiment is the second terminal in this embodiment, and the server in the foregoing embodiment is a server in the resource processing system. That is, the resource processing method may include all the steps executed by the first terminal in the foregoing embodiment, all the steps executed by the second terminal in the foregoing embodiment, and all the steps executed by the server in the foregoing embodiment.

Referring to fig. 1, in a specific application scenario, the resource request message is a discussion red envelope video message, the resource request media data is a discussion red envelope video, the decoration element belonging to the resource request class is a discussion red envelope pendant, the resource sharing entry is a reward entry, the resource sharing page is a reward page, and the resource sharing result viewing entry is a red envelope detail entry. An operation manager logs in the server to set the discussion red packet hanging piece, so that the terminal can select the discussion red packet hanging piece configured by the server to record the discussion red packet video.

The second terminal may launch a social application showing an interface as shown in fig. 12 or an interface as shown in fig. 13. In the interface shown in fig. 12, the interface shown in fig. 14 may be entered according to a click operation of the user on the entry 1203, or in the interface shown in fig. 13, the interface shown in fig. 14 may be entered according to a click operation of the user on the entry 1201. The second terminal can display the candidate hanging pieces according to the clicking operation of the user on the entrance 1401, select the discussion red packet hanging piece from the candidate hanging pieces, and record the discussion red packet video according to the discussion red packet hanging piece. The second terminal can obtain the current logged user identifier as a discussion red packet party identifier, and then generates a discussion red packet video message according to the discussion red packet party identifier and the recorded discussion red packet video and sends the discussion red packet video message in the current social conversation or selects a new social conversation to send the discussion red packet video message.

After receiving the discussion red packet video message in the social session, the first terminal may play the discussion red packet video corresponding to the discussion red packet video message, and display the reward entrance when playing the discussion red packet video, as shown in fig. 4. The first terminal can detect the operation of the reward entrance, enter the reward page and further acquire the discussion red packet party identification designated by the discussion red packet video message so as to reward the red packet on the reward page. After the first terminal finishes the reward, the reward entrance is updated to the red packet detail entrance, as shown in fig. 10. The first terminal can continue to obtain and display details of the discussion bonus package party rewarded bonus packages by each member participating in the current social conversation according to the clicking operation of the user on the bonus package detail entrance.

And after the second terminal sends the discussion red packet video message, the discussion red packet video can also be played, and the red packet detail entry is displayed in the playing process. When the party discussing the red envelope does not receive the reward, the user interface UI of the red envelope detail entry may be an empty red envelope as shown in fig. 19. When the party discussing the red envelope receives the reward, the user interface UI of the red envelope details entry 2020 is a red envelope filled with gold bulls as shown in fig. 20. The second terminal can detect the clicking operation of the user on the red packet detail entrance, and obtain and display the details of the members participating in the current social conversation on the discussion red packet party rewarding the red packet.

It can be understood that the resource sharing, resource requesting, and resource processing in the foregoing embodiments can be implemented as the reward bonus package, discussion bonus package, and bonus package processing in the specific application scenario of this embodiment.

As shown in fig. 26, in one embodiment, a resource sharing device 2600 is provided. Referring to fig. 26, the resource sharing apparatus 2600 includes: the system comprises a receiving module 2601, a playing module 2602, a presentation module 2603, a skipping module 2604, an obtaining module 2605 and a sharing module 2606.

A receiving module 2601 is configured to receive a resource request message in a social session.

The playing module 2602 is configured to play the resource request media data corresponding to the resource request message.

The showing module 2603 is configured to show the resource sharing entry when the media data is requested by the playing resource.

The skip module 2604 is configured to detect an operation on the resource sharing entry and enter the resource sharing page.

An obtaining module 2605 is configured to obtain the resource requestor identifier specified by the resource request message.

The sharing module 2606 is configured to share the resource on the resource sharing page according to the identifier of the resource requester.

In one embodiment, the play module 2602 is further configured to extract the storage location identification from the resource request message; and downloading the resource request media data according to the storage position identification and playing the media data. The sharing module 2606 is further configured to extract a first hash value corresponding to the resource request media data from the resource request message; generating a second hash value according to the downloaded resource request media data; and when the first hash value is consistent with the second hash value, resource sharing is carried out on the resource sharing page according to the resource requester identifier.

In one embodiment, the play module 2602 is further configured to extract the storage location identification from the resource request message; and downloading the resource request media data from the server according to the storage position identification and playing the media data. The obtaining module 2605 is further configured to extract a ciphertext from the downloaded resource request media data; the ciphertext is obtained by encrypting the resource request media data identifier corresponding to the resource request media data; sending the extracted ciphertext to a server; and receiving the resource request party identifier returned by the server after the check ciphertext passes.

In one embodiment, the sharing module 2606 is further configured to obtain shares configured on the resource sharing page; generating a resource sharing message according to the resource requester identifier and the share; sending a resource sharing message in a social session; and updating the resource sharing entry into a resource sharing result viewing entry.

In one embodiment, the resource sharing device 2600 further comprises: a view module 2607, configured to detect a trigger operation on a resource sharing result view entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

In one embodiment, the resource sharing device 2600 further comprises: a recording module 2609, configured to present a media data recording entry in a message container of a social session; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

As shown in fig. 27, in one embodiment, the resource sharing device 2600 further includes: a view module 2607, a check module 2608, and a record module 2609.

A checking module 2608, configured to obtain a currently logged-in user identifier as a resource sharing party identifier; acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data; correspondingly sending the resource request media data identification, the session identification, the resource sharing party identification, the resource requesting party identification and the share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by the block chain nodes.

In one embodiment, the sharing module 2606 is further configured to query the resource identifier specified by the resource request media data at the time of generation; acquiring a resource corresponding to the resource identifier; and sharing the acquired resources on the resource sharing page according to the resource requester identifier.

In one embodiment, the resource request media data is generated according to the decoration element corresponding to the selected decoration element identification and the collected media data.

In one embodiment, the playing module 2602 is further configured to extract the decoration element identifier and the storage location identifier from the resource request message; acquiring decorative elements corresponding to the decorative element identifiers; downloading the media data of the resource request according to the storage position identification; and playing the media data requested by the resource and correspondingly displaying the decorative elements.

As shown in fig. 28, in one embodiment, a resource requesting apparatus 2800 is provided. Referring to fig. 28, the resource requesting apparatus 2800 includes: an acquisition module 2801, a generation module 2802, a transmission module 2803, and a play module 2804.

An obtaining module 2801, configured to obtain a currently logged-in user identifier as a resource requestor identifier; and acquiring the media data of the resource request.

A generating module 2802, configured to generate a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier.

A sending module 2803 for sending the resource request message in the social session.

A playing module 2804, configured to play the resource request media data, and display a resource sharing result viewing entry; and the resource sharing result viewing entry is used for triggering the result of displaying the shared resource.

In one embodiment, the obtaining module 2801 is further configured to detect a trigger action on the media data recording entry; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

In one embodiment, the play module 2804 is further configured to play the asset request media data; when a resource sharing message corresponding to the resource request message is not received, directly displaying a resource sharing result viewing entry; and when a resource sharing message corresponding to the resource request message is received, adding a resource request success decoration element in the displayed resource sharing result viewing entry.

As shown in fig. 29, in one embodiment, resource requesting device 2800 further comprises: a view module 2805 configured to detect a trigger operation that acts on the resource sharing result view entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

As shown in fig. 30, in one embodiment, a resource requesting device 3000 is provided. Referring to fig. 30, the resource request apparatus 3000 includes: a detection module 3001, a presentation module 3002, a determination module 3003, a generation module 3004, an acquisition module 3005 and a transmission module 3006.

The detecting module 3001 is configured to detect a trigger operation applied to a recording entry of media data.

A display module 3002, configured to display the candidate decoration element identifier according to the trigger operation.

A determining module 3003, configured to determine a decoration element identifier selected from the displayed decoration element identifiers through a selection operation.

The generating module 3004 is configured to generate resource request media data according to the collected media data and the decoration element when the decoration element corresponding to the selected decoration element identifier belongs to the resource request class.

An obtaining module 3005, configured to obtain a currently logged-in user identifier as a resource requestor identifier.

The generating module 3004 is further configured to generate a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier.

A sending module 3006, configured to send a resource request message.

FIG. 31 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the terminal 110 in fig. 1. As shown in fig. 31, the computer device includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and also stores a computer program, and when the computer program is executed by a processor, the computer program can enable the processor to realize the resource sharing and requesting method. The internal memory may also store a computer program that, when executed by the processor, causes the processor to perform a resource sharing and resource requesting method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, or an external keyboard, a touch pad or a mouse, and the like. Those skilled in the art will appreciate that the architecture shown in fig. 31 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the resource sharing apparatus or the resource requesting apparatus provided in the present application may be implemented in a form of a computer program, the computer program may be run on a computer device as shown in fig. 31, and the nonvolatile storage medium of the computer device may store various program modules constituting the resource sharing apparatus or the resource requesting apparatus, for example, the receiving module 2601, the playing module 2602, the presentation module 2603, the jumping module 2604, the obtaining module 2605, the sharing module 2606, and the like shown in fig. 26. The computer program composed of the program modules causes the processor to execute the steps in the resource sharing method or the resource requesting method according to the embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 31 may receive the resource request message in a social session through the receiving module 2601 in the resource sharing apparatus 2600 shown in fig. 26. The resource request media data corresponding to the resource request message is played through the playing module 2602. The resource sharing entry is presented by the presentation module 2603 when the media data is requested by the playback resource. The operation on the resource sharing entry is detected by the skip module 2604, and the resource sharing page is entered. The resource requestor identification specified by the resource request message is obtained by the obtaining module 2605. Resource sharing is performed on the resource sharing page through the sharing module 2606 according to the resource requester identifier.

For another example, the computer device shown in fig. 31 may obtain, through the obtaining module 2801 in the resource requesting apparatus 2800 shown in fig. 26, the currently logged-in user identifier as the resource requester identifier; and acquiring the media data of the resource request. Generating a resource request message according to the resource requester identifier and the resource request media data through a generating module 2802; the resource request message is used for indicating to share the resource according to the resource requester identifier. The resource request message is sent in a social session via the sending module 2803. Playing the resource request media data through the playing module 2804, and displaying the resource sharing result viewing entry; and the resource sharing result viewing entry is used for triggering the result of displaying the shared resource.

In one embodiment, a resource processing system is provided that includes a first terminal, a second terminal, and a server. The second terminal is used for acquiring the media data of the resource request. The second terminal is further configured to obtain a second user identifier currently logged in as a resource requester identifier, and generate a resource request message according to the resource requester identifier and the resource request media data. The second terminal is further used for sending the resource request message to the server through the social session. The server is used for obtaining a first user identification participating in the social conversation and sending the resource request message to a first terminal corresponding to the first user identification. The first terminal is used for receiving the resource request message. The first terminal is further configured to play the resource request media data corresponding to the resource request message, and display the resource sharing entry when the resource request media data is played. The first terminal is further used for entering a resource sharing page according to the operation on the resource sharing entry and carrying out resource sharing on the resource sharing page according to the resource requester identification specified by the resource request message.

It should be understood that the first terminal for executing the resource sharing method in the foregoing embodiment is a first terminal in the resource processing system, the second terminal for executing the resource requesting method in the foregoing embodiment is a second terminal in the resource processing system, and the server in the foregoing embodiment is a server in the resource processing system. That is, a first terminal in the resource processing system may be configured to perform all the steps performed by the first terminal in the foregoing embodiment, a second terminal in the resource processing system may be configured to perform all the steps performed by the second terminal in the foregoing embodiment, and a server in the resource processing system may be configured to perform all the steps performed by the server in the foregoing embodiment.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: receiving a resource request message in a social session; playing the resource request media data corresponding to the resource request message; when the media data of the resource request are played, the resource sharing entrance is displayed; detecting the operation of a resource sharing inlet and entering a resource sharing page; acquiring a resource requester identifier specified by a resource request message; and according to the resource requester identification, resource sharing is carried out on the resource sharing page.

In one embodiment, playing the resource request media data corresponding to the resource request message includes: extracting a storage location identification from the resource request message; and downloading the resource request media data according to the storage position identification and playing the media data. The computer program, when executed by a processor, causes the processor to perform the steps of: extracting a first hash value corresponding to the resource request media data from the resource request message; generating a second hash value according to the downloaded resource request media data; and when the first hash value is consistent with the second hash value, executing a step of resource sharing on the resource sharing page according to the resource requester identifier.

In one embodiment, playing the resource request media data corresponding to the resource request message includes: extracting a storage location identification from the resource request message; and downloading the resource request media data from the server according to the storage position identification and playing the media data. The computer program, when executed by a processor, causes the processor to perform the steps of: extracting a ciphertext from the downloaded resource request media data; the ciphertext is obtained by encrypting the resource request media data identifier corresponding to the resource request media data; sending the extracted ciphertext to a server; and receiving the resource request party identifier returned by the server after the check ciphertext passes.

In one embodiment, according to the resource requester identifier, resource sharing is performed on a resource sharing page, including: acquiring shares configured on a resource sharing page; generating a resource sharing message according to the resource requester identifier and the share; sending a resource sharing message in a social session; and updating the resource sharing entry into a resource sharing result viewing entry.

In one embodiment, the computer program, when executed by a processor, causes the processor to perform the steps of: detecting a trigger operation on a resource sharing result viewing entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

In one embodiment, the computer program, when executed by a processor, causes the processor to perform the steps of: acquiring a current login user identifier as a resource sharing party identifier; acquiring a session identifier corresponding to the social session and a resource request media data identifier corresponding to the resource request media data; correspondingly sending the resource request media data identification, the session identification, the resource sharing party identification, the resource requesting party identification and the share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by the block chain nodes.

In one embodiment, according to the resource requester identifier, resource sharing is performed on a resource sharing page, including: inquiring a resource identifier appointed by the resource request media data during generation; acquiring a resource corresponding to the resource identifier; and sharing the acquired resources on the resource sharing page according to the resource requester identifier.

In one embodiment, the computer program, when executed by a processor, causes the processor to perform the steps of: displaying a media data recording entry in a message container of the social session; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; acquiring decorative elements corresponding to the selected decorative element identifications; collecting media data; and generating the resource request media data according to the media data and the decoration elements.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: acquiring a user identifier of current login as a resource requester identifier; acquiring resource request media data; generating a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier; sending a resource request message in a social session; playing the media data of the resource request, and displaying a resource sharing result viewing entry; and the resource sharing result viewing entry is used for triggering the result of displaying the shared resource.

In one embodiment, playing the resource request media data and displaying the resource sharing result viewing entry includes: playing the resource request media data; when a resource sharing message corresponding to the resource request message is not received, directly displaying a resource sharing result viewing entry; and when a resource sharing message corresponding to the resource request message is received, adding a resource request success decoration element in the displayed resource sharing result viewing entry.

In one embodiment, the computer program, when executed by a processor, causes the processor to perform the steps of: detecting a trigger operation acting on a resource sharing result viewing entry; acquiring share of resources, which correspond to the resource request media data and are shared in the social session according to the resource requester identifier, according to the triggering operation; and displaying the obtained shares.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: detecting a trigger operation acting on a media data recording entrance; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; when the decoration element corresponding to the selected decoration element identification belongs to the resource request class, generating resource request media data according to the collected media data and the decoration element; acquiring a user identifier of current login as a resource requester identifier; generating a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier; a resource request message is sent.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: receiving a resource request message in a social session; playing the resource request media data corresponding to the resource request message; when the media data of the resource request are played, the resource sharing entrance is displayed; detecting the operation of a resource sharing inlet and entering a resource sharing page; acquiring a resource requester identifier specified by a resource request message; and according to the resource requester identification, resource sharing is carried out on the resource sharing page.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: acquiring a user identifier of current login as a resource requester identifier; acquiring resource request media data; generating a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier; sending a resource request message in a social session; playing the media data of the resource request, and displaying a resource sharing result viewing entry; and the resource sharing result viewing entry is used for triggering the result of displaying the shared resource.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: detecting a trigger operation acting on a media data recording entrance; displaying the candidate decoration element identification according to the triggering operation; determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation; when the decoration element corresponding to the selected decoration element identification belongs to the resource request class, generating resource request media data according to the collected media data and the decoration element; acquiring a user identifier of current login as a resource requester identifier; generating a resource request message according to the resource requester identifier and the resource request media data; the resource request message is used for indicating to share the resource according to the resource requester identifier; a resource request message is sent.

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 non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above examples only show some embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method of resource sharing, the method comprising:

receiving a resource request message in a social session; the resource request message is generated according to the resource request media data identifier and the storage position identifier; the resource request media data identifier is generated according to a resource requester identifier and a first hash value of the resource request media data, the storage position identifier is generated by the server after the resource request media data is stored in the server, and the resource identifier appointed by the resource request media data during generation is at least one;

extracting the storage location identification and the first hash value from the resource request message;

downloading the media data of the resource request according to the storage position identification;

generating a second hash value according to the downloaded resource request media data;

playing the downloaded resource request media data in a social session;

displaying a resource sharing inlet when the downloaded resource request media data is played;

entering a resource sharing page from the resource sharing entry;

when the designated resource identifiers are multiple and the first hash value is consistent with the second hash value, resource sharing is carried out according to the resource identifier selected by the user instruction;

acquiring a session identifier corresponding to the social session and a resource request media data identifier;

correspondingly sending the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier and the resource sharing share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by each block chain node.

2. The method of claim 1, further comprising:

extracting a ciphertext from the downloaded resource request media data; the ciphertext is obtained by encrypting the resource request media data identifier corresponding to the resource request media data;

sending the extracted ciphertext to the server;

and receiving the resource requester identification returned by the server after the ciphertext is verified.

3. The method according to claim 1, wherein when the specified resource identifiers are multiple and the first hash value is consistent with the second hash value, the resource identifier selected according to the user instruction is used for resource sharing, including:

when the number of the specified resource identifications is multiple and the first hash value is consistent with the second hash value, acquiring a share which is configured on the resource sharing page and corresponds to the resource identification selected by the user instruction;

generating a resource sharing message according to the resource requester identifier and the share;

sending the resource sharing message in the social session;

and updating the resource sharing entry into a resource sharing result viewing entry.

4. The method of claim 3, further comprising:

detecting a trigger operation of the resource sharing result viewing entry;

acquiring share of the shared resources in the social session, which corresponds to the resource request media data and is identified by the resource requester, according to the triggering operation;

and displaying the obtained share.

5. The method of claim 1, wherein after entering a resource sharing page from the resource sharing entry, the method further comprises:

when the appointed resource identifier is one and the first hash value is consistent with the second hash value, inquiring the resource identifier appointed by the resource request media data in the generation process;

acquiring a resource corresponding to the resource identifier;

and sharing the acquired resources on the resource sharing page according to the resource requester identifier.

6. The method according to any one of claims 1 to 5, wherein the resource request media data is generated according to the decoration element corresponding to the selected decoration element identification and the collected media data.

7. The method of claim 1, wherein playing the downloaded resource request media data in a social session comprises:

extracting a decoration element identifier from the resource request message;

acquiring a decorative element corresponding to the decorative element identifier;

and playing the media data of the resource request in the social conversation, and correspondingly displaying the decoration elements.

8. The method of claim 4, further comprising:

displaying a media data recording entry in a message container of the social session;

displaying candidate decoration element identifications according to the triggering operation;

determining a decoration element identifier selected from the displayed decoration element identifiers through a selection operation;

acquiring a decorative element corresponding to the selected decorative element identifier;

collecting media data;

and generating resource request media data according to the media data and the decoration elements.

9. A resource request method, comprising:

acquiring a user identifier of current login as a resource requester identifier;

acquiring resource request media data and appointing a resource identifier corresponding to at least one resource requested to be shared;

generating a resource request media data identifier according to the resource requester identifier and the first hash value of the resource request media data;

uploading the resource request media data to a server, so that the server receives the resource request media data and then stores and generates a storage position identifier, and feeds back the storage position identifier;

generating a resource request message according to the resource requester identifier and the storage location identifier; the resource request message is used for indicating resource sharing according to the resource requester identifier;

sending the resource request message in a social session;

receiving a resource sharing message corresponding to the resource request message; the resource sharing message is used for triggering and acquiring the action of the resource corresponding to the resource identifier selected by the user instruction when more than one specified resource identifier is available and the first hash value is consistent with the second hash value; the second hash value is generated by that the receiving terminal corresponding to the resource request message extracts the storage position identification from the resource request message, downloads the resource request media data according to the storage position identification and then downloads the resource request media data;

displaying the resource sharing message in the social conversation, and picking up resources according to the resource sharing message; the resource sharing records are generated by a plurality of block chain nodes and used for verifying the resource sharing result through the consistency among the resource sharing records generated by each block chain node.

10. The method according to claim 9, wherein the obtaining of the media data requested by the resource and specifying the resource identifier corresponding to the at least one resource requested to be shared comprises:

detecting a trigger operation acting on a media data recording entrance;

collecting media data;

generating resource request media data according to the media data and the decoration elements;

and appointing a resource identifier corresponding to at least one resource which the resource requests the media data to share.

11. The method of claim 9, further comprising:

playing the resource request media data;

when a resource sharing message corresponding to the resource request message is not received, directly displaying a resource sharing result viewing entry;

and when a resource sharing message corresponding to the resource request message is received, adding a resource request success decoration element in the displayed resource sharing result viewing entry.

12. The method of claim 9, further comprising:

detecting a trigger operation acting on the resource sharing result viewing entry;

and displaying the obtained share.

13. A resource sharing apparatus, the apparatus comprising:

a receiving module for receiving a resource request message in a social session; the resource request message is generated according to the resource request media data identifier and the storage position identifier; the resource request media data identifier is generated according to a resource requester identifier and a first hash value of the resource request media data, the storage position identifier is generated by the server after the resource request media data is stored in the server, and the resource identifier appointed by the resource request media data during generation is at least one;

the playing module is used for extracting the storage position identification from the resource request message; downloading the media data of the resource request according to the storage position identification;

the sharing module is used for extracting the first hash value from the resource request message; generating a second hash value according to the downloaded resource request media data;

the playing module is further configured to play the downloaded resource request media data in a social session;

the display module is used for displaying the resource sharing inlet when the downloaded playing resource requests the media data;

the skipping module is used for entering a resource sharing page from the resource sharing entry;

the sharing module is further configured to share the resource according to the resource identifier selected by the user instruction when the plurality of specified resource identifiers are provided and the first hash value is consistent with the second hash value;

the verification module is used for acquiring the current login user identification as the resource sharing party identification; acquiring a session identifier corresponding to the social session and a resource request media data identifier; correspondingly sending the resource request media data identifier, the session identifier, the resource sharing party identifier, the resource requesting party identifier and the resource sharing share to a plurality of block link points to generate resource sharing records; the resource sharing records generated by the plurality of block chain nodes are used for verifying the resource sharing result through the consistency among the resource sharing records generated by each block chain node.

14. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 12.

15. A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 12.