Methods, terminals, and servers for sending service data groups.

Abstract

------15 / 03 / 2561------(OCR) ------------

Description

Methods, terminals, and servers for sending business data in groups This invention claims priority to the prior application filed on August 21, 2015, entitled "Method and Apparatus for Group Transmission of Business Data" with application number 201510520668.3, and the prior application filed on July 29, 2015, entitled "A Method for Processing Information and Initiating Device, Server, and Participating Device" with application number 201510454782.0, the contents of which are incorporated herein by reference. Technical Field This invention relates to the field of computer technology, and in particular to a method and apparatus for sending business data in bulk. Background Technology In traditional social networking applications, users typically need to share business data. For example, business data can be messages (such as e-cards), files, pictures (such as photographs), financial data (such as numeric data representing actual financial amounts in online banking accounts or third-party payment accounts), or virtual financial data (such as numeric data representing virtual currency in online game accounts or social networking application accounts). However, in traditional technologies, the sharing of business data between users is usually based on social relationship chains (such as friends, group members, alumni, and people you may know). In other words, users can only share business data with users within their social relationship chains. To send business data to strangers—that is, users who are not in the social relationship chain of the social network application—it is necessary to first add each stranger as a friend, then create a group, add the added strangers to the newly created group, and then send the business data through the group. Therefore, in traditional social networking applications, when a user sends business data to multiple strangers, the user needs to perform many operations such as adding friends and creating groups to complete the mass sending operation, resulting in insufficient convenience of operation. Summary of the Invention Therefore, to address the aforementioned issues in traditional social network applications where users send messages to multiple... When sending business data to strangers in bulk, the user needs to perform many operations such as adding friends and creating groups to complete the bulk sending operation, which leads to insufficient convenience. Therefore, a new method for sending business data in bulk is proposed. A method for sending business data in bulk includes: A pairing request is broadcast via short-range wireless signal; Pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request; Receive input business data; A business data mass transmission request is generated based on the business data and sent to the server. The business data is then sent to the server, and the server sends the business data to the terminal corresponding to the recipient account according to the business data mass transmission request. Furthermore, to address the issue of insufficient convenience in traditional social network applications where users need to perform numerous operations such as adding friends and creating groups to send business data to multiple strangers, a business data group sending terminal is proposed. A terminal, comprising: Memory, which stores computer-readable program code; and A processor for executing the computer-readable program code to perform the following operations: A pairing request is broadcast via short-range wireless signal; Pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request; Receive input business data; A business data mass transmission request is generated based on the business data and sent to the server. The business data is then sent to the server, and the server sends the business data to the terminal corresponding to the recipient account according to the business data mass transmission request. Furthermore, to address the issue of insufficient convenience in traditional social network applications where users need to perform numerous actions such as adding friends and creating groups to send business data to multiple strangers, a new method is proposed. Methods for forwarding business data between terminals. A method for forwarding service data between terminals, the method comprising: Obtain the sender's account and the receiver's account, wherein the receiver's account is within the range of the short-range wireless signal of the terminal corresponding to the sender's account and accepts the pairing request broadcast by the terminal corresponding to the sender's account. Receive a business data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain business data according to the business data mass transmission request; The business data is sent to the terminal corresponding to the recipient's account. Furthermore, to address the issue of insufficient convenience in traditional social network applications where users need to perform numerous operations such as adding friends and creating groups to send business data to multiple strangers, a server for forwarding business data between terminals is proposed. A server, characterized in that it comprises: Memory, which stores computer-readable program code; and A processor for executing the computer-readable program code to perform the following operations: Obtain the sender's account and the receiver's account, wherein the receiver's account is within the range of the short-range wireless signal of the terminal corresponding to the sender's account and accepts the pairing request broadcast by the terminal corresponding to the sender's account. Receive a business data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain business data according to the business data mass transmission request; The business data is sent to the terminal corresponding to the recipient's account. After adopting the aforementioned method and apparatus for sending group service data, when the initiator sends service data to strangers (i.e., users not on the initiator's social network), the initiator does not need to add multiple strangers as friends sequentially. Instead, they can directly broadcast a pairing identifier over a short distance using a short-range wireless signal, thus establishing a connection with multiple strangers. In other words, terminals with the same pairing identifier as the initiator's can receive the group service data sent by the initiator, eliminating the cumbersome steps of adding and verifying friends, thereby improving operational convenience. Furthermore, in the aforementioned method and apparatus for sending business data in bulk, the initiator does not need to create groups for multiple recipient accounts to send business data. Instead, the server can determine the user account matching the recipient account's identity based on the pairing identifier, and then send the business data to the user account that is the recipient account. This eliminates the initiator's need to create groups for bulk sending, thereby improving operational convenience. Attached Figure Description To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. in: Figure 1 is a network diagram of a group data transmission system for a service in one embodiment; Figure 2 is a timing diagram of the interaction process between the sender, receiver and server in the group sending system of the above business data; Figure 3 is a flowchart of a method for sending service data in a group according to an embodiment; Figure 4 is a flowchart of a method for receiving mass-sent service data in one embodiment; Figure 5 is a flowchart of a method for forwarding service data between terminals in one embodiment; Figure 6 is a schematic diagram of the display interface for inputting data and sending commands in a red envelope application scenario; Figure 7 is a schematic diagram showing the display interface of the recipient's account in an application scenario of sending red envelopes; Figure 8 is a schematic diagram of the business data input interface in an application scenario of sending red envelopes; Figure 9 is a schematic diagram of the interface showing the process of distributing red envelopes in an application scenario; Figure 10 is a schematic diagram of the structure of a group data transmission device in one embodiment; Figure 11 is a schematic diagram of the structure of a device for receiving mass-sent service data in one embodiment; Figure 12 is a schematic diagram of a device for forwarding service data between terminals in one embodiment; Figure 13 is a flowchart of a group transmission method for service data in another embodiment; Figure 14 is a flowchart of a group transmission method for service data in another embodiment; Figure 15 is a flowchart of a method for receiving mass-sent service data in another embodiment; Figure 16 is a flowchart of a method for receiving mass-sent service data in another embodiment; Figure 17 is a schematic diagram of the structure of a group transmission device for service data in another embodiment; Figure 18 is a schematic diagram of a device for forwarding service data between terminals in another embodiment. Detailed Implementation The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention. Based on this, in order to solve the problem mentioned above in traditional social network applications where users need to perform many operations such as adding friends and creating groups to complete the mass sending operation when sending business data to multiple strangers, resulting in insufficient convenience of operation, a mass sending mechanism for business data is proposed in one embodiment, as shown in Figure 1. The mass sending mechanism for business data is based on the computer system shown in Figure 1. The computer system includes a terminal 10 of the sender account for mass sending of business data, a server 20 responsible for forwarding business data, and a terminal 30 of the receiver account for mass sending of business data. The group data transmission mechanism consists of three parts: a group data transmission method running on terminal 10 of the sender's account; a method for forwarding business data between terminals running on server 20; and a method for receiving the group data on terminal 30 of the receiver's account. Terminal 10 of the sender's account and terminal 30 of the receiver's account can be smartphones, tablets, or other computer systems based on the von Neumann architecture equipped with short-range wireless communication components, such as Near Field Communication (NFC), Bluetooth, Wi-Fi, or Zigbee. Server 20, responsible for forwarding business data, can be a server device for social networking applications. The aforementioned method for sending service data in bulk on terminal 10 running on the sender's account, the method for forwarding service data between terminals running on server 20, and the method for receiving bulk service data on terminal 30 running on the receiver's account can all rely on computer programs. Furthermore, the method for sending service data in bulk on terminal 10 running on the sender's account and the method for receiving bulk service data on terminal 30 running on the receiver's account can be based on client programs of social networking applications, and the method for forwarding service data between terminals running on server 20 can be based on server programs of social networking applications. Specifically, the interaction process of the group sending mechanism for this service data can be shown in Figure 2. The group sending method for service data on terminal 10 running on the sender's account can be shown in Figure 3, including: Step S102: Receive data mass transmission command, generate pairing identifier, and broadcast the pairing identifier via short-range wireless signal. If a user sending business data wishes to send it to strangers in bulk, they can input a bulk data sending command into the smart terminal to activate the bulk data sending function. In this embodiment, before sending the business data in bulk, the sender needs to log in to the server using their social networking application account on terminal 10; this logged-in user account is the sender's account. After the sender inputs the bulk data sending command, the terminal generates a pairing identifier. This pairing identifier can be used to establish a mapping relationship with the terminals of strangers. The target of the business data sent in bulk by the terminal corresponding to the sender's account is the terminal that stores other user accounts with the same pairing identifier. In this embodiment, after the sender's terminal generates a pairing identifier, it can send the pairing identifier to other user accounts' corresponding terminals via short-range wireless signals. These short-range wireless signals can be NFC, Bluetooth, Wi-Fi (Wireless Local Area Network), or Zigbee signals, all of which propagate within a range of tens of meters. For example, if the smart terminal has an NFC chip installed, it can broadcast the pairing identifier to other terminals via NFC signals. Other users can then establish a connection with the sender's terminal by bringing their terminals close to the sender's terminal, thereby receiving the pairing identifier. The user account logged into the social networking application on that terminal can then become the receiving account. Step S104: Upload the pairing identifier to the server and receive the receiver account corresponding to the pairing identifier returned by the server. In this embodiment, the terminal with the sender's account can upload a pairing identifier to the server via a pairing initiation request, and the server can then receive the pairing identifier. The pairing initiation request may also include the sender's account, or the server can obtain a session object containing the sender's account through an established connection with the terminal with the sender's account, and then retrieve the sender's account through the session object. As mentioned earlier, a terminal that makes close contact with the sender's account and obtains the same pairing identifier as the sender's account by detecting short-range wireless signals can also establish a connection with the server. The terminal can then send the same pairing identifier to the server by sending a pairing request. The server can then find the user account with the same pairing identifier as the sender's account by comparing the pairing identifiers. This user account is the recipient account in the mass data transmission. In other words, even if a user's terminal is near the sender's account and obtains a pairing identifier, if the user's terminal is not logged into a user account or is not connected to the network and cannot establish a connection with the server, that is, if the server cannot receive the pairing request or the received pairing request does not contain a user account, the user's terminal still cannot receive business data as a recipient of business data. Correspondingly, if the user's terminal obtains a pairing identifier and establishes a connection with the server by being close to the sender's account, and successfully uploads a pairing request containing the pairing identifier, and the server obtains the user account logged in on the user's terminal, then regardless of whether the user account is in a social relationship chain with the sender's account (which includes cases of strangers relative to the sender), it can use the user account as a recipient account to receive mass-sent business data. After receiving the recipient account from the server, the sender's terminal can display the recipient account in the pairing status display interface. It's important to note that the process of the sender's terminal receiving recipient accounts from the server can be continuous. That is, each time the server receives a user account containing the same pairing identifier as the sender's account, it caches it as a recipient account and returns it to the sender's terminal. The sender's terminal can then continuously receive multiple recipient accounts and add them to the pairing status display interface for the initiator to view. The initiator can view all recipient accounts in the pairing display interface and can delete a selected recipient account. The sender's terminal will then send the deleted recipient account to the server, which will delete it from its cache. The server will then prevent the initiator from sending any subsequent mass-sent business data to that user account. Step S106: Receive the input service data. It can display a business data input interface for the initiator to enter business data. The input business data can be in various formats, such as files, images, and numerical values. For example, in one application scenario, if the initiator wants to send files from a certain cloud drive to multiple other users, the initiator can enter the network storage path of the files in that cloud drive. In another application scenario, if the initiator wants to send locally stored photos to multiple users, the business data input interface can provide a photo selection box. The initiator can first select a local photo file as the business data input, then upload the photo file to a server or third-party storage server or other network storage location, and receive the returned network storage information for the photo file. The storage path is then used, and the network storage address is used as the input for business data. In a mobile payment application scenario, business data can also be numerical, such as payment amount or transfer amount. This business data is numerical data that can be transferred between the sender's account and the recipient's account. It should be noted that the execution order of step S106, S102, and S104 does not need to be strictly limited. The initiator can first generate a pairing identifier by sending a mass data input command to find the recipient's account terminal, and then input business data in the displayed business data input interface; alternatively, the initiator can input business data in the displayed business data input interface, generate a pairing identifier by sending a mass data input command, and find the recipient's account terminal. These two methods do not conflict. Step S108: Generate a business data mass transmission request based on the business data and send it to the server, and send the business data to the server. The server then sends the business data to the terminal corresponding to the recipient account based on the business data mass transmission request. On the other hand, the method for forwarding service data between terminals by the server can be illustrated in Figure 4, including: Step S202: Receive the uploaded pairing identifier and obtain the sender account corresponding to the pairing identifier. Step S204: Receive a pairing join request. If the pairing join request includes the pairing identifier, obtain the user account carried in the pairing join request as the receiver account. The pairing identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the receiver account via a short-range wireless signal. Step S206: Receive the business data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain the business data according to the business data mass transmission request. Step S208: Send the service data to the terminal corresponding to the recipient account. The method for receiving bulk data executed by the recipient's account terminal can be shown in Figure 5, including: Step S302: Detect short-range wireless signals and obtain the pairing identifier carried by the short-range wireless signals. Step S304: Obtain the recipient account, upload the pairing identifier to the server along with the recipient account, and have the server find the sender account corresponding to the pairing identifier and the business data uploaded by the sender account. In other words, after the initiator inputs the data mass transmission command, generates a pairing identifier, and uploads it to the server, the pairing identifier can be broadcast within a small area via short-range wireless signals. Other users who wish to receive the mass-transmitted service data can bring their handheld devices (which need to be logged in with a user account first) close to the sender's phone to detect the short-range wireless signal, extract the pairing identifier carried in the signal, and generate a pairing request to send to the server. At this point, the logged-in user account corresponding to the pairing request becomes the receiver's account. Preferably, before sending the pairing request to the server, the recipient's terminal can display a verification box, requiring the recipient to enter verification information corresponding to the pairing identifier. For example, if the pairing identifier is a random number "32452", the initiator can observe this identifier and verbally inform a user. If that user wishes to become the recipient, their terminal will display a verification box before sending the pairing request to the server, requiring the user to manually enter "32452" (verbally provided by the initiator). If the verification is successful, the pairing request can continue to be sent to the server, meaning the recipient is the user invited by the initiator, not a user who "overheard the pairing identifier". Step S306: Receive business data uploaded to the server by the sender's account. In the example above, if the business data input by the initiator is a network storage address or numerical data used for online payment, the business data can be sent to the server via a business data bulk request. If the business data input by the initiator is a local photo, audio file, or other file, it can first be uploaded to a network storage location such as a server or a third-party storage server, and the network storage path of the photo file can be obtained. Then, a business data bulk request can be generated based on the returned network storage path corresponding to the actual business data and sent to the server. In one embodiment, after receiving a request to send business data in bulk, the server can extract the business data or the network storage path of the business data according to the request, and then send it to the terminal of the recipient account stored in the cache. The terminal corresponding to the recipient account can then download the business data according to the network storage path. In one application scenario, if the initiator inputs the network storage path of a file on a cloud drive, the server can then send this network storage path to all recipient accounts, and the recipient accounts' terminals can download the corresponding file based on the network storage path. In another application scenario, the initiator inputs locally stored photos, audio, or video data, while the bulk data transmission request includes the network storage of the input photos, audio, or video. If the path is specified, the server can send the network storage path to all recipient accounts, and the recipient accounts' terminals can then download the corresponding photos, audio, or video according to the network storage path. In another embodiment, the data type of the business data can be numerical. The step of receiving input business data further includes: The server receives input business data of numerical type corresponding to the sender's account, and then performs business data transfer between the sender's account and the receiver's account based on the business data. Business value transfer refers to transferring numerical business data from the sender's account attribute value to the receiver's account attribute value. For example, in a mobile payment application scenario, if the business data is a payment amount of 100, then business value transfer means deducting 100 from the sender's account payment balance and then adding 100 to the receiver's account payment balance. This operation is transactional; if deducting 100 from the sender's account payment balance and then adding 100 to the receiver's account payment balance fails, a rollback operation is performed, returning the deducted 100 to the sender's account payment balance. For example, in one application scenario, the initiator can input the business data as a value of 100 for each recipient account. After inputting the data mass transmission command, the initiator can sequentially transmit pairing identifiers with the terminals of multiple users via short-range wireless communication. In this way, a value of 100 can be added to the payment balance of each recipient account, while the payment balance of the sender account is deducted by 100 each time a recipient account is added. In this embodiment, after the server completes the transfer of transaction value between the sender's account and the receiver's account, it can send a notification message corresponding to the transaction value transfer to the receiver's account. For example, in the above case, after the transaction value transfer is completed, if the receiver's account balance increases by 100, the server can notify the receiver's terminal that their payment balance has increased by 100. Furthermore, when the initiator inputs business data, the number of copies can also be input. That is, the terminal of the sender's account can receive the input number of copies during the process of receiving the input business data of data type corresponding to the sender's account, which is numerical. The step of generating a business data bulk sending request based on the business data and sending it to the server can be achieved by adding the number of copies parameter to the business data bulk sending request. The server can divide the business data into sub-data according to the number of parts parameter. The value set is used to extract sub-values ​​from the sub-value set for the recipient account to perform business value transfer. In this context, dividing business data into multiple parts allows for better management of the data. For example, in a scenario of sending group red envelopes (where the initiator generates an electronic red envelope using a portion of the payment balance of their logged-in sender account, containing payment data, and then establishes a correspondence between the electronic red envelope data and other users, with the server transferring the payment value from the electronic red envelope to the payment balance of other users' accounts), as shown in Figure 6, the initiator can input a data group sending command by clicking "Face-to-Face Red Envelope" on their mobile phone interface. The mobile phone interface then displays a message indicating that NFC is enabled and prompting for close contact with other terminals (i.e., "tap" with other terminals). At this point, a pairing identifier is generated on the initiator's mobile phone, and this pairing identifier is broadcast to other nearby terminals via short-range wireless signals such as NFC. Once a nearby mobile phone detects the NFC signal and extracts the pairing identifier, it can send a pairing request containing that identifier to the server. The server uses this pairing identifier to identify the user account that initiated the request as the recipient account, thus establishing a mapping between the sender and recipient accounts. The server can then return the recipient account to the sender's terminal, which can then display the recipient user's information. For example, as shown in Figure 7, which illustrates the interface displaying the recipient's account on the initiator's terminal, the user accounts such as vivi and coco are the recipient accounts returned by the server. In other words, the initiator can first send a pairing identifier to vivi via NFC. After receiving the pairing identifier, vivi sends it to the server, thus becoming the initiator's recipient account. The server can then send the recipient account vivi to the initiator's terminal. Then, coco also receives the pairing identifier and sends it to the server, thus also becoming the initiator's recipient account. The server can then continue to send the recipient account coco to the initiator's terminal. Furthermore, in this embodiment, a relationship chain addition instruction can be received through a display interface showing the recipient's account, and the recipient's account selected on the display interface corresponding to the relationship chain addition instruction can be obtained. A relationship chain addition request is generated based on the selected recipient's account and sent to the server, whereby the server establishes a relationship chain mapping between the sender's account and the selected recipient's account. In other words, if the initiator wants to add Coco as a friend, they can select Coco's avatar on the display screen showing the recipient's account, and then submit a friend request through the pop-up menu. This makes it convenient. It facilitates the establishment of social connections among users. As shown in Figure 8, the initiator can input business data by clicking the "Send Red Envelope" icon on the interface. After the user clicks the "Send Red Envelope" icon, the business data input interface will be displayed. As shown in Figure 7, the business data input interface in this application scenario is the red envelope amount input interface. The "number of red envelopes" entered by the initiator is the number of envelopes parameter, and the "total amount" is the input business data, which is the numerical payment value contained in the electronic red envelope. After the initiator submits the "number of red envelopes" and "total amount" to the server, the server can obtain the number of envelopes parameter and business data. Preferably, after receiving the input business data of numerical data corresponding to the sender account, an authentication window can be displayed. The authentication information corresponding to the sender account can be obtained through the authentication window and sent to the server for verification. When the server returns a message indicating that the verification has passed, the step of generating a business data mass transmission request based on the business data and sending it to the server is executed. Referring to Figure 8, for payment-type business data as in the example above, the initiator needs to verify their identity before confirming the mass distribution. The identity verification information can be the password corresponding to the sender's account or the third-party payment account and password corresponding to the sender's account. Only after successful verification will the server be allowed to deduct the corresponding business data from the sender's payment balance. The server can divide the business data into sub-value sets according to the number of portions parameter. For example, if the total amount is 200 and the number of red envelopes is 10, the server can divide the business data of 200 into 10 portions. The division method can be equal distribution (in the case of distributing fixed red envelopes, the initiator can set the amount of the red envelope at once, thereby improving convenience), random distribution (in the case of grabbing red envelopes, the amount of red envelopes that each recipient can get is a random value, increasing fun), or a preset distribution rule (for example, allocating more sub-values ​​to female recipients, less sub-values ​​to male recipients, or allocating more sub-values ​​to recipients whose age is less than a threshold, etc.). After the server divides the red envelopes, for example, in the above example, it divides the business data 200 into 10 equal parts, and the set of sub-values ​​contains 10 sub-values ​​of 20. Then, each time the server receives a pairing request and establishes a recipient account, it can extract the sub-value of 20 from the set of sub-values, and then transfer the business value of 20 between the sender account and the recipient account (in other embodiments, the 20 value can be transferred not only from the sender's account's payment balance to the recipient's payment balance, but also from the recipient's account's payment balance to the sender's account). The payment balance in the sender's account, for example, in the application scenario of asking for a wallet. Correspondingly, the sender's terminal can also receive the receiver account whose reception status is "received" returned by the server, and display a prompt effect for the received receiver account on the display interface. For example, as shown in Figure 9, after the initiator of the red envelope distribution enters the number of red envelopes and the total amount on the sender's account terminal and passes identity verification, the business data mass sending request is sent to the server. Then, the number of red envelopes and the animation of the red envelopes flying to the recipient's account avatar can be displayed on the display interface showing the recipient's account. If the sender's account terminal receives the reception status returned by the server as received by the recipient account vivi, then the animation of vivi's avatar receiving the flying red envelope is displayed to indicate to the initiator vivi that she has received it. Correspondingly, the recipient's terminal can also display the avatars of the sender's account and other recipient accounts. After the server completes the transfer of the transaction value to the recipient's account, a notification message is sent to that recipient's account, which can be displayed on the recipient's terminal. For example, on vivi's phone screen, the avatars of the initiator "Bey" and another recipient, Coco, can also be displayed. After the server completes the process of transferring the payment value of 20 from the initiator "Bey's" account to the recipient vivi's account, vivi's phone screen can then display that vivi received a red envelope with a value of 20. In another application scenario for distributing electronic red envelopes, a "red envelope grabbing" method can be used. That is, after the initiator inputs the number of shares parameter 10 and the business data 200 and uploads it to the server, the server can randomly divide the value 200 into 10 sub-values ​​of random size to form a sub-value set. In this application scenario, the recipient's terminal, such as the Vivi or Coco phones in the previous example, can display a server-sent notification message on its screen, showing information such as a total amount of 200 and 10 red envelopes, along with an icon or button for grabbing the red envelopes. When the recipient presses or triggers this icon or button, they have entered a request to receive the red envelope. In other words, the recipient's terminal can receive the entered request to receive the red envelope, upload it to the server, and include a timestamp. The server can then extract sub-values ​​from the business data based on the order of the received timestamps and transfer the business data between the sender's account and the recipient's account. Specifically, the server can receive the request to receive the red envelope uploaded by the terminal corresponding to the recipient's account and extract the first timestamp; then, according to the order of the first timestamps, it sequentially sends the business data to the terminal corresponding to the recipient's account. In the above scenario, the recipient accounts can be sorted using the first timestamp, and then the business data can be sent to the terminal corresponding to the recipient account in sequence, thus avoiding chaos and disorder. For example, in the previous example, both vivi and coco are recipient accounts. Vivi clicked the "grab a red envelope" icon or button first, followed by coco. Therefore, vivi's phone uploaded the request to receive the red envelope to the server first. Since the server received the request earlier than coco, a sub-value is first extracted from the sub-value set (corresponding to a set of 10 electronic red envelopes). One electronic red envelope is randomly selected from these 10 and sent to vivi. After sending one electronic red envelope to vivi, the request to receive the red envelope uploaded by coco can be processed, and another electronic red envelope is extracted from the remaining 9 red envelopes and sent to coco. In other words, the recipient account that uploaded the request to receive the red envelope first is given priority in being assigned a sub-value from the sub-value set for business value transfer. Furthermore, in this embodiment, if the number of copies input by the initiator is 10, and the number of recipient accounts is greater than 10, some recipient accounts may not receive the corresponding sub-values ​​in the sub-value set. To better send mass data in this situation, the following solution can be implemented: In the first approach, the server can obtain the number of recipients for each recipient account when retrieving the user account carried in the pairing request as the recipient account. Additionally, when performing the step of extracting sub-values ​​from the sub-value set and transferring business values ​​to the recipient account, the server can also determine whether the number of recipients is greater than the number of copies parameter. If so, a receiving failure message is returned to the recipient account. In other words, in application scenarios where the initiator first inputs business data and then generates a matching identifier to match the recipient's account on the terminal, if the server detects that the number of recipients exceeds the input number parameter, it will return a message indicating that data reception failed to occur to the recipient's account on the terminal. For example, if Coco is the 11th recipient account, then after Coco clicks the "grab red envelope" button, a message will appear indicating that all red envelopes have been claimed. The above solution allows for better management of multiple business data sets. Furthermore, when the number of recipients exceeds the number of sets parameter, a message indicating that data reception failed is returned to the recipient's account terminal, preventing recipients from blindly making repeated requests because they are unaware that the business data is empty. In the second approach, when the server sends the business data to the terminal corresponding to the recipient account, it can also determine whether the set of sub-values ​​is empty. If so, it returns a message indicating that the reception failed to the recipient account. In other words, for each request received by the server, a sub-value is extracted from the sub-value set, and the business value is transferred based on this sub-value. When a sub-value is extracted from the sub-value set... When the data transfer process is complete and the set of sub-values ​​is empty (meaning all numeric business data has been transferred), the server can return a message indicating that data reception failed to occur to the recipient's account. For example, in the example above, if the server has already transferred all business data totaling 200 (meaning all 10 electronic red envelopes have been distributed) when retrieving sub-values ​​for Coco, then a message indicating that all red envelopes have been claimed can be displayed after Coco clicks the "Claim Red Envelope" button. The above solution also allows for better management of multiple business data sets. Furthermore, when the number of recipients exceeds the number of sets parameter, a message indicating that data reception failed is returned to the recipient's account terminal, preventing recipients from blindly making repeated requests because they are unaware that the business data is empty. Furthermore, when the server receives the business data mass transmission request, it can also obtain a second timestamp of the received business data mass transmission request; The server can also determine whether the second timestamp has expired. If so, it retrieves the remaining sub-values ​​from the sub-value set, returns the remaining sub-values ​​to the sender's account, and sends a prompt message to the terminal corresponding to the sender's account. In the example above, if a user enters a total amount of 200 and 10 red packets, but only 6 recipient accounts are found nearby, after the red packets are distributed, 4 red packets remain undistributed. The server can detect the time elapsed since the second timestamp; this time elapses is the duration of the distributed electronic red packets. If the undistributed electronic red packets exist for too long, the server can terminate the current data distribution, transfer the remaining payment value from the remaining 4 red packets back to the sender's account, and notify the sender's account's terminal. The sender's terminal can then display a notification to the user that the red packet distribution activity has ended and the payment value from the undistributed electronic red packets has been returned to the sender's account. The above solution returns business data to the sender's account based on whether a timeout has occurred, thus preventing the sender's account from suffering unnecessary losses. To address the inconvenience of traditional social network applications where users need to perform numerous friend-adding and group-creating operations to send business data to multiple strangers, as mentioned above, a business data group sending device corresponding to the aforementioned business data group sending method is proposed in one embodiment, as shown in Figure 10. This device includes: a pairing identifier generation module 102, a pairing identifier uploading module 104, and a business data group sending device. Service data input module 106 and mass message request upload module 108, wherein: The pairing identifier generation module 102 is used to receive data mass transmission instructions, generate pairing identifiers, and broadcast the pairing identifiers via short-range wireless signals. The pairing identifier upload module 104 is used to upload the pairing identifier to the server and receive the receiver account corresponding to the pairing identifier returned by the server. The business data input module 106 is used to receive input business data. The bulk data transmission request upload module 108 is used to generate a bulk data transmission request based on the business data and send it to the server, so that the server can send the business data to the terminal corresponding to the recipient account based on the bulk data transmission request. In one embodiment, the business data input module 106 is further configured to obtain the network storage path of the business data; The bulk request upload module 108 is also used to generate a bulk request for business data based on the network storage path of the business data and send it to the server. The server then sends the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the business data according to the network storage path. In one embodiment, the pairing identifier upload module 104 is further configured to obtain and upload the sender's account. The service data input module 106 is further configured to receive input service data of numerical data corresponding to the sender's account, and the server performs service data transfer between the sender's account and the receiver's account based on the service data. In one embodiment, the business data input module 106 is further configured to receive an input number of copies parameter. The bulk sending request upload module 108 is further configured to add the number of copies parameter to the business data bulk sending request, and the server divides the business data into sub-value sets according to the number of copies parameter, and extracts the sub-values ​​from the sub-value sets for the recipient account to perform business value transfer. In one embodiment, as shown in FIG10, the device further includes an authentication module 110, which is used to display an authentication window, obtain the authentication information corresponding to the sender's account through the authentication window, and send it to the server for verification. When the server returns a message indicating that the verification has passed, the bulk request upload module is invoked. In one embodiment, as shown in FIG10, the device further includes a bulk messaging status display module 112 for displaying the recipient's account on a display interface; the receiving server returns a receiving status indicating that the message has been received. The recipient's account is displayed on the display interface, providing a notification effect for the received recipient's account. In one embodiment, as shown in FIG10, the device further includes a social relationship addition module 114, which is used to receive a relationship chain addition instruction through the display interface, obtain the recipient account selected on the display interface corresponding to the relationship chain addition instruction; generate a relationship chain addition request based on the selected recipient account and send it to the server, and the server establishes a relationship chain mapping between the sender account and the selected recipient account. To address the inconvenience of traditional social network applications where users need to perform numerous friend-adding and group-creating operations to send business data to multiple strangers, as mentioned above, in one embodiment, as shown in Figure 11, a device for forwarding business data between terminals, corresponding to the aforementioned method for forwarding business data between terminals, is proposed. This device includes: a pairing initiation module 202, a receiver addition module 204, a business data receiving module 206, and a business data transmission module 208, wherein: The pairing initiation module 202 is used to receive the uploaded pairing identifier and obtain the sender account corresponding to the pairing identifier. The receiver adding module 204 is used to receive a pairing join request. When the pairing join request includes the pairing identifier, the user account carried in the pairing join request is obtained as the receiver account. The pairing identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the receiver account via a short-range wireless signal. The business data receiving module 206 is used to receive the business data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain business data according to the business data mass transmission request. The business data transmission module 208 is used to send the business data to the terminal corresponding to the recipient account. In one embodiment, the data type of the business data is numerical. The business data transmission module 208 is used to transfer business numerical data between the sender account and the receiver account according to the business data, and send a prompt message corresponding to the business numerical transfer to the receiver account. In one embodiment, the business data transmission module 208 is further configured to extract the number of copies of the business data according to the business data mass transmission request; divide the business data into a set of sub-values ​​according to the number of copies; and extract the sub-values ​​from the set of sub-values ​​to transfer the business data to the recipient account. In one embodiment, as shown in FIG11, the device further includes: an application receiving instruction receiving module 210, used to receive the application receiving instruction uploaded by the terminal corresponding to the recipient account and extract the first timestamp. The business data transmission module 208 is used to send the business data to the terminal corresponding to the recipient account in sequence according to the order of the first timestamp. In one embodiment, the receiver adding module 204 is further configured to obtain the number of receivers for the receiver account. The business data transmission module 208 is configured to determine whether the number of receivers is greater than the number of copies parameter; if so, it returns a receiving failure message to the receiver account. In one embodiment, the business data transmission module 208 is used to determine whether the sub-value set is empty. If so, it returns a message indicating that the reception failed to the recipient account. In one embodiment, the business data transmission module 208 is used to obtain a second timestamp of receiving the business data mass transmission request; determine whether the second timestamp has timed out; if so, obtain the remaining sub-values ​​in the sub-value set, return the remaining sub-values ​​to the sender account, and send a prompt message to the terminal corresponding to the sender account. To address the inconvenience of traditional social network applications where users need to perform numerous friend-adding and group-creating operations to send mass data to multiple strangers, as mentioned above, a device for receiving mass data is proposed in one embodiment, as shown in Figure 12. This device includes: a pairing identifier detection module 302, a pairing module 304, and a data receiving module 306, wherein: The pairing identifier detection module 302 is used to detect short-range wireless signals and obtain the pairing identifier carried by the short-range wireless signals. A pairing module 304 is added to obtain the recipient's account, upload the pairing identifier to the server along with the recipient's account, and the server searches for the sender's account corresponding to the pairing identifier and then searches for the business data uploaded by the sender's account. The data receiving module 306 is used to receive business data uploaded to the server by the sender's account. In one embodiment, the data type of the business data is numerical; the server performs business data transfer between the sender's account and the receiver's account based on the business data; data receiving module. 306 is used to receive the prompt information returned by the server corresponding to the transfer of the service value. In one embodiment, as shown in FIG12, the device further includes an application receiving module 308, which is used to receive an input application receiving instruction, upload the application receiving instruction to the server and carry a timestamp, and the server extracts the sub-values ​​in the service data according to the order of the received timestamps and transfers the service values ​​between the sender account and the receiver account. After adopting the aforementioned method and apparatus for sending group service data, when the initiator sends service data to strangers (i.e., users not on the initiator's social network), the initiator does not need to add multiple strangers as friends sequentially. Instead, they can directly broadcast a pairing identifier over a short distance using a short-range wireless signal, thus establishing a connection with multiple strangers. In other words, terminals with the same pairing identifier as the initiator's can receive the group service data sent by the initiator, eliminating the cumbersome steps of adding and verifying friends, thereby improving operational convenience. Furthermore, in the aforementioned method and apparatus for sending business data in bulk, the initiator does not need to create groups for multiple recipient accounts to send business data. Instead, the server can determine the user account matching the recipient account's identity based on the pairing identifier, and then send the business data to the user account that is the recipient account. This eliminates the initiator's need to create groups for bulk sending, thereby improving operational convenience. The above describes a method for using a pairing identifier to obtain recipient accounts that are not in a social relationship chain and then mass-sending business data to the terminals corresponding to those recipient accounts. However, besides using a pairing identifier, other methods can be used to mass-send business data to the terminals corresponding to the recipient accounts, as long as the identifier can facilitate pairing with the recipient accounts. In one embodiment, this mass-sending method for business data can run on the sender account's terminal 10, as shown in Figure 13, and includes: Step S402: Broadcast a pairing request via short-range wireless signal. Short-range wireless signals can be NFC, Bluetooth, Wi-Fi (Wi-Fi neighborhood), or Zigbee signals, which propagate within a range of tens of meters. For example, if a smart terminal has an NFC chip installed, it can broadcast a pairing request to other terminals via NFC signals. Other users can then establish a connection with the sender's terminal by bringing their terminals close to the sender's terminal, thereby receiving the pairing request. They can then log into their social networking application accounts on their terminals. Become the recipient account. Step S404: Pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request. In this embodiment of the invention, the sender and receiver may add each other as friends in advance, or they may not need to add each other as friends in advance. When the terminal corresponding to the sender's account needs to send a pairing request to the terminal corresponding to the receiver's account, the terminal corresponding to the sender's account receives the response from the terminal corresponding to the receiver's account. That is, the terminal corresponding to the sender's account needs to first confirm which terminal(s) or terminals(s) to distribute the service data to. Step S406: Receive input service data. It can display a business data input interface for the initiator to enter business data. The input business data can be in various formats, such as files, images, and numerical values. For example, in an alternative embodiment, if the initiator wants to send files from a certain cloud drive to multiple other users, the initiator can enter the network storage path of the files in the cloud drive. In another alternative embodiment, if the initiator wishes to send locally stored photos to multiple other users, a photo selection box can be provided in the business data input interface. The initiator can first select a local photo file as business data input in the business data input interface, then upload the photo file to a network storage location such as a server or a third-party storage server, and obtain the returned network storage path of the photo file, and then use the network storage address as business data input. In addition, in the case of mobile payment, the business data can also be a numerical type, such as the payment amount or transfer amount, which is numerical data that can be transferred between the sender's account and the recipient's account. It should be noted that the execution order of steps S406, S402, and S404 does not need to be strictly limited. The sender can first broadcast a pairing request via short-range wireless signal to pair with a receiver account within the range of the short-range wireless signal that accepts the pairing request, find the terminal corresponding to the receiver account, and then enter service data in the displayed service data input interface; alternatively, the sender can first enter service data in the displayed service data input interface, and then broadcast a pairing request via short-range wireless signal to pair with a receiver account within the range of the short-range wireless signal that accepts the pairing request, thus finding the terminal of the receiver account. These two methods do not conflict. Step S408: Generate a business data mass transmission request based on the business data and send it to the server, and The service data is sent to the server, which then forwards the service data to the terminal corresponding to the recipient account according to the service data mass transmission request. In this embodiment, since the above-mentioned group sending method for business data is adopted, when the initiator of sending business data sends business data to strangers, that is, users who are not on the initiator's social relationship chain, the initiator does not need to add multiple strangers as friends in turn. The initiator can directly communicate with multiple strangers through short-range wireless signals and then match with multiple strangers who accept the matching request, thereby eliminating the cumbersome steps of adding friends and verifying them, and improving the convenience of operation. In addition, in the above-mentioned method of sending business data in groups, the initiator does not need to create groups for multiple recipient accounts to send business data in groups. Instead, the initiator can determine the user account that matches the identity of the recipient account through short-range wireless signals or servers, and then send business data to the user account that is the recipient account. This eliminates the need for the initiator to create groups for mass sending, thereby improving the convenience of operation. In one embodiment, the step of broadcasting a pairing request via short-range wireless signals may include: Generate a pairing identifier and broadcast the pairing identifier via short-range wireless signals; The process of pairing with a receiver account that is within range of the short-range wireless signal and accepts the pairing request may include: The pairing identifier is uploaded to the server, and the receiver account corresponding to the pairing identifier is returned by the server. In another embodiment, the pairing step with a receiver account that is within range of the short-range wireless signal and accepts the pairing request, as shown in FIG14, may include: S4022: Receive a response signal returned by each of the terminals corresponding to the receiver account based on the short-range wireless signal, wherein each response signal includes an application identifier corresponding to one of the receiver accounts. The application identifier corresponding to the recipient account can be any type of unique identifier, as long as it can uniquely distinguish each recipient account from its corresponding terminal on the sender account's terminal side. For example, the application identifier corresponding to the recipient account can be the International Mobile Equipment Identity (IMEI). There are several ways for the terminal corresponding to the sender account to obtain the application identifier corresponding to the recipient account. For example, the sender can operate the terminal corresponding to the sender account by inputting the application identifier corresponding to the recipient account, or the terminal corresponding to the sender account... The client obtains the application identifier corresponding to the recipient's account through a pre-query. In this embodiment, the terminal corresponding to the sender account does not rely on the server, but directly obtains the application identifier corresponding to the receiver account from the receiver account that accepts the pairing request, and then completes the pairing. Therefore, the step of obtaining the receiver account from the server is omitted, which is more efficient. After each step of receiving a response signal returned by the short-range wireless signal from the terminal corresponding to the receiver account, the method may further include: S4024: Send the application identifier corresponding to the sender's account and the application identifier corresponding to the receiver's account to the server. In this embodiment of the invention, after the terminal corresponding to the sender account obtains the application identifier corresponding to the receiver account, the terminal corresponding to the sender account sends the application identifier corresponding to the sender account and the application identifier corresponding to the receiver account to the server through the current connection network. The server can record all the application identifier information. In one embodiment, after performing the step of sending the application identifier corresponding to the sender's account and the application identifier corresponding to the receiver's account to the server, the method may further include: Upon entering the business data distribution interface, the business data obtained by the terminal corresponding to the recipient account is displayed on the business data distribution interface. A business data distribution interface can be created on the terminal corresponding to the sender's account. This business data distribution interface can be a distribution interface for social products. When the terminal corresponding to the sender's account needs to distribute business data to the terminal corresponding to the receiver's account, the terminal corresponding to the sender's account first enters the business data distribution interface. The business data distribution interface displays the business data that the terminal corresponding to the receiver's account can obtain. Through the business data distribution interface of the terminal corresponding to the sender's account, users can easily and conveniently see the amount of business data that needs to be distributed, as well as the amount of business data that is currently remaining. In the above situation, the step of sending the business data to the server may include: The business data displayed in the business data distribution interface will be sent to the server. After the terminal corresponding to the sender account displays the business data on the business data distribution interface, the terminal will send the business data displayed on the business data distribution interface to the server, thereby ensuring the consistency between the amount of business data displayed on the business data distribution interface and the amount of business data sent to the server. As described in the above embodiments, the terminal corresponding to the sender's account first obtains the application identifier corresponding to the receiver's account, and then the terminal corresponding to the sender's account sends the application identifier corresponding to the sender's account. The sender sends an identifier and the application identifier corresponding to the recipient's account to the server. Next, the terminal corresponding to the sender's account sends the service data that the terminal corresponding to the recipient's account can obtain to the server. The server then simultaneously sends the service data to the terminal corresponding to the recipient's account. In this embodiment of the invention, the service data provided by the terminal corresponding to the sender's account to the terminal corresponding to the recipient's account can be obtained by the terminal corresponding to the recipient's account. The sender does not need to add the recipient as a friend or create a group for the terminals corresponding to the sender's account to complete the distribution of service data, which simplifies the existing service data processing process and improves the efficiency of service data acquisition between users. Accordingly, the method for forwarding service data between terminals executed by the server can be shown in Figure 15, including: Step S502: Obtain the sender's account and the receiver's account. The receiver's account is within the range of the short-range wireless signal of the terminal corresponding to the sender's account and accepts the pairing request broadcast by the terminal corresponding to the sender's account. Step S504: Receive the service data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain the service data according to the service data mass transmission request. Step S506: Send the service data to the terminal corresponding to the recipient account. In one embodiment, the step of obtaining the sender's account and the receiver's account may include: Receive the uploaded pairing identifier and obtain the sender account corresponding to the pairing identifier; When a pairing request is received, and the pairing identifier is included in the pairing request, the user account carried in the pairing request is obtained as the receiver account. The pairing identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the receiver account via a short-range wireless signal. In one embodiment, the step of obtaining the sender's account and the receiver's account, as shown in Figure 16, may include: Step S5022: Receive the uploaded application identifier from the terminal corresponding to the sender account, and obtain the sender account and receiver account corresponding to the application identifier. In one embodiment, the business data bulk sending request includes a number parameter N of the business data, and the business data is divided into a set of sub-data according to the number parameter. In this case, it may also include: Simultaneously, the number of copies parameter N is sent to each terminal in the terminal corresponding to the recipient account; sub-values ​​are extracted from the sub-value set and transferred to the recipient account for business value transfer; If the service data sent by the first terminal in the terminal corresponding to the recipient account is received, then... If a request is received, the number of copies parameter N is modified to N-1 according to the business data acquisition request, and a business data acquisition response is sent to the first terminal; The number of copies parameter N-1 is sent to each terminal in the terminal corresponding to the recipient account. In this process, after the server sends N service data items to each of the terminals corresponding to the recipient account, each terminal corresponding to the recipient account can know that the number of service data items distributed by the terminal corresponding to the sender account is N. If a terminal corresponding to a recipient account wants to obtain one of the N service data items, it sends a service data retrieval request to the server to obtain one service data item from the N service data items. The server will then receive the service data retrieval request sent by the terminal corresponding to the recipient account. Taking the first terminal corresponding to the recipient account sending a service data retrieval request to the server as an example, the server can receive the service data retrieval request sent by the first terminal corresponding to the recipient account. Upon receiving the service data retrieval request sent by the first terminal corresponding to the recipient account, the server modifies the N service data items into (N-1) service data items according to the service data retrieval request and sends a service data retrieval response to the first terminal corresponding to the recipient account. The business data acquisition response is used by the server to indicate that the terminal corresponding to the first recipient account has successfully acquired a piece of business data. The server changes the number of business data from N to (N-1) pieces of business data. As the terminal corresponding to the first recipient account successfully acquires business data, the number of business data will decrease. Furthermore, all terminals corresponding to the recipient account can request to acquire business data from the server, so the number of business data will continue to decrease until the number of business data is zero. In this embodiment, by monitoring the amount of business data, the mass distribution operation can be terminated in a timely manner when all business data has been distributed (i.e., the amount of business data is zero), thereby saving system resources. In one embodiment, after performing the step of sending the number of copies N-1 to each of the terminals corresponding to the recipient account, the method may further include: If a business data acquisition request is received from the first or second terminal in the terminal corresponding to the recipient account, determine whether the number of copies parameter N-1 is greater than 0. If the number of copies parameter N-1 is greater than 0, then the number of copies parameter N-1 is modified to the number of copies parameter N-2, and a business data acquisition response is sent to the first terminal or the second terminal, and the number of copies parameter N-2 is sent to each terminal in the terminal corresponding to the receiver account; If the number of copies parameter N-1 equals 0, then a notification instruction indicating that the business data distribution is complete is sent to each terminal in the terminal corresponding to the recipient account. In this process, the server receives a service data retrieval request from the terminal corresponding to the first receiver account. Based on the service data retrieved by the terminal corresponding to the first receiver account, the server modifies the number of service data items from N to (N-1). Each terminal corresponding to the receiver account modifies the N service data items received from the server to (N-1) service data items. At this point, the terminal corresponding to the first receiver account displays (N-1) service data items. If (N-1) is not zero, the terminal corresponding to the first receiver account can continue to send a service data retrieval request to the server to retrieve one service data item from (N-1) service data items. Of course, other terminals corresponding to the receiver account (such as the terminal corresponding to the second receiver account) can also send a request to the server to retrieve one service data item from (N-1) service data items. When a server receives a business data retrieval request from either the terminal corresponding to the first recipient account or the terminal corresponding to the second recipient account, the server checks if (N-1) is greater than 0. This means the server needs to check if all N business data items distributed by the terminal corresponding to the sender account have been retrieved. If (N-1) is greater than 0, it indicates that there is still business data remaining and has not been fully retrieved. The server then modifies the (N-1) business data items to (N-2) business data items and sends a business data retrieval response to either the terminal corresponding to the first or second recipient account. The server sends (N-2) business data items to each terminal corresponding to a recipient account, meaning each terminal corresponding to a recipient account can know that the number of business data items is (N-2). It should be noted that after the terminal corresponding to the first recipient account obtains one piece of business data, it can continue to send business data retrieval requests to the server. As long as the quantity of business data is not zero, the terminal corresponding to the first recipient account can obtain another piece of business data. In the existing business data processing, after a user receives business data dispatched by another user, the business data retrieval process ends, and the user can no longer receive business data from the same user, but can only wait for the user to re-distribute business data. For example, a real-world application scenario in the existing technology is that a user can only grab one red envelope. If a user has already grabbed a red envelope, even if there are still unclaimed red envelopes in the group, they cannot grab another red envelope. For the user, it is impossible to obtain business data multiple times. However, in this embodiment of the invention, for the terminal corresponding to the same recipient account (taking the terminal corresponding to the first recipient account as an example), as long as the quantity of business data is not zero, the terminal corresponding to that recipient account can obtain business data multiple times, satisfying the user's need to obtain business data multiple times. In some embodiments of the present invention, the service data acquisition request received by the server from the terminal corresponding to the first recipient account is a service data acquisition request sent by the terminal corresponding to the recipient account. The goal is to determine which business data retrieval request arrives at the server first. In other words, the server processes and modifies N pieces of business data in a round-robin fashion based on the order in which these requests arrive, and also processes and sends the modified business data in a round-robin fashion based on the same order of arrival time. In one embodiment, as shown in FIG17, a terminal corresponding to the aforementioned group transmission method for service data is proposed. The terminal 1700 may include at least: at least one processor 1701, such as a CPU; at least one network interface 1704; a user interface 1703; a memory 1705; and at least one communication bus 1702. The communication bus 1702 is used to implement communication between these components. The user interface 1703 may include a display screen and a keyboard; optionally, the user interface 1703 may also include a standard wired interface or a wireless interface. The network interface 1704 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1705 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1705 may also be at least one storage device located remotely from the aforementioned processor 1701. In the terminal 1700 shown in Figure 17, the user interface 1703 is mainly used to provide an input interface for the user and to obtain the user's input data; the network interface 1704 is mainly used for data transmission with the server; and the processor 1701 can be used to execute the computer-readable program code stored in the memory 1705 and specifically perform the following operations: A pairing request is broadcast via short-range wireless signal; Pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request; Receive input business data; A business data mass transmission request is generated based on the business data and sent to the server. The business data is then sent to the server, and the server sends the business data to the terminal corresponding to the recipient account according to the business data mass transmission request. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to broadcast a pairing request via short-range wireless signals, including: Generate a pairing identifier and broadcast the pairing identifier via short-range wireless signals; The processor is configured to execute the computer-readable program code to pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request, including: The pairing identifier is uploaded to the server, and the receiver account corresponding to the pairing identifier is returned by the server. In another embodiment, the processor 1701 is configured to execute the computer-readable program code to pair with a receiver account that is within range of the short-range wireless signal and accepts the pairing request, including: Each terminal corresponding to the receiver account receives a response signal returned by the short-range wireless signal, wherein each response signal includes an application identifier corresponding to one of the receiver accounts. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to, after receiving a response signal returned by each of the terminals corresponding to the receiver account based on the short-range wireless signal, further perform the following operations: The application identifier corresponding to the sender's account and the application identifier corresponding to the receiver's account are sent to the server. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to receive input business data, including: Obtain the network storage path of the business data; The processor 1701 is configured to execute the computer-readable program code to generate a business data bulk sending request based on the business data and send it to the server, including: A business data mass transmission request is generated based on the network storage path of the business data and sent to the server. The server then mass-transmits the network storage path to the terminals corresponding to the recipient accounts, and the terminals corresponding to the recipient accounts download the business data according to the network storage path. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to upload the pairing identifier to a server, including: Obtain the sender's account and upload it. In one embodiment, the data type of the business data is numerical, and the processor 1701 is configured to execute the computer-readable program code to receive the input business data, including: The server receives the input service data corresponding to the sender's account and processes it according to the service data. Service data is transferred between the sender's account and the receiver's account. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to receive input business data corresponding to the sender's account, including: Receive the input number of copies parameter; The processor 1701 is configured to execute the computer-readable program code to generate a business data bulk sending request based on the business data and send it to the server, including: The number of copies parameter is added to the business data mass transmission request. The server divides the business data into sub-value sets according to the number of copies parameter, and extracts the sub-values ​​from the sub-value sets for the recipient account to transfer business values. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to receive input business data corresponding to the sender's account, and then further perform the following operations: An authentication window is displayed, through which the authentication information corresponding to the sender's account is obtained and sent to the server for verification. Upon receiving a verification success message from the server, a business data mass transmission request is generated based on the business data and sent to the server. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to pair with a receiver account that is within range of the short-range wireless signal and has accepted the pairing request, and then further perform the following operations: The recipient's account is displayed on the screen; The processor 1701 is configured to execute the computer-readable program code to generate a business data bulk sending request based on the business data and send it to the server, and then further perform the following operations: The receiving server returns a receiving status indicating that the account has been received, and a notification effect is displayed on the display interface for the account that has been received. In one embodiment, the processor 1701 is configured to execute the computer-readable program code to further perform the following operations after displaying the recipient's account on the display interface: Receive relationship chain addition instructions through the display interface, and obtain the recipient account selected on the display interface corresponding to the relationship chain addition instructions; A relationship chain addition request is generated based on the selected recipient account and sent to the server, whereby the server establishes a relationship chain mapping between the sender account and the selected recipient account. In one embodiment, the processor 1701 is configured to execute the computer-readable program code. After sending the application identifier corresponding to the sender's account and the application identifier corresponding to the receiver's account to the server, the following operations are performed: Upon entering the business data distribution interface, the business data obtained by the terminal corresponding to the recipient account is displayed on the business data distribution interface. The processor 1701 is configured to execute the computer-readable program code to send the business data to the server, including: The business data displayed in the business data distribution interface will be sent to the server. In one embodiment, as shown in FIG18, a server for forwarding service data between terminals, corresponding to the aforementioned method for forwarding service data between terminals, is provided. The server 1800 may include at least: at least one processor 1801, such as a CPU; at least one network interface 1804; a user interface 1803; a memory 1805; and at least one communication bus 1802. The communication bus 1802 is used to implement communication between these components. The user interface 1803 may include a display screen and a keyboard; optionally, the user interface 1803 may also include a standard wired interface or a wireless interface. The network interface 1804 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1805 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1805 may also be at least one storage device located remotely from the aforementioned processor 1801. In the server 1800 shown in Figure 17, the user interface 1803 is mainly used to provide an input interface for the user and to obtain the user's input data; the network interface 1804 is mainly used for data transmission with the terminal; and the processor 1801 can be used to execute the computer-readable program code stored in the memory 1805 and specifically perform the following operations: Obtain the sender's account and the receiver's account, wherein the receiver's account is within the range of the short-range wireless signal of the terminal corresponding to the sender's account and accepts the pairing request broadcast by the terminal corresponding to the sender's account. Receive a business data mass transmission request uploaded by the terminal corresponding to the sender account, and obtain business data according to the business data mass transmission request; The business data is sent to the terminal corresponding to the recipient's account. In one embodiment, the processor 1801 is configured to execute the computer-readable program code. To obtain the sender's account and the recipient's account, including: Receive the uploaded pairing identifier and obtain the sender account corresponding to the pairing identifier; When a pairing request is received, and the pairing identifier is included in the pairing request, the user account carried in the pairing request is obtained as the receiver account. The pairing identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the receiver account via a short-range wireless signal. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to obtain the sender's account and the receiver's account, including: Receive the uploaded application identifier from the terminal corresponding to the sender account, and obtain the sender account and receiver account corresponding to the application identifier. In one embodiment, the data type of the business data is numerical; the processor 1801 is configured to execute the computer-readable program code to send the business data to the terminal corresponding to the recipient account, including: Based on the business data, a business value transfer is performed between the sender's account and the receiver's account, and a prompt message corresponding to the business value transfer is sent to the receiver's account. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to receive a request for mass transmission of business data uploaded by the terminal corresponding to the sender account, and then further perform the following operations: Extract the number of copies of the business data based on the mass data sending request; The business data is divided into sub-value sets according to the number of parts parameter; The processor 1801 is configured to execute the computer-readable program code to perform a service value transfer between the sender's account and the receiver's account based on the service data, including: Extract sub-values ​​from the sub-value set and transfer them to the recipient account for business value transfer. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to further perform the following operations before extracting sub-values ​​from the sub-value set and transferring them to the recipient account for business value transfer: Receive the application acceptance instruction uploaded by the terminal corresponding to the recipient account and extract the first timestamp; The processor 1801 is configured to execute the computer-readable program code to extract sub-values ​​from the sub-value set and transfer business values ​​to the recipient account, including: The business data is sent to the recipient account sequentially according to the order of the first timestamp. The corresponding terminal. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to obtain the sender's account and the receiver's account, including: Get the number of recipients for the recipient account; The processor 1801 is configured to execute the computer-readable program code to extract sub-values ​​from the sub-value set and transfer business values ​​to the recipient account, including: Determine whether the number of recipients is greater than the number of copies parameter. If so, return a message indicating that the reception failed to be sent to the recipient's account. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to send the business data to the terminal corresponding to the recipient account, including: Determine whether the set of sub-values ​​is empty. If it is, return a message indicating that the reception failed to the recipient account. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to receive a request for mass transmission of business data uploaded by the terminal corresponding to the sender account, including: Obtain the second timestamp of receiving the business data mass transmission request; The processor 1801 is configured to execute the computer-readable program code and also perform the following operations: Determine whether the second timestamp has timed out. If so, obtain the remaining sub-values ​​in the sub-value set, return the remaining sub-values ​​to the sender's account, and send a prompt message to the terminal corresponding to the sender's account. In one embodiment, the number of parts parameter is N; the processor 1801 is configured to execute the computer-readable program code to divide the business data into sub-value sets according to the number of parts parameter, and then perform the following operations: Simultaneously, the number of copies parameter N is sent to each terminal in the terminals corresponding to the recipient account; The processor 1801 is configured to execute the computer-readable program code to, after extracting sub-values ​​from the sub-value set and transferring the business value to the recipient account, also perform the following operations: If a service data acquisition request is received from the first terminal in the terminal corresponding to the recipient account, the number of copies parameter N is modified to N-1 according to the service data acquisition request, and a service data acquisition response is sent to the first terminal. The number of copies parameter N-1 is sent to each terminal in the terminal corresponding to the recipient account. In one embodiment, the processor 1801 is configured to execute the computer-readable program code to send the number of copies N-1 to each of the terminals corresponding to the recipient account, and then further perform the following operations: If a business data acquisition request is received from the first or second terminal in the terminal corresponding to the recipient account, determine whether the number of copies parameter N-1 is greater than 0. If the number of copies parameter N-1 is greater than 0, then the number of copies parameter N-1 is modified to the number of copies parameter N-2, and a business data acquisition response is sent to the first terminal or the second terminal, and the number of copies parameter N-2 is sent to each terminal in the terminal corresponding to the receiver account; If the number of copies parameter N-1 equals 0, then a notification instruction indicating that the business data distribution is complete is sent to each terminal in the terminal corresponding to the recipient account. In one embodiment, the received service data acquisition request sent by the first terminal is the first service data acquisition request to arrive among the service data acquisition requests sent by the terminals corresponding to the recipient account. The above description discloses only preferred embodiments of the present invention and should not be construed as limiting the scope of the present invention. Therefore, equivalent variations made in accordance with the claims of the present invention are still within the scope of the present invention.

Claims

Revised January 7, 2020. No claims. -------------------------------------------------------------------------------- 07 / 02 / 2019 ------ (OCR) Page 1 of 13. Claims 1. Method of transmitting service data packets which includes: broadcasting matching requests using near-range wireless signals; matching with matched recipient accounts within near-range wireless signals and accepting matching requests; receiving incoming service data; and generating service data packet transmission requests based on the service data, transmitting service data packet transmission requests to servers, and transmitting service data to servers so that a group of servers can transmit service data to the corresponding terminals of the recipient accounts according to the service data packet transmission request. 2.The method for transmitting service data groups under claim 1, where the procedure for broadcasting a matching request via near-range wireless signal, includes: generating a matching identifier and broadcasting the matching identifier via near-range wireless signal; and the procedure for matching with a recipient account within the near-range wireless signal range and accepting the matching request includes: uploading the matching identifier to the server, and receiving the recipient account returned by the server and corresponding to the matching identifier.

3. The method for transmitting service data groups under claim 1, where the procedure for matching with a recipient account within the near-range wireless signal range and accepting the matching request, includes: receiving the acknowledgment returned by the terminal corresponding to the recipient account via near-range wireless signal, where each acknowledgment contains a unique identifier set corresponding to one recipient account from among the recipient accounts listed on page 2 of 13 on page 4.The method for transmitting service data groups under claim 3, whereby after the acknowledgment signal is received from the terminal corresponding to the recipient account via a near-range wireless signal, also includes: sending a dedicated identifier set corresponding to the sender account and a dedicated identifier set corresponding to the recipient account to the server.

5. The method for transmitting service data groups under any one of claims 1 to 4, whereby the process of receiving the incoming service data also includes: searching for the network storage path of the service data; and the process of generating a request to transmit the service data group based on the service data and sending the request to the server also includes: generating a request to transmit the service data group via the network storage path and sending the request to the server so that the server transmits the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the service data via the network storage path. 6.The method for sending service data groups under claim 2, where the upload process for identifying the server trajectory includes: searching for the sender account and uploading the sender account.

7. The method for sending service data groups under any one of claims 3, 4, and 6, where the data type of the service data is numeric; and the process for receiving the imported service data includes: receiving the imported service data which corresponds to the sender account so that the server can transfer the service numbers between the sender and recipient accounts according to the service data. 8.The method for sending service data sets under claim 7, where the procedure for receiving the imported service data that corresponds to the sender account, also includes receiving the imported share parameters; and page 3 of the 13-page procedure for generating a request to send service data sets based on the service data and sending the request to the server also includes: adding share parameters to the request to send service data sets so that the server can divide the service data into subsets according to the share parameters and extract the subsets from the subsets for the recipient account to process the service data transfer 9.The method for sending service data groups under claim 7, after the service data receiving procedure is consistent with the sender account, includes: displaying the identity verification window, searching for the consistent imported identity verification information that matches the sender account using the identity verification window, sending the identity verification information to the server for verification, and performing the procedure for generating a request to send the service data group based on the service data, and sending the request to send the service data group to the server upon receiving a verification successful message returned by the server.10.The method for transmitting service data groups under claim 7, whereby after the pairing process with a recipient account within the near-range wireless signal and the acceptance of the pairing request, the method also includes: displaying the recipient account on the display interface; and after the process of generating a request to transmit the service data group according to the service information and sending the request to the server, the method also includes: receiving the recipient account returned by the server and the acceptance status of the account is received, and displaying a trigger on the display interface for the received recipient account.11.The method for sending service data groups according to claim 10, after the recipient account display process on the display interface, also includes: receiving the chain addition command via the display interface and searching for recipient accounts that correspond to the chain addition command and are selected on the display interface; and on page 4 of page 13, generating the chain addition request based on the selected recipient account and sending the chain addition request to the server so that the server can create a chain transmission diagram between the sender account and the selected recipient account.12.The method for sending service data groups under claim 4, whereby after the service transmission process to the specific use set indicator corresponding to the sender account and the specific use set indicator corresponding to the recipient account, the method also includes: accessing the service distribution interface, and displaying the service data obtained by the terminal corresponding to the recipient account on the service distribution interface; and the process for sending service data to the server includes: sending the service data displayed on the service distribution interface to the server.13.The method for forwarding service data between terminals includes: searching for the sender's account and the recipient's account, where the recipient's account is within the near-range wireless signal of the terminal corresponding to the sender's account, and accepting the broadcasting of the pairing request by the terminal corresponding to the sender's account; receiving the request to send the uploaded service data packet by the terminal corresponding to the sender's account and searching for the service data based on the service data packet request; and sending the service data to the terminal corresponding to the recipient's account.14.The method for data forwarding services between terminals under claim 13, where the procedure for retrieving sender and recipient accounts includes: receiving the uploaded matching identifier and retrieving the sender account corresponding to the matching identifier; and receiving the add-and-match request, retrieving the user account present in the add-and-match request when the add-and-match request includes the matching identifier, and using the user account as the recipient account, where the matching identifier is transmitted by the terminal corresponding to the sender account to the terminal corresponding to the recipient account via a near-range wireless signal.

15. The method for data forwarding services between terminals under claim 13, where page 5 of 13, the procedure for retrieving sender and recipient accounts includes: receiving the uploaded proprietary identifier from the terminal corresponding to the sender account and retrieving the sender and recipient accounts corresponding to the proprietary identifier.16.The method for forwarding service data between terminals under claim 13, where the data type of the service data is numeric; and the procedure for sending service data to the terminal corresponding to the recipient account is: the operation of transferring service numbers between the sender account and the recipient account according to the service data, and the transmission of the trigger information corresponding to the transfer of service numbers to the recipient account.

17. The method for forwarding service data between terminals under claim 16, where, after the procedure of receiving the request to send the uploaded service data group by the terminal corresponding to the sender account, the method also includes: extracting the share parameters corresponding to the transfer of service numbers according to the request to send the service data group; and dividing the service data into sub-sets of numeric numbers according to the share parameters; and the procedure for transferring service numbers between the sender account and the recipient account according to the service data also includes: extracting sub-numbers from the sub-number sets for the operation of transferring service numbers to the recipient account.18.The method for forwarding service data between terminals under claim 17, whereby the preceding step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account, includes the receiving command for the uploaded specific use set by receiving the corresponding terminal to the recipient account and extracting the first timestamp; and the step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account also includes the sequential transmission of service data to the corresponding terminal to the recipient account with the first timestamp (page 6 of number 13, page 19).The method for forwarding service data between terminals under claim 17, where the procedure for retrieving the sender and recipient accounts includes: retrieving the number of recipients in the recipient account; and the procedure for extracting sub-digits from the sub-digit set for transferring service numbers to the recipient account includes: determining whether the number of recipients exceeds the share parameter and returning trigger information indicating that the reception failed to the recipient account if the number of recipients exceeds the share parameter.

20. The method for forwarding service data between terminals under claim 17, where the procedure for sending service data to the terminal corresponding to the recipient account includes: determining whether the sub-digit set is zero and returning trigger information indicating that the reception failed to the recipient account if the sub-digit set is zero. 21.The method for forwarding service data between terminals under claim17, whereby the procedure for receiving a request to send the service data set uploaded by the terminal corresponding to the sender account, also includes the search for a second time stamp for the receipt of the service data set request; and the method also includes the determination of whether the second time stamp has expired; and the search for the remaining sub-number in the sub-number set, the return of the remaining number to the sender account, and the transmission of the stimulus information to the terminal corresponding to the sender account before the second time stamp expires.22.The method for forwarding service data between terminals according to any one of the claims 17 to 21, where the share parameter is N; after the process of dividing the service data into sub-sets of numbers according to the share parameter, the method also includes: sending the share parameter N simultaneously to each terminal among the terminals corresponding to the recipient account; and page 7 of page 13, after the process of extracting sub-sets of numbers from the sub-sets of numbers for the transfer of service numbers to the recipient account, the method also includes: converting the share parameter N into (N-1) according to the service data request; the service data request sent by the first terminal of the terminal corresponding to the recipient account is received and the service data request response is sent to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account.23.The method for forwarding service data between terminals under claim 22, whereby after the process of sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the method also includes: determining whether the share parameter (N-1) is greater than 0; a request to retrieve service data sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; converting the share parameter (N-1) to a share parameter (N-2); sending a response requesting service data to the first or second terminal; and sending the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and sending a trigger command indicating completion of the service data distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is equal to 0.24.The method for forwarding service information between terminals under claim 22, whereby a service request received and sent by the first terminal is the first service request among all service requests sent in sequence by terminals corresponding to the recipient account 25. The terminals consist of: a module to generate matching identifiers to broadcast matching requests using near-range wireless signals; a module to upload matching identifiers to match recipient accounts within the range of near-range wireless signals (page 8 of 13); a module to import service information to receive imported service information; and a module to upload grouping requests to generate grouping service requests based on the service information, send grouping service requests to the server, and send service information to the server so that the group of servers can forward the service information to the terminals corresponding to the recipient accounts according to the grouping service request 26.The terminal under claim 25, where the matching indicator generation module is configured to: generate matching indicators and broadcast matching indicators via near-range wireless signals; and the matching indicator upload module is configured to: upload matching indicators to the server and receive recipient accounts returned by the server and corresponding to the matching indicators.

27. The terminal under claim 25, where the pairing with a recipient account is within near-range wireless range, includes: receiving acknowledgments returned via near-range wireless signals by the terminal corresponding to the recipient account, where each acknowledgment contains a unique indicator set corresponding to one of the recipient accounts.

28. The terminal under claim 27, where the terminal is also configured to: send unique indicator sets corresponding to the sender account and unique indicator sets corresponding to the recipient account to the server. 29.A terminal under any of Claims 25 through 28 where the Service Data Input module is configured to seek the Service Data network storage path; and the Group Sending Request Upload module is configured to: Page 9 of 13 generates a Service Data Group Sending Request via the Service Data Network Storage Path and sends the Service Data Group Sending Request to the Server so that the Server Group sends the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the Service Data via the network storage path.

30. A terminal under Claim 26 where the Matching Identifier Upload module is configured to: seek the Sender account and upload to the Sender account.

31. A terminal under any of Claims 27, 28, and 30 where the Service Data data type is numeric; and the Service Data Input module is configured to: receive the imported Service Data corresponding to the Sender account so that the Server performs the Service Number transfer between the Sender and Recipient accounts according to the Service Data. 32.The terminal under claim 31, where the service data import module is configured to: receive imported share parameters; and the upload request for grouping submission module is configured to: add share parameters to the service data grouping submission request so that the server divides the service data into subsets based on the share parameters and extracts subsets from the subsets for the recipient account for the transfer of service numbers.

33. The terminal under claim 31, where the terminal also incorporates a character verification module to: display the character verification window; retrieve the corresponding imported character verification information for the sender account based on the character verification window; send the character verification information to the server for verification; and call the upload request for grouping submission module to generate a service data grouping submission request based on the service data and send the service data grouping submission request to the server when a successful verification message returned by the server is received. (Page 10 of 13, page 34)A terminal under claim 31 includes a module for displaying the grouping status to: display the recipient account on the display interface; receive the recipient account returned by the server, and its receiving state is accepted; and display a trigger for the received recipient account on the display interface.

35. A terminal under claim 34 includes a module for adding social relationships to: receive the add-chain command via the display interface and search for recipient accounts corresponding to the add-chain command and selection on the display interface; and generate an add-chain request based on the selected recipient account and send the add-chain request to the server so that the server can construct a social relationship map between the sender account and the selected recipient account. 36.The terminal under claim 28, whereby after sending the specific use identifier set corresponding to the sender account and the specific use identifier set corresponding to the recipient account to the server, the terminal is also configured to: enter the 'Service Distribution Interface', and display the service information received by the terminal corresponding to the recipient account on the Service Distribution Interface; and the transmission of service information to the server includes the transmission of service information displayed on the Service Distribution Interface to the server.37.The service provider assembly consists of: a pairing initiation module and a receiver add module to seek the sender account with the receiver account, where the receiver account is within the near-range wireless signal of the terminal corresponding to the sender account and accepts the pairing broadcast request from the terminal corresponding to the sender account; a service data reception module to receive the request to send service data packets uploaded by the terminal corresponding to the sender account and seeks the service data according to the service data packet sending request; and a service data transmission module to send the service data to the terminal corresponding to the receiver account. (Page 11 of 13, page 38)The service provider under claim 37, where the 'Initiate Matching' module is configured to: receive the matching indicator, which the client uploads and searches for the sender account corresponding to the matching indicator; and the 'Add Receiver' module is configured to: receive the add-and-match request, search for the user account present in the add-and-match request when the add-and-match request includes a matching indicator, and use the user account as the receiver account, where the matching indicator is broadcast by the corresponding terminal to the sender account to the corresponding terminal to the receiver account via a near-range wireless signal.

39. The service provider under claim 37, where the search for the sender account to the receiver account includes receiving the dedicated indicator set uploaded by the client from the corresponding terminal to the sender account and searching for the sender account to the receiver account corresponding to the dedicated indicator set.40.The server under claim 37, where the data type of the service data is numeric; and the service data transmission module is configured to: perform the transfer of service numbers between the sender and recipient accounts according to the service data; and send the corresponding prompt information to the recipient account.

41. The server under claim 40, where the service data transmission module is configured to: extract the share parameters corresponding to the transfer of service numbers according to the request to send a service data group; and divide the service data into subsets of numeric sequences according to the share parameters; and extract the subsets of numeric sequences for the transfer of service numbers to the recipient account.42.The server under claim 41, whereby the server comprises: a task-specific program receiving module to receive task-specific program orders uploaded by the terminal corresponding to the recipient account and extract the timestamp; and on page 12 of 13, the service data transmission module will configure: to send service data sequentially to the terminal corresponding to the recipient account according to the timestamp.

43. The server under claim 41, whereby the recipient addition module will be configured: to seek the number of recipients for the recipient account; and the service data transmission module will configure: to determine whether the number of recipients exceeds the share parameter and return a trigger information that the reception failed to the recipient account if the number of recipients exceeds the share parameter.

44. The server under claim 41, whereby the service data transmission module will configure: to determine whether the sub-number is zero and return a trigger information that the reception failed to the recipient account if the sub-number is zero. 45.The service provider under claim 41, where the service data transmission module is configured to: seek a second timestamp for receiving a request to send a service data group; and determine whether the second timestamp has expired; and seek a remaining subset of numbers in the subset of numbers, return the remaining subset of numbers to the sender account, and send the trigger information to the terminal corresponding to the sender account before the second timestamp expires.46.The server, pursuant to any one of claims 41 to 45, where the share parameter is N; after dividing the service data into subsets of numbers according to the share parameter, the server is also configured to: send the share parameter N simultaneously to each terminal from among the terminals corresponding to the recipient account; and after extracting the subsets of numbers from the subsets of numbers for the transfer of service numbers to the recipient account, the server is also configured to: page 13 of page 13, modify the share parameter N to (N-1) according to the service data request if the service data request sent by the first terminal of the terminal corresponding to the recipient account is received, and send the service data request response to the first terminal; and send the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account. 47.The server under claim 46, whereby after sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the server is also configured to: determine whether the share parameter (N-1) is greater than 0 if a request to retrieve service information sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; modify the share parameter (N-1) to the share parameter (N-2), send a response to the request for service information to the first or second terminal, and send the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and send a trigger command indicating completion of service information distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) equals 0.48.The server under claim 46, whereby a service request received which is sent by one terminal is the first service request to arrive among service request requests sent in sequence by the terminals corresponding to the recipient account.------------------07 / 02 / 2019------(OCR) Page 1 of 13 Claim 1. Method of service group transmission which includes: broadcasting of matching request via near-range wireless signal; matching with a matched recipient account within the near-range wireless signal range and accepting the matching request; receiving the incoming service data; and generating a service group transmission request based on the service data, sending the service group transmission request to the server, and sending the service data to the server so that the server group can transmit the service data to the terminals corresponding to the recipient accounts based on the service group transmission request. 2.The method for transmitting service data groups under claim 1, where the procedure for broadcasting a matching request via near-range wireless signal, includes: generating a matching identifier and broadcasting the matching identifier via near-range wireless signal; and the procedure for matching with a recipient account within the near-range wireless signal range and accepting the matching request includes: uploading the matching identifier to the server, and receiving the recipient account returned by the server and corresponding to the matching identifier.

3. The method for transmitting service data groups under claim 1, where the procedure for matching with a recipient account within the near-range wireless signal range and accepting the matching request, includes: receiving the acknowledgment returned by the terminal corresponding to the recipient account via near-range wireless signal, where each acknowledgment contains a unique identifier set corresponding to one recipient account from among the recipient accounts listed on page 2 of 13 on page 4.The method for transmitting service data groups under claim 3, whereby after the acknowledgment signal is received from the terminal corresponding to the recipient account via a near-range wireless signal, also includes: sending a dedicated identifier set corresponding to the sender account and a dedicated identifier set corresponding to the recipient account to the server.

5. The method for transmitting service data groups under any one of claims 1 to 4, whereby the process of receiving the incoming service data also includes: searching for the network storage path of the service data; and the process of generating a request to transmit the service data group based on the service data and sending the request to the server also includes: generating a request to transmit the service data group via the network storage path and sending the request to the server so that the server transmits the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the service data via the network storage path. 6.The method for sending service data groups under claim 2, where the upload process for identifying the server trajectory includes: searching for the sender account and uploading the sender account.

7. The method for sending service data groups under any one of claims 3, 4, and 6, where the data type of the service data is numeric; and the process for receiving the imported service data includes: receiving the imported service data which corresponds to the sender account so that the server can transfer the service numbers between the sender and recipient accounts according to the service data. 8.The method for sending service data sets under claim 7, where the procedure for receiving the imported service data that corresponds to the sender account, also includes receiving the imported share parameters; and page 3 of the 13-page procedure for generating a request to send service data sets based on the service data and sending the request to the server also includes: adding share parameters to the request to send service data sets so that the server can divide the service data into subsets according to the share parameters and extract the subsets from the subsets for the recipient account to process the service data transfer 9.The method for sending service data groups under claim 7, after the service data receiving procedure is consistent with the sender account, includes: displaying the identity verification window, searching for the consistent imported identity verification information that matches the sender account using the identity verification window, sending the identity verification information to the server for verification, and performing the procedure for generating a request to send the service data group based on the service data, and sending the request to send the service data group to the server upon receiving a verification successful message returned by the server.10.The method for transmitting service data groups under claim 7, whereby after the pairing process with a recipient account within the near-range wireless signal and the acceptance of the pairing request, the method also includes: displaying the recipient account on the display interface; and after the process of generating a request to transmit the service data group according to the service information and sending the request to the server, the method also includes: receiving the recipient account returned by the server and the acceptance status of the account is received, and displaying a trigger on the display interface for the received recipient account.11.The method for sending service data groups according to claim 10, after the recipient account display process on the display interface, also includes: receiving the chain addition command via the display interface and searching for recipient accounts that correspond to the chain addition command and are selected on the display interface; and on page 4 of page 13, generating the chain addition request based on the selected recipient account and sending the chain addition request to the server so that the server can create a chain transmission diagram between the sender account and the selected recipient account.12.The method for sending service data groups under claim 4, whereby after the service transmission process to the specific use set indicator corresponding to the sender account and the specific use set indicator corresponding to the recipient account, the method also includes: accessing the service distribution interface, and displaying the service data obtained by the terminal corresponding to the recipient account on the service distribution interface; and the process for sending service data to the server includes: sending the service data displayed on the service distribution interface to the server.13.The method for forwarding service data between terminals includes: searching for the sender's account and the recipient's account, where the recipient's account is within the near-range wireless signal of the terminal corresponding to the sender's account, and accepting the broadcasting of the pairing request by the terminal corresponding to the sender's account; receiving the request to send the uploaded service data packet by the terminal corresponding to the sender's account and searching for the service data based on the service data packet request; and sending the service data to the terminal corresponding to the recipient's account.14.The method for data forwarding services between terminals under claim 13, where the procedure for retrieving sender and recipient accounts includes: receiving the uploaded matching identifier and retrieving the sender account corresponding to the matching identifier; and receiving the add-and-match request, retrieving the user account present in the add-and-match request when the add-and-match request includes the matching identifier, and using the user account as the recipient account, where the matching identifier is transmitted by the terminal corresponding to the sender account to the terminal corresponding to the recipient account via a near-range wireless signal.

15. The method for data forwarding services between terminals under claim 13, where page 5 of 13, the procedure for retrieving sender and recipient accounts includes: receiving the uploaded proprietary identifier from the terminal corresponding to the sender account and retrieving the sender and recipient accounts corresponding to the proprietary identifier.16.The method for forwarding service data between terminals under claim 13, where the data type of the service data is numeric; and the procedure for sending service data to the terminal corresponding to the recipient account is: the operation of transferring service numbers between the sender account and the recipient account according to the service data, and the transmission of the trigger information corresponding to the transfer of service numbers to the recipient account.

17. The method for forwarding service data between terminals under claim 16, where, after the procedure of receiving the request to send the uploaded service data group by the terminal corresponding to the sender account, the method also includes: extracting the share parameters corresponding to the transfer of service numbers according to the request to send the service data group; and dividing the service data into sub-sets of numeric numbers according to the share parameters; and the procedure for transferring service numbers between the sender account and the recipient account according to the service data also includes: extracting sub-numbers from the sub-number sets for the operation of transferring service numbers to the recipient account.18.The method for forwarding service data between terminals under claim 17, whereby the preceding step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account, includes the receiving command for the uploaded specific use set by receiving the corresponding terminal to the recipient account and extracting the first timestamp; and the step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account also includes the sequential transmission of service data to the corresponding terminal to the recipient account with the first timestamp (page 6 of number 13, page 19).The method for forwarding service data between terminals under claim 17, where the procedure for retrieving the sender and recipient accounts includes: retrieving the number of recipients in the recipient account; and the procedure for extracting sub-digits from the sub-digit set for transferring service numbers to the recipient account includes: determining whether the number of recipients exceeds the share parameter and returning trigger information indicating that the reception failed to the recipient account if the number of recipients exceeds the share parameter.

20. The method for forwarding service data between terminals under claim 17, where the procedure for sending service data to the terminal corresponding to the recipient account includes: determining whether the sub-digit set is zero and returning trigger information indicating that the reception failed to the recipient account if the sub-digit set is zero. 21.The method for forwarding service data between terminals under claim17, whereby the procedure for receiving a request to send the service data set uploaded by the terminal corresponding to the sender account, also includes the search for a second time stamp for the receipt of the service data set request; and the method also includes the determination of whether the second time stamp has expired; and the search for the remaining sub-number in the sub-number set, the return of the remaining number to the sender account, and the transmission of the stimulus information to the terminal corresponding to the sender account before the second time stamp expires.22.The method for forwarding service data between terminals according to any one of the claims 17 to 21, where the share parameter is N; after the process of dividing the service data into sub-sets of numbers according to the share parameter, the method also includes: sending the share parameter N simultaneously to each terminal among the terminals corresponding to the recipient account; and page 7 of page 13, after the process of extracting sub-sets of numbers from the sub-sets of numbers for the transfer of service numbers to the recipient account, the method also includes: converting the share parameter N into (N-1) according to the service data request; the service data request sent by the first terminal of the terminal corresponding to the recipient account is received and the service data request response is sent to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account.23.The method for forwarding service data between terminals under claim 22, whereby after the process of sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the method also includes: determining whether the share parameter (N-1) is greater than 0; a request to retrieve service data sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; converting the share parameter (N-1) to a share parameter (N-2); sending a response requesting service data to the first or second terminal; and sending the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and sending a trigger command indicating completion of the service data distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is equal to 0.24.The method for forwarding service information between terminals under claim 22, whereby a service request received and sent by the first terminal is the first service request among all service requests sent in sequence by terminals corresponding to the recipient account 25. The terminals consist of: a module to generate matching identifiers to broadcast matching requests using near-range wireless signals; a module to upload matching identifiers to match recipient accounts within the range of near-range wireless signals (page 8 of 13); a module to import service information to receive imported service information; and a module to upload grouping requests to generate grouping service requests based on the service information, send grouping service requests to the server, and send service information to the server so that the group of servers can forward the service information to the terminals corresponding to the recipient accounts according to the grouping service request 26.The terminal under claim 25, where the matching indicator generation module is configured to: generate matching indicators and broadcast matching indicators via near-range wireless signals; and the matching indicator upload module is configured to: upload matching indicators to the server and receive recipient accounts returned by the server and corresponding to the matching indicators.

27. The terminal under claim 25, where the pairing with a recipient account is within near-range wireless range, includes: receiving acknowledgments returned via near-range wireless signals by the terminal corresponding to the recipient account, where each acknowledgment contains a unique indicator set corresponding to one of the recipient accounts.

28. The terminal under claim 27, where the terminal is also configured to: send unique indicator sets corresponding to the sender account and unique indicator sets corresponding to the recipient account to the server. 29.A terminal under any of Claims 25 through 28 where the Service Data Input module is configured to seek the Service Data network storage path; and the Group Sending Request Upload module is configured to: Page 9 of 13 generates a Service Data Group Sending Request via the Service Data Network Storage Path and sends the Service Data Group Sending Request to the Server so that the Server Group sends the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the Service Data via the network storage path.

30. A terminal under Claim 26 where the Matching Identifier Upload module is configured to: seek the Sender account and upload to the Sender account.

31. A terminal under any of Claims 27, 28, and 30 where the Service Data data type is numeric; and the Service Data Input module is configured to: receive the imported Service Data corresponding to the Sender account so that the Server performs the Service Number transfer between the Sender and Recipient accounts according to the Service Data. 32.The terminal under claim 31, where the service data import module is configured to: receive imported share parameters; and the upload request for grouping submission module is configured to: add share parameters to the service data grouping submission request so that the server divides the service data into subsets based on the share parameters and extracts subsets from the subsets for the recipient account for the transfer of service numbers.

33. The terminal under claim 31, where the terminal also incorporates a character verification module to: display the character verification window; retrieve the corresponding imported character verification information for the sender account based on the character verification window; send the character verification information to the server for verification; and call the upload request for grouping submission module to generate a service data grouping submission request based on the service data and send the service data grouping submission request to the server when a successful verification message returned by the server is received. (Page 10 of 13, page 34)A terminal under claim 31 includes a module for displaying the grouping status to: display the recipient account on the display interface; receive the recipient account returned by the server, and its receiving state is accepted; and display a trigger for the received recipient account on the display interface.

35. A terminal under claim 34 includes a module for adding social relationships to: receive the add-chain command via the display interface and search for recipient accounts corresponding to the add-chain command and selection on the display interface; and generate an add-chain request based on the selected recipient account and send the add-chain request to the server so that the server can construct a social relationship map between the sender account and the selected recipient account. 36.The terminal under claim 28, whereby after sending the specific use identifier set corresponding to the sender account and the specific use identifier set corresponding to the recipient account to the server, the terminal is also configured to: enter the 'Service Distribution Interface', and display the service information received by the terminal corresponding to the recipient account on the Service Distribution Interface; and the transmission of service information to the server includes the transmission of service information displayed on the Service Distribution Interface to the server.37.The service provider assembly consists of: a pairing initiation module and a receiver add module to seek the sender account with the receiver account, where the receiver account is within the near-range wireless signal of the terminal corresponding to the sender account and accepts the pairing broadcast request from the terminal corresponding to the sender account; a service data reception module to receive the request to send service data packets uploaded by the terminal corresponding to the sender account and seeks the service data according to the service data packet sending request; and a service data transmission module to send the service data to the terminal corresponding to the receiver account. (Page 11 of 13, page 38)The service provider under claim 37, where the 'Initiate Matching' module is configured to: receive the matching indicator, which the client uploads and searches for the sender account corresponding to the matching indicator; and the 'Add Receiver' module is configured to: receive the add-and-match request, search for the user account present in the add-and-match request when the add-and-match request includes a matching indicator, and use the user account as the receiver account, where the matching indicator is broadcast by the corresponding terminal to the sender account to the corresponding terminal to the receiver account via a near-range wireless signal.

39. The service provider under claim 37, where the search for the sender account to the receiver account includes receiving the dedicated indicator set uploaded by the client from the corresponding terminal to the sender account and searching for the sender account to the receiver account corresponding to the dedicated indicator set.40.The server under claim 37, where the data type of the service data is numeric; and the service data transmission module is configured to: perform the transfer of service numbers between the sender and recipient accounts according to the service data; and send the corresponding prompt information to the recipient account.

41. The server under claim 40, where the service data transmission module is configured to: extract the share parameters corresponding to the transfer of service numbers according to the request to send a service data group; and divide the service data into subsets of numeric sequences according to the share parameters; and extract the subsets of numeric sequences for the transfer of service numbers to the recipient account.42.The server under claim 41, whereby the server comprises: a task-specific program receiving module to receive task-specific program orders uploaded by the terminal corresponding to the recipient account and extract the timestamp; and on page 12 of 13, the service data transmission module will configure: to send service data sequentially to the terminal corresponding to the recipient account according to the timestamp.

43. The server under claim 41, whereby the recipient addition module will be configured: to seek the number of recipients for the recipient account; and the service data transmission module will configure: to determine whether the number of recipients exceeds the share parameter and return a trigger information that the reception failed to the recipient account if the number of recipients exceeds the share parameter.

44. The server under claim 41, whereby the service data transmission module will configure: to determine whether the sub-number is zero and return a trigger information that the reception failed to the recipient account if the sub-number is zero. 45.The service provider under claim 41, where the service data transmission module is configured to: seek a second timestamp for receiving a request to send a service data group; and determine whether the second timestamp has expired; and seek a remaining subset of numbers in the subset of numbers, return the remaining subset of numbers to the sender account, and send the trigger information to the terminal corresponding to the sender account before the second timestamp expires.46.The server, pursuant to any one of claims 41 to 45, where the share parameter is N; after dividing the service data into subsets of numbers according to the share parameter, the server is also configured to: send the share parameter N simultaneously to each terminal from among the terminals corresponding to the recipient account; and after extracting the subsets of numbers from the subsets of numbers for the transfer of service numbers to the recipient account, the server is also configured to: page 13 of page 13, modify the share parameter N to (N-1) according to the service data request if the service data request sent by the first terminal of the terminal corresponding to the recipient account is received, and send the service data request response to the first terminal; and send the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account. 47.The server under claim 46, whereby after sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the server is also configured to: determine whether the share parameter (N-1) is greater than 0 if a request to retrieve service information sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; modify the share parameter (N-1) to the share parameter (N-2), send a response to the request for service information to the first or second terminal, and send the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and send a trigger command indicating completion of service information distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) equals 0.48.The server under claim 46, whereby a service request received which is sent by the first terminal is the first service request to arrive among service requests sent in sequence by the terminals corresponding to the recipient account.------------------15 / 03 / 2018------(OCR) Page 1 of 15 Claims 1. Method of transmitting service data packets which includes: broadcasting a matching request using a near-range wireless signal; matching with a matching recipient account within the near-range wireless signal and accepting the matching request; receiving the incoming service data; and generating a service packet transmission request based on the service data, transmitting the service packet transmission request to the server, and transmitting the service data to the server so that the server group transmits the service data to the terminals corresponding to the recipient accounts based on the service packet transmission request. 2.The method for transmitting service data groups under claim 1, where the process of broadcasting the pairing request via near-range wireless signal includes the generation of a pairing identifier and the broadcasting of the pairing identifier via near-range wireless signal; and the process of pairing with a recipient account within the near-range wireless signal range that accepts the pairing request includes the uploading of the pairing identifier to the server, and the receipt of the recipient account returned by the server and corresponding to the pairing identifier.

3. The method for transmitting service data groups under claim 1, where the process of pairing with a recipient account within the near-range wireless signal range that accepts the pairing request includes: receiving the acknowledgment returned by the terminal corresponding to the recipient account via near-range wireless signal, where each acknowledgment contains a unique pairing identifier corresponding to one recipient account from among the recipient accounts listed on page 2 of 15 pages 4.The method for transmitting service data groups under claim 3, whereby after the acknowledgment received from the corresponding terminal account via a near-range wireless signal, also includes the transmission of a dedicated identifier corresponding to the sender account and a dedicated identifier corresponding to the recipient account to the server.

5. The method for transmitting service data groups under any one of claims 1 to 4, whereby the process of receiving the incoming service data also includes searching for the service data network storage path; and the process of generating a request to transmit the service data group according to the service data and the process of sending the service data group request to the server also includes generating a request to transmit the service data group via the service data network storage path and sending the request to the server so that the server transmits the service data via the network storage path to the corresponding terminal account, and the corresponding terminal account downloads the service data via the network storage path. 6.The method for sending service data groups under claim 2, where the upload process for matching the server identifier includes searching for the sender account and uploading the sender account (7). The method for sending service data groups under any one of claims 3, 4, and 6, where the data type of the service data is numeric; and the process for receiving the imported service data includes receiving the imported service data that corresponds to the sender account so that the server can transfer the service numbers between the sender and recipient accounts according to the service data (8).The method for sending service data sets according to claim 7, where the procedure for receiving the imported service data that corresponds to the sender account, also includes: receiving the imported share parameters; and page 3 of the 15-page procedure for generating a request to send the service data set according to the service data and sending the request to send the service data set to the server also includes: adding share parameters to the request to send the service data set so that the server can divide the service data into subsets according to the share parameters and extract the subsets from the subsets for the recipient account to proceed with the service data transfer 9.The method for sending service data groups under claim 7 involves, after the process of receiving the imported service data that corresponds to the sender account, including: displaying the identification verification window; searching for the imported identification verification information that corresponds to the sender account using the identification verification window; sending the identification verification information to the server for verification; and performing the steps of generating a request to send the service data group based on the service data. Finally, the request to send the service data group is sent to the server upon receiving a verification successful message returned by the server. 10.The method for transmitting service data groups under claim 7, whereby after the pairing process with the recipient account is within the near-range wireless signal and the pairing request is accepted, the method also includes: displaying the recipient account on the display interface; and after the process of generating the service data group transmission request and sending the service data group transmission request to the server, the method also includes: receiving the recipient account returned by the server and its receiving status is acknowledged, and displaying a trigger on the display interface for the received recipient account.11.The method for sending service data groups based on claim 10, after the recipient account display process on the display interface, includes: receiving the chain addition request via the display interface and searching for recipient accounts that correspond to the chain addition request and are selected on the display interface; and on page 4 of 15, generating the chain addition request based on the selected recipient account and sending the chain addition request to the server so that the server can create a chain transmission diagram between the sender account and the selected recipient account.12.The method for sending service data groups under claim 4, whereby the process of sending the service data to the service provider's terminal and the service data set corresponding to the sender's account and the service data set corresponding to the recipient's account, also includes access to the service data distribution interface, and displaying the service data obtained by the terminal corresponding to the recipient's account on the service data distribution interface; and the process of sending the service data to the service provider includes: sending the service data displayed on the service data distribution interface to the service provider.13.The method for forwarding service data between terminals consists of: searching for the sender account and the recipient account, where the recipient account is within the near-range wireless signal of the terminal corresponding to the sender account, and accepting the transmission of the pairing request signal by the terminal corresponding to the sender account; receiving the request to send the uploaded service data group by the terminal corresponding to the sender account and searching for the service data based on the service data group transmission request; and sending the service data to the terminal corresponding to the recipient account.14.The method for forwarding service data between terminals under claim 13, where the procedure for retrieving sender and recipient accounts, consists of: receiving the uploaded matching identifier and retrieving the sender account corresponding to the matching identifier; and receiving the add-and-match request, retrieving the user account included in the add-and-match request when the add-and-match request includes the matching identifier, and using the user account as the recipient account, where the matching identifier is broadcast, signaled by the terminal corresponding to the sender account to the terminal corresponding to the recipient account via a near-range wireless signal.

15. The method for forwarding service data between terminals under claim 13, where page 5 of page 15, the procedure for retrieving sender and recipient accounts consists of: receiving the uploaded unique identifier from the terminal corresponding to the sender account and retrieving the sender and recipient accounts corresponding to the unique identifier.16.The method for forwarding service data between terminals under claim 13, where the data type of the service data is numerical; and the procedure for sending service data to the terminal corresponding to the recipient account is: the operation of transferring service numbers between the sender account and the recipient account according to the service data, and the transmission of the trigger information corresponding to the transfer of service numbers to the recipient account.

17. The method for forwarding service data between terminals under claim 16, where, after the procedure of receiving the request to send the uploaded service data group by the terminal corresponding to the sender account, the method also includes: extracting the share parameters corresponding to the transfer of service numbers according to the request to send the service data group; and dividing the service data into sub-sets of numerical values ​​according to the share parameters; and the procedure for transferring service numbers between the sender account and the recipient account according to the service data also includes: extracting sub-numbers from the sub-number set for the operation of transferring service numbers to the recipient account.18.The method for forwarding service data between terminals under claim 17, whereby the preceding step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account, includes the method of receiving the specific work order uploaded by receiving the terminal corresponding to the recipient account and extracting the first timestamp; and the step of extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account also includes: sequential transmission of service data to the corresponding terminal recipient account according to the first timestamp (page 6 of section 15, page 19).The method for forwarding service data between terminals under claim 17, where the procedure for retrieving the sender and recipient accounts includes: retrieving the number of recipients in the recipient account; and the procedure for extracting subdigits from the subdigit set for transferring service data to the recipient account includes: determining whether the number of recipients exceeds the share tariff and returning trigger information indicating that the reception failed to the recipient account if the number of recipients exceeds the share tariff.

20. The method for forwarding service data between terminals under claim 17, where the procedure for sending service data to the terminal corresponding to the recipient account includes: determining whether the subdigit set is zero and returning trigger information indicating that the reception failed to the recipient account if the subdigit set is zero. 21.The method for forwarding service data between terminals under claim 17, whereby the procedure for receiving a request to send the uploaded service data set by the terminal corresponding to the sender account, includes: searching for a second time stamp for the receipt of the service data set request; and the method also includes: determining whether the second time stamp has expired; and searching for the remaining sub-number in the sub-number set, returning the remaining number to the sender account, and sending the trigger information to the terminal corresponding to the sender account before the second time stamp expires. 22.The method for forwarding service data between terminals according to any one of the claims 17 to 21, where the share parameter is N; after the process of dividing the service data into subsets according to the share parameter, the method also includes sending the share parameter N simultaneously to each terminal among the terminals corresponding to the recipient account; and on page 7 of 15, after the process of extracting subsets from the subsets for transferring service data to the recipient account, the method also includes converting the share parameter N to (N-1) according to the service data request if the service data request sent by the first terminal of the terminal corresponding to the recipient account is received and the service data request response is sent to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account.23.The method for forwarding service data between terminals under claim 22, whereby after the process of sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the method also includes determining whether the share parameter (N-1) is greater than 0; a request to retrieve service data sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; modifying the share parameter (N-1) to a share parameter (N-2), sending a response requesting service data to the first or second terminal, and sending the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and sending a trigger command indicating completion of the service data distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is equal to 0. 24.The method for forwarding service information between terminals under claim22, whereby a service request received by the first terminal is the first service request to arrive among sequential service requests sent by the terminals corresponding to the recipient account25.The terminal consists of: memory configured to store computer-readable program code; and a processor configured to execute the computer-readable program code to perform the following operations: broadcasting a pairing request via near-range wireless signal; pairing with a recipient account within near-range wireless signal and accepting the pairing request; receiving incoming service data; and generating a service group request based on the service data, sending the service group request to the server, and sending the service data to the server so that the server group can send the service data to the corresponding terminal account according to the service group request.26.The terminal under claim 25, whereby the processor is configured to execute computer-readable program code to broadcast pairing requests via a near-range wireless signal, shall include: the generation of a pairing identifier and the broadcasting of the pairing identifier via a near-range wireless signal; and whereby the processor is configured to execute computer-readable program code to pair with recipient accounts within the range of a near-range wireless signal and accept pairing requests, shall include: the uploading of the pairing identifier to the server and the receipt of recipient accounts returned by the server and corresponding to the pairing identifier 27.The terminal under claim 25, whereby the processor is configured to execute computer-readable program code to match with recipient accounts within the range of a near-range wireless signal and accept such matching requests, includes page 9 of 15, receiving acknowledgments returned via a near-range wireless signal by the terminal corresponding to the recipient account, whereby each acknowledgment contains a unique identifier corresponding to one of the recipient accounts.

28. The terminal under claim 27, whereby after executing computer-readable program code to receive acknowledgments returned via a near-range wireless signal by each terminal among the terminals corresponding to the recipient account, the processor then performs the following operation: sending the unique identifier corresponding to the sender account and the unique identifier corresponding to the recipient account to the server. 29.A terminal under any of the claims 25 through 28 whereby the processor is configured to execute computer-readable code to receive input service data, includes the search for the service data network storage path; and whereby the processor is configured to execute computer-readable code to generate a service data packet request and send the service data packet request to the server, includes the generation of the service data packet request along the service data network storage path and the sending of the service data packet request to the server so that the server sends the service data along the network storage path to the terminal corresponding to the recipient account and the terminal corresponding to the recipient account downloads the service data along the network storage path.30.A terminal under claim 26 where the processor is configured to execute computer-readable program code to upload a matching identifier to the server shall include: retrieving the sender account and uploading it to the sender account.

31. A terminal under any of claims 27, 28 and 30 where the data type of the service data is numeric; and page 10 of 15 where the processor is configured to execute computer-readable program code to retrieve the incoming service data shall include: retrieving the incoming service data corresponding to the sender account so that the server can transfer the service number between the sender account and the retriever account according to the service data. 32.The terminal under claim 31, whereby the processor is configured to execute computer-readable program code to seize the incoming service data corresponding to the sender account, shall include the seizing of the incoming share parameters; and whereby the processor is configured to execute computer-readable program code to generate a request to send the service data set according to the service data and send the request to send the service data set to the server, shall include the addition of share parameters to the request to send the service data set so that the server divides the service data into subsets according to the share parameters and extracts subsets from the subsets for the seizing account for the transfer of service numbers. 33.The terminal, pursuant to claim 31, after executing computer-readable program code to extract the imported service data corresponding to the sender account, the processor then performs the following operations: displaying the identity verification window, searching for the imported identity verification information corresponding to the sender account based on the identity verification window, sending the identity verification information to the server for verification, generating a request to send the service data group based on the service data, and sending the request to send the service data group to the server when the verification successful message returned by the server is received.34.The terminal, pursuant to claim 31, after executing computer-readable program code to match with a forfeit account within the range of the near-range wireless signal and accepting the forfeit matching request, the processor then performs the following operations: displays the forfeit account on the display interface; and on page 11 of 15, after executing computer-readable program code to generate a request to send a service data group and sending the request to send a service data group to the server, the processor then performs the following operations: receives the recipient account returned by the server and its receiving status is accepted, and displays the trigger for the received recipient account on the display interface. 35.The terminal, under claim 34, after executing computer-readable program code to display the recipient account on the interface, the processor performs the following operations: receiving the chain addition command via the interface and searching for the recipient account corresponding to the chain addition command and selection on the interface; and generating a chain addition request based on the selected recipient account and sending the chain addition request to the server so that the server constructs the chain flowchart between the sender account and the selected recipient account. 36.The terminal under claim 27 or 28, whereby after executing computer-readable program code to send the corresponding use set identifier to the sender account and the corresponding use set identifier to the recipient account to the server, the processor then performs the following operations: accessing the service distribution interface, and displaying the service information obtained by the terminal corresponding to the recipient account on the service distribution interface; and that the processor is configured to execute computer-readable program code to send service information to the server, including sending the service information displayed on the service distribution interface to the server. 37.The server consists of: memory configured to store computer-readable program code; and a processor configured to execute the computer-readable program code to perform the following operations: (page 12 of 15) Searching for and acquiring sender and receiver accounts where the receiver account is within the near-range wireless signal of the terminal corresponding to the sender account and accepts a pairing broadcast request from the terminal corresponding to the sender account; receiving a request to send service data packets uploaded by the terminal corresponding to the sender account and searching for service data according to the service data packet request; and sending service data to the terminal corresponding to the receiver account. (38)The server under claim 37, where the processor is configured to execute computer-readable program code to retrieve sender and recipient accounts, includes: receiving uploaded matching identifiers and retrieving the sender account corresponding to the matching identifier; and receiving add-and-match requests, retrieving the user account present in the add-and-match request when the add-and-match request includes a matching identifier, and using the user account as the recipient account, where the matching identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the recipient account via near-range wireless signal.

39. The server under claim 37, where the processor is configured to execute computer-readable program code to retrieve sender and recipient accounts, includes: receiving uploaded proprietary identifiers from the terminal corresponding to the sender account and retrieving the sender and recipient accounts corresponding to the proprietary identifier.40.The service provider, under claim 37, where the data type of the service data is numeric; that the processor is configured to execute computer-readable program code to send service data to the terminal corresponding to the recipient account, shall include the operation of transferring the service number between the sender and recipient accounts according to the service data and the transmission of the trigger information corresponding to the transfer of the service number to the recipient account. (Page 13 of 15, page 41)The service provider, pursuant to claim 40, after executing computer-readable program code to receive a request to send a service data set uploaded by the terminal corresponding to the sender account, the processor then performs the following operations: extracting the share parameters corresponding to the service number transfer in the service data set request; and dividing the service data into sub-sets of numbers according to the share parameters; and that the processor is configured to execute computer-readable program code to perform the service number transfer between the sender and recipient accounts based on the included service data; and extracting sub-sets of numbers from the sub-sets of numbers for the service number transfer to the recipient account. 42.The service provider under claim 41, whereby prior to executing computer-readable program code to extract sub-numbers from the sub-number set for the transfer of service numbers to the recipient account, the processor also performs the following operations: receiving the specific use order uploaded by the terminal corresponding to the recipient account and extracting the first timestamp; and that the processor being configured to execute computer-readable program code to extract sub-numbers from the sub-number set for the transfer of service numbers to the recipient account shall include the sequential transmission of service data to the terminal corresponding to the recipient account according to the first timestamp.43.The server under claim 41, whereby the processor is configured to execute computer-readable program code to retrieve the sender account and recipient account, including the number of recipient accounts; and the processor is configured to execute computer-readable program code to extract sub-digits from the sub-digit set for the transfer of service numbers to the recipient account, including page 14 of 15, the decision determines whether the number of recipients exceeds the sub-digit parameter and returns a trigger information that the reception failed to the recipient account if the number of recipients exceeds the sub-digit parameter.

44. The server under claim 41, whereby the processor is configured to execute computer-readable program code to send service data to the corresponding terminal to the recipient account, including: the decision determines whether the sub-digit set is zero and a trigger information that the reception failed is returned to the recipient account if the sub-digit set is zero. 45.The service machine under claim 41, whereby the processor is configured to execute computer-readable code to receive requests to submit service data packets uploaded by terminals corresponding to the sender account, shall include the search for a second timestamp for receipt of service data packet requests; and that the processor is configured to execute computer-readable code to perform the following operations: determining whether the second timestamp has expired; and the search for the remaining sub-digits in the sub-digits set, which returns the remaining sub-digits to the sender account and sends a trigger information to the terminals corresponding to the sender account if the second timestamp has expired.46.The service provider operates under one of the claims 41 to 45, where the share parameter is N; after executing the computer-readable program code to divide the service data into subsets of numbers according to the share parameter, the processor performs the following operations: simultaneously sending the share parameter N to each terminal from among the terminals corresponding to the recipient account; and after executing the computer-readable program code to extract the subsets of numbers for the transfer of service numbers to the recipient account, the processor performs the following operations: on page 15 of page 15, modifying the share parameter N to (N-1) according to the service data request; if the service data request sent by the first terminal of the terminal corresponding to the recipient account is received, and sending the service data request response to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account. 47.The server operates under claim 46, whereby after executing the program code readable by the computer to send the share parameter (N-1) to each terminal among those corresponding to the recipient account, the processor then performs the following operations: determining whether the share parameter (N-1) is greater than 0; a request to retrieve service data sent by the first or second terminal among those corresponding to the recipient account is continuously received; converting the share parameter (N-1) to a share parameter (N-2); sending a response to retrieve service data to the first or second terminal; and sending the share parameter (N-2) to each terminal among those corresponding to the recipient account if the share parameter (N-1) is greater than 0; and sending a command indicating completion of service data distribution to each terminal among those corresponding to the recipient account if the share parameter (N-1) is equal to 0.The server, as per claim 46, whereby a service request received by a first terminal is the first service request to arrive among service requests sequentially sent by terminals corresponding to the recipient account. ------------ Page 1 of 14 pages of claim 1. Method of service group transmission which includes: broadcasting of a matching request via short-range wireless signal; matching with a matching recipient account within the short-range wireless signal range and accepting the matching request; receiving the incoming service data; and generating a service group transmission request based on the service data, sending the service group transmission request to the server, and sending the service data to the server so that the server group can transmit the service data to the terminals corresponding to the recipient accounts based on the service group transmission request. 2.The method for transmitting service data groups under Claim 1, where the pairing request transmission procedure via short-range wireless signal includes: generating a pairing identifier and transmitting the pairing identifier via short-range wireless signal; and the pairing procedure with a receiver account within short-range wireless range that accepts the pairing request includes: uploading the pairing identifier to the server, and receiving the receiver account returned by the server and corresponding to the pairing identifier.

3. The method for transmitting service data groups under Claim 1, where the pairing procedure with a receiver account within short-range wireless range that accepts the pairing request includes: receiving the acknowledgment returned by the terminal corresponding to the receiver account via short-range wireless signal, where each acknowledgment contains a unique pairing identifier corresponding to one receiver account from among the receiver accounts. 4.The method for sending service data groups under claim 3, whereby after the acknowledgment received from the terminal corresponding to the receiver account via short-range wireless signal, the method also includes: sending a dedicated identification set corresponding to the transmitter account and a dedicated identification set corresponding to the receiver account to the server (page 2 of 14, page 5).The method for sending service data packets under any of Claims 1 through 4, where the process for receiving the imported service data includes: searching for the network storage path of the service data; and the process for generating a request to send the service data packet based on the service data and sending the request to the server includes: generating a request to send the service data packet along the network storage path of the service data and sending the request to the server so that the server packet sends the network storage path to the terminal corresponding to the recipient account, and the terminal corresponding to the recipient account downloads the service data along the network storage path.

6. The method for sending service data packets under Claim 2, where the upload process for the server matching identifier includes: searching for the sender account and uploading the sender account. 7.The method for sending service data groups under any of Claims 3, 4, and 6, where the data type of the service data is numeric; and the procedure for receiving the imported service data includes: receiving the imported service data corresponding to the sending account so that the server can transfer the service numbers between the sending and receiving accounts according to service data 8. The method for sending service data groups under Claim 7, where the procedure for receiving the imported service data corresponding to the sending account, also includes: receiving the share parameters for import; and the procedure for generating a request to send the service data group according to the service data and sending the request to send the service data group to the server also includes: adding the share parameters to the request to send the service data group so that the server can divide the service data into subsets of numeric numbers according to the share parameters and extract the subsets of numeric numbers from the subsets for the receiving account to transfer the service numbers 9.The method for sending service data groups under claim 7, after the process of receiving the imported service data that corresponds to the sender account, includes: presenting the identity verification window, searching for the imported identity verification information that corresponds to the sender account using the identity verification window, sending the identity verification information to the server for verification, and performing the request generation procedure (page 3 of 14, request to send service data groups based on the service data), and sending the request to send service data groups to the server upon receiving a verification successful message returned by the server. 10.The method for transmitting service data groups under claim 7, whereby after the pairing procedure with a receiving account within the short-range wireless signal and accepting the pairing request, the method also includes: presenting the receiving account on the display interface; and after the procedure for generating a request to transmit service data groups based on the service information and sending the request to transmit service data groups to the server, the method also includes: receiving the receiving account which is returned by the server and its receiving status is accepted, and presenting on the display interface a trigger for the received receiving account.11.The method for sending service data groups based on claim 10, after the receiver account presentation step on the display interface, also includes: receiving the chain addition command via the display interface and searching for receiver accounts corresponding to the chain addition command and selected on the display interface; and generating a chain addition request based on the selected receiver account and sending the chain addition request to the server so that the server can create a chain transmission diagram between the selected sender and receiver accounts.12.The method for transmitting service data groups under claim 4, whereby after the process of transmitting the service device to the specific use set indicator corresponding to the sending device account and the specific use set indicator corresponding to the receiving device account, the method also includes: passing into the service data distribution interface, and presenting the service data obtained by the terminal corresponding to the receiving device account on the service data distribution interface; and the process of transmitting service data to the service device includes: transmitting the service data presented on the service data distribution interface to the service device.13.The method for forwarding service data between terminals includes: searching for the transmitter account and receiver account, where the receiver account is within the short-range wireless signal range of the terminal corresponding to the transmitter account; and accepting the transmission of a matching request by the terminal corresponding to the transmitter account; page 4 of 14: receiving a request to send the uploaded service data group by the terminal corresponding to the transmitter account and searching for the service data based on that request; and sending the service data to the terminal corresponding to the receiver account.The method for forwarding service information between terminals under claim 13, where the procedure for retrieving the transmitter account and the receiver account, consists of: receiving the uploaded matching identifier and retrieving the transmitter account corresponding to the matching identifier; and receiving the add-and-match request, retrieving the user account contained in the add-and-match request when the add-and-match request includes the matching identifier, and using the user account as the receiver account, where the matching identifier is transmitted by the terminal corresponding to the transmitter account to the terminal corresponding to the receiver account via a short-range wireless signal.

15. The method for forwarding service information between terminals under claim 13, where the procedure for retrieving the transmitter account and the receiver account, consists of: receiving the uploaded dedicated set identifier from the terminal corresponding to the transmitter account and retrieving the transmitter and receiver accounts corresponding to the dedicated set identifier.16.The method for forwarding service data between terminals under claim 13, where the data type of the service data is numerical; and the procedure for sending service data to the terminal corresponding to the recipient account is: performing the transfer of service numbers between the sending account and the receiving account according to the service data, and sending the trigger information corresponding to the transfer of service numbers to the receiving account.

17. The method for forwarding service data between terminals under claim 16, where, after the procedure of receiving the request to send the uploaded service data group by the terminal corresponding to the sending account, the method also includes: extracting the share parameters corresponding to the transfer of service numbers according to the request to send the service data group; and dividing the service data into sub-sets of numbers according to the share parameters; and the procedure for transferring service numbers between the sending account and the receiving account according to the service data also includes: page 5 of page 14, extracting sub-numbers from the sub-set of numbers for the transfer of service numbers to the receiving account.18.The method for forwarding service data between terminals under claim17, whereby the pre-extraction step involves extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account, includes: a specific use order received by the receiving terminal corresponding to the recipient account and the extraction of the first time stamp; and the step for extracting sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account includes: sequential transmission of service data to the corresponding terminal recipient account based on the first time stamp.19.The method for forwarding service data between terminals under claim 17, where the procedure for retrieving the sender and receiver accounts, also includes: retrieving the number of receivers in the receiver account; and the procedure for extracting sub-digits from the sub-digit set for transferring service numbers to the receiver account also includes: determining whether the number of receivers exceeds the sharing parameter and returning information indicating that the reception failed to the receiver account due to the number of receivers exceeding the sharing parameter.

20. The method for forwarding service data between terminals under claim 17, where the procedure for sending service data to the terminal corresponding to the receiver account, also includes: determining whether the sub-digit set is zero and returning information indicating that the reception failed to the receiver account due to the sub-digit set being zero. 21.The method for forwarding service data between terminals under claim 17, where the procedure for receiving a request to send the uploaded service data set by the terminal corresponding to the sending account, also includes: searching for a second timestamp for receiving the request to send the service data set; and the method also includes: page 6 of the 14-page decision determining whether the second timestamp has expired; and searching for the remaining sub-number in the sub-number set, returning the remaining number to the sending account, and sending the trigger information to the terminal corresponding to the sending account if the second timestamp has expired.22.The method for forwarding service data between terminals according to any one of claims 17 to 21, where the share parameter is N; after the process of dividing the service data into subsets of numbers according to the share parameter, the method also includes: simultaneously sending the share parameter N to each terminal among the terminals corresponding to the recipient account; and after the process of extracting the subsets of numbers from the subsets of numbers for the transfer of service numbers to the recipient account, the method also includes: modifying the share parameter N to (N-1) according to the service data request if the service data request sent by the first terminal of the terminal corresponding to the recipient account is received and sending the service data request response to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account. 23.The method for forwarding service data between terminals under claim 22, whereby after the procedure of sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account, the method also comprises: determining whether the share parameter (N-1) is greater than 0 if a request to retrieve service data sent by the first or second terminal from among the terminals corresponding to the recipient account is continuously received; modifying the share parameter (N-1) to a share parameter (N-2), sending a response requesting service data to the first or second terminal, and sending the share parameter (N-2) to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is greater than 0; and sending a trigger command indicating completion of the service data distribution to each terminal from among the terminals corresponding to the recipient account if the share parameter (N-1) is equal to 0. (Page 7 of 14, page 24.)The method for forwarding service information between terminals under claim 22, whereby a service request received by a first terminal is the first service request to arrive among sequential service requests sent by terminals corresponding to recipient account 25.A terminal consists of: memory configured to store computer-readable program code; and a processor configured to execute the computer-readable program code to perform the following operations: broadcasting a matching request via a short-range wireless signal; matching with a receiver account within the short-range wireless signal range and accepting the matching request; receiving incoming service data; and generating a service group transmission request based on the service data, transmitting the service group transmission request to the server, and transmitting the service data to the server so that the server group can transmit the service data to the terminal corresponding to the receiver account based on the service group transmission request.26.The terminal under claim 25, whereby the processor is configured to execute computer-readable program code to broadcast matching requests via short-range wireless signals, shall include: the generation of a matching identifier and the broadcasting of the matching identifier via short-range wireless signals; and whereby the processor is configured to execute computer-readable program code to match with receiver accounts within short-range wireless range and accept matching requests, shall include: the uploading of the matching identifier to the server and the receipt of receiver accounts returned by the server and corresponding to the matching identifier 27.The terminal under claim 25, whereby the processor is configured to execute computer-readable program code to match a receiver account within short-range wireless range and accept such matching request, consists of: Page 8 of 14, receiving acknowledgments returned via short-range wireless signal by the terminal corresponding to the receiver account, whereby each acknowledgment consists of a unique set identifier corresponding to one receiver account from among the receiver accounts.

28. The terminal under claim 27, whereby after executing computer-readable program code to receive acknowledgments returned via short-range wireless signal by each terminal from among the terminals corresponding to the receiver account, the processor then performs the following operation: sending the unique set identifier corresponding to the transmitter account to the unique set identifier corresponding to the receiver account to the server. 29.A terminal under any of the claims 25 through 28 whereby the processor is configured to execute computer-readable code to receive incoming service data includes: seeking the network storage path of the service data; and whereby the processor is configured to execute computer-readable code to generate a request to send the service data group based on the service data and sending the request to send the service data group to the server includes: generating a request to send the service data group based on the service data network storage path and sending the request to send the service data group to the server so that the server group sends the network storage path to the terminal corresponding to the recipient account and the terminal corresponding to the recipient account downloads the service data along the network storage path.30.A terminal under claim 26 where the processor is configured to execute computer-readable program code for uploading matching identifiers to the server shall include: seeking the sender account and uploading it to the sender account.

31. A terminal under any of claims 27, 28 and 30 where the data type of the service data is numeric; and where the processor is configured to execute computer-readable program code for receiving incoming service data shall include: receiving the incoming service data corresponding to the sender account so that the server can transfer the service number between the sender and receiver accounts according to the service data on page 9 of the 14 pages of 32.The terminal under claim 31, whereby the processor is configured to execute computer-readable program code to receive incoming service data corresponding to the sender account, shall include: receiving share parameters for import; and whereby the processor is configured to execute computer-readable program code to generate a request to send a service data set according to the service data and to send the request to send a service data set to the server, shall include: adding share parameters to the request to send a service data set so that the server can divide the service data into subsets according to the share parameters and extract subsets from the subsets for the receiver account for the transfer of service numbers.33.The terminal, under claim 31, after executing computer-readable program code to receive the input service information corresponding to the sender account, the processor then performs the following operations: presents the identity verification window; searches for the input identity verification information corresponding to the sender account based on the identity verification window; sends the identity verification information to the server for verification and generates a request to send the service data group based on the service information; and sends the request to send the service data group to the server when the verification successful message returned by the server is received.34.The terminal under claim 31, whereby after executing computer-readable program code to match a receiver account within short-range wireless signal range and accepting the matching request, the processor then performs the following operations: presenting the receiver account on the display interface; and after executing computer-readable program code to generate a request to send a service data group according to the service data and sending the request to send a service data group to the server, the processor then performs the following operations: receiving the receiver account returned by the server and the receiving condition of the account is received, and presenting the trigger for the received receiver account on the display interface.35.The terminal, under claim 34, after executing the computer-readable program code to display the receiver account on the interface, the processor performs the following operations: Page 10 of page 14: receiving the add-chain command via the interface and searching for the receiver account corresponding to the add-chain command and selection on the interface; and generating the add-chain request based on the selected receiver account and sending the add-chain request to the server so that the server creates a chain diagram between the selected sender and receiver accounts.36.The terminal under claim 27 or 28, whereby after executing computer-readable program code to send the corresponding serial number identifier to the sender account and the corresponding serial number identifier to the receiver account to the server, the processor then performs the following operations: passing into the Service Distribution Interface, and presenting the service data obtained by the terminal corresponding to the receiver account on the Service Distribution Interface; and that the processor is configured to execute computer-readable program code to send the service data to the server, including: sending the service data presented on the Service Distribution Interface to the server. 37.The server consists of: memory configured to store computer-readable program code; and a processor configured to execute the computer-readable program code to perform the following operations: searching for a transmitter-receiver account where the receiver account is within the short-range wireless signal of the terminal corresponding to the transmitter account and accepting a matching broadcast request from the terminal corresponding to the transmitter account; receiving a service data packet transmission request uploaded by the terminal corresponding to the transmitter account and searching for service data based on the service data packet transmission request; and transmitting service data to the terminal corresponding to the receiver account.38.The server under claim 37, where the processor is configured to execute computer-readable program code to retrieve the sender and receiver accounts, shall consist of: page 11 of 14, receiving the uploaded matching identifier and retrieving the sender account corresponding to the matching identifier; and receiving the add-and-match request, retrieving the user account contained in the add-and-match request when the add-and-match request includes a matching identifier, and using the user account as the receiver account, where the matching identifier is broadcast by the terminal corresponding to the sender account to the terminal corresponding to the receiver account via a short-range wireless signal.39.A service provider under claim 37 where the data type of the service data is numeric; where the processor is configured to execute computer-readable program code to retrieve sender and receiver accounts, shall include: receiving the use set identifier uploaded from the terminal corresponding to the sender account and retrieving the sender and receiver accounts corresponding to the use set identifier.

40. A service provider under claim 37 where the data type of the service data is numeric; where the processor is configured to execute computer-readable program code to send the service data to the terminal corresponding to the receiver account, shall include: performing the transfer of the service number between the sender and receiver accounts according to the service data and sending the trigger information corresponding to the transfer of the service number to the receiver account.41.The processor operates under claim 40, whereby after executing computer-readable program code to receive a request to send a service data set uploaded by the terminal corresponding to the sending account, the processor performs the following operations: extracting the share parameters corresponding to the service number transfer in the service data set request; and dividing the service data into subsets of numbers according to the share parameters; and that the processor is configured to execute computer-readable program code to perform the service number transfer between the sending and receiving accounts based on the service data, including: extracting subsets of numbers from the subsets of numbers for the service number transfer to the receiving account. (Page 12 of 14, page 42.)The service provider under claim 41, whereby prior to executing computer-readable program code to extract sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account, the processor performs the following operations: receiving the specific use order uploaded by the terminal corresponding to the recipient account and extracting the first timestamp; and that the processor being configured to execute computer-readable program code to extract sub-numbers from the sub-number sequence for the transfer of service numbers to the recipient account shall include: sending sequential service data to the terminal corresponding to the recipient account according to the first timestamp.43.The service provider under claim 41, whereby the processor is configured to execute computer-readable program code to retrieve the sender account and receiver account, shall consist of: the number of receivers in the receiver account; and the processor is configured to execute computer-readable program code to extract sub-digits from the sub-digit set for the transfer of service numbers to the receiver account, shall consist of: a decision determining whether the number of receivers exceeds the share parameter and returning trigger information that the reception failed to the receiver account if the number of receivers exceeds the share parameter.

44. The service provider under claim 41, whereby the processor is configured to execute computer-readable program code to send service data to the terminal corresponding to the receiver account, shall consist of: a decision determining whether the sub-digit set is zero or not and trigger information that the reception failed to the receiver account if the sub-digit set is zero. 45.The service machine under claim 41, whereby the processor is configured to execute computer-readable program code to receive service packet submission requests uploaded by terminals corresponding to the sender account, shall include: retrieving the second timestamp for service packet submission requests; and page 13 of page 14, whereby the processor is configured to execute computer-readable program code to perform the following operations: determining whether the second timestamp has expired; and retrieving the remaining sub-digits in the sub-digits set, which returns the remaining sub-digits to the sender account, and sending the trigger information to the terminals corresponding to the sender account if the second timestamp has expired.46.The service provider operates under one of the claims 41 to 45, where the share parameter is N; after executing the computer-readable program code to divide the service data into subsets according to the share parameter, the processor performs the following operations: simultaneously sending the share parameter N to each terminal from among the terminals corresponding to the recipient account; and after executing the computer-readable program code to extract the subsets for transferring the service data to the recipient account, the processor performs the following operations: modifying the share parameter N to (N-1) upon the service data request after the service data request sent by the first terminal of the terminal corresponding to the recipient account is received, and sending the service data request response to the first terminal; and sending the share parameter (N-1) to each terminal from among the terminals corresponding to the recipient account.The service provider, as per claim 46, states that after executing the program code readable by the computer to send the share parameter (N-1) to each terminal among those corresponding to the recipient account, the processor then performs the following operations: determining whether the share parameter (N-1) is greater than 0; continuing the request to retrieve service data sent by the first or second terminal among those corresponding to the recipient account; modifying the share parameter (N-1) to a share parameter (N-2); sending the service data retrieval response to the first or second terminal; and sending the share parameter (N-2) to each terminal among those corresponding to the recipient account if the share parameter (N-1) is greater than 0; and on page 14 of the trigger command, indicating completion of the distribution of service data to each terminal among those corresponding to the recipient account if the share parameter (N-1) equals 0.The service provider pursuant to claim 46, whereby a service request received which is sent by a first terminal is the first service request to arrive among the sequential service requests sent by the terminals corresponding to the recipient account;