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.12 MBS transmission in MCData  7.3.3.12.1 General  7.3.3.12.2 Usage of MBS session for MCData  7.3.3.12.3 Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCData  7.3.3.12.4 Group communication connect and disconnect over MBS session procedures  7.3.3.12.4.1 General  7.3.3.12.4.2 Procedure  7.3.3.12.4.2.1 Group communication connect over MBS session  7.3.3.12.4.2.2 Group communication disconnect from MBS session  7.3.3.12.5 Downlink media transmission with 5MBS 
...

 

7.3.3.12  MBS transmission in MCData  p. 98

7.3.3.12.1  General  p. 98
The procedures and information flows for Short data service and file distribution of MC Data group are defined in TS 23.282.
When using 5G MBS, MCData server can determine to use either pre-created MBS session or dynamic MBS session as defined in clause 7.3.3.1 for the transmission of DL link media for different types of MCData service capabilities.
MCData may use the 5G MBS session for the MCData features short data service and file distribution for MCData group communication. The 5G MBS session can be used by any MCData group.
Both the media packets as well as application level control signalling (e.g. transmission control) to the receiving users may be sent on the MBS session. Optionally, a separate MBS Session could be used for the application level control signalling (e.g. transmission control).
When MBSF/MBSTF are deployed in 5GS, MCData server could also determine to use File distribution capabilities provided by MBSF/MBSTF for file distribution.
Up
7.3.3.12.2  Usage of MBS session for MCData  p. 98
The MCData service shall support the procedure for using pre-created MBS session or dynamic MBS session as specified in clause 7.3.3.1 with the following clarifications:
  • The MC service client is the MCData client;
  • The MC service server is the MCData server; and
  • The MC service ID is the MCData ID.
When using the procedures for pre-created or dynamic MBS session establishment for MCData, the MCData server performs the procedure of group communication connect and disconnect over MBS session at the group communication session establishment phase.
The MCData service shall use the MCData-SDS-1, MCData-SDS-3, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure.
Up
7.3.3.12.3  Switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer for MCData  p. 98
The MCData service shall support the procedure for switching between 5G MBS session, 5G unicast PDU session, LTE eMBMS bearer, and LTE unicast bearer or eMBMS 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 MCData client;
  • The MC service server is the MCData server; and
  • The MC service ID is the MCData ID.
The MCData service shall use the MCData-SDS-1, MCData-SDS-2, MCData-SDS-3, MCData-FD-1, MCData FD-2, MCData-FD-3, MCData-DS-1, MCData-DS-2 and MCData-DS-3 reference points for this procedure.
Up
7.3.3.12.4  Group communication connect and disconnect over MBS session procedures  p. 99
7.3.3.12.4.1  General  p. 99
MBS session can be used for MCData group communication. One MBS session may be not permanently associated to one specific group or group communication.
The procedure in clause 7.3.3.12.4 requires that the group session is setup before the data transmission starts. This eliminates the need for the receiving clients to continuously use a unicast session. Prior to group session setup, the MBS session is activated and announced to the MCData clients.
Up
7.3.3.12.4.2  Procedure  p. 99
The procedure specified in this clause is applicable (for the group communication establishment) for Group standalone short data service using media plane as described in clause 7.4.2.6 in TS 23.282 and for Group short data service session as described in clause 7.4.2.7 in TS 23.282.
7.3.3.12.4.2.1  Group communication connect over MBS session  p. 99
Pre-conditions:
  • The MCData clients 1 to n are attached to the 5GS, registered and affiliated to the same MCData group X.
  • The MCData server has directly performed (or via NEF/MBSF) an MB-SMF discovery and selection, unless the corresponding information is locally configured.
  • The MCData server has decided to use an MBS session for the MCData service group communication associated with to the MCData group X.
Copy of original 3GPP image for 3GPP TS 23.289, Fig. 7.3.3.12.4.2.1-1: Group communication connect over broadcast and multicast MBS sessions.
Figure 7.3.3.12.4.2.1-1: Group communication connect over broadcast and multicast MBS sessions.
(⇒ copy of original 3GPP image)
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 MCData UE initiates a UE session join towards the 5GS based on the session information provided to the MCData UE during the session announcement step. This step 2 is essential in order to receive the corresponding MC media. The multicast MBS session is hence established once the first initiated UE session join is accepted as indicated in TS 23.247.
Step 3.
The MCData client 1 initiates a group communication by sending a MCData group data request over a unicast PDU session towards the MCData server.
Step 4.
MCData server initiates the MCData group data request towards each MCData clients 2 to n.
Step 5.
The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request.
Step 6.
The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server.
Step 7.
The MCData server sends a MapGroupToSessionStream including the necessary stream information for the MCData clients 2 to n to receive the MC data related to the group communication which is taken place within the associated MBS session.
Step 8.
The MCData clients 2 to n process the MapGroupToSessionStream information and may send a MapGroupToSessionStream Ack back to the MCData server if required.
Step 9.
MCData server forwards the MCData group data response received from MCData client 2 to n to the MCData user initiating the MCData session data request.
Step 10.
MCData client 1 sends the MC data over uplink unicast PDU session towards the MCData server.
Step 11.
The MCData server sends the MC data over the indicated stream within the associated MBS session to the MCData clients 2 to n.
Up
7.3.3.12.4.2.2  Group communication disconnect from MBS session  p. 100
Figure 7.3.3.12.4.2.2-1 presents the procedure for a group communication disconnect over broadcast and multicast MBS sessions.
Copy of original 3GPP image for 3GPP TS 23.289, Fig. 7.3.3.12.4.2.2-1: Group communication disconnect over broadcast and multicast MBS sessions.
Figure 7.3.3.12.4.2.2-1: Group communication disconnect over broadcast and multicast MBS sessions.
(⇒ copy of original 3GPP image)
Up
Step 1.
The MC group communication is taking place over the associated MBS session. MCData client 1 is sending the MC data over a unicast PDU session to the MCData server.
Step 2.
The MCData server sends the MC data over the associated MBS session to MCData clients 2 to n.
Step 3.
After the MC data transmission is over, i.e., no further data to be sent over the group communication, the MCData server sends an UnMapGroupFromSessionStream to de-associate the group communication from the MBS session.
Step 4.
The MCData server may release the MBS session as described in clause 7.3.3.3.2.
Up
7.3.3.12.5  Downlink media transmission with 5MBS  p. 101
The MCData service shall support the procedure for using pre-established MBS session, or dynamic MBS session as specified in clause 7.3.3.1.
MCData may use MBS session for the different types of sub-services. Both SDS and FD can use the pre-established MBS session or dynamic MBS session for distributing the data.

Up   Top   ToC