Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 43.068  Word version:  16.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2.3…   5…   11…

 

4.2.3  Leaving of a group call without termination

A service subscriber can leave the voice group call at any point by "deselecting" it via an MMI function. Having deselected the voice group call the mobile station returns to idle mode and "ignores" any further notification messages related to that voice group call.
The service subscriber shall have the capability to reselect the voice group call. The mobile station shall not ignore notification messages to that call any more.
The dispatcher shall be able to leave a voice group call without terminating it.
Up

4.2.4  Group call termination

A voice group call can only be terminated by the calling service subscriber, by calling dispatcher, by an entitled dispatcher or due to no activity timer expiry (see subclause 8.1.2.3 and subclause 11.3.2.3).
The calling service subscriber can terminate the call only if he has access to the uplink. He shall remain the calling service subscriber during the length of the particular voice group call even if he leaves the call and then returns to it later.
An entitled dispatcher can terminate the call at any time by using a network-defined user operation (via DTMF or the signalling option specified in ETSI TS 103 389 [19]).
Up

4.2.5  Acknowledgements

The acknowledgement is an application option.
For voice group calls which are identified by an acknowledgement flag mobile stations which have acknowledgement facilities have to return an acknowledgement message with a predefined content in a predefined manner.
The acknowledgement shall be sent using an appropriate data service, to a predefined address or with a predefined short code stored on the SIM/USIM card. The network may apply geographical routing to a predefined acknowledgement service centre.
Up

4.2.6  Transactions between the mobile station and the network

Mobile stations which are in group receive mode may support the reception of short messages to voice group calls, but shall not perform any other transactions with the network while adjusted to the voice group call channel. They shall leave the group receive mode and act in a standard way to perform any transaction if necessary and return to the voice group call afterwards.
Mobile stations which have access to the voice group call channel uplink shall not perform any transactions for supplementary services, but may support the transmission and reception of short messages as specified in subclause 11.3.9.
Up

4.2.7  Processing of originator-to-dispatcher informationWord‑p. 16

The calling service subscriber may include originator-to-dispatcher information during call setup. If the originating MSC supports processing of originator-to-dispatcher information, it transforms the received originator-to-dispatcher information into UUS1, and sends it:
  • if the originating MSC is not the voice group call anchor MSC: to the voice group call anchor MSC;
  • if the originating MSC is the voice group call anchor MSC: to the dispatchers to be attached to the group call during call setup of the connections to these dispatchers.
The anchor MSC receiving UUS1 in a voice group call setup from an originating relay MSC forwards this UUS1 to the dispatchers to be attached to the group call during call setup of the connections to these dispatchers.
Transformation of originator-to-dispatcher information: Originator-to-dispatcher information can be compressed or uncompressed.
  • Decompression of compressed originator-to-dispatcher information is specified in TS 44.068.
  • The transformation of uncompressed originator-to-dispatcher information into UUS1 is the UUS1 containing the same user-user IE as the originator-to-dispatcher information.
  • The transformation of compressed originator-to-dispatcher information into UUS1 is the UUS1 resulting from transforming the decompressed originator-to-dispatcher information into UUS1.
Up

4.2.8  Transfer of application-specific data to group call members |R8|

4.2.8.1  General

Mobile stations may support the transmission of application-specific data to other group call members or VGCS applications in the network, and the reception of application-specific data from other group call members or VGCS applications in the network during an ongoing voice group call, in parallel to the voice conversation.
Service subscribers can request the transmission of application-specific data while they are talker or listener.
A mobile station supporting the transmission of application-specific data shall check with the USIM whether the subscriber is allowed to transmit application-specific data for the respective group ID before starting the signalling procedures specified in subsclause 4.2.8.
The procedure specified in the following subclauses supports the transfer of application-specific data.
The same procedure can also be used by the receiver of application-specific data to confirm the reception of application-specific data.
The support of the transfer of application-specific data by the network is an operator option.
The exact format of the application-specific data is out of scope of the 3GPP specifications. If roaming service subscribers from other PLMNs are to be the supported or if a group call area includes cells from more than one PLMN, the use of application-specific data requires coordination between the operators.
Up

4.2.8.2  Sending of application-specific dataWord‑p. 17

4.2.8.2.1  By the talking service subscriber
When application-specific data is to be sent and the talking subscriber is allowed to transmit application-specific data for the respective group ID, the mobile station of the talking service subscriber shall send a DATA INDICATION (Application_Data) message to the network on the uplink of the dedicated channel or group call channel. On receipt of the application-specific data, the network shall transmit these data to the other group call members as specified in subclause 4.2.8.4.
Up
4.2.8.2.2  By a listener
When application-specific data is to be sent and the network indicates the uplink as free, the listener shall use the group call channel uplink for the signalling as specified in item a) below.
Otherwise, when the network does not indicate the uplink as free, the channel to be used by the listener is indicated by the network in the "uplink access indication" IE sent in periodic transmissions of the UPLINK BUSY message. If the talking service subscriber uses the group call channel uplink in the current cell, the RACH shall be used, see item b) below; otherwise the group call channel uplink shall be used, see item a) below.
a)
Sending application-specific data via the group call channel uplink
When application-specific data is to be sent and the listener is allowed to transmit application-specific data for the respective group ID, the mobile station of the listener shall send an UPLINK ACCESS message with an appropriate establishment cause ("UL request for sending application-specific data") on the group call channel uplink to the BSS.
It is an operator option whether the BSS treats an UPLINK ACCESS message with establishment cause "UL request for sending application-specific data" with higher or lower priority than UPLINK ACCESS messages with any other establishment cause. The same order of priorities applies to all voice group calls in a network.If the BSS grants the uplink of the group call channel, then the MS sends a SABM (DATA INDICATION) message with its mobile identity and the application data to the network. The serving BSS responds with a UA (DATA INDICATION) message and releases the group call channel uplink. The MS returns to group receive mode.
On receipt of the DATA INDICATION message, the BSC shall add the cell identifier of the cell where the application data were sent from and passes the L3 information by sending the UPLINK APPLICATION DATA message to the MSC.
On receipt the UPLINK APPLICATION DATA message, the MSC shall distribute the data to all members of the group call (see subclause 4.2.8.4).
b)
Sending application-specific data via the RACH
When application-specific data is to be sent and the listener is allowed to transmit application-specific data for the respective group ID, the mobile station of the listener shall leave the group call and send a CHANNEL REQUEST message with an appropriate establishment cause on the RACH to the BSS in order to request an SDCCH. When a new layer 2 connection is established on a SDCCH channel the data can be sent by the mobile station to the network with the DATA INDICATION 2 message on the main DCCH (figure 7j).
In order to indicate to the network which group call the application-specific data is addressed to, the DATA INDICATION 2 message shall include the group call reference.
On receipt of the DATA INDICATION 2 message the BSC shall add the cell identifier of the cell from which the application data was sent and pass the L3 information in the UPLINK APPLICATION DATA message to the MSC.
On receipt of the UPLINK APPLICATION DATA message, the MSC shall distribute the data to all members of the group call (see subclause 4.2.8.4).
Up

4.2.8.3  Sending a confirmation of receipt of application-specific dataWord‑p. 18

On receiving application-specific data, any service subscriber can send a confirmation to the network which will send the confirmation to the ongoing group call.
For the purpose of identifying the received data, the confirmation shall include the data_id which was received in the message that contained the application data that is being confirmed.
The further proceeding is as described in 4.2.8.2.1 and 4.2.8.2.2 (see also figure 7i).

4.2.8.4  Distributing application-specific data to a voice group call

4.2.8.4.1  Distribution via the MSC
On receipt of the UPLINK APPLICATION DATA, the MSC shall check if the sending subscriber has a subscription to the group ID. If yes, the MSC shall distribute the application-specific data dependent on the distribution parameter included in the DATA INDICATION or DATA INDICATION 2 message; otherwise the MSC shall discard the UPLINK APPLICATION DATA message.
Without a RANflex configuration, the MSC can perform this check locally with its own VLR. In a RANflex configuration with or without group call redundancy, if the group call serving MSC receives an UPLINK APPLICATION DATA message it shall check by analysing the NRI of the requesting subscriber's TMSI whether it is the requesting subscriber's VMSC. If it is not, the group call serving MSC shall retrieve the IMSI and information about subscribed talker priorities from the VLR of the VMSC by means of the MAP service SEND_GROUP_CALL_INFO. During this MAP operation the VMSC shall check the subscription for the group ID.
If the application-specific data are to be sent to the listeners and the talking service subscriber, the MSC shall proceed as follows:
If the MSC is the anchor MSC, it shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message NOTIFICATION DATA and distribute the message towards all relay MSCs and all BSSs in its MSC area involved in the group call (figure 7f). If the MSC receives an indication from the originating BSC that the application-specific data were immediately distributed to the originating BSS area (see subclause 4.2.8.4.2), the MSC shall not send the BSSMAP message NOTIFICATION DATA to the originating BSS.
If the MSC is a relay MSC, it shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message NOTIFICATION DATA and distribute the message to the anchor MSC and all BSSs of the relay MSC area. If the MSC receives an indication from the originating BSC that the application-specific data were immediately distributed to the originating BSS area (see subclause 4.2.8.4.2), the MSC shall not send the BSSMAP message NOTIFICATION DATA to the originating BSS. On receiving the NOTIFICATION DATA message from the relay MSC, the anchor MSC shall send the message towards all BSSs in its MSC area involved in the group call and to all relay MSCs except the relay MSC from which the NOTIFICATION DATA was received (figure 7h). The BSS shall broadcast the notification data to all listeners and talking service subscriber in the NOTIFICATION APPLICATION DATA message on the FACCH.
The network may repeat the NOTIFY APPLICATION DATA message for application-specific data on the group call channel downlink. If a mobile station receives the NOTIFY APPLICATION DATA message more than once, it shall deliver only the first received message to its local application and discard any received repetitions of the message.
The mechanism how the mobile station detects a repetition of the NOTIFY APPLICATION DATA message is application- specific.
Up
4.2.8.4.2  Immediate distribution by the BSCWord‑p. 19
As a network option, on receipt of application-specific data from the MS, the BSS may distribute the application-specific data immediately to the cells within the BSC area belonging to the group call area, if the distribution parameter included in the DATA INDICATION message or DATA INDICATION 2 message indicates that the application-specific data are to be sent to the service subscribers. In addition, the BSC shall send the application-specific data to the MSC with an indication that the application-specific data were already distributed to the originating BSC area.
When this network option is used, the BSS cannot include the mobile subscriber's MSISDN in the NOTIFY APPLICATION DATA message broadcast immediately to the cells within the BSC area. Furthermore, the BSS cannot check if the sending subscriber has a subscription for the group ID.
If the network option of immediate distribution of application-specific data by the BSS is activated, then during the establishment phase of the voice group call the BSC shall store the cell identities of the cells belonging to the group call area and served by the BSC.
Up

Up   Top   ToC