4.5 Domain model
26.5023GPP5G Multicast-Broadcast User Service ArchitectureRelease 17TS
4.5.1 User Services domain model
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.
Figure 4.5.1-1: MBS User Services domain model
In the above figure:
1. The MBS Application Provider initiates MBS User Service Provisioning with the MBSF to provision an MBS User Service.
2. 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:
3. 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).
4. 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.
5. 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:
6. The MBS-Aware Application instructs the MBSF Client to activate an MBS User Service by means of MBS User Service Control.
7. 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.
7bis. 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.
8. 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.
9. 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.
4.5.2 Static information model
Figure 4.5.2‑1 shows how the different service and session concepts depicted in figure 4.5.1‑1 above relate to each other. In this figure:
1. The MBS Application Provider provisions the parameters of a new MBS User Service by invoking the Nmbsf service either directly, or via the NEF. This specifies which of the Service announcement modes are to be used to advertise the MBS User Service, as well as descriptive metadata for inclusion in the MBS User Service Announcement.
2. The MBS Application Provider provisions a number of time-bound MBS User Data Ingest Sessions within the scope of the MBS User Service by invoking the Nmbsf service either directly, or via an equivalent Nnef service provided by the NEF. Each MBS User Data Ingest Session includes the details of one or more MBS Distribution Sessions.
– To indicate that it has a restricted MBS service area (i.e. corresponding to a local MBS Service, as defined in clause 6.2.2 of TS 23.247 [5]), an MBS Distribution Session may specify one or more Target service areas. In line with [5], MBS data is not transmitted outside the MBS service area derived from the indicated Target service areas.
– To provision location-dependent variants of an MBS User Service (see clause 6.2.3 of TS 23.247 [5]), a number of MBS Distribution Sessions conveying different MBS data may be provisioned within the scope of the same MBS User Service by setting the Location-dependent service flag on the MBS Distribution Sessions of each variant. Location-dependent MBS Distribution Session variants shall have the same MBS Session Identifier, but they shall have disjoint Target service areas.
– When the Multiplexed service flag is set on the MBS Distribution Session, all MBS Distribution Sessions with an identical (or empty) set of Target service areas shall be multiplexed onto the same MBS Session. The MBS Session Identifier shall be the same for all MBS Distribution Sessions within the multiplex. This feature may be combined with the Location-dependent service flag, in which case each location-dependent multiplex of MBS Distribution Sessions is mapped into a separate MBS Session.
The MBSF provisions additional MBS Distribution Session parameters (denoted in table 4.5.6‑1 as assigned by the MBSF) and exposes some of them back to the MBS Application Provider (as indicated by the NOTE to table 4.5.6‑1).
NOTE 1: The MBSF typically allocates an MBS Session Identifier, such as a Temporary Mobile Group Identity (TMGI) for each MBS Distribution session (see step 4 below) as a side-effect of provisioning, but it is also possible for the Nmbsf service invoker to nominate a particular value during this provisioning step if TMGI allocations are managed externally to the MBSF.
3. The MBS Application Provider may additionally provision an MBS Consumption Reporting Configuration within the scope of the MBS User Service by invoking the Nmbsf service either directly, or via the NEF.
NOTE 2: Reception reporting for MBS User Services is for future study.
Shortly before the current time enters the time window of a provisioned MBS User Data Ingest Session:
4. The MBSF provisions an MBS Session in the MBS System by invoking the Nmbsmf service on the MB‑SMF (see clause 9 of TS 23.247 [5]) to allocate a TMGI (if one has not already been allocated) for each MBS Distribution Session and to create an MBS Session Context for each one. The parameters of the MBS Session Context shall be populated as specified in clause 4.5.9. In response, the MB-SMF provides the MB-UPF ingest information (specifically, the MB‑UPF tunnel endpoint address and traffic flow information to be used by the MBSTF) to the MBSF.
5. The MBSF provisions an MBS Distribution Session in the MBSTF by invoking the Nmbstf service at reference point Nmb2 using the parameters from the newly created MBS Session Context.
6. Using the parameters from the MBS Distribution Session and from the newly created MBS Session Context, the MBSF compiles an MBS User Service Announcement to advertise the availability of the MBS User Service and makes this service access information available by one or more of the Service announcement modes provisioned in the MBS User Service.
NOTE 1 Square brackets after a parameter name indicate multiplicity; parameter names rendered in italics with parentheses are optional. See the following clauses for details.
NOTE 2: Parameters and entities not exposed to the MBS Application Provider via the Nmbsf service at reference point Nmb10 are annotated with the dagger symbol †.
NOTE 3: MBS Session Identifier is defined by clause 6.5.1 of TS 23.247 [5] as a Temporary Mobile Group Identity (TMGI) or a Source-Specific Multicast (SSM) IP address.
Figure 4.5.2-1: MBS User Services static information model
4.5.3 MBS User Service parameters
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.
NOTE 1: Propagation of modified parameter values to the MBS Client in an updated MBS User Service Announcement is subject to implementation-dependent and operational latencies.
Table 4.5.3‑1: Baseline parameters of MBS User Service entity
|
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.
NOTE 2: Reception reporting for MBS User Services is for future study.
4.5.4 MBS Reception Reporting Configuration parameters
Reception reporting for MBS User Services is for future study.
4.5.5 MBS User Data Ingest Session parameters
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.
NOTE: A linkage from the MBS User Data Ingest Session to its parent MBS User Service is additionally required at stage 3. The User Service identifier defined in table 4.5.3‑1 serves this purpose.
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.
Table 4.5.5‑1: Baseline parameters of MBS User Data Ingest Session entity
|
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 is active in the MBS System. If omitted, the MBS User Data Ingest session is 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
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.
With the exception of the MBS Session Identifier (which is immutable after initial assignment) and the Location-dependent service flag (which is immutable after creation), all other parameters assigned by the MBS Application Provider may be updated by the MBS Application Provider when the MBS Distribution Session is in the INACTIVE state.
The baseline parameters for an MBS Distribution Session that are common to all distribution methods are listed in table 4.5.6‑1 below. All parameters are exposed to the MBS Application Provider except where noted otherwise.
Table 4.5.6‑1: Common baseline parameters of MBS Distribution Session entity
|
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 [5] (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[5]. 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). |
|
|
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) [2] 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 Level 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. |
|
|
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. |
|||
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:
Table 4.5.6‑2: Additional MBS Distribution Session parameters for Object Distribution Method
|
Parameter |
Cardinality |
Assigner |
Description |
|
Object acquisition method |
1..1 |
MBS Application Provider |
Indicates whether the objects(s) 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 as part of the corresponding MBS User Data Ingest Session. 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. |
|
Object acquisition identifiers |
1..* |
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, or the ingest URL of a manifest describing a set of objects, or a reference into a manifest describing a set of objects. |
|
|
Object ingest base URL |
0..1 |
MBS Application Provider or MBSF |
A URL prefix substituted by the MBSTF with the Object distribution base URL prior to distribution of ingested objects. Assigned by the MBS Application Provider for the pull-based Object acquisition method. Assigned by the MBSF for push-based object acquisition. If omitted, nothing is removed from 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. The value shall point to the MBS AS. Present only when object repair is provisioned for this MBS Distribution Session. |
The following MBS distribution session are additionally relevant when the distribution method is the Packet Distribution Method:
Table 4.5.6‑3: Additional MBS Distribution Session parameters for 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
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:
Table 4.5.7‑1: Baseline parameters of MBS User Service Announcement entity
|
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..* |
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
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:
Table 4.5.8‑1: Baseline parameters of MBS Distribution Session Announcement entity
|
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.) Identifies 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) |
|
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. |
|
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:
Table 4.5.8‑2: Additional MBS Distribution Session Announcement parameters for 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
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 [5] shall be populated as indicated in table 4.5.9‑1 below.
Table 4.5.9‑1: Mapping of baseline parameters to MBS Session Context parameters
|
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 |
|
TMGI |
|||
|
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 |
|
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: Mapping to Tracking Area Identifier (TAI) list and/or Cell ID list performed by MBSF 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 [5] shall be populated as indicated in table 4.5.9‑2 below.
Table 4.5.9‑2: Mapping of baseline parameters to Nmbsmf_MBSSession_Create parameters
|
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. |
|
|
NOTE: Applicable to Multicast MBS Session only. |
|||