hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.6.2 Procedure
| The procedure for an authorized MC service user in a primary MC system to update initial MC service UE configuration data information in the partner MC system is shown in figure 10.17.6.2-1.
Pre-conditions:
- Primary MC system and partner MC system are interconnected.
- Both MC systems have implemented ACM functiona... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.7 ACM updating MC service user profiles assigned from partner MC system
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.7.1 General
| A primary MC system may request through ACM entities to add a list of its MC service users for migration to a connected partner MC system as specified in clause 10.17.5 ACM user migration management. In case the partner MC system agrees to accept these users for migration it will reply with a response containing assign... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.17.7.2 Procedure
| The procedure for an authorized MC service user in a primary MC system to request MC service user profile update from a partner MC system is shown in figure 10.17.7.2-1.
Pre-conditions:
- Primary MC system and partner MC system are interconnected.
- Both MC systems have implemented ACM functionality.
- When a funct... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18 Recording and replay
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1 Service configuration
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.1 Service ID and user profile
| A recording admin and/or replay user is identified by an MCRec ID. An MCRec ID is associated with one user profile. This is depicted in figure 10.18.1.1-1.
Figure 10.18.1.1-1: The relationship of MC service user, MCRec ID and Recording admin and replay service user profile
One MC service user (MC ID) may have one ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.2 Recording admin service configuration
| Depicted in figure 10.18.1.2-1 is a recording admin service configuration time sequence, representing the general lifecycle of a Recording admin UE using recording admin service.
Figure 10.18.1.2-1 Recording admin UE configuration time sequence and associated configuration data
The recording admin UE is provided w... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.3 Replay service configuration
| Depicted in figure 10.18.1.3-1 is a replay service configuration time sequence, representing the general lifecycle of a Replay UE using replay service.
Figure 10.18.1.3-1 Replay UE configuration time sequence and associated configuration data
The replay UE is provided with initial recording admin UE and/or replay ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4 Information flows for recording admin and replay service user profiles
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4.1 Get recording admin and replay service user profile request
| Table 10.18.1.4.1-1 describes the information flow get recording admin and replay service user profile request from the configuration management client to the configuration management server.
Table 10.18.1.4.1-1: Get recording admin and replay service user profile request
Information element
Status
Description
MCR... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4.2 Get recording admin and replay service user profile response
| Table 10.18.1.4.2-1 describes the information flow get recording admin and replay service user profile response from the configuration management server to the configuration management client.
Table 10.18.1.4.2-1: Get recording admin and replay service user profile response
Information element
Status
Description
R... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4.3 Notification for recording admin and replay service user profile data update
| Table 10.18.1.4.3-1 describes the information flow notification for recording admin and replay service user profile data update from the configuration management server to the configuration management client.
Table 10.18.1.4.3-1: Notification for recording admin and replay service user profile data update
Information... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4.4 Get updated recording admin and replay service user profile data request
| Table 10.18.1.4.4-1 describes the information flow get updated recording admin and replay service user profile data request from the configuration management client to the configuration management server.
Table 10.18.1.4.4-1: Get updated recording admin and replay service user profile data request
Information element... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.4.5 Get updated recording admin and replay service user profile data response
| Table 10.18.1.4.5-1 describes the information flow get updated recording admin and replay service user profile data response from the configuration management server to the configuration management client.
Table 10.18.1.4.5-1: Get updated recording admin and replay service user profile data response
Information eleme... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.5 Procedures for recording admin and replay service user profiles
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.5.1 Get recording admin and replay service user profile
| Pre-conditions:
- The recording admin and replay service user has performed user authentication in the identity management server.
- The UE has secure access to the configuration management server.
Figure 10.18.1.5.1-1: Recording admin and/or replay user obtains the user profile from the network
1. The configura... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.1.5.2 Get updated recording admin and replay service user profile data
| Pre-conditions:
- The recording admin and replay service user has performed user authentication with the identity management server.
- The UE has secure access to the configuration management server.
- The UE has already obtained a recording admin and/or replay service user profile.
Figure 10.18.1.5.2-1: Recordin... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.2 Target group and target user configuration
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.2.1 Store target group configuration at the GMS
| The procedure for store target group configurations at the group management server is described in figure 10.18.2.1-1.
A recording admin shall use this procedure to set/modify/remove target group(s) for recording.
Pre-conditions:
- The recording admin service user has performed user authentication and service autho... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.2.2 Update target MC service user profile data to the CMS
| The procedure for update target MC service user profile data to CMS is illustrated in figure 10.18.2.2-1.
A recording admin shall use this procedure to set/modify/remove target MC service user (s) for recording.
Pre-conditions:
- The recording admin service user has performed user authentication and service authori... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.3 Recording procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.3.1 General
| The MC recording procedures for MCPTT and MCVideo group and private communications utilize Session Recording Protocol [40]. The Session Recording Client (SRC) is located in the MC service server. Recording server represents the Session Recording Server (SRS) in the Session Recording Protocol architecture.
Recording of... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.3.2 Procedure for recording communication sessions of an MC service user
| Figure 10.18.3.2-1 below illustrates the recording procedure for communication sessions of an MC service user (MCPTT ID, MCVideo ID).
Pre-conditions:
- The user (MCPTT ID or MCVideo ID) has been configured as a target for recording in the MC service user profile (see 3GPP TS 23.281 [12] clause A.3 and 3GPP TS 23.379... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.3.3 Procedure for recording communication sessions of an MC service group
| Figure 10.18.3.3-1 below illustrates recording procedure for communication session of an MCPTT group or MCVideo group service.
Pre-conditions:
- The target group (MCPTT group ID or MCVideo group ID) has been configured as a target for recording in the common group configuration data (A.4) and the group configuration... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.4 Replay procedure
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.4.1 General
| The MC replay procedure between MC replay UE and recording server utilized reference point REC-1 (see clause 7.5.2.29).
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.18.4.2 Procedure for fetching a recording from a recording server
| Figure 10.18.4.2-1 below illustrates the procedure for fetching a recording from a recording server.
Pre-conditions:
- Replay UE has performed initial bootstrap and the initial UE configuration.
- MC replay user has performed user authentication and service authorization with IdMS.
- MC replay user has fetched its... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11 MC gateway UE
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.1 General
| An MC gateway UE enables MC service access for a MC service user residing on non-3GPP devices which may or may not have the ability to host MC service clients. In order to be able to participate in a MC service, the MC gateway UE provides the following necessary functions to enable the MC service access for such MC cli... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2 Functional Model
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.0 General
| The MC gateway UE offers access to the MC server for several MC clients as shown in Figure 11.2.0-1. The MC clients can be either located in the MC gateway UE or in the non-3GPP devices connected to the MC gateway UE via non-3GPP access. The configuration data defined in Annex A is needed in the MC client and the UE th... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.1 Functional model
| The authentication and authorisation of the MC clients hosted on the MC gateway UE follows the procedures described in 3GPP TS 33.180 [25]. Upon successful authentication and authorisation the MC clients can access a MC server via an MC gateway UE.
The MC gateway UE supports the authentication and authorisation of the... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2 Reference points
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2.1 General
| The reference points for the use of the MC gateway UE are described in the following subclauses.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2.2 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2.3 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2.4 Reference points MCX-n, CSC-n, SIP-1 and HTTP-1
| The reference points MCX-n and CSC-n belonging to the application plane, and the reference points SIP-1 and HTTP-1 belonging to the signalling control plane, are relayed by the MC gateway UE between MC client on the non-3GPP device and the corresponding MC service server.
MCX-n, CSC-n, SIP-1 and HTTP-1 reference point... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.2.5 Reference points GW-local (between the GW client and the GW server)
| The reference points GW-local is between the GW Client and GW Server. It supports the following functionalities:
- MBMS related signalling exchange (e.g., MBMS listening status report, MBMS announcement) to enable the MC gateway UE to receive the MBMS data for the MC service user using the non-3GPP device.
- Location... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.2.3 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.3 Using identities behind the MC gateway UE
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.3.1 General
| The MC gateway UE enables access to the MC system for MC clients either hosted on the MC gateway UE or hosted on non-3GPP devices. MC clients hosted in a non-3GPP device utilize MC service identities that are transparently passed through the MC gateway UE. This is further illustrated in clause 11.3.2.
MC clients host... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.3.2 When using separate IMS subscriptions
| If the MC clients are hosted by non-3GPP devices or the MC clients are hosted by the MC gateway UE, an MC service user corresponding to an MC client uses a dedicated IMS/SIP subscription without any relation to the MC gateway UE subscription.
Figure 11.3.2-1 depicts the use of the IMS Credential (IMC) application in a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.3.3 When sharing MC gateway UE's IMS subscription
| The MC clients, instantiated at the MC gateway UE on behalf of the non-3GPP devices which cannot host an MC client, rely on the IMS subscription provided by the MC gateway UE. In this case, the MC clients instantiated at the MC gateway UE share the credentials from the IMS subscription of the MC gateway UE, as shown in... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.4 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5 Procedures and information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.0 General
| This clause describes the procedures related to providing MC services, e.g., location reporting and MBMS support, to MC clients hosted in non-3GPP device.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.1 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2 3GPP access network related location information management
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.1 General
| The MC clients residing on the non-3GPP devices may receive the location reporting configuration from the location management server containing the trigger criteria related to 3GPP access network related location parameters and the requested location information may contain the 3GPP access network related location info... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.2.1 MC GW location reporting configuration
| Table 11.5.2.2.1-1 describes the information flow from the MC client, which resides on a non-3GPP device, to the MC gateway UE for the location reporting configuration.
Table 11.5.2.2.1-1: MC GW location reporting configuration
Information element
Status
Description
MC service ID
M
The MC service ID of the reque... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.2.2 MC GW location information report
| Table 11.5.2.2.2-1 describes the information flow from the MC gateway UE to the MC client residing on a non-3GPP device for the location information reporting.
Table 11.5.2.2.2-1: MC GW location information report
Information element
Status
Description
MC service ID
M
The MC service ID of the requesting MC servi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.2.3 MC GW location information request
| Table 11.5.2.2.3-1 describes the information flow from the MC client residing on a non-3GPP device to the MC gateway UE for requesting an immediate location information report.
Table 11.5.2.2.3-1: MC GW location information request
Information element
Status
Description
MC service ID
M
The MC service ID of the r... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.3 Procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.3.1 Event triggered location reporting procedure
| The procedure for how the MC clients residing on non-3GPP devices handling the location reporting configuration containing the trigger criteria related to the 3GPP access network related location information is shown in the figure 11.5.2.3.1-1.
Pre-conditions
- The MC service user wishes to have access to MC services... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.3.2 On-demand location reporting procedure
| The MC client may need to immediately send the location report to the location management sometimes and the requested location information may be related to the 3GPP access network. Under these circumstances the MC client can request the MC gateway UE to report its location information as described in the figure 11.5.2... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.2.3.3 Location reporting cancel procedure
| The location reporting cancel procedure reuses the information flow of location reporting configuration as defined in the subclause 11.5.2.3.1 as described in the figure 11.5.2.3.3-1
Pre-conditions
- The MC service user wishes to have access to MC services by using a non-3GPP device.
- The MC client successfully com... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3 MBMS support for MC clients residing on non-3GPP devices
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.1 General
| This subclause addresses the MBMS support for the MC clients residing on the non-3GPP devices associated with an MC gateway UE. The MC clients instruct the MC gateway UE about the corresponding MBMS bearer details to enable MC gateway listening on them. On demand, MC gateway UE forwards the traffic received over MBMS b... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.1 MC GW MBMS bearer announcement
| Table 11.5.3.2.1-1 describes the information flow from the MC client which resides on a non‑3GPP device to the MC gateway UE for sharing the details of MBMS bearer announcement received by the MC Client from the MC Service server.
Table 11.5.3.2.1-1: MC GW MBMS bearer announcement
Information element
Status
Descrip... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.2 MC GW MBMS listening status report
| Table 11.5.3.2.2-1 describes the information flow from the MC gateway UE to the MC client which resides on a non‑3GPP device for the MC GW MBMS listening status report.
Table 11.5.3.2.2-1: MC GW MBMS listening status report
Information element
Status
Description
TMGI(s)
M
TMGI(s) information.
MBMS listening sta... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.3 MC GW MapGroupToBearer request
| Table 11.5.3.2.3-1 describes the information flow from the MC client which resides on a non‑3GPP device to the MC gateway UE for sharing the details of MapGroupToBearer message received from the MC service server.
Table 11.5.3.2.3-1: MC GW MapGroupToBearer request
Information element
Status
Description
MC service ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.4 MC GW MapGroupToBearer response
| Table 11.5.3.2.4-1 describes the information flow from the MC gateway UE to the MC client which resides on a non‑3GPP device for the MC GW MapGroupToBearer response.
Table 11.5.3.2.4-1: MC GW MapGroupToBearer response
Information element
Status
Description
MapGroupToBearer Status
M
Success or failure response
N... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.5 MC GW MBMS listening status report
| Table 11.5.3.2.5-1 describes the information flow from the MC gateway UE to the MC client which resides on a non‑3GPP device for the MC GW MBMS listening status report.
Table 11.5.3.2.5-1: MC GW MBMS listening status report
Information element
Status
Description
TMGI(s)
M
TMGI(s) information.
MBMS listening sta... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.6 MC GW MBMS bearer suspension indication
| Table 11.5.3.2.6-1 describes the information flow from the MC gateway UE to the MC client which resides on a non‑3GPP device for the MC GW MBMS bearer suspension indication.
Table 11.5.3.2.6-1: MC GW MBMS bearer suspension indication
Information element
Status
Description
TMGI(s)
M
TMGI(s) information.
MBMS sus... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.7 MC GW UnMapGroupToBearer request
| Table 11.5.3.2.7-1 describes the information flow from the MC client which resides on a non‑3GPP device to the MC gateway UE for sharing the details of UnMapGroupToBearer message received from the MC service server.
Table 11.5.3.2.7-1: MC GW UnMapGroupToBearer request
Information element
Status
Description
MC serv... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.2.8 MC GW UnMapGroupToBearer response
| Table 11.5.3.2.8-1 describes the information flow from the MC gateway UE to the MC client which resides on a non‑3GPP device for the MC GW UnMapGroupToBearer response.
Table 11.5.3.2.8-1: MC GW UnMapGroupToBearer response
Information element
Status
Description
UnMapGroupToBearer Status
M
Success or failure respo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.3 Procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.3.1 Procedure for handling MBMS bearer announcement
| MC clients residing on non-3GPP devices receive MBMS bearer announcements from the MC system, MC clients share the details of the MBMS bearer received in MBMS bearer announcement to the MC gateway UE. This enables the MC gateway UE to start monitoring the corresponding MBMS bearer.
Figure 11.5.3.3.1-1 illustrates the ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.3.2 Procedure for handling MapGroupToBearer message
| Whenever the MC client detects that traffic received from MC service server is MapGroupToBearer message and if the MC client participates in the group session or communication identified by the MapGroupToBearer message then it should inform the details contained in the MapGroupToBearer message to MC gateway UE. When th... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.3.3 Procedure for MBMS bearer suspension notification
| The MC service server can choose to instruct some MC clients to send the MBMS bearer suspension report when notified by RAN. When the MC clients are residing on non 3GPP devices, MC gateway UE would be the one listening on the MBMS bearers. When RAN decides to suspend the MBMS bearer it indicates the MC gateway UE. MC ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.3.3.4 Procedure for reporting MBMS listening status
| The MC gateway UE listening on the MBMS bearer has to report the MBMS listening status and the optional MBMS bearer quality to the MC clients so that MC clients can report the same to the MC service server. MC gateway UE monitors an MBMS bearer to receive MC service media. Based on the MBMS listening status and the rec... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 11.5.4 Void
|
Annex A (normative):
Configuration data for MC services
A.1 General
This Annex provides information about the static data needed for configuration for MC services, which belong to one of the following categories:
- MC service UE configuration data (see subclause A.2);
- MC service user profile data (see subclaus... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 1 Scope
| This document specifies the functional model, procedures and information flows needed for the mission critical video (MCVideo) service. Support for both MCVideo group streaming and MCVideo private streaming operating in on-network and off-network modes of operation is specified.
The corresponding service requirements ... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 3 Definitions, symbols and abbreviations
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
MCVideo client: An instance of an MC service client that provides the cli... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 3.2 Symbols
| For the purposes of the present document, the following symbols given in 3GPP TS 22.280 [2] apply:
Nc2
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
E-UTRAN Evolved Universal Terrestrial Radio Access Network
EP... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 4 Introduction
| The MCVideo service supports video media communication between several users (i.e. group call), where each user has the ability to gain access to the permission to stream video in an arbitrated manner. The MCVideo service also supports private calls between two users.
The MCVideo architecture is based on the function... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5 Architectural requirements
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.1 Media routing requirements
| The video media flow for a private call shall be routed according to one of the following two options:
a) Option 1:
1) Through the primary MCVideo system if both users in the call belong to the same organisation; or
2) Through the primary MCVideo system of each users, if the users in the call do not belong to the sa... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.2 MCVideo group affiliation and MCVideo group de-affiliation
| MCVideo group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [6]. In addition, the following requirements shall be fulfilled by the MCVideo service for MCVideo users affiliated to MCVideo groups:
- MCVideo users receive notifications for MCVideo group call setup and invitations for their affiliate... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.3 Device inventory requirements
| The MCVideo service shall provide device inventory capabilities for MCVideo UEs. The device inventory capabilities shall include:
- device information registration;
- device information storage; and
- device information query.
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.4 Device discovery requirements (off-network)
| The MCVideo service shall provide device discovery for devices as requested by the MCVideo user according to the MC service provider policy for off-network operations.
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.5 Bearer management
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.5.1 General
| The MCVideo UE shall use the APNs as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [6]. The MCVideo UE shall use the MC services APN as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [6] for the SIP-1 reference point.
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.5.2 EPS bearer considerations
| The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [6] shall apply.
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.5.3 EPS unicast bearer considerations for MCVideo
| For an MCVideo call session request, resources shall be requested utilising interaction with dynamic PCC. The MCVideo system shall request resources over Rx to a PCRF. It is recommended that the dedicated bearer(s) for video media and control of the video media (i.e. MCVideo‑4 and MCVideo‑7) utilise the QCI values depe... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 5.5.4 MBMS bearer management
| The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [6].
5A Involved business relationships
The description of the involved business relationships for the MCVideo service is contained in clause 6 of 3GPP TS 23.280 [6].
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6 MCVideo Functional model
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.1 Functional model description
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.1.1 On-network functional model
| Figure 6.1.1-1 shows the functional model for the application plane of MCVideo service for on-network operations.
Figure 6.1.1-1: Functional model for application plane of MCVideo service
In the model shown in figure 6.1.1-1, the following apply:
- The MCVideo server is an instantiation of a MC service server in a... |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.1.2 Off-network functional model
| Figure 6.1.2-1 shows the functional model for the application plane of MCVideo service for off-network operations.
Figure 6.1.2-1: Functional model for application plane of off-network MCVideo service
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.2 Functional entities description
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.2.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.2.2 MCVideo service application plane
| |
821fe75a139a4ea963b889f1f128a599 | 23.281 | 6.2.2.1 General
| Entities within the application plane of MCVideo service provide application control, media transmission control and distribution functions.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.