Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.2.0

Top   Top   Up   Prev   None
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

C  Application Priority |R17|p. 377

C.1  Use of application prioritiesp. 377

Different communications between two or more MC service users need to be distinguished in their urgency in order to appropriately or less preferably allocate 3GPP system transport resources. Also simultaneous incoming communications to a MC service user requires an indication of the urgency in order to preferentially join the communication in accordance with the urgency.
To make this distinction of urgencies, the MC system necessarily supports different types of priorities and corresponding levels within each priority category representing the relative importance of a request at the application level. The use of application priority allows the MC system to decide whether a communication establishment or modification request can be accepted or needs to be rejected (e.g. in case of transport resource limitations), or it allows the MC service client to rank simultaneous incoming communication for presentation to an MC service user. Hence the application priority can also be used to decide which existing transport resources (e.g. bearers) to pre-empt during resource limitations. Such pre-emption capability information defines whether a communication can obtain transport resources that were already assigned to another communication with a lower priority level. The pre-emption vulnerability information defines whether a communication can lose the resources assigned to it in order to admit a communication with higher priority level.
The following types of application priorities are provided by the MC system:
Reproduction of 3GPP TS 23.280, Fig. C.1-1: Types of application priorities in the MC system
Up
Communication priority involves a combination of the type of call/communication, the role of the requesting MC service user, and the predefined/requested priority of the initiating MC service user and/or group.
Presentation priority involves the determination of which communications, from within multiple simultaneous possible, are the highest priority to present to the MC service user either audibly or visibly. An example would be a private call received at the same time as an emergency call on a monitored group. This category can be configured uniquely for each MC service user.
Floor priority involves the determination of who can transmit within a communication at a particular time. This is essentially the priority of the MC service user according to its profile, and possibly modified by its role and/or mode of service (e.g. using emergency or imminent peril call). This category is used, for example, to determine the ordering of the floor control queue within an established communication.
Up

D  Consideration MC gateway UE selection |R18|p. 379

D.1  Generalp. 379

Operating conditions can influence the selection and the use of the MC gateway UE and its response/decision on providing an MC client connection to the MC server. Potential conditions should be verified by the MC gateway UE when sending connection notification, and upon reception of the connection authorization response.
Such status information can be considered by the MC client either to associate with another MC gateway UE (e.g. with better operating conditions for the requested service), or to re-associate to the same MC gateway UE (e.g. reattempt association after a certain time).
Up

D.2  Potential Conditionsp. 379

Possible operating conditions information could belong to one of the following categories:
MC gateway UE capacity limits
The MC gateway UE might not be able to allow MC clients to associate when the limit of connected MC clients has been reached.
3GPP access congestion
The MC gateway UE can make use of to the special Categories/Access Identity, the preferential access applies based on its assigned Access Control Class/Access Identity during periods of congestion. The MC gateway UE subscription allows to obtain priority treatment for the required communication.
Nevertheless, the serving access network can indicate to the UEs (including MC gateway UE) that Access Class Barring applies and this can passed by the MC gateway UE to the associated MC client.
PLMN reselection and migration
Depending on operator policy, roaming agreements, and on national/regional regulatory requirements MC gateway UE disassociation and re-association with the corresponding MC server are necessary (e.g. to handle the IP connectivity, QoS, etc.).
Network status information
If the network status information of an EPS/5GS capability available at MC gateway UE, it can be further propagated to the corresponding associated MC clients for further processing (e.g. if the requested QoS for service can be provided for MC client or not).
Up

$  Change historyp. 380


Up   Top