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.289  Word version:  19.3.0

Top   Top   Up   Prev   Next
0…   4…   4.7…   4.7.4…   4.8…   5…   5.4…   6…   6.3…   6.3.2…   7…   7.2.4…   7.3…   7.3.3…   7.3.3.2…   7.3.3.4…   7.3.3.5…   7.3.3.7…   7.3.3.8…   7.3.3.9…   7.3.3.10…   7.3.3.11…   7.3.3.12…   7.3.3.13…   7.4…   7.5…   7.6…   A… 
7.3.3.11 MBS transmission in MCVideo  7.3.3.11.1 General  7.3.3.11.2 Call connect and disconnect over MBS session procedures  7.3.3.11.2.1 General  7.3.3.11.2.2 Procedure  7.3.3.11.2.2.1 Group call connect over MBS session  7.3.3.11.2.2.2 Group call disconnect from MBS session  7.3.3.11.3 Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCVideo  7.3.3.11.4 DL media transmission with 5MBS for MCVideo 
...

 

7.3.3.11  MBS transmission in MCVideo  p. 95

7.3.3.11.1  General  p. 95
MCVideo server can determine to use 5G MBS for the transmission of DL link media for different types of MCVideo group calls.
The application layer signalling such as the transmit media request and transmit media granted messages, may be transmitted along with the MC media over the same MBS session however with different QoS requirements, or over other means such as unicast downlink or a different MBS session.
When using the procedures for pre-configured or dynamic MBS session establishment for MCVideo, the MCVideo server perform the procedure of call connect and disconnect over MBS session.
The MCVideo service shall support the procedure for using MBS sessions as specified clause 7.3.3.1 with the following clarifications:
  • The MC service client is the MCVideo client;
  • The MC service server is the MCVideo server; and
  • The MC service ID is the MCVideo ID.
The MCVideo service shall use the MCVideo-1, MCVideo-8 and MCVideo-9 reference points for this procedure.
Up
7.3.3.11.2  Call connect and disconnect over MBS session procedures  p. 95
7.3.3.11.2.1  General  p. 95
MBS session can be used for MCVideo group calls. One MBS session may not be permanently associated to one specific group or group call.
The procedure in clause 7.3.3.11.2.2 requires that the group session is setup before the media transmission start. This eliminates the need for the receiving clients to continuously use a unicast session. Prior to this the MBS session is activated and announced to the MCVideo clients.
Up
7.3.3.11.2.2  Procedure  p. 95
7.3.3.11.2.2.1  Group call connect over MBS session  p. 95
Figure 7.3.3.11.2.2.1-1 presents the procedure for a group communication, in specific, video call connect over either broadcast or multicast MBS sessions.
Pre-conditions:
  • The MCVideo clients 1 to n are attached to the 5GS, registered and affiliated to the same MCVideo group X.
  • The MCVideo server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
  • The MCVideo server has decided to use an MBS session for the MCVideo services associated to the MCVideo group X.
Reproduction of 3GPP TS 23.289, Fig. 7.3.3.11.2.2.1-1: Group call connect on MBS session
Figure 7.3.3.11.2.2.1-1: Group call connect on MBS session
Up
Step 1.
An MBS session is configured with the required QoS requirements, announced and established.
Step 2.
In the case of multicast MBS sessions, the MCVideo UEs initiate a UE session join towards the 5GC based on the session information provided to the MCVideo UE during the session announcement step. This step is essential in order to receive the corresponding MC media. The multicast MBS session is hence established once the request of the first initiated UE session join is accepted as indicated in TS 23.247.
Step 3.
MCVideo client 1 initiates a MCVideo group communication, namely a video group call, by sending an initial transmit media request over a unicast PDU session towards the MCVideo server.
Step 4.
The MCVideo server sends a MapGroupToSessionStream including the necessary stream information for the MCVideo clients 2 to n to receive the MC media related to the group call which is taken place within the associated MBS session.
Step 5.
The MCVideo clients 2 to n process the MapGroupToSessionStream information and may send a MapGroupToSessionStream Ack back to the MCVideo server if required.
Step 6.
The MCVideo server grants MCVideo client 1 the right to transmit media over the associated MBS session and sends a transmit media grated message to client 1 over a unicast PDU session.
Step 7.
A media transmission notification message is sent from the MCVideo server to the MC clients 2 to n over the associated MBS session. It indicates the MCVideo ID of the transmitting client, i.e., MCVideo ID of service client 1 and the associated MC group ID.
Step 8.
MCVideo clients 2 to n process the notification message and get informed about the necessary information of the video group call.
Step 9.
The MCVideo clients 2 to n may send a receive media request to the MCVideo server, to indicate the reception of media over the associated MBS session. As a result, the MCVideo server sends a corresponding response message.
Step 10.
MCVideo client 1 sends the MC media over a unicast PDU session towards the MCVideo server.
Step 11.
The MCVideo server sends the MC media over the indicated stream within the associated MBS session to the MCVideo clients 2 to n.
Up
7.3.3.11.2.2.2  Group call disconnect from MBS session  p. 97
Figure 7.3.3.11.2.2.2-1 presents the procedure for a group call disconnect over broadcast and multicast MBS sessions.
Reproduction of 3GPP TS 23.289, Fig. 7.3.3.11.2.2.2-1: Group call disconnect from MBS session
Figure 7.3.3.11.2.2.2-1: Group call disconnect from MBS session
Up
Step 1.
The MC group call is taking place over the associated MBS session. MCVideo client 1 is sending the MC media over a unicast PDU session to the MCVideo server.
Step 2.
The MCVideo delivers the MC media over the associated broadcast or multicast MBS session to MCVideo clients 2 to n.
Step 3.
After the MC media transmission is over, i.e., no further media to be sent over the group communication, the MCVideo server sends an UnMapGroupFromSessionStream to MCVideo clients 2 to n to indicate the de-association of the group call from the corresponding MBS session stream.
Step 4.
The MCVideo server may release the MBS session as described in clause 7.3.3.3.2.
Up
7.3.3.11.3  Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCVideo  p. 97
The MCVideo service shall support the procedure for switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer and LTE unicast bearer as specified in clause 7.3.3.8 and clause 7.3.3.9 with the following clarifications:
  • The MC service client is the MCVideo client;
  • The MC service server is the MCVideo server; and
  • The MC service ID is the MCVideo ID.
The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure.
Up
7.3.3.11.4  DL media transmission with 5MBS for MCVideo  p. 97
The MCViedo service shall support the procedure for using pre-created MBS session, or dynamic MBS session as specified clause 7.3.3.1.
MCVideo may use pre-created MBS session for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the pre-created MBS session for distributing the media. The MBS session can be used by any group.
When using the pre-created MBS session for MCVideo, the MCVideo server may perform the procedure of call connect and disconnect over MBS as defined in clause 7.3.3.11.2 for the group communication session establishment step, or send map group communication to MBS session as defined in clause 7.3.2.4 after group communication session establishment.
MCVideo may also use dynamic MBS session for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the dynamic MBS session for distributing the media.
When using the procedures for dynamic MBS session establishment for MCVideo, the MCVideo server perform the procedure of triggering MBS session configuration as defined in clause 7.3.3.1 and mapping group communication to MBS session as defined in defined in clause 7.3.2.4 at the group communication session establishment step.
Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the MBS session. Optionally a separate MBS session could be used for the transmission control messages.
Up

Up   Top   ToC