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 MC service resource management (on-network)  10.11.1 General  10.11.2 Request for unicast resources at session establishment - SIP core based  10.11.2a Request for unicast resources at session establishment - MC service server based  10.11.3 Request for modification of unicast resources  10.11.4 Management of multicast media bearers 
...

 

10.11  MC service resource management (on-network) |R15|  p. 254

10.11.1  General  p. 254

The following subclauses specify the procedures for resource management for mission critical services. The procedures are utilised by the following MC services:
The MC service server sets up media bearers and may need to modify the bearers for an already established MC communication.
Media characteristics that may need to be modified include:
  • activation and deactivation of the bearer;
  • modification of the QoS characteristics of the bearer (e.g. bearer priority adjustment); and
  • modification of GBR due to media codec change
The information elements associated to the resources management procedures in this clause are derived from the respective communication setup procedures in TS 23.379, TS 23.281 and TS 23.282.
Up

10.11.2  Request for unicast resources at session establishment - SIP core based  p. 255

The procedure defined in this subclause specifies how network resources are requested at session establishment. If concurrent sessions are used the MC service server may utilize the capability of resource sharing specified in TS 23.203. The request for resources is sent to the PCRF on the Rx reference point and includes media type, bandwidth, priority, application identifier and resource sharing information.
The procedure is generic to any type of session establishment that requires requests for network resources.
Procedures in Figure 10.11.2-1 are the signalling procedures for the requesting resource at session establishment.
Reproduction of 3GPP TS 23.280, Fig. 10.11.2-1: Resource request at session establishment - SIP core based
Figure 10.11.2-1: Resource request at session establishment - SIP core based
Up
Step 1.
MC service client sends a session establishment request.
Step 2.
MC service server receives evaluates the need network resources and use of media resource sharing.
Step 3.
MC service server send a session progress request containing request for resources.
Step 4.
PCC procedures (as defined in TS 23.203) initiated from SIP core local inbound/outbound proxy over Rx.
Step 5.
The SIP core local inbound / outbound proxy forwards the call control protocol request to the MC service client.
Step 6.
The MC service client acknowledges the session progress request with an OK message.
Step 7.
The SIP core local inbound / outbound proxy forwards the OK message to the MC service server.
Step 8.
The MC service session is established and resources have been allocated.
Up

10.11.2a  Request for unicast resources at session establishment - MC service server based |R17|  p. 256

10.11.2a.1  General  p. 256

The procedure defined in this clause specifies how network resources are requested at session establishment from the MC service server. The request for resources is sent to the PCRF via the Rx reference point from the MC service server and includes media type, bandwidth, priority, application identifier and resource sharing information. If concurrent sessions are used, the MC service server may utilize the capability of resource sharing specified in TS 23.203.
For the request of network resources by the MC service server via the Rx reference point, the MC service client provides to the MC service server the final access resource details (e.g. IP addresses and ports) of the MC service client and the media anchoring points.
This procedure is generic to any type of session establishment with the MC service server requesting network resources.
Up

10.11.2a.2  Procedure  p. 256

Figure 10.11.2a.2-1 describes the procedure for the request of resources at session establishment from the MC service server.
Reproduction of 3GPP TS 23.280, Fig. 10.11.2a.2-1: Resource request at session establishment - MC service server based
Figure 10.11.2a.2-1: Resource request at session establishment - MC service server based
Up
Step 1.
The MC service client sends a session establishment request. The request includes, apart from the SDP offer, access resource details, e.g. IP addresses and ports of the MC service client related to the media session.
Step 2.
The MC service server evaluates the need of network resources and use of media resource sharing.
Step 3.
The MC service server sends a session progress request to the SIP core.
Step 4.
The SIP core local inbound / outbound proxy forwards the session progress request to the MC service client.
Step 5.
The MC service client acknowledges the session establishment to the MC service server. This message contains the final negotiated media access parameters, e.g. IP addresses and ports related to the media anchoring points received in the SDP answer from the SIP core.
Step 6.
The MC service server sends a request for media resources to the PCRF over Rx (as defined in TS 23.203).
Step 7.
The MC service session is established, and resources have been allocated.
Up

10.11.3  Request for modification of unicast resources  p. 257

To modify unicast media bearers, the MC service server shall send a resource modification request containing the parameters to be modified, using the call control protocol via the SIP core to the UE.
Possible scenarios when this procedure may be used are:
  • Modify the allocation and retention priority for unicast resources;
  • Release and resume resources in-between MC service calls when using the chat model; or
  • Release and resume resources when a UE is able to receive the MC service call over multicast transmission
Releasing resources for the media plane should give the option to allow the SIP session to either be torn down or continue.
Procedures in Figure 10.11.3-1 are the signalling procedures for the modification of a unicast:
Pre-conditions:
  • An MC service session is already in progress;
Reproduction of 3GPP TS 23.280, Fig. 10.11.3-1: Bearer modification request
Figure 10.11.3-1: Bearer modification request
Up
Step 1.
MC service server decides to modify the parameters of a unicast bearer (e.g. a request to upgrade the existing MC service call to an MC service emergency or imminent-peril call).
Step 2.
MC service server sends a session update which includes a resource modification request containing the modified parameters of the unicast bearer.
Step 3.
PCC procedures (as defined in TS 23.203) initiated from SIP core local inbound/outbound proxy over Rx.
Step 4.
The SIP core local inbound / outbound proxy forwards the session update request to the MC service client.
Step 5.
The MC service client acknowledges the call control protocol request with an OK message.
Step 6.
The SIP core local inbound / outbound proxy forwards the OK message to the MC service server.
Step 7.
The MC service session continues with the modified unicast resources.
Up

10.11.4  Management of multicast media bearers  p. 258

To activate the multicast media bearers the MC service server shall use the Activate MBMS Bearer procedure specified in TS 23.468 with the MC service server performing the GCS AS function. The MC service server shall activate MBMS bearers in broadcast areas where eMBMS capable UEs are or are expected to be located. For that, the MC service server shall use the MBMS SAI(s) and/or cell id(s) information to construct the MBMS broadcast area parameter in the Activate MBMS Bearer procedure.
To deactivate the multicast media bearers the MC service server shall use the Deactivate MBMS Bearer procedure specified in TS 23.468 with the MC service server performing the GCS AS function.
To modify multicast media bearers the MC service server shall use the Modify MBMS Bearer procedure specified in TS 23.468 with the MC service server performing the GCS AS function.
Up

Up   Top   ToC