WO2019127520A1 - Method, system and device for group callback in broadband trunking system - Google Patents

Abstract

Disclosed is a method for group callback in a broadband trunking system. The method comprises: a sending end sending a first group callback request to a trunking core network; the trunking core network selecting a callback receiving end according to the first group callback request; the trunking core network sending a second group callback request to the callback receiving end; and the callback receiving end receiving and storing the second group callback request, and when a pre-set condition is met, calling back a session group where the sending end is located in response to the second group callback request. In this way, according to the present invention, the communication efficiency can be improved, the requirements of related application scenarios can be satisfied, and the user experience can be improved.

Description

Method, system and device for group callback in broadband cluster system

[Technical Field]

The present invention relates to the field of trunking communications, and in particular, to a method, system and apparatus for group callback in a broadband cluster system.

 【Background technique】

Existing Mission-Critical Push To Talk, There are two types of group calls in the MCPTT) standard: preset group calls and chat group calls.

After the caller initiates the group call, the preset group call initiates a call to each called point-to-point, and needs related personnel to participate, and these people are not in the group session (the user is in other calls, and the user actively takes the group from the group) When the group quits, etc., the system will not be able to communicate effectively with these people.

A chat group call can only be actively joined by a user. When the related personnel are required to participate, and the personnel are not in the group session (the user does not actively join the session), the system cannot effectively communicate with these people.

 [Summary of the Invention]

The invention provides a method, a system and a device for group callback in a broadband cluster system, which can improve communication efficiency, meet the requirements of related application scenarios, and improve user experience.

In order to solve the above technical problem, the first aspect of the present invention provides a method for group callback in a broadband cluster system, comprising: sending, by a sender, a first group callback request to a cluster core network; The first group callback request selects a callback receiving end; the cluster core network sends a second group callback request to the callback receiving end; the callback receiving end receives and stores the second group And the callback request is sent back to the session group where the sender is located in response to the second group callback request when the preset condition is met.

In order to solve the above technical problem, the second aspect of the present invention provides a method for group callback in a broadband cluster system, where the method is applied to a cluster core network, and the method includes: receiving a first group sent by a sender a call request; selecting a callback receiving end according to the first group callback request; and sending a second group callback request to the callback receiving end, so that the callback receiving end receives and stores the second callback The group callback request is to respond to the second group callback request to call back the session group in which the sender is located when the preset condition is met.

In order to solve the above technical problem, a third aspect of the present invention provides a group callback method in a broadband cluster system, including: a callback receiving end receives a second group callback request sent by a cluster core network, and stores the a second group callback request to call back the session group in which the sender is located in response to the second group callback request when the preset condition is met; wherein the second group callback request is The cluster core network selects the callback receiving end to send to the callback receiving end according to the first group callback request sent by the sending end.

In order to solve the above technical problem, a fourth aspect of the present invention provides a cluster system, including: a sending end, configured to send a first group callback request to a cluster core network; a cluster core, the network is configured to use the first group according to the first group The group callback request selects the callback receiving end and sends a second group callback request to the callback receiving end; the callback receiving end; and receives and stores the second group callback request to satisfy the pre When the condition is set, the session group in which the sending end is located is returned in response to the second group callback request.

In order to solve the above technical problem, a fifth aspect of the present invention provides a group callback apparatus in a broadband cluster system, including a processor and a memory, the processor is connected to the memory, and the processor is configured to execute an instruction to implement the foregoing. Any of the methods described.

In order to solve the above technical problem, a sixth aspect of the present invention provides a group callback apparatus in a broadband cluster system, in which an instruction is stored, and when the instruction is executed, the method described in any one of the above is implemented.

The invention has the beneficial effects of providing a method, system and device for group callback in a broadband cluster system, by sending a group callback request to a callback receiving end, so that the callback receiving end meets a preset condition Calling back the session group where the sender is located can improve the communication efficiency, meet the requirements of related application scenarios, and improve the user experience.

 [Description of the Drawings]

1 is a schematic structural view of a first embodiment of a broadband cluster system according to the present invention;

2 is a schematic flowchart of a first embodiment of a method for group callback in a broadband cluster system according to the present invention;

3 is a schematic flow chart of an embodiment of step S2 in FIG. 2 of the present invention;

4 is a schematic flowchart of a second embodiment of a method for group callback in a broadband cluster system according to the present invention;

5 is a schematic flowchart of a third embodiment of a method for group callback in a broadband cluster system according to the present invention;

6 is a schematic flow chart of an embodiment of S22 in FIG. 5 of the present invention;

7 is a schematic flowchart of a fourth embodiment of a method for group callback in a broadband cluster system according to the present invention;

8 is a schematic flowchart of a fifth embodiment of a method for group callback in a broadband cluster system according to the present invention;

9 is a schematic flowchart of a sixth embodiment of a method for group callback in a broadband cluster system according to the present invention;

10 is a schematic flowchart diagram of a seventh embodiment of a method for group callback in a broadband cluster system according to the present invention;

11 is a schematic structural diagram of a first embodiment of a group call back device in a broadband cluster system according to the present invention;

12 is a schematic structural diagram of a second embodiment of a group call back device in a broadband cluster system according to the present invention;

13 is a schematic structural diagram of a third embodiment of a group call back device in a broadband cluster system according to the present invention;

FIG. 14 is a schematic structural diagram of a fourth embodiment of a group call back device in a broadband cluster system according to the present invention.

【Detailed ways】

The invention will now be described in detail in conjunction with the drawings and embodiments. The conflicts in the following embodiments may be combined with each other.

Please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a first embodiment of a broadband cluster system according to the present invention. The broadband cluster system includes: a transmitting end 1, a cluster core network 2, and a receiving end 3. Embodiments of the cluster system for performing the method of group callback in the broadband cluster system of the present invention.

The sender 1 and the receiver 3 provide various services for the user. The number of the receivers 3 shown in FIG. 1 is only one, and the number of the actual receivers 3 can be more. The cluster core network 2 can include multiple network elements to meet different service requirements and support cluster services to complete cluster services, including call management, media distribution, and voice control.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a first embodiment of a method for group callback in a broadband cluster system according to the present invention, where the method includes the following steps:

S1. The sending end sends a first group callback request to the cluster core network.

In an application scenario of the present invention, when a session group in which the sender is located needs to specify a group user to join the session group, the group call user can be notified to join the current session group by means of group callback. Specifically, the sending end sends a first group callback request to the cluster core network. The first group callback request includes at least a callback policy, and the callback policy may include, but is not limited to, an identifier of the callback receiving end specified by the sending end, a selection condition of the callback receiving end, and/or an exclusion condition. The sending end and the callback receiving end of the callback call belong to the same static group, and the selection condition and/or the exclusion condition of the callback receiving end means that the sending end has already sent the first group callback request before sending Set and select the receiving object that needs to request the callback, which may be all the terminals in the static group that are not added to the group session, or specify some terminals in the static group that are not joined to the group session, or The partial terminal and the like that are not joined to the group session in the static group are excluded, and the specific selection and/or exclusion conditions are not specifically limited in the present invention.

In addition, the foregoing first group callback request may further include: an urgency for requesting a callback and/or a callback valid time.

S2. The cluster core network selects a callback receiving end according to the first group callback request.

As shown in FIG. 3, step S2 further includes the following sub-steps:

S21. The cluster core network parses the first group callback request, and obtains a callback policy.

S22. The cluster core network interacts with the static group management server according to the static group identifier of the sender, and obtains information about all the terminals in the static group where the sender is located.

In the step S22, the first group callback request further includes a static group identifier of the sending end. In the cluster system, there may be more than one static group, and the cluster core network may perform indexing by using the static group identifier. Get the static group where the sender is located.

Further, the cluster core network interacts with the static group management server to parse the information of all the terminals in the static group where the sending end is located, where the information may include but is not limited to the address, name, and name of the static group. Status, area, number, priority, etc. of all terminals in the group. The static group management server mainly implements group management functions, including configuration, analysis, and management of group user relationships.

S23. The cluster core network selects the callback receiving end from the non-session group and the static group terminal according to the callback policy.

The cluster core network can know the information of the terminal currently joining the session group according to the static group identifier of the sender, and further select the receiver of the required callback from the static group according to the callback policy.

S3. The cluster core network sends a second group callback request to the callback receiving end.

The cluster core network sends a second group callback request to each callback receiving end, wherein the second group callback request may include, but is not limited to, a callback urgency and/or a callback effective time.

S4. The callback receiving end receives and stores the second group callback request to respond to the second group callback request to call back the session group where the sender is located when the preset condition is met.

After receiving the second group callback request, the callback receiving end stores the second group callback request locally, and displays the callback request on the interface of the callback receiving end in a specific form, and the user returns the interface of the receiving end by calling back After the display of the second group callback request is displayed, the session group is actively joined when the preset condition is met. The preset condition refers to the callback receiving end exiting from other conversation groups and/or during the callback valid time. In an application scenario of the present invention, the receiving end that the transmitting end selects to perform the callback may be in other session groups at this time, and only when it exits from other session groups, and satisfies the effective time of the callback, actively Joined in the session group where the sender is located, the second group callback request will not expire.

In the embodiment of the present invention, the cluster core network interacts with the static group management server to obtain information about all the terminals in the static group. In other embodiments, the static core server may not be involved, and the cluster core network may also learn static. Information about all terminals in the group.

In this embodiment, the group callback request is sent to the callback receiving end, so that the callback receiving end can call back the session group where the sender is located when the preset condition is met, thereby improving communication efficiency and satisfying related application scenarios. Demand, enhance the user experience.

As shown in FIG. 4, FIG. 4 is a schematic flowchart of a second embodiment of a group callback method in a broadband cluster system according to the first embodiment of the method for group callback in the broadband cluster system of the present invention. The present embodiment is a further extension of the first embodiment of the method for group callback in the broadband cluster system of the present invention. Therefore, the same steps as the first embodiment of the method for group callback in the broadband cluster system of the present invention are no longer used herein. Narration. This embodiment includes:

S11. The sending end sends a first group callback request to the cluster core network.

S12. The cluster core network selects a callback receiving end according to the first group callback request.

S13. The cluster core network sends a second group callback request to the callback receiving end.

S14. The callback receiving end receives and stores the second group callback request, to respond to the second group callback request to call back the session group where the sender is located when the preset condition is met.

S15. The callback receiving end sends a second group callback request response message to the cluster core network.

After receiving the second group callback request and receiving the second group callback request locally, the callback receiving end sends a second group callback request response message to the cluster core network, and has notified the cluster core network that the callback receiving end receives the sending back from the sending end. Call request.

S16. The cluster core network sends a first group callback request response message to the sending end, where the first group callback request response message includes a group callback identifier.

Further, after receiving the second group callback request response message sent by the callback receiving end, the cluster core network sends a first group callback request response message to the sending end, and has notified the sending end that the callback needs to be received. The terminal receives the group callback request sent by it. The first group callback request response message includes a group callback identifier, and the sender can know the information of all callback receivers that request the callback according to the group callback identifier, which may specifically include the receiving end of the callback. Address, name, status, area, number, and priority.

S17. The receiving end responds to the second group callback request to the callback group where the sending end is located when the preset condition is met.

In an application scenario of the present invention, the receiving end responds to the second group callback request when the preset condition is met, such as the callback receiving end exits from other session groups and/or within the valid time. Join to this conversation group.

S18. The callback receiving end deletes the second group callback request.

After the calling back party actively joins the session group where the sending end is located, the second group callback request stored locally is deleted. Further, if the callback receiving end does not respond to the second group callback request to join the session group within a preset condition (for example, the valid time of the callback), the terminal itself invalidates or deletes the local storage. The second group callback request.

In this embodiment, the group callback request is sent to the callback receiving end, so that the callback receiving end can call back the session group where the sender is located when the preset condition is met, thereby improving communication efficiency and satisfying related application scenarios. Demand, enhance the user experience.

As shown in FIG. 5, FIG. 5 is a schematic flowchart diagram of a third embodiment of a method for group callback in a broadband cluster system according to the present invention. In this embodiment, based on the first embodiment of the method for group callback in the broadband cluster system of the present invention, this embodiment is a further extension of the first embodiment of the method for group callback in the broadband cluster system of the present invention. And further comprising after step S1:

S21. The sending end sends a first cancel group callback request to the cluster core network.

The sender decides to cancel the group callback and sends a first cancel group callback request to the cluster core network. The first canceled group callback request includes a group callback identifier of the group callback request to be canceled. The method further includes the sending end canceling the group callback request for all, part or some of the receiving parties that previously sent the group callback request.

S22. The cluster core network selects to cancel the callback receiving end according to the first canceled group callback request.

As shown in FIG. 6, FIG. 6 is a sub-step of step S22, including:

S221. The cluster core network confirms the selected callback receiving end according to the group callback identifier.

The cluster core network is indexed by the group callback identifier, and the sender confirms the selected callback receiver, and further interacts with the static group management server to parse out the information of the selected callback receiver. The information may include, but is not limited to, an address, a name, a number, a priority, and the like of the callback receiving end.

S222. The cluster core network selects to cancel the callback receiving end from the callback receiving end.

Further, the cluster core network selects, from the confirmed callback receiving end, the reception of the callback that needs to be canceled according to the first canceled group callback request.

S23. The cluster core network sends a second cancel group callback request to the cancel callback receiving end.

Further, the cluster core network sends a second canceled group callback request to the callback receiving end of the sending end to cancel the callback, and has notified that the canceled callback receiving end does not need to perform group callback for the second group callback request. .

S24. The cancel callback receiving end receives and responds to the second canceled group callback request, and abandons the session group where the callback sending end is located.

After canceling the callback receiving end, after receiving the second canceled group callback request, there are two cases:

1) Cancel the call back when the receiver has joined the group session:

Before the sending end sends the first canceled group callback request, the selected canceled callback receiving end has actively joined the session group in which the sending end is located. At this time, if the second canceled group callback request sent by the cluster core network is received, the cancel callback receiving end may actively exit the group session and delete the stored second group callback request.

2) Cancel the callback when the receiving end is not joined to the group session:

If the canceled receiving end has not responded to the second group callback request, if the second canceled group callback request sent by the cluster core network is received, the canceled callback receiving end deletes the received/has received The stored second group callback request abandons the session group in which the callback sender is located.

In the embodiment of the present invention, the cluster core network interacts with the static group management server to obtain information of all terminals in the static group. In other embodiments, the static server may not be involved, and the cluster core network may also be used. Get information about all terminals in the static group.

As shown in FIG. 7, FIG. 7 is a schematic flowchart diagram of a fourth embodiment of a method for group callback in a broadband cluster system according to the present invention. In this embodiment, based on the third embodiment of the method for group callback in the broadband cluster system of the present invention, this embodiment is a further extension of the third embodiment of the method for group callback in the broadband cluster system of the present invention. And after step S24, further comprising:

S25. The cancel callback receiving end sends a second canceled group callback request response message to the cluster core network.

After canceling the local storage second group callback request, the cancel callback receiving end sends a second canceled group callback request response message to the cluster core network, and has notified the cluster core network that the callback receiving end receives the sending end and sends the sending end. Cancel the callback request.

S26. The cluster core network sends a first cancel group callback request response message to the sending end.

After receiving the second canceled group callback request response message sent by the callback receiving end, the cluster core network sends a first canceled group callback request response message to the sending end, and has notified the sending end that canceling the callback is required. The receiving end receives the canceled group callback request sent by the receiving end.

In this embodiment, by sending a cancel group callback request to the callback receiving end, the callback receiving end abandons the callback session group after receiving the canceled group callback request, thereby avoiding unnecessary callback request to be The sender is called to perform interference, thereby improving communication efficiency, meeting the requirements of related application scenarios, and improving the user experience.

As shown in FIG. 8, FIG. 8 is a schematic flowchart of a method for performing a group callback in a broadband trunking system according to a fifth embodiment of the present invention.

S110. Receive a first group callback request sent by the sending end.

S120. Select a callback receiving end according to the first group callback request.

S130. Send a second group callback request to the callback receiving end, so that the callback receiving end receives and stores the second group callback request, to respond to the second group callback request when the preset condition is met. Call back the conversation group where the sender is located.

For specific content and subsequent embodiments, reference may be made to the descriptions of the first to fourth embodiments of the method for group callback in the broadband cluster system of the present invention, and details are not described herein again.

As shown in FIG. 9, FIG. 9 is a schematic flowchart of a method for performing a group callback in a broadband trunking system according to a sixth embodiment of the present invention. The embodiment includes:

The sending end sends the first group callback request to the cluster core network, so that the cluster core network selects the callback receiving end according to the first group callback request; the cluster core network sends the second group callback request to the callback receiving end. The callback receiving end receives and stores the second group callback request to respond to the second group callback request to call back the session group in which the sender is located when the preset condition is met.

For specific content and subsequent embodiments, reference may be made to the descriptions of the first to fourth embodiments of the method for group callback in the broadband cluster system of the present invention, and details are not described herein again.

As shown in FIG. 10, FIG. 10 is a schematic flowchart of a method for performing a group callback in a broadband trunking system according to a seventh embodiment of the present invention.

The callback receiving end receives the second group callback request sent by the cluster core network and stores the second group callback request, so as to respond to the second group callback request to the callback group where the sending end is located when the preset condition is met The second group callback request is sent by the cluster core network to the callback receiving end according to the first group callback request sent by the sending end to select the callback receiving end.

For specific content and subsequent embodiments, reference may be made to the descriptions of the first to fourth embodiments of the method for group callback in the broadband cluster system of the present invention, and details are not described herein again.

As shown in FIG. 11, FIG. 11 is a schematic structural diagram of a first embodiment of a group call back device in a broadband cluster system according to the present invention. The callback device as shown in the present invention includes a processor 110 and a transceiver 120, and the processor 110 is coupled to the transceiver 120.

The transceiver 120 is configured to send and receive data, and is an interface for the group callback device to communicate with other communication devices in the broadband cluster system of the present invention.

The processor 110 controls the operation of the cluster core network, and the processor 110 may also be referred to as a CPU (Central Processing). Unit, central processing unit). Processor 110 may be an integrated circuit chip with signal processing capabilities. The processor 110 can also be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, and discrete hardware components. . The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The cluster core network may further include a memory (not shown) for storing instructions and data necessary for the operation of the processor 110, and for storing data received by the transceiver 120, and may include a read only memory (ROM, Read-Only Memory), Random Access Memory (RAM), Flash Memory, hard disk, optical disk, etc.

The processor 110 is configured to receive, by the transceiver 120, a first group callback request sent by the sender, and the processor 110 selects the callback receiver according to the first group callback request and sends the callback to the callback receiver through the transceiver 120. The second group calls back the request, so that the callback receiving end receives and stores the second group callback request to respond to the second group callback request to call back the session group where the sender is located when the preset condition is met. The sender and all callback receivers belong to the same static group.

The processor is configured to parse the first group callback request, obtain a callback policy, parse the first group callback request, and obtain a callback policy.

The processor is configured to interact with the static group management server according to the static group identifier of the sending end, and obtain information about all the terminals in the static group where the sending end is located; and the non-session group and the static group according to the callback policy. Select the callback receiver in the terminal.

The processor sends a first group callback request response message to the sending end by using the transceiver, where the first group callback request response message includes a group callback identifier.

The processor is configured to receive, by the transceiver, a second group callback request response message sent by the callback receiving end.

The processor is configured to receive, by the transceiver, a first canceled group callback request sent by the sending end, and select, according to the first canceled group callback request, the canceled callback receiving end, and send, by the transceiver, the canceled callback receiving end. And second canceling the group callback request, so that the cancel callback receiving end receives and responds to the second canceled group callback request, and abandons the session group where the callback sender is located.

For the function of each part in the embodiments of the cluster core network of the present invention, reference may be made to the description in the corresponding embodiment of the method for group callback in the broadband cluster system of the present invention, which is not repeated here.

As shown in FIG. 12, FIG. 12 is a schematic structural diagram of a second embodiment of a group call back device in a broadband cluster system according to the present invention. The callback device as shown in the present invention includes a processor 210 and a transceiver 220, and the processor 210 is connected to the transceiver 220.

The transceiver 220 is configured to send and receive data, and is an interface for the group callback device to communicate with other communication devices in the broadband cluster system of the present invention.

The processor 210 controls the operation of the transmitting end, and the processor 210 may also be referred to as a CPU (Central Processing). Unit, central processing unit). Processor 210 may be an integrated circuit chip with signal processing capabilities. The processor 210 can also be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. . The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The transmitting end may further include a memory (not shown) for storing instructions and data necessary for the operation of the processor 210, and may also store data received by the transceiver 220, and may include a read only memory (ROM, Read). -Only Memory), Random Access Memory (RAM), Flash Memory, hard disk, optical disk, etc.

The processor 210 is configured to send, by using the transceiver 220, a first group callback request to the cluster core network, so that the cluster core network selects a callback receiving end according to the first group callback request; and the cluster core network sends the callback receiving end to the callback receiving end. The second group callback request; the callback receiving end receives and stores the second group callback request to respond to the second group callback request to call back the conversation group when the preset condition is met.

The processor is configured to send, by using a transceiver, a first canceled group callback request to the cluster core network, so that the cluster core network sends a second canceled group callback request to the canceled callback receiving end; The callback session group is abandoned in response to the second canceled group callback request.

The functions of the various parts in the embodiments of the present invention are specifically described in the corresponding embodiments of the method for group callback in the broadband cluster system of the present invention, and are not repeated here.

As shown in FIG. 13, FIG. 13 is a schematic structural diagram of a third embodiment of a group call back device in a broadband cluster system according to the present invention. The callback device as shown in the present invention includes a processor 310 and a transceiver 320, and the processor 310 is coupled to the transceiver 320.

The transceiver 320 is configured to send and receive data, and is an interface for the group callback device to communicate with other communication devices in the broadband cluster system of the present invention.

The processor 310 controls the operation of the receiving end, and the processor 310 can also be called a CPU (Central Processing) Unit, central processing unit). Processor 310 may be an integrated circuit chip with signal processing capabilities. The processor 110 can also be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, and discrete hardware components. . The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The receiving end may further include a memory (not shown) for storing instructions and data necessary for the operation of the processor 310, and for storing data received by the transceiver 220, and may include a read only memory (ROM, Read). -Only Memory), Random Access Memory (RAM), Flash Memory, hard disk, optical disk, etc.

The processor 310 is configured to receive, by the transceiver 320, a second group callback request sent by the cluster core network, and store a second group callback request, to send a callback in response to the second group callback request when the preset condition is met. The session group in which the terminal is located; wherein the second group callback request is that the cluster core network receives the first group callback request sent by the sender.

The processor is configured to respond to the second group callback request to the callback group where the sending end is located when the preset condition is met; the processor deletes the second group callback request.

For the functions of the various parts in the embodiments of the receiving end of the present invention, reference may be made to the description in the corresponding embodiment of the method for group callback in the broadband cluster system of the present invention, which is not repeated here.

As shown in FIG. 14, FIG. 14 is a schematic structural diagram of a fourth embodiment of a group call back device in a broadband cluster system according to the present invention. The callback device of the present invention stores a program file 41 capable of implementing all of the above methods, wherein the program file 41 can be stored in the form of a software product in a group call back device, including a plurality of instructions for causing a computer device (may be a personal computer, server, or network device, etc.) or a processor performs all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned group callback device includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory, memory, or optical disk, etc., which can store program code, or terminal devices such as computers, servers, mobile phones, and tablets.

In summary, those skilled in the art can easily understand that the present invention provides a method, system and device for group callback in a broadband cluster system, by sending a group callback request to a callback receiving end, so that callback reception is performed. When the terminal meets the preset condition, the callback group sends the canceled group callback request to the callback receiving end, and the callback receiving end abandons the callback session group after receiving the canceled group callback request. The unnecessary callback request can be prevented from interfering with the called sender, thereby improving communication efficiency, meeting the requirements of related application scenarios, and improving the user experience.

In the several embodiments provided by the present invention, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the device implementations described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods of the various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

The above is only the embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the invention and the drawings are directly or indirectly applied to other related technologies. The fields are all included in the scope of patent protection of the present invention.

Claims (25)

1. A method for group callback in a broadband cluster system, comprising:

   The sending end sends a first group callback request to the cluster core network;

   The cluster core network selects a callback receiving end according to the first group callback request;

   Sending, by the cluster core network, a second group callback request to the callback receiving end;

   The callback receiving end receives and stores the second group callback request, to respond to the second group callback request to call back the session group where the sender is located when the preset condition is met.
2. The method according to claim 1, wherein the first group callback request includes at least a callback policy, and the cluster core network selects the callback receiving end according to the first group callback request to include :

   The cluster core network parses the first group callback request to obtain the callback policy;

   The cluster core network selects the callback receiving end from the terminals not in the conversation group according to the callback policy.
3. The method according to claim 2, wherein the callback policy comprises an identifier of the callback receiving end specified by the sending end.
4. The method according to claim 2, wherein the callback policy comprises a selection condition and/or an exclusion condition of the callback receiving end.
5. The method of claim 2 wherein:

   The sending end and all the callback receiving ends all belong to the same static group, and the first group callback request further includes a static group identifier of the sending end;

   The cluster core network further includes: before selecting the callback receiving end from the terminal not in the session group according to the callback policy:

   The cluster core network interacts with the static group management server according to the static group identifier of the sending end, and obtains information about all terminals in the static group where the sending end is located;

   The cluster core network selects the callback receiving end from the terminal group and the terminal in the static group according to the callback policy.
6. The method according to claim 2, wherein the first group callback request further includes a callback urgency and/or a callback valid time, and the second group callback request includes the The urgency of the callback and/or the effective time of the callback.
7. The method of claim 1 wherein said predetermined condition comprises:

   The callback receiving end exits from other conversation groups and/or during the callback validity time.
8. The method according to any one of claims 1 to 7, wherein after the sending end sends the first group callback request to the cluster core network, the method further includes:

   The cluster core network sends a first group callback request response message to the sending end, where the first group callback request response message includes a group callback identifier.
9. The method according to any one of claims 1 to 7, wherein the callback receiving end further comprises: after receiving and storing the second group callback request:

   The callback receiving end sends a second group callback request response message to the cluster core network.
10. The method according to any one of claims 1 to 7, wherein the callback receiving end further comprises: after receiving and storing the second group callback request:

    Receiving, by the receiving end, the session group in which the sending end is located in response to the second group callback request when the preset condition is met;

    The callback receiving end deletes the second group callback request.
11. The method according to any one of claims 1 to 7, wherein after the sending end sends the first group callback request to the cluster core network, the method further includes:

    Sending, by the sending end, a first canceled group callback request to the cluster core network;

    The cluster core network selects to cancel the callback receiving end according to the first canceled group callback request;

    Sending, by the cluster core network, a second cancel group callback request to the cancel callback receiving end;

    And the canceling the callback receiving end receives and responds to the second canceled group callback request, and discards the callback group in which the sending end is located.
12. The method of claim 11 wherein

    After the canceling the callback receiving end receives the second canceled group callback request, the method further includes:

    The cancel callback receiving end deletes the received/stored second group callback request.
13. The method of claim 11 wherein

    The first canceled group callback request includes a group callback identifier of the group callback request to be canceled;

    The selecting, by the cluster core network, the cancel callback receiving end according to the first canceled group callback request includes:

    The cluster core network confirms the selected callback receiving end according to the group callback identifier;

    The cluster core network selects the cancel callback receiving end from the callback receiving end.
14. A method for group callback in a broadband cluster system, wherein the method is applied to a cluster core network, and the method includes:

    Receiving a first group callback request sent by the sender;

    Selecting a callback receiving end according to the first group callback request;

    Sending a second group callback request to the callback receiving end, so that the callback receiving end receives and stores the second group callback request to respond to the second group when a preset condition is met The group callback request returns the session group in which the sender is located.
15. The method according to claim 14, wherein the first group callback request includes at least a callback policy, and the cluster core network selects the callback receiving end according to the first group callback request to include :

    The cluster core network parses the first group callback request to obtain the callback policy;

    The cluster core network selects the callback receiving end from the terminals not in the conversation group according to the callback policy.
16. The method of claim 15 wherein:

    The sender and all of the callback receivers belong to the same static group;

    The cluster core network further includes: before selecting the callback receiving end from the terminal not in the session group according to the callback policy:

    The cluster core network interacts with the static group management server according to the static group identifier of the sending end, and obtains information about all terminals in the static group where the sending end is located;

    The cluster core network selects the callback receiving end from the terminal group and the terminal in the static group according to the callback policy.
17. The method according to any one of claims 14-16, wherein the cluster core network further comprises: after receiving the first group callback request sent by the sender:

    The cluster core network sends a first group callback request response message to the sending end, where the first group callback request response message includes a group callback identifier.
18. The method according to any one of claims 14-16, wherein after the cluster core network sends the second group callback request to the callback receiving end, the method further includes:

    The cluster core network receives the second group callback request response message sent by the callback receiving end.
19. The method according to any one of claims 14-16, wherein the cluster core network further comprises: after receiving the first group callback request sent by the sender:

    Receiving, by the cluster core network, a first canceled group callback request sent by the sending end;

    The cluster core network selects to cancel the callback receiving end according to the first canceled group callback request;

    Sending, by the cluster core network, the second cancel group callback request to the cancel callback receiving end, so that the cancel callback receiving end receives and responds to the second canceled group callback request, and gives up the callback The session group where the sender is located.
20. The method of claim 19 wherein:

    The first canceled group callback request includes a group callback identifier of the group callback request to be canceled;

    The selecting, by the cluster core network, the cancel callback receiving end according to the first canceled group callback request includes:

    The cluster core network confirms the selected callback receiving end according to the group callback identifier;

    The cluster core network selects the cancel callback receiving end from the callback receiving end.
21. A method for group callback in a broadband cluster system, comprising:

    The callback receiving end receives the second group callback request sent by the cluster core network, and stores the second group callback request, to respond to the second group callback request callback when the preset condition is met. a session group in which the sender is located; wherein the second group callback request is that the cluster core network selects a callback receiver according to the first group callback request sent by the sender to the callback Received by the receiving end.
22. The method according to claim 21, wherein the receiving, by the callback receiving end, after receiving and storing the second group callback request, further comprising: the receiving end responding to the second when a preset condition is met The group callback request returns the session group in which the sender is located; the callback receiver deletes the second group callback request.
23. A broadband cluster system, comprising:

    a sending end, configured to send a first group callback request to the cluster core network;

    a cluster core network, configured to select a callback receiving end according to the first group callback request, and send a second group callback request to the callback receiving end;

    The callback receiving end is configured to receive and store the second group callback request, to respond to the second group callback request to call back the session group where the sending end is located when the preset condition is met.
24. A group callback device in a broadband cluster system, comprising: a processor and a transceiver, wherein the processor is connected to the transceiver;

    The processor is operative to execute instructions to implement the method of any of claims 1-23.
25. A group callback device in a broadband cluster system, storing instructions, wherein the instructions are executed to implement the method of any of claims 1-23.