Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 26.502  Word version:  17.3.0

Top   Top   Up   Prev   Next
1…   4…   4.3…   4.5…   4.5.2   4.5.3…   4.6…   4.9   5…   5.3   5.4   5.5   5.6   6…   7…   A…   B…   C…   C.3…   C.4…


4.5  Domain modelp. 18

4.5.1  User Services domain modelp. 18

The domain model for MBS User Services addresses different service and session concepts that are established between the different functional entities of the MBS User Services architecture, as shown in Figure 4.5.1-1.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. 4.5.1-1: MBS User Services domain model
Figure 4.5.1-1: MBS User Services domain model
(⇒ copy of original 3GPP image)
In the above Figure:
The MBS Application Provider initiates MBS User Service Provisioning with the MBSF to provision an MBS User Service.
Subsequently, the MBS Application Provider provisions a number of time-bound MBS User Data Ingest Sessions within the scope of the newly provisioned MBS User Service, also by means of MBS User Service Provisioning.
When the current time enters the time window of a provisioned MBS User Data Ingest Session:
The MBSF establishes an MBS User Service Session of the parent MBS User Service by establishing an MBS Session in the MBS System. The reception parameters of the MBS Session are advertised in an MBS User Service Announcement, as defined in clause 4.5.2 below. The MBS User Service Announcement is optionally passed back to the MBS Application Provider by means of MBS User Service Provisioning (see step 7bis).
The MBSTF establishes an MBS User Data Ingest Session between itself and the MBS Application Provider for the purpose of ingesting objects or packets, according to the type of distribution method provisioned.
The MBSTF establishes an MBS Distribution Session and begins to transmit objects or packets on it according to the configured distribution method as and when they are available from the MBS User Data Ingest Session.
When an MBS User Service is established:
The MBS-Aware Application instructs the MBSF Client to activate an MBS User Service by means of MBS User Service Control.
The MBSF Client may acquire the MBS User Service Announcement from the MBSF via the MBS User Service [or via the MBS Distribution Session] and pass selected application-facing parameters (such as the service class and service names) up to the MBS-Aware Application by means of MBS User Service Control.
Alternatively, the MBS User Service Announcement may be made available to the MBS Application Provider, in which case the MBS-Aware Application obtains it via an application-private MBS Application Service and then provides it to the MBSF Client by means of MBS User Service Control.
The MBS-Aware Application selects the announced MBS User Service via MBS User Service Control and, as a result, the MBSF Client activates reception of the corresponding MBS Distribution Session in the MBSTF Client.
An MBS Application Data Session is established between the MBSTF Client and the MBS-Aware Application to supply the latter with received (and possibly repaired) user data.

Up   Top   ToC