METHOD AND APPARATUS FOR SERVICE IMPLEMENTATION

Abstract

A method including receiving a prompt request sent by an initiator; generating an object allocation set according to object allocation information in the prompt request, the object allocation set including a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and allocating the object allocation set to a prompt target, and sending to the prompt target a prompt message related to the allocation operation. The technical solution of the present disclosure optimizes the object allocation solution.

Description

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This application claims priority to and is a continuation of PCT Patent Application No. PCT/CN2017/070149, filed on 4 Jan. 2017, which claims priority to Chinese Patent Application No. 201610019333.8, filed on 12 Jan. 2016 and entitled “METHOD AND APPARATUS FOR SERVICE IMPLEMENTATION”, which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates to the field of communications technologies, and, more particularly, to service implementation methods and apparatuses.

BACKGROUND

With the development of network technologies, various implementations for online services have occurred. Using a virtual item exchange in the form of “red packet” as an example, a user may put an electronic greeting card, a cash gift and the like into a “red packet”, and then issue the “red packet” to a particular user, or to a group so that group members receive the “red packet”.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify all key features or essential features of the claimed subject matter, nor is it intended to be used alone as an aid in determining the scope of the claimed subject matter. The term “technique(s) or technical solution(s)” for instance, may refer to apparatus(s), system(s), method(s) and/or computer-readable instructions as permitted by the context above and throughout the present disclosure.

The present disclosure provides service implementation methods and apparatuses, which may optimize the object allocation solution.

In order to achieve the foregoing objective, technical solutions provided by the present disclosure are as follows:

According to a first aspect of the present disclosure, a service implementation method is provided, including:

receiving a prompt request sent by an initiator;

generating an object allocation set according to object allocation information in the prompt request, the object allocation set including a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and

executing an allocation operation of allocating the object allocation set to a prompt target, and sending to the prompt target a prompt message related to the allocation operation.

According to a second aspect of the present disclosure, a service implementation apparatus is provided, including:

a first receiving unit configured to receive a prompt request sent by an initiator;

a generation unit configured to generate an object allocation set according to object allocation information in the prompt request, the object allocation set including a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and

a processing unit configured to execute an allocation operation of allocating the object allocation set to a prompt target, and send to the prompt target a prompt message related to the allocation operation.

According to a third aspect of the present disclosure, a service implementation method is provided, including:

determining an allocation source, an allocation target, a notification target, and a quantity of to-be-allocated objects according to a received object allocation request;

extracting to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source; and

executing an allocation operation of allocating the to-be-allocated objects to the allocation target, and notifying the notification target of a message related to the allocation operation.

According to a fourth aspect of the present disclosure, a service implementation apparatus is provided, including:

a determining unit configured to determine an allocation source, an allocation target, a notification target, and a quantity of to-be-allocated objects according to a received object allocation request;

an extraction unit configured to extract to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source; and

a processing unit configured to execute an allocation operation of allocating the to-be-allocated objects to the allocation target, and notify the notification target of a message related to the allocation operation.

As shown from the foregoing technical solutions, the present disclosure uses the prompt function of a prompt message by combining the prompt message with object allocation, thus avoiding an object allocation failure caused by omission of a prompt target, and helping improve the success rate and promptness of object allocation.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the example embodiments of the present disclosure, the following briefly introduces the accompanying drawings describing the example embodiments. Apparently, the accompanying drawings described in the following merely represent some example embodiments described in the present disclosure, and those of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

FIG. 1 is a schematic diagram of an interface for red packet issuing in the related art;

FIG. 2 is a flowchart of a service implementation method according to an example embodiment of the present disclosure;

FIG. 3A is a schematic diagram of an interface for configuring a prompt request according to an example embodiment of the present disclosure;

FIG. 3B is a schematic diagram of an interface for initiating a prompt request on a red packet issuing page according to an example embodiment of the present disclosure;

FIG. 4 is a flowchart of a red packet issuing process according to an example embodiment of the present disclosure;

FIG. 5 is a schematic diagram of an interface for receiving a red packet according to an example embodiment of the present disclosure;

FIG. 6 is a flowchart of another red packet issuing process according to an example embodiment of the present disclosure;

FIG. 7 is a flowchart of further another red packet issuing process according to an example embodiment of the present disclosure;

FIG. 8 is a flowchart of further another red packet issuing process according to an example embodiment of the present disclosure;

FIG. 9 to FIG. 13 are schematic diagrams of an interface for red packet issuing according to an example embodiment of the present disclosure;

FIG. 14 is a schematic structural diagram of an electronic device according to an example embodiment of the present disclosure;

FIG. 15 is a block diagram of a service implementation apparatus according to an example embodiment of the present disclosure;

FIG. 16 is a flowchart of a service implementation method according to an example embodiment of the present disclosure;

FIG. 17 to FIG. 20 are schematic diagrams of a service configuration page according to an example embodiment of the present disclosure;

FIG. 21 is a flowchart of object allocation according to an example embodiment of the present disclosure;

FIG. 22 to FIG. 24 are schematic diagrams of object allocation pages according to an example embodiment of the present disclosure;

FIG. 25 to FIG. 26 are schematic diagrams of a page for an object allocation notification message according to an example embodiment of the present disclosure;

FIG. 27 is a schematic structural diagram of an electronic device according to an example embodiment of the present disclosure; and

FIG. 28 is a block diagram of a service implementation apparatus according to an example embodiment of the present disclosure.

DETAILED DESCRIPTION

Technical solutions of the embodiments of the present disclosure may implement related services between different users, for example, implement a “red packet” issuing service, a “coupon” issuing service, and so on. The red packet issuing service may specifically refer to a user giving funds, other virtual items, or the like of his/her own to another user by issuing a red packet. In an enterprise scenario, the red packet issuing service may refer to a boss, financial staff or other authorized persons accessing a user's personal account (such as an account of the boss), a public funds account, an enterprise funds account or the like and send funds or other virtual items in the account by issuing a red packet.

Using a “red packet” as an example, in an application scenario of the related art, red packet issuing is closely integrated with a communication message. For example, as shown in FIG. 1, when a user Xiaobai issues a red packet to a user Xiaohei by using an instant communication message, an issuance notification obtained by the user Xiaohei is the same as other types of instant communication messages. Then, the user Xiaohei taps on the instant communication message to receive the red packet. However, since red packet issuing based on an instant communication message has a low prompt effect, the user usually cannot respond in time, affecting the process of red packet issuing.

Therefore, the present disclosure improves the service implementation process above, to solve the foregoing problem in the related art. The following embodiments are provided to further illustrate the present disclosure:

FIG. 2 is a flowchart of a service implementation method according to an example embodiment of the present disclosure. As shown in FIG. 2, the method is applied to a server, and may include the following steps:

Step 202: A prompt request sent by an initiator is received.

Step 204: An object allocation set is generated according to object allocation information in the prompt request, the object allocation set including a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator.

Step 206: An allocation operation of allocating the object allocation set to a prompt target is executed, and a prompt message related to the allocation operation is sent to the prompt target.

By using an application scenario of red packet issuing as an example, a detailed description is made below with reference to features in the foregoing embodiment. Certainly, the technical solutions of the present disclosure are also applicable to other scenarios. The present disclosure does not limit the technical solution to the scenario of red packet issuing.

1. Prompt Request

In the technical solution of the present disclosure, an initiator initiates a prompt request to a server by using an application (APP) installed on an electronic device. It is assumed that the initiator initiates the prompt request to the server by using an instant messaging APP, and the instant messaging APP may be an Enterprise Instant Messaging (EIM) APP, such as “DING Talk”. Certainly, an initiator user may also initiate the prompt request by using other APPs or in other manners, which are not limited in the present disclosure.

Using “DING Talk” as an example, this APP provides a “DING” function, so that the initiator may configure the foregoing prompt request by using an operation interface shown in FIG. 3A. The scenario where the user Xiaobai sends a red packet to the user Xiaohei depicted in FIG. 1 is still used as an example, i.e., it is assumed that the user Xiaobai is the initiator and the user Xiaohei is the prompt target. Then, as shown in FIG. 3A:

1) Recipient: the user Xiaobai may set the user Xiaohei as the “recipient”; Certainly, the user Xiaobai may also set a group as the “recipient”, and then each user in the group may be used as a corresponding prompt target.

2) Prompt manner: the user Xiaobai may set the “prompt manner” to be a “phone call” manner as shown in FIG. 3A, so that the prompt target may receive a phone call initiated by the server and receive the red packet accordingly. Certainly, the user Xiaobai may also set other prompt manners. For example, in a “text message” manner, the prompt target may receive a text message sent by the server, and receive the red packet accordingly. An example process of receiving the red packet will be described in detail in the following.

3) Sending time: the user Xiaobai may set the “sending time” to be “send now” as shown in FIG. 3A, and then the server may initiate a corresponding operation to the prompt target immediately upon receiving the prompt request. Certainly, the user Xiaobai may also set any time point such as “send 30 minutes later” or “send at 12:00 today”.

4) Red packet information: the user Xiaobai may set a name of the “red packet”, such as “May you be happy and prosperous!!!” shown in FIG. 3A; meanwhile, the user Xiaobai may also set the amount of the “red packet”, such as “RMB 10” shown in FIG. 3A. The user Xiaobai may further set other information of the “red packet”, which is not limited in the present disclosure.

5) Prompt content: the user Xiaobai may set a speech-form prompt content, i.e., record a speech content of the user Xiaobai, to be played to the user Xiaohei. Alternatively, the prompt content may also be in a text form; in this case, the prompt content may be presented to the user Xiaohei, or played to the user Xiaohei after being automatically converted into a speech for playing.

When autonomously configuring the foregoing prompt content, the user Xiaobai as the initiator may configure the prompt content to be any content, for example, “Xiaohei, I have sent a red packet to you in DING Talk!” as shown in FIG. 3A. Alternatively, if the user Xiaobai does not configure the prompt content, the server may autonomously generate a prompt content when the prompt request is related to red packet issuing. For example, the prompt content may include a manner in which the red packet is received, e.g., “Your friend Xiaobai has sent you an RMB 10 red packet. Please log onto DING Talk to receive the red packet.”

Certainly, apart from the solution of directly configuring the prompt request related to red packet issuing as shown in FIG. 3A, the prompt request may also be generated in other manners. For example, as shown in FIG. 3B, the user Xiaobai may issue the red packet to the user Xiaohei by directly using a red packet issuing manner in the related art, for example, using a communication message. Then, the user Xiaobai may tap on a communication message including the red packet on a message sending/receiving page shown in FIG. 3B, and select a “DING” option in a popup menu, thus sending to the user Xiaohei a prompt request related to the red packet. Alternatively, the user Xiaobai is redirected to the page as shown in FIG. 3A and further edits the prompt request, and then the prompt request is sent to the user Xiaohei.

2. Red Packet Issuing

1) Prompt and red packet issuing are independent of each other.

In the technical solution of the present disclosure, e.g., in the foregoing step 206, execution of the allocation operation and sending of the prompt message are combined, to make use of the prompt function of the prompt message, such that the prompt target finds and receives the allocated set of allocation objects in time, avoiding occurrence of an allocation failure or the like caused by omission.

As an example embodiment, sending of the prompt message and execution of the allocation operation may be independent of each other. Correspondingly, FIG. 4 is a flowchart of red packet issuing according to an example embodiment of the present disclosure. As shown in FIG. 4, using “DING Talk” as an example, the foregoing red packet issuing process may include the following steps:

Step 402: An initiator initiates a DING request (equivalent to the “prompt request” in the embodiment shown in FIG. 2) to a server.

In this embodiment, reference may be made to FIG. 3A and the corresponding description for the configuration process of the DING request. Details are not described here again.

Step 404: The server generates a corresponding red packet (equivalent to the “object allocation set” in the embodiment shown in FIG. 2) according to red packet information (equivalent to the “object allocation information” in the embodiment shown in FIG. 2) in the DING request, for example, the red packet name “May you be happy and prosperous!!!” and the red packet amount “RMB 10” shown in FIG. 3A.

Step 406A: The server initiates a DING prompt to a prompt target.

In this embodiment, the DING prompt in the form of a phone call is used as an example. After determining a prompt target specified by the initiator, the server may obtain a phone number of the prompt target, and call the phone number, to implement the DING prompt. For example, after converting “Xiaohei, I have sent a red packet to you in DING Talk!” shown in FIG. 3A into a speech, the server may play the speech when the prompt target answers the call, to enable the prompt target to understand a relationship between the DING prompt and red packet issuing, thus guiding the prompt target to receive the red packet.

Step 406B: The server sends a communication message to the prompt target.

In this embodiment, assuming that red packet issuing is carried out through “DING Talk”, after determining the prompt target specified by the initiator, the server may further determine an electronic device on which a registered account of the prompt target is logged onto. Then, the communication message is sent to the electronic device and displayed in the “DING Talk” APP installed in the electronic device. Certainly, if “DING Talk” requires that a user should bind a registered account with a phone number, it may be ensured that the prompt target will receive the phone call of the DING prompt and the foregoing communication message on the same electronic device. Thus, it is ensured that the prompt target may check the communication message in time after responding to the DING prompt, to receive the red packet.

It should be noted that, in this embodiment, step 406A and step 406B are independent of each other. There is no necessary sequence or dependency between step 406A and step 406B. Therefore, even if the prompt target fails to respond to the DING prompt, the prompt target may still receive the communication message directly and receive the red packet.

In one situation, the server may automatically allocate the red packet to the prompt target when sending the communication message to the prompt target, without instructing the prompt target to perform extra processing. In another situation, the foregoing embodiment may further include the following steps:

Step 408: The server receives a trigger response message from the prompt target.

Step 410: The server issues the red packet to the prompt target.

In this embodiment, as shown in FIG. 5, the user Xiaohei as the prompt target may view, on a “DING message label page” of “DING Talk”, content of a DING message (i.e., the foregoing communication message) sent by the user Xiaobai as the initiator. The content includes a “red packet” icon, a corresponding theme “May you be happy and prosperous!!!”, and the like. In this case, after the user Xiaohei executes a preset trigger operation such as tapping on the “red packet” icon, “DING Talk” returns the trigger response message to the server accordingly. Then, the server issues the red packet to the user Xiaohei, for example, the server deposits funds in the red packet into an account of the user Xiaohei.

2) The red packet is issued after the prompt succeeds.

As another example embodiment, when sending the prompt message to the prompt target in step 206, the server may execute a prompt operation for the prompt target, to send the prompt message to the prompt target. Then, the server executes the allocation operation of allocating the object allocation set to the prompt target only when determining that the prompt message has been transmitted to the prompt target successfully.

Based on the foregoing embodiment, there still exist various situations, which are described below respectively.

Implementation 1

FIG. 6 is a flowchart of another red packet issuing process according to an example embodiment of the present disclosure. As shown in FIG. 6, the red packet issuing process may include the following steps:

Step 602: An initiator initiates a DING request to a server.

Step 604: The server generates a red packet.

Step 606: The server initiates a DING prompt to a prompt target.

For steps 602-606 in this embodiment, reference may be made to steps 402-406A above. Details are not described here again.

Step 608: The server receives a prompt response returned by the prompt target.

In this embodiment, the prompt response may be construed as a confirm message that is returned by “DING Talk” to the server when the prompt target responds to the DING prompt actively, such that the server may determine that the DING prompt is received by the prompt target. Thus, the prompt function and effect are realized.

Prompt responses corresponding to DING prompts of different forms may also be different. For example, when the DING prompt is in a phone call form, it may be determined that the prompt response is received as long as at least one of the following conditions is met: the phone call is answered, duration of answering the phone call reaches preset duration, a full announcement of the phone call is listened to, a response message sent by the prompt target is received, a response content of the response message accords with a preset content, and so on. When the DING prompt is in a text message form, it may be determined that the prompt response is received as long as at least one of the following conditions is met: the text message is viewed, a reply text message is received, a content of the reply text message accords with a preset content, and so on.

Step 610: The server issues the red packet to the prompt target.

In this embodiment, the server may issue the red packet directly or in a manner similar to that in steps 408-410. Details are not described here again.

According to the foregoing embodiment, the server does not allocate the object allocation set blindly; instead, the server confirms that the prompt message has been transmitted to the prompt target successfully according to the prompt response from the prompt target, to ensure an actual prompt effect of the DING prompt, and then executes the allocation operation. The server may even prompt again when the prompt response is not received.

Implementation 2

FIG. 7 is a flowchart of further another red packet issuing process according to an example embodiment of the present disclosure. As shown in FIG. 7, the red packet issuing process may include the following steps:

Step 702: An initiator initiates a DING request to a server.

Step 704: The server generates a red packet.

Step 706: The server initiates a DING prompt to a prompt target.

For steps 702-706 in this embodiment, reference may be made to steps 402-406A above. Details are not described here again.

Step 708: The server receives a prompt response returned by the prompt target.

Step 710: The server determines whether a response content in the prompt response are consistent with a preset content; if yes, step 712 is performed; otherwise, the process ends.

In this embodiment, the server may receive a response message that is returned by the prompt target in response to the prompt message. In addition, when a response content of the response message accords with a preset content, it is determined that the prompt message has been transmitted to the prompt target successfully.

When the prompt operation is setting up a call with the prompt target and playing the prompt message by voice, the response message may be a voice speech produced by the prompt target or a character string input in a call interface. For example, the preset content may be “I want a red packet”. The prompt target may directly produce a voice speech of “I want a red packet”, to be identified and judged by the server. Alternatively, the prompt target may input, on a dial of the call interface, a number “9942” corresponding to “WYHB” (“WYHB” corresponds to initials of Chinese Pinyin of a sentence meaning “I want a red packet”), to be identified and judged by the server.

When the prompt operation is sending a communication message including the prompt message to the prompt target, the response message may be a reply message of the prompt target in response to the communication message. For example, the communication message may be a text message, an email, an instant communication message, and so on. Similarly, for example, the preset content may be “I want a red packet”. The prompt target may return a reply message including “I want a red packet”, “WYHB” or a similar content, to be identified and judged by the server.

Step 712: The server issues the red packet to the prompt target.

In this embodiment, the server may issue the red packet directly or in a manner similar to that in steps 408-410. Details are not described here again.

According to the foregoing embodiment, when the response content of the response message from the prompt target accords with the preset content, the server may determine that the prompt target receives and understands the prompt message in the DING prompt and that the prompt target wants to obtain the corresponding object allocation set. Therefore, the server may execute the corresponding allocation operation.

3. Activity Initiation Manner

As an example embodiment, the technical solution of the present disclosure may be applied to a red packet issuing activity. Correspondingly, FIG. 8 is a flowchart of further another red packet issuing process according to an example embodiment of the present disclosure. As shown in FIG. 8, the red packet issuing process may include the following steps:

Step 802: An initiator sends an activity initiation request to a server.

Step 804: The server sends an activity invitation to candidate targets.

In this embodiment, in one situation, the candidate targets may be all registered users. Only a candidate target A and a candidate target B are taken as an example here for description. In another situation, in combination with “conditional judgment” in step 808 below, it is actually possible to perform conditional judgment on each registered user in advance, and only registered users meeting the condition are used as the candidate targets here.

For example, as shown in FIG. 9, assuming that the activity is “Boss Ma's red packet” activity initiated by “DING Talk”, the candidate targets may view a corresponding activity sign-up entry on a preset page in “DING Talk”. For example, in the “welfare service” page shown in FIG. 9, the candidate targets may see introduction contents such as “red packet for commencement” and “Boss Ma sending red packets by phone” as well as prompt information of “sign up”. Then, the candidate targets may tap on a corresponding area to view a specific activity invitation content.

Step 806: The server receives activity sign-up messages (equivalent to the object allocation request for the object allocation set in the embodiment shown in FIG. 2) sent by the candidate targets.

In this embodiment, it is assumed that after tapping on a corresponding area on the page shown in FIG. 9, a candidate target may be redirected to the specific introduction of the activity content about “Boss Ma's red packet” shown in FIG. 10, including contents such as “Boss Ma sends you a red packet for commencement! . . . Invite your friends to share Boss Ma's red packet together!”, and a description about an activity sign-up time such as “February 1^st to February 15^th”. Then, the candidate target may tap on “sign up now” to send a corresponding activity sign-up message to the server to sign up.

In one situation, as described above, the server may determine whether each of the registered users meets a condition, and then initiate activity invitations only to users meeting the condition in step 804.

In another situation, the server may initiate activity invitations to all the registered users. When each candidate target wants to register, an electronic device logged onto by the candidate target may determine (by using the installed “DING Talk” APP) whether the candidate target meets the condition. When the candidate target meets the condition, a page as shown in FIG. 10 may be presented, and the candidate target signs up successfully. When the candidate target does not meet the condition, a page as shown in FIG. 11 is presented, to inform the candidate target of a necessary condition, for example, “only users in a team with 6 or more members may participate in the activity”.

In further another situation, the server may initiate activity invitations to all the registered users, and each candidate target may sign up through the page shown in FIG. 10. Then, the conditional judgment is implemented through step 808 below:

Step 808: The server performs conditional judgment on all candidate targets that participate in sign-up.

Step 810: The server returns, according to conditional judgment results, corresponding sign-up results to the candidate targets that participate in sign-up; for example, the candidate target A signs up successfully, the candidate target B fails in sign-up, and so on

Certainly, the server may pre-configure a judgment condition. The judgment condition may be any content required. For example, the preset condition may include at least one of the following: the candidate target is a registered user; the candidate target is a member of a registered team; a total quantity of members of a team to which the candidate target belongs reaches a preset quantity; and so on.

In addition, the candidate target may further share the activity content, for example, share the activity content to platforms other than “DING Talk”, so that users in these platforms may view a shared content as shown in FIG. 12 through a shared link. If these users are not registered users of “DING Talk”, the users may further participate in the corresponding activity according to information in the shared content, for example, “Step 1: Download and register with DING Talk”, “Step 2: Make sure that 6 or more members in your team have signed up”, and so on.

Step 812: The server sends contact information of the initiator to the candidate target A that signs up successfully, and uses the candidate target as the prompt target of the current red packet issuing.

This embodiment is different from the red packet issuing solution in the related art that requires an initiator and a prompt target to be associated users, such as friends or members of the same group. In the embodiment of the present disclosure, the initiator may be a user not associated with the prompt target. Therefore, the contact information of the initiator may be sent to and stored in an address book of the prompt target in advance, so that the prompt target knows the identity of the opposite party (i.e., the initiator) in subsequent sending of a prompt message and execution of an allocation operation.

Step 814: The server receives a DING request sent by the initiator.

Step 816: The server generates a red packet.

Step 818: The server initiates a DING prompt.

In this embodiment, the server may initiate a prompt operation to the prompt target in the name of the initiator, to send the prompt message to the prompt target. For example, as shown in FIG. 13, when the initiator is “Ma Yun” and a prompt is initiated by making a phone call, the server may send contact information of “Ma Yun” to the prompt target and store the contact information in the prompt target in advance in step 812. As such, a phone call made in the name of “Ma Yun” may be received in step 818, thus realizing the prompt function and corresponding red packet issuing.

Step 820: The server issues the red packet to the prompt target.

In this embodiment, the operation of issuing the red packet may be implemented based on the relationship between the DING prompt and red packet issuing according to the solution shown in any embodiment in FIG. 4, FIG. 6 and FIG. 7 above. Details are not described here again.

FIG. 14 is a schematic structural diagram of an electronic device 1400 according to an example embodiment of the present disclosure. Referring to FIG. 14, on a hardware level, the electronic device 1400 includes a processor 1402, an internal bus 1404, a network interface 1406, a memory 1408, and a non-volatile storage 1410, and may include other hardware required for the service. The processor 1402 reads a corresponding computer program from the non-volatile storage 1410 to the memory 1408 and then runs the computer program, to form a service implementation apparatus 1412 on a logic level. Certainly, in addition to the software implementation, the present disclosure does not exclude other implementations, such as logic devices, or a combination of software and hardware. In other words, an entity executing the following processing procedure is not limited to logic units, and may also be hardware or logic devices. Both the memory 1408 and the non-volatile storage 1410 are examples of computer readable medium.

Referring to FIG. 15, in the software implementation, the service implementation apparatus 1500 includes one or more processor(s) 1502 or data processing unit(s) and computer readable media 1504. The terminal interaction apparatus 1500 may further include one or more input/output interface(s) 1506 and one or more network interface(s) 1508. The service implementation apparatus 1400 and the electronic device 1500 may be applied at a client terminal.

The computer readable media 1508 may store therein a plurality of modules or units including:

a first receiving unit 1510, a generation unit 1512 and a processing unit 1514, wherein:

the first receiving unit 1510 is configured to receive a prompt request sent by an initiator;

the generation unit 1512 is configured to generate an object allocation set according to object allocation information in the prompt request, the object allocation set including a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and

the processing unit 1514 is configured to execute an allocation operation of allocating the object allocation set to a prompt target, and send to the prompt target a prompt message related to the allocation operation.

Optionally, a prompt content of the prompt message includes: a manner in which the object allocation set is received.

Optionally, the processing unit 1514 is specifically configured to:

execute a prompt operation for the prompt target, to send the prompt message to the prompt target; and

execute the allocation operation of allocating the object allocation set to the prompt target when the prompt message has been transmitted to the prompt target successfully.

Optionally, the service implementation apparatus 1500 further includes the following unit stored on the computer readable media 1504:

a second receiving unit 1516 configured to receive a response message returned by the prompt target in response to the prompt message,

wherein when a response content of the response message accords with a preset content, the processing unit determines that the prompt message has been transmitted to the prompt target successfully.

Optionally,

when the prompt operation is setting up a call with the prompt target and playing the prompt message by voice, the response message is a voice speech produced by the prompt target or a character string input in a call interface; and

when the prompt operation is sending a communication message including the prompt message to the prompt target, the response message is a reply message of the prompt target in response to the communication message.

Optionally, the service implementation apparatus 1500 further includes the following units stored on the computer readable media 1504:

a third receiving unit 1518 configured to receive an object allocation request from a candidate target; and

a target determining unit 1520 configured to use the candidate target as the prompt target when the candidate target meets a preset condition.

Optionally, the preset condition includes at least one of the following:

the candidate target is a registered user;

the candidate target is a member of a registered team; and

a total quantity of members of a team to which the candidate target belongs reaches a preset quantity.

Optionally, service implementation apparatus 1500 further includes the following unit stored on the computer readable media 1504:

a sending unit 1522 configured to: before the prompt message is sent to the prompt target, send contact information of the initiator to the prompt target, so that the prompt target stores the contact information of the initiator in advance,

wherein the processing unit 1514 sends to the prompt target the prompt message related to the allocation operation in the following manner: initiating a prompt operation to the prompt target in the name of the initiator, to send the prompt message to the prompt target.

Optionally, the processing unit 1514 executes the allocation operation of allocating the object allocation set to the prompt target in the following manner:

sending to the prompt target a communication message related to the object allocation set; and

allocating objects in the object allocation set to the prompt target when it is determined that the prompt target has executed a preset trigger operation on the communication message.

FIG. 16 is a flowchart of a service implementation method according to an example embodiment of the present disclosure. As shown in FIG. 16, the method is applied to a server, and may include the following steps:

Step 1602: An allocation source, an allocation target, a notification target, and the quantity of to-be-allocated objects are determined according to a received object allocation request;

Step 1604: To-be-allocated objects corresponding to the quantity of to-be-allocated objects are extracted from an object set corresponding to the allocation source.

Step 1606: An allocation operation of allocating the to-be-allocated objects to the allocation target is executed, and the notification target is notified of a message related to the allocation operation.

1. Information Determining

In step 1602 above, various information such as the allocation source, the allocation target, the notification target, and the quantity of to-be-allocated objects may be determined in multiple manners. The information determining manner is illustrated in detail below.

Embodiment 1

As an example embodiment, the server may use a sender of the object allocation request as the allocation source, and read the allocation target and the quantity of to-be-allocated objects from the object allocation request. In other words, the allocation source has configured the allocation target and the quantity of to-be-allocated objects in advance.

For example, the allocation source performs the foregoing configuration process by using an APP installed on an electronic device, wherein the APP may be an instant messaging APP. For example, in an embodiment, the instant messaging APP may be an EIM APP, such as the EIM APP “Ding Talk”.

In this case, when sending an object allocation request by using, for example, a message session window of a communication group in “DING Talk”, the allocation source may configure the allocation target and the quantity of to-be-allocated objects correspondingly, and automatically determine the notification target based on a characteristic of the “group”

As shown in FIG. 17, it is assumed that the allocation source performs an operation in a message session window corresponding to a group named “hard working group”. For example, the allocation source may tap on the “∘+” icon at the lower left of the message session window shown in FIG. 17, to evoke the menu option located at the bottom of the message session window as shown in FIG. 3A. The menu option includes enterprise management function entries such as “announcement”, “log”, “approval” and “sign in”, and may also include function entries for services such as “red packet”. That is, a red packet issuing service is taken as an example here, to introduce the service implementation solution based on the present disclosure.

After selecting the “red packet” shown in FIG. 18, the allocation source may be redirected to a red packet configuration page as shown in FIG. 19. As shown in FIG. 19, a red packet issuing manner based on the present disclosure is “targeted red packet”, that is, it is still possible to specifically indicate an expected target user of issuance in a multi-user scenario such as a group. “Random red packet” is a red packet issuing solution in the related art, in which it is impossible to specifically indicate an expected target user of issuance in a multi-user scenario such as a group, and it is necessary to use all users in the group as targets of issuance.

As shown in FIG. 19, a “recipient” is a user acting as an “allocation target”. The allocation source may select, at will, expected red packet issuing targets from all members of the “hard working group” as the “recipient” here. For example, the “hard working group” includes 13 persons in total, and 3 persons are selected as the “recipients” in the embodiment shown in FIG. 19. Correspondingly, when the allocation source selects 3 persons as the “allocation targets” and the “hard working group” includes 13 persons in total, the server may automatically determine other 9 group members in the group than the allocation source and the allocation targets as the notification targets.

Meanwhile, a “single-packet amount” shown in FIG. 19 is the quantity of objects allocated to each allocation target. In the embodiment shown in FIG. 19, the total quantity of to-be-allocated objects is RMB 3,000×3 persons=RMB 9,000.

Certainly, in the red packet scenario shown in FIG. 19, issued objects may be funds. The funds may be from an account (i.e., the “object set”) corresponding to the allocation source. In other application scenarios, there may be other forms of objects and object sets, which are not limited in the present disclosure.

Embodiment 2

As another example embodiment, the server may use a sender of the object allocation request as the allocation source, and read, from the object allocation request, the allocation target, the notification target and the quantity of to-be-allocated objects which are configured by the allocation source. In other words, the allocation source may configure all aspects such as the allocation target, the notification target and the quantity of to-be-allocated objects in advance.

As shown in FIG. 20, the allocation source may configure the “recipient” in a manner similar to that in the embodiment shown in FIG. 19. Assuming that the allocation source still selects 3 persons, the 3 persons will be used as the “allocation targets”. Similar to the manner of configuring the “recipients”, the allocation source may further select any member except the 3 selected “recipients” from the group as the “notification target” (labeled as “flaunt” in FIG. 20). For example, 5 persons are selected in FIG. 20, and they are not necessarily all remaining members in the group. Certainly, in Embodiment 2, the allocation target and the notification target may belong to different groups, and may be randomly selected by the allocation source from an address book.

Meanwhile, the allocation source may further configure “the quantity of to-be-allocated objects” in a red packet configuration page as shown in FIG. 20, i.e., configure a specific value of the “total amount (random allocation)” in FIG. 20. For example, the value is configured to be RMB 10,000 in FIG. 20. In the embodiment shown in FIG. 19, a configuration form of “single-packet amount” is used, that is, each allocation target obtains the same quantity of to-be-allocated objects, which is RMB 3,000 as shown in FIG. 19. In the embodiment shown in FIG. 20, a configuration form of “total amount (random allocation)” is used, that is, RMB 10,000, for example, is randomly allocated to all the allocation targets, instead of setting a fixed amount for each allocation target.

It should be noted that, both the “single-packet amount” shown in FIG. 19 and the “total amount (random allocation)” shown in FIG. 20 are merely examples of the configuration form of “the quantity of to-be-allocated objects” listed in the present disclosure.

On one hand, each configuration form may be applied to any embodiment. For example, the configuration form of “single-packet amount” shown in FIG. 19 may also be applied to the embodiment shown in FIG. 20, and the configuration form of “total amount (random allocation)” shown in FIG. 20 may also be applied to the embodiment shown in FIG. 19. The allocation source may select a configuration form to be used currently, or directly use a default configuration form. Correspondingly, the server needs to use a corresponding object allocation rule according to the configuration form selected by the allocation source, to allocate the to-be-allocated objects reasonably, or the server allocates the to-be-allocated objects according to a default rule corresponding to the default configuration form.

On the other hand, other configuration forms may also be used. For example, the quantity of all to-be-allocated objects is equally allocated (the final allocation effect is similar to that of the embodiment shown in FIG. 19, but the configuration process is different), an object quantity is configured for each allocation target (for example, 1,000 for user A, 3,000 for user B, and 5,000 for user C), and so on, which are not limited in the present disclosure.

In addition, as shown in FIG. 19 to FIG. 20, on the red packet configuration page, corresponding description information, for example, “third quarter high-efficiency staff employee award”, may also be added for red packet issuing, to distinguish and identify different red packets.

2. Object Allocation

In step 1606 above, the allocation operation of allocating the to-be-allocated objects to the allocation target may be executed in multiple manners. The object allocation manner is illustrated in detail below.

FIG. 21 is a flowchart of an object allocation according to an example embodiment of the present disclosure. As shown in FIG. 21, assuming that any allocation target logs onto a corresponding registered account on a mobile phone A, an interaction process of the server and the mobile phone A includes the following steps:

Step 2102: The server pushes a session message to the mobile phone A.

Step 2104: The mobile phone A presents a preset trigger identifier according to the received session message.

Step 2106: The mobile phone A detects a trigger operation.

Step 2108: The mobile phone A sends a trigger request to the server according to the detected trigger operation.

Step 2110: The server allocates to-be-allocated objects according to the received trigger request.

In the foregoing embodiment, the preset trigger identifier may be included in the session message. In this case, the mobile phone A extracts the preset trigger identifier from the session message and presents the preset trigger identifier on a preset page. Alternatively, the session message is merely a notification message, which is used to instruct the mobile phone A to present the preset trigger identifier.

By using a user Xiaobai in the embodiments shown in FIG. 19 to FIG. 20 as an example, a description is made with reference to a red packet issuing scenario. As shown in FIG. 19 to FIG. 20, the user Xiaobai is selected as a “recipient” in red packet issuing, i.e., an allocation target. Then, a registered account of the user Xiaobai is logged onto on the mobile phone A, and a message session page of a “hard working group” as shown in FIG. 22 is displayed. As shown in FIG. 22, the user Xiaobai may see a red packet message sent by a user Smile, wherein the red packet message includes a red packet icon.

In an embodiment, the preset trigger identifier may be a red packet icon as shown in FIG. 22. In this case, after the user Xiaobai taps on the red packet icon as shown in FIG. 22, the mobile phone A may use the “tap” as the trigger operation. As such, the mobile phone A initiates a trigger request to the server, so that the server allocates a corresponding red packet amount such as RMB 3,000.00 to the user Xiaobai.

In another embodiment, after the user Xiaobai taps on the red packet icon as shown in FIG. 22, a content as shown in FIG. 23 may be displayed on the current message session window in an overlay manner, that is, the preset trigger identifier may include the red packet icon as shown in FIG. 22 and an “open red packet” icon as shown in FIG. 23. In this case, after the user Xiaobai taps on the red packet icon in the FIG. 22 and the “open red packet” icon in the FIG. 23 respectively, the mobile phone A may use the “tap” performed by the user Xiaobai in FIG. 22 and FIG. 23 as the trigger operation. As such, the mobile phone A initiates a trigger request to the server, so that the server allocates a corresponding red packet amount such as RMB 3,000.00 to the user Xiaobai.

Certainly, FIG. 22 and FIG. 23 only show examples of the preset trigger identifier. In fact, the preset trigger identifier may also be presented in other forms. For example, as shown in FIG. 24, after the user Xiaobai taps on the red packet icon as shown in FIG. 22, information such as the preset trigger identifier “open red packet” icon may be presented at the top of the message session window. In this case, a subsequent operation manner of the user Xiaobai is similar to the processing manner of the mobile phone A. Details are not described here again.

In addition, in the embodiment shown in FIG. 23 or FIG. 24, the mobile phone A may further show information prior to the preset trigger identifier, for example, the mobile phone A shows that the allocation source is the user Smile and all the allocation targets. Moreover, upon a tap on “view receiving details”, the mobile phone A may further show the red packet receiving status of each allocation target, and the like.

In addition to the implementation shown in FIG. 23 or FIG. 24 where the red packet icon and the corresponding operations are all implemented in the message session window corresponding to the group, it is also possible to present the preset trigger identifier such as the red packet icon in a separate chat window, for example, in a “red packet receiving window” specially used for red packet issuing, or in an independent session window of a red packet issuing target such as an enterprise financial account and the user Xiaobai. For the process of presenting and operating the red packet icon in the window, reference may be made to the embodiment shown in FIG. 23 or FIG. 24. Details are not described here again.

3. Message Notification

In step 1606 above, the message related to the allocation operation may be notified to the notification target in multiple manners. The message notification manner is illustrated in detail below.

In the technical solution of the present disclosure, although the to-be-allocated objects are allocated only to the allocation target and are not allocated to the notification target, it is necessary to notify the notification target of the message related to the allocation operation, so that the notification target may be motivated correspondingly. For example, in an enterprise management or team management scenario, funds or material (i.e., “objects”) rewards are directly given to some employees (i.e., the allocation targets), and other unrewarded employees (i.e., the notification targets) are notified of the reward, so that the unrewarded employees may be motivated to study and work harder.

In this embodiment, the server may notify the notification target of the message in a default manner; or the server may also read a notification manner configured by the allocation source in the object allocation request, and notify the notification target of the message related to the allocation operation according to the notification manner. For the server, there are many optional notification manners (all these notification manners may be selected by the allocation source), which are illustrated below.

In an example embodiment, as shown in FIG. 25, similar to the embodiment shown in FIG. 23, the server may send a notification message to an electronic device logged onto by the notification target, for example, the notification target may be a user Baibai in FIG. 25. In this case, the electronic device may present a preset trigger identifier similar to the red packet icon as shown in FIG. 22. Then, after the user Baibai taps on the preset trigger identifier, an overlay page as shown in FIG. 25 may be shown. According to the comparison between FIG. 25 and FIG. 23, on the page presented to the user Baibai, only the message related to the allocation operation may be seen, where the message may include at least one of the following: the allocation source is the user Smile, all the allocation targets, the quantity of allocation objects, an object receiving status of each allocation target (which may be viewed by a tap on “view reception details”). Meanwhile, the “open red packet” icon is not shown in FIG. 25. Therefore, the user Baibai cannot be allocated with the bonus or any other object in the red packet.

Similar to FIG. 24, in the embodiment shown in FIG. 26, the overlay page may be shown at the top area of the message session window. Meanwhile, in the embodiment shown in FIG. 26, the “open red packet” icon is not shown either. Therefore, the user Baibai cannot be allocated with the bonus or any other object in the red packet.

In the foregoing embodiment, the message related to the allocation operation is presented by using the user Baibai's tap operation on a “red packet icon” similar to that shown in FIG. 22 as a predetermined trigger operation. In fact, the predetermined trigger operation may be in other forms. For example, the predetermined trigger operation may include: an operation of opening the message session window of the group. In this case, after the electronic device logged onto by the user Baibai receives the notification message sent by the server, once the user Baibai taps to enter the message session window of the corresponding group, the electronic device may automatically present the message related to the allocation operation in the manner as shown in FIG. 25 or FIG. 26. As such, it is ensured that the user Baibai may view the related message immediately, avoiding that the user Baibai needs to scroll the page manually to see and tap on the red packet icon when there are too many messages in the group.

Assuming that the user Smile issues a red packet to the “hard working group”, in all the foregoing embodiments, operations such as red packet receiving and message viewing are performed in the message session window of the group. In another example embodiment, the server may present the message related to the allocation operation to the notification target by using a manner irrelevant to the message session window of the group. For example, in one situation, the server may send to the notification target a communication message including the message related to the allocation operation, where the communication message may include various forms such as an instant communication message, a text message, or an email. In another situation, the server may further convert the message related to the allocation operation into a speech, and play the speech after setting up a session with the notification target. Alternatively, the server may simultaneously use multiple message notification manners provided in the present disclosure, to make sure that the notification target may receive and view the corresponding message content in time. For example, as shown in FIG. 19 to FIG. 20, if the allocation source enables a “lightening red packet” function in the red packet configuration page, a message notification operation of “text-message DING to group members at the same time” may be implemented, wherein the “text-message DING” refers to implementing message notification by sending a text message. Similarly, the allocation source may also select a manner such as “phone-call DING” or “in-application DING”, to implement a message notification operation based on a phone call, an instant communication message or another manner.

Similarly, the implementation of the “lightening red packet” above may also be applied to the object allocation process, that is, the red packet issuing process. For example, when the allocation source enables the “lightening red packet” based on “text-message DING” as shown in FIG. 19 or FIG. 20, on one hand, the server may notify the notification target by using a text message, and on the other hand, the server may send a text message to the allocation target, where the text message describes an issuing status and a receiving manner of the red packet. In this case, when receiving a text message that is returned by the allocation target according to the receiving manner, the server may allocate the red packet or other objects to the allocation target.

Alternatively, after the allocation source enables the “lightening red packet” based on “phone-call DING”, on one hand, the server may notify the notification target by making a phone call, and on the other hand, the server may make a phone call to the allocation target and announce, by voice, an issuing status and a receiving manner of the red packet in the phone call, such that the allocation target inputs a character string on a dial of a call interface accordingly or directly produces a voice speech. In this case, after the server receives the character string or voice speech, if the character string or a call content recognized from the voice speech accords with a preset content, the server may allocate the red packet or other objects to the allocation target.

The text message, phone call, or the like usually has a stronger prompt effect than internal prompt messages of APPs such as an instant messaging APP, and therefore may help the allocation target receive allocation objects such as the red packet in time, and also make sure that the notification target is notified in a timely and effective fashion.

FIG. 27 is a schematic structural diagram of an electronic device 2700 according to an example embodiment of the present disclosure. Referring to FIG. 27, on a hardware level, the electronic device 2700 includes a processor 2702, an internal bus 2704, a network interface 2706, a memory 2708, and a non-volatile storage 2710, and may include other hardware required for the service. The processor 2702 reads a corresponding computer program from the non-volatile storage 2710 to the memory 2708 and then runs the computer program, to form a service implementation apparatus 2712 on a logic level. Certainly, in addition to the software implementation, the present disclosure does not exclude other implementations, such as logic devices, or a combination of software and hardware. In other words, an entity executing the following processing procedure is not limited to logic units, and may also be hardware or logic devices. Both the memory 2708 and the non-volatile storage 2710 are examples of computer readable medium.

Referring to FIG. 28, in the software implementation, the service implementation apparatus 2800 includes one or more processor(s) 2802 or data processing unit(s) and computer readable media 2804. The terminal interaction apparatus 2800 may further include one or more input/output interface(s) 2806 and one or more network interface(s) 2808. The service implementation apparatus 2800 and the electronic device 2700 may be applied at a server.

The computer readable media 2808 may store therein a plurality of modules or units including:

a determining unit 2810, an extraction unit 2812 and a processing unit 2814, wherein:

the determining unit 2810 is configured to determine an allocation source, an allocation target, a notification target, and the quantity of to-be-allocated objects according to a received object allocation request;

the extraction unit 2812 is configured to extract to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source; and

the processing unit 2814 is configured to execute an allocation operation of allocating the to-be-allocated objects to the allocation target, and notify the notification target of a message related to the allocation operation.

Optionally, the determining unit 2810 is specifically configured to:

use a sender of the object allocation request as the allocation source, and read, from the object allocation request, the allocation target, the notification target and the quantity of to-be-allocated objects which are configured by the allocation source.

Optionally, the determining unit 2810 is specifically configured to:

use a sender of the object allocation request as the allocation source, and read the allocation target and the quantity of to-be-allocated objects from the object allocation request,

wherein when the object allocation request is sent by the allocation source for any group, the notification target is any other group member in the any group than the allocation source and the allocation target.

Optionally, the any group is a group in an instant messaging APP.

Optionally, the instant messaging APP is an EIM APP.

Optionally, the processing unit 2814 executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

pushing a session message to the allocation target, so that an electronic device logged onto by the allocation target presents a corresponding preset trigger identifier; and

when receiving a trigger request initiated by the allocation target, allocating the to-be-allocated object to the initiator of the request, wherein the trigger request is initiated by the electronic device when detecting a trigger operation of the allocation target for the preset trigger identifier.

Optionally, the processing unit 2814 executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

allocating a corresponding quantity of objects to each allocation target according to a default object allocation rule or an object allocation rule included in the object allocation request.

Optionally, the object allocation rule includes: equal allocation; or allocation based on a quantity configured by the allocation source for each allocation target.

Optionally, the processing unit executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

setting up a call with the allocation target, and announcing, by voice, a receiving manner of the to-be-allocated objects, so that the allocation target inputs a character string in a call interface or produces a voice speech; and

acquiring the character string or the voice speech, and allocating the to-be-allocated objects to the allocation target when the character string or a call content corresponding to the voice speech accords with a preset content.

Optionally, the processing unit 2814 notifies the notification target of the message related to the allocation operation in the following manner:

reading a notification manner that is configured by the allocation source in the object allocation request; and

notifying the notification target of the message related to the allocation operation according to the notification manner.

Optionally, the processing unit notifies the notification target of the message related to the allocation operation in the following manner:

pushing a notification message to the notification target, so that an electronic device logged onto by the notification target presents the message related to the allocation operation upon detecting a predetermined trigger operation.

Optionally, when the allocation source, the allocation target and the notification target belong to the same group, the predetermined trigger operation comprises: an operation of opening a message session window of the group.

In a typical configuration, a computer device includes one or more central processing units (CPUs), input/output interfaces, network interfaces, and memories.

The memory may include computer readable media such as a volatile memory, a Random Access Memory (RAM), and/or a non-volatile memory, e.g., a Read-Only Memory (ROM) or a flash RAM. The memory is an example of a computer readable medium.

The computer readable medium includes non-volatile and volatile media as well as movable and non-movable media, and may implement information storage by means of any method or technology. Information may be a computer readable instruction, a data structure, and a module of a program or other data. Examples of computer storage media include, but are not limited to, a phase change memory (PRAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), other types of RAMs, a ROM, an electrically erasable programmable read-only memory (EEPROM), a flash memory or other memory technologies, a compact disk read-only memory (CD-ROM), a digital versatile disc (DVD) or other optical storages, a cassette tape, a magnetic tape/magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, and may be used to store information accessible by the computing device. According to the definition in this text, the computer readable medium does not include transitory media, such as a modulated data signal and a carrier.

It should be further noted that, the terms “include”, “comprise” or their other variations are intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes the elements, but also includes other elements not clearly listed, or further includes inherent elements of the process, method, article or device. An element proceeded by “a”, “an”, or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or device that includes the element.

Described above are merely example embodiments of the present disclosure, which are not intended to limit the present disclosure. Any modification, equivalent replacement, improvement, or the like made within the spirit and principle of the present disclosure shall fall in the protection scope of the present disclosure.

The present disclosure may further be understood with clauses as follows.

Clause 1. A service implementation method comprising:

receiving a prompt request sent by an initiator;

generating an object allocation set according to object allocation information in the prompt request, the object allocation set comprising a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and

executing an allocation operation of allocating the object allocation set to a prompt target, and sending to the prompt target a prompt message related to the allocation operation.

Clause 2. The method of clause 1, wherein a prompt content of the prompt message comprises a manner in which the object allocation set is received.

Clause 3. The method of clause 1, wherein the executing the allocation operation of allocating the object allocation set to the prompt target, and sending to the prompt target the prompt message related to the allocation operation comprises:

executing a prompt operation for the prompt target, to send the prompt message to the prompt target; and

executing the allocation operation of allocating the object allocation set to the prompt target when the prompt message has been transmitted to the prompt target successfully.

Clause 4. The method of clause 3, further comprising:

receiving a response message returned by the prompt target in response to the prompt message,

wherein when a response content of the response message accords with a preset content, determining that the prompt message has been transmitted to the prompt target successfully.

Clause 5. The method of clause 4, wherein

when the prompt operation is setting up a call with the prompt target and playing the prompt message by voice, the response message is a voice speech produced by the prompt target or a character string input in a call interface; and

when the prompt operation is sending a communication message comprising the prompt message to the prompt target, the response message is a reply message of the prompt target in response to the communication message.

Clause 6. The method of clause 1, further comprising:

receiving an object allocation request from a candidate target; and

using the candidate target as the prompt target when the candidate target meets a preset condition.

Clause 7. The method of clause 6, wherein the preset condition comprises at least one of the following:

the candidate target is a registered user;

the candidate target is a member of a registered team; and

a total quantity of members of a team to which the candidate target belongs reaches a preset quantity.

Clause 8. The method of clause 1, further comprising:

before sending the prompt message to the prompt target, sending contact information of the initiator to the prompt target, so that the prompt target stores the contact information of the initiator in advance,

wherein the sending to the prompt target the prompt message related to the allocation operation comprises initiating a prompt operation to the prompt target in the name of the initiator, to send the prompt message to the prompt target.

Clause 9. The method of clause 1, wherein the executing the allocation operation of allocating the object allocation set to the prompt target comprises:

sending to the prompt target a communication message related to the object allocation set; and

allocating objects in the object allocation set to the prompt target when determining that the prompt target has executed a preset trigger operation on the communication message.

Clause 10. A service implementation apparatus comprising:

a first receiving unit configured to receive a prompt request sent by an initiator;

a generation unit configured to generate an object allocation set according to object allocation information in the prompt request, the object allocation set comprising a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; and

a processing unit configured to execute an allocation operation of allocating the object allocation set to a prompt target, and send to the prompt target a prompt message related to the allocation operation.

Clause 11. The apparatus of clause 10, wherein a prompt content of the prompt message comprises a manner in which the object allocation set is received.

Clause 12. The apparatus of clause 10, wherein the processing unit is specifically configured to:

execute a prompt operation for the prompt target, to send the prompt message to the prompt target; and

execute the allocation operation of allocating the object allocation set to the prompt target when the prompt message has been trans mined to the prompt target successfully.

Clause 13. The apparatus of clause 12, further comprising:

a second receiving unit configured to receive a response message returned by the prompt target in response to the prompt message,

wherein when a response content of the response message accords with a preset content, the processing unit determines that the prompt message has been transmitted to the prompt target successfully.

Clause 14. The apparatus of clause 13, wherein:

when the prompt operation is setting up a call with the prompt target and playing the prompt message by voice, the response message is a voice speech produced by the prompt target or a character string input in a call interface; and

when the prompt operation is sending a communication message comprising the prompt message to the prompt target, the response message is a reply message of the prompt target in response to the communication message.

Clause 15. The apparatus of clause 10, further comprising:

a third receiving unit configured to receive an object allocation request from a candidate target; and

a target determining unit configured to use the candidate target as the prompt target when the candidate target meets a preset condition.

Clause 16. The apparatus of clause 15, wherein the preset condition comprises at least one of the following:

the candidate target is a registered user;

the candidate target is a member of a registered team; and

a total quantity of members of a team to which the candidate target belongs reaches a preset quantity.

Clause 17. The apparatus of clause 10, further comprising:

a sending unit configured to, before the prompt message is sent to the prompt target, send contact information of the initiator to the prompt target, so that the prompt target stores the contact information of the initiator in advance,

wherein the processing unit sends to the prompt target the prompt message related to the allocation operation in the following manner including initiating a prompt operation to the prompt target in the name of the initiator, to send the prompt message to the prompt target.

Clause 18. The apparatus of clause 10, wherein the processing unit executes the allocation operation of allocating the object allocation set to the prompt target in the following manner:

sending to the prompt target a communication message related to the object allocation set; and

allocating objects in the object allocation set to the prompt target when determining that the prompt target has executed a preset trigger operation on the communication message.

Clause 19. A service implementation method comprising:

determining an allocation source, an allocation target, a notification target, and a quantity of to-be-allocated objects according to a received object allocation request;

extracting to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source; and

executing an allocation operation of allocating the to-be-allocated objects to the allocation target, and notifying the notification target of a message related to the allocation operation.

Clause 20. The method of clause 19, wherein the determining the allocation source, the allocation target, the notification target, and the quantity of to-be-allocated objects according to the received object allocation request comprises:

using a sender of the object allocation request as the allocation source, and reading, from the object allocation request, the allocation target, the notification target and the quantity of to-be-allocated objects which are configured by the allocation source.

Clause 21. The method of clause 19, wherein the determining the allocation source, the allocation target, the notification target, and the quantity of to-be-allocated objects according to the received object allocation request comprises:

using a sender of the object allocation request as the allocation source, and reading the allocation target and the quantity of to-be-allocated objects from the object allocation request,

wherein when the object allocation request is sent by the allocation source for a group, the notification target is any group member in the group other than the allocation source and the allocation target.

Clause 22. The method of clause 21, wherein the group is a group in an instant messaging application (APP).

Clause 23. The method of clause 22, wherein the instant messaging APP is an enterprise instant messaging (EIM) APP.

Clause 24. The method of clause 19, wherein the executing the allocation operation of allocating the to-be-allocated objects to the allocation target comprises:

pushing a session message to the allocation target, so that an electronic device logged onto by the allocation target presents a corresponding preset trigger identifier; and

when receiving a trigger request initiated by the allocation target, allocating the to-be-allocated object to the initiator of the request, wherein the trigger request is initiated by the electronic device when detecting a trigger operation of the allocation target for the preset trigger identifier.

Clause 25. The method of clause 19, wherein the executing the allocation operation of allocating the to-be-allocated objects to the allocation target comprises:

allocating a corresponding quantity of objects to each allocation target according to a default object allocation rule or an object allocation rule comprised in the object allocation request.

Clause 26. The method of clause 25, wherein the object allocation rule comprises: equal allocation; random allocation; or allocation based on a quantity configured by the allocation source for each allocation target.

Clause 27. The method of clause 19, wherein the executing the allocation operation of allocating the to-be-allocated objects to the allocation target comprises:

setting up a call with the allocation target, and announcing, by voice, a receiving manner of the to-be-allocated objects, so that the allocation target inputs a character string in a call interface or produces a voice speech; and

acquiring the character string or the voice speech, and allocating the to-be-allocated objects to the allocation target when the character string or a call content corresponding to the voice speech accords with a preset content.

Clause 28. The method of clause 19, wherein the notifying the notification target of the message related to the allocation operation comprises:

reading a notification manner that is configured by the allocation source in the object allocation request; and

notifying the notification target of the message related to the allocation operation according to the notification manner.

Clause 29. The method of clause 19, wherein the notifying the notification target of a message related to the allocation operation comprises:

pushing a notification message to the notification target, so that an electronic device logged onto by the notification target presents the message related to the allocation operation upon detecting a predetermined trigger operation.

Clause 30. The method of clause 29, wherein when the allocation source, the allocation target and the notification target belong to the same group, the predetermined trigger operation comprises an operation of opening a message session window of the group.

Clause 31. A service implementation apparatus comprising:

a determining unit configured to determine an allocation source, an allocation target, a notification target, and a quantity of to-be-allocated objects according to a received object allocation request;

an extraction unit configured to extract to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source; and

a processing unit configured to execute an allocation operation of allocating the to-be-allocated objects to the allocation target, and notify the notification target of a message related to the allocation operation.

Clause 32. The apparatus of clause 31, wherein the determining unit is specifically configured to:

use a sender of the object allocation request as the allocation source, and read, from the object allocation request, the allocation target, the notification target and the quantity of to-be-allocated objects which are configured by the allocation source.

Clause 33. The apparatus of clause 31, wherein the determining unit is specifically configured to:

use a sender of the object allocation request as the allocation source, and read the allocation target and the quantity of to-be-allocated objects from the object allocation request,

wherein when the object allocation request is sent by the allocation source for a group, the notification target is any group member in the group other than the allocation source and the allocation target.

Clause 34. The apparatus of clause 33, wherein the group is a group in an instant messaging application (APP).

Clause 35. The apparatus of clause 34, wherein the instant messaging APP is an enterprise instant messaging (EIM) APP.

Clause 36. The apparatus of clause 31, wherein the processing unit executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

pushing a session message to the allocation target, so that an electronic device logged onto by the allocation target presents a corresponding preset trigger identifier; and

when receiving a trigger request initiated by the allocation target, allocating the to-be-allocated object to the initiator of the request, wherein the trigger request is initiated by the electronic device when detecting a trigger operation of the allocation target for the preset trigger identifier.

Clause 37. The apparatus of clause 31, wherein the processing unit executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

allocating a corresponding quantity of objects to each allocation target according to a default object allocation rule or an object allocation rule comprised in the object allocation request.

Clause 38. The apparatus of clause 37, wherein the object allocation rule comprises: equal allocation; or allocation based on a quantity configured by the allocation source for each allocation target.

Clause 39. The apparatus of clause 31, wherein the processing unit executes the allocation operation of allocating the to-be-allocated objects to the allocation target in the following manner:

setting up a call with the allocation target, and announcing, by voice, a receiving manner of the to-be-allocated objects, so that the allocation target inputs a character string in a call interface or produces a voice speech; and

acquiring the character string or the voice speech, and allocating the to-be-allocated objects to the allocation target when the character string or a call content corresponding to the voice speech accords with a preset content.

Clause 40. The apparatus of clause 31, wherein the processing unit notifies the notification target of the message related to the allocation operation in the following manner:

reading a notification manner that is configured by the allocation source in the object allocation request; and

notifying the notification target of the message related to the allocation operation according to the notification manner.

Clause 41. The apparatus of clause 31, wherein the processing unit notifies the notification target of the message related to the allocation operation in the following manner:

pushing a notification message to the notification target, so that an electronic device logged onto by the notification target presents the message related to the allocation operation upon detecting a predetermined trigger operation.

Clause 42. The apparatus of clause 41, wherein when the allocation source, the allocation target and the notification target belong to the same group, the predetermined trigger operation comprises an operation of opening a message session window of the group.

Claims

1. A method comprising:

receiving a prompt request sent by an initiator;

generating an object allocation set according to object allocation information in the prompt request, the object allocation set comprising a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator;

allocating the object allocation set to a prompt target; and

sending to the prompt target a prompt message related to the allocation operation.

2. The method of claim 1, wherein a prompt content of the prompt message comprises a manner in which the object allocation set is received.

3. The method of claim 1, wherein an object includes a virtual item.

4. The method of claim 1, wherein the sending to the prompt target the prompt message related to the allocation operation comprises:

executing a prompt operation for the prompt target to send the prompt message to the prompt target; and

allocating the object allocation set to the prompt target when the prompt message has been transmitted to the prompt target successfully.

5. The method of claim 4, further comprising:

receiving a response message returned by the prompt target in response to the prompt message,

wherein when a response content of the response message accords with a preset content, determining that the prompt message has been transmitted to the prompt target successfully.

6. The method of claim 5, wherein

the prompt operation is setting up a call with the prompt target and playing the prompt message by voice; and

the response message is a voice speech produced by the prompt target or a character string input in a call interface.

7. The method of claim 5, wherein:

the prompt operation is sending a communication message comprising the prompt message to the prompt target; and

the response message is a reply message of the prompt target in response to the communication message.

8. The method of claim 1, further comprising:

receiving an object allocation request from a candidate target; and

using the candidate target as the prompt target when the candidate target meets a preset condition.

9. The method of claim 6, wherein the preset condition comprises at least one of the following:

the candidate target is a registered user;

the candidate target is a member of a registered team; and

a total quantity of members of a team to which the candidate target belongs reaches a preset quantity.

10. The method of claim 1, further comprising:

before sending the prompt message to the prompt target, sending contact information of the initiator to the prompt target, so that the prompt target stores the contact information of the initiator in advance,

wherein the sending to the prompt target the prompt message related to the allocation operation comprises initiating a prompt operation to the prompt target in the name of the initiator, to send the prompt message to the prompt target.

11. The method of claim 1, wherein the allocating the object allocation set to the prompt target comprises:

sending to the prompt target a communication message related to the object allocation set; and

allocating objects in the object allocation set to the prompt target when determining that the prompt target has executed a preset trigger operation on the communication message.

12. A method comprising:

determining an allocation source, an allocation target, a notification target, and a quantity of to-be-allocated objects according to a received object allocation request;

extracting to-be-allocated objects corresponding to the quantity of to-be-allocated objects from an object set corresponding to the allocation source;

allocating the to-be-allocated objects to the allocation target; and

notifying the notification target of a message related to the allocation operation.

13. The method of claim 12, wherein the determining the allocation source, the allocation target, the notification target, and the quantity of to-be-allocated objects according to the received object allocation request comprises:

using a sender of the object allocation request as the allocation source, and reading, from the object allocation request, the allocation target, the notification target and the quantity of to-be-allocated objects which are configured by the allocation source.

14. The method of claim 12, wherein the determining the allocation source, the allocation target, the notification target, and the quantity of to-be-allocated objects according to the received object allocation request comprises:

using a sender of the object allocation request as the allocation source, and reading the allocation target and the quantity of to-be-allocated objects from the object allocation request,

wherein when the object allocation request is sent by the allocation source for a group, the notification target is any group member in the group other than the allocation source and the allocation target.

15. The method of claim 12, wherein the allocating the to-be-allocated objects to the allocation target comprises:

pushing a session message to the allocation target, so that an electronic device logged onto by the allocation target presents a corresponding preset trigger identifier; and

when receiving a trigger request initiated by the allocation target, allocating the to-be-allocated object to the initiator of the request, wherein the trigger request is initiated by the electronic device when detecting a trigger operation of the allocation target for the preset trigger identifier.

16. The method of claim 12, wherein the allocating the to-be-allocated objects to the allocation target comprises:

allocating a corresponding quantity of objects to each allocation target according to a default object allocation rule or an object allocation rule comprised in the object allocation request.

17. The method of claim 16, wherein the allocating the to-be-allocated objects to the allocation target comprises:

setting up a call with the allocation target, and playing a receiving manner of the to-be-allocated objects by voice, so that the allocation target inputs a character string in a call interface or produces a voice speech;

acquiring the character string or the voice speech; and

allocating the to-be-allocated objects to the allocation target when the character string or a call content corresponding to the voice speech accords with a preset content.

18. The method of claim 12, wherein the notifying the notification target of the message related to the allocation operation comprises:

reading a notification manner that is configured by the allocation source in the object allocation request; and

notifying the notification target of the message related to the allocation operation according to the notification manner.

19. The method of claim 12, wherein the notifying the notification target of a message related to the allocation operation comprises:

pushing a notification message to the notification target, so that an electronic device logged onto by the notification target presents the message related to the allocation operation upon detecting a predetermined trigger operation.

20. An apparatus comprising:

one or more processors; and

one or more computer readable storing thereon computer-readable instructions that, when executed by the one or more processors, cause the one or more processors to perform acts comprising: receiving a prompt request sent by an initiator; generating an object allocation set according to object allocation information in the prompt request, the object allocation set comprising a preset quantity of objects specified by the object allocation information, and the preset quantity of objects being extracted from an object set corresponding to the initiator; allocating the object allocation set to a prompt target; and sending to the prompt target a prompt message related to the allocation operation.