Content for  TS 23.280  Word version:  19.2.0

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2……   9.3…   10…   10.1.2…   10.1.3………   10.1.5…   10.1.6…   10.2…   10.2.3………   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3……………   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3………………………   10.10……   10.10.2…   10.10.3………   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.16…   10.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3……   11.5.4…   A…   B…   C…


10.12  Priority Management |R15|p. 260

10.12.1  Generalp. 260

Mission critical priority and QoS management is situational. The MC Services provides a real-time priority and QoS experience for the MC users, who have significant dynamic operational requirements that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the LTE system.
Priority treatment applies on both application layer as well as on transport layer. The details on how the priority level is evaluated and used is outside the scope of this specification. What is specified is the necessary mechanisms to apply the priority and QoS and map different priority parameters between different entities, for example to map application layer priority to transport layer priority.
One of the requirements for MC communication services is to coordinate the use of priority levels between the different MC service servers. This priority coordination is used to mitigate and manage the risk for network congestion situations.

10.12.2  Information flowsp. 260  MC priority requestp. 260

Table describes the information flow MC priority request from one MC service server to an MC service server taking the priority arbitration role.
Information element Status Description
PriorityMRequested priority
Priority areaMThe geographical area for which the requested priority is required.
Type of serviceOThe MC service type e.g. MCVideo, MCPTT or MCData

10.12.3  Procedure for priority coordination between multiple MC service serversp. 261

In deployment scenarios with multiple MC service servers of different or the same type it is required to coordinate the priorities used by the different servers. The procedure defined below provides the necessary coordination between MC service servers to manage high priority levels. One of the involved MC service servers is assigned the role of being a priority arbitrator among a group of MC service servers serving the same geographical area. The priority arbitrator may also compete for the same limited network resources. Prior to using this procedure all MC service servers need to be configured with information about which MC service server will act as the priority arbitrator and under what conditions (e.g. priority level) the priority arbitrator should be used. The use of this procedure is not mandated. MC systems that support priority coordination between multiple MC service servers should support this procedure.
  1. One of the MC service servers is assigned the role of the priority arbitrator.
  2. It is assumed that all MC service servers are part of the same trusted domain.
  3. A MC communication session is ongoing or is about to commence. The operational situation together with static and dynamic attributes requires the use of elevated priority for network resources.
Reproduction of 3GPP TS 23.280, Fig. 10.12.3-1: Priority arbitration between multiple MC service servers
Step 1.
A need for high priority level is identified by the MC service server 1. The priority level identified is above the level of priority that the MC service server 1 can utilise without centralized priority arbitration.
Step 2.
The MC service server 1 sends a MC priority request to the MC service server being assigned the priority arbitrator role. The request includes the geographical area, duration, the priority level, service type and needed capacity.
Step 3.
The priority arbitrator determines whether to grant, reject or queue the request for elevated priority.
Step 4.
The priority arbitrator grants MC service server 1 the elevated priority
Step 5.
The priority arbitrator notifies other MC service servers about the elevated priority granted to other services.
Step 6.
The MC service server utilizes the elevated priority when requesting resources for new or existing MC service communication.
Step 7a-c.
A priority notification may be sent to the MC service clients in the geographical area in which the priority was granted. Messages to MC service clients need to be sent from the MC service server serving each MC user. This message is preferably sent over a multicast bearer.
Step 8.
The MC service server 1 identifies that the elevated priority is not needed.
Step 9.
The requested MC Priority is released from the MC service server 1.
Step 10.
The MC service server 2 (priority arbitrator) informs other MC servers that the elevated priority is released.

Up   Top   ToC