BR112017028606B1 - METHOD, DEVICE AND TANGIBLE NON-TRANSIENT COMPUTER READABLE MEDIA - Google Patents

Abstract

MERGE ACTIVE GROUP CALLS. This is a method for merging active group calls that includes hosting, on a first Push To Talk (PTT) server, a first active group call. A first group of PTT customers participates in the first active group call. The first PTT server receives a request to invite a second group of PTT clients. The request includes an identifier for the second group of PTT clients. The first PTT server sends a first invitation message to the second PTT server. The first invitation message includes the identifier for the second group of PTT customers. In response to the first invitation message, the first PTT server receives a response message. The response message indicates that the second group of PTT clients participates in the second active group call. The first PTT server hosts a merged PTT group call.

Description

CLAIM OF PRIORITY

[001] This patent application claims priority to U.S. Patent Application 14/754,218 filed on June 29, 2015, the entire contents of which are incorporated herein by reference.

FIELD OF TECHNIQUE

[002] This disclosure relates to data transmission in wireless communication systems and, more specifically, to merging active group calls.

BACKGROUND OF THE INVENTION

[003] In some cases, a Push To Talk (PTT) service may provide an arbitrated service for two or more users who engage in communication. For example, a user on a group call may request permission to transmit media, for example voice, video, or other multimedia content. In some cases, the user can request permission by pressing a button on a device, which sends a request to a server. The server can determine when to grant the user a permission to transmit and send a grant message to the user. Examples of PTT service may include Mission Critical PTT (MCPTT) service which may be suitable for mission critical scenarios. In some cases, the MCPTT service may use the Third Generation Partnership Project (3GPP) transport communication mechanisms provided by Evolved Packet System (EPS) architectures to establish, maintain, and terminate current communication paths between users . In some cases, the MCPTT service may use different than 3GPP, for example, dispatcher or administrator access technologies and architectures. Examples of PTT service may also include services other than mission-critical PTT.

DESCRIPTION OF DRAWINGS

[004] Figure 1 is an exemplary wireless communication system that merges active group calls according to a deployment.

[005] Figure 2 is a data flowchart illustrating an exemplary process for merging active group calls according to a deployment.

[006] Figure 3 illustrates an exemplary signature request according to a deployment

[007] Figure 4 illustrates an exemplary notification message according to a deployment.

[008] Figure 5 illustrates an exemplary portion of a notification message that indicates bearer information according to a deployment.

[009] Figure 6 illustrates an exemplary portion of a notification message that indicates pending requests according to a deployment.

[010] Figure 7 is a data flowchart illustrating an exemplary process for merging active group calls with the use of a broadcast message in accordance with a deployment.

[011] Figure 8 is a block diagram of an exemplary computer that can be used to merge active group calls according to a deployment.

[012] Figure 9 is a flowchart illustrating an exemplary method for merging active group calls.

[013] Figure 10 illustrates an exemplary ad hoc PTT group call.

[014] Figure 11 illustrates an exemplary prearranged PTT group call.

[015] Figure 12 illustrates an exemplary conversation PTT group call.

[016] Similar reference numbers and designations in the various drawings indicate similar elements.

DETAILED DESCRIPTION

[017] The present disclosure is directed to merging active group calls. In some cases, multiple PTT groups may be temporarily merged. For example, when an incident occurs in an area, different PTT groups can be merged so that members in these different PTT groups can communicate with each other. In some cases, an ad hoc group or a prearranged group may be formed to include different PTT groups. An adhoc group call is one in which group members are included in the request that initiates the call. A prepackaged group is one in which a group list of members is predefined and the call is initiated by including the URI associated with the group in the request that initiates the call. Users in these different PTT groups can be invited to join the ad hoc group call or the pre-arranged group call. After the incident, the ad hoc group or prearranged group call may be cancelled.

[018] In some cases, two or more PTT groups have active group calls and would like to merge their active group calls into a merged group call. Using an ad hoc group call or a prearranged group call for a merged call may lose the status of active group calls. For example, the ad hoc group call or prearranged group call approach can invite all members of PTT groups, including members who do not participate in current active group calls. Additionally, metadata information of active group calls, for example queue information, may be lost in the ad hoc group call or prearranged group call.

[019] In some cases a type of group known as a talk group may be used for PTT calls. Unlike an adhoc group or pre-arranged group where members are invited to join the group call at the start of the call in a chat group, group members need to request to join (in a similar way as in a chat group). dial-in conference).

[020] In some cases of pre-arranged and chat groups as well as having a list of members authorized to be invited or allowed to join to join the group call, the authorized members may have to join the group to nominate a current interest in being invited to a group call. Active participants in a group call may be a subset of those affiliated with the group as some affiliated members may not be able to participate in the call (for example, due to being out of radio coverage or the user not accepting the invitation to join) .

[021] In some cases, multiple talkgroups may need to be merged and authorized members of other groups may attempt to join the merged talkgroup call (e.g., by sending an invitation to the PTT server to join the call server-hosted fused chat group). However, the chat group call hosting server may not have access to group information, for example the member list, of other PTT groups that host their active group calls on a different server. Therefore, the hosting server may be unable to invite or authorize members of other PTT groups to join the chat group call. Additionally, authorized members of a chat group may not be aware that the chat group has been merged with a temporary chat group call. Therefore, a means is needed to indicate to all authorized members that the chat group has been merged into a temporary chat group call or to redirect members who attempt to join the original chat group and that they need to join the call. fused temporary chat group icon.

[022] Figure 1 is an exemplary wireless communication system 100 that merges active group calls according to a deployment. For example, a first Push To Talk (PTT) server may already host a first active group call or be in the process of establishing a new group call that comprises multiple groups. A first group of PTT customers can now participate in the first active group call. The first PTT server may need to invite a second group of PTT clients as part of establishing a new group call comprising multiple groups or may receive a request to invite a second group of PTT clients to the already established group call. The request to establish a new group call comprising multiple groups or the request to invite a second group of PTT clients may include an identifier for the second group of PTT clients. The first PTT server may send a first invitation message to a second PTT server. The second PTT server can host a second active group call. The first invitation message may include the identifier for the second group of PTT customers. The second group of PTT customers participates in the second active group call. In response to the first invitation message, the first PTT server may receive a response message that contains a list of members of the second group. The response message may indicate which members of the second group of PTT customers are affiliated with the group. The response may indicate that the group is on an active group call. The response message may indicate which members of the second group of PTT customers participate in the second active group call.

[023] In some deployments, the first PTT server may send a second invitation message. The second invitation message may invite at least one PTT client from the second group of PTT clients to the merged PTT group call. The second invitation message may indicate that the merged PTT group call replaces or suspends the second active group call. In some cases multiple instances of the second invitation message may be sent and addressed individually to each PTT client in the second group of PTT clients. In some cases, the second invitation message may be sent over a Multimedia Broadcast Service (MBMS) channel.

[024] In some implementation the first invitation message to a second PTT server may contain an indication to the second PTT server that if the group is on an active call that a second invitation message is requested to be sent by the second PTT server to the second group of PTT customers for the merged PTT call. In this case, the first and second invitation messages contain the identifiers necessary for PTT Clients to join the merged PTT call.

[025] In some deployments, the first PTT server may send a subscription request to the second PTT server. In response to the subscription request, the first PTT server may receive a notification message. The notification message may include metadata from the second group of PTT clients. In some cases, the metadata may indicate one or more pending requests to send media from members of the second group of PTT clients. The pending request (or pending requests) may be received (or may be received) on the second PTT server before the first invitation message. In some cases, the metadata may indicate at least one of a timestamp, a queue position, or a priority of each of the pending requests. In some cases, the metadata may indicate a Multimedia Multicast Service (MBMS) bearer that is used by at least one PTT client of the second PTT client group for the second active group call.

[026] The first PTT server may host a merged PTT group call that may have participants from the first group of PTT clients and the second group of PTT clients.

[027] Merging active group calls in accordance with methods and systems described herein may provide one or more advantages. For example, the call status information of the second group call is transferred to the first PTT server. Therefore, the first PTT server can invite only affiliated members or those members who actually participate in the second group call. In some cases the authorized members of a group may be very large, but the affiliate members and current active participants in the call may be much smaller, so there is a great advantage to inviting only the affiliated group members or active participants in the group call. Furthermore, the first PTT server may also obtain the information of the pending requests in the second group call and may process these pending requests in the merged call and consolidate the pending requests of the first group call with the pending request of the second group call accordingly. with the timestamps, relative queue positions and/or priorities of the requesting participants of both group calls. Furthermore, using an MBMS channel to invite members participating in the second group call to the merged call can save resources and improve the efficiency of the communication system, and individually inviting a very large number of participants to join is impractical in a reasonable time.

[028] At a high level, the exemplary wireless communication system 100 includes a wireless communication network 110, which includes a first PTT server 102 and a second PTT server 112. The exemplary wireless communication system 100 also includes Equipment User Units (UEs) 106a to 106c and UEs 116a to 116b. In some cases, each of UEs 106a to 106c and UEs 116a to 116b may include a PPT client. The wireless communication system 100 may also include UEs that are non-wireless devices, such as a PTT Dispatch Console that may be connected to a wireless network using a fixed access technology such as Ethernet or a WLAN. . A PTT client may represent an application, set of applications, software, software modules, hardware, or a combination thereof that can be configured to communicate with a PTT server for PTT services. As illustrated, UEs 106a to 106c are included in the first group 104 and UEs 116a to 116b are included in the second group 114. In some cases, the first group 104 has a first group call in progress in which the UEs 106a to 106c participate, and the second group 114 has a second group call in progress in which UEs 116a to 116b participate.

[029] The exemplary wireless communication system 100 also includes a first PTT server 102 that hosts the first group call and a second PTT server 112 that hosts the second group call. In some cases, a PTT server, e.g., the first PTT server 102 or the second PTT server 112, may provide a participation function, a control function, a termination function, or a combination thereof for a PTT service. For example, in some cases, a PTT server may provide a participation function for an associated PTT client. In these or other cases, the PTT server may be in the same service domain as the associated PTT client. An example of a service domain might be a network or a portion of a network. For example, the PTT server may be an application server on a PPT client's home core network. The PTT server may have access to the configurations and settings of the associated PTT client. The PTT server may also perform a media replication function, a traffic optimization function, or a combination thereof for the associated PTT client.

[030] In some cases, a PTT server may provide the control function for a group call. In these or other cases, the PTT server can act as the host of the group call. The PTT server can perform the Media Burst Control Arbitration function, for example, the Media Burst Control or Base Control function, to receive and arbitrate requests to send media in a group call. The PTT server may also perform a media replication function, a traffic optimization function, or a combination thereof for the group call.

[031] In some cases, the PTT servers that perform the participation function and the control function may be co-located in the same entity, for example, the first PTT server 102 and the second PTT server 112 illustrated in Figure 1. Alternatively, the PTT servers 102 PTT that realize the participation function and the control function can be located in different entity in the network architecture. In some cases, as illustrated, the first PTT server 102 and the second PTT server 112 may be located on the same wireless network. Alternatively, the first PTT server 102 and the second PTT server 112 may be located on different wireless networks.

[032] In some cases, PTT servers and PTT clients may be deployed in compliance with the PPT over Cellular (PoC) or Push to Communicate for Public Safety (PCPS) standard. The PoC and PCPS standards were developed by Open Mobile Alliance (OMA) to provide PTT service over Internet Protocol (IP) based cellular networks. In some cases PTT servers and PTT clients can be deployed in compliance with the Mission Critical PTT standard under development by 3GPP.

[033] In operation, the first PTT server 102 receives a request to invite UEs in the second group 114. The request may include an identifier for the second group 114. The first PTT server 102 sends a first invitation message to the second PTT server 112. The first invitation message may include the identifier for the second group 114. In response to the first invitation message, the first PTT server 102 receives a response message. The response message may indicate that the second group 114 has an active group call. The first PTT server 102 sends a second invitation message to at least one of the UEs 116a to 116b to invite the at least one of the UEs 116a to 116b to the merged PTT group call. The second invitation message may indicate that the merged PTT group call replaces or suspends the second active group call. The first PTT server 102 may host a fused PTT group call in which UEs 106a to 106c and UEs 116a to 116b may participate. Figures 2 through 12 and associated descriptions provide additional details for these deployments.

[034] Regarding a general description of the elements, a UE can be called a mobile electronic device, user device, mobile station, subscriber station, portable electronic device, mobile communications device, wireless modem, PTT dispatch console or wireless terminal. Examples of a UE (e.g., UEs 106a to 106c and UEs 116a to 116b) may include a cell phone, personal data assistant (PDA), smart phone, PTT dispatch console, laptop-type computer, personal computer ( PC) tablet, pager, portable computer, portable gaming device, wearable electronic device, or other mobile communications device that has components to communicate voice or data via a wireless communications network. The wireless communication network may include a wireless link over at least one of licensed spectrum and unlicensed spectrum.

[035] Other examples of a UE include mobile and fixed electronic devices. A UE may include a Mobile Equipment (ME) device and a removable memory module, such as a Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, an Identity Module application Subscriber Identity Module (USIM), or a Removable User Identity Module (R-UIM) application. The term "UE" may also refer to any hardware or software component that can terminate a communication session for a user. Additionally, the terms "user equipment", "UE", "user equipment device", "user agent", "UA", "user device" and "mobile device" may be used synonymously in the this document.

[036] The wireless communication network 110 may include one or a plurality of radio access networks (RANs), other access networks such as fixed Ethernet or IEEE 802.11 WLAN, core networks (CNs), and external networks. RANs may comprise one or more radio access technologies. In some deployments, radio access technologies may be Global System Mobile Communications (GSM), Interim Standard 95 (IS-95), Universal Mobile Telecommunications System (UMTS), CDMA2000 (Code Division Multiple Access), System Universal Evolved Mobile Telecommunications (UMTS), Long Term Trial (LTE) or LTE-Advanced. In some instances, core networks may be evolved packet cores (EPCs).

[037] A RAN is part of a wireless telecommunications system that deploys a radio access technology, such as UMTS, CDMA2000, 3GPP LTE and 3GPP LTE-A. In many applications, a RAN includes at least one base station. A base station may be a radio base station that can control all or at least some radio-related functions in a fixed part of the system. The base station can provide radio interface in its coverage area or a cell for a UE to communicate. The base station can be distributed throughout the cellular network to provide a wide area of coverage. The base station communicates directly with one or a plurality of UEs, other base stations, and one or more core network nodes.

[038] Although the elements of Figure 1 are shown to include various parts, portions or various component modules that implement the various features and functionalities, regardless of whether these elements may instead include numerous submodules, third-party services, components, libraries, and the like, as appropriate. Furthermore, the features and functionality of multiple components can be combined into fewer components as appropriate.

[039] Figure 10 illustrates an exemplary ad hoc PTT group call. The system 1000 for an ad hoc group PTT call may involve a PPT client 1002 that acts as a group call initiator, a number of PTT clients 1004a to 1004c that will participate in the group call, and a PTT server 1006. The initiator of group call 1002 may send an invitation message to the PTT server 1006 to initiate the group call. The invitation message can include a list of PTT customers who will be invited to the group call. The PTT server 1006 then sends invitation requests 1008a to 1008c to the PTT clients 1004a to 1004c to form a group call 1010.

[040] Figure 11 illustrates an exemplary prearranged PTT group call. The system 1100 for a prearranged PTT group call may involve a PTT server 1104, a PPT client 1106 that acts as a group call initiator, and a number of PTT clients 1108a to 1108c that will participate in the group call. A list of pre-arranged group PTT clients 1102 is pre-provided on the PTT server 1104. The group call initiator 1106 may send an invitation message to the Uniform Resource Indicator (URI) for the group. The PTT server 1104 hosting the group then sends an invitation message to the PTT clients 1108a to 1108c in the prearranged group to form a group call 1112.

[041] Figure 12 illustrates an exemplary conversation PTT group call. The system 1200 for a conversational PTT group call may involve a PTT server 1204, a PPT client 1206 that acts as a group call initiator, and a number of PTT clients 1208a to 1208c that will participate in the group call. In a talk-restricted PTT group call, a list of PTT clients 1202 is pre-supplied on the PTT server 1204. PTT clients that would like to join the group call send invitation messages or dialed messages 1210a to 1210c to the URI to the group to form a group call 1212. In a restricted talk PTT group call, the PTT server 1204 hosting the group checks whether the requesting PTT client is in the pre-provided list. In an unrestricted talk PTT group call, there is no pre-supplied list and any PTT customer can call in. These long-running, semi-permanent group talk calls are likely to be a common type of group call used by law enforcement agencies.

[042] Figure 2 is a data flowchart illustrating an exemplary process 200 for merging active group calls according to a deployment. The data flowchart includes a PTT X1 control server 202. The PTT X1 control server 202 represents an application, set of applications, software, software modules, hardware, or a combination thereof that can be configured to provide the control function. for an active group call, for example, active group call X1 as illustrated in Figure 2. In some cases, a group of PTT clients, for example, group X1, may participate in active group call X1. For example, as illustrated, group hardware, or a combination thereof that may be configured to provide a participation function for the PTT client A 206. In some cases, the PTT X1 control server 202 and the PTT participant server A 204 may be deployed on the same PTT server. In these or other cases, messages between the PTT X1 control server 202 and the PTT A participant server 204 shown in the data flow chart may be omitted.

[043] The data flowchart also includes an X2 PTT control server 212 that provides a control function for an active X2 group call. In some cases, another group of PTT customers, for example, group X2, may participate in the active group call X2. For example, as illustrated, group PTT B2 218. In some cases, the PTT X2 control server 212 and the PTT B participant server 214 may be deployed on the same PTT server. In these or other cases, messages between the PTT X2 control server 212 and the PTT B participant server 214 shown in the data flow chart may be omitted.

[044] As shown in Figure 2, before step 1, both active group calls X1 and X2 are in progress. In step 1, PTT client A 206 sends a request to participating PTT server A 204 to invite group X2 to the active group call X1. In some cases, the request may be a Reference request. In some cases, the request may include an identifier for the X2 group. Examples of the identifiers may include a Uniform Resource Indicator (URI) or any other indicators of group identity. In some cases, the URI may be a string of characters used to identify the X2 group. In some cases, the identifier may be included in a References header field of the Reference request. In some cases, the request may be sent by an authorized PTT client in group X1, for example, PTT client A 206 as illustrated. Alternatively or in combination, the request may be sent by a dispatcher who is not in group X1. Alternatively or in combination, the request may be sent by a Group Management Server based on creating a merged group of X1 and X2 on the Group Management Server in order to merge the group calls of X1 and X2.

[045] In step 2, the PTT participating server A 204 forwards the request to the PTT X1 control server 202. In step 3, the PTT X1 control server 202 sends an OK response to the PTT participating server A 204, which forwards the same for the PTT A client 706 in step 4. In some cases, the OK response indicates that the PTT X1 control server 202 received the request.

[046] In step 5, the PTT X1 control server 202 sends an invitation message to the PTT X2 control server 212. In some cases, the invitation message may include the X2 group identifier. In responding to the invitation message, in step 6, the PTT X2 control server 212 sends a response message to the PTT X1 control server 202. In some cases, the response message may be a 4xx message, e.g. 403 message. In some cases, the response message may include an indication that group X2 is on an active group call. In some cases, the indication that group X2 is on an active group call can be encoded using Extensible Markup Language (XML). Alternatively or in combination, the indication may be encoded in one or more existing or new header fields in the response message. In some cases, the response message may also include a list of PTT clients in group X2. In some cases, the PTT client list may be encoded using Extensible Markup Language (XML). Alternatively or in combination, the PTT client list may be encoded in one or more existing or new header fields in the response message.

[047] In some cases, some of the PTT customers in group X2 currently participate in the active group call X2, while some other PTT customers in group X2 are authorized to participate but do not currently participate in the current active group call X2 yet. In some cases some of the PTT customers in the X2 group are affiliated with the group but do not currently participate in the active X2 group call. In these or other cases, the response message may include a list of the PTT clients in group X2, and one or more indications to indicate whether the PTT clients in group X2 currently participate in the group X2 call or are currently affiliated with group X2. Therefore, PTT customers who currently participate in or are affiliated with the active X2 group call can be invited to the merged call. PTT customers in the X2 group who do not participate in the X2 group call may be allowed to join the merged call later. This approach allows the PTT control server X1 202 to merge the active participants or affiliate members of group calls X1 and X2 without inviting all authorized members of groups X1 and

[048] Alternatively or in combination, the PTT control server X1 202 may use a subscription notification procedure to obtain the information of members in group X2 currently participating in the active group call X2. For example, the PTT control server X1 202 may send a subscription request to the PTT control server X2 212 and request data about the PTT clients in the group X2. The subscription request may include an identifier for the X2 group. Figure 3 illustrates an exemplary subscription request 300 in accordance with a deployment. As shown in Figure 3, subscription request 300 may include an event identity (ID) field. The event ID field may indicate that the event is group_members, which informs the PTT X2 control server 212 that group member information in a group is requested.

[049] In response to the subscription request, the PTT control server X2 212 may send a notification message to the PTT control server X1 202. The notification message may indicate the PTT clients currently participating in the active group call X2 and PTT customers who are authorized but have not yet joined. Figure 4 illustrates an exemplary notification message 400 in accordance with a deployment. As shown in Figure 4, notification message 400 may include a list of group members in group X2. For each group member, notification message 400 may include the member's identity, for example, the member's Session Initiation Protocol (SIP) URI, and a status indicator. The status indicator can be set to "active" for the member currently participating in the X2 group call. The status indicator can be set to "inactive" for the member not currently participating in the X2 group call. The status indicator can be set to “affiliated” for the member who is affiliated but not currently participating in the X2 group call.

[050] In some cases, the notification message may also indicate bearer information that members in group X2 use to participate in the active group call X2. Figure 5 illustrates an exemplary portion of a notification message 500 that indicates bearer information in accordance with a deployment. As shown in Figure 5, notification message 500 may include a Temporary Multicast Group Identity (TMGI) for each member of group X2 that actively participates in group call X2. The TMGI may indicate a Multimedia Broadcast/Selective Broadcast Service (MBMS) bearer that is used by the active member in the X2 group call. In some cases, the signature notification procedure may be combined with steps 15 through 18 discussed below.

[051] In step 7 and 9, the PTT control server X1 202 invites PTT clients in group X2 that actively participate in the active group call X2 to participate in the merged call. For example, in step 7, the PTT control server , the PTT control server for PTT Customers to join the merged PTT call.

[052] In some cases the invitation message sent in step 5 may indicate that if the group is in an active group call that the PTT X2 control server 212 should invite the active X2 group call members. In this case the invitation messages in steps 7 and 9 are sent by the PTT X2 control server 212 instead of the PTT X1 control server 202. In this case the invitation message in steps 5, 7 and 9 contains the identifiers necessary for the PTT customers join the merged PTT call.

[053] In some cases, the invitation message may indicate that the invitation is for a merged call that replaces or suspends the active X2 group call. If the merged call replaces the active group call X2, then the active group call X2 may end when the PTT clients participating in the active group call X2 join the merged call. If the merged call suspends the active group call X2, then the active group call X2 may be placed on hold when PTT clients participating in the active group call X2 have joined the merged call. When the merged call ends, the active X2 group call can be resumed. In some cases, the indication that the merged call replaces or suspends the active X2 group call can be encoded using Extensible Markup Language (XML). Alternatively or in combination, the indication may be encoded in one or more existing or new header fields in the response message.

[054] In some cases, the invitation message may also indicate whether a unicast bearer or a multicast bearer is used for the merged call. If a multicast bearer is used, the invitation message may include a TMGI that is associated with the multicast bearer to be used.

[055] In step 11, the PTT B1 client 216 sends an OK message to the participating PTT B server 214, which forwards the OK message to the PTT X1 control server 202 in step 12. Similarly, in step 13 , the PTT B2 client 218 sends an OK message to the participating PTT B server 214, which forwards the OK message to the PTT X1 control server 202 in step 14. OK messages may indicate that the PTT client has received the PTT message. invitation.

[056] In step 15, the PTT X1 control server 202 may send a signature request to the PTT X2 control server 212 to request metadata information from the X2 group. The subscription request may include an identifier for the X2 group. In step 16, the PTT X2 control server 212 sends an OK message to the PTT X1 control server 202 to indicate that the signature request is received. In step 17, the PTT X2 control server 212 sends a notification message to the PTT X1 control server 202. The notification message may include the X2 group metadata information. In some cases, metadata information may include information about pending requests to send media on the active group call activates X2 before the PTT control server queue appropriately ordered requests pending in the active group call X1 and process accordingly.

[057] Figure 6 illustrates an exemplary portion of a notification message 600 that indicates pending requests according to a deployment. As shown in Figure 6, notification message 600 may indicate the PTT base request queue information of a pending request. The queue information may include the queue position, priority, timestamp, or a combination thereof for the pending request. In some cases, a privilege level may be used to indicate priority.

[058] In some cases, as discussed previously, the notification message may also indicate the bearer information that is used by the PTT clients for the active X2 group call. For example, the notification message may include a TMGI for the MBMS bearer that is used by an active member participating in the active group call X2.

[059] In step 19, the PTT B1 client 216 sends an update to the participating PTT B server 214, which forwards the update to the PTT X2 control server 212 in step 20. In some cases, the update may indicate that the client PTT B1 216 will put the session in which the active group call X2 was on hold. Alternatively or in combination, an invitation message can be used to indicate that the session he had with the X2 group call is placed on hold. In some cases, for example, the active group call X2 can be replaced by the merged call. In these or other cases, the PTT B1 client 216 can send a Bye message to indicate that the session it had with the active group call X2 will be terminated. In step 21, the PTT X2 control server 212 sends an OK response to the participating PTT B server 214, which forwards the OK response to the PTT B1 client 216 in step 22. The OK response indicates that the update is received. Similarly, in step 23, the PTT B2 client 218 sends an update to the participating PTT B server 214, which forwards the update to the PTT X2 control server 212 in step 24. Consequently, the PTT X2 control server 212 can placing the active group call X2 on hold or ending the active group call X2 when the PTT control server

[060] In step 25, the PTT client A 206 may send a media burst request message to the participating PTT server A 204, which forwards the media burst request message to the PTT X1 control server 202. media burst request message can be used to request to send media in the merged group call. In some cases, the media burst request message may be sent using a Real-Time Control Protocol (RTCP) application package (APP). Alternatively or in combination, the media burst request message can be sent using Binary Base Control Protocol (BFCP).

[061] In step 27, the PTT X1 control server 202 may determine to grant the request to send media. The PTT control server an APP RTCP or BFCP package. The PTT control server The obtained media burst message can be sent using an APP RTCP or BFCP packet. Consequently, PTT client A 206 can send media to PTT X1 control server 202, which forwards the media to other members in the merged call, which includes PTT client B1 216 and PTT client B2 218.

[062] In some cases, instead of inviting members of the active group call X2 individually to the merged call, an invitation message may be broadcast to multiple members in the active group call X2. Figure 7 is a data flowchart illustrating an exemplary process 700 for merging active group calls using a broadcast message in accordance with a deployment. The data flowchart includes an X1 PTT control server 702 that hosts an X1 active group call and an X2 PTT control server 712 that hosts an X2 active group call. The data flowchart also includes a PPT participant server A 704 associated with a PPT client A 706 that participates in the active group call X1. In some cases, the PTT X1 control server 702 and the PTT A participant server 704 may be deployed on the same PTT server. The data flowchart also includes a participating PPT server B 714 associated with a PPT client B1 716 and a PPT client B2 718. The PTT client B1 716 and the PTT client B2 718 participate in the active group call X2. In some cases, the PTT X2 control server 712 and the PTT B participant server 714 may be deployed on the same PTT server.

[063] As illustrated, the active group call X1 is in progress in step 1 and the active group call 704 to invite group X2 to active group call X1. In some cases, the request may be a Reference request. In some cases, the request may include an identifier for the X2 group. Examples of the identifiers may include a Uniform Resource Indicator (URI) or any other indicators of group identity. In some cases, the URI may be a string of characters used to identify the X2 group. In some cases, the identifier may be included in a References header field of the Reference request. Alternatively or in combination, the request may be sent by a Group Management Server based on creating a merged group of X1 and X2 on the Group Management Server in order to merge the group calls of X1 and X2.

[064] In step 4, the PTT participating server A 704 forwards the request to the PTT X1 control server 702. In step 5, the PTT X1 control server 702 sends an OK response to the PTT participating server A 704, which forwards the same for the PTT A 706 client in step 4.

[065] In step 7, the PTT X1 control server 702 sends an invitation message to the PTT X2 control server 712. In some cases, the invitation message may include the X2 group identifier. In responding to the invitation message, in step 8, the PTT control server X2 712 sends a response message to the PTT control server X1 702. In some cases, the response message may include an indication that the group X2 is on an active group call. In some cases, the response message may also include a list of PTT clients in the X2 group and information about whether each PTT client is currently active in the X2 group call. In some cases, the response message may include an indication that group X2 is on an active group call. In some cases, the indication that group X2 is on an active group call can be encoded using Extensible Markup Language (XML). Alternatively or in combination, the indication may be encoded in one or more existing or new header fields in the response message. In some cases, the response message may also include a list of PTT clients in group X2. In some cases, the PTT client list may be encoded using Extensible Markup Language (XML). Alternatively or in combination, the PTT client list may be encoded in one or more existing or new header fields in the response message.

[066] In some cases, some of the PTT customers in group X2 currently participate in the active group call X2, while some other PTT customers in group X2 are authorized to participate, but do not currently participate in the current active group call X2 yet. In some cases some of the PTT customers in the X2 group are affiliated with the group but do not currently participate in the active X2 group call. In these or other cases, the response message may include a list of the PTT clients in group X2, and one or more indications to indicate whether the PTT clients in group X2 currently participate in the group X2 call or are currently affiliated with group X2. Therefore, PTT customers who currently participate in or are affiliated with the active X2 group call can be invited to the merged call. PTT customers in the X2 group who do not participate in the X2 group call may be allowed to join the merged call later. This approach allows the PTT control server X1 702 to merge active participants or affiliate members of group calls X1 and X2 without inviting all authorized members of groups X1 and X2.

[067] The invitation message in step 7 and step 9 contains the identifiers necessary for PTT Clients to join the merged PTT call.

[068] In some cases the invitation message sent in step 7 may indicate that if the group is in an active group call, that the PTT X2 control server 712 should invite the active X2 group call members. In other cases the invitation message sent in step 7 does not indicate that the PTT X2 control server 712 should invite active X2 group call members. In this case the invitation messages at 9 are sent by the PTT X1 control server 702 instead of the PTT X2 control server 712.

[069] In step 9, the PTT X2 control server 712 broadcasts an invitation message to all active members in the X2 group. The invitation message can be a message that is configured to send over a multicast bearer. For example, the invitation message can be a different SIP message. In some cases, the invitation message may include information from the active group call X1 that members of the group X2 can join the merged call. For example, the invitation message may include an identifier of group X1, for example, the URI of group X1. In some cases, the invitation message may indicate the bearer information for the active X1 group call. For example, the invitation message may include one or more TMGIs for the active bearers used in the active group call X1. In some cases, the invitation message may also include ProSe (Proximity Based Services) information for the active X1 group call. Alternatively or in combination, the invitation message may be sent using a modified base control message. The modified base control message may include information about the new group call for the merged group call. For example, the invitation message may include an identifier, a TMGI, or a combination thereof of the new group. In some cases, the invitation message may include authentication information that can be used to authenticate PTT clients to the X2 group. For example, the authentication information may be an encrypted authentication device, a P-Asserted URI, or a combination thereof.

[070] In step 10, PTT client B1 716 requests to join active group call X1 for the merged call. In some cases, the PTT B1 client 716 sends authentication response information to the PTT X1 control server 702. The authentication response information may be associated with the authentication information in the broadcast invitation message. For example, authentication response information may be based on the decoded authentication device. The PTT X1 control server 702 may authenticate the PTT B1 client 716 based on the authentication information and authorize the PTT B1 client 716 to join the merged call. In some cases, the PTT control server receive an authentication challenge. The authentication challenge can include a contact URI identity for the active group call X2. If the PTT client B1 716 does not successfully pass the authentication challenge, the PTT control server X1 702 may determine that the group membership characteristics for the PTT Client will be changed, for example, instructing the PTT Client to leave the call group, instruct the PTT Client not to send data, or not to receive and send data.

[071] Similarly, in step 11, the PTT B2 client 718 requests to join the active group call X1 for the merged call.

[072] In step 12, the PTT B1 client 716 sends an update message to the participating PTT B server 714, which forwards the update message to the PTT X2 control server 712 in step 13. The update message may indicate that PTT client B1 716 would not participate in the X2 group call. For example, the update message may indicate that PTT client B1 716 will not receive, will not send, or a combination thereof, on the X2 group call. Similarly, in step 14, the PTT B2 client 718 sends an update message to the participating PTT B server 714, which forwards the update message to the PTT X2 control server 712 in step 15. In some cases, the server X2 PTT control module 712 can keep the X2 group call active until all active members cease participating in the X2 group call. As discussed previously, in some cases, the PTT X2 control server 712 may terminate the X2 group call. Alternatively, the X2 PTT control server 712 may place the X2 group call on hold.

[073] Figure 8 is a block diagram 800 of an exemplary computer that can be used to merge active group calls according to a deployment. The illustrated computer 802 is intended to encompass any computing device such as a server, a desktop computer, a laptop/notebook type computer, a wireless data port, a smart phone, a personal data assistant (PDA), a tablet-type computing device, one or more processors on such devices, and/or any other suitable processing device, including both physical and/or virtual instances of the computing device. Additionally, computer 802 may comprise a computer that includes an input device, such as a numeric keypad, a keyboard, a touch screen, microphone, speech recognition device, other device that can accept user information, and/or or an output device that carries information associated with the operation of the computer 802, which includes digital data, visual and/or audio information, or a GUI.

[074] Computer 802 can serve as a client, a network component, a server, a database or other persistence, and/or any other component of system 100. For example, computer 802 can be used to deploy a or more functions of a PTT server or a PPT client. The illustrated computer 802 is communicably coupled to a network 830. In some deployments, one or more components of the computer 802 may be configured to operate in a cloud computing-based environment.

[075] At a high level, computer 802 is an electronic computing device operable to receive, transmit, process, store, or manage data and information associated with system 100. According to some implementations, computer 802 may also include or be communicably coupled to an application server, email server, web server, cache server, streaming data server, business intelligence (BI) server, and/or other server.

[076] Computer 802 may receive requests over network 830 from a client application (e.g., running on another computer 802) and respond to the received requests by processing said requests in an appropriate software application. In addition, requests may also be made to the computer 802 from internal (e.g., from a command console or other appropriate access method), external or third-party users, other automated applications, as well as any other entities, other individuals , appropriate systems or computers.

[077] Each of the components of the computer 802 may communicate using a system bus 803. In some implementations, any and/or all of the components of the computer 802, both hardware and/or software, may interface with each other. with others and/or interface 804 via system bus 803 using an application programming interface (API) 812 and/or a service layer 813. API 812 may include specifications for routines, data structures, and object classes. API 812 may be computer language independent or dependent and refer to a complete interface, a single function, or even a set of APIs. Service layer 813 provides software services to the computer 802 and/or the system 100. The functionality of computer 802 may be accessible to all service consumers using this service layer. Software services, such as those provided by service layer 813, provide defined and reusable business functionality through a defined interface. For example, the interface may be written by software in JAVA, C++, or another suitable language that provides data in Extensible Markup Language (XML) or other suitable format. Although illustrated as an integrated component of computer 802, alternative implementations may illustrate API 812 and/or service layer 813 as autonomous components relative to other components of computer 802 and/or system 100. Furthermore, any part or all of Portions of API 812 and/or service layer 813 may be deployed as children or submodules of another software module, enterprise application, or hardware module without departing from the scope of this disclosure.

[078] Computer 802 includes an interface 804. Although illustrated as a single interface 804 in Figure 8, two or more interfaces 804 may be used according to particular needs, desires, or implementations of the computer 802 and/or the system 100. Interface 804 is used by computer 802 to communicate with other systems in a distributed environment - including system 100 - connected to network 830 (whether illustrated or not). Generally, interface 804 comprises logic encoded in software and/or hardware in a suitable and operable combination to communicate with network 830. More specifically, interface 804 may comprise software that supports one or more communication protocols associated with mode communications. that the network 830 or interface hardware is operable to communicate physical signals within the illustrated system 100 and beyond.

[079] Computer 802 includes a processor 805. Although illustrated as a single processor 805 in Figure 8, two or more processors may be used according to particular needs, desires, or particular implementations of the computer 802 and/or the system 100. Generally, processor 805 executes instructions and manipulates data to perform operations of computer 802. Specifically, processor 805 performs functionality required to merge active group calls.

[080] The computer 802 also includes a memory 806 that holds data for the computer 802 and/or other components of the system 100. Although illustrated as a single memory 806 in Figure 8, two or more memories can be used according to needs in particular desires, or particular implementations of computer 802 and/or system 100. Although memory 806 is illustrated as an integral component of computer 802, in alternative implementations, memory 806 may be external to computer 802 and/or system 100.

[081] Application 807 is an algorithmic software engine that provides functionality in accordance with particular needs, desires, or particular deployments of computer 802 and/or system 100, particularly with respect to functionality required to merge active group calls . For example, application 807 may serve as one or more components/applications depicted in Figures 1 through 12. Additionally, although illustrated as a single application 807, application 807 may be deployed as multiple applications 807 on computer 802. Furthermore, although illustrated as integral to computer 802, in alternative deployments, application 807 may be external to computer 802 and/or system 100.

[082] There may be any number of computers 802 associated with or external to system 100 and communicating over network 830. Additionally, the terms "client", "user" and other appropriate terminology may be used interchangeably as appropriate without departing from the scope of this revelation. Furthermore, this disclosure contemplates that many users can use one computer 802, or that a user can use multiple computers 802.

[083] Figure 9 is a flowchart illustrating an exemplary method 900 for merging active group calls. Method 900 may begin at block 902, where a first Push To Talk (PTT) server hosts a first active group call. A first group of PTT customers participates in the first active group call. At block 904, the first PTT server receives a request to invite a second group of PTT clients. The request includes an identifier for the second group of PTT clients.

[084] In block 906, the first PTT server sends a first invitation message to a second PTT server. The second PTT server hosts a second active group call. The first invitation message includes the identifier for the second group of PTT customers. The second group of PTT customers participates in the second active group call. In block 908, in response to the first invitation message, the first PTT server receives a response message. The response message indicates that the second group of PTT clients participates in the second active group call.

[085] In block 910, the first PTT server sends a second invitation message. The second invitation message invites at least one PTT client from the second group of PTT clients to the merged PTT group call. The second invitation message indicates that the merged PTT group call replaces or suspends the second active group call. In some cases, the second invitation message is sent over a Multimedia Broadcast Service (MBMS) channel.

[086] In block 912, the first PTT server sends a signature request to the second PTT server. At block 914, in response to the subscription request, the first PTT server receives a notification message. The notification message includes metadata from the second group of PTT clients. In some cases, metadata indicates a pending request to send media. The pending request is received on the second PTT server before the first invitation message. In some cases, the metadata indicates at least one of a timestamp, queue position, or priority of the pending request. In some cases, the metadata indicates a Multimedia Multicast Service (MBMS) bearer that is used by at least one PTT client of the second group of PTT clients for the second active group call. In block 916, the first PTT server hosts a merged PTT group call in which the first group of PTT clients and the second group of PTT clients participate.

[087] Although the operations are depicted in the drawings in a particular order, the same should not be understood to require that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be employed. Furthermore, the separation of various system components in the implementation described above should not be construed to require such separation in all implementations, and it should be understood that the components and program systems described can generally be integrated together into one software product. signal software or packaged into multiple software products.

[088] Furthermore, techniques, systems, subsystems and methods described and illustrated in the various implementations as distinct or separate may be combined or integrated with other systems, modules, techniques or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicate through some intermediary interface, device or component, whether electrically, mechanically or otherwise. Other examples of changes, substitutions and alterations are verifiable by a person skilled in the art and can be made.

[089] Although the above detailed description has shown, described and pointed out the fundamental innovative features of the disclosure as applied to various implementations, it will be understood that various omissions, substitutions and changes in the form and details of the illustrated system can be made by those skilled in the art. technique. Furthermore, the order of method steps is not implied by the order in which they appear in the claims.

Claims (8)

1. Method characterized by the fact that it comprises: hosting, on a first Press To Talk (PTT) server (102; 204; 202; 212), a first active group call, in which a first group of PTT clients (206) participates in the first active group call; receive, at the first PTT server (204; 202; 212), a request (1; 2) to invite a second group of PTT clients (618), wherein the request (1; 2) includes an identifier for the second group of PTT customers; send (5), from the first PTT server (202) and to a second PTT server (112; 212; 214), a first invitation message (5), wherein the first invitation message includes the identifier for the second group of PTT clients, the second PTT server (212; 214) hosts a second active group call, and the second group of PTT clients participates in the second active group call; receive (9) on the first PTT server (202) from the second PTT server (212; 214), in response to the first invitation message, a response message (6), wherein the response message indicates that the second group of PTT customers participates in the second active group call; and hosting on the first PTT server (204; 202; 212) a fused PTT group call, wherein the first group of PTT clients and the second group of PTT clients participate in the fused PTT group call; the method further comprises sending by the first PTT server a second invitation message (7; 9), wherein the second invitation message invites at least one PTT client from the second group of PTT clients to the merged PTT group call and the second invitation message indicates that the merged PTT group call replaces or suspends the second active group call. 2. Method according to claim 1, characterized by the fact that the second invitation message is sent via a Multimedia Broadcast/Selective Broadcast Service (MBMS) channel. 3. Method, according to claim 1, characterized by the fact that it further comprises: sending a subscription request (15) to the second PTT server; and receiving, in response to the subscription request, a notification message (16; 17), wherein the notification message includes metadata of the second group of PTT clients. 4. The method of claim 3, wherein the metadata indicates a pending request to send media, wherein the pending request is received on the second PTT server before the first invitation message. 5. The method of claim 4, wherein the metadata indicates at least one of a timestamp, a queue position, or a priority of the pending request. 6. Method according to claim 4, characterized by the fact that the metadata indicates a Multimedia Broadcast Service (MBMS) bearer that is used by at least one PTT client of the second group of PTT clients for the second active group call. 7. Device characterized by the fact that it comprises: a memory; and at least one hardware processor communicatively coupled to the memory and configured to perform the method as defined in claims 1 to 6. 8. Tangible non-transitory computer-readable media characterized by the fact that it contains instructions that, when executed on a computing device, cause a computing device to perform operations comprising the method as defined in claims 1 to 6.