hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
00c630369f4492b30b380be367f5dbf7 | 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... |
00c630369f4492b30b380be367f5dbf7 | 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 ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3 Common functional model description
| |
00c630369f4492b30b380be367f5dbf7 | 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 fu... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.2 Functional entities description
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.2.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.2.2 Application plane
| The description of the application plane entities in 3GPP TS 23.280 [3] applies.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.2.3 Signalling control plane
| The description of the signalling control plane entities in 3GPP TS 23.280 [3] applies.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.3 Reference points
| |
00c630369f4492b30b380be367f5dbf7 | 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].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.3.2 Application plane
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.3.2.1 General
| The definition of the application plane reference points in 3GPP TS 23.280 [3] applies.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.3.3 Signalling control plane
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.3.3.1 General
| The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
00c630369f4492b30b380be367f5dbf7 | 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 ... |
00c630369f4492b30b380be367f5dbf7 | 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 t... |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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].
|
00c630369f4492b30b380be367f5dbf7 | 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... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.3.5 Functional model for off-network operation via MC service capable 5G ProSe UE-to-UE relay(s)
| Figure 5.3.5-1 shows the functional model for off-network operation via MC service capable 5G ProSe UE-to-UE relay(s).
Figure 5.3.5-1: Functional model for MC service off-network operation via MC service capable 5G ProSe UE-to-UE relay(s)
The number of MC service capable 5G ProSe UE-to-UE relays between MC service ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.4 MCPTT functional model description
| |
00c630369f4492b30b380be367f5dbf7 | 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 referenc... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.5 MCVideo functional model description
| |
00c630369f4492b30b380be367f5dbf7 | 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 refere... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5.6 MCData functional model description
| |
00c630369f4492b30b380be367f5dbf7 | 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 entit... |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6 Application of functional models and deployment scenarios
| |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.2 On-network architectural model
| |
00c630369f4492b30b380be367f5dbf7 | 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
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.2.2 Application services layer
| |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.2.4 5GS
| The 5GS provides data connectivity and services with QoS control for the support of MC service sessions.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.3 Deployment scenarios
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.3.1 Administration of MC service, SIP core and 5GS
| |
00c630369f4492b30b380be367f5dbf7 | 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 organi... |
00c630369f4492b30b380be367f5dbf7 | 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]... |
00c630369f4492b30b380be367f5dbf7 | 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 serv... |
00c630369f4492b30b380be367f5dbf7 | 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... |
00c630369f4492b30b380be367f5dbf7 | 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 par... |
00c630369f4492b30b380be367f5dbf7 | 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... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.3.2 Resource management of MC service sessions by SIP core and MC service server
| |
00c630369f4492b30b380be367f5dbf7 | 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 ... |
00c630369f4492b30b380be367f5dbf7 | 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
|
00c630369f4492b30b380be367f5dbf7 | 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
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.4 Involved business relationships
| |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 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 ... |
00c630369f4492b30b380be367f5dbf7 | 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 ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.5 Off-network architectural model
| |
00c630369f4492b30b380be367f5dbf7 | 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 f... |
00c630369f4492b30b380be367f5dbf7 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 6.5.3 UE 4
| The UE 4 represents one or more UEs with the same functionality as UE 3.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 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.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7 MC procedures for 5GS
| |
00c630369f4492b30b380be367f5dbf7 | 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], 3GPP TS 23.283 [23] and 3GPP T... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.2 MC service resource management (on-network)
| |
00c630369f4492b30b380be367f5dbf7 | 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, Q... |
00c630369f4492b30b380be367f5dbf7 | 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 resour... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.2.3 Request for unicast resources at session establishment – MC service server based
| |
00c630369f4492b30b380be367f5dbf7 | 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, Q... |
00c630369f4492b30b380be367f5dbf7 | 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 of... |
00c630369f4492b30b380be367f5dbf7 | 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... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.2.5 Request for media resources from MC service server
| |
00c630369f4492b30b380be367f5dbf7 | 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) ... |
00c630369f4492b30b380be367f5dbf7 | 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 communic... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3 MC service over 5G MBS
| |
00c630369f4492b30b380be367f5dbf7 | 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 s... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2 Information flows for 5G MBS
| |
00c630369f4492b30b380be367f5dbf7 | 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-e... |
00c630369f4492b30b380be367f5dbf7 | 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
Desc... |
00c630369f4492b30b380be367f5dbf7 | 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: MapGroup... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.4 Void
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.5 Void
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.6 Void
| |
00c630369f4492b30b380be367f5dbf7 | 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
Stat... |
00c630369f4492b30b380be367f5dbf7 | 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 s... |
00c630369f4492b30b380be367f5dbf7 | 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 ses... |
00c630369f4492b30b380be367f5dbf7 | 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 se... |
00c630369f4492b30b380be367f5dbf7 | 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 ses... |
00c630369f4492b30b380be367f5dbf7 | 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
St... |
00c630369f4492b30b380be367f5dbf7 | 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 Q... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.14 Media distribution response
| Table 7.3.2.14-1 describes the information flow media distribution response from an MC Service server (5G MBS session control role) that has a desired 5G MBS session to the MC service server.
Table 7.3.2.14-1: Media distribution response
Information element
Status
Description
MBS session ID
M
MBS session identif... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.15 Media distribution release
| Information flow for Media distribution release is reused without modification as specified in clause 10.7.2.10 of 3GPP TS 23.280 [3].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.2.16 MBS session announcement acknowledgement
| Table 7.3.2.16-1 describes the information flow of an MBS session announcement acknowledgement message sent from the MC service clients to the MBS service server, to acknowledge the reception of the MBS session announcement.
Table 7.3.2.16-1: MBS session announcement acknowledgement.
Information element
Status
Des... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3 Procedures for usage of 5G MBS
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.1 MBS session creation and MBS session announcement
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 7.3.3.1.1 General
| The procedures in this clause describe how MBS session creation and MBS session announcement can be used for the transmission of MC service group communication data over either broadcast or multicast MBS sessions. The MBS session can either be created with or without dynamic PCC rule, where the latter requires less int... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.