This Annex provides informative call flows for how a GCS AS can use the Unicast Delivery and MBMS Delivery mechanisms defined in this specification to deliver data to group(s) of users.
In this scenario, the GCS AS pre-establishes MBMS bearer(s) in certain pre-configured areas before the start of the group communication session. When a UE originates a request for group communication for one of these areas, the pre-established MBMS bearer(s) is used for the DL traffic.
The GCS AS pre-establishes the MBMS bearers for the group communication session according to the procedures defined in clause 5.1.2.3.1. The BM-SC returns the MBMS service description associated with the MBMS bearer(s) to the GCS AS.
The UE establishes a group communication session with the GCS AS. The GCS AS passes the service description associated with the MBMS bearer service to the UE. The UE obtains the TMGI(s), identifying the MBMS bearer (s), from the service description.
In this scenario, the GCS AS uses a unicast bearer for communication with the UE on the DL at the start of the group communication session. When the GCS AS decides to use an MBMS bearer for the DL data, the GCS AS establishes one using the procedures defined in clause 5.1.2.3.1. The GCS AS provides the service description associated with MBMS bearer(s), obtained from the BM-SC, to the UE. The UE starts using the MBMS bearer(s) to receive DL data and stops using the unicast bearer for the DL data.
The GCS AS establishes the MBMS bearer(s) for the group communication session according to the procedures defined in clause 5.1.2.3.1. The BM-SC returns the service description associated with the MBMS bearer(s) to the GCS AS.