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 26.502  Word version:  18.1.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.3 Functional entities  4.3.1 General  4.3.2 MBSF  4.3.3 MBSTF  4.3.3.1 General  4.3.3.2 MBSTF subfunctions to support Object Distribution Method  4.3.3.3 MBSTF subfunctions to support Packet Distribution Method  4.3.3A MBS AF  4.3.4 MBS AS  4.3.4A MBSSF  4.3.5 MBS Client  4.3.6 MBS-Aware Application  4.4 Reference points and interfaces 
...

 

4.3  Functional entities  p. 14

4.3.1  General  p. 14

The MBSF and MBSTF offer service layer functionality for sending data via MBS Sessions. The MBSF (clause 4.3.2) offers control plane functionality while the MBSTF (clause 4.3.3) offers user plane functionality. The MBSTF acts as a User Plane anchor when it sources IP multicast traffic. Reference point Nmb2 provides the means for the MBSF to configure the delivery methods in the MBSTF, and also supports push-based ingest of object manifests. Reference point MBS-11 supports pull-based ingest by the MBSTF of object manifests and pull-based ingest of User Service Announcement objects for delivery to the MBS Client via reference point MBS-4-MC (as described in clause 4.2.4).
Figure 4.3.1-1 shows the complete set of functional entities involved in supporting MBS User Services when the MBS Application Provider is deployed in the Trusted DN, including client functions in the UE.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. 4.3.1-1: MBS User Service reference architecture
Figure 4.3.1-1: MBS User Service reference architecture
(⇒ copy of original 3GPP image)
Up
In the above architecture, MBS-specific functions such as the MBS AS and MBSF are shown as independent and standalone. In deployments, they may be co-located on physical devices with other functions. As an example, the MBS AS may be hosted in the MBS Application Provider domain, or it may be hosted in a 5GMS AS.

4.3.2  MBSF  p. 14

The functionality of the MBSF is defined in clause 5.3.2.11 of TS 23.247. It receives provisioning and control commands either directly at reference point Nmb10 or at reference point Nmb5 (via the NEF). The MBSF invokes MBS Session operations on the MB-SMF at reference point Nmb1. The MBSF configures the MBSTF at reference point Nmb2.
The User Service Announcement function of the MBSF provides session access information which is consumed by the MBS Client and subsequently used to discover and initiate the reception of one or multiple MBS User Services. The session access information may contain information for presentation to the end-user, as well as application parameters used in generating service content for consumption by the MBS Client.
The present document defines additional Control Plane functionalities of the MBSF to support MBS User Services including:
  1. Generating the User Service Announcement for each MBS Session.
  2. Managing User Service Announcement updates.
  3. Providing the User Service Announcement information to the MBS Client in a timely manner using one or more of the following mechanisms:
    1. Unicast User Service Announcement delivered by the MBS AF via reference point MBS-5, including the possible use of push- or notification-based update mechanisms.
    2. User Service Announcement via an MBS Distribution Session delivered by the MBSTF at reference point MBS-4-MC, optionally in the same MBS Distribution Session as the content it is advertising, or else via a dedicated MBS Distribution Session managed by the MBSF called the MBS User Service Announcement Channel.
    3. User Service Announcement via application-private means at reference point MBS-8.
Up

4.3.3  MBSTF  p. 15

4.3.3.1  General  p. 15

The functionality of the MBSTF is defined in clause 5.3.2.12 of TS 23.247. It receives User Plane data traffic at reference point Nmb8 and sends MBS data packets to the MB-UPF via reference point Nmb9.
The present document defines additional User Plane functionalities of the MBSTF to support MBS User Services as follows:
  1. Receiving MBS Distribution Session configurations from the MBSF at reference point Nmb2.
  2. Sending notification events to the MBSF, e.g., data ingest failure, session terminated, delivery started via reference point Nmb2.
  3. Based on the MBS Distribution Session configuration:
    1. MBS delivery of ingested objects or sequences of objects to the MBS Client using the Object Distribution Method (see clause 6.1). This may be used to support real-time distribution of media segments (as special objects) including CMAF segments.
    2. MBS delivery of ingested packet streams to the MBS Client using the Packet Distribution Method (see clause 6.2).
    3. Delivery of MBS User Service Announcement information (including updates as necessary) within the MBS Session.
Up

4.3.3.2  MBSTF subfunctions to support Object Distribution Method  p. 16

The MBSTF subfunctions supporting the Object Distribution Method are depicted in Figure 4.3.3.2-1 below.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. 4.3.3.2-1: MBSTF architecture overview for Object Distribution Method
Figure 4.3.3.2-1: MBSTF architecture overview for Object Distribution Method
(⇒ copy of original 3GPP image)
Up
The Object ingest subfunction supports:
  • Pull-based ingest at reference point MBS-11: The Object ingest subfunction in this case fetches one or more objects from the MBS AF using HTTPS for inclusion in the MBS User Service Announcement Channel. (The set of objects to be included is listed in an object manifest previously fetched from the MBS AF at the same reference point.)
  • Push-based ingest at reference point Nmb2: The Object ingest subfunction receives an object manifest from the MBSF that describes a set of objects for inclusion in the MBS User Service Announcement Channel. The MBSTF goes on to fetch the objects listed in the object manifest from the MBS AF via reference point MBS-11.
  • Pull-based ingest at reference point Nmb8: The Object ingest subfunction in this case fetches one or more objects from the MBS Application Provider (AF/AS).
  • Push-based ingest at reference point Nmb8: The Object ingest subfunction receives one or more objects from the MBS Application Provider (AF/AS).
Object ingest procedures at reference point Nmb2 and MBS-11 shall be a subset of those at reference point Nmb8.
The Object segmentation subfunction supports the partitioning of an object into payload units suitable for MBS transmission.
The optional Application Layer FEC subfunction supports object recovery when some packets are not received by the MBMS Client.
The Packetisation subfunction places the payload units (and, optionally, the FEC data) into Nmb9 transmission packets according to clause 6.1.
The Packet scheduling subfunction schedules the outgoing packet stream according to target bit rate configuration.
The Control subfunction offers support for MBSTF service configuration, status query and notifications at reference point Nmb2.
Up

4.3.3.3  MBSTF subfunctions to support Packet Distribution Method  p. 17

The MBSTF subfunctions supporting the Packet Distribution Method are depicted in Figure 4.3.3.3-1 below.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. 4.3.3.3-1: MBSTF architecture overview for Packet Distribution Method
Figure 4.3.3.3-1: MBSTF architecture overview for Packet Distribution Method
(⇒ copy of original 3GPP image)
Up
The Packet ingest subfunction supports the reception of a packet sequence at reference point Nmb2 from authorized sources.
The optional Application Layer FEC subfunction to support object recovery when some packets are not received by the MBMS Client.
The Packetisation subfunction places the ingested packets (and, optionally, the FEC data) into Nmb9 transmission packets. Depending on the transmission mode, ingested packets may be reformatted suitable for MBS transmission.
The Packet scheduling subfunction schedules the outgoing data stream according to target bit rate configuration.
The Control subfunction offers support for MBSTF service configuration and service notifications at reference point Nmb2.
Up

4.3.3A  MBS AF  p. 17

The MBS AF is an optional entity that performs the following functions to support MBS User Services:
  • Serving User Service Announcements to the MBSF Client via unicast reference point MBS-5.
  • Serving object manifests and/or User Service Announcements to the MBSTF via reference point MBS-11.
The MBS AF is configured by the MBSF at reference point MBS-3. This interaction is not further defined by the present document.
The MBS AF may be deployed as a standalone entity, or its functions may be co-located with other Network Functions such as the MBSF (see clause 4.3.2), or the 5GMS AF defined in TS 26.501.
Up

4.3.4  MBS AS  p. 18

The MBS AS is an optional entity that performs the following functions to support MBS User Services:
  • Providing a byte-range file repair service to the MBSTF Client (via reference point MBS-4-UC) for use with the Object Distribution Method.
The MBS AS is configured by the MBSF at reference point MBS-9. The MBS AS may acquire content from the MBSTF. These interactions are not further defined by the present document.
The MBS AS may be deployed as a standalone entity, or its functions may be co-located with other Network Functions such as the MBSTF (see clause 4.3.3) or the 5GMS AS defined in TS 26.501.
Up

4.3.4A  MBSSF  p. 18

The MBS Security Function (MBSSF) is an optional logical entity defined in clause 6.13 of TS 23.247 and TS 33.501 that performs the following functions to support MBS User Services:
In deployment, the MBSSF may be co-located with the MBSF or with the MBSTF, as described in clause 6.13 of TS 23.247. Interactions and procedures between these three functions are not defined in the present document.
Up

4.3.5  MBS Client  p. 18

The MBS Client function is part of the UE. The functionality of the UE is defined in clause 5.3.2.8 of TS 23.247.
The MBS Client is further divided into the following subfunctions:
  • MBSF Client: Communicates with the MBS AF at reference point MBS-5 on MBS User Service control aspects. Communicates with the MBSSF at reference point MBS-10 to authenticate access to security-protected MBS data (see clause W.4 of TS 33.501) that it has received from reference point MBS-4-MC.
  • MBSTF Client: Communicates with the MBSTF at reference point MBS-4-MC and/or with the MBS AS at reference point MBS-4-UC in order to provide an MBS Application Data Session to the MBS-Aware Application.
The MBS Client performs the following functions to support MBS User Services:
  • Acquisition of MBSF-compiled User Service Announcements from the MBS AF at reference point MBS-5 and/or from the MBSTF at reference point MBS-4-MC.
  • Authorisation of access to security-protected MBS data by invoking the User Plane security procedure defined in clause W.4.1.3 of TS 33.501 at reference point MBS-10.
  • Reception of MBS data via reference point MBS-4-MC from either a Multicast MBS Session or a Broadcast MBS Session.
  • Exposure of MBS Application Data Sessions towards an MBS-Aware Application.
  • Using AL-FEC to recover packets or objects, if this optional feature is provisioned for the MBS Session.
  • Unicast recovery via reference point MBS-4-UC of the application payload data carried in multicast/broadcast packets that are not successfully received via MBS-4-MC, if unicast repair is provisioned for the MBS Session.
Up

4.3.6  MBS-Aware Application  p. 19

The MBS Client is typically controlled by an external application which triggers the establishment of an MBS User Services session. The MBS-Aware Application is not defined within the present document, but the function makes use of the MBS Client and (indirectly) the Network Functions supporting MBS User Services (MBSF, MBSTF and MBS AS) via reference points MBS-6 and MBS-7.

4.4  Reference points and interfaces  p. 19

4.4.1  Overview  p. 19

The following reference points defined in clause 5.1 of TS 23.247 are relevant to MBS User Services architecture: Nmb1, Nmb2, Nmb5, Nmb8, Nmb9, Nmb10 and Nmb12.
The following additional reference points are defined by the present document:
  • MBS-3: Used by the MBSF to configure the MBS AF and to publish User Service Announcements to it. This reference point is not described further in the present document.
  • MBS-4-UC: User Plane interactions between the MBSTF Client and the MBS AS for the purpose of file-based unicast repair.
  • MBS-5: User Plane interactions between the MBSF Client and the MBS AF for the purpose of MBS control plane and service handling.
  • MBS-6: API exposed by the MBSF Client and used by the MBS-Aware Application to manage and control MBS User Services.
  • MBS-7: API exposed by the MBSTF Client and used by the MBS-Aware Application to receive user data information distributed using MBS User Services.
  • MBS-8: Announcement of MBS User Services to the MBS-Aware Application by the MBS Application Provider. The procedures at this reference point are beyond the scope of 3GPP specification.
  • MBS-9: Used by the MBSF to configure the MBS AS. This reference point is not described further in the present document.
  • MBS-10: User Plane interactions between the MBSF Client and the MBSSF for the purpose of authorising access to security-protected MBS data by means of the User Plane security procedure specified in clause W.4.1.3 of TS 33.501.
  • MBS-11: Used by the MBSTF to retrieve object manifests and User Service Announcements listed in object manifests from the MBS AF.
In addition, the following reference points are defined inside the MBS Client function:
  • MBS-6': API exposed by the MBSTF Client and used by the MBSF Client to (de)activate reception of an MBS Session by the MBSTF. The reception parameters are supplied by the MBSF Client.
    This reference point is outside the scope of MBS User Services and is not described further in the present document.
  • MBS-7': API exposed by the MSTF Client and used by the MBSTF to supply MBS Session configuration information that has been received from reference point MBS-4-MC.
    This reference point is outside the scope of MBS User Services and is not described further in the present document.
Up

Up   Top   ToC