Patent Description:
There exists a limitation with respect to bearer resource activation to use bearer resources before waiting for full resource activation to be achieved. This functionality typically may not be achieved by simply using bearer resources without feedback about partial resource establishment. Moreover, there exists a limitation with respect to bearer resource activation of particular nodes and cells within a broadcast area for mission critical communications. This functionality typically may not be achieved simply by activating all resources distributed across the entire broadcast area or by activating multiple bearers among smaller broadcast areas.

<CIT> discloses a resource management database with a listing of preestablished MBMS bearers and an indication of assignment status.

<CIT> discloses pre-establishing a group communication session and activation of an MBMS bearer before call setup.

<CIT> describes dynamic allocation of resources.

The system, method, and apparatus components have been represented where appropriate by suitable symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

Disclosed herein are a method and apparatus, according to the independent claims <NUM> and <NUM>, for communicating resource reservation details.

In one embodiment, a disclosed method of resource activation by a group application server includes requesting, by the group application server, establishment of a distributed resource and an indication of progress to establish the distributed resource, , and receiving a first notification at the group application server. The distributed resource may be requested to be established in a broadcast area. The first notification may be indicative of progress in the establishment of the distributed resource and the first notification may be received before the distributed resource is established in the broadcast area.

In one embodiment, a disclosed group application server for resource activation includes a memory and a processor. The processor is coupled to the memory. The processor may be configured to request establishment of a distributed resource in a broadcast area, and receive a first notification. The request for establishment of the distributed resource may include requesting an indication of progress to establish the distributed resource to be established. The first notification may be indicative of progress in the establishment of the distributed resource and the first notification may be received before the distributed resource is established in the broadcast area.

In at least some embodiments of the present disclosure, the systems, methods, and apparatuses as described herein for communicating resource reservation details may support a notification indicative of progress in the establishment of the distributed resource. Unlike systems, methods, and apparatuses that receive a status indicating that the distributed resource has been established, the systems, methods, and apparatuses as described herein may support receiving a notification indicative of progress in the establishment of the distributed resource after the request is accepted and before the entire distributed resource has been established.

In at least some embodiments of the present disclosure, the systems, methods, and apparatuses as described herein for communicating resource establishment details may support requesting an indication of progress for at least one of: one or more predetermined percentages of the distributed resource being established in the broadcast area and a specified set of one or more cells of one or more nodes in the broadcast area. Unlike systems, methods, and apparatuses that employ a status indicating that all or none of the distributed resource was established or that employ general resource availability in a non-distributed area, such as for a unicast bearer or resource availability within a critical site, the systems, methods, and apparatuses as described herein may support one or more notifications of the establishment of the distributed resource at one or more predetermined percentages or at a specified set of one or more cells of one or more nodes within the broadcast area.

In at least some embodiments of the present disclosure, the systems, methods, and apparatuses as described herein for communicating resource establishment details may support requesting establishment of the distributed resource with a list of supported features. Unlike systems, methods, and apparatuses that employ a list of supported features indicating support for a heartbeat for restoration of communication interfaces, the systems, methods, and apparatuses as described herein may support a list of supported features indicating support for at least one of: a resource activation percentage notification and a critical resource availability notification.

In at least some embodiments of the present disclosure, the systems, methods, and apparatuses as described herein for communicating resource establishment details may support performing one or more actions on a group communication service call. Unlike systems, methods, and apparatuses that employ a status indicating that all or none of the distributed resource was established or that employ general resource availability in a non-distributed area, the systems, methods, and apparatuses as described herein may support based on the first notification indicative of progress in the establishment of the distributed resource to perform one or more actions, including admitting, rejecting, resuming, and suspending a call.

Referring now to <FIG>, there is provided a block diagram illustrating an example communication system <NUM> supporting communication of resource activation details. Communication system <NUM> may include a group application server <NUM> for requesting activation of bearer resources for the transport of data, including but not limited to push-to-talk, voice, data, and video communications. In various embodiments, group application server <NUM> may be implemented as a group communication service application server (GCS-AS), such as a Push-to-Talk (PTT) controller, which may be included in the application level of communication system <NUM>, which may also be referred to as the application domain. Group application server <NUM> may be implemented with processor <NUM> that is coupled to memory <NUM> and network interface <NUM>. Memory <NUM> may store instructions which when executed by processor <NUM> provide for group application server <NUM> operation in system <NUM>. Network interface <NUM> may include one or more network devices coupled to one or more elements of system <NUM>. Although a single processor <NUM> and memory <NUM> are shown, processor <NUM> may include one or more processors and memory <NUM> may include one or more types of memories and one or more memory modules.

Group application server <NUM> may be coupled via interface <NUM> to broadcast multicast service center <NUM> to activate bearer resources for the transport of data. Although one group application server <NUM> is illustrated, communication system <NUM> may include a plurality of group application servers coupled to broadcast multicast service center <NUM>. In various embodiments, broadcast multicast service center <NUM> may be implemented as an eMBMS Broadcast Multicast Service Centre (BM-SC). Broadcast multicast service center <NUM> may provide for the activation, deactivation, and modification of resources for one or more eMBMS bearers. Requests to activate, deactivate, or modify resources for eMBMS bearers sent from group application server <NUM> may be received by broadcast multicast service center <NUM> over interface <NUM>. In various embodiments, interface <NUM> may be implemented as one or more references points or multicast broadcast protocol interfaces, such as an MB2-C (control plane interface) and an MB2-U (user plane interface). Although one broadcast multicast service center <NUM> and one interface <NUM> to group application server <NUM> is illustrated, communication system <NUM> may include a plurality of broadcast multicast service centers <NUM> coupled via a plurality of interfaces <NUM> to group application server <NUM>. In some embodiments, broadcast multicast service center <NUM> may be included in the application level of communication system <NUM>.

Broadcast multicast service center <NUM> may be coupled via interface <NUM> to broadcast multicast service gateway <NUM>. Group application server <NUM> may send data for one or more user equipment <NUM> to broadcast multicast service center <NUM> to be forwarded via interface <NUM> to broadcast multicast service gateway <NUM>. In various embodiments, interface <NUM> may be implemented in accordance with one or more reference points, such as an SGmb and an SGi-mb. Interface <NUM> may be used for sending data to user equipment <NUM>. Control messages, such as messages to activate resources for a bearer, may also be communicated via interface <NUM>. In communication system <NUM>, broadcast multicast service gateway <NUM> may provide for the distribution of broadcast or multicast communication traffic across radio access network <NUM>. In various embodiments, broadcast multicast service gateway <NUM> may be implemented as an eMBMS Broadcast Multicast Service Gateway (MBMS GW).

Group application server <NUM> may be coupled to packet data network gateway (PDN GW) <NUM> via interface <NUM> for unicast communication. In various embodiments, interface <NUM> may be implemented in accordance with one or more reference points or interfaces, such as an SGi and a Rx. PDN GW <NUM> may be coupled to provide one or more policy and filtering operations, including but not limited to policy enforcement and packet filtering, screening, and interception. PDN GW <NUM> may serve as a conduit for non-3GPP communications, such as code-division multiple access (CDMA) communications. PDN GW <NUM> may be coupled to serving gateway (SGW) <NUM> via interface <NUM>. In communication system <NUM>, SGW <NUM> may provide for communication of unicast communication traffic to a particular destination in radio access network <NUM>.

In various embodiments, radio access network <NUM> may be implemented as an evolved universal mobile telecommunications system terrestrial radio access network (E-UTRAN). Radio access network <NUM> may also be referred to as a broadcast area. Radio access network <NUM> may include one or more service areas (<NUM>, <NUM> and <NUM>). In some embodiments, a service area (e.g., service area <NUM>) may overlap in geographic area with another service area (e.g., service area <NUM>). Each service area may be coupled to broadcast multicast service gateway <NUM> via one or more links (<NUM>, <NUM>, and <NUM>) and to SGW <NUM> via one or more links (<NUM>, <NUM>, and <NUM>).

A service area (<NUM>, <NUM>, or <NUM>) may include a plurality of nodes (<NUM>). In various embodiments, a node <NUM> may be implemented as evolved nodeBs (eNodeBs), such as a base transceiver station. Each node <NUM> may provide for communications across a coverage area <NUM>, which may overlap in geographic area with the coverage area of another node. A node <NUM> may include a plurality of cells <NUM>, which may provide for communication to one or more user equipment (UE) <NUM>. A node <NUM> may serve as an intermediary in communications between UE <NUM> and broadcast multicast service gateway <NUM>. UE <NUM> may be a device that receives broadcast multicast communications, such as a vehicle, radio, mobile phone, mobile data terminal, laptop computer, tablet computer, or personal digital assistant (PDA). UE <NUM> may be communicatively coupled to one or more cells in one or more nodes. Although three service areas each with seven coverage areas are shown, any number of services areas with any plurality of coverage areas may be used in radio access network <NUM>.

Group application server <NUM> may request the activation of a distributed resource from broadcast multicast service center <NUM>. The request may reserve resources to be activated for an eMBMS bearer of communications. The distributed resource may be an eMBMS Bearer in an LTE network. The request may include a list of features supported by group application server <NUM>. For example, the list may indicate that group application server <NUM> supports a resource activation percentage notification. Group application server <NUM> may provide one or more distributed resource activation thresholds, such as <NUM>, <NUM>, and <NUM> percent activation thresholds, in the request to activate the distributed resource. Although three resource activation thresholds are described, any suitable number of thresholds may be provided by group application server <NUM>.

As another example, the list may indicate that group application server <NUM> supports a critical resource availability notification. Group application server <NUM> may provide an indication of which distributed resources in radio access network <NUM> may be necessary for mission critical communications. The indication may specify a set of one or more cells in a geographic area or a set of one or more cells in one or more nodes that is in a service area. Skilled artisans will appreciate that the cells and nodes may be selected based on a particular mission critical communication, including but not limited to the selection of one or more nodes in the central portion of the service area.

In response to the request to activate the distributed resource, the broadcast multicast service center <NUM> may send an acceptance of the request to group application server <NUM> and start activating resources. Broadcast multicast service center <NUM> may determine which notifications to provide to group application server <NUM> based on the list of features supported by group application server <NUM>. For example, group application server <NUM> may support a resource activation percentage notification with three resource activation thresholds corresponding to <NUM>, <NUM> and <NUM> percent of the resource being established. In response, broadcast multicast service center <NUM> may send a notification about the establishment of the distributed resource for each of the three resource activation thresholds. The notification may indicate which resource activation threshold has been satisfied. As another example, group application server <NUM> may support a critical resource availability notification specifying that one or more cells in one or more nodes of a service area be activated for mission critical communications. In response, broadcast multicast service center <NUM> may send a notification to group application server <NUM> indicating whether the activation of the specific resources requested was successful.

In response to a notification from broadcast multicast service center <NUM>, group application server <NUM> may evaluate whether sufficient resources are established for a group communication service call. The group communication service call may have a pending or active status, which may indicate one or more characteristics of the group communication service call, including, but not limited to, whether the group communication service call is a confirmed or unconfirmed type of call, an emergency type of call or non-emergency type of group call, and whether the group communication service call has a high priority or low priority. Sufficient resources for a group communication service call may be determined based on any suitable criteria including whether the group communication service call is confirmed, whether the group communication service call is an emergency communication, the priority assigned to the group communication service call, and whether the group communication service call is waiting on an eMBMS bearer or is using an eMBMS bearer. Group application server <NUM> may perform one or more actions based on the evaluation, including but not limited to admitting a group communication service call, rejecting a group communication service call, resuming a group communication service call, suspending or holding a group communication service call, or queuing a group communication service call. For example, a confirmed group communication service call may require a higher percentage of resources to be activated before the call is admitted than an unconfirmed group communication service call. As another example, an emergency group communication service call may require all resources be activated before the call is admitted.

Skilled artisans will appreciate that resource establishment as described herein may be used to activate new resources, deactivate existing resources, and modify existing resources to increase, decrease, or change the establishment of distributed resources.

Referring now to <FIG> and <FIG>, there is provided a flow diagram illustrating communication of resource establishment details in an example communication system <NUM> designed in accordance with some embodiments. Communication system <NUM> may include group application server <NUM> and broadcast multicast service center <NUM>. Group application server <NUM> may request the establishment of distributed resource <NUM> in one or more radio access networks from broadcast multicast service center <NUM>. In some embodiments, request <NUM> is a resource establishment request in a 3GPP group communication action-request (GAR) command that may be sent to one of a plurality of broadcast multicast service centers (<NUM>). Request <NUM> may include a request for broadcast multicast service center <NUM> to provide notification of partial resource activation. Group application server <NUM> may include in request <NUM> a request for an indication of progress when the distributed resource is being established. In some embodiments, the request for an indication may be provided by an attribute-value pair in request <NUM>. Group application server <NUM> may include a supported feature list in request <NUM>. The supported feature list may indicate support for one of more notification features, including but not limited to a resource activation percentage notification and a critical resource availability notification. Skilled artisans will appreciate that request <NUM> may include one or more requests for one or more eMBMS bearers to be established.

In some embodiments, group application server <NUM> may indicate support for a resource activation percentage notification. Group application server <NUM> may provide one or more resource activation thresholds, up to a maximum number of resource activation thresholds, to broadcast multicast service center <NUM>. Broadcast multicast service center <NUM> may notify group application server <NUM> of partial resource establishment when the activation of the distributed resources reaches or exceeds a resource activation threshold. In some embodiments, group application server <NUM> may indicate support for a critical resource availability notification. Group application server <NUM> may specify which portions of the distributed resource in the radio access network are suitable for mission critical communications. Group application server <NUM> may select distributed resources at a fine-grain level within a broadcast area by specifying a set of one or more cells in a geographic area or a set of one or more cells in one or more nodes in a service area.

In response to request <NUM>, broadcast multicast service center <NUM> may start distributed resource activation <NUM> and may send acceptance of the request <NUM>. In some embodiments, acceptance of the request <NUM> is a resource establishment acknowledgement in a 3GPP group communication action-answer (GAA) command. The acceptance may indicate the duration for which the distributed resource for the eMBMS bearer will be reserved.

After distributed resource activation starts (<NUM>), broadcast multicast service center <NUM> may determine whether to notify group application server <NUM> (<NUM>) based on the amount of resources that have been established. The determination may be based on the list of features supported by group application server <NUM>. For example, group application server <NUM> may support a resource activation percentage notification. Broadcast multicast service center <NUM> may determine whether the established resources satisfy a resource activation threshold predetermined by group application server <NUM>. After a predetermined resource activation threshold is reached or exceeded, broadcast multicast service center <NUM> may determine that notification of partial resource establishment is required. As another example, group application server <NUM> may a support critical resource availability notification. Broadcast multicast service center <NUM> may determine whether the established resources match the resources specified in a request by group application server <NUM>. When the established resources match the specified resources, broadcast multicast service center <NUM> may determine that notification of critical resource activation is required. Skilled artisans will appreciate that broadcast multicast service center <NUM> may determine that the resources specified in a request by group application service <NUM> may be unavailable for activation.

After broadcast multicast service center <NUM> determines that notification is required, broadcast multicast service center <NUM> may send a notification about the establishment of the distributed resource (<NUM>). In some embodiments, notification <NUM> may be received in a message that is a 3GPP group communication service notification-request (GNR) command. Notification (<NUM>) may specify one or more indications including, but not limited to, whether a resource activation threshold satisfied by the establishment of the distributed resource or whether the activation of critical resources was successful. Skilled artisans will appreciate that the notification may include a suitable indication of the resource activation threshold, including but not limited to whether a specified resource activation threshold is exceeded and the specific percentage of resources established. In some embodiments, acceptance of request <NUM> and notification <NUM> may be sent in the same communication. For example, the request may be accepted and a notification may be provided to indicate that little or no resources (e.g., <NUM>%) have been established.

Group application server <NUM> receives the notification and then determines that an action on a group communication service call should be performed based on an evaluation of whether the notification corresponds to sufficient resources for the group communication service call (<NUM>). The group communication service call may have a pending or active status, which may indicate one or more characteristics of the group communication service call, including, but not limited to, whether the group communication service call is a confirmed or unconfirmed type of call, an emergency type of call or non-emergency type of group call, and whether the group communication service call has a high priority or low priority. Sufficient resources for a group communication service call may be determined based on any suitable criteria including whether the group communication service call is confirmed, whether the group communication service call is an emergency communication, the priority assigned to the group communication service call, and whether the group communication service call is waiting on an eMBMS bearer or is using an eMBMS bearer. Group application server <NUM> may perform one or more actions based on the evaluation, including but not limited to admitting a group communication service call, rejecting a group communication service call, resuming a group communication service call, suspending or holding a group communication service call, or queuing a group communication service call. For example, group application server <NUM> may admit a group communication service call with a low priority based on an evaluation that the notification corresponds to a low percentage of the distributed resource having been established.

After sending a notification to group application server <NUM> about the establishment of the distributed resource (<NUM>), broadcast multicast service center <NUM> may determine that another notification is required (<NUM>). The determination may be similar to the previous determination (<NUM>) performed by broadcast multicast service center <NUM>. Broadcast multicast service center <NUM> may send another notification to group application server <NUM> about the establishment of the distributed resource (<NUM>). In some embodiments, the notification <NUM> may be received in a message that is a 3GPP group communication service notification-request (GNR) command. Notification <NUM> may indicate that another resource activation threshold has been satisfied by partial resource activation. In response, group application server <NUM> may determine that another action is to be performed on a group communication service call (<NUM>). When all of the distributed resource is activated (<NUM>), broadcast multicast service center <NUM> may send a status to group application server <NUM> indicating that the distributed resource has been fully established (<NUM>). In some embodiments, the status may be received in a message that is a 3GPP group communication service notification-request (GNR) command.

Skilled artisans will appreciate that broadcast multicast service center <NUM> may continue to send notifications to group application server <NUM> after all of the distributed resource is activated based on whether failures or errors result in the percentage of activated resources to be reduced or the critical resources no longer being available.

Referring now to <FIG>, there is provided a flow diagram illustrating a method <NUM> for resource activation by communication of resource establishment details shown in accordance with some embodiments. While a particular order of operations is indicated in <FIG> for illustrative purposes, the timing and ordering of such operations may vary where appropriate without negating the purpose and advantages of the examples set forth in detail throughout the remainder of this disclosure. In some embodiments, one or more portions of method <NUM> may be executed at some predetermined periodic time period thereafter, in response to an activation, deactivation, or modification of distributed resources. For example, the request to establish the distributed resource may be modified before all of the distributed resource is established.

In this example embodiment, method <NUM> begins with block <NUM> in <FIG> and continues to block <NUM>, where establishment of a distributed resource in a broadcast area and an indication of progress to establish the distributed resource is requested. The distributed resource may be for a bearer that may be assigned to a group communication service call. Group application server <NUM> may send the request (<NUM>) to broadcast multicast service center <NUM> as described for <FIG>. The broadcast area may correspond to one or more service areas in a radio access network, such as service area <NUM> in radio access network <NUM> as described for <FIG>. In some embodiments, the request to indicate progress in establishing the distributed resource may be provided by an attribute-value pair. The indication of progress to establish the distributed resource may be requested in a resource establishment request, which may be a 3GPP group communication action-request (GAR) command for one or more broadcast areas. The request may include a list of supported features. The features supported by group application server <NUM> may include support for one or more features, such as a resource activation percentage notification and a critical resource availability notification. The indication of progress may be requested for one or more predetermined percentages, such as <NUM> and <NUM> percent of the requested distributed resource. Group application server <NUM> may support a critical resource availability notification and the indication of progress may be requested for a specified set of one or more cells of one or more nodes in the broadcast area. For example, cells <NUM> of a node <NUM> in service area <NUM> may be specified as described for <FIG>.

At block <NUM>, a first notification indicative of progress in the establishment of the distributed resource may be received. For example, group application server <NUM> may receive the notification (<NUM>) from broadcast multicast service center <NUM> as described for <FIG>. The first notification may be received after the acceptance of the request or in the same communication as the acceptance of the request. In some embodiments, the first notification may be received in a message that is a 3GPP group communication service notification-request (GNR) command. The first notification may specify that a predetermined resource activation threshold is satisfied or whether the activation of the critical resource was successful. The predetermined resource activation threshold may have been specified at block <NUM> in the request for the establishment of distributed resources. The request may have specified one or more resource activation thresholds at which a notification will be sent to indicate partial establishment of the distributed resource. In some embodiments, the first notification may indicate whether the predetermined resource activation threshold has been reached. At block <NUM>, all distributed resources may be activated as requested after the first notification is received.

Referring now to <FIG>, there is provided a flow diagram illustrating a method <NUM> for using partial resource establishment shown in accordance with some embodiments. While a particular order of operations is indicated in <FIG> for illustrative purposes, the timing and ordering of such operations may vary where appropriate without negating the purpose and advantages of the examples set forth in detail throughout the remainder of this disclosure. In some embodiments, one or more portions of method <NUM> may be executed at some predetermined periodic time period thereafter, in response to a change in established distributed resources. For example, an additional portion of the distributed resource may be established in excess of a predetermined threshold or a failure in a portion of the distributed resource may result in a critical resource requirement no longer being satisfied.

In this example embodiment, method <NUM> begins with block <NUM> in <FIG> and continues to block <NUM>, where establishment of a distributed resource in a broadcast area and an indication of progress to establish the distributed resource is requested as described for block <NUM> in <FIG>. At block <NUM>, an acceptance of the request to establish the distributed resource may be received. For example, group application server <NUM> may receive the acceptance (<NUM>) from broadcast multicast service center <NUM> as described for <FIG>. Acceptance of the request may indicate the broadcast multicast service center <NUM> has begun activation of the requested distributed resource. In some embodiments, the acceptance may be a resource establishment acknowledgement in a 3GPP group communication action-answer (GAA) command. At block <NUM>, a first notification indicative of progress in the establishment of the distributed resource may be received, as described for block <NUM> in <FIG>.

At block <NUM>, in which one or more actions on a group communication service call may be performed based on the first notification. For example, group application server <NUM> may perform the actions (<NUM>) as described for <FIG>. Group application server <NUM> may determine that actions on the group communication service call should be performed based on an evaluation of whether the notification corresponds to sufficient resources for the group communication service call. The group communication service call may have a pending or active status, which may indicate one or more characteristics of the group communication service call, including, but not limited to, whether the group communication service call is a confirmed or unconfirmed type of call, an emergency type of call or non-emergency type of group call, and whether the group communication service call has a high priority or low priority. Sufficient resources for a group communication service call may be determined based on any suitable criteria including whether the group communication service call is confirmed, whether the group communication service call is an emergency communication, the priority assigned to the group communication service call, and whether the group communication service call is waiting on an eMBMS bearer or is using an eMBMS bearer. Group application server may perform one or more actions based on the evaluation, including but not limited to admitting a group communication service call, rejecting a group communication service call, resuming a group communication service call, suspending or holding a group communication service call, or queuing a group communication service call. For example, group application server <NUM> may admit a group communication service call with a low priority based on an evaluation that the first notification corresponds to a low percentage of the distributed resource being established.

At block <NUM>, a second notification indicative of progress in the establishment of the distributed resource may be received. The second notification may be received after the first notification. For example, the second notification may be received by group application server <NUM> as described by notification <NUM> for <FIG>. As described for block <NUM> in <FIG> and <FIG>, the second notification may be received in a message that is a 3GPP group communication service notification-request (GNR) command. The second notification may specify that a second predetermined resource activation threshold is satisfied. Group application server <NUM> may determine another action to be performed on a group communication service call based on receiving the second notification. For example, group application server <NUM> may suspend a group communication service call with a low priority and admit another group communication service call with a high priority based on an evaluation that the second notification corresponds to a high percentage of the distributed resource being established.

At block <NUM>, all distributed resources may be activated as described for block <NUM> in <FIG>. At block <NUM>, a status indicating that the distributed resource has been established may be received. For example, the status may be sent by broadcast multicast service center <NUM> to group application server <NUM> as described for <FIG>. In some embodiments, the status may be received in a message that is a 3GPP group communication service notification-request (GNR) command. The status may be sent by the broadcast multicast service center after all of the distributed resource is activated.

However, one of ordinary skill in the art appreciates that various modifications and changes may be made without departing from the scope of the invention as set forth in the claims below.

The invention is defined solely by the appended claims.

Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has", "having," "includes", "including," "contains", "containing" or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises. a", "includes. a", "contains. a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially", "essentially", "approximately", "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within <NUM>%, in another embodiment within <NUM>%, in another embodiment within <NUM>% and in another embodiment within <NUM>%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed when falling within the scope of the appended claims.

It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or "processing devices") such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the system, method, or apparatus described herein.

Claim 1:
A method of resource activation by a group application server (<NUM>, <NUM>) including:
requesting, by the group application server (<NUM>, <NUM>):
establishment of a distributed resource, the distributed resource to be established in a broadcast area; and
an indication of progress to establish the distributed resource;
the method being characterized in:
receiving a first notification (<NUM>) at the group application server (<NUM>, <NUM>) in response to requesting the establishment of the distributed resource and the indication of progress,
wherein:
the first notification is indicative of progress in the establishment of the distributed resource; and
the first notification is received before the distributed resource is established in the broadcast area;
determining that an action on a group communication service call should be performed based on an evaluation of whether the first notification corresponds to sufficient resources for the group communication service call (<NUM>).