hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.9.2 Requirements
|
For MC services over a 5G system with EPS interworking, inter-system mobility between 5GC and EPC/E-UTRAN of MC service UEs shall be supported by the network based on the capabilities and procedures defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], and 3GPP TS 23.503 [9].
For the case that seamless session continuity is required for MC services, e.g. for MCPTT services, EPS interworking with N26 (interface between AMF in 5GC and MME in EPC) is required for inter-system change.
The MC system should be able to subscribe/unsubscribe to notification capabilities of specific events from the network related to EPS interworking. Thereby, the MC system can identify whether an MC service UE is registered on 5GS or EPS.
4.10 Use of 5G ProSe UE-to-UE relay
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.10.1 General
|
The MC service shall support the capabilities for 5G ProSe UE-to-UE single hop relay. For this matter, 5G ProSe Layer-2 and 5G ProSe Layer-3 UE-to-UE relaying techniques can be utilized, as described in 3GPP TS 23.304 [17].
A 5G ProSe UE-to-UE relay supporting MC service UE provides means of connectivity and relaying of MC traffic from a MC service UE to another MC service UE(s) via a MC UE Relay. For this matter, the 5G ProSe UE-to-UE Relay Discovery service allows the MC service remote UE to discover a potential UE-to-UE relay supporting MC service in its proximity as described in 3GPP TS 23.304 [17]. Upon its discovery, the 5G ProSe Direct UE-to-UE Relay Communication functionality is utilized to achieve communication to provide the MC service between MC UEs, relaying MC traffic via the UE-to-UE relay UE over the NR PC5 reference point.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.10.2 5G ProSe UE-to-UE relay service requirements
|
In order to enable 5G ProSe UE-to-UE relaying capabilities – whether based on Layer-3 or Layer-2 UE-to-UE relaying techniques, the MC system provides the appropriate parameters and configurations to the MC service UE(s).
As defined in 3GPP TS 23.304 [17], among these parameters are: Relay Service Code(s) (RSCs) which can be associated to a certain MC service group, User Info, ProSe Layer-2 Group ID and ProSe Group IP multicast address. Moreover, the MC service group ID is resolved to the ProSe Layer-2 Group ID and ProSe Group IP multicast address, which are utilized within the 5G ProSe Relay Discovery and 5G ProSe Direct Communication procedures, as described in 3GPP TS 23.304 [17]. Furthermore, the RSCs are utilized to restrict the necessary UE-to-UE relay service and related procedures within members of a certain MC service group.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.11 Support of the 5GS congestion information exposure using L4S
|
Based on the request from the MC system, the 5G system can expose network congestion information on the media path between the MC service server and MC service UE to enable reacting accordingly, e.g., adjust the application layer bit rate at the media sender side.
The 5G System can support Explicit Congestion Notification (ECN) marking for Low Latency, Low Loss and Scalable Throughput (L4S) support as defined in 3GPP TS 23.501 [7], clause 5.37.3. When supported and enabled, the 5G System is applying ECN marking for L4S on a per QoS flow basis in the uplink and/or downlink direction and may be used for GBR and non-GBR QoS flows.
To support this feature on a service data flow, the MC service client and MC service server are capable of supporting the L4S handling including e.g., parsing the L4S ECN mark in the IP header, reporting the L4S feedback about downlink and/or uplink direction. The MC service server enables this feature by initiating the request for L4S marking towards the network (either directly towards PCF or indirectly via NEF).
Related procedures are specified in clause 7.7.
NOTE 1: The activation of ECN marking can also be triggered via the 5G core (SMF or PCF) based on either a dynamic or a predefined PCC rule, or dynamically upon the detection of L4S traffic in the IP header.
NOTE 2: The details related to MC service server and MC service UE upon reception of congestion information, e.g., including media handling, codec and bit rate negotiation are outside the scope of the current document.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.12 Support of MC services over NTN
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
4.12.1 General
|
The MC service UE should utilize satellite access to obtain MC services as specified in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10] and 3GPP TS 23.503 [9].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5 MC system functional model
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.1 General
|
The functional model for the MC services architecture is defined as a series of planes to allow for the breakdown of the architectural description. Each plane is expected to operate in an independent manner, providing services to the connected planes as and when requested by the connected plane, and requesting services from other planes as required.
In this context, each plane manages on its own behalf:
a) Use of identities: Each plane is responsible for the privacy of that plane's own identities; and
b) Security for that plane: It does not preclude a plane requesting security services from another plane, but that is a decision made within the plane, as to whether to use offered security services or mechanisms within the plane itself.
NOTE: Terminology such as client and server are not meant to imply specific physical implementation of a functional entity.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.2 Description of the planes
|
The following planes are identified:
a) application plane: The application plane provides all of the services (e.g. call control, floor control, video control, data control, conferencing of media, provision of tones an announcements) required by the user together with the necessary functions to support MC service. It uses the services of the signalling control plane to support those requirements.
b) signalling control plane: The signalling control plane provides the necessary signalling support to establish the association of users involved in an MC service, such as an MCPTT call or other type of MC services. The signalling control plane also offers access to and control of services across MC services. The signalling control plane uses the services of session connectivity.
The corresponding session connectivity supporting these planes are defined for the use of 5GS within 3GPP TS 23.501 [7]. The associated resource control to support these planes is defined within 3GPP TS 23.503 [9].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3 Common functional model description
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.1 On-network functional model
|
Each MC service can be represented by an application plane functional model. The corresponding functional model across MC services may be similar but is described by the individual functional entities and reference points that belong to that MC service. Within the application plane for an MC service, a common set of functions as well as reference points is shared across MC services and is referred as the common services core.
The common functional model for the application plane, the functional model for signalling control plane, and the relationship between reference points of MC service application plane and signalling control planes are as defined in clause 7.3.1 of 3GPP TS 23.280 [3] with the only change of having the 5GS as the utilized 3GPP network instead of EPS.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.2 Functional entities description
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.2.1 General
|
Each subclause is a description of a functional entity and does not imply a physical entity.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.2.2 Application plane
|
The description of the application plane entities in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.2.3 Signalling control plane
|
The description of the signalling control plane entities in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3 Reference points
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.1 General reference point principle
|
The protocols on any reference point that is exposed for MC service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [8].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.2 Application plane
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.2.1 General
|
The definition of the application plane reference points in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3 Signalling control plane
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.1 General
|
The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.2 Reference point SIP-1(between the signalling user agent and the SIP core)
|
The SIP-1 reference point, which exists between the signalling user agent and the SIP core for establishing a session in support of MC service, shall use the Gm reference point as defined in 3GPP TS 23.002 [8] (with necessary enhancements to support MC service requirements and profiled to meet the minimum requirements for support of MC services). The SIP-1 reference point fulfils the requirements of the 5G-GC1 reference point, and is used for:
- SIP registration (including the UE's capabilities, for example eMBMS capable, or MBS capable UE) , capability to receive multicast MBS data in RRC_INACTIVE state;
- authentication and security to the service layer;
- event subscription and event notification;
- overload control;
- MBS session management; e.g., MBS session announcement and de-announcement; and
- media negotiation.
NOTE 1: The reference point 5G-GC1 is defined within SA6, and outside of SA2 scope.
NOTE 2: Information related to the UE´s MBS/eMBMS capabilities can be exchanged during either registration or service authorization procedure.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.3 Reference point SIP-2 (between the SIP core and the SIP AS)
|
The SIP-2 reference point, which exists between the SIP core and the SIP AS for establishing a session in support of MC service, shall use the ISC and Ma reference points as defined in 3GPP TS 23.002 [8]. The SIP-2 reference point is used for:
- notification to the MC service server(s) of SIP registration (including the UE's capabilities, for example eMBMS capable, or MBS capable UE, capability to receive multicast MBS data in RRC_INACTIVE state) by the MC service UE;
- authentication and security to the service layer;
- event subscription and event notification;
- session management; and
- media negotiation.
NOTE: Information related to the UE´s MBS/eMBMS capabilities can be exchanged during either registration or service authorization procedure.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.4 Reference point SIP-3 (between the SIP core and SIP core)
|
The description of the SIP-3 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy)
|
The description of the HTTP-1 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server)
|
The description of the HTTP-2 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)
|
The description of the HTTP-3 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.8 Reference point AAA-1 (between the SIP database and the SIP core)
|
The description of the AA1-1 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.9 Reference point AAA-2 (between the SIP core and Diameter proxy)
|
The description of the AA1-2 reference point in 3GPP TS 23.280 [3] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.3.3.10 Reference points N5 and Rx (between the SIP core and the 5GS)
|
The N5 reference point and Rx reference point, which exist between the SIP core and the 5GS, are used for resource management of MC service sessions, e.g. QoS control, as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10] and 3GPP TS 23.503 [9].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.4 Off-network functional model
|
The description of functional model for off-network operation in clause 7.3.2 of 3GPP TS 23.280 [3] applies.
The description of functional model for off-network operation of MCPTT service in clause 7.3.2 of 3GPP TS 23.379 [6] applies.
The description of functional model for off-network operation of MCVideo service in clause 6.1.2 of 3GPP TS 23.281 [4] applies.
The description of functional model for off-network operation of MCData service in clause 6.4.2 of 3GPP TS 23.282 [5] applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.3.5 Off-network single hop relay functional model
|
Figure 5.3.5-1 shows the functional model for off-network operation.
Figure 5.3.5-1: Functional model for MC service off-network single hop relay operation
For a specific MC service, the description of off-network operation is contained in the corresponding MC service TS.
Editor's Note: Additional work is needed to finalize the information flows and information elements to support this functionality.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.4 MCPTT functional model description
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.4.1 On-network functional model
|
Figure 5.4.1-1 shows the functional model for the application plane for an MCPTT system using the 5GS.
Figure 5.4.1-1: MCPTT functional model for application plane
In the functional model shown in figure 5.4.1-1, the following is considered:
- The description of the corresponding functional entities and reference points in 3GPP TS 23.379 [6] applies.
- MCPTT-1, uses the 5G-GC1 reference point as described in clause 4.7 and fulfils the requirements of the 5G-GC1 reference point for MCPTT.
- The description of the MCPTT-4 and MCPTT-7 reference points in 3GPP TS 23.379 [6] applies considering that it utilizes the N6 reference point defined in 3GPP TS 23.501 [7].
- The description of the MCPTT-5 reference point in 3GPP TS 23.379 [6] applies considering that it exists between the MCPTT server and the 5GS. It is used for resource management of MCPTT sessions, e.g. QoS control, and utilizes the N5 reference point or the Rx reference point or the N33 reference point as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], 3GPP TS 23.503 [9] and 3GPP TS 23.247 [15].
- MCPTT-5, utilizing Rx reference point or N5 reference point, may be used when the MCPTT service provider directly interacts with operator's relevant 5GS network function for QoS control for both unicast PDU sessions and MBS sessions (if dynamic PCC is applicable).
- MCPTT-5, utilizing N33 reference point, may be used when the MCPTT service provider is limited by the operational agreement, i.e., indirect interaction with operator's 5GS network functions for QoS control.
- The MCPTT-6 reference point, which exists between the MCPTT server and the 5GS, is used to create an MBS session obtaining multicast or broadcast resources for MCPTT application usage.
- The MCPTT-6 reference point utilizes Nmb13 reference point when the MCPTT service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCPTT service provider domain.
- The MCPTT-6 reference point utilizes Nmb10 reference point when MBSF is used.
- The MCPTT-6 reference point utilizes N33 reference point when the MCPTT service provider is limited by the operational agreement for QoS control, i.e. indirect interaction with operator's 5GS network functions for QoS control is only allowed.
- The MCPTT-6 reference point utilizes Nmb10 or N33+Nmb5 reference point when MCPTT service provider interacts with the Joint BM-SC, MBSF and MBSTF entity to facilitate interworking with LTE.
- For MCPTT-8 reference point, the reference point definition in 3GPP TS 23.379 [6] applies. The MCPTT-8 reference point utilizes the N6mb reference point according to 3GPP TS 23.247 [15].
- The MCPTT-8 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15] when MBSTF is used.
- For interworking with LTE via Joint BM-SC, MBSF and MBSTF entity, the MCPTT-8 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15].
- For MCPTT-9 reference point, the reference point definition in 3GPP TS 23.379 [6] applies. The MCPTT-9 reference point utilizes the N6mb reference point according to 3GPP TS 23.247 [15].
- The MCPTT-9 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15] when MBSTF is used.
- For interworking with LTE via Joint BM-SC, MBSF and MBSTF entity, the MCPTT-9 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.5 MCVideo functional model description
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.5.1 On-network functional model
|
Figure 5.5.1-1 shows the functional model for the application plane for an MCVideo system using the 5GS.
Figure 5.5.1-1: MCVideo functional model for application plane
In the functional model shown in figure 5.5.1-1, the following is considered:
- The description of the corresponding functional entities and reference points in 3GPP TS 23.281 [4] applies.
- MCVideo-1, uses the 5G-GC1 reference point as described in clause 4.7 and fulfils the requirements of the 5G-GC1 reference point for MCVideo.
- The description of the MCVideo-4 and MCVideo-7 reference points in 3GPP TS 23.281 [4] applies considering that it utilizes the N6 reference point defined in 3GPP TS 23.501 [7].
- The description of the MCVideo-5 reference point in 3GPP TS 23.281 [4] applies considering that it exists between the MCVideo server and the 5GS. It is used for resource management of MCVideo sessions, e.g. QoS control, and utilizes the N5 reference point or the Rx reference point or the N33 reference point as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], 3GPP TS 23.503 [9] and 3GPP TS 23.247 [15].
- MCVideo-5, utilizing Rx reference point or N5 reference point, may be used when the MCVideo service provider directly interacts with operator's relevant 5GS network function for QoS control for both unicast PDU sessions and MBS sessions (if dynamic PCC is applicable).
- MCVideo-5, utilizing N33 reference point, may be used when the MCVideo service provider is limited by the operational agreement, i.e., indirect interaction with operator's 5GS network functions for QoS control.
- The MCVideo-6 reference point, which exists between the MCVideo server and the 5GS, is used to create an MBS session obtaining multicast or broadcast resources for MCVideo application usage.
- The MCVideo-6 reference point utilizes Nmb13 reference point when the MCVideo service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCVideo service provider domain.
- The MCVideo-6 reference point utilizes Nmb10 reference point when MBSF is used.
- The MCVideo-6 reference point utilizes N33 reference point when the MCVideo service provider is limited by the operational agreement for QoS control, i.e. indirect interaction with operator's 5GS network functions for QoS control is only allowed.
- The MCVideo-6 reference point utilizes Nmb10 or N33+Nmb5 reference point when MCVideo service provider interacts with the Joint BM-SC, MBSF and MBSTF entity to facilitate interworking with LTE.
- For MCVideo-8 reference point, the reference point definition in 3GPP TS 23.281 [4] applies. The MCVideo-8 reference point utilizes the N6mb reference point according to 3GPP TS 23.247 [15].
- The MCVideo-8 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15] when MBSTF is used.
- For interworking with LTE via Joint BM-SC, MBSF and MBSTF entity, the MCVideo-8 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15].
- For MCVideo-9 reference point, the reference point definition in 3GPP TS 23.281 [4] applies. The MCVideo-9 reference point utilizes the N6mb reference point according to 3GPP TS 23.247 [15].
- The MCVideo-9 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15] when MBSTF is used.
- For interworking with LTE via Joint BM-SC, MBSF and MBSTF entity, the MCVideo-9 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.6 MCData functional model description
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.6.1 On-network functional model
|
Figure 5.6.1-1 shows the generic functional model for the application plane for an MCData system using the 5GS.
Figure 5.6.1-1: Generic MCData functional model for application plane
In the functional model shown in figure 5.6.1-1, the following is considered:
- The description of the corresponding functional entities and reference points in 3GPP TS 23.282 [5] applies.
- MCData-cap-1, uses the 5G-GC1 reference point as described in clause 4.7 and fulfils the requirements of the 5G-GC1 reference point for MCData.
- The description of the MCData-5 reference point in 3GPP TS 23.282 [5] applies considering that it exists between the MCData server and the 5GS. It is used for resource management of MCData sessions, e.g. QoS control, and utilizes the N5 reference point or the Rx reference point or the N33 reference point as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], 3GPP TS 23.503 [9] and 3GPP TS 23.247 [15].
- MCData-5, utilizing Rx reference point or N5 reference point, may be used when the MCData service provider directly interacts with operator's relevant 5GS network function for QoS control for both unicast PDU sessions and MBS sessions (if dynamic PCC is applicable).
- MCData-5, utilizing N33 reference point, may be used when the MCData service provider is limited by the operational agreement, i.e., indirect interaction with operator's 5GS network functions for QoS control.
- The respective functional models supporting MCData capabilities (e.g., SDS, FD, DS, IPcon) over unicast transmissions along with the corresponding reference points (i.e., MCData-cap-1 to MCData-cap-n) described in 3GPP TS 23.282 [5] also apply when the 5G system is used.
- The MCData-6 reference point, which exists between the MCData server and the 5GS, is used to create an MBS session obtaining multicast or broadcast resources for MCData application usage.
- The MCData-6 reference point utilizes Nmb13 reference point when the MCData service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCData service provider domain.
- The MCData-6 reference point utilizes Nmb10 reference point when MBSF is used.
- The MCData-6 reference point utilizes N33 reference point when the MCData service provider is limited by the operational agreement for QoS control, i.e. indirect interaction with operator's 5GS network functions for QoS control is only allowed.
- The MCData-6 reference point utilizes Nmb10 or N33+Nmb5 reference point when MCData service provider interacts with the Joint BM-SC, MBSF and MBSTF entity to facilitate interworking with LTE.
- The MCData-6 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15] when MBSTF is used.
- For interworking with LTE via Joint BM-SC, MBSF and MBSTF entity, the MCData-6 reference point utilizes the Nmb8 reference point according to 3GPP TS 23.247 [15].
- The respective functional models supporting MCData capabilities (e.g., SDS, FD, DS, IPcon) over eMBMS transmissions along with the corresponding reference points (i.e., MCData-cap-1 to MCData-cap-n) described in 3GPP TS 23.282 [5] also apply when the 5G MBS is used.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.7 MC Interworking with LMR systems functional model description
|
The MC service specific functional model and reference point, procedures and information flows for the MC interworking with LMR systems defined in 3GPP TS 23.283 [23] is also applicable for the 5G MC system interworking with LMR systems.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
5.8 Support of MC services via MC gateway UE
|
The support of MC gateway UE to enable MC service access for MC service UE residing on non-3GPP devices, which may or may not host an MC client, follows the functional model and concepts as defined in clause 11 of 3GPP TS 23.280 [3].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6 Application of functional models and deployment scenarios
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.1 General
|
This clause describes the application of the functional models described in clause 5. It also describes deployment scenarios that highlight some of the possible variations in the way that the functional models can be applied in different situations.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2 On-network architectural model
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.1 On-network architectural model diagram
|
Figure 6.2.1-1 below is the on-network architectural model for the MC system solution, where the MC system provides one or more MC services via a single PLMN.
Figure 6.2.1-1: On-network architectural model
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.2 Application services layer
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.2.1 Overview
|
The application services layer includes application functions of one or more MC services and any required supporting functions grouped into common services core.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.2.2 Common services core
|
Common services core is composed of the functional entities described in the common functional model in clause 5.3.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.2.3 MC services
|
MC services are composed of the functional entities described in the corresponding MC service functional models in clause 5.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.3 SIP core
|
The SIP core provides rendezvous (contact address binding and URI resolution) and service control (application service selection) functions, as described in clause 5.3.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.4 5GS
|
The 5GS provides data connectivity and services with QoS control for the support of MC service sessions.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.5 UE 1
|
UE 1 is an MC service UE in on-network mode supporting data connectivity and application(s) related to one or more MC services over the 5GS, or a UE that acts as 5G ProSe UE-to-network relay, or both of the above. It is composed of the corresponding MC service functional entities described in clause 5.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.2.6 UE 2
|
UE 2 is a device using 5G ProSe UE-to-network relay, and supporting application(s) related to one or more MC services. It is composed of the corresponding MC service functional entities described in clause 5.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3 Deployment scenarios
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1 Administration of MC service, SIP core and 5GS
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.1 General
|
This clause describes deployment scenarios in which different administration of MC service, SIP core and 5GS are described, together with the sensitivities of identities and other forms of signalling in those scenarios.
In each of these scenarios, the owner of the devices at each plane may be different from the organization that administers these devices. For example, the MC service provider may own some RAN components within the 5GS even when the 5GS is administered by the PLMN operator, and the MC service UE may be owned by an organization that is independent from PLMN and MC service providers.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.2 Common administration of all planes
|
In this scenario, all planes (application services layer, SIP core and 5GS) are administered by the same party. This is illustrated in figure 6.3.1.2-1 below.
Figure 6.3.1.2-1: Common administration of all services by one operator
Although the identities in each plane are separate as described in 3GPP TS 23.280 [3], there is no particular sensitivity of identities and other information at the application plane, and these may be exposed to the SIP core and the 5GS.
All authorization and authentication mechanisms at each plane, i.e. the application services layer, SIP core and 5GS, shall be separate, but there may be no need for any restrictions in how these are stored and managed; for example the same entity could provide services to each of the application services layer, SIP core and 5GS.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.3 MC service provider separate from SIP core and 5GS
|
In this scenario, as illustrated in figure 6.3.1.3-1, the MC service provider is separate and independent from the PLMN operator, and the MC service is administered independently of the 5GS and SIP core. The PLMN operator administers the 5GS and the SIP core.
Figure 6.3.1.3-1: MC service provider administers MC service separately from SIP core and 5GS
The MC service provider may require that all application services layer identities and other sensitive information are hidden both from the SIP core and the 5GS.
When required by the MC service provider, all authentication and authorization mechanisms, including security roots, at the application services layer are hidden from and not available to the PLMN operator.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.4 MC service provider administers SIP core, separate from 5GS
|
In this scenario, as illustrated in figure 6.3.1.4-1, the MC service provider administers the SIP core, and the MC services and SIP core are independent of the PLMN operator.
Figure 6.3.1.4-1: MC service provider provision of SIP core, separate domain from 5GS
The MC service provider may require that all identities and other sensitive information at the application services layer are hidden from the 5GS. The MC service provider need not hide the identities and signalling at the application services layer from the SIP core. However, the MC service provider may require that identities and other sensitive information between SIP core and SIP client in the MC service UE are also hidden from the 5GS.
All authentication and authorization mechanisms, including security roots, at both application services layer and at SIP signalling plane may need to be hidden from, and not available to, the PLMN operator.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.5 SIP core partially administered by both PLMN operator and MC service provider
|
In this scenario, as illustrated in figure 6.3.1.5-1, the SIP core is partially administered by both parties, for example when the SIP core registrar is administered by the MC service provider, but the SIP core registrar finder and proxy is administered by the PLMN operator.
Figure 6.3.1.5-1: MC service provider partial provision of SIP core, separate domain from 5GS
The MC service provider may require that all identities and signalling at the application services layer are hidden from the 5GS, and may require identities and other sensitive information to be hidden from the PLMN operator administered part of the SIP core.
All authentication and authorization mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.1.6 PLMN operator administers SIP core with SIP identities administered by MC service provider
|
In this scenario, the PLMN operator administers the SIP core. However, the identities used by the SIP core (IMPI and IMPU) for MC service UEs served by the MC service provider are provided from the SIP database of the MC service provider.
Figure 6.3.1.6-1: MC service provider provides identities to PLMN operator SIP core
The MC service provider may require that all identities and signalling at the application services layer are hidden from the SIP core and 5GS.
When required by the MC service provider, all authentication and authorization mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator.
The security roots (authentication keys) required for access to the signalling control plane are not available to the PLMN operator as these are held in the MC service provider's SIP database. However, derived parameters e.g. authentication vectors are provided to the SIP core to allow signalling control plane authentication to take place.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.2 Resource management of MC service sessions by SIP core and MC service server
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.2.1 General
|
This clause describes two different scenarios in which resource management of MC service sessions is performed via the Rx reference point, or N5 reference point, or N33 reference point as defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10] and 3GPP TS 23.503 [9], by either the SIP core or the MC service server with the 5GS (PCF).
These may provide suitable models for each of the scenarios listed in clause 6.3.1. However, there is no direct correlation of any of the scenarios described in this clause to each of the scenarios described in clause 6.3.1.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.2.2 Resource Management of MC service sessions by SIP core
|
In the scenario shown in figure 6.3.2.2-1, resource management of MC service sessions is performed by the SIP core.
Figure 6.3.2.2-1: Resource management of MC service sessions by SIP core
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.3.2.3 Management of MC service sessions by MC service server
|
In the scenario shown in figure 6.3.2.3-1, resource management of MC service sessions is performed by the MC service server.
Figure 6.3.2.3-1: Resource management of MC service sessions by MC service server
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.4 Involved business relationships
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.4.1 General
|
For the relationship between the MC service provider, the MC service organization and the MC service user 3GPP TS 23.280 [3] clause 6 applies.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.4.2 Public network and non-public network utilization
|
For the relationship between MC service provider and the utilization of public networks and/or non-public networks the following service arrangements apply:
- A home public network operator or a home non-public network operator can have service arrangements with multiple MC service providers.
- A MC service provider can have service arrangements with multiple home public network operators and/or home non-public network operators.
- As part of the service arrangement between the MC service provider and the home public network operator/home non-public network operator, the corresponding 5GS user profile can be provided which allows the MC service UEs to register to the home public network operator/home non-public network operator.
- The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.
Figure 6.4.2-1: Business relationships for MC services
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.4.3 NTN utilization
|
Figure 6.4.3-1 shows required additional relationship related to MC services over NTN.
Figure 6.4.3-1: Business relationships for MC services for NTN operator
The home PLMN operator and the MC service provider can have satellite service agreement with multiple satellite service providers to offer MC services over NTN, e.g., for areas with no terrestrial network coverage. The satellite providers guarantee a certain level of transmission performance via considering the type of satellite constellation and their characteristics (e.g., altitude).
For the relationship between the MC service provider, the home PLMN operator and satellite service provider, the following service agreements apply:
- The home PLMN operator and MC service provider can have satellite service agreements with multiple satellite service provider.
- The home PLMN operator and visited PLMN operator can have satellite service agreements with multiple satellite service provider as part of their roaming agreements.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.5 Off-network architectural model
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.5.1 Off-network architectural model diagram
|
Figure 6.5.1-1 shows the off-network architectural model for the MC system solution for 5G inter-UE communication, where no relay function is used.
Figure 6.5.1-1: Off-network architectural model for 5G inter-UE communication where no relay function is used
Figure 6.5.1-2 shows the off-network architectural model for the MC system solution for configuration management and group management. The description in clause 9.3.1 of 3GPP TS 23.280 [3] applies.
Figure 6.5.1-2: Off-network architectural model for configuration management and group management
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.5.2 UE 3
|
The UE 3 is a UE using 5G ProSe and supporting application(s) related to off-network MC service, and it is composed of the corresponding MC service functional entities described in clause 5.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
6.5.3 UE 4
|
The UE 4 represents one or more UEs with the same functionality as UE 3.
6.5.4 Offline common services server
The offline common services server supports configuration applications related to MC service, and it is composed of the corresponding MC service functional entities described in clause 5.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7 MC procedures for 5GS
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.1 General
|
In this clause, only the procedures and information flows which are different from that over EPS are captured. The MC service specific procedures and information flows over 5GS remains the same as specified in 3GPP TS 23.280 [3], 3GPP TS 23.379 [6], 3GPP TS 23.281 [4], 3GPP TS 23.282 [5] and 3GPP TS 23.283 [23] if not specially described in this clause.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2 MC service resource management (on-network)
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.1 General
|
These clauses specify the procedures for resource management for mission critical services. The procedures are utilized by the following MC services:
- MCPTT (as specified in 3GPP TS 23.379 [6]);
- MCVideo (as specified in 3GPP TS 23.281 [4]); and
- MCData (as specified in 3GPP TS 23.282 [5]).
Session management, QoS model and QoS policy control are defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10] and 3GPP TS 23.503 [9].
The information elements associated to the resource management procedures in this clause are derived from the respective communication setup procedures in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.2 Request for unicast resources at session establishment – SIP core based
|
The procedure defined in this clause specifies how communication resources are requested from 5GS at session establishment. If concurrent sessions are used the MC service server may utilize the capability of resource sharing specified in 3GPP TS 23.503 [9]. The exchange of the QoS characteristics of the required resources takes place exclusively by means of direct interaction between SIP core and PCF using N5 reference point or Rx reference point and encompass media type, bandwidth, priority, application identifier and resource sharing information.
Establishment, modification or release of communication resources are managed according to 3GPP TS 23.503 [9]. The procedure is generic to any type of session establishment that requires communication resources.
Procedures in figure 7.1.2-1 show the signalling procedures for the requesting resource at session establishment.
Figure 7.2.2-1: Resource request at session establishment – SIP core based
1. MC service client sends a session establishment request.
2. MC service server receives evaluates the need of communication resources and the use of media resource sharing.
3. MC service server sends a session progress request containing request for communication resources.
4. Session management procedures using PCF policy control enforcement (as defined in 3GPP TS 23.503 [9]) initiated from SIP core local inbound/outbound proxy using direct interaction between SIP core and PCF.
5. The SIP core local inbound/outbound proxy forwards the call control protocol request to the MC service client.
6. The MC service client acknowledges the session progress request with an OK message.
7. The SIP core local inbound/outbound proxy forwards the OK message to the MC service server.
8. The MC service session is established, and resources have been allocated.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.3 Request for unicast resources at session establishment – MC service server based
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.3.1 General
|
The procedure defined in this clause specifies how communication resources are requested from 5GS at session establishment from the MC service server. The required QoS characteristics for resources are sent directly to the PCF via the N5 reference point or Rx reference point from the MC service server. Alternatively, QoS characteristics for resources can be exchanged indirectly utilizing N33 reference point between MC service server and NEF. QoS characteristic information encompasses media type, bandwidth, priority, application identifier, resource sharing information and network slice information. If concurrent sessions are used, the MC service server may utilize the capability of resource sharing specified in 3GPP TS 23.503 [9].
For the request of communication resources by the MC service server via N5 reference point or Rx reference point, or N33 reference point, the MC service client provides to the MC service server the corresponding communication resource details (e.g. IP addresses and ports) of the MC service client and the corresponding media anchoring points.
This procedure is generic to any type of session establishment with the MC service server requesting network resources.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.3.2 Procedure
|
Figure 7.2.3.2-1 describes the procedure for the request of resources at session establishment from the MC service server.
Figure 7.2.3.2-1: Resource request at session establishment – MC service server based
1. The MC service client sends a session establishment request. The request includes, apart from the SDP offer, access resource details, e.g. IP addresses and ports of the MC service client related to the media session.
2. The MC service server evaluates the need of communication resources and use of media resource sharing.
3. The MC service server sends a session progress request to the SIP core.
NOTE: The session progress request does not include a request for network communication resources to be performed by the SIP core.
4. The SIP core local inbound/outbound proxy forwards the session progress request to the MC service client.
5. The MC service client acknowledges the session establishment to the MC service server. This message contains the final negotiated media parameters, e.g. IP addresses and ports related to the media anchoring points received in the SDP answer from the SIP core.
6. To trigger resources allocation, the MC service server sends a request for media resources to 5GS. For direct interaction, the resource allocation request is exchanged between MC service server and 5GS PCF using N5 reference point or Rx reference point. For indirect interaction, the resource allocation request is exchanged between MC service server and 5GS NEF using N33 reference point. The respective procedures are defined in 3GPP TS 23.503 [9]).
7. Session management procedures using PCF policy control enforcement (as defined in 3GPP TS 23.503 [9]) initiated from MC service server either directly via PCF or indirectly via NEF.
8. The MC service session is established, and resources have been allocated.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.4 Request for modification of unicast resources
|
To modify a unicast media flow, the MC service server shall send a resource modification request containing the parameters to be modified, using the call control protocol via the SIP core to the UE. The exchange of the QoS characteristics of the concerned resources takes place exclusively by means of direct interaction between SIP core and PCF.
Possible scenarios when this procedure may be used are:
- Modify the allocation and retention priority for unicast resources;
- Release and resume resources in-between MC service calls when using the chat model; or
- Releasing resources for the media plane should give the option to allow the SIP session to either be torn down or continue.
Procedures in figure 7.2.4-1 are the signalling procedures for the modification of a unicast:
Pre-conditions:
- An MC service session is already in progress;
Figure 7.2.4-1: Media flow modification request
1. MC service server decides to modify the parameters of a unicast bearer (e.g. a request to upgrade the existing MC service call to an MC service emergency or imminent peril call).
2. MC service server sends a session update which includes a resource modification request containing the modified parameters of the unicast bearer.
3. Session management procedures using PCF policy control enforcement (as defined in 3GPP TS 23.503 [9]) initiated by the MC service server using direct interaction between SIP core and PCF.
4. The SIP core local inbound / outbound proxy forwards the session update request to the MC service client.
5. The MC service client acknowledges the call control protocol request with an OK message.
6. The SIP core local inbound / outbound proxy forwards the OK message to the MC service server.
7. The MC service session continues with the modified unicast resources.
NOTE: If multiple audio streams are sent to the UE, additional QoS flows could be required during an established session. Pre-allocation of additional QoS flows already at session establishment could be useful.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.5 Request for media resources from MC service server
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.5.1 General
|
The procedure in this sub clause specifies how to request resources for floor control (or transmission control in MCVideo and MCData) and for the media plane can be handled independently. This procedure utilizes the N5 reference point or Rx reference point for direct interaction between MC service server and 5GS (PCF) and for direct interaction between SIP core and 5GS (PCF). Alternatively, resource requests for the media plane can be exchanged indirectly using N33 reference point between MC service server and NEF.
Resources for transmission control are requested at session establishment, in this case the IMS standard procedures using for direct interaction N5 reference point or Rx reference point as specified in 3GPP TS 23.228 [2] are used. The session description in this procedure shall encompass bandwidth information applicable for the transmission control traffic requirement. At group call setup the request for resources for the media plane is triggered. Either this request is sent directly from the MC service server to 5GS (PCF) or indirectly from the MC service server to 5GS (NEF).
The procedure is optional and is suitable when the procedures for pre-established sessions are used. It may also be used to setup and tear down the media plane used between consecutive group calls in one communication session using the chat call model.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.2.5.2 Procedure
|
The figure 7.2.5.2-1 illustrates the procedure for resource allocation.
Figure 7.2.5.2-1: Request of resources for transmission control and media plane
1. The MC service client sends a request for group affiliation.
2. The MC service client sends a request to the MC service server for establishment of a communication session.
3. The MC service server answer the session establishment request and adjust the bandwidth information in the session description. The requested bandwidth shall be minimized to cover the bandwidth requirements for floor control signalling (or transmission control for MCVideo or MCData).
4. The SIP core request resources towards the 5GS according to the session establishment request.
5. Session management procedures using PCF policy control enforcement (as defined in 3GPP TS 23.503 [9]) initiated by the SIP Core.
6. The session establishment request is completed, and a response is sent towards the MC service client.
7. The MC service client sends a call setup message according to existing procedures.
8. The MC service server sends a session establishment request for resources for the media plane to 5GS, and the media plane is by that established. For direct interaction, the resource allocation request is exchanged between MC service server and 5GS PCF using N5 reference point or Rx reference point. For indirect interaction, the resource allocation request is exchanged between MC service server and 5GS NEF using N33 reference point. The respective procedures are defined in 3GPP TS 23.503 [9]). This request includes media description relevant for the media plane.
9. Session management procedures using PCF policy control enforcement (as defined in 3GPP TS 23.503 [9]) initiated by the MC service server either directly via PCF or indirectly via NEF.
10. Group call is ongoing on the group communication session.
11. The MC service serve sends a release of media resources to 5GS, and the media plane is by that terminated.
12. The PCF performs session termination procedure according to 3GPP TS 23.503 [9].
13. The PCF sends a session release response back to the MC service server.
NOTE 1: The resources for transmission control are retained.
NOTE 2: Step 7-11 can be repeated several times within the life cycle of one communication session.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3 MC service over 5G MBS
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.1 General
|
This subclause defines information flows and procedures for 5G MBS usage that applies to MC services. 5G MBS session can be used by any MC service for any MC service group.
The following subclauses specify the procedures and information flows for the usage of 5G MBS transmission that are utilized by the following MC services:
- MCPTT (as specified in 3GPP TS 23.379 [6]);
- MCVideo (as specified in 3GPP TS 23.281 [4]); and
- MCData (as specified in 3GPP TS 23.282 [5]).
MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above.
The first phase to utilize MBS sessions for MC service media transmission is to have the sessions created hence the network resources are reserved. The MC service server may consider the UE's capabilities and service related information e.g., UE's MBS capabilities, location, MBS listening status report sent by group members when it decides to create or use MBS sessions. The MC service server needs to interact with the 5GC for this matter. During the interaction, the necessary information related to the requested session is determined, e.g., MBS session mode (either a broadcast or a multicast session) and the required QoS profile. This interaction depends on the configuration option under consideration, i.e., whether the MC service server is in trusted domain (limited operations), and whether the session creation is done with or without a dynamic PCC rule.
NOTE 1: It is implementation specific whether the MC service server decides to use multicast or broadcast MBS sessions.
NOTE 2: It is implementation specific whether the MC service server decides to create (one or multiple) MBS sessions for MC media for MC group communications associated to a certain MC group or create (one or multiple) dynamic MBS sessions once the need has emerged, e.g., dynamic MBS sessions to be associated for an ad hoc group.
NOTE 3: It is implementation specific whether an MBS session is associated to one or multiple MC groups, and whether it is re-assigned to other MC groups.
NOTE 4: How the MC service server uses the UE's capabilities and service related information in order to create and use the MBS session is implementation specific.
The information elements describing the MBS session under consideration is then sent to the MC service clients via MBS session announcement, where the latter need to react according to the announced session mode.
If eMBMS and 5G MBS co-exist for MC services, the MC service server may decide to trigger the establishment of an eMBMS bearer to deliver the MC media associated to the MC service group communications, if the target MC service group(s) consists of members with eMBMS capable UE. As a result, the MC service server subsequently needs to send an eMBMS bearer announcement towards the clients camping on LTE.
NOTE 5: It is implementation specific whether the MC service server triggers an eMBMS bearer or a unicast bearer to serve MC service clients camping on LTE.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2 Information flows for 5G MBS
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.1 MBS session announcement
|
Table 7.3.2.1-1 provides the information elements during MBS session announcement, which are sent by the MC service server to the clients. The MBS session announcement includes information elements related to the announced MBS session. Optionally, it includes eMBMS related information elements, if eMBMS and 5G MBS co-exist.
Table 7.3.2.1-1: MBS session announcement
Information element
Status
Description
5G MBS session information
M
Providing the MBS session related information if MC service server decides to use 5G MBS session to deliver MC service group communication data
>MBS session ID
M
The identity of the MBS session used to deliver MC service group communication data. It is either TMGI for broadcast MBS and multicast MBS sessions, or source specific IP multicast address for multicast MBS session
>MBS session mode
M
Indicate the service type of the MBS session, either a multicast MBS session or a broadcast MBS session
>MC service group ID
O
Indicate the MC service group ID associated to the MBS session
>MBS related SDP information
M
SDP related to application-level control signalling or media to be transmitted over the MBS session (e.g., codec, protocol ID, FEC information, IP address and ports)
>List of MBS Service Area information (see NOTE 5)
O
For the case of local MBS services, it indicates either multicast service area identifier(s) for multicast MBS session, or broadcast service area identifier(s) for broadcast MBS session
>MBS session announcement acknowledgement
O
Indicate if the MC service server requires an acknowledgement to the MBS session announcement
>Multicast MBS session related information (see NOTE 1)
O
Additional information to be used by the MC service client to join the multicast MBS session such as PLMN ID of the default PLMN service provider, NID (for the case of SNPN deployments) in case of source specific IP multicast address, DNN, and SNSSAI of the PDU session associated with the multicast MBS session
> UE session join notification (see NOTE 2)
O
Indicate if the MC service server requires a notification from the MC service client once it has joined the multicast MBS session
>Monitoring state
O
Indicate if the MC service client is required to actively monitor the MBS session quality and report it to the MC service server. This is applicable for both multicast and broadcast eMBMS session.
>Frequency (see NOTE 3)
O
Identification of frequency associated with a broadcast MBS session, if multi carrier support is provided
>MBS Frequency Selection Area ID (MBS FSA ID) (see NOTE 3)
O
The frequency associated to a certain broadcast area, if multi carrier support is provided
eMBMS bearer information
O
Providing the 4G eMBMS bearer related information if MC service server decides to use 4G eMBMS additionally with 5G MBS session to deliver MC service group communication data
>TMGI (see NOTE 4)
M
TMGI information
>Alternative TMGI
O
A list of additional alternative TMGI may be included and used in roaming scenarios
>QCI
O
QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5
>List of service area identifier
M
A list of service area identifier for the applicable eMBMS broadcast area
>Frequency
O
Identification of frequency if multi carrier support is provided
>eMBMS related SDP information
M
SDP with media and floor control information applicable to groups that can use this eMBMS bearer (e.g., codec, protocol id, FEC information)
>Monitoring state
O
Indicate if the MC service client is required to actively monitor the eMBMS bearer quality and report it to the MC service server
>ROHC information
O
Indicate the usage of ROHC over the eMBMS bearer and provide the parameters of the ROHC channel to signal to the ROHC decoder
NOTE 1: Such information may be pre-configured in the MC service UE, or provided in any other implementation specific way
NOTE 2: It is applicable for multicast MBS session
NOTE 3: It is applicable for broadcast MBS session
NOTE 4: TMGI for 4G eMBMS bearer can be the same or different with 5G MBS session ID.
NOTE 5: Details of MBS service area information is defined in 3GPP TS 23.247 [15].
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.2 UE session join notification
|
Table 7.3.2.2-1 describes the information flow of UE session joining notification from the MC service client to the MC service server after successfully joining a certain multicast MBS session procedure as defined in 3GPP TS 23.247 [15].
Table 7.3.2.2-1: UE session join notification
Information element
Status
Description
MBS session ID(s)
M
The identity of the multicast MBS session(s) being joined. It is either TMGI or source specific IP multicast address.
MC service ID
M
Identity of the MC service user who is reporting the session status
MBS multicast joining status
M
The multicast listening status can be joined if successfully joined MBS session.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.3 MapGroupToSessionStream
|
Table 7.3.2.3-1 defines the MapGroupToSessionStream to be sent from the MC service server to MC service clients to provide specific required information to receive the media related to a group communication within an MBS session. The MC service can either be MCPTT, MCVideo or MCData services.
Table 7.3.2.3-1: MapGroupToSessionStream
Information element
Status
Description
MC service group ID
M
This element identifies the MC service group related to a group communication to be delivered over the MBS session. The MC service group ID is either MCPTT group ID, MCVideo group ID, or MCData group ID.
Media stream identifier
M
This element identifies the media stream of the SDP used for the group communication within the MBS session. In case separate media streams are used for the audio and video media components in MCVideo services, separate identifiers can be used.
MBS session ID
O
The MBS session identifier if the MapGroupToSessionStream message is not sent on the same session as the MC media
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.4 Void
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.5 Void
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.6 Void
| |
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.7 UnMapGroupFromSessionStream
|
Table 7.3.2.7-1 describes the information flow to disconnect an MC group communication call from an MBS session. It is sent from the MC service server to the MC service client, where the MC service can either be MCPTT, MCVideo or MCData services.
Table 7.3.2.7-1: UnMapGroupFromSessionStream
Information element
Status
Description
MCPTT group ID
M
This element identifies the MC service group related to a group call to be dissociated over the MBS session. The MC service group ID is either MCPTT group ID, MCVideo group ID, or MCData group ID.
Media stream identifier
M
This element identifies the media stream of the SDP, which is no longer used for the group call within the MBS session. In case separate media streams are used for audio and video stream in MCVideo services, a separate identifier is optinally used to identify the audio stream, which is no longer used.
MBS session ID
O
Indicating the MBS session ID, if the information is sent over another MBS session or unicast path
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.8 Discover MBS Session request
|
The usage of Discover MBS Session request is similar to Discover Bearer request for eMBMS as it defined in 3GPP TS 23.280 [3].
Table 7.3.2.8-1 describes the information flow discover MBS session request from the MC service server to another MC service server (MBS session control role).
Table 7.3.2.8-1: Discover MBS session request
Information element
Status
Description
List of MBS service area information
O
A list of MBS service area information for the applicable MBS session service area.
Bandwidth
M
Maximum bandwidth required
5QI
O
Desired 5QI
NOTE: List of MBS service area information is optional and needed once it is applicable with the MBS session ID under consideration.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.9 Discover MBS Session response
|
The usage of Discover MBS Session response is similar to Discover Bearer response for eMBMS as it defined in 3GPP TS 23.280 [3].
Table 7.3.2.9-1 describes the information flow discover MBS session response from an MC service server (MBS session control role) to the MC service server.
Table 7.3.2.9-1: Discover MBS session response
Information element
Status
Description
MBS Session ID(s)
M
List of MBS session IDs and related information
List of MBS service area information (see NOTE)
O
A list of MBS service area identifiers for the applicable MBS session service areas, corresponding to the listed MBS session IDs, over which the request was successful.
Frequency
O
Identification of the frequency if multi-carrier support is provided
5QI
O
Providing feedback related to the applicable 5QI information.
NOTE: List of MBS service area information is optional and needed once it is applicable with the MBS session ID under consideration
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.10 MBS listening status report
|
Table 7.3.2.10-1 describes the information flow of MBS listening status report from the MC service client to the MC service server. The MBS listening status report is applicable to both broadcast and multicast MBS sessions.
Table 7.3.2.10-1: MBS listening status report
Information element
Status
Description
MBS session ID(s)
M
The identity of the MBS session(s) being monitored.
MC service ID
M
Identity of the MC service user who is reporting the session status. It may either be the MCPTT ID, MCVideo ID, or MCData ID.
MBS listening status
M
The listening status per MBS session ID.
MBS reception quality level
O
The reception quality level
Unicast listening status
O
The unicast listening status associated with the unicast delivery.
NOTE: The set of quality levels helps service continuity in broadcast and multicast scenarios. A reception quality level may help to make an efficient switching decision to unicast delivery. How these levels are used is implementation specific.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.11 MBS session de-announcement
|
Table 7.3.2.11-1 describes the information flow of an MBS session de-announcement sent from the MC service server to the MC service clients.
Table 7.3.2.11-1: MBS session de-announcement.
Information element
Status
Description
MBS session ID(s)
M
The identity of the MBS session(s) to be de-announced.
MBS session de-announcement acknowledgement
O
Indicate if the MC service server requires an acknowledgement to the MBS session de-announcement
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.12 MBS session de-announcement acknowledgement
|
Table 7.3.2.12-1 describes the information flow of an MBS session de-announcement acknowledgement message sent from the MC service clients to the MBS service server, to acknowledge the reception of the MBS session de-announcement.
Table 7.3.2.12-1: MBS session de-announcement acknowledgement.
Information element
Status
Description
MC service ID
M
The MC service identity of the MC service client, whose group is no longer associated to the MBS session(s)
MBS session ID(s)
M
The identity of the MBS session(s) to be de-announced.
MBS session de-announcement status
M
The de-announcement status per MBS session ID.
|
92c39d4e31dc10812fa1955d84ca0fc9
|
23.289
|
7.3.2.13 Media distribution request
|
Table 7.3.2.13-1 describes the information flow media distribution request from the MC Service server to an MC service server (5G MBS Session control role) that has a desired 5G MBS session.
The difference compared with the information flow defined in 3GPP TS 23.280 [3] is that in 5G MBS, the information element for QoS is 5QI.
Table 7.3.2.13-1: Media distribution request
Information element
Status
Description
MBS session ID
M
MBS session identifier
Bandwidth
M
Maximum bandwidth required
Separate floor control
M
Whether or not a separate session is required for floor control
SDP information
M
SDP with media and floor control information applicable to groups that can use this MBS session (e.g. codec, protocol id)
5QI
O
Desired 5QI
MC Group ID
O
The MC group id for when the request is sent for a specific group call
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.