Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.1.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.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…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C… 
10.11.5 Request for resources with shared priority  10.11.6 Request for media resources from MC service server 
...

 

10.11.5  Request for resources with shared priority  p. 259

10.11.5.1  General  p. 259

An MC service server that supports simultaneous sessions may need to share a common priority on the EPS bearer for several MC service group calls that may use different priorities on the application level. This is achieved by including information for priority sharing on the request of resources over Rx reference point to PCRF. All sessions associated with the same priority sharing information will be handled by one EPS bearer, which will have a priority based on the highest requested priority among the sessions.
The use of the procedure defined in subclause 10.11.5.2 is dependent on operator policy.
Up

10.11.5.2  Procedure  p. 259

Pre-conditions:
  • All previous resource requests from the MC service have included a priority sharing information.
Reproduction of 3GPP TS 23.280, Fig. 10.11.5.2-1: Resource request including priority sharing information
Figure 10.11.5.2-1: Resource request including priority sharing information
Up
Step 1.
The MC service server decides based on a request from the MC service client that the priority of an ongoing call must be adjusted.
Step 2.
The MC service server requests a session update to the SIP core. This request will contain information of priority sharing.
Step 3.
PCC update procedures (as defined in TS 23.203) initiated from SIP core local inbound/outbound proxy over Rx. PCC updates the bearer priority for the bearer that contains the SDFs associated with the same priority sharing information. The priority is set to highest priority (lowest ARP) among those SDFs. No additional bearer is created. Also, the default bearer priority is updated accordingly.
Step 4.
The session update is forwarded to the MC service client.
Up

10.11.6  Request for media resources from MC service server  p. 260

10.11.6.1  General  p. 260

The procedure in this sub clause specify how request for resource for floor control (or transmission control in MCVideo and MCData) and for the media plane can be handled independently. This procedure utilizes the Rx reference point both between from the MC service server to the PCRF and from the SIP core to the PCRF.
Resource for the transmission control is requested at session establishment, in this case the IMS standard procedures as specified in TS 23.228 are used. The session description shall in this procedure include bandwidth information applicable for the transmission control traffic requirement. At group call setup the request for resources for the media plane is triggered. This request is sent directly from the MC service server to the PCRF.
The procedure is optional and is suitable when the procedures for pre-established sessions are used, it may also be used to setup and tear down the media plane used by between consecutive group calls in one communication session using the chat call model.
Up

10.11.6.2  Procedure  p. 260

The Figure below illustrates the procedure for resource reservation
Reproduction of 3GPP TS 23.280, Fig. 10.11.6.2-1: Request for resources for transmission control and media plane
Figure 10.11.6.2-1: Request for resources for transmission control and media plane
Up
Step 1.
The MC service client sends a request for group affiliation.
Step 2.
The MC service client sends a request to the MC service server for establishment of a communication session.
Step 3.
The MC service server answer the session establishment request and adjust the bandwidth information in the session description. The requested bandwidth shall be minimized to cover the bandwidth requirements for floor control signaling (or transmission control for MCVideo or MCData).
Step 4.
The SIP core request resources towards the PCRF according to the session establishment request.5. The session establishment request is completed and a response is sent towards the MC service client.
Step 6.
The MC service client sends a cell setup message according to existing procedures.
Step 7.
The MC service server sends a session establishment request for resources for the media plane to PCRF, and the media plane is by that established. This request includes media description relevant for the media plane.
Step 8.
Group call is ongoing on the group communication session.
Step 9.
The MC service serve sends a release of media resources to PCRF, and the media plane is by that terminated.
Step 10.
The PCRF performs session termination procedure according to TS 23.203.
Step 11.
The PCRF sends a session release response back to the MC service server.
Up

Up   Top   ToC