Content for TS 26.502 Word version: 18.1.0
4.5.3 MBS User Service parameters
4.5.4 MBS Reception Reporting Configuration parameters
4.5.5 MBS User Data Ingest Session parameters
4.5.6 MBS Distribution Session parameters
4.5.7 MBS User Service Announcement parameters
4.5.8 MBS Distribution Session Announcement parameters
4.5.9 Mapping of MBS Distribution Session to MBS Session Context
4.5.10 Object manifest parameters
...
...
4.5.3 MBS User Service parameters p. 24
This entity models an MBS User Service, as provisioned by the MBS Application Provider and as managed by the MBSF. The baseline parameters of an MBS User Service are listed in Table 4.5.3-1 below:
With the exception of Service type, which is an immutable property of an MBS User Service, any of the parameters assigned by the MBS Application Provider may be updated by the MBS Application Provider at any time.
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| User Service Identifier | 1..1 | MBSF | A unique identifier for this MBS User Service in the MBSF. |
| External service identifiers | 1..* | MBS Application Provider | A unique identifier for this MBS User Service that is also present in the MBS User Service Announcement. If assigned in a globally unique manner, this identifier may be useful in correlating this MBS User Service with the same service delivered by a different system. |
| Service type | 1..1 | Indicates whether this MBS User Service is distributed via Multicast MBS Session(s) or Broadcast MBS Session(s) | |
| Service class | 1..1 | The class of this MBS User Service, expressed as a fully-qualified term identifier from a controlled vocabulary such as the OMNA BCAST Service Class [16], e.g. urn:oma:bcast:oma_bsc:st:1.0. | |
| Service announcement modes | 1..* | Determines whether the MBS User Service Announcement compiled by the MBSF is advertised to the MBSF Client at reference point MBS-5 and/or advertised to the MBSF Client via the MBS Distribution Session and/or passed back to the MBS Application Provider via reference point Nmb10. | |
| Service names | 1..* | A set of distinguishing names for this MBS User Service, one per language. | |
| Service descriptions | 1..* | A set of descriptions of this MBS User Service, one per language. | |
| Main service language | 0..1 | The main language of this MBS User Service. |
MBS User Data Ingest Sessions (see clause 4.5.5) are separately provisioned within the scope of an MBS User Service. It is valid for an MBS User Service to have no MBS User Data Ingest Sessions currently provisioned.
An MBS Reception Reporting Configuration (see clause 4.5.4 below) may be separately provisioned within the scope of an MBS User Service.
4.5.4 MBS Reception Reporting Configuration parameters p. 24
Reception reporting for MBS User Services is for future study.
4.5.5 MBS User Data Ingest Session parameters p. 25
This entity models an MBS User Data Ingest Session, as provisioned by the MBS Application Provider and as managed by the MBSF. The baseline parameters for an MBS User Data Ingest Session are listed in Table 4.5.5-1 below.
The set of active periods may be updated by the MBS Application Provider at any time. The state of constituent MBS Distribution Sessions (and their corresponding MBS Distribution Session Announcements) may need to change as a consequence.
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| User Data Ingest Session Identifier | 1..1 | MBSF | An identifier for this MBS User Data Ingest Session that is unique in the scope of the parent MBS User Service (see clause 4.5.3). |
| MBS User Service Announcement | 0..1 | The MBS User Service Announcement (see clause 4.5.7) currently associated with this MBS User Data Ingest Session. Present only if all constituent MBS Distribution Sessions are in the ESTABLISHED or ACTIVE state. | |
| Active periods | 0..* | MBS Application Provider | Periods of time during which the MBS User Data Ingest Session and all its subordinate MBS Distribution Sessions are active in the MBS System. If omitted, the MBS User Data Ingest session and all its subordinate MBS Distribution Sessions are intended to be active until further notice. |
The MBS User Data Ingest Session is composed of one or more MBS Distribution Sessions (see clause 4.5.6 below) and these shall be provisioned in the same operation as the enclosing MBS User Data Ingest Session. It is not valid for an MBS User Data Ingest Session to have no MBS Distribution Sessions defined.
MBS Distribution Sessions may be added to or removed from an MBS User Data Ingest Session by the MBS Application Provider at any time, subject to the minimum number specified above. The MBS User Service Announcement may need to change as a consequence to refer to a revised set of corresponding MBS Distribution Session Announcements.
4.5.6 MBS Distribution Session parameters p. 25
This entity models an MBS Distribution Session, as provisioned by the MBS Application Provider and as managed by the MBSF. This MBSF subsequently uses this information to provision a corresponding MBS Distribution Session in the MBSTF.
The following parameters assigned by the MBS Application Provider may be updated by the MBS Application Provider at any time:
- Target service areas,
- MBS Frequency Selection Area (FSA) Identifier (applicable only to broadcast Service type),
- QoS information,
- Target UE classes as defined in clause 6.19 of TS 23.247.
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| Distribution Session Identifier | 1..1 | MBSF | An identifier for this MBS Distribution Session that is unique within the scope of the MBS User Service (see clause 4.5.3). |
| State | 1..1 | The current state of the MBS Distribution Session: INACTIVE, ESTABLISHED, ACTIVE or DEACTIVATING (see clause 4.6.1). | |
| MBS Session Context | 1..* | As defined in clause 6.9 of TS 23.247 (see NOTE 1). There shall be one MBS Session Context associated with the MBS Distribution Session unless multiple Target service areas are specified (see below). | |
| MB-UPF tunnel endpoint address | 0..1 | The tunnel endpoint address of the MB-UPF that supports this MBS Distribution Session at reference point Nmb9 (see NOTE 1, NOTE 4). | |
| MBMS GW tunnel endpoint address | 0..1 | The tunnel endpoint address of the MBMS GW that supports this MBS Distribution Session at reference point SGi-mb (see NOTE 1, NOTE 4). | |
| User Plane traffic flow information | 0..1 | Details of the MBS-4-MC User Plane traffic flow to be used by the MBSTF for this MBS Distribution Session, including the multicast group destination address and port number to be used inside the unicast tunnel at reference point Nmb9 (see NOTE 1). This parameter is mandatory except in the case of Packet Distribution Method operating in Forward-only mode, in which case multicast-addressed packets ingested at reference point Nmb8 are relayed to Nmb9 without changing their address. | |
| MBS Session Identifier | 0..1 | MBSF or MBS Application Provider | The Temporary Mobile Group Identity (TMGI) or Source-Specific Multicast (SSM) IP address of the MBS Session supporting this MBS Distribution Session (see NOTE 2). Multiple MBS Distribution Sessions within the scope of the same MBS User Service may share the same value if they are location-dependent MBS Services, as defined in clause 6.2.3 of TS 23.247. TMGI values are allocated by the MBSF in conjunction with the MB-SMF unless supplied by the MBS Application Provider at the time of provisioning. |
| Target service areas | 0..* | MBS Application Provider | The set of regions comprising the MBS service area in which this MBS Distribution Session is to be made available (see NOTE 2). The provided set of regions shall be disjoint with that of every other MBS Distribution Session sharing the same MBS Session Identifier. A unique MBS Session Context shall be associated with the MBS Distribution Session for each declared service area, distinguishable by its Area Session Identifier. |
| MBS Frequency Selection Area (FSA) Identifier | 0..1 | (Applicable only to broadcast Service type.) Identifies a preconfigured area within which, and in proximity to, the cell(s) announce the MBS FSA ID and the associated frequency corresponding to this MBS Distribution Session (see NOTE 3). | |
| Target UE classes | 0..* | Indicates whether this MBS Distribution Session is suitable for consumption by NR RedCap UEs and/or non-NR RedCap UEs as defined in clause 6.19 of TS 23.247. | |
| Location-dependent service flag | 0..1 | An indication that this MBS Distribution Session corresponds to a location-dependent MBS Session. If the flag is unset or omitted, the MBS Distribution Session is not location-dependent. | |
| Multiplexed service flag | 0..1 | If set, all MBS Distribution Sessions in the scope of the same parent MBS User Data Ingest Session with identical or empty sets of Target service areas shall be multiplexed onto the same MBS Session. All MBS Distribution Sessions in the multiplex shall be assigned the same MBS Session Identifier. | |
| Restricted membership flag | 0..1 | (Applicable only to multicast Service type.) An indication that this MBS Distribution Session is restricted to a set of UEs according to their current subscription status in the MBS System. If the flag is set, only UEs in the restricted set are permitted to join thls MBS Distribution Session; otherwise, any UE is permitted to join. | |
| QoS information | 0..1 | A 5G QoS Identifier (5QI) TS 23.501 to be applied to the traffic flow for this MBS Distribution Session (see NOTE 2). The 5QI information is used by the MBSF to set the Quality of Service for the MBS Session by interacting with the PCF at reference point Nmb12. | |
| Maximum content bit rate | 1..1 | The maximum bit rate for content in this MBS Distribution Session. | |
| Maximum content delay | 0..1 | The maximum end-to-end content distribution delay that is tolerated for this MBS Distribution Session by the MBS Application Provider. | |
| Distribution method | 1..1 | The distribution method for this MBS Distribution Session, as defined in clause 6. | |
| Operating mode | 0..1 | The operating mode in the case where multiple modes are defined in clause 6 for the indicated distribution method. | |
| FEC configuration | 0..1 | Configuration for Application Layer FEC (AL-FEC) information added by the MBSTF to protect this MBS Distribution Session. The AL-FEC scheme shall be identified using a term from the Reliable Multicast Transport (RMT) controlled vocabulary of FEC Encoding IDs [17] expressed as a fully-qualified URI, e.g. urn:ietf:rmt:fec:encoding:0. The overhead of AL-FEC protection shall be specified as a proportion of the (unprotected) MBS data, e.g. 1.1 for 10% overhead. Additional scheme-specific parameters may be signalled in the form of uncontrolled name-value pairs. | |
| Transport security protection | 1..1 | A flag indicating whether transport security protection is required by the MBS Application Provider for this MBS Distribution Session. The MBSSF determines whether the control plane security procedure (see NOTE 5) or the user plane security procedure is selected. (See annex W of TS 33.501 for details of these procedures.) | |
| Traffic marking information | 0..1 | MBS Application Provider or MBSF | Information (e.g. a Differentiated Services Code Point) used by the MBSTF to mark the multicast packets that it conveys to the MB-UPF at reference point Nmb9. |
|
NOTE 1:
Internal parameter not exposed to the MBS Application Provider.
NOTE 2:
Parameter not relevant to the MBSTF.
NOTE 3:
Used to guide frequency selection by the UE for a broadcast MBS Session.
NOTE 4:
At least one of MB-UPF tunnel endpoint address or MBMS GW tunnel endpoint address shall be present.
NOTE 5:
The control plane security procedure (see clause W.4.1.2 of TS 33.501) is applicable only to Multicast MBS Session(s).
|
|||
An MBS Distribution Session Announcement (see clause 4.5.8 below) shall be associated with an MBS Distribution Session when the latter is in the ESTABLISHED or ACTIVE state.
The following MBS Distribution Session parameters are additionally relevant when the distribution method is the Object Distribution Method:
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| Object acquisition method | 1..1 | MBS Application Provider | Indicates whether the objects(s) to be acquired and possibly distributed as part of the corresponding MBS User Data Ingest Session are to be pushed into the MBSTF by the MBS Application Provider or whether they are to be pulled from the MBS Application Provider by the MBSTF. In the latter case, the Object acquisition method indicates whether the object(s) are to be retrieved once from the MBS Application Provider at the start of each active period of the corresponding MBS User Data Ingest Session, or whether the MBSTF is required to check their validity periodically, for example once per rotation of an object carousel. When a reference to an object manifest is provided as the Object acquisition identifiers, it is the responsibility of the MBSTF to check for updates to the object manifest itself in an efficient manner. |
| Object acquisition identifiers | 0..* | Directly or indirectly identifies the object(s) to be ingested and distributed by the MBSTF during this MBS Distribution Session. This could be the ingest URL of the object, the ingest URL of a manifest describing a set of objects or the ingest URL of an Application Service Entry Point document. For both pull- and push-based object acquisition, values are expressed as URL paths to be resolved relative to the Object ingest base URL. Constraints on this parameter are specified in Table 6.1-1. In particular, when referencing an object manifest, exactly one object acquisition identifier shall be present. | |
| Object ingest base URL | 0..1 | MBS Application Provider or MBSF | In the case of push-based object acquisition, a URL indicating the host part and base path on the MBSTF to which objects are published. In this case, the value shall be nominated by the MBSF and shall be unique for all MBS Distribution Sessions within the MBS System. In the case of pull-based object acquisition, a URL indicating a host part and base path on the MBS Application Provider's origin server (or, in the case of the User Service Announcement Channel, on the MBS AF) relative to which objects lacking an absolute URL are acquired. In this case, the value shall be nominated by the MBS Application Provider (or, in the case of the User Service Announcement Channel, by the MBSF) and need not be unique. When present, this URL prefix is replaced by the MBSTF with the Object distribution base URL prior to distribution of ingested objects. If omitted, nothing is substituted in the content ingest URL when forming the object distribution URL. |
| Object distribution base URL | 0..1 | MBS Application Provider | A URL prefix substituted by the MBSTF in place of the Object ingest base URL prior to distribution of ingested objects. If present, the optional Object ingest base URL shall also be present. If omitted, the object distribution URL is the same as the object ingest URL. |
| Object repair base URL | 0..1 | MBSF | A URL prefix substituted by the MBSTF Client in place of the Object distribution base URL when repairing objects not received completely intact from this MBS Distribution Session (see NOTE). The value shall point to the MBS AS. Present only when object repair is provisioned for this MBS Distribution Session. |
|
NOTE:
Parameter not relevant to the MBSTF.
|
|||
The following MBS distribution session are additionally relevant when the distribution method is the Packet Distribution Method:
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| Packet ingest method | 1..1 | MBS Application Provider | Indicates whether packets are to be ingested using multicast ingest or unicast ingest. Multicast ingest is valid for Proxy mode only. In this case, the MBSTF shall join a Source-Specific Multicast (SSM) group indicated in MBSTF ingest endpoint addresses parameter. Unicast ingest is valid for Proxy mode and Forward-only mode. In this case, the MBSTF shall allocate a listening IP address and port number for packet ingest and shall return it to the MBSF in the MBSTF ingest endpoint addresses parameter below. |
| MBSTF ingest endpoint addresses | 1..1 | MBS Application Provider, MBSF, MBSTF | The endpoint addresses used by the MBS Application Provider and MBSTF to establish a connection at reference point Nmb8 prior to the commencement of this MBS User Data Ingest Session. In the case of Proxy mode, this shall be the Source-Specific Multicast (SSM) endpoint addresses (including the source IP address, destination multicast group address and destination UDP port) nominated by the MBS Application Provider or else by the MBSF. In the case of Forward-only mode, this shall be the IP addresses and UDP port numbers at the source and destination ends of the content ingest tunnel, nominated respectively by the MBS Application Provider and the MBSTF. |
4.5.7 MBS User Service Announcement parameters p. 29
This entity models an MBS User Service Announcement, which is compiled by the MBSF and used to advertise the current or imminent availability of an MBS User Service in the MBS System. The baseline parameters for an MBS User Service Announcement are listed in Table 4.5.7-1 below:
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| External service identifiers | 1..* | MBS Application Provider | A unique identifier used by the MBSF Client to distinguish between MBS User Services. If assigned in a globally unique manner, this identifier may be useful to the MBSF Client in correlating the MBS User Service with the same service delivered by a different system. |
| Service class | 1..1 | The class of the MBS User Service, expressed as a term identifier from a controlled vocabulary. | |
| Start date-time | 0..1 | The point in time from which this MBS User Service Announcement is valid. If not present, the announcement is already valid. | |
| End date-time | 0..1 | The point in time after which this MBS User Service Announcement is no longer valid. If not present, the announcement is valid indefinitely. | |
| Service names | 1..* | A set of distinguishing names for the MBS User Service, one per language. | |
| Service descriptions | 1..* | A set of descriptions of the MBS User Service, one per language. | |
| Main service language | 0..1 | The main language of the MBS User Service. | |
| MBS Distribution Session Announcements | 1..1 | MBSF | The set of MBS Distribution Session Announcements (see clause 4.5.8) currently associated with this MBS User Service Announcement. |
4.5.8 MBS Distribution Session Announcement parameters p. 30
This entity models an MBS Distribution Session Announcement, which is compiled by the MBSF and used to advertise the current or imminent availability of an MBS Distribution Session in the MBS System. The baseline parameters for an MBS Distribution Session Announcement are listed in Table 4.5.8-1 below:
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| MBS Session Identifier | 1..1 | MB-SMF | The Temporary Mobile Group Identity (TMGI) or Source-Specific Multicast (SSM) IP address of the MBS Distribution Session from which this announcement is derived. |
| MBS Frequency Selection Area (FSA) Identifier | 0..1 | MBS Application Provider or MB-SMF | (Broadcast MBS Session only.) IIdentifies a preconfigured area within which, and in proximity to, the cell(s) are announcing the MBS FSA ID and the associated frequency corresponding to this MBS Distribution Session Announcement (see NOTE). |
| Target UE classes | 0..* | MBS Application Provider | (Broadcast MBS Session only.) Indicates whether the MBS Distribution Session described by this announcement is suitable for consumption by NR RedCap UEs and/or non-NR RedCap UEs as defined in clause 6.19 of TS 23.247. |
| Distribution method | 1..1 | MBS Application Provider | The distribution method (as defined in clause 6) of the MBS Distribution Session from which this announcement is derived. |
| Session Description parameters | 1..* | MBSF | Additional parameters needed to receive the MBS Distribution Session from which this announcement is derived, including relevant User Plane traffic flow parameters. |
| Service protection description | 0..1 | MBSSF | The security parameters for the MBS Distribution Session (see clause W.4.2 of TS 33.501), including:
|
|
NOTE:
Used to guide frequency selection by the UE for a broadcast MBS Session.
|
|||
The following session announcement parameters are additionally relevant when Distribution method above indicates the Object Distribution Method:
| Parameter | Cardinality | Assigner | Description |
|---|---|---|---|
| Object distribution schedule | 0..1 | MBS Application Provider | A schedule indicating when individual objects are to be delivered on the corresponding MBS Distribution Session. Present only when this information has been provided in the Object acquisition identifiers of the corresponding MBS Distribution Session (see Table 4.5.6-2). |
| Object distribution base URL | 0..1 | A URL prefix substituted by the MBSTF Client with the Object repair base URL when repairing objects not received completely intact from the corresponding MBS Distribution Session. Present only when object repair is provisioned for the corresponding MBS Distribution Session. | |
| Object repair base URL | 0..1 | MBSF | The base URL of the MBS AS to be used for object repair of the corresponding MBS Distribution Session. Present only when object repair is provisioned for the corresponding MBS Distribution Session. |
4.5.9 Mapping of MBS Distribution Session to MBS Session Context p. 31
Except when it is in the INACTIVE state, an MBS Distribution Session in the MBSF is associated with an MBS Session Context in the MB-SMF. When the MBSF invokes the Nmbsmf_MBSSession service, the parameters defined in clause 6.9 of TS 23.247 shall be populated as indicated in Table 4.5.9-1 below.
| MBS Session Context parameter | Source | Clause | Source parameter |
|---|---|---|---|
| State | MBS Distribution Session. | 4.5.6 | State. |
| Source-Specific Multicast (SSM) IP address | MBS Distribution Session. | 4.5.6 | MBS Session Identifier |
| TMG | |||
| MBS Service Area | MBS Distribution Session. | 4.5.6 | Target service area (see NOTE 2) |
| Area Session Identifier | Assigned by MB-SMF. | 4.5.6 | Location-dependent service flag |
| MBS Frequency Selection Area (FSA) ID (see NOTE 1) | MBS Distribution Session. | 4.5.6 | MBS Frequency Selection Area |
| NR RedCap UE Information (see NOTE 1) | MBS Distribution Session | 4.5.6 | Target UE classes |
| MB-SMF | Not applicable to MB-SMF. | N/A | Not applicable. |
| AMF | Discovered by MB-SMF | N/A | Not applicable. |
| SMF | Selected by AMF. | N/A | Not applicable. |
| PCF | [Selected by MBSF or MB-UPF.] | N/A | Not applicable. |
| QoS (flow) information | MBS Distribution Session. | 4.5.6 | QoS information |
| Tunnel Endpoint Identifier (TEID) for distribution | Assigned by MB-SMF. | N/A | Not applicable. |
| IP multicast and source address for data distribution | ? | N/A | Not applicable. |
| NG-RAN IP address for data distribution | Selected by MB-SMF. | N/A | Not applicable. |
| NG-RAN Node ID(s) | Not applicable to MB-SMF. | N/A | Not applicable. |
| UE IDs | Not applicable to MB-SMF. | N/A | Not applicable. |
|
NOTE 1:
Applicable to Broadcast MBS Session only.
NOTE 2:
Target service area is signalled to the MBSF at reference point Nmb10/Nmb5 in the form of a Tracking Area Identifier (TAI) list and/or Cell ID list. External-facing target service area identification at reference point N33 is translated by the NEF into the appropriate form(s) as required.
|
|||
In addition, the following parameters to the Nmbsmf_MBSSession_Create service operation defined in clause 9.1.3.6 of TS 23.247 shall be populated as indicated in Table 4.5.9-2 below.
| MBSSessionCreate input parameter | Source | Clause | Source parameter |
|---|---|---|---|
| MBS Service type | MBS User Service | 4.5.3 | Service type |
| MBS activation time | MBS User Data Ingest Session | 4.5.5 | Active period |
| MBS termination time | |||
| Indication that any UE may join (see NOTE) | MBS Distribution Session | 4.5.6 | Restricted membership flag |
| [MBS Service requirements or MBS Session information] | MBS Distribution Session | 4.5.3 | QoS information |
| Data Network Name (DNN) | Selected by MBSF based on MBS Application Provider authorisation. | N/A | Not applicable. |
| Single-Network Slice Selection Assistance Information (S-NSSAI) | N/A | Not applicable. |
4.5.10 Object manifest parameters p. 32
An object manifest describes a set of objects to be distributed in an MBS Distribution Session that is provisioned in OBJECT_COLLECTION or OBJECT_CAROUSEL operating mode. For each such object, the baseline properties listed in Table 4.5.10-1 below are defined.
| Parameter name | Cardinality | Description |
|---|---|---|
| Location | 1..1 | The URL from which the object is to be ingested by the MBSTF. |
| Repetition period | 0..1 | The periodicity of the object in the MBS Distribution Session, expressed in appropriate time units (see NOTE). If omitted, the MBSTF shall determine the periodicity of the object. |
| Update period | 0..1 | The maximum period of time that the MBSTF waits after acquiring the object and before checking for changes to the object at its origin Location (see NOTE). In case of conflicting information, cache control metadata provided by the object origin should take precedence over this parameter. If omitted, the MBSTF shall not attempt to check for updates to the object. Any changes to the object that are detected by the MBSTF shall be reflected in the MBS Distribution Session at the earliest opportunity and the replacement of an object with a more up-to-date version shall be signalled to the MBSTF Client. |
| Earliest fetch time | 0..1 | The MBSTF shall fetch the object no sooner than this time. If omitted, the object shall be present at the origin indicated by Location and the MBSTF may fetch it at a time of its choosing. |
| Latest fetch time | 0..1 | The MBSTF shall fetch the object no later than this time. If omitted, the object shall be present at the origin indicated by Location and the MBSTF may fetch it at a time of its choosing. |
|
NOTE:
Not applicable to OBJECT_COLLECTION operating mode.
|
||
In addition, it shall be possible to specify an update period for the object manifest itself.
- When a pull-based object acquisition method is provisioned, the MBSTF shall poll for updates to the object manifest at this interval.
- When a push-based object acquisition method is provisioned, any update period indicated in the object manifest is ignored by the MBSTF.
