WO2014101643A1 - 组队方法、客户端、服务器及系统 - Google Patents

组队方法、客户端、服务器及系统 Download PDF

Info

Publication number
WO2014101643A1
WO2014101643A1 PCT/CN2013/088659 CN2013088659W WO2014101643A1 WO 2014101643 A1 WO2014101643 A1 WO 2014101643A1 CN 2013088659 W CN2013088659 W CN 2013088659W WO 2014101643 A1 WO2014101643 A1 WO 2014101643A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
team
identifier
request
server
Prior art date
Application number
PCT/CN2013/088659
Other languages
English (en)
French (fr)
Inventor
杨雪绸
王有斌
徐光兴
Original Assignee
广州华多网络科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 广州华多网络科技有限公司 filed Critical 广州华多网络科技有限公司
Priority to US14/654,052 priority Critical patent/US20150341432A1/en
Priority to KR1020157020078A priority patent/KR20150102079A/ko
Priority to SG11201504938TA priority patent/SG11201504938TA/en
Publication of WO2014101643A1 publication Critical patent/WO2014101643A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H04L67/1048—Departure or maintenance mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H04L67/1046—Joining mechanisms

Definitions

  • the present invention relates to the field of Internet communications, and in particular, to a teaming method, a client, a server, and a system.
  • the Team Voice tool is a widely used and popular instant messaging program. Commonly used for multi-person conferences, online teaching, team collaboration and multiplayer K Song and other application scenarios. Common teaming methods when team collaboration is used for team collaboration, including: the current client enters or establishes an empty channel in the team voice tool, and passes the channel number of the channel to other clients that need to be teamed up. For example, the user of the current client informs the channel number by telephone, sends it by SMS, or sends the text message to other users through instant messaging text; other clients know the channel number of the channel, according to the channel number of the channel. The channel is added to the team voice tool so that all clients that need to team up enter the same channel and then have voice communication within the channel.
  • the inventors have found that at least the following problems exist in the prior art: the current client must pass the channel number to other clients that need to be teamed, and other clients can complete the teaming process only after knowing the channel number. If the user using the current client and the user using the other client are two users who are not recognized, the team operation cannot usually be completed smoothly.
  • the embodiment of the present invention provides a teaming method, a client, a server, and a system.
  • a team formation method comprising: Receiving a team initiation request sent by the first client in the current channel, where the team initiation request carries an identifier of the first client; Sending team state information to all clients in the current channel, where the team state information includes a total number of card slots, a content type of the card slots, a correspondence between each card slot and an identifier of the queued client, and All four items or the first three items in the enqueue request, the corresponding relationship includes a correspondence between the first card position and the identifier of the first client; Receiving a team join request sent by the second client in the current channel, where the team join request includes an identifier of the second client and a card slot to be joined by the second client; Sending the group state information to all the clients in the current channel, where the correspondence relationship in the team state information includes a correspondence between the second card and the identifier of the second client; After all the cards have the identity of
  • the sending before sending the group state information to all the clients in the current channel, includes: Reading the group setting information preset by the client where the administrator of the current channel is located, where the team setting information includes all three of the card slots, the content type of the card slot, and the enqueue request or the former Two items.
  • the method further includes: Detecting whether the identifier of the enqueue client corresponding to the card slot to be joined by the second client is empty; If the detection result is that the identifier of the enqueue client corresponding to the card slot to be joined by the second client is empty, performing the step of resending the team state information to all clients in the current channel; If the detection result is that the identifier of the enqueue client corresponding to the card slot to be joined by the second client is not empty, the group status information is sent again to the second client, where the group status information is The current latest team status information.
  • the sending the group state information to all the clients in the current channel where the correspondence in the team state information includes the second card and the identifier of the second client
  • it also includes: Receiving a team exit request sent by the second client, where the team exit request includes an identifier of the second client and a card slot to be withdrawn by the second client;
  • the group state information is sent again to all the clients in the current channel, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information.
  • the method further includes: Detecting whether the identifier of the enqueue client corresponding to the card slot that the second client is to exit is the same as the identifier of the second client; If the detection result is that the identifier of the enqueue client corresponding to the card slot to be withdrawn by the second client is the same as the identifier of the second client, performing the resending to all clients in the current channel.
  • Steps of teaming state information If the detection result is that the identifier of the enqueue client corresponding to the card slot to be withdrawn by the second client is different from the identifier of the second client, the group status information is sent to the second client again.
  • the team status information is current latest group status information.
  • the sending the group state information to all the clients in the current channel where the correspondence in the team state information includes the second card and the identifier of the second client
  • it also includes: Receiving a kick-out player request sent by the first client, where the kick-out player request includes a correspondence between the second card position and an identifier of the second client;
  • the group state information is sent again to all the clients in the current channel, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information.
  • the method further includes: Detecting whether the identifier of the enqueue client corresponding to the second card slot in the kick-out player request is the same as the identifier of the second client; If the detection result is that the identifier of the enqueue client corresponding to the second card position in the kick-out player request is the same as the identifier of the second client, executing all the customers in the current channel The step of sending the team status information again; If the detection result is that the identifier of the enqueue client corresponding to the second card position in the kick-out player request is different from the identifier of the second client, send the team to the first client again.
  • Status information the team status information is current latest group status information.
  • the method further includes: Receiving a team state read request sent by the second client newly joining the current channel; sending the team state information to the second client, where the team state information is the current latest team state information.
  • the method further includes: Receiving a team cancellation request sent by the first client or the client where the administrator of the current channel is located, and the team cancellation request sent by the first client is triggered by the user or after the team initiates the request. a request that is automatically triggered after a predetermined period of time; Sending team state information to all clients in the current channel, where the team state information includes a total number of card slots, a content type of the card slots, a correspondence between each card slot and an identifier of the queued client, and All four items or the first three items in the enqueue request, the corresponding relationship is empty.
  • the networked clients corresponding to the respective card slots are moved into the same subchannel to complete the teaming, including: After the identifier of the queried client is corresponding to all the card slots, the team completion information sent by the client where the administrator of the current channel is located is received; After receiving the team completion information, the teamed clients corresponding to the respective card slots are moved into the same subchannel to complete the teaming.
  • the method further includes: receiving, by using a channel server as a relay server, a request of each client in the current channel; and Or, the channel server is used as a relay server to send information to each client in the current channel in a broadcast form or a unicast form.
  • a teaming method for use in a first client, including: Sending a team initiation request to the team server, where the team initiation request carries the identifier of the first client; Receiving the team state information sent by the team server, where the team state information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the teamed client, and the enqueue requirement.
  • the correspondence relationship includes a correspondence between the first card position and the identifier of the first client; Receiving the team state information that is sent by the group server again, where the correspondence relationship in the team state information includes a correspondence between the second card bit and the identifier of the second client; After all the cards in the card have an ID of the queued client, they enter the same subchannel as the other queued clients.
  • a teaming method for use in a second client, including: Receiving the team status information sent by the team server, where the team status information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the enqueue client, and the enqueue request.
  • the corresponding relationship includes a correspondence between the first card position and the identifier of the first client; Sending a team join request to the team server, where the team join request includes an identifier of the second client and a card slot to be joined by the second client; Receiving the team state information that is sent by the team server again, where the correspondence relationship in the team state information includes a correspondence between the second card bit and the identifier of the second client; After all the cards have the identity of the enqueue client, the enqueue clients corresponding to the respective card slots are moved into the same subchannel to complete the team.
  • a team server comprising: a first receiving module, configured to receive a group initiation request sent by a first client in a current channel, where the group initiation request carries an identifier of the first client; a status broadcast module, configured to send the group status information to all clients in the current channel, where the group status information includes the total number of card slots, the content type of the card slots, and the identifier of each card slot and the enqueue client.
  • the correspondence relationship includes the first card position and the identifier of the first client received by the first receiving module.
  • Correspondence relationship a second receiving module, configured to receive a team joining request sent by a second client in the current channel, where the team joining request includes an identifier of the second client and a second client to join Card position
  • the status broadcast module is further configured to send the group status information to all the clients in the current channel, where the corresponding relationship in the group status information includes a second card bit and the second receiving module.
  • a channel move-in module configured to: after all the card receivers of the first receiving module or the second receiving module receive the identifiers of the networked clients that are corresponding to each card slot, the networked client corresponding to each card slot The end moves into the same subchannel to complete the team.
  • a first client comprising: a first sending module, configured to send a group initiation request to the team server, where the team initiation request carries an identifier of the first client; a state receiving module, configured to receive the team state information sent by the team server, where the team state information includes a total number of card slots, a content type of the card slot, and an identifier between each card slot and the ID of the queued client.
  • the status receiving module is further configured to receive the group status information that is sent by the group server again, where the correspondence between the group status information includes a second card position and an identifier of the second client Correspondence relationship;
  • the channel entry module is configured to enter the same subchannel with other queued clients after the identifier of the queued client exists in all the card slots.
  • a second client comprising: The status receiving module is configured to receive the group status information sent by the team server, where the team status information includes a total number of card slots, a content type of the card bit, and a correspondence between each card bit and an identifier of the teamed client.
  • the correspondence relationship includes a correspondence between the first card position and the identifier of the first client; a second sending module, configured to send a team joining request to the team server, where the team joining request includes an identifier of the second client and a card slot to be joined by the second client;
  • the status receiving module is further configured to receive the group status information that is sent by the group server again, where the correspondence between the second card position and the identifier of the second client is included in the correspondence relationship in the group status information. relationship;
  • the channel entry module is configured to move the grouped clients corresponding to the respective card slots into the same subchannel to complete the teaming after the identifiers of the queued clients are corresponding to all the card slots.
  • a team system comprising a team server, a first client, and a second client;
  • the team server is the team server as described in the fourth aspect or the various further aspects of the fourth aspect;
  • the first client is as described in various further aspects of the fifth aspect or the fifth aspect First client;
  • the second client is the second client as described in the sixth aspect or the various further aspects of the sixth aspect.
  • a team system comprising a team server, a first client, a second client, and a channel server;
  • the team server is a team server as described in the last further aspect of the fourth aspect;
  • the first client is any of the various aspects of the fifth aspect or the fifth aspect First client;
  • the second client is the second client as described in the sixth aspect or the various further aspects of the sixth aspect.
  • the beneficial effects brought by the technical solutions provided by the embodiments of the present invention are: Receiving a request by a team of the first client, then sending the team state information to all the clients in the current channel, and then receiving the team joining request sent by the second client in the current channel according to the team state information; When other clients do not know the channel number, they cannot successfully team up; as soon as the first client initiates team formation in the current channel, the second client can freely join the team to complete the team process. .
  • FIG. 1 is a flowchart of a method for forming a teaming method according to Embodiment 1 of the present invention
  • 2 is a schematic structural diagram of an implementation environment according to Embodiment 2 of the present invention
  • 3 is a flowchart of a method for forming a teaming method according to Embodiment 2 of the present invention
  • 4A to 4D are schematic diagrams showing implementation of a teaming method according to Embodiment 2 of the present invention
  • 5 is a structural block diagram of a teaming system according to Embodiment 3 of the present invention
  • 6 is a structural block diagram of a teaming system according to Embodiment 4 of the present invention
  • FIG. 7 is a structural block diagram of a channel shifting module according to Embodiment 4 of the present invention.
  • FIG. 4 is a flowchart showing a method of the teaming method provided by Embodiment 1 of the present invention. This embodiment is mainly illustrated by the team method applied to the team system including the first client, the at least one second client, and the team server.
  • the team approach includes:
  • Step 102 The first client in the current channel sends a group initiation request to the team server, where the group initiation request carries the identifier of the first client;
  • Team voice tools typically divide all users into channels or sub-channels by category or demand, for example, '90 Songs' channel, 'xx concert' channel, 'xx
  • the game explains the 'channel or 'national exchange' channel and so on.
  • a channel is the same communication area where users with the same communication theme are located, and may also be called other names such as rooms and chat rooms. For example, a scenario in which a channel includes multiple clients is used.
  • the first client in the current channel may send a group initiation request to the team server, where the group initiation request carries the identifier of the first client. .
  • the identity of the first client is used to uniquely identify the identity of the first client in the team voice tool.
  • the team server receives the team initiation request sent by the first client in the current channel, and the team initiation request carries the identity of the first client.
  • Step 104 The team server sends the team state information to all the clients in the current channel, and the team state information includes the total number of card slots, the content type of the card slot, and the correspondence between each card slot and the identity of the queued client. And all four items or the first three items in the enqueue request, the correspondence relationship includes a correspondence between the first card position and the identifier of the first client; After receiving the team initiation request sent by the first client in the current channel, the team server sends the team state information to all clients in the current channel.
  • the team status information may include the total number of card slots, the content type of the card slots, the correspondence between each card slot and the identity of the queued client, and all four items or the first three items in the enqueue request.
  • a card indicates the position of a player in a team, such as a team 5 card slots, which means a total of 5
  • the content type of the card position refers to the information to be displayed on the card position, usually including the identification and introduction information of the queued client; the correspondence between each card position and the identity of the queued client means After a client joins a card slot, the correspondence between the client's identity and the card slot, for example, the client A joined the second card, then client A's logo '0981' and the second
  • the correspondence between the card positions; the enqueue requirement is an optional condition, and generally includes at least one of whether the current channel contribution value reaches a predetermined threshold, whether the current credit reaches a predetermined threshold, and whether the current channel authority reaches a predetermined authority requirement.
  • the first client Since the first client initiates the team initiation request, the first client joins the first card as the team leader by default.
  • the correspondence between the first card position and the identifier of the first client is included in the correspondence between the team status information sent by the team server.
  • all clients in the current channel receive the group status information sent by the team server.
  • the first client and the at least one second client in the current channel receive the team sending by the team server. status information.
  • Step 106 The second client in the current channel sends a team join request to the team server, where the team join request includes the identifier of the second client and the card slot to be joined by the second client; After receiving the team status information sent by the team server, the second client can know the current team status.
  • the second client sends a team join request to the team server, where the team join request includes the identifier of the second client and the card slot to be joined by the second client, for example, the team server
  • the team status information sent to the second client includes: the total number of card slots' 5', the content type of the card 'identification of the queued client' Corresponding relationship 'the first card position corresponds to the identifier of the first client, and the identifier of the enqueue client corresponding to the other four card slots is empty'; then the second client may send a team join request to the team server,
  • the team join request includes the identity of the second client and the card slot to be joined by the second client as the 'second card slot'.
  • the team server can receive the team joining request sent by the second client, and after receiving the team joining request, the identifier of the second client is corresponding to the second card bit, and then added to the corresponding relationship.
  • Step 108 The team server sends the team state information to all the clients in the current channel, and the corresponding relationship in the team state information includes the correspondence between the second card and the identifier of the second client. In order to let other clients know that the second client has joined the second card, the team server sends the team state information again to all the clients in the current channel, and the corresponding relationship in the team state information includes the second card.
  • the correspondence between the bit and the identity of the second client. All clients in the current channel include a first client and a second client.
  • the second client may have more than one. For example, when the total number of card slots is 5, there may be 4 The second client joins the team and becomes a member of the team. That is, steps 106 and 108 may occur multiple times.
  • Step 110 After all the card slots have an identifier of the queued client, the team server moves the teamed client corresponding to each card slot into the same subchannel to complete the team.
  • the team server moves the enqueued client corresponding to each card to the same subchannel to complete the team. For example, the total number of card slots is 5, if 5 If there is a client joining in each card slot, the team server can move the 5 clients into the same subchannel to complete the team.
  • the user and the other queued clients enter the same subchannel.
  • the teaming method receives a team initiation request by receiving a first client, and then sends the team state information to all clients in the current channel, and then receives the second client in the current channel.
  • the team join request is sent according to the team status information; the problem that the other clients cannot successfully team up when the channel number is not known is solved; as long as the first client initiates the team in the current channel, the second client is reached. You can freely join the team to complete the team process.
  • the implementation environment includes at least 1 client 202, channel server 204, and teaming server 206.
  • Each client 202 is connected to the channel server 204 via a wireless or wired network; the channel server 204 It is connected to the team server 206 via a wireless or wired network.
  • the channel server 204 has transparent transmission capabilities and broadcast and unicast capabilities. Individual clients 202 and team servers 206 No direct communication is performed. Specifically: when each client 202 sends request information to the team server 206, the channel server 204 As the relay server, the request information is sent to the team server 206 through the transparent transmission channel. After the team server 206 receives the request information, it performs corresponding processing. When needed to all or part of the client 202 When the message is sent, the team server 206 first sends the message to the channel server 204. After receiving the information, the channel server 204 transmits to all or part of the client 202 in the form of broadcast or unicast. .
  • FIG. 3 is a flowchart of a method for forming a teaming method according to Embodiment 2 of the present invention. This embodiment is mainly applied to the team method in FIG. 2 An example is given in the implementation environment shown.
  • the team approach includes:
  • Step 302 The first client sends a group initiation request to the team server, where the group initiation request carries the identifier of the first client.
  • the first client in the current channel may send a group initiation request to the team server, where the group initiation request carries the identifier of the first client.
  • the identity of the first client is used to uniquely identify the identity of the first client in the team voice tool.
  • the wheat-sequence mode refers to dividing a plurality of wheat-order time segments in the current channel, and each wheat-order time period can only have 1
  • the client occupies the microphone, that is, the mode that the other client can only listen to or send text messages.
  • the first client can click the 'grab wheat' button displayed on the current interface. Or the 'Start Teaming' button 42 on the first card slot sends a team initiation request to the teaming server.
  • the team server receives the team initiation request sent by the first client in the current channel, and the team initiation request carries the identity of the first client.
  • Step 304 The team server sends the team state information to all the clients in the current channel, and the team state information includes the total number of card slots, the content type of the card slot, and the correspondence between each card slot and the identity of the queued client. And all four items or the first three items in the enqueue request, the correspondence relationship between the first card position and the identifier of the first client is included in the correspondence relationship; After receiving the team initiation request sent by the first client in the current channel, the team server sends the team state information to all clients in the current channel.
  • the team status information may include the total number of card slots, the content type of the card slots, the correspondence between each card slot and the identity of the queued client, and all four items or the first three items in the enqueue request.
  • a card indicates the position of a player in a team, such as a team 5 card slots, which means a total of 5 Players;
  • the content type of the card position refers to the information that needs to be displayed on the card slot, usually including the logo, avatar, level and introduction information of the queued client;
  • the correspondence between each card slot and the identity of the queued client Relationship refers to the correspondence between the identity of the client and the card when a client joins a card. For example, the client 'Zhang San' joined the first client as the first client.
  • the enqueue requirement is an optional condition, and generally includes at least one of whether the current channel contribution value reaches a predetermined threshold, whether the current credit reaches a predetermined threshold, and whether the current channel authority reaches a predetermined authority requirement.
  • the first client Since the first client initiates the team initiation request, the first client joins the first card as the team leader by default.
  • the correspondence between the first card position and the identifier of the first client is included in the correspondence between the team status information sent by the team server.
  • all clients in the current channel receive the group status information sent by the team server.
  • the first client and the at least one second client in the current channel receive the team sending by the team server. status information.
  • each client in the current channel can learn the current latest team state based on the received team state information.
  • Each client can display the card position and the content of each card position on its own interface according to the team status information.
  • Combination diagram 4B It can be seen that the team status information is: the total number of card positions '5', the content type of the card position 'avatar + nickname corresponding to the tag +
  • the corresponding relationship between each card slot and the identity of the queued client is introduced.
  • the correspondence relationship includes the correspondence between the first card slot and the identifier of the first client, and the first client receives the team state.
  • you can display it on the current interface.
  • 5 card slots 43 each of which has an avatar 44, a nickname 45 corresponding to the client's logo, and an introduction 46.
  • the first card shows the 'avatar of the first client'.
  • the nickname + introduction corresponding to the logo.
  • the team setting information such as the total number of card slots, the content type of the card slot, and the enqueue request may be constant or may be changed as needed by setting. If the team setting information is variable, before the step, the team server can read the group setting information preset by the client where the administrator of the current channel is located, and the team setting information includes the total number of card slots and the content of the card slot. All three items or the first two items in the type and enqueue requirements. For example, the client of the current channel administrator can modify the team setting information during the last team formation process, and then the modified team setting information takes effect during the team formation process.
  • Step 306 After the second client enters the current channel, send a group status read request to the team server. It is assumed that the second client does not initially enter the current client after the first client sends the team state information, and the second client sends the team to the team server after entering the current channel. The status reads the request to get the current latest team status information. If the second client is initially in the current channel, then at the step The corresponding team status information has been obtained in 304. Correspondingly, the team server can receive the team state read request sent by the second client newly joining the current channel. The team status read request typically carries the identity of the second client.
  • Step 308 The team server sends the team state information to the second client, where the team state information is the current latest team state information.
  • the team server After receiving the group state read request sent by the second client, the team server sends the team state information to the second client, where the team state information is the current latest team state information.
  • the team server sends the team state information to the second client according to the identifier of the second client by using the channel server in a unicast manner.
  • the second client can receive the team status information sent by the team server.
  • the second client can also display the card position and the content of each card position according to the team status information.
  • the displayed interface can be referred to FIG. 4B.
  • Step 310 The second client sends a team join request to the team server, where the team join request includes the identifier of the second client and the card slot to be joined by the second client; When it is desired to join the team, the second client sends a team join request to the team server.
  • the team join request includes the identity of the second client and the card slot to be joined by the second client.
  • the second client first detects whether the enqueue requirement in the team state information is met before sending the team joining request, and the enqueue request includes the current channel contribution value. Whether the predetermined threshold is reached, whether the current credit reaches a predetermined threshold, and whether the current channel authority reaches at least one of the predetermined authority requirements. If the detection result is that the enqueue requirement in the team status information is met, a team join request is sent to the team server. If the detection result is that the enqueue request in the team status information is not met, the team join request is not sent to the team server.
  • the team server can receive the team joining request sent by the second client in the current channel, and the team joining request includes the identifier of the second client and the card slot to be joined by the second client.
  • Step 312 The team server sends the group status information to all the clients in the current channel again.
  • the correspondence between the second card position and the identifier of the second client is included in the corresponding relationship in the team status information.
  • the team server sends the team state information again to all the clients in the current channel, and the corresponding relationship in the team state information includes the second card.
  • the correspondence between the bit and the identity of the second client. All clients in the current channel include a first client and a second client.
  • each client in the current channel can learn the current latest team state based on the received team state information.
  • Each client can display the card position and the content of each card position on its own interface according to the team status information. For example, the client 'Li Si' joined the team as the second client. The interface displayed at this time can refer to the figure. 4C is shown.
  • the total number of card positions in the received team status information and the content type of the card position and the total number of card positions and card positions in the last received team status information may be first. The content types are compared. If the comparison result is the same, the correspondence between each card position and the identity of the enqueued client is updated; if the comparison result is not the same, the card position is redrawn and displayed.
  • the second client may have more than one. For example, when the total number of card slots is 5, there may be 4
  • the second client joins the team and becomes a member of the team. That is, step 310 and step 312 may be performed multiple times.
  • Step 314 The second client sends a team exit request to the team server, where the team exit request includes the identifier of the second client and the card slot to be withdrawn by the second client; After the second client joins the team, it may also choose to quit the team before the end of the team because of temporary or wrong team information. At this time, the second client may send a team exit request to the team server, where the team exit request includes the identifier of the second client and the card slot to be withdrawn by the second client.
  • Combination diagram 4C after the cursor of the second client stays at the second card position, the second client can click the 'Leave' button 47 on the second card slot to send a team exit request to the team server.
  • the team server receives the team exit request sent by the second client, and the team exit request includes the identifier of the second client and the card slot to be withdrawn by the second client.
  • Step 316 The team server sends the group state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information; After receiving the group exit request sent by the second client, the team server may delete the correspondence between the second card and the identifier of the second client from the corresponding relationship of the current team state. Then, the team server sends the team state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information; The client can update the team status.
  • the team state information in the client may be different from the team state information in the team server because the team state information may be due to packet loss or the like.
  • the team server may detect whether the identity of the teamed client corresponding to the card slot to be withdrawn by the second client in the current latest team state information is the second The client's logo is the same; If the detection result is that the identifier of the enqueue client corresponding to the card slot to be exited by the second client is the same as the identifier of the second client, the team server deletes the second card position from the correspondence relationship of the current team state. Correspondence with the identity of the second client.
  • the team server sends the team state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information;
  • the client can update the team status; If the detection result is that the identifier of the enqueue client corresponding to the card slot to be exited by the second client is different from the identifier of the second client, the team server sends the group status information to the second client again.
  • the team status information is the current latest team status information; so that the second client can update to the current latest team status.
  • steps 314 to 316 are optional steps.
  • Step 318 The first client sends a kick-out player request to the team server, where the exit team member request includes a correspondence between the second card position and the identifier of the second client; After the second client joins the team, the first client as the captain may choose to kick out the second client before the team ends because he does not like the second client or thinks that the second client adds the wrong team. end. At this time, the first client sends a kick-out player request to the team server, and the exit player request includes a correspondence between the second card and the identifier of the second client.
  • Combination diagram 4D after the first client's cursor stays at the second card position, the first client can click the 'remove team' button in the second card position. And sending a kick-out player request to the team server, the exit team request including a correspondence between the second card location and the identity of the second client.
  • the team server receives the kick-out player request sent by the first client, and the kick-out player request includes a correspondence between the second card position and the identifier of the second client.
  • Step 320 The team server sends the group state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information; After receiving the kick-out player request sent by the first client, the team server may delete the correspondence between the second card location and the identifier of the second client from the correspondence between the current team states. Then, the team server sends the team state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information; The client can update the team status.
  • the team state information in the client may be different from the team state information in the team server because the team state information may be due to packet loss or the like.
  • the team server may detect whether the identifier of the enqueue client corresponding to the second card slot in the kick-out player request is the same as the identifier of the second client; If the detection result is that the identifier of the enqueue client corresponding to the second card position in the kick-out player request is the same as the identifier of the second client, the team server deletes the second card position from the correspondence relationship of the current team state. The correspondence between the identifiers of the second client.
  • the team server sends the team state information to all the clients in the current channel again, and the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information;
  • the client can update the team status.
  • the second client may receive the group status information that is sent again by the team server after receiving the kick-out player request of the first client, and the second relationship is deleted in the corresponding relationship in the group status information.
  • the group status information is sent to the first client again, and the team status information is The current latest team status information; so that the first client can update the team status.
  • steps 318 to 320 are also optional steps.
  • the above steps 314 to 320 In a team formation process, there may be 0 to many times.
  • Step 322 After all the card slots have an identifier of the queued client, the team server moves the teamed client corresponding to each card slot into the same subchannel to complete the team.
  • the team server moves the enqueued client corresponding to each card to the same subchannel to complete the team. For example, the total number of card slots is 5, if 5 Each card has a client join, then the team server can put this 5 Clients are moved into the same subchannel to complete the team.
  • the team server receives the team completion information sent by the client (not specifically shown) of the current channel; After the server receives the team completion information, the team server moves the teamed clients corresponding to the respective card slots into the same subchannel to complete the team formation.
  • the user and the other queued clients enter the same subchannel.
  • the client of the first client or the administrator of the current channel may send a team cancellation request to the team server, and the team server cancels the team after receiving the team cancellation request.
  • the first client sends a team cancellation request to the team server, and the team cancellation request is actively triggered by the user, that is, the first client actively cancels the teaming process, and the first client can click on FIG. 4A.
  • the 'Cancel Team' button in the first card slot in the middle sends a team cancellation request to the team server.
  • the team server cancels the current team, and then sends the team state information to all the clients in the current channel.
  • the team state information includes the total number of card slots, the content type of the card slot, and the identifier of each card slot and the queued client.
  • the correspondence between the correspondence and the four items or the first three items in the enqueue request is empty.
  • the first client and other clients in the current channel receive the team status information sent by the team server again, thereby canceling the current teaming process and waiting for the next teaming process.
  • the first client sends a team cancellation request to the team server, and the team cancellation request is automatically triggered after a predetermined time period after the team initiates the request, that is, the first client sends a team initiation request.
  • the first client After obtaining the wheat sequence time period, when the teaming process is not completed at the end of the wheat time period, the first client automatically cancels the teaming process, and the first client can be in the figure.
  • the current wheat order is left' in 4D is 0s
  • a team cancellation request is automatically sent to the teaming server.
  • the team server cancels the current team, and then sends the team state information to all the clients in the current channel.
  • the team state information includes the total number of card slots, the content type of the card slot, and the identifier of each card slot and the queued client.
  • the correspondence between the correspondence and the four items or the first three items in the enqueue request is empty.
  • the first client and other clients in the current channel receive the team status information sent by the team server again, thereby canceling the current teaming process and waiting for the next teaming process.
  • the client of the current channel administrator can also send a team cancellation request to the team server. For example, if the administrator of the current channel moves the first client out of the wheat order, the client of the current channel administrator will The team server sends a team cancellation request. The team server cancels the current team, and then sends the team state information to all the clients in the current channel.
  • the team state information includes the total number of card slots, the content type of the card slot, and the identifier of each card slot and the queued client.
  • the correspondence between the correspondence and the four items or the first three items in the enqueue request is empty.
  • the first client and other clients in the current channel receive the team status information sent by the team server again, thereby canceling the current teaming process and waiting for the next teaming process.
  • the teaming method receives a team initiation request by receiving a first client, and then sends the team state information to all clients in the current channel, and then receives the second client in the current channel.
  • the team join request is sent according to the team status information; the problem that the other clients cannot successfully team up when the channel number is not known is solved; as long as the first client initiates the team in the current channel, the second client is reached.
  • the first client can be more free to complete the entire teaming process and deal with problems that may arise during the teaming process.
  • the request or information is also transmitted in both directions by using the channel server as a transit server, so that the original system structure of the team voice tool is used as much as possible, and the original system structure is better compatible.
  • the channel server is not a device that must exist. In other embodiments, only the client and the team server may be included, and the client and the team server communicate directly.
  • FIG. 5 is a structural block diagram of a teaming system according to Embodiment 3 of the present invention.
  • the team system includes a first client 520 Second client 540 and team server 560. among them:
  • the first client 520 includes: a first sending module 522, configured to the teaming server 560 Sending a team to initiate a request, the team initiation request carrying an identifier of the first client; a status receiving module 524, configured to receive the team server 560 The sent team status information, where the team status information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the enqueue client, and all four items in the enqueue request. Or the first three items, the correspondence relationship includes a correspondence between the first card position and the identifier of the first client;
  • the status receiving module 524 is further configured to receive the group server 560.
  • the corresponding relationship in the team state information includes a correspondence between the second card and the identifier of the second client; the channel entry module 526 It is used to enter the same subchannel with other enqueue clients after the ID of an enqueue client exists in all the card slots.
  • the second client 540 includes: a status receiving module 542, configured to receive the team server 560 The sent team status information, where the team status information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the enqueue client, and all four items in the enqueue request. Or the first three items, the correspondence relationship includes a correspondence between the first card position and the identifier of the first client; a second sending module 544, configured to send a team joining request to the team server 560, where the team joining request includes an identifier of the second client and a card slot to be joined by the second client;
  • the status receiving module 542 is further configured to receive the team server 560.
  • the corresponding relationship in the team state information includes a correspondence between the second card and the identifier of the second client; the channel entry module 546 After the identifiers of the queued clients exist in all the card slots, the queued clients corresponding to the respective card slots are moved into the same subchannel to complete the team formation.
  • the team server 560 includes: a first receiving module 562, configured to receive the first client 520 in the current channel Sending a team to initiate a request, the team initiation request carrying an identifier of the first client; a status broadcast module 564 And configured to send the group state information to all the clients in the current channel, where the team state information includes a total number of card slots, a content type of the card slots, and an identifier between each card slot and the identity of the queued client.
  • a second receiving module 566 configured to receive a second client 540 in the current channel
  • the sent team join request, the team join request includes an identifier of the second client and a card slot to be joined by the second client
  • the status broadcast module 564 is further configured to send the group state information to all the clients in the current channel, where the correspondence in the team state information includes a second card bit and a second received by the second receiving module.
  • Channel shifting module 568 is configured to have one of the first receiving module 562 or the second receiving module 566 in all the card slots. After the received ID of the enqueue client corresponds to the ID, the enqueued client corresponding to each card slot is moved into the same subchannel to complete the team.
  • the teaming system receives the teaming initiation request by receiving the first client, and then sends the team state information to all clients in the current channel, and then receives the second client in the current channel.
  • the team join request is sent according to the team status information; the problem that the other clients cannot successfully team up when the channel number is not known is solved; as long as the first client initiates the team in the current channel, the second client is reached. You can freely join the team to complete the team process.
  • FIG. 4 is a block diagram showing the structure of the teaming system provided in Embodiment 4 of the present invention.
  • the team system includes a first client 520 and a second client 540. And teaming up the server 560. among them:
  • the first client 520 includes: a first sending module 522, configured to the teaming server 560 Sending a team to initiate a request, the team initiation request carrying an identifier of the first client; a status receiving module 524, configured to receive the team server 560 The sent team status information, where the team status information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the enqueue client, and all four items in the enqueue request. Or the first three items, the correspondence relationship includes a correspondence between the first card position and the identifier of the first client;
  • the status receiving module 524 is further configured to receive the group server 560.
  • the corresponding relationship in the team state information includes a correspondence between the second card and the identifier of the second client; the channel entry module 526 It is used to enter the same subchannel with other enqueue clients after the ID of an enqueue client exists in all the card slots.
  • the first client further includes: a fourth sending module 527; the fourth sending module 527 For sending a kick-out player request to the team server 560, the exit player request includes a correspondence between the second card and the identifier of the second client; the status receiving module 524 For receiving the team server 560 The team status information that is sent again, the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information, or the team state information is current Team status information.
  • the first client 520 further includes: a sixth sending module 529; the sixth sending module 529 For sending a team cancellation request to the team server 560, the team cancellation request is a request that is triggered automatically by the user or automatically after a predetermined period of time after the team initiates the request; the status receiving module 524 And for receiving the team server 560
  • the team status information sent again, the team status information includes the total number of card slots, the content type of the card slots, the correspondence between each card slot and the identity of the enqueue client, and all four entries in the enqueue request. Content or the first three items, the corresponding relationship is empty.
  • the second client 540 includes: a status receiving module 542, configured to receive the team server 560 The sent team status information, where the team status information includes the total number of card slots, the content type of the card slot, the correspondence between each card slot and the identity of the enqueue client, and all four items in the enqueue request. Or the first three items, the correspondence relationship includes a correspondence between the first card position and the identifier of the first client; a second sending module 544, configured to send a team joining request to the team server 560, where the team joining request includes an identifier of the second client and a card slot to be joined by the second client;
  • the status receiving module 542 is further configured to receive the group server 560.
  • the corresponding relationship in the team state information includes a correspondence between the second card and the identifier of the second client; the channel entry module 546 After the identifiers of the queued clients exist in all the card slots, the queued clients corresponding to the respective card slots are moved into the same subchannel to complete the team formation.
  • the second client 540 further includes: a requirement detecting module 543; the request detecting module 543 And configured to detect whether the enqueue requirement in the team status information is met, where the enqueue requirement includes whether the current channel contribution value reaches a predetermined threshold, whether the current credit reaches a predetermined threshold, and whether the current channel authority meets the predetermined permission requirement.
  • a requirement detecting module 543 configured to detect whether the enqueue requirement in the team status information is met, where the enqueue requirement includes whether the current channel contribution value reaches a predetermined threshold, whether the current credit reaches a predetermined threshold, and whether the current channel authority meets the predetermined permission requirement.
  • At least one The second sending module 544 is configured to: if the requirement detecting module 543 The result of the detection is that the enqueue request in the team status information is met, and the step of sending the team join request to the team server is performed.
  • the second client 540 further includes: a third sending module 547; the third sending module 547 And sending a team exit request to the team server 560, where the team exit request includes an identifier of the second client and a card slot to be withdrawn by the second client; the status receiving module 542 For receiving the team server 560 The team status information that is sent again, the correspondence between the second card and the identifier of the second client is deleted in the corresponding relationship in the team state information, or the team state information is current and latest Team status information.
  • the status receiving module 542 is further configured to receive the group server 560. After receiving the kick-out player request of the first client, the group status information sent again, the correspondence between the team status information is deleted between the second card position and the identifier of the second client Correspondence.
  • the second client 540 further includes: a fifth sending module 549; the fifth sending module 549 After entering the current channel, sending a team state read request to the team server.
  • the team server 560 includes: a first receiving module 562, configured to receive the first client 520 in the current channel Sending a team to initiate a request, the team initiation request carrying an identifier of the first client;
  • Status broadcast module 564 configured to send the group state information to all the clients in the current channel, where the team state information includes a total number of card slots, a content type of the card slots, and an identifier between each card slot and the identity of the queued client. Corresponding relationship between the first card and the identifier of the first client received by the first receiving module;
  • a second receiving module 566 configured to receive a second client 540 in the current channel Sending a team join request, the team join request including an identifier of the second client and a card slot to be joined by the second client;
  • the status broadcast module 564 is further configured to send the group state information to all the clients in the current channel, where the correspondence in the team state information includes a second card bit and a second received by the second receiving module. Correspondence between the identifiers of the clients;
  • Channel shifting module 568 is configured to have one of the first receiving module 562 or the second receiving module 566 in all the card slots. After the received ID of the enqueue client corresponds to the ID, the enqueued client corresponding to each card slot is moved into the same subchannel to complete the team.
  • the team server 560 further includes: a setting reading module 563; the setting reading module 563 For reading the group setting information preset by the client where the administrator of the current channel is located, the team setting information includes all three of the card slots, the content type of the card slot, and the enqueue request. Content or the first two items.
  • the team server 560 further includes: a join detection module 567 and a state unicast module 569;
  • the join detection module 567 is configured to detect whether the identifier of the enqueue client corresponding to the card slot to be joined by the second client received by the second receiving module 566 is empty; the status broadcast module 564 Also used if the detection module 567 is added The detection result is that the identifier of the enqueue client corresponding to the card slot to be joined by the second client is empty, and then performing the step of sending the group state information to all the clients in the current channel again; State unicast module 569.
  • the second client 540 is sent to the second client 540.
  • the team status information is sent again, and the team status information is the current latest team status information.
  • the team server 560 further includes: a third receiving module 601; the third receiving module 601 And receiving the team exit request sent by the second client 540, where the team exit request includes an identifier of the second client and a card slot to be withdrawn by the second client; Module 564 And is further configured to send the group state information to all the clients in the current channel, where the second card position and the second receiving module receive the second information are deleted in the correspondence relationship in the team state information.
  • the team server 560 further includes: an exit detection module 602 and a state unicast module 569;
  • the exit detection module 602 is configured to detect whether the identifier of the enqueue client corresponding to the card slot to be withdrawn by the second client received by the third receiving module 601 is the same as the identifier of the second client;
  • the status broadcast module 564 is further configured to: if the exit detection module 602 The detection result is that the identifier of the enqueue client corresponding to the card slot to be exited by the second client is the same as the identifier of the second client, and then performing the resending to all the clients in the current channel.
  • the status unicast module 569 is configured to exit the detection module 602.
  • the detection result is that the identifier of the enqueue client corresponding to the card slot to be exited by the second client is different from the identifier of the second client, and the group status information is sent to the second client again.
  • the team status information is current latest group status information.
  • the team server 560 further includes: a fourth receiving module 603; the fourth receiving module 603 For receiving a kick-out player request sent by the first client, the kick-out player request includes a correspondence between the second card position and an identifier of the second client; the status broadcast module 564 And sending the group status information to all the clients in the current channel, where the second card received by the fourth receiving module is deleted from the corresponding relationship in the group status information.
  • the team server 560 further includes: a kick-out detection module 604 and a state unicast module 569;
  • the kick-out detection module 604 is configured to detect whether the identifier of the enqueue client corresponding to the second card slot in the kick-out player request received by the fourth receiving module 603 is related to the second client The same identifier;
  • the status broadcast module 564 is further configured to: if the kick detection module 603 The detection result is that the identifier of the enqueue client corresponding to the second card position in the kick-out player request is the same as the identifier of the second client, and then executing all the customers in the current channel The step of sending the team status information again;
  • the status unicast module 569 is configured to: if the kick detection module 603 The detection result is that the identifier of the enqueue client corresponding to the second card position in the kick-out player request is different from the identifier of the second client, and then sending the team to the first client again.
  • the team server 560 further includes: a fifth receiving module 605 and a state unicast module 569;
  • the fifth receiving module 605 is configured to receive a group status read request sent by the second client 540 newly joining the current channel.
  • the status unicast module 569 is configured to send to the second client 540.
  • the team status information is sent, and the team status information is current latest group status information.
  • the team server 560 further includes: a sixth receiving module 606; the sixth receiving module 606 For receiving the first client 520 Or the team cancellation request sent by the client of the current channel, the team cancellation request sent by the first client is automatically triggered after a predetermined time period after the user initiates the request or the group initiates the request. request;
  • the status broadcast module 564 For resending the group state information to all the clients in the current channel, where the team state information includes the total number of card slots, the content type of the card slots, and the identifier of each card slot and the queued client. Correspondence relationship and all four items or the first three items in the enqueue request, the corresponding relationship is empty.
  • the channel move-in module 568 further includes: a completion receiving unit 568a and a channel shifting unit 568b, as shown in the figure. 7 is shown.
  • the completion receiving unit 568a For receiving the ID of the queried client in all the card positions, receiving the team completion information sent by the client where the administrator of the current channel is located; the channel moving in unit 568b After the completion receiving unit 568a receives the team completion information, the teamed clients corresponding to the respective card slots are moved into the same subchannel to complete the teaming.
  • the team system may further include a channel server (not specifically shown), the team server 560 Receiving, by the channel server, a request of each client in the current channel as a relay server; and/or, the team server 560
  • the channel server is used as a relay server to send information to each client in the current channel in a broadcast form or a unicast form.
  • the teaming system receives the teaming initiation request by receiving the first client, and then sends the team state information to all clients in the current channel, and then receives the second client in the current channel.
  • the team join request is sent according to the team status information; the problem that the other clients cannot successfully team up when the channel number is not known is solved; as long as the first client initiates the team in the current channel, the second client is reached. You can freely join the team to complete the team process. By providing functions such as team exit, kicking out players, and canceling team formation, the first client can be more free to complete the entire teaming process and deal with problems that may arise during the teaming process.
  • the request or information is also transmitted in both directions by using the channel server as a transit server, so that the original system structure of the team voice tool is used as much as possible, and the original system structure is better compatible.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种组队方法、客户端、服务器及系统，属于互联网通信领域。所述方法包括：接收在当前频道中的第一客户端发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识；向所述当前频道中的所有客户端发送组队状态信息；接收在所述当前频道中的第二客户端发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；向所有客户端再次发送组队状态信息；在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。本发明解决了其它客户端没有获知频道号码时，无法顺利组队的技术问题，本发明达到了只要第一客户端在当前频道发起了组队，第二客户端可以自由加入该组队，从而完成组队过程的效果。

Description

组队方法、客户端、服务器及系统
技术领域
本发明涉及互联网通信领域，特别涉及一种组队方法、客户端、服务器及系统。
背景技术
团队语音工具是一种使用广泛且热门的即时通信程序。常用于多人会议、网上教学、组队协作和多人 K 歌等应用场景。 在使用团队语音工具进行组队协作时，常用的组队方法，包括：当前客户端在团队语音工具中进入或者建立一个空频道，并且将该频道的频道号码传递至需要组队的其它客户端，比如当前客户端的使用者将频道号码通过电话告知、通过短信发送或者通过即时通信文字信息发送给其它客户端的使用者；其它客户端在获知该频道的频道号码后，根据该频道的频道号码在团队语音工具中加入该频道，从而使得所有需要组队的客户端进入了同一频道，然后在该频道内进行语音交流。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：当前客户端必须将频道号码传递至需要组队的其它客户端，其它客户端只有获知频道号码以后才能完成组队过程。若使用当前客户端的用户和使用其它客户端的用户是不认识的两个用户，则通常不能顺利地完成组队操作。
发明内容
为了解决其它客户端没有获知频道号码时，无法顺利组队的问题，本发明实施例提供了一种组队方法、客户端、服务器及系统。
所述技术方案如下： 根据本发明的第一方面，提供了一种组队方法，所述方法包括： 接收在当前频道中的第一客户端发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系； 接收在所述当前频道中的第二客户端发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
进一步地， 所述接收在当前频道中的第一客户端发送的组队发起请求之后，所述向所述当前频道中的所有客户端发送组队状态信息之前，还包括： 读取所述当前频道的管理员所在客户端预先设置的组队设置信息，所述组队设置信息包括所述卡位总数、卡位的内容类型和入队要求中的全部三项内容或者前两项内容。
进一步地，所述接收在所述当前频道中的第二客户端发送的组队加入请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括： 检测所述第二客户端要加入的卡位所对应的已入队客户端的标识是否为空； 若检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识为空，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 若检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识不为空，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
进一步地，所述向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系之后，还包括： 接收所述第二客户端发送的组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位； 向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
进一步地，所述接收所述第二客户端发送的组队退出请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括： 检测所述第二客户端要退出的卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同； 若检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 若检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
进一步地，所述向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系之后，还包括： 接收所述第一客户端发送的踢出队员请求，所述踢出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系； 向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
进一步地，所述接收所述第一客户端发送的踢出队员请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括： 检测所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同； 若检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 若检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第一客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
进一步地，所述接收在所述当前频道中的第二客户端发送的组队加入请求之前，还包括： 接收新加入当前频道的第二客户端发送的组队状态读取请求； 向所述第二客户端发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
进一步地，所述向所述当前频道中的所有客户端发送组队状态信息之后，还包括： 接收所述第一客户端或者所述当前频道的管理员所在客户端发送的组队取消请求，所述第一客户端发送的组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求； 向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
进一步地，所述在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队，包括： 在所有卡位都存在一个已入队客户端的标识与之对应后，接收所述当前频道的管理员所在客户端发送的组队完成信息； 在接收到所述组队完成信息之后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
进一步地，所述方法，还包括： 利用频道服务器作为中转服务器接收所述当前频道中的各个客户端的请求；和 / 或， 利用频道服务器作为中转服务器以广播形式或者单播形式向所述当前频道中的各个客户端发送信息。
根据本发明第二方面，提供了一种组队方法，用于第一客户端中，包括： 向组队服务器发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 接收所述组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系； 接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
根据本发明的第三方面，提供了一种组队方法，用于第二客户端中，包括： 接收组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 向所述组队服务器发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 接收组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
根据本发明的第四方面，一种组队服务器，所述服务器，包括： 第一接收模块，用于接收在当前频道中的第一客户端发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 状态广播模块，用于向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一接收模块接收到的第一客户端的标识之间的对应关系； 第二接收模块，用于接收在所述当前频道中的第二客户端发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 所述状态广播模块，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二接收模块接收到的第二客户端的标识之间的对应关系； 频道移入模块，用于在所有卡位都存在一个所述第一接收模块或者第二接收模块接收到的已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
根据本发明的第五方面，提供了第一客户端，包括： 第一发送模块，用于向组队服务器发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 状态接收模块，用于接收所述组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系； 所述状态接收模块，还用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块，用于在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
根据本发明的第六方面，提供了第二客户端，包括： 状态接收模块，用于接收组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 第二发送模块，用于向所述组队服务器发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 所述状态接收模块，还用于接收组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块，用于在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
根据本发明的第七方面，提供了一种组队系统，所述系统包括组队服务器、第一客户端和第二客户端； 所述组队服务器为如第四方面或者第四方面的各种进一步方案中所述的组队服务器； 所述第一客户端为如第五方面或者第五方面的各种进一步方案中所述的第一客户端； 所述第二客户端为如第六方面或者第六方面的各种进一步方案中所述的第二客户端。
根据本发明的第八方面，提供了一种组队系统，所述系统包括组队服务器、第一客户端、第二客户端和频道服务器； 所述组队服务器为如第四方面的最后一种进一步方案中所述的组队服务器； 所述第一客户端为如第五方面或者第五方面的各种进一步方案中任一所述的第一客户端； 所述第二客户端为如第六方面或者第六方面的各种进一步方案中所述的第二客户端。
本发明实施例提供的技术方案带来的有益效果是： 通过接收第一客户端的组队发起请求，然后向当前频道内的所有客户端发送组队状态信息，然后接收当前频道内的第二客户端根据组队状态信息发送的组队加入请求；解决了其它客户端没有获知频道号码时，无法顺利组队的问题；达到了只要第一客户端在当前频道内发起了组队，第二客户端可以自由加入该组队，从而完成组队过程的效果。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图 1 是本发明实施例一提供的组队方法的方法流程图；
图 2 是本发明实施例二所涉及的实施环境的结构示意图；
图 3 是本发明实施例二提供的组队方法的方法流程图；
图 4A 至图 4D 是本发明实施例二提供的组队方法的实施示意图；
图 5 是本发明实施例三提供的组队系统的结构方框图；
图 6 是本发明实施例四提供的组队系统的结构方框图；
图 7 是本发明实施例四提供的频道移入模块的结构方框图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
实施例一
请参考图 1 ，其示出了本发明实施例一提供的组队方法的方法流程图。本实施例主要以该组队方法应用于包含第一客户端、至少一个第二客户端和组队服务器的组队系统中举例说明。该组队方法，包括：
步骤 102 ，在当前频道中的第一客户端向组队服务器发送组队发起请求，该组队发起请求中携带有第一客户端的标识； 团队语音工具通常将所有用户按照类别或者需求划分在一个个频道或者子频道中，比如，' 90 歌声会'频道、' xx 演唱会'频道、' xx 游戏解说'频道或者'国学交流'频道等等。频道是具有相同交流主题的用户所处的同一交流区域，也有可能称之为房间、聊天室之类的其它名称。以一个频道包括多个客户端的场景为例，在需要组队时，当前频道中的第一客户端可以向组队服务器发送组队发起请求，该组队发起请求中携带有第一客户端的标识。第一客户端的标识用于在团队语音工具中唯一识别第一客户端的身份。 相应地，组队服务器接收在当前频道中的第一客户端发送的组队发起请求，该组队发起请求携带有第一客户端的标识。
步骤 104 ，组队服务器向当前频道中的所有客户端发送组队状态信息，该组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，该对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 组队服务器在接收到当前频道中的第一客户端发送的组队发起请求之后，向当前频道中的所有客户端发送组队状态信息。组队状态信息可以包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容。一个卡位表示一个组队中的一个队员的位置，比如一个组队有 5 个卡位，则表示总共需要 5 个队员；卡位的内容类型是指卡位上需要显示的信息，通常包括已入队客户端的标识和介绍信息等；每个卡位与已入队客户端的标识之间的对应关系是指当一个客户端加入一个卡位后，该客户端的标识和该卡位之间的对应关系，比如，客户端 A 加入了第 2 个卡位，则客户端 A 的标识' 0981 '与第 2 个卡位之间的对应关系；入队要求则是可选条件，通常包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种。
由于第一客户端发起了组队发起请求，所以第一客户端默认作为队长加入了第一卡位。组队服务器本次发送的组队状态信息的对应关系中包含有第一卡位与第一客户端的标识之间的对应关系。 相应地，在当前频道中的所有客户端都会接收组队服务器发送的组队状态信息，比如在当前频道中的第一客户端和至少一个第二客户端都会接收到组队服务器发送的组队状态信息。
步骤 106 ，在当前频道中的第二客户端向组队服务器发送组队加入请求，该组队加入请求中包括第二客户端的标识和第二客户端要加入的卡位； 第二客户端在接收到组队服务器发送的组队状态信息之后，可以获知当前的组队状态。然后在希望加入组队时，第二客户端向组队服务器发送组队加入请求，该组队加入请求中包括第二客户端的标识和第二客户端要加入的卡位，比如，组队服务器向第二客户端发送的组队状态信息包括：卡位总数' 5' 、卡位的内容类型'已入队客户端的标识 ' 、对应关系'第一卡位与第一客户端的标识对应，其它四个卡位所对应的已入队客户端的标识为空'；则第二客户端可以向组队服务器发送组队加入请求，该组队加入请求包括第二客户端的标识和第二客户端要加入的卡位为'第二卡位'。 相应地，组队服务器可以接收到第二客户端发送的组队加入请求，并在接收到组队加入请求之后，将第二客户端的标识与第二卡位对应，然后添加入对应关系中。
步骤 108 ，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中包含有第二卡位与第二客户端的标识之间的对应关系； 为了让其他客户端获知第二客户端加入了第二卡位，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中包含有第二卡位与第二客户端的标识之间的对应关系。在当前频道中的所有客户端包括第一客户端和第二客户端。
需要说明的是，第二客户端可以不止一个，比如卡位总数为 5 时，可以有 4 个第二客户端加入组队，从而成为该组队中的队员。也即步骤 106 和步骤 108 可能会进行多次。
步骤 110 ，在所有卡位都存在一个已入队客户端的标识与之对应后，组队服务器将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
在所有卡位都存在一个已入队客户端的标识与之对应后，组队服务器将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队，比如，卡位总数为 5 时，如果 5 个卡位都存在一个客户端加入，则组队服务器可以将这 5 个客户端移入同一个子频道中来完成组队。
对于第一客户端或者第二客户端来讲，在所有卡位都存在一个已入队客户端的标识与之对应后，自身与其它已入队客户端进入同一个子频道。
综上所述，本实施例提供的组队方法，通过接收第一客户端的组队发起请求，然后向当前频道内的所有客户端发送组队状态信息，然后接收当前频道内的第二客户端根据组队状态信息发送的组队加入请求；解决了其它客户端没有获知频道号码时，无法顺利组队的问题；达到了只要第一客户端在当前频道内发起了组队，第二客户端可以自由加入该组队从而完成组队过程的效果。
需要说明的是，根据执行主体的不同，上述组队方法中的部分步骤可以拆分，而单独实现成为组队服务器、第一客户端和第二客户端单侧执行的组队方法。
请参考图 2 ，其示出了本发明实施例二所涉及的实施环境的结构示意图。该实施环境包括至少 1 个客户端 202 、频道服务器 204 和组队服务器 206 。
各个客户端 202 通过无线或者有线网络与频道服务器 204 相连； 频道服务器 204 通过无线或者有线网络与组队服务器 206 相连。 频道服务器 204 具有透传能力和广播及单播能力。各个客户端 202 与组队服务器 206 不进行直接通信。具体来讲： 各个客户端 202 向组队服务器 206 发送请求信息时，频道服务器 204 作为中转服务器，将请求信息通过透传通道发送给组队服务器 206 。 组队服务器 206 收到请求信息后，进行相应的处理。当需要向全部或者部分客户端 202 下发信息时，组队服务器 206 先将信息发送给频道服务器 204 。 频道服务器 204 接收到信息后，以广播或者单播的形式发送给全部或者部分客户端 202 。
实施例二
请参考图 3 ，其示出了本发明实施例二提供的组队方法的方法流程图。本实施例主要以该组队方法应用于图 2 所示的实施环境中来举例说明。该组队方法，包括：
步骤 302 ，第一客户端向组队服务器发送组队发起请求，组队发起请求携带有第一客户端的标识； 以当前频道包括多个客户端的场景为例，在需要组队时，当前频道中的第一客户端可以向组队服务器发送组队发起请求，该组队发起请求中携带有第一客户端的标识。第一客户端的标识用于在团队语音工具中唯一识别第一客户端的身份。
在团队语音工具中，第一客户端发起组队后，同时成为当前麦序下的上麦人。麦序模式是指在当前频道中划分多个麦序时间段，每个麦序时间段只能有 1 个客户端占用麦克风，也即上麦人，其它客户端只能听或者发文字信息的模式。结合图 4A 可知，第一客户端可以点击当前界面上显示的'抢麦'按钮 41 或者第一卡位上的'开始组队'按钮 42 来向组队服务器发送组队发起请求。
相应地，组队服务器接收在当前频道中的第一客户端发送的组队发起请求，该组队发起请求携带有第一客户端的标识。
步骤 304 ，组队服务器向当前频道中的所有客户端发送组队状态信息，该组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 组队服务器在接收到当前频道中的第一客户端发送的组队发起请求之后，向当前频道中的所有客户端发送组队状态信息。组队状态信息可以包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容。一个卡位表示一个组队中的一个队员的位置，比如一个组队有 5 个卡位，则表示总共需要 5 个队员；卡位的内容类型是指卡位上需要显示的信息，通常包括已入队客户端的标识、头像、等级和介绍信息等；每个卡位与已入队客户端的标识之间的对应关系是指当一个客户端加入一个卡位后，该客户端的标识和该卡位之间的对应关系，比如，客户端'张三'作为第一客户端加入了第 1 个卡位，则客户端'张三'的标识' 0981 '与第 1 个卡位之间的对应关系；入队要求则是可选条件，通常包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种。
由于第一客户端发起了组队发起请求，所以第一客户端默认作为队长加入了第一卡位。组队服务器本次发送的组队状态信息的对应关系中包含有第一卡位与第一客户端的标识之间的对应关系。
相应地，在当前频道中的所有客户端都会接收组队服务器发送的组队状态信息，比如在当前频道中的第一客户端和至少一个第二客户端都会接收到组队服务器发送的组队状态信息。
之后，在当前频道中的各个客户端可以根据接收到的组队状态信息获知当前最新的组队状态。各个客户端可以根据组队状态信息在自身的界面上显示卡位和各个卡位的内容。结合图 4B 可知，假设组队状态信息为：卡位总数' 5 '、卡位的内容类型'头像 + 与标识对应的昵称 + 介绍'、每个卡位与已入队客户端的标识之间的对应关系，该对应关系包括第一卡位与第一客户端的标识之间的对应关系，则第一客户端接收到组队状态信息之后，可以在当前界面上显示 5 个卡位 43 ，每个卡位 43 中显示有头像 44 、与客户端的标识对应的昵称 45 和介绍 46 。同时，第一卡位中显示了第一客户端的'头像 + 与标识对应的昵称 + 介绍'。
对于其它客户端的显示过程，可以参考图 4B 所示。
需要说明的是，卡位总数、卡位的内容类型和入队要求等组队设置信息可以是始终不变的，也可以是通过设置按需要变化的。若组队设置信息是可变的，则本步骤之前，组队服务器可以读取当前频道的管理员所在客户端预先设置的组队设置信息，组队设置信息包括卡位总数、卡位的内容类型和入队要求中的全部三项内容或者前两项内容。比如，当前频道的管理员所在客户端可以在上一次组队过程中修改组队设置信息，然后修改后的组队设置信息在本次组队过程中生效。
步骤 306 ，第二客户端进入当前频道之后，向组队服务器发送组队状态读取请求； 假设第二客户端初始并不在当前频道中，在第一客户端发送组队状态信息之后，才进入了当前客户端，则该第二客户端在进入当前频道之后，向组队服务器发送组队状态读取请求，以便获取当前最新的组队状态信息。如果第二客户端初始已经在当前频道中，则在步骤 304 中已经获取了相应的组队状态信息。 对应地，组队服务器可以接收新加入当前频道的第二客户端发送的组队状态读取请求。该组队状态读取请求通常携带有第二客户端的标识。
步骤 308 ，组队服务器向第二客户端发送组队状态信息，该组队状态信息为当前最新的组队状态信息； 组队服务器在接收到第二客户端发送的组队状态读取请求之后，向第二客户端发送组队状态信息，该组队状态信息为当前最新的组队状态信息。比如，组队服务器通过频道服务器采用单播的形式根据第二客户端的标识向第二客户端发送组队状态信息。 对应地，第二客户端可以接收组队服务器发送的组队状态信息。第二客户端也可以根据组队状态信息显示卡位和各个卡位的内容，显示后的界面可以参考图 4B 所示。
步骤 310 ，第二客户端向组队服务器发送组队加入请求，该组队加入请求包括第二客户端的标识和第二客户端要加入的卡位； 在希望加入该组队时，第二客户端向组队服务器发送组队加入请求。该组队加入请求包括第二客户端的标识和第二客户端要加入的卡位。结合图 4B 所示，第二客户端的光标停留在第二卡位后，第二客户端可以点击自身界面上要加入卡位上的' + '号按钮 46 ，从而向组队服务器发出组队加入请求。
优选地，如果组队状态信息中包含有入队要求，则第二客户端在发送组队加入要求之前，先检测是否满足组队状态信息中的入队要求，入队要求包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种。 若检测结果为满足组队状态信息中的入队要求，则向组队服务器发送组队加入请求。 若检测结果为不满足组队状态信息中的入队要求，则不向组队服务器发送组队加入请求。 对应地，组队服务器可以接收在当前频道中的第二客户端发送的组队加入请求，组队加入请求包括第二客户端的标识和第二客户端要加入的卡位。
步骤 312 ，组队服务器向当前频道中的所有客户端再次发送组队状态信息，组队状态信息中的对应关系中包含有第二卡位与第二客户端的标识之间的对应关系； 为了让其他客户端获知第二客户端加入了第二卡位，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中包含有第二卡位与第二客户端的标识之间的对应关系。在当前频道中的所有客户端包括第一客户端和第二客户端。
之后，在当前频道中的各个客户端可以根据接收到的组队状态信息获知当前最新的组队状态。各个客户端可以根据组队状态信息在自身的界面上显示卡位和各个卡位的内容。比如，客户端'李四'作为第二客户端加入了组队，此时显示的界面可以参考图 4C 所示。在各个客户端在第 2 到 n 次接收到组队状态信息时，可以先将本次接收到的组队状态信息中的卡位总数和卡位的内容类型与上次接收到的组队状态信息中的卡位总数和卡位的内容类型进行比较，若比较结果相同，则更新每个卡位与已入队客户端的标识之间的对应关系；若比较结果不相同，则重新绘制和显示卡位。
需要说明的是，第二客户端可以不止一个，比如卡位总数为 5 时，可以有 4 个第二客户端加入组队，从而成为该组队中的队员。也即步骤 310 和步骤 312 可能会进行多次。
步骤 314 ，第二客户端向组队服务器发送组队退出请求，组队退出请求包括第二客户端的标识和第二客户端要退出的卡位； 由于第二客户端加入组队后，还可能因为临时有事或者看错组队信息等原因，在组队结束前选择退出该组队。此时，第二客户端可以向组队服务器发送组队退出请求，组队退出请求包括第二客户端的标识和第二客户端要退出的卡位。结合图 4C 可知，第二客户端的光标停留在第二卡位后，第二客户端可以点击第二卡位上的'离开'按钮 47 ，从而向组队服务器发送组队退出请求。
对应地，组队服务器接收第二客户端发送的组队退出请求，组队退出请求包括第二客户端的标识和第二客户端要退出的卡位。
步骤 316 ，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系； 组队服务器在接收到第二客户端发送的组队退出请求后，可以从当前组队状态的对应关系中删除第二卡位与第二客户端的标识之间的对应关系。然后，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系；以便各个客户端可以更新组队状态。
由于组队状态信息可能因为丢包等原因，导致客户端中的组队状态信息与组队服务器中的组队状态信息不相同。组队服务器在接收到第二客户端发送的组队退出请求之后，可以检测当前最新的组队状态信息中第二客户端要退出的卡位所对应的已入队客户端的标识是否与第二客户端的标识相同； 若检测结果为第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则组队服务器从当前组队状态的对应关系中删除第二卡位与第二客户端的标识之间的对应关系。然后，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系；以便各个客户端可以更新组队状态； 若检测结果为第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则组队服务器向第二客户端再次发送组队状态信息，该组队状态信息为当前最新的组队状态信息；以便第二客户端可以更新至当前最新的组队状态。
需要说明的是，步骤 314 至 316 是可选步骤。
步骤 318 ，第一客户端向组队服务器发送踢出队员请求，该退出队员请求包括第二卡位与第二客户端的标识之间的对应关系； 由于第二客户端加入组队后，作为队长的第一客户端还可能因为不喜欢第二客户端或者认为第二客户端加错组队等原因，在组队结束前选择踢出第二客户端。此时，第一客户端向组队服务器发送踢出队员请求，该退出队员请求包括第二卡位与第二客户端的标识之间的对应关系。结合图 4D 可知，第一客户端的光标停留在第二卡位后，第一客户端可以点击第二卡位中的'移出队伍'按钮 48 ，从而向组队服务器发送踢出队员请求，该退出队员请求包括第二卡位与第二客户端的标识之间的对应关系。
对应地，组队服务器接收第一客户端发送的踢出队员请求，该踢出队员请求包括第二卡位与第二客户端的标识之间的对应关系。
步骤 320 ，组队服务器向当前频道中的所有客户端再次发送组队状态信息，组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系； 组队服务器在接收到第一客户端发送的踢出队员请求后，可以从当前组队状态的对应关系中删除第二卡位与第二客户端的标识之间的对应关系。然后，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系；以便各个客户端可以更新组队状态。
由于组队状态信息可能因为丢包等原因，导致客户端中的组队状态信息与组队服务器中的组队状态信息不相同。组队服务器在接收到第一客户端发送的踢出队员请求之后，可以检测踢出队员请求中的第二卡位所对应的已入队客户端的标识是否与第二客户端的标识相同； 若检测结果为踢出队员请求中的第二卡位所对应的已入队客户端的标识与第二客户端的标识相同，则组队服务器从当前组队状态的对应关系中删除第二卡位与第二客户端的标识之间的对应关系。然后，组队服务器向当前频道中的所有客户端再次发送组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系；以便各个客户端可以更新组队状态。特别地，此时第二客户端可以接收到组队服务器在接收到第一客户端的踢出队员请求之后，再次发送的组队状态信息，该组队状态信息中的对应关系中删除了第二卡位与第二客户端的标识之间的对应关系。
若检测结果为踢出队员请求中的第二卡位所对应的已入队客户端的标识与第二客户端的标识不相同，则向第一客户端再次发送组队状态信息，该组队状态信息为当前最新的组队状态信息；以便第一客户端可以更新组队状态。
需要说明的是，步骤 318 至 320 也是可选步骤。上述步骤 314 至步骤 320 ，在一次组队过程，可能出现 0 到多次。
步骤 322 ，在所有卡位都存在一个已入队客户端的标识与之对应后，组队服务器将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
在所有卡位都存在一个已入队客户端的标识与之对应后，组队服务器将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队，比如，卡位总数为 5 时，如果 5 个卡位都存在一个客户端加入，则组队服务器可以将这 5 个客户端移入同一个子频道中来完成组队。具体来讲，在所有卡位都存在一个已入队客户端的标识与之对应后，组队服务器接收当前频道的管理员所在客户端（未具体示出）发送的组队完成信息；在组队服务器接收到组队完成信息之后，组队服务器将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
对于第一客户端或者第二客户端来讲，在所有卡位都存在一个已入队客户端的标识与之对应后，自身与其它已入队客户端进入同一个子频道。
需要补充说明的是，组队过程也可能在未完成之前被取消。也即步骤 322 之前，第一客户端或者当前频道的管理员所在客户端可能会向组队服务器发送组队取消请求，组队服务器在接收到组队取消请求后，取消组队。具体来讲，分为如下三种情形： 第一，第一客户端向组队服务器发送组队取消请求，该组队取消请求为用户主动触发的，也即第一客户端主动取消组队过程，第一客户端可以点击图 4A 中第一卡位中的'取消组队'按钮来向组队服务器发送组队取消请求。组队服务器取消当前组队，然后向当前频道中的所有客户端发送组队状态信息，该组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，对应关系为空。第一客户端和当前频道中的其它客户端都接收组队服务器再次发送的组队状态信息，从而取消了当前组队过程，等待下次组队过程。
第二，第一客户端向组队服务器发送组队取消请求，该组队取消请求为组队发起请求之后的预定时间段后自动触发的请求，也即第一客户端在发出组队发起请求后，获得了麦序时间段，在该麦序时间段结束时，组队过程还未完成，则第一客户端会自动取消组队过程，第一客户端可以在图 4D 中'当前麦序还剩'为 0s 时，自动向组队服务器发送组队取消请求。组队服务器取消当前组队，然后向当前频道中的所有客户端发送组队状态信息，该组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，对应关系为空。第一客户端和当前频道中的其它客户端都接收组队服务器再次发送的组队状态信息，从而取消了当前组队过程，等待下次组队过程。
第三，当前频道的管理员所在客户端也可以向组队服务器发送组队取消请求，比如当前频道的管理员将第一客户端移出了麦序，则当前频道的管理员所在客户端会向组队服务器发送组队取消请求。组队服务器取消当前组队，然后向当前频道中的所有客户端发送组队状态信息，该组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，对应关系为空。第一客户端和当前频道中的其它客户端都接收组队服务器再次发送的组队状态信息，从而取消了当前组队过程，等待下次组队过程。
综上所述，本实施例提供的组队方法，通过接收第一客户端的组队发起请求，然后向当前频道内的所有客户端发送组队状态信息，然后接收当前频道内的第二客户端根据组队状态信息发送的组队加入请求；解决了其它客户端没有获知频道号码时，无法顺利组队的问题；达到了只要第一客户端在当前频道内发起了组队，第二客户端可以自由加入该组队从而完成组队过程的效果。还通过提供组队退出、踢出队员和取消组队等功能，可以使第一客户端更加自由地完成整个组队过程，并处理组队过程中可能出现的问题。还通过利用频道服务器作为中转服务器来双向传递请求或者信息，使得尽可能沿用团队语音工具的原有系统结构，与原有系统结构更好地兼容。但是本领域技术人员易于思及的是，频道服务器并非必须存在的设备，在其它一些实施例中，可以只包含客户端和组队服务器，此时客户端和组队服务器之间直接通信。
需要说明的是，根据执行主体的不同，上述组队方法中的部分步骤可以拆分，而单独实现成为组队服务器、第一客户端和第二客户端单侧执行的组队方法。
实施例三
请参考图 5 ，其示出了本发明实施例三提供的组队系统的结构方框图。该组队系统包括第一客户端 520 、第二客户端 540 和组队服务器 560 。其中：
第一客户端 520 ，包括： 第一发送模块 522 ，用于向组队服务器 560 发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 状态接收模块 524 ，用于接收所述组队服务器 560 发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系； 所述状态接收模块 524 ，还用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块 526 ，用于在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
第二客户端 540 ，包括： 状态接收模块 542 ，用于接收组队服务器 560 发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 第二发送模块 544 ，用于向所述组队服务器 560 发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 所述状态接收模块 542 ，还用于接收组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块 546 ，用于在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
组队服务器 560 ，包括： 第一接收模块 562 ，用于接收在当前频道中的第一客户端 520 发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 状态广播模块 564 ，用于向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一接收模块接收到的第一客户端的标识之间的对应关系； 第二接收模块 566 ，用于接收在所述当前频道中的第二客户端 540 发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 所述状态广播模块 564 ，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二接收模块接收到的第二客户端的标识之间的对应关系； 频道移入模块 568 ，用于在所有卡位都存在一个所述第一接收模块 562 或者第二接收模块 566 接收到的已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
综上所述，本实施例提供的组队系统，通过接收第一客户端的组队发起请求，然后向当前频道内的所有客户端发送组队状态信息，然后接收当前频道内的第二客户端根据组队状态信息发送的组队加入请求；解决了其它客户端没有获知频道号码时，无法顺利组队的问题；达到了只要第一客户端在当前频道内发起了组队，第二客户端可以自由加入该组队从而完成组队过程的效果。
实施例四
请参考图 6 ，其示出了本发明实施例四提供的组队系统的结构方框图。作为基于实施例三提供的更为优选的实施例，该组队系统包括第一客户端 520 、第二客户端 540 和组队服务器 560 。其中：
第一客户端 520 ，包括： 第一发送模块 522 ，用于向组队服务器 560 发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识； 状态接收模块 524 ，用于接收所述组队服务器 560 发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系； 所述状态接收模块 524 ，还用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块 526 ，用于在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
优选地，所述第一客户端，还包括：第四发送模块 527 ； 所述第四发送模块 527 ，用于向所述组队服务器 560 发送踢出队员请求，所述退出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系； 所述状态接收模块 524 ，用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者，所述组队状态信息为当前最新的组队状态信息。
优选地，所述第一客户端 520 ，还包括：第六发送模块 529 ； 所述第六发送模块 529 ，用于向组队服务器 560 发送组队取消请求，所述组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求； 所述状态接收模块 524 ，还用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
第二客户端 540 ，包括： 状态接收模块 542 ，用于接收组队服务器 560 发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系； 第二发送模块 544 ，用于向所述组队服务器 560 发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位； 所述状态接收模块 542 ，还用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系； 频道进入模块 546 ，用于在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
优选地，所述第二客户端 540 ，还包括：要求检测模块 543 ； 所述要求检测模块 543 ，用于检测是否满足所述组队状态信息中的入队要求，所述入队要求包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种； 所述第二发送模块 544 ，用于若所述要求检测模块 543 的检测结果为满足所述组队状态信息中的入队要求，则执行所述向组队服务器发送组队加入请求的步骤。
优选地，所述第二客户端 540 ，还包括：第三发送模块 547 ； 所述第三发送模块 547 ，用于向组队服务器 560 发送组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位； 所述状态接收模块 542 ，用于接收所述组队服务器 560 再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者所述组队状态信息为当前最新的组队状态信息。 优选地，所述状态接收模块 542 ，还用于接收所述组队服务器 560 在接收到所述第一客户端的踢出队员请求之后，再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
优选地，所述第二客户端 540 ，还包括：第五发送模块 549 ； 所述第五发送模块 549 ，用于进入所述当前频道之后，向所述组队服务器发送组队状态读取请求。
组队服务器 560 ，包括： 第一接收模块 562 ，用于接收在当前频道中的第一客户端 520 发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识；
状态广播模块 564 ，用于向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一接收模块接收到的第一客户端的标识之间的对应关系；
第二接收模块 566 ，用于接收在所述当前频道中的第二客户端 540 发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；
所述状态广播模块 564 ，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二接收模块接收到的第二客户端的标识之间的对应关系；
频道移入模块 568 ，用于在所有卡位都存在一个所述第一接收模块 562 或者第二接收模块 566 接收到的已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
优选地，所述组队服务器 560 ，还包括：设置读取模块 563 ； 所述设置读取模块 563 ，用于读取所述当前频道的管理员所在客户端预先设置的组队设置信息，所述组队设置信息包括所述卡位总数、卡位的内容类型和入队要求中的全部三项内容或者前两项内容。
优选地，所述组队服务器 560 ，还包括：加入检测模块 567 和状态单播模块 569 ； 所述加入检测模块 567 ，用于检测所述第二接收模块 566 接收到的第二客户端要加入的卡位所对应的已入队客户端的标识是否为空； 所述状态广播模块 564 ，还用于若所述加入检测模块 567 的检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识为空，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 所述状态单播模块 569 ，用于若所述加入检测模块 567 的检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识不为空，则向所述第二客户端 540 再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
优选地，所述组队服务器 560 ，还包括：第三接收模块 601 ； 所述第三接收模块 601 ，还用于接收所述第二客户端 540 发送的组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位； 所述状态广播模块 564 ，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第三接收模块接收到的第二客户端的标识之间的对应关系。
优选地，所述组队服务器 560 ，还包括：退出检测模块 602 和状态单播模块 569 ； 所述退出检测模块 602 ，用于检测所述第三接收模块 601 接收到的第二客户端要退出的卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同； 所述状态广播模块 564 ，还用于若所述退出检测模块 602 的检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 所述状态单播模块 569 ，用于若所述退出检测模块 602 的检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
优选地，所述组队服务器 560 ，还包括：第四接收模块 603 ； 所述第四接收模块 603 ，用于接收所述第一客户端发送的踢出队员请求，所述踢出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系； 所述状态广播模块 564 ，用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了所述第四接收模块接收到的第二卡位与所述第二客户端的标识之间的对应关系。
优选地，所述组队服务器 560 ，还包括：踢出检测模块 604 和状态单播模块 569 ； 所述踢出检测模块 604 ，用于检测所述第四接收模块 603 接收到的踢出队员请求中的所述第二卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同； 所述状态广播模块 564 ，还用于若所述踢出检测模块 603 的检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤； 所述状态单播模块 569 ，用于若所述踢出检测模块 603 的检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第一客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
优选地，所述组队服务器 560 ，还包括：第五接收模块 605 和状态单播模块 569 ； 所述第五接收模块 605 ，用于接收新加入当前频道的第二客户端 540 发送的组队状态读取请求； 所述状态单播模块 569 ，用于向所述第二客户端 540 发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
优选地，所述组队服务器 560 ，还包括：第六接收模块 606 ； 所述第六接收模块 606 ，用于接收所述第一客户端 520 或者所述当前频道的管理员所在客户端发送的组队取消请求，所述第一客户端发送的组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求； 所述状态广播模块 564 ，用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
优选地，所述频道移入模块 568 ，还包括：完成接收单元 568a 和频道移入单元 568b ，如图 7 所示。
所述完成接收单元 568a ，用于在所有卡位都存在一个已入队客户端的标识与之对应后，接收所述当前频道的管理员所在客户端发送的组队完成信息； 所述频道移入单元 568b ，用于在所述完成接收单元 568a 接收到所述组队完成信息之后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
优选地，组队系统还可以包括频道服务器（未具体示出），所述组队服务器 560 利用频道服务器作为中转服务器接收所述当前频道中的各个客户端的请求；和 / 或， 所述组队服务器 560 利用频道服务器作为中转服务器以广播形式或者单播形式向所述当前频道中的各个客户端发送信息。
综上所述，本实施例提供的组队系统，通过接收第一客户端的组队发起请求，然后向当前频道内的所有客户端发送组队状态信息，然后接收当前频道内的第二客户端根据组队状态信息发送的组队加入请求；解决了其它客户端没有获知频道号码时，无法顺利组队的问题；达到了只要第一客户端在当前频道内发起了组队，第二客户端可以自由加入该组队从而完成组队过程的效果。还通过提供组队退出、踢出队员和取消组队等功能，可以使第一客户端更加自由地完成整个组队过程，并处理组队过程中可能出现的问题。还通过利用频道服务器作为中转服务器来双向传递请求或者信息，使得尽可能沿用团队语音工具的原有系统结构，与原有系统结构更好地兼容。
需要说明的是：上述实施例提供的组队系统在组队时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的组队系统与组队方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (40)

  1. 一种组队方法，其特征在于，所述方法包括：
    接收在当前频道中的第一客户端发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识；
    向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系；
    接收在所述当前频道中的第二客户端发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；
    向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系；
    在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  2. 根据权利要求 1 所述的组队方法，其特征在于，所述接收在当前频道中的第一客户端发送的组队发起请求之后，所述向所述当前频道中的所有客户端发送组队状态信息之前，还包括：
    读取所述当前频道的管理员所在客户端预先设置的组队设置信息，所述组队设置信息包括所述卡位总数、卡位的内容类型和入队要求中的全部三项内容或者前两项内容。
  3. 根据权利要求 1 所述的组队方法，其特征在于，所述接收在所述当前频道中的第二客户端发送的组队加入请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括：
    检测所述第二客户端要加入的卡位所对应的已入队客户端的标识是否为空；
    若检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识为空，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    若检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识不为空，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  4. 根据权利要求 1 所述的组队方法，其特征在于，所述向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系之后，还包括：
    接收所述第二客户端发送的组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位；
    向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
  5. 根据权利要求 4 所述的组队方法，其特征在于，所述接收所述第二客户端发送的组队退出请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括：
    检测所述第二客户端要退出的卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同；
    若检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    若检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  6. 根据权利要求 1 所述的组队方法，其特征在于，所述向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系之后，还包括：
    接收所述第一客户端发送的踢出队员请求，所述踢出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系；
    向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
  7. 根据权利要求 6 所述的组队方法，其特征在于，所述接收所述第一客户端发送的踢出队员请求之后，所述向所述当前频道中的所有客户端再次发送组队状态信息之前，还包括：
    检测所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同；
    若检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    若检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第一客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  8. 根据权利要求 1 所述的组队方法，其特征在于，所述接收在所述当前频道中的第二客户端发送的组队加入请求之前，还包括：
    接收新加入当前频道的第二客户端发送的组队状态读取请求；
    向所述第二客户端发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  9. 根据权利要求 1 所述的组队方法，其特征在于，所述向所述当前频道中的所有客户端发送组队状态信息之后，还包括：
    接收所述第一客户端或者所述当前频道的管理员所在客户端发送的组队取消请求，所述第一客户端发送的组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求；
    向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
  10. 根据权利要求 1 所述的组队方法，其特征在于，所述在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队，包括：
    在所有卡位都存在一个已入队客户端的标识与之对应后，接收所述当前频道的管理员所在客户端发送的组队完成信息；
    在接收到所述组队完成信息之后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  11. 根据权利要求 1 至 10 任一所述的组队方法，其特征在于，所述方法，还包括：
    利用频道服务器作为中转服务器接收所述当前频道中的各个客户端的请求；和 / 或，
    利用频道服务器作为中转服务器以广播形式或者单播形式向所述当前频道中的各个客户端发送信息。
  12. 一种组队方法，用于第一客户端中，其特征在于，包括：
    向组队服务器发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识；
    接收所述组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系；
    接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系；
    在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
  13. 根据权利要求 12 所述的组队方法，其特征在于，所述在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道之前，还包括：
    向所述组队服务器发送踢出队员请求，所述退出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系；
    接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者，所述组队状态信息为当前最新的组队状态信息。
  14. 根据权利要求 12 所述的组队方法，其特征在于，所述向组队服务器发送组队发起请求之后，还包括：
    向组队服务器发送组队取消请求，所述组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求；
    接收所述组队服务器再次发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
  15. 一种组队方法，用于第二客户端中，其特征在于，包括：
    接收组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系；
    向所述组队服务器发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；
    接收组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系；
    在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  16. 根据权利要求 15 所述的组队方法，其特征在于，所述接收组队服务器发送的组队状态信息之后，所述向组队服务器发送组队加入请求之前，还包括：
    检测是否满足所述组队状态信息中的入队要求，所述入队要求包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种；
    若检测结果为满足所述组队状态信息中的入队要求，则执行所述向组队服务器发送组队加入请求的步骤。
  17. 根据权利要求 15 所述的组队方法，其特征在于，所述向所述组队服务器发送组队加入请求之后，还包括：
    向组队服务器发送组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位；
    接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者所述组队状态信息为当前最新的组队状态信息。
  18. 根据权利要求 15 所述的组队方法，其特征在于，所述接收组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系之后，还包括：
    接收所述组队服务器在接收到所述第一客户端的踢出队员请求之后，再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
  19. 根据权利要求 15 至 18 任一所述的组队方法，其特征在于，所述接收组队服务器发送的组队状态信息之前，还包括：
    进入所述当前频道之后，向所述组队服务器发送组队状态读取请求。
  20. 一种组队服务器，其特征在于，所述服务器，包括：
    第一接收模块，用于接收在当前频道中的第一客户端发送的组队发起请求，所述组队发起请求携带有所述第一客户端的标识；
    状态广播模块，用于向所述当前频道中的所有客户端发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一接收模块接收到的第一客户端的标识之间的对应关系；
    第二接收模块，用于接收在所述当前频道中的第二客户端发送的组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；
    所述状态广播模块，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二接收模块接收到的第二客户端的标识之间的对应关系；
    频道移入模块，用于在所有卡位都存在一个所述第一接收模块或者第二接收模块接收到的已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  21. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：设置读取模块；
    所述设置读取模块，用于读取所述当前频道的管理员所在客户端预先设置的组队设置信息，所述组队设置信息包括所述卡位总数、卡位的内容类型和入队要求中的全部三项内容或者前两项内容。
  22. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：加入检测模块和状态单播模块；
    所述加入检测模块，用于检测所述第二接收模块接收到的第二客户端要加入的卡位所对应的已入队客户端的标识是否为空；
    所述状态广播模块，还用于若所述加入检测模块的检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识为空，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    所述状态单播模块，用于若所述加入检测模块的检测结果为所述第二客户端要加入的卡位所对应的已入队客户端的标识不为空，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  23. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：第三接收模块；
    所述第三接收模块，还用于接收所述第二客户端发送的组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位；
    所述状态广播模块，还用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第三接收模块接收到的第二客户端的标识之间的对应关系。
  24. 根据权利要求 23 所述的组队服务器，其特征在于，所述组队服务器，还包括：退出检测模块和状态单播模块；
    所述退出检测模块，用于检测所述第三接收模块接收到的第二客户端要退出的卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同；
    所述状态广播模块，还用于若所述退出检测模块的检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    所述状态单播模块，用于若所述退出检测模块的检测结果为所述第二客户端要退出的卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第二客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  25. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：第四接收模块；
    所述第四接收模块，用于接收所述第一客户端发送的踢出队员请求，所述踢出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系；
    所述状态广播模块，用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息中的对应关系中删除了所述第四接收模块接收到的第二卡位与所述第二客户端的标识之间的对应关系。
  26. 根据权利要求 25 所述的组队服务器，其特征在于，所述组队服务器，还包括：踢出检测模块和状态单播模块；
    所述踢出检测模块，用于检测所述第四接收模块接收到的踢出队员请求中的所述第二卡位所对应的已入队客户端的标识是否与所述第二客户端的标识相同；
    所述状态广播模块，还用于若所述踢出检测模块的检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识相同，则执行所述向所述当前频道中的所有客户端再次发送组队状态信息的步骤；
    所述状态单播模块，用于若所述踢出检测模块的检测结果为所述踢出队员请求中的所述第二卡位所对应的已入队客户端的标识与所述第二客户端的标识不相同，则向所述第一客户端再次发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  27. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：第五接收模块和状态单播模块；
    所述第五接收模块，用于接收新加入当前频道的第二客户端发送的组队状态读取请求；
    所述状态单播模块，用于向所述第二客户端发送组队状态信息，所述组队状态信息为当前最新的组队状态信息。
  28. 根据权利要求 20 所述的组队服务器，其特征在于，所述组队服务器，还包括：第六接收模块；
    所述第六接收模块，用于接收所述第一客户端或者所述当前频道的管理员所在客户端发送的组队取消请求，所述第一客户端发送的组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求；
    所述状态广播模块，用于向所述当前频道中的所有客户端再次发送组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
  29. 根据权利要求 20 所述的组队服务器，其特征在于，所述频道移入模块，还包括：完成接收单元和频道移入单元；
    所述完成接收单元，用于在所有卡位都存在一个已入队客户端的标识与之对应后，接收所述当前频道的管理员所在客户端发送的组队完成信息；
    所述频道移入单元，用于在所述完成接收单元接收到所述组队完成信息之后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  30. 根据权利要求 20 至 29 任一所述的组队服务器，其特征在于，所述组队服务器利用频道服务器作为中转服务器接收所述当前频道中的各个客户端的请求；和 / 或，
    所述组队服务器利用频道服务器作为中转服务器以广播形式或者单播形式向所述当前频道中的各个客户端发送信息。
  31. 第一客户端，其特征在于，包括：
    第一发送模块，用于向组队服务器发送组队发起请求，所述组队发起请求携带有所述第一客户端的标识；
    状态接收模块，用于接收所述组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与所述第一客户端的标识之间的对应关系；
    所述状态接收模块，还用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系；
    频道进入模块，用于在所有卡位都存在一个已入队客户端的标识与之对应后，与其它已入队客户端进入同一个子频道。
  32. 根据权利要求 31 所述的第一客户端，其特征在于，所述第一客户端，还包括：第四发送模块；
    所述第四发送模块，用于向所述组队服务器发送踢出队员请求，所述退出队员请求包括所述第二卡位与所述第二客户端的标识之间的对应关系；
    所述状态接收模块，还用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者，所述组队状态信息为当前最新的组队状态信息。
  33. 根据权利要求 31 所述的第一客户端，其特征在于，所述第一客户端，还包括：第六发送模块；
    所述第六发送模块，用于向所述组队服务器发送组队取消请求，所述组队取消请求为用户主动触发或者所述组队发起请求之后的预定时间段后自动触发的请求；
    所述状态接收模块，还用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系为空。
  34. 第二客户端，其特征在于，包括：
    状态接收模块，用于接收组队服务器发送的组队状态信息，所述组队状态信息包括卡位总数、卡位的内容类型、每个卡位与已入队客户端的标识之间的对应关系和入队要求中的全部四项内容或者前三项内容，所述对应关系中包含有第一卡位与第一客户端的标识之间的对应关系；
    第二发送模块，用于向所述组队服务器发送组队加入请求，所述组队加入请求包括所述第二客户端的标识和所述第二客户端要加入的卡位；
    所述状态接收模块，还用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中包含有第二卡位与所述第二客户端的标识之间的对应关系；
    频道进入模块，用于在所有卡位都存在一个已入队客户端的标识与之对应后，将与各个卡位分别对应的已入队客户端移入同一子频道中来完成组队。
  35. 根据权利要求 34 所述的第二客户端，其特征在于，所述第二客户端，还包括：要求检测模块；
    所述要求检测模块，用于检测是否满足所述组队状态信息中的入队要求，所述入队要求包括当前频道贡献值是否达到预定阈值、当前积分是否达到预定阈值和当前频道权限是否达到预定权限要求中的至少一种；
    所述第二发送模块，用于若所述要求检测模块的检测结果为满足所述组队状态信息中的入队要求，则执行所述向组队服务器发送组队加入请求的步骤。
  36. 根据权利要求 34 所述的第二客户端，其特征在于，所述第二客户端，还包括：第三发送模块；
    所述第三发送模块，用于向组队服务器发送组队退出请求，所述组队退出请求包括所述第二客户端的标识和所述第二客户端要退出的卡位；
    所述状态接收模块，用于接收所述组队服务器再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系，或者所述组队状态信息为当前最新的组队状态信息。
  37. 根据权利要求 34 所述的第二客户端，其特征在于，所述状态接收模块，还用于接收所述组队服务器在接收到所述第一客户端的踢出队员请求之后，再次发送的组队状态信息，所述组队状态信息中的对应关系中删除了第二卡位与所述第二客户端的标识之间的对应关系。
  38. 根据权利要求 34 至 37 任一所述的第二客户端，其特征在于，所述第二客户端，还包括：第五发送模块；
    所述第五发送模块，用于进入所述当前频道之后，向所述组队服务器发送组队状态读取请求。
  39. 一种组队系统，其特征在于，所述系统包括组队服务器、第一客户端和第二客户端；
    所述组队服务器为如权利要求 20 至 29 任一所述的组队服务器；
    所述第一客户端为如权利要求 31 至 33 任一所述的第一客户端；
    所述第二客户端为如权利要求 34 至 38 任一所述的第二客户端。
  40. 一种组队系统，其特征在于，所述系统包括组队服务器、第一客户端、第二客户端和频道服务器；
    所述组队服务器为如权利要求 30 所述的组队服务器；
    所述第一客户端为如权利要求 31 至 33 任一所述的第一客户端；
    所述第二客户端为如权利要求 34 至 38 任一所述的第二客户端。
PCT/CN2013/088659 2012-12-24 2013-12-05 组队方法、客户端、服务器及系统 WO2014101643A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US14/654,052 US20150341432A1 (en) 2012-12-24 2013-12-05 Grouping method, client, server, and system
KR1020157020078A KR20150102079A (ko) 2012-12-24 2013-12-05 그룹핑 방법, 클라이언트, 서버 및 시스템
SG11201504938TA SG11201504938TA (en) 2012-12-24 2013-12-05 Grouping method, client, server, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210571842.3A CN103905216B (zh) 2012-12-24 2012-12-24 组队方法、客户端、服务器及系统
CN201210571842.3 2012-12-24

Publications (1)

Publication Number Publication Date
WO2014101643A1 true WO2014101643A1 (zh) 2014-07-03

Family

ID=50996372

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/088659 WO2014101643A1 (zh) 2012-12-24 2013-12-05 组队方法、客户端、服务器及系统

Country Status (5)

Country Link
US (1) US20150341432A1 (zh)
KR (1) KR20150102079A (zh)
CN (1) CN103905216B (zh)
SG (1) SG11201504938TA (zh)
WO (1) WO2014101643A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104361125A (zh) * 2014-12-03 2015-02-18 广州华多网络科技有限公司 一种网络活动参与方法及相关设备
CN110121148A (zh) * 2019-04-02 2019-08-13 西安极蜂天下信息科技有限公司 对讲机组队方法及装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107066199B (zh) * 2017-04-13 2020-02-04 网易（杭州）网络有限公司 用于消息发送的交互方法及装置
CN107317825B (zh) * 2017-08-09 2021-03-02 贵阳朗玛信息技术股份有限公司 多人语音会议聊天方法及装置
CN108391156B (zh) * 2018-02-07 2022-03-01 北京密境和风科技有限公司 互动直播方法、客户端、服务器和系统
CN108494833A (zh) * 2018-03-01 2018-09-04 北京峰趣互联网信息服务有限公司 通信方法、介质以及服务器
CN108888959B (zh) * 2018-06-27 2020-06-30 腾讯科技（深圳）有限公司 虚拟场景中的组队方法、装置、计算机设备及存储介质
CN111091253A (zh) * 2018-10-23 2020-05-01 北京嘀嘀无限科技发展有限公司 网约车组队方法、装置、设备及存储介质
CN111405310B (zh) * 2020-03-31 2022-02-08 北京达佳互联信息技术有限公司 直播互动方法、装置、电子设备及存储介质
CN113763101A (zh) * 2021-01-07 2021-12-07 北京沃东天骏信息技术有限公司 一种业务请求处理方法和装置
CN115314729A (zh) * 2022-08-04 2022-11-08 广州方硅信息技术有限公司 组队互动的直播方法、装置、计算机设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968110A (zh) * 2005-11-17 2007-05-23 腾讯科技（深圳）有限公司 快速建立在线企业以及加入在线企业的方法
CN101150536A (zh) * 2007-11-07 2008-03-26 腾讯科技（深圳）有限公司 讨论组创建/分发方法及装置、即时通讯系统
CN101345718A (zh) * 2007-07-13 2009-01-14 阿里巴巴集团控股有限公司 一种在群内支持话题分类的方法、系统和装置
TW201012149A (en) * 2008-09-12 2010-03-16 Inventec Appliances Corp Instant messaging method and instant messaging system
CN102138156A (zh) * 2008-08-28 2011-07-27 微软公司 维持即时消息接发应用程序中的群

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6903190B1 (en) * 2001-05-31 2005-06-07 Divergence, Inc. Nematode ATP synthase subunit E-like sequences
US7359724B2 (en) * 2003-11-20 2008-04-15 Nokia Corporation Method and system for location based group formation
US7664816B2 (en) * 2005-06-10 2010-02-16 Microsoft Corporation Multi-participant online activities
US8145719B2 (en) * 2006-03-03 2012-03-27 Gogroups Method and system for messaging and communication based on groups
KR101932714B1 (ko) * 2010-09-28 2018-12-26 삼성전자주식회사 소셜 그룹 생성 및 연결 방법, 그 방법을 수행할 수 있는 유저 디바이스, 서버 및 저장 매체

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968110A (zh) * 2005-11-17 2007-05-23 腾讯科技（深圳）有限公司 快速建立在线企业以及加入在线企业的方法
CN101345718A (zh) * 2007-07-13 2009-01-14 阿里巴巴集团控股有限公司 一种在群内支持话题分类的方法、系统和装置
CN101150536A (zh) * 2007-11-07 2008-03-26 腾讯科技（深圳）有限公司 讨论组创建/分发方法及装置、即时通讯系统
CN102138156A (zh) * 2008-08-28 2011-07-27 微软公司 维持即时消息接发应用程序中的群
TW201012149A (en) * 2008-09-12 2010-03-16 Inventec Appliances Corp Instant messaging method and instant messaging system

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104361125A (zh) * 2014-12-03 2015-02-18 广州华多网络科技有限公司 一种网络活动参与方法及相关设备
CN110121148A (zh) * 2019-04-02 2019-08-13 西安极蜂天下信息科技有限公司 对讲机组队方法及装置
CN110121148B (zh) * 2019-04-02 2021-07-06 西安极蜂天下信息科技有限公司 对讲机组队方法及装置

Also Published As

Publication number Publication date
US20150341432A1 (en) 2015-11-26
CN103905216B (zh) 2017-02-08
SG11201504938TA (en) 2015-07-30
CN103905216A (zh) 2014-07-02
KR20150102079A (ko) 2015-09-04

Similar Documents

Publication Publication Date Title
WO2014101643A1 (zh) 组队方法、客户端、服务器及系统
JP5883013B2 (ja) 受信確認を提供する対話形メッセージングサービス運用方法
CN101068194B (zh) 一种实现在线游戏邀请的方法及系统
JP4357699B2 (ja) 通信手段の通知方法及び通知システム
JP7050354B2 (ja) 非同期メッセージシステムにおける単一アカウントに対する複数プロファイルを管理する方法、システムおよびコンピュータ読み取り可能媒体
US7917640B2 (en) Communication bandwidth control method for a broadcast communication system, a server and a user terminal used in a broadcast communication system, and a program
WO2010041360A1 (ja) 情報処理装置および情報処理方法
WO2006095508A1 (ja) フラッディング抑制方法
JP2004102547A (ja) コミュニケーションシステム、コミュニケーションサーバ、及び、コミュニケーション方法
JP5043956B2 (ja) 仮想キャラクタを制御する方法、サーバおよびシステム
JP4182955B2 (ja) 同報送信システム、サーバ装置、端末装置、データ配信方法およびプログラム
US9561438B2 (en) Method for realizing multi-party interactive communication and system thereof
JP3938379B2 (ja) 電子音声会議における話者権についての情報処理方法及びプログラム、並びに無線通信携帯端末
WO2009009967A1 (fr) Système, composant et procédé de messagerie instantanée pour des services supplémentaires
CN103078788A (zh) 一种基于应用的信息交互方法及系统
JP4792495B2 (ja) 通信制御装置および方法
JP2015041885A (ja) テレビ会議システム
CN206145900U (zh) 空调控制系统、集中控制节点及空调
CN102172006A (zh) 网络系统、通信装置、通信方法、及通信程序
JP3616129B2 (ja) 通信制御装置及び通信制御方法
JP4508755B2 (ja) Ｓｉｐに従った通信システム及び通信端末
JP2010087704A (ja) 通信方法、サーバ装置及びそのシステム
CN109041038A (zh) 用于控制电子装置与指定用户绑定的方法和系统
WO2001053954A1 (fr) Systeme de forum, terminal, procede de formation d'environnement de forum et support d'enregistrement
CN103338192B (zh) 用于在呼叫者与被呼叫者之间建立呼叫的网络节点和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13866657

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14654052

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20157020078

Country of ref document: KR

Kind code of ref document: A

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22/12/2015)

122 Ep: pct application non-entry in european phase

Ref document number: 13866657

Country of ref document: EP

Kind code of ref document: A1