hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
701465bc5227ddf47bbba259b7283444
|
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 data has been uploaded to the MC service server.
Figure 10.18.3.3-1: Procedure for recording communication sessions of an MC service group
1. An MC group communication session (MCPTT/MCVideo group call) involving the target group is initiated.
2. A Session Recording Client (SRC) in the MC service server starts a recording session (see IETF RFC 7866 [40]) with the recording server.
3. Group communication session ends.
4. The recording session ends.
5. The recording server stores the recording session, and it is available for download and/or replay.
NOTE: Steps 1-5 are repeated as long as the none of the conditions of step 6 is true.
6. When the group is removed from the recording targets (see 10.18.2.1) or the group is deleted (see 10.2.8), an ongoing recording session (if exists) is terminated.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
10.18.4 Replay procedure
| |
701465bc5227ddf47bbba259b7283444
|
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).
|
701465bc5227ddf47bbba259b7283444
|
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 user profile from the CMS
- Recording server has up-to-date copy of the user profile of the MC replay user.
Figure 10.18.4.2-1: Procedure for fetching a recording from a recording server
1. MC replay user, utilizing replay client in the replay UE, sends a Get recording request to the recording server.
2. Recording server checks that the replay user (MCRec ID) is authorized to replay recordings of the requested user or group.
3. If authorized, recording server sends Get recording response to the replay UE
NOTE: The contents and formatting of Get recording request and Get recording response messages are out of scope of the current document.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11 MC gateway UE
| |
701465bc5227ddf47bbba259b7283444
|
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 clients:
- 3GPP transport resources: Sharing of MC gateway UE 3GPP transport resources among the associated MC service clients.
- MC client identification: Independent MC service client identification, MC service client authorisation and MC service profile association.
- Location Management: Providing location management support for the associated MC clients to handle the location information and triggers related to 3GPP access network.
- MC client communication integrity: Ensure that signalling, media content and traffic attributes, e.g. priority and QoS, of communications between the MC system and MC service client remains unaltered.
- Transparent MC traffic forwarding: The MC gateway UE forwards MC traffic without altering the content to the non-3GPP device whether it hosts or does not host an MC client. For the case the MC client is hosted at the non-3GPP device, the MC gateway UE forwards:
- the signalling between the MC client in the non-3GPP device and the MC service server/ CSC server
- the signalling between the user agent in the non-3GPP device and the SIP core
- the signalling between the HTTP client in the non-3GPP device and the HTTP proxy
- the media between the MC service server and the MC client in the non-3GPP device
NOTE 1: The traffic exchange between the non-3GPP device and the MC gateway UE is implementation specific.
NOTE 2: Information related to MC gateway UE routing capabilities is found in Annex E.
NOTE 3: Information about MC gateway UE selection are summarized in Annex D.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.2 Functional Model
| |
701465bc5227ddf47bbba259b7283444
|
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 that is hosting the MC clients, i.e., either non-3GPP device or MC gateway UE, to access the MC service.
For non-3GPP devices which can host an MC client, the MC gateway UE enables connectivity to the MC server. For non-3GPP devices which cannot host the MC client, the MC gateway UE hosts the instantiation of the MC client on behalf of the non-3GPP device.
Figure 11.2.0-1: Functional architecture
The MC gateway UE obtains MC service access via 3GPP network using the procedures as defined in 3GPP TS 33.180 [25].
The non-3GPP connection between the non-3GPP device and the MC gateway UE is out of scope of 3GPP.
For non-3GPP devices which cannot host MC clients, the MC gateway UE instantiates an MC client, acting on behalf of the non-3GPP device, to provide the requested services (e.g. emergency call, group calls, short data messages services, etc.). The communication interworking and the definition of associated procedures between the MC client (initiated at the MC gateway UE) and the non-3GPP devices is out of scope of this document.
For non-3GPP devices that host MC clients, MC service access is through the MC gateway UE. The MC gateway UE forwards (unmodified) signalling and media from the individual MC clients to the MC server and vice versa.
If the MC service user on the non-3GPP device utilizes multiple MC services simultaneously, the MC service access may also be provided via one or multiple MC gateway UEs as shown in figure 11.2.0-2. In this case, each MC service is restricted to one MC gateway UE (e.g. MCPTT via MC gateway UE1, MCData via MC gateway UE2).
Figure 11.2.0-2: Simultaneous multiple MC gateway UE use by a single non-3GPP device
NOTE 2: Although not shown in the above figure, the same principle of simultaneous use of multiple MC gateway UEs is applied for non-3GPP devices which cannot host an MC client.
|
701465bc5227ddf47bbba259b7283444
|
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 MC client residing at the non-3GPP device by forwarding the unmodified application layer signalling between the MC client and the corresponding MC server. The authentication and authorisation of the MC client in the non-3GPP device follows the procedures described in 3GPP TS 33.180 [25].
NOTE: The authentication and authorisation between the MC gateway UE and the non-3GPP device is out of scope of 3GPP.
Figure 11.2.1-1 represents the functional model for the application plane for utilizing MC gateway UE to enable MC services to non-3GPP devices that can host an MC client.
Figure 11.2.1-2 represents the functional model for the signalling plane for utilizing MC gateway UE to enable MC services to non-3GPP devices that can host an MC client.
Figure 11.2.1-3 represents the functional model for the application plane for non-3GPP devices that cannot host an MC client.
Figure 11.2.1-1: Functional model of MC gateway UE application plane with MC client hosted in the non- 3GPP device
Figure 11.2.1-2: Functional model of MC gateway UE signalling plane with MC client hosted in the non- 3GPP device
Figure 11.2.1-3: Functional model of MC gateway UE application plane with MC client hosted in the MC gateway UE
The functional model for the signalling control plane as described in figure 7.3.1-2 is applicable to figure 11.2.1-3.
11.2.2 Reference points
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.2.2.1 General
|
The reference points for the use of the MC gateway UE are described in the following subclauses.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.2.2.2 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.2.2.3 Void
| |
701465bc5227ddf47bbba259b7283444
|
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 points are specified in the present specification. The MCX-n reference points are specified in 3GPP TS 23.379 [16], 3GPP TS 23.281 [12] and 3GPP TS 23.282 [13].
|
701465bc5227ddf47bbba259b7283444
|
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 management related signalling exchange (e.g., location configuration trigger, location report) to enable the MC client residing on the non 3GPP device to handle the 3GPP network related location information and triggers.
The security aspects of the GW-local interface are out of scope of 3GPP.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.2.3 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.3 Using identities behind the MC gateway UE
| |
701465bc5227ddf47bbba259b7283444
|
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 hosted in MC gateway UE also utilize unique MC service identities and share one common IMS subscription that is unique for MC gateway UE. This is further illustrated in subclause 11.3.3.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.3.2 When using separate IMS subscriptions
|
Editor's Note: The content of this clause is FFS.
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 accordance with 3GPP TS 23.228 [9].
Figure 11.3.2-1: IMC per MC service client
The MC service user profiles are independent of the MC gateway MC service user profile.
|
701465bc5227ddf47bbba259b7283444
|
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 Figure 11.3.3-1.
Figure 11.3.3-1: Sharing MC gateway UE's IMC for non-3GPP devices which cannot host a client
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.4 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5 Procedures and information flows
| |
701465bc5227ddf47bbba259b7283444
|
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.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.1 Void
| |
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.2 3GPP access network related location information management
| |
701465bc5227ddf47bbba259b7283444
|
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 information. The procedures defined in this subclause enables the MC clients residing on the non-3GPP devices to request the MC gateway UE to handle these triggers on its behalf and to request the required location information (3GPP access network related) from MC gateway UE.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.2.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
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 requesting MC service user
Requested location information
O (see NOTE 1)
Identifies what location information is requested
Triggering criteria
O (see NOTE 1)
Identifies when the location management client will send the location report (see NOTE 2)
Minimum time between consecutive reports
O (see NOTE 1)
Defaults to 0 if absent
NOTE 1: If none of the information elements is present, this represents a cancellation for location reporting, if configured.
NOTE 2: The triggering criteria contains only the events related to the 3GPP access network.
|
701465bc5227ddf47bbba259b7283444
|
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 service user
Triggering event
O
Identity of the event that triggered the sending of the report
Location information
(see NOTE)
O
Location information of the MC gateway UE
NOTE: The following location information elements which are related to 3GPP access network shall be present (configurable): Serving and neighbouring ECGI, MBMS SAIs, MBMSfnArea, PLMN ID.
|
701465bc5227ddf47bbba259b7283444
|
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 requesting MC service user
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.2.3 Procedures
| |
701465bc5227ddf47bbba259b7283444
|
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 by using a non-3GPP device.
- The MC client successfully completed service authorization via MC gateway UE.
Figure 11.5.2.3.1-1: Event-triggered location reporting procedure
1. MC client receives the location reporting configuration request from LMS which contains the triggering criteria of 3GPP access network related location information changes.
2. MC client sends the MC GW location reporting configuration to the MC gateway UE containing the 3GPP access network related location information triggers and the requested location information. MC Gateway UE stores the location reporting configuration and starts monitoring for the triggers as received in the MC GW location reporting configuration.
3. A location reporting event occurs, triggering step 4.
4. MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client.
5. MC client updates the locally available location information with the location information received from the MC gateway UE.
6. The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client.
|
701465bc5227ddf47bbba259b7283444
|
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.3.2-1.
Pre-conditions
- The MC service user wishes to have access to MC services by using a non-3GPP device.
- The MC client successfully completed service authorization via MC Gateway UE.
Figure 11.5.2.3.2-1: On-demand location reporting procedure
1. MC client receives the location information request from LMS to send the location information immediately or any other events where it has to send the location report to the location management server immediately like initial login, group call etc. Requested location information includes the location information related to 3GPP access network.
2. MC service user is notified and asked for permission to share location information. MC service user can accept or deny the request.
3. MC client sends the MC GW Location information request to the MC gateway requesting for the location information related to the 3GPP access network of the MC gateway UE.
4. MC gateway UE sends the MC GW Location information report containing the location information requested by the MC client.
5. MC client updates the locally available location information with the location information received from the MC gateway UE.
6. The MC client sends a location information report to the location management server, containing location information identified by the location management server and available to the MC client.
|
701465bc5227ddf47bbba259b7283444
|
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 completed service authorization via MC gateway UE.
- The MC client no longer needs the location information report from MC gateway UE.
Figure 11.5.2.3.3-1: On-demand location reporting procedure
1. The location management client sends MC GW location reporting configuration without any information element to the MC gateway UE to stop location reporting from the MC gateway UE.
2. The MC gateway UE stops sending location information reports to the MC client.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.3 MBMS support for MC clients residing on non-3GPP devices
| |
701465bc5227ddf47bbba259b7283444
|
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 bearer to the MC clients residing on non‑3GPP devices. With the procedure defined in this subclause MBMS bearer can be supported for the MC clients residing on non-3GPP devices. Changes required are confined to the reference point between MC gateway UE and the MC clients residing on non‑3GPP devices. MC service server may consider the location of the corresponding MC clients as defined in subclause 11.5.2 while deciding to establish MBMS bearer.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.3.2 Information flows
| |
701465bc5227ddf47bbba259b7283444
|
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
Description
MC service ID
M
The MC service ID of the requesting MC client.
TMGI
M
TMGI information
List of service area identifier
M
A list of service area identifier for the applicable MBMS broadcast area.
Frequency
O
Identification of frequency if multi carrier support is provided
SDP information
M
SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information)
Monitoring state
O
The monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not.
ROHC information
O
Indicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder.
|
701465bc5227ddf47bbba259b7283444
|
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 status(s)
M
The MBMS listening status per TMGI.
MBMS reception quality level
O
The reception quality level per TMGI
Non 3GPP transport resources establishment parameters (see NOTE)
O
This element contains the details of the non‑3GPP transport resources establishment parameters (IP address, Port etc.) which are used by the MC gateway UE to forward the MC service communication traffic received over 3GPP MBMS bearer to the MC client.
NOTE: These parameters are implementation specific and are dependent on the non 3GPP transport mechanism used between the MC client and MC gateway UE. This parameter can be present mandatorily if the MBMS bearer listening status is success.
|
701465bc5227ddf47bbba259b7283444
|
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 ID
M
The MC service ID of the MC service user.
MCPTT group ID
M
This element identifies the MCPTT group, in which the call is started.
Media stream identifier
M
This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel).
TMGI
M
The MBMS bearer identifier.
|
701465bc5227ddf47bbba259b7283444
|
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
Non 3GPP transport resources establishment parameters (see NOTE)
M
This element contain the details of the non 3GPP transport resources establishment parameters(IP address, Port etc.,) which are used by the MC gateway UE to forward the MC service Group communication traffic received over 3GPP MBMS bearer to the MC client.
NOTE: These parameters are implementation specific and are dependent on the non-3GPP transport mechanism used between the MC client and MC gateway UE
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.3.2.5 MC GW MBMS bearer quality 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 bearer quality report.
Table 11.5.3.2.5-1: MC GW MapGroupToBearer response
Information element
Status
Description
TMGI(s)
M
TMGI(s) information.
MBMS listening status(s)
M
The MBMS listening status per TMGI.
MBMS reception quality level
O
The reception quality level per TMGI
|
701465bc5227ddf47bbba259b7283444
|
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 suspension status(s)
M
The MBMS suspension status per TMGI.
|
701465bc5227ddf47bbba259b7283444
|
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 service ID
M
The MC service ID of the MC service user.
MCPTT group ID
M
This element identifies the MC service group related to a group call to be dissociated over the MBS session.
Media stream identifier
M
This element identifies the media stream of the SDP, which is no longer used for the group call within the MBMS session.
TMGI
M
The MBMS bearer identifier.
|
701465bc5227ddf47bbba259b7283444
|
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 response
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.3.3 Procedures
| |
701465bc5227ddf47bbba259b7283444
|
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 procedure for handling the MBMS bearer announcement by the MC client and the MC gateway UE.
Pre-conditions:
1. The MC client has been configured with the necessary parameters to enable the use of the MC gateway UE.
2. The MC client successfully completed service authorization via MC gateway UE.
Figure 11.5.3.3.1-1: Handling of MBMS bearer announcement
1. The MC service server establishes the MBMS bearer(s) according to the procedures defined in 3GPP TS 23.468 [18]. Service description associated with the MBMS bearer(s) is returned from the BM-SC.
2. The MC service server provides service description information associated with the MBMS bearer to the MC client residing on non‑3GPP devices via MC gateway UE.
3. The MC client sends the MC GW MBMS bearer announcement to the MC Gateway UE containing the MBMS bearer related information received from the MC service server.
4. The MC gateway UE stores the information associated with the TMGI(s). The MC gateway UE uses the TMGI and other MBMS bearer related information to activate the monitoring of the MBMS bearer.
5. The MC gateway UE that enters or is in the service area of at least one announced TMGI notifies to the MC client that it can receive data over MBMS by sending the MC GW MBMS listening status report. The MC GW MBMS listening status report also contains the details of the non‑3GPP transport resources related parameters. The MC gateway UE may choose to send the details of existing transport resources information as part of non-3GPP transport resources establishment parameters IE if existing communication channel can be reused.
6. The MC client establishes the transport resources with the MC gateway UE based on the parameters received in step 5 to receive the MC service data from the MC gateway UE, if these parameters are not referring to any of the already established transport resources. The MC Gateway UE forwards the MC service data it received over the MBMS bearer from the MC service server to the MC client over this transport resources.
7. The MC client sends the MBMS Listening Status Report to the MC service server indicating that it is able to receive the media over MBMS.
|
701465bc5227ddf47bbba259b7283444
|
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 the association of group call, MBMS bearer and the MC service ID of the MC client is known to the MC gateway UE, it can forward the traffic received over MBMS bearer accordingly.
Figure 11.5.3.3.2-1 illustrates the procedure for handling the MapGroupToBearer message by the MC client and the MC gateway UE.
Pre-conditions:
1. The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
2. The MC client successfully completed service authorization via MC gateway UE.
Figure 11.5.3.3.2-1: Handling of MapGroupToBearer message
1. The MC service server sends a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MC service group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call.
2. If the MC client is participating in the MC group communication identified by the MapGroupToBearer message, it sends the details contained in the MapGroupToBearer message to the MC gateway UE through MC GW MapGroupToBearer request message.
3. The MC gateway UE on receiving the MC GW MapGroupToBearer Request message from the MC client it maintains the association between the MC Service ID and the corresponding MBMS sub channel.
4. The MC gateway UE sends the MC GW MapGroupToBearer response message to the MC client which contains the details of the non‑3GPP transport resources related parameters. The MC gateway UE may choose to send the details of existing communication channel information as part of non-3GPP transport resources establishment parameters IE if existing transport resources can be reused.
5. The MC client establishes the communication channel with the MC gateway UE based on the parameters received in step 4 to receive the MC service group communication data from the MC gateway UE, if these parameters are not referring to any of the already established transport resources. The MC Gateway UE forwards the MC service group communication data it received over the MBMS bearer from the MC service server to the MC client over this transport resources.
6. The MC service server sends the downlink media for the group communication session over the MBMS bearer.
7. The MC gateway UE checks which MC clients should receive the media of the MC group communication based on Step 3.
8. The MC gateway UE forwards the downlink media to the intended MC clients over the transport resources established as in step 5.
11.5.3.3.2A Procedure for handling UnmapGroupFromBearer message
Whenever the MC client receives UnmapGroupFromBearer message and if the MC client participates in the group session or communication identified by the UnmapGroupFromBearer message then it should inform the details contained in the UnmapGroupFromBearer message to MC gateway UE. When the association of group call, MBMS bearer and the MC GW service ID of the MC client is known to the MC gateway UE, it can remove the association and stop forwarding of the traffic received over MBMS bearer accordingly.
Figure 11.5.3.3.2A-1 illustrates the procedure for handling the UnmapGroupFromBearer message by the MC client and the MC gateway UE.
Pre-conditions:
1. The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
2. The MC client successfully completed service authorization via MC gateway UE.
Figure 11.5.3.3.2A-1: Handling of UnmapGroupFromBearer message
1. An MCPTT group call is ongoing; the MC gateway UE forwards the downlink media to the intended MC client over the transport resources established.
2. MCPTT server has determined to disconnect the call over the MBMS bearer for the MC client.
3. An UnmapGroupFromBearer message is sent by the MCPTT server to MC client (if in MBMS coverage area) on MBMS bearer(s).
4. If the MC client is participating in the MC group communication identified by the UnmapGroupFromBearer message, it sends the details contained in the UnmapGroupFromBearer message to the MC gateway UE through MC GW UnMapGroupToBearer request message.
5. The MC gateway UE on receiving the MC GW UnMapGroupToBearer Request message from the MC client it removes the association maintained between the MC Service ID and the corresponding MBMS sub channel.
6. The MC gateway UE sends the MC GW MapGroupToBearer response message to the MC client.
|
701465bc5227ddf47bbba259b7283444
|
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 gateway UE to notify the MC clients it is serving so that MC clients can report the same to the MC service server. This procedure is applicable only if the MC client is instructed to report the MBMS bearer suspension. Irrespective of whether the MC clients need to send the MBMS bearer suspension report to the MC service server, MC gateway can choose to notify the MC clients it is serving whenever RAN suspends the MBMS bearer. MC clients can then decide to send the MBMS bearer suspension report to the MC service server only if they are instructed by the MC service server.
Figure 11.5.3.3.3-1 illustrates the procedure for MC clients residing on non-3GPP devices reporting the MC service server about the MBMS bearer suspension.
Figure 11.5.3.3.3-1: MBMS bearer suspension notification
1. The MC service server sends an MBMS suspension reporting instruction to the MC client residing on non-3GPP device.
NOTE: This message may be included in the MBMS bearer announcement message and may be sent both on a unicast bearer and a multicast bearer.
2. RAN decides to suspend the MBMS bearer, according to existing procedures in 3GPP TS 36.300 [21].
3. An MBMS suspension indication is sent to the MC gateway UE in the MSI (MCH Scheduling Information), according to existing procedures in 3GPP TS 36.300 [21].
4. The MC gateway UE detect the MBMS suspension and sends an MC GW MBMS suspension indication to the MC Client residing on non-3GPP device.
5. The MC client MBMS suspension report to the MC Service server via MC gateway UE.
|
701465bc5227ddf47bbba259b7283444
|
23.280
|
11.5.3.3.4 Procedure for reporting MBMS bearer quality
|
The MC gateway UE listening on the MBMS bearer has to report the 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 received quality (e.g. radio level quality) the MC gateway UE needs to inform the MC Clients which requested the MC gateway UE to listen on MBMS bearer, whether it is able to receive the MC service media on the MBMS bearer with sufficient quality or not the MC Clients can inform the MC service server accordingly.
Figure 11.5.3.3.4-1 illustrates the procedure for MC clients residing on non‑3GPP devices reporting the MC service server about the MBMS bearer quality.
Pre-conditions:
1. There is an MBMS bearer activated and the MBMS bearer information is announced to the MC gateway UE.
2. The MC gateway UE is located in the MBMS broadcasting area
3. The MC gateway UE monitors SIB-13 (or SIB-20) and (SC-)MCCH to receive the modulation and coding scheme.
4. The MC gateway UE monitors the cell specific reference signal and when MBSFN transmission is used, the MBSFN specific reference signals.
Figure 11.5.3.3.4-1: Reporting MBMS bearer quality
1. The MC gateway UE follows the Step 1 of the procedure as described in clause 10.7.3.6.2 for the MC service UE. The corresponding MBMS bearer quality information is forwarded to all the MC clients which have asked the MC gateway UE to listen on the particular MBMS bearer.
2. If the MBMS bearer quality reaches a certain threshold, the MC gateway UE sends an MC GW MBMS bearer quality report to the MC client. The threshold is used to define the MBMS listening status, which indicates if the MBMS bearer quality has been acceptable or not to receive a specific MC service media. If the MBMS bearer quality is mapped to a different MBMS reception quality level, the MC gateway UE may send an MBMS Bearer Quality report including the MBMS reception quality level to the MC Client.
NOTE: The threshold used to indicate MBMS bearer quality depends on service type (i.e. MCPTT, MCVideo or MCData) and the metrics used. The metrics used and the associated thresholds are out of scope of this specification.
3. The MC Client sends the MBMS listening status report to the MC Service server via MC gateway UE containing the information received in the MC GW MBMS bearer quality report.
4. The MC service server may send an additional proposal for measurements e.g. information about neighbouring MBMS bearers. This message may be an MBMS bearer announcement message.
|
701465bc5227ddf47bbba259b7283444
|
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 subclause A.3); - MC service group configuration data (see subclause A.4); - MC service configuration data (see subclause A.5); and - Initial MC service UE configuration data (see subclause A.6). - Initial recording admin UE and/or replay UE configuration data (see subclause A.10). For each configuration category, data is split between configuration data that is applicable to both on‑network and off‑network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MC service UE, MC service group, MC service user and MC service configuration data refers to the information that will be stored against each MC service UE, MC service group, MC service user and MC service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. The columns in the tables have the following meanings: - Reference: the reference of the corresponding requirement in 3GPP TS 22.280 [3] or 3GPP TS 22.281 [4] or 3GPP TS 22.282 [5] or 3GPP TS 22.179 [2] or the corresponding subclause from the present document. - Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. - When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all the three tables of on-network and off‑network, on‑network only and off‑network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top‑most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. A.2 MC service UE configuration data MC service UE configuration data has to be known by an MC service UE after MC service authorization. The CSC-4 reference point is used for configuration between the configuration management server and the configuration management client on the MC service UE when the MC service UE is on-network. MC service UE configuration data can be configured offline using the CSC-11 reference point. MC service UE configuration data is specific to each MC service and is specified as follows: - MCPTT UE configuration data is specified in 3GPP TS 23.379 [16]; - MCVideo UE configuration data is specified in 3GPP TS 23.281 [12]; and - MCData UE configuration data is specified in 3GPP TS 23.282 [13]. Within each MC service, the MC service UE configuration data can be the same or different across MC service UEs. A.3 MC service user profile configuration data The MC service user profile configuration data is stored in the MC service user database. The configuration management server is used to configure the MC service user profile configuration data to the MC service user database (CSC-13) and MC service UE (CSC-4). MC service user profile configuration data can be configured offline using the CSC-11 reference point. MC service user profile configuration data is specific to each MC service and is specified as follows: - MCPTT user profile configuration data is specified in 3GPP TS 23.379 [16]; - MCVideo user profile configuration data is specified in 3GPP TS 23.281 [12]; - MCData user profile configuration data is specified in 3GPP TS 23.282 [13]; and - Location user profile configuration data is specified in clause A.8. - Recording admin and/or replay service user profile configuration data is specified in clause A.11. A.4 Group configuration data The group configuration data is stored in the group management server. The group management server is used to configure the group configuration data to the MC service UE (CSC-2), recording admin UE (CSC-2), replay UE (CSC-2), MC service server (CSC-3) and the recording server (REC-5). A single group can support one or multiple MC service configurations. Hence, the MC service group configuration data is divided into common group configuration data and MC service specific group configuration data. The group configuration data can be configured offline using the CSC-12 reference point. The common group configuration data are specified in table A.4-1. Tables A.4-1 and A.4-2 contain the group configuration required to support the use of on-network MC service. Tables A.4-1 and A.4-3 contain the group configuration required to support the use of off-network MC service. The MC service related group configuration data specific to each MC service is specified as follows: - MCPTT related group configuration data is specified in 3GPP TS 23.379 [16]; - MCVideo related group configuration data is specified in 3GPP TS 23.281 [12]; and - MCData related group configuration data is specified in 3GPP TS 23.282 [13]; Table A.4-1: Common group configuration data (on and off network) Reference Parameter description MC service UE Rec. admin UE & Replay UE(see NOTE 9) MC service Server Group management server Recording server [R-5.17-004], [R-6.4.3-001], [R-6.4.3-002], [R-6.9-004] and [R-5.1.3-002] of 3GPP TS 22.280 [3] MC service group ID Y Y (NOTE 12) Y Y Y (NOTE 12) [R-5.17-004], [R-6.4.3-001], [R-6.4.3-002] and [R-6.9-004] of 3GPP TS 22.280 [3] Group Alias (Contact URIs) Y Y Y List of group members (see NOTE 1) (see NOTE 8) [R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of 3GPP TS 22.280 [3] > MCPTT >> MCPTT ID (see NOTE 2) N Y Y Y 3GPP TS 33.180 [25] >> KMSUri for security domain of the MCPTT ID (see NOTE 3) N Y Y [R-6.2.2-001] and [R-7.6-007] of 3GPP TS 22.280 [3], [R-6.2.3.7.4.1-002] and [R-6.2.3.7.4.1-006] of 3GPP TS 22.179 [2] >> User priority for the group N Y Y [R-5.1.3-001] of 3GPP TS 22.280 [3] >> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). N Y Y Y [R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of 3GPP TS 22.280 [3] > MCVideo >> MCVideo ID (see NOTE 2) N Y Y Y 3GPP TS 33.180 [25] >> KMSUri for security domain of the MCVideo ID (see NOTE 3) N Y Y [R-6.2.2-001] and [R-7.6-007] of 3GPP TS 22.280 [3] >> User priority for the group N Y Y [R-5.1.3-001] of 3GPP TS 22.280 [3] >> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). N Y Y Y [R-5.1.3-001], [R-5.1.5-001], [R-6.4.5-005] and [R-6.4.5-006] of 3GPP TS 22.280 [3] > MCData >> MCData ID (see NOTE 2) N Y Y 3GPP TS 33.180 [25] >> KMSUri for security domain of the MCData ID (see NOTE 3) N Y Y [R-6.2.2-001] and [R-7.6-007] of 3GPP TS 22.280 [3] >> User priority for the group N Y Y [R-5.1.3-001] of 3GPP TS 22.280 [3] >> Participant type for the group (group membership information). The particpant type values are defined and configured by the Mission Critical Organisation (e.g.first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). N Y Y [R-5.16.2-001] and [R-5.16.2-002] of 3GPP TS 22.280 [3] Group’s owner (Mission Critical Organisation) Y Y Y Y Y Subclause 8.3.2, 10.2.3 MC service specific configuration (see NOTE 4) > MCPTT configuration (see NOTE 5) > MCVideo configuration (see NOTE 6) > MCData configuration (see NOTE 7) List of subordinate groups [R-5.2.2-002] of 3GPP TS 22.280 [3] > MC service group ID N Y Y Y Group broadcast information [R-5.2.2-001] of 3GPP TS 22.280 [3] Level within group hierarchy N Y Y [R-5.2.3-001] of 3GPP TS 22.280 [3] Level within user hierarchy N Y Y Subclause 10.6.2.9 of 3GPP TS 23.379 [16] Group is a preconfigured regroup group Y Y Y Y [R-5.2.1-002] of 3GPP TS 22.280 [3] Group is a broadcast group Y Y Y Y [R-6.15.4-001…010] of 3GPP TS 22.280 [3] Group is a target for recording Y (see NOTE 11) Y Y Y Y [R-6.15.4-001…010] of 3GPP TS 22.280 [3] Recording server address (URI) (see NOTE 10) Y (see NOTE 11) Y Y Y NOTE 1: The list of group members is provided to an authorized user only upon request and not by default. NOTE 2: MC service Ids for all configured MC services shall be provided for the configured group member. NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1. NOTE 4: An MC service specific configuration shall be provided for all of the MC services for which the group is enabled. At least one MC service shall be enabled for a group. NOTE 5: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. NOTE 6: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. NOTE 7: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. NOTE 8: The list of group members comprises all group members in primary and in partner MC systems of the MC service group. NOTE 9: This is the recording admin UE and/or replay UE of a user who is authorized to set this MC service group as a target for recording and/or authorized to replay this MC service group’s recordings. NOTE 10: If this parameter is absent, the Recording server URI shall be that identified in the initial MC service UE configuration data (on-network, table A.6-1) or in the initial recording admin and replay UE configuration data (on-network, table A.10-1) NOTE 11: These parameters, when provided to an MC service UE, are relevant only for recording administrators and replay users. NOTE 12: In this version of this specification only MCPTT and MCVideo groups shall be configured to the recording admin UE, replay UE and the recording server. Recording of MCData services is not supported. Table A.4-2: Common group configuration data (on‑network) Reference Parameter description MC service UE MC service Server Group management server [R-6.1-001] of 3GPP TS 22.280 [3] Maximum number of group members (Nc6) N Y Y [R-6.1-003] of 3GPP TS 22.280 [3] Enabled/disabled group (basic status) Y Y Y [R-6.6.1-006] of 3GPP TS 22.280 [3] Temporary group indication Y Y Y [R-6.4.5-005] and [R-6.15.4-001…010] of 3GPP TS 22.280 [3] List of authorised users who can request the list of members of an MC service group Y Y Y > MCPTT IDs Y > MCVideo IDs Y > MCData IDs Y > MCRec IDs Y MC service specific configuration > MCPTT configuration (see NOTE 1) > MCVideo configuration (see NOTE 2) > MCData configuration (see NOTE 3) [R-6.4.9-006] of 3GPP TS 22.280 [3] Geographic area within which affiliation to the group is permitted (see NOTE 4) Y Y Y [R-6.4.9-006] of 3GPP TS 22.280 [3] Geographic area outside which de-affiliation from the group is mandatory (see NOTE 4) Y Y Y Subclause 10.2.5 and [R-6.15.4-001…010] of 3GPP TS 22.280 [3] List of authorised users who can retrieve the group information > MCPTT IDs Y > MCVideo IDs Y > MCData IDs Y > MCRec IDs Y Subclause 5.2.3 Associated relay service code (as specified in 3GPP TS 23.303 [14]) Y N Y Subclause 5.2.9 of 3GPP TS 23.280 [16] List of partner MC systems from which interconnection is permitted for the group Subclause 5.2.9 of 3GPP TS 23.280 [16] > Identity of partner MCPTT system Y Y Subclause 5.2.9 of 3GPP TS 23.280 [16] > Identity of partner MCVideo system Y Y Subclause 5.2.9 of 3GPP TS 23.280 [16] > Identity of partner MCData system Y Y [R-6.4.4-003] of 3GPP TS 22.280 [16] List of functional aliases which prevents de-affiliating > Functional alias N Y Y [R-6.4.4-004] of 3GPP TS 22.280 [16] List of functional aliases which prevents de-affiliating, if only one user has bound the functional alias to the group > Functional alias N Y Y NOTE 1: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. NOTE 2: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. NOTE 3: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. NOTE 4: The geographic area may consist of a union of regions that are non-contiguous or contain holes. Table A.4-3: Common group configuration data (off‑network) Reference Parameter description MC service UE MC service server Group management server Subclause 8.1.3.2 ProSe layer-2 group ID (as specified in 3GPP TS 23.303 [14]) Y N Y Subclause 8.1.3.2 ProSe group IP multicast address (as specified in 3GPP TS 23.303 [14]) Y N Y Subclause 8.1.3.2 Indication of whether the UE shall use Ipv4 or Ipv6 for the MC service group (as specified in 3GPP TS 23.303 [14]) Y N Y MC service specific configuration > MCPTT configuration (see NOTE 1) > MCVideo configuration (see NOTE 2) > MCData configuration (see NOTE 3) NOTE 1: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. NOTE 2: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. NOTE 3: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. A.5 MC service configuration data The MC service configuration data is stored in the MC service server. The configuration management server is used to configure the MC service configuration data to the MC service server (CSC-5) and the MC service UE (CSC-4). The MC service configuration data can be configured offline using the CSC-11 reference point. The MC service configuration data is specific to each MC service and hence the detailed list of MC service configuration data is listed as follows: - MCPTT service configuration data is specified in 3GPP TS 23.379 [16]; - MCVideo service configuration data is specified in 3GPP TS 23.281 [12]; and - MCData service configuration data is specified in 3GPP TS 23.282 [13]; A.6 Initial MC service UE configuration data The initial MC service UE configuration data is essential to the MC service UE to successfully connect to the MC system. The initial MC service UE configuration data can be the same or different across MC service UEs. Data in table A.6-1 is provided to the MC service UE’s clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client, replay client) during the bootstrap process (see subclause 10.1.1), and can be configured on the MC service UE offline using the CSC-11 reference point or via other means e.g. as part of the MCPTT client’s provisioning on the UE, using a device management procedure. Table A.6-1: Initial MC service UE configuration data (on-network) Reference Parameter description Subclause 10.1.1 PDN connectivity information > HPLMN ID and optionally VPLMN ID to which the data pertains > MC services PDN >> APN >> PDN access credentials > MC common core services PDN >> APN >> PDN access credentials > MC identity management service PDN >> APN >> PDN access credentials Subclause 10.1.1 Application plane server identity information > Identity management server >> Server URI > Configuration management server >> Server URI > Key management server >> Server URI (also known as KMSUri for security domain managed by KMS) > Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCPTT > MCPTT Server >> Server URI > Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCData > MCData Server >> Server URI > Indication of whether the UE shall use Ipv4 or Ipv6 for on-network MCVideo > MCVideo Server >> Server URI > Location management server >> Server URI > Recording server (see NOTE 1) >> Server URI Subclause 10.1.1 Operational information > MC service UE label (see NOTE 2) NOTE 1: This parameter shall be present only if this MC service UE contains a replay client. NOTE 2: The MC service UE label is optional. A.7 Initial MC gateway UE configuration data Editor`s Note: The content of this clause is FFS. A.8 Location user profile configuration data The location user profile configuration data is stored in the location user database. The location management server obtains the location user profile configuration data via the configuration management server (CSC-24). Table A.8-1 contains the location user profile configuration required to support the use of on-network location service. Data in table A.8-1 can be configured offline using the CSC-11 reference point. Table A.8-1: location user profile data (on and off network) Reference Parameter description Location UE Location Server Configuration management server Location user database [R-5.11-007] of 3GPP TS 22.280 [3] Clause 10.9.3.3 Authorization to set a trigger at a LMC > List of MC service IDs for which a trigger is authorized to be set Y Y Y Y >> MCPTT ID (see NOTE 1) Y Y Y Y >> MCVideo ID (see NOTE 1) Y Y Y Y >> MCData ID (see NOTE 1) Y Y Y Y > List of MC service group IDs for which a trigger is authorized to be set Y Y Y Y >> MCPTT group ID (see NOTE 1) Y Y Y Y >> MCVideo group ID (see NOTE 1) Y Y Y Y >> MCData group ID (see NOTE 1) Y Y Y Y [R-5.11-008] of 3GPP TS 22.280 [3] Authorization to cancel a trigger at a LMC > List of MC service IDs for which a trigger is authorized to be cancelled Y Y Y Y >> MCPTT ID (see NOTE 1) Y Y Y Y >> MCVideo ID (see NOTE 1) Y Y Y Y >> MCData ID (see NOTE 1) Y Y Y Y > List of MC service group IDs for which a trigger is authorized to be cancelled Y Y Y Y >> MCPTT group ID (see NOTE 1) Y Y Y Y >> MCVideo group ID (see NOTE 1) Y Y Y Y >> MCData group ID (see NOTE 1) Y Y Y Y Clause 10.9.3.5 Clause 10.9.3.7 Authorization to subscribe to location information for an MC user > List of MC service IDs for which subscription and subscription cancellation is authorized Y Y Y Y >> MCPTT ID (see NOTE 1) Y Y Y Y >> MCVideo ID (see NOTE 1) Y Y Y Y >> MCData ID (see NOTE 1) Y Y Y Y > List of MC service group IDs for which subscription and subscription cancellation is authorized Y Y Y Y >> MCPTT group ID (see NOTE 1) Y Y Y Y >> MCVideo group ID (see NOTE 1) Y Y Y Y >> MCData group ID (see NOTE 1) Y Y Y Y Clause 10.9 Authorised to request location information of another user in the primary MC system (see NOTE 3) Y Y Y Y > List of MC service IDs for which requesting location information is authorised >> MCPTT Y Y Y Y >> MCVideo Y Y Y Y >> MCData Y Y Y Y Clause 10.9 Authorised to share the location information with an MC service user (NOTE 3) > List of MC service IDs for which sharing location information is authorised (NOTE 4) >> MCPTT ID Y Y Y Y >> MCVideo ID Y Y Y Y >>MCData ID Y Y Y Y > List of MC service group IDs for which obtaining location information is authorized Y Y Y Y >> MCPTT group ID (see NOTE 1) Y Y Y Y >> MCVideo group ID (see NOTE 1) Y Y Y Y >> MCData group ID (see NOTE 1) Y Y Y Y Clause 10.9.3.10.6 Clause 10.9.3.11 Authorization to modify the location user profile of an MC user > Modification to the location user profile is permanent/temporary Y N Y Y >> Duration of time for temporary modification Y N Y Y > List of MC service IDs for which modifying the location reporting configuration is authorized Y N Y Y >> MCPTT ID (see NOTE 1) Y N Y Y >> MCVideo ID (see NOTE 1) Y N Y Y >> MCData ID (see NOTE 1) Y N Y Y [R-6.12-003] of 3GPP TS 22.280 [3] Authorised to restrict the dissemination of the location information Y Y Y Y Clause 10.9 List of partner MC systems for which an MC user is authorised to request location information for another MC user > Identity of partner MCPTT system Y Y Y Y > Identify of partner MCVideo system Y Y Y Y > Identity of partner MCData system Y Y Y Y Clause 10.9.3.12.2 Clause 10.9.3.12.3 List of MC service IDs for which trigger overriding and cancelling an override is authorized > MCPTT ID (see NOTE 1) Y Y Y Y > MCVideo ID (see NOTE 1) Y Y Y Y > MCData ID (see NOTE 1) Y Y Y Y Clause 10.9.1 Default location reporting configuration >Requested non-emergency location information (see NOTE 5) Y Y Y Y >Requested emergency location information (see NOTE 5) Y Y Y Y >Triggering criteria in non- emergency cases (see NOTE 5) Y Y Y Y >Triggering criteria in emergency cases (see NOTE 5) Y Y Y Y >Minimum time between consecutive reports for emergency cases (see NOTE 5) Y Y Y Y >Minimum time between consecutive reports for non‑emergency cases (see NOTE 5) Y Y Y Y >Handling criteria in not reporting location information cases (see NOTE 5) Y Y Y Y >Triggering criteria in not reporting location information cases (see NOTE 5) Y Y Y Y NOTE 1: There can be zero or more. NOTE 2: The default authorization applies to all MC users not listed as specifically authorized or not authorized. The intent of this parameter is to avoid having to list all MC users as specifically authorized or not authorized and allowing the administrator to only indicate specific authorization statuses. NOTE 3: Further differentiation on authorisation for location information based on detailed characteristics (e.g. MC organization, MC service ID, functional alias) is left to implementation. NOTE 4: If the list of MC service IDs, for which sharing location information is authorised, is empty, then the MC service user shares their location information with any requesting MC service user. NOTE 5: For a description of this parameter see table 10.9.2.1-1 Location reporting configuration A.9 ACM client user profile configuration data The ACM client user profile configuration data is stored at the MC system’s ACM server and at the Configuration management server. The authorisations of requesting ACM clients will be verified based on valid entries in Table A.9‑1. Table A.9-1: MC service user profile configurations for authorisation of ACM (on-network) Reference Parameter description ACMC ACMS Configuration management server Subclause 5.16.4 of 3GPP TS 22.280 [2] Authorised to perform ACM transactions Y Y Y Subclause 5.16.4 of 3GPP TS 22.280 [2] List of permitted partner MC systems > Identity of partner MC service system Y Y Y Subclause 5.16.4 of 3GPP TS 22.280 [2] >> Access information for ACMS Y Y Y Subclause 5.16.4 of 3GPP TS 22.280 [2] >> List of authorized actions >>> Request to provide interconnection MC service group ID to partner MC system Y Y Y >>> Request to update members of an interconnection MC service group Y Y Y >>> Request to query interconnection MC service group ID from partner MC system Y Y Y >>> Request to add MC service users of its primary MC system for migration to partner MC system Y Y Y >>> Request to delete MC service users of its primary MC system from migration to partner MC system Y Y Y >>> Request to update MC service UE initial configuration of its primary MC system for MC service users at partner MC system which are permitted to migrate Y Y Y >>> Request to update MC service user profiles assigned by partner MC system for primary MC system’s user permitted to migrate Y Y Y A.10 Initial recording admin UE and/or replay UE configuration data The initial recording admin UE and/or replay UE configuration data is essential to the recording admin UEs and replay UEs to successfully connect to the MC system. Data in table A.10-1 is provided to the recording admin UEs and replay UEs clients (identity management client, configuration management client, replay client) during the bootstrap process of a recording admin UE and/or replay UE (see subclause 10.18.1.2 and 10.18.1.3) and can be configured offline using the CSC-11 reference point or via other means e.g. as part of the recording client’s or replay client’s provisioning on the UE, using a device management procedure. Table A.10-1: Initial recording admin UE and/or replay UE configuration data (on-network) Reference Parameter description Subclause 10.1.1 PDN connectivity information (NOTE 1) > HPLMN ID and optionally VPLMN ID to which the data pertains > MC common core services PDN >> APN >> PDN access credentials > MC identity management service PDN >> APN >> PDN access credentials Non-3GPP access network connectivity information (NOTE 2) Subclause 10.1.1 Application plane server identity information > Identity management server >> Server URI > Configuration management server >> Server URI > Recording server (NOTE 3) >> Server URI Subclause 10.1.1 Operational information > Recording admin and replay UE label (see NOTE 4) NOTE 1: The PDN connectivity information is included only when this UE uses 3GPP network to access the MC servers. NOTE 2: This parameter is included only when this UE uses non-3GPP access network to access the MC servers. The detailed parameters are out of scope of the present document. NOTE 3: This parameter shall be present only if this UE contains a replay client. NOTE 4: The Recording admin and replay UE label is optional. A.11 Recording admin and/or replay service user profile configuration data The recording admin and/or replay service user profile configuration data is stored in the configuration management server. The recording server and the group management server obtain the recording admin and/or replay service user profile configuration data from the configuration management server. Table A.11-1 contains the recording admin and/or replay service user profile configuration required to support the use of on-network recording and replay service. Data in table A.11-1 can be configured offline using the CSC-11 reference point. Table A.11-1: Recording admin and/or replay service user profile configuration data (on-network) Reference Parameter description Rec. admin UE & Replay UE Recording server Conf. mgmt server Group mgmt server [R-6.15.4-001…010] of 3GPP TS 22.280 [3] and subclause 5.2.4a Recording admin and replay user identity (MCRec ID) Y Y Y Y Subclause 5.2.4a Recording admin and/or replay user profile name Y Y Subclause 5.2.4a User profile status (enabled/disable) Y Y Y Y [R-6.15.4-001] of 3GPP TS 22.280 [17] and subclause 5.2.4a User's Mission Critical Organization Y Y Y Y [R-6.15.4-001] - [R-6.15.4-010] of 3GPP TS 22.280 [17] and subclause 5.2.4a Authorized to set and modify target MC service users for recording in his/her organization (yes/no) Y Y > All MC service users (see NOTE 1) >> MCPTT Y Y >> MCVideo Y Y > All MC service users with exceptions (see NOTE 1) >> List of exceptions (see NOTE 5) >>> MCPTT ID Y Y >>> MCVideo ID Y Y > Only the listed MC service users (see NOTE 1) >> List of users (see NOTE 5) >>> MCPTT ID Y Y >>> MCVideo ID Y Y [R-6.15.4-001] - [R-6.15.4-010] of 3GPP TS 22.280 [17] and subclause 5.2.4a Authorized to set and modify target groups for recording in his/her organization (yes/no) Y Y Y > All MC service groups (see NOTE 2) >> MCPTT Y Y Y >> MCVideo Y Y Y > All MC service groups with exceptions (see NOTE 2) >> List of exceptions (see NOTE 5) >>> MC service group ID Y Y Y >>> Group management server URI Y Y Y > Only the listed MC service groups (see NOTE 2) >> List of groups (see NOTE 5) >>> MC service group ID Y Y Y >>> Group management server URI Y Y Y [R-6.15.4-001] - [R-6.15.4-010] of 3GPP TS 22.280 [17] and subclause 5.2.4a Authorized to replay recordings of users in his/her organization (yes/no) Y Y Y > All MC service users (see NOTE 3) >> MCPTT Y Y Y >> MCVideo Y Y Y > All MC service users with exceptions (see NOTE 3) >> List of exceptions (see NOTE 5) >>> MCPTT ID Y Y Y >>> MCVideo ID Y Y Y > Only the listed MC service users (see NOTE 3) >> List of users (see NOTE 5) >>> MCPTT ID Y Y Y >>> MCVideo ID Y Y Y [R-6.15.4-001] - [R-6.15.4-010] of 3GPP TS 22.280 [17] and subclause 5.2.4a Authorized to replay recordings of MC service groups in his/her organization (yes/no) Y Y Y > All groups (see NOTE 4) >> MCPTT Y Y Y >> MCVideo Y Y Y > All MC service groups with exceptions (see NOTE 4) >> List of exceptions (see NOTE 5) >>> MC service group ID Y Y Y >>> Group management server URI Y Y Y > Only the listed groups (see NOTE 4) >> List of groups (see NOTE 5) >>> MC service group ID Y Y Y >>> Group management server URI Y Y Y NOTE 1: If authorized to set and modify target MC service users for recording, one and only one of these parameter sets shall be set. Recording of MCData users is not supported in this version of this specification. NOTE 2: If authorized to set and modify target groups for recording, one and only one of these parameter sets shall be set. Recording of MCData groups is not supported in this version of this specification. NOTE 3: If authorized to replay recordings of users, one and only one of these parameter sets shall be set. Recording/replay of MCData users is not supported in this version of this specification. NOTE 4: If authorized to replay recordings of groups, one and only one of these parameter sets shall be set. Recording/replay of MCData groups is not supported in this version of this specification. NOTE 5: The list may contain zero or more of each of its subitems, but if included, the list shall not be empty. Annex B (informative): Service continuity for MC service B.1 Service continuity between on-network MC service and UE-to-network relay MC service This annex describes how 3GPP TS 23.237 [10] mechanisms for IMS service continuity can be used to provide service continuity between on-network MC service and UE-to-network relay MC service. For illustration, MCPTT AS is considered as the MC service. Only the procedure for service continuity from on-network MCPTT service to UE-to-network relay MCPTT service is described in figure B.1-1. The procedure for service continuity in the opposite direction is identical. Figure B.1-1: Service continuity from on-network to UE-to-network relay As illustrated in figure B.1-1: - Initially UE-1 has a direct connection to the network (on-network MCPTT service). It is registered with the SIP core and is engaged in a SIP session with the MCPTT Application Server (solid lines SIP-1 and MCPTT-1 in figure B.1-1). - When UE-1 realises that it is losing connection to the network, or after the connection to the network has been lost, UE-1 discovers a UE-to-network relay (UE-R) and establishes a PC5 connection with UE-R. UE-1 registers with the SIP core over the target access leg and enters UE-to-network relay MCPTT service by transferring the media streams over the target leg (dashed lines SIP-1 and MCPTT-1 in figure B.1-1). - The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) before and after the handover, as described in 3GPP TS 23.237 [10]. Depicted in figure B.1-2 is the call flow for service continuity when the UE switches from on-network MCPTT service to UE-to-network MCPTT relay service. Figure B.1-2 Service continuity when UE switches from on-network MCPTT service to UE-to-network relay MCPTT service 0. UE-1 has a direct connection to the network and is engaged in a SIP session with the MCPTT AS (on-network MCPTT service). The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) and a Session transfer Identifier (STI) is assigned for the anchored SIP session, as described in 3GPP TS 23.237 [10]. 1. UE-1 realises that it is losing connection to the network or has completely lost it. 2. UE-1 (in the role of remote UE) performs ProSe UE-to-network relay discovery over PC5 and establishes a secure point-to-point link with the relay (UE-R) over PC5. As part of this process the remote UE is mutually authenticated at PC5 layer with either the relay or with the network as specified in 3GPP TS 23.303 [14]. In the process UE-1 is also assigned an IP address/prefix by the relay. NOTE 1: If step 2 is started after losing connection, the service interruption can be noticeable to the user. NOTE 2: Step 2 will be entirely described under in 3GPP TS 23.303 [14]. 3: UE-1 registers with the SIP core over the UE-to-network relay leg. 4. In order to transfer the media streams of the SIP session UE-1 sends an INVITE message on the new access leg towards the SCC AS. The INVITE message includes the STI identifying the session to be transferred. The SCC AS identifies the session based on STI and updates the session over the remote access leg i.e. towards the MCPTT AS. 5. The procedure is completed when all media streams have been transferred on the access leg relayed via UE-R. At this point UE-1 may deregister the on-network leg if it still has direct network connection (not shown in the figure). NOTE 3: The procedure for service continuity is always completed with unicast delivery on the target side. If MCPTT content is being distributed on the target side in multicast mode, then switching from unicast to multicast delivery is performed after completion of the service continuity procedure. Annex C (informative): Application Priority C.1 Use of application priorities Different communications between two or more MC service users need to be distinguished in their urgency in order to appropriately or less preferably allocate 3GPP system transport resources. Also simultaneous incoming communications to a MC service user requires an indication of the urgency in order to preferentially join the communication in accordance with the urgency. To make this distinction of urgencies, the MC system necessarily supports different types of priorities and corresponding levels within each priority category representing the relative importance of a request at the application level. The use of application priority allows the MC system to decide whether a communication establishment or modification request can be accepted or needs to be rejected (e.g. in case of transport resource limitations), or it allows the MC service client to rank simultaneous incoming communication for presentation to an MC service user. Hence the application priority can also be used to decide which existing transport resources (e.g. bearers) to pre-empt during resource limitations. Such pre-emption capability information defines whether a communication can obtain transport resources that were already assigned to another communication with a lower priority level. The pre-emption vulnerability information defines whether a communication can lose the resources assigned to it in order to admit a communication with higher priority level. The following types of application priorities are provided by the MC system: Figure C.1.-1: Types of application priorities in the MC system Communication priority involves a combination of the type of call/communication, the role of the requesting MC service user, and the predefined/requested priority of the initiating MC service user and/or group. Presentation priority involves the determination of which communications, from within multiple simultaneous possible, are the highest priority to present to the MC service user either audibly or visibly. An example would be a private call received at the same time as an emergency call on a monitored group. This category can be configured uniquely for each MC service user. Floor priority involves the determination of who can transmit within a communication at a particular time. This is essentially the priority of the MC service user according to its profile, and possibly modified by its role and/or mode of service (e.g. using emergency or imminent peril call). This category is used, for example, to determine the ordering of the floor control queue within an established communication. Annex D (informative): Considerations for MC gateway UE selection D.1 General Operating conditions can influence the selection and the use of the MC gateway. Multiple conditions can be considered by the non-3GPP device either to connect to another MC gateway UE (e.g. with better operating conditions for the requested service), or to re- connect to the same MC gateway UE (e.g. reattempt connection after a certain time). D.2 Potential operating Conditions Possible operating conditions information could belong to one of the following categories: MC gateway UE capacity limits The MC gateway UE might not be able to allow non-3GPP devices to connect when the limit of connected MC clients has been reached. 3GPP access congestion The MC gateway UE can make use of to the special Categories/Access Identity, the preferential access applies based on its assigned Access Control Class/Access Identity during periods of congestion. The MC gateway UE subscription allows to obtain priority treatment for the required communication. Nevertheless, the serving access network can indicate to the UEs (including MC gateway UE) that Access Class Barring applies and this can be passed by the MC gateway UE to the non-3GPP device. PLMN reselection PLMN reselection depends on operator policy, roaming agreements, and on national/regional regulatory requirements. Network status information If the network status information of an EPS/5GS capability available at MC gateway UE, it can be further propagated to the corresponding non-3GPP devices for further processing (e.g., if the requested QoS for service can be provided for MC client or not). Annex E (informative): MC gateway UE routing capabilities E.1 General When the MC client resides on a non-3GPP device the use of the MC gateway UE requires the support of an IP network behind the MC gateway UE, that a range of IP addresses is reachable over a single MC gateway UE. That enables the forwarding of signalling information and media plane between an MC client on the non-3GPP device and the MC server by the MC gateway UE. If the MC client resides on the MC gateway UE the MC gateway UE may support IP based and non-IP based connectivity behind it. E.2 MC client IP address association The use of a unique IP address by the MC clients shall be ensured for the period of association of the MC clients via the MC gateway UE with the IMS/SIP core and the MC server. Each MC gateway UE requires a unique IP address range for their MC client association which is known by the MC service environment and a correlation between the MC client's IP address and the MC gateway UE's IP address exists. Figure E.2.-1: MC client IP address relationship Framed routing in accordance with IETF RFC 2865 [32], IETF RFC 3162 [33], 3GPP TS 23.501 [34] shall be used to enable the support of an IP network behind the MC gateway UE, such that a range of IP addresses is reachable over a single 3GPP transport session. It allows the routing of packets to IP addresses that do not belong to the PDN/PDU session of the MC gateway UE. NOTE: The MC gateway UE can provide necessary IP address allocation to MC clients, e.g., as a DHCP relay agent in accordance with IETF RFC 1541 [35] and IETF RFC 8415 [36], or as a requesting router in accordance with IETF RFC 8415 [36] and 3GPP TS 23.401 [17] when using IPv6 prefix delegation. E.3 IP address association using the MC gateway UE If the MC client relies on IP address provided by the MC gateway UE, the MC gateway UE shall store the correlation between the non-3GPP device and the IP address (MC gateway UE IP and the local IP) used by the MC client . The procedures initiated by the MC client, i.e., SIP registration, user authentication and service authorisation use the MC gateway UE's IP address. The MC gateway UE assigns the local IPs from address pool which it maintains to the individual MC clients. Managing the local IP addresses, re-using the local IP address, and how the traffic is routed between the MC clients and the network is left for implementation. Figure E.3-1: non-3GPP device uses MC gateway UE's IP address Annex F (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-04 Initial version. 0.0.0 2016-04 Alignment with the following Rel-13 CRs agreed at SA6#10: CR0057(S6-160312), CR0063(S6-160189), CR0065(S6-160362),CR0068(S6-160348), CR0069(S6-160313), CR0070(S6-160280), CR0071(S6-160199), CR0079(S6-160360), CR0080(S6-160297), CR0085(S6-160361), CR0092(S6-160345), CR0095(S6-160339), CR0099(S6-160342) 0.1.0 2016-06 Implemented the following pCRs approved in SA6#11: S6-160378, S6-160489, S6-160492, S6-160504, S6-160524, S6-160528, S6-160560, S6-160561, S6-160570, S6-160578, S6-160579, S6-160583, S6-160600, S6-160601 Also implemented the Rapporteur actions from SA6#11: 1. Removed all colour coding from the TS 2. Fixed the subclauses numbering in the entire TS. 3. Generalized the text as per agreed terminology. 4. Added references for TS 23.303 and TS 23.237 0.2.0 2016-08 Implemented the following pCRs approved in SA6#12: S6-160794, S6-160795, S6-160796, S6-160797, S6-160798, S6-160799, S6-160880, S6-160888, S6-160919, S6-160920 0.3.0 2016-09 Implemented the pCR S6-160822 which was approved in SA6#12 Modified the references order 0.4.0 2016-10 Implemented the following pCRs approved in SA6#13: S6-160960, S6-161119, S6-161120, S6-161122, S6-161128, S6-161207, S6-161208, S6-161214, S6-161215, S6-161220, S6-161252, S6-161255 0.5.0 2016-11 Implemented the following pCRs approved in SA6#14: S6-161417, S6-161490, S6-161521, S6-161527, S6-161530, S6-161531, S6-161539, S6-161571, S6-161582, S6-161583, S6-161592, S6-161593, S6-161606, S6-161617, S6-161618, S6-161619, S6-161620, S6-161625, S6-161627, S6-161632, S6-161638 0.6.0 2016-11 SA#74 SP-160875 Submitted for Approval at SA#74 1.0.0 2016-12 SA#74 SP-160875 MCC Editorial update for publication after TSG SA approval (SA#74) 14.0.0 2017-03 SA#75 SP-170069 0001 1 F Alignment of definitions 14.1.0 2017-03 SA#75 SP-170069 0002 2 F Alignment of group affiliation and de-affiliation requirements 14.1.0 2017-03 SA#75 SP-170069 0003 1 F Alignment of bearer management 14.1.0 2017-03 SA#75 SP-170068 0004 1 F Removal of CSC-6 from figure 7.3.1-1 14.1.0 2017-03 SA#75 SP-170069 0005 1 F CFA Correction of information flow for MBMS 14.1.0 2017-03 SA#75 SP-170069 0009 1 F Corrections on group configuration tables 14.1.0 2017-03 SA#75 SP-170069 0012 1 F MBMS quality report clarifications 14.1.0 2017-03 SA#75 SP-170069 0014 2 D Resolving editor's note on service continuity 14.1.0 2017-03 SA#75 SP-170069 0015 2 F Clarification on Editor's notes in CFA 14.1.0 2017-03 SA#75 SP-170069 0020 3 F Add location management entities and reference points in figure 7.3.1-3 14.1.0 2017-03 SA#75 SP-170069 0022 1 F Clarification that initial UE config and UE config are specific to one or more UEs 14.1.0 2017-03 SA#75 SP-170069 0023 1 F Identities used in location information procedures 14.1.0 2017-06 SA#76 SP-170390 0024 1 F Correction on Annex A Configuration data for MC services 14.2.0 2017-06 SA#76 SP-170390 0033 1 F Addition of MC service to group configuration request 14.2.0 2017-06 SA#76 SP-170390 0034 F Miscellaneous corrections to configuration 14.2.0 2017-06 SA#76 SP-170390 0035 2 F Corrections on determination of MBMS bearer quality 14.2.0 2017-06 SA#76 SP-170390 0044 1 F Add note to bearer coordination procedure 14.2.0 2017-06 SA#76 SP-170390 0050 F Correction of information flow MBMS listening report 14.2.0 2017-06 SA#76 SP-170390 0054 1 F Alignment of server address with stage 3 14.2.0 2017-06 SA#76 SP-170390 0055 2 F Inclusion of KMSUri to allow multiple security domains 14.2.0 2017-06 SA#76 SP-170390 0063 1 F Corrections to Group configuration data for all MC services 14.2.0 2017-06 SA#76 SP-170396 0026 4 B Introduction of MC server initiated group de-affiliation procedure 15.0.0 2017-06 SA#76 SP-170396 0052 1 B Enhancement on group regrouping with an MC system 15.0.0 2017-06 SA#76 SP-170396 0053 3 B MC server initiated group de-affiliation from group(s) in partner system 15.0.0 2017-06 SA#76 SP-170396 0059 2 B Resource Management in CFA 15.0.0 2017-06 SA#76 SP-170397 0025 2 B MBMS bearer event notification 15.0.0 2017-06 SA#76 SP-170397 0043 4 B FEC for mission critical services 15.0.0 2017-06 SA#76 SP-170397 0058 1 B Header compression for MC services over MBMS 15.0.0 2017-09 SA#77 SP-170679 0070 1 A MC group configuration data correction 15.1.0 2017-09 SA#77 SP-170684 0073 2 B Application plane functional model for interconnection 15.1.0 2017-09 SA#77 SP-170684 0074 1 B Group configuration for interconnection 15.1.0 2017-09 SA#77 SP-170684 0075 2 B User profile retrieval for migration 15.1.0 2017-09 SA#77 SP-170683 0076 2 B Service type for group regroup 15.1.0 2017-09 SA#77 SP-170684 0077 2 C Rules for temporary groups 15.1.0 2018-01 SA#78 SP-170895 0066 9 B Retrieval of migration credentials for access to SIP core / IMS of a partner MC system 15.2.0 2018-01 SA#78 SP-170897 0070 2 A MC group configuration data correction 15.2.0 2018-01 SA#78 SP-170893 0071 4 B Priority between MC service servers 15.2.0 2018-01 SA#78 SP-170894 0072 3 C Multi-server MBMS bearer coordination 15.2.0 2018-01 SA#78 SP-170895 0079 1 B Architecture requirements for migration 15.2.0 2018-01 SA#78 SP-170895 0080 4 B Signalling plane functional model for interconnection 15.2.0 2018-01 SA#78 SP-170895 0081 1 B Architectural requirements for interconnection 15.2.0 2018-01 SA#78 SP-170895 0082 4 B Addition of interconnection affiliation 15.2.0 2018-01 SA#78 SP-170897 0086 3 F CR on clarification for MC service group ID 15.2.0 2018-01 SA#78 SP-170894 0088 1 F CR on MBMS usage for group configuration 15.2.0 2018-01 SA#78 SP-170893 0091 1 B Request for resources from MC service server 15.2.0 2018-01 SA#78 SP-170893 0092 2 B Functional model update 15.2.0 2018-01 SA#78 SP-170893 0093 1 F Location Server integration to PLMN 15.2.0 2018-01 SA#78 SP-170896 0094 1 B Introduction of multi-talker control 15.2.0 2018-01 SA#78 SP-170896 0095 4 B Introduction of Functional alias(es) 15.2.0 2018-01 SA#78 SP-170887 0096 D CR to replace uneditable figures 15.2.0 2018-01 SA#78 SP-170897 0097 1 F Renaming of "emergency condition" 15.2.0 2018-01 SA#78 SP-170895 0099 1 B Network selection for EPC-level roaming to support migration 15.2.0 2018-01 SA#78 SP-170896 0105 2 C Take over procedure for Functional alias(es) 15.2.0 2018-01 SA#78 SP-170896 0106 2 B Functional alias controlling role of MC service server 15.2.0 2018-01 SA#78 SP-170893 0107 1 F GMS selection during group regroup 15.2.0 2018-01 SA#78 SP-170893 0108 1 F Correction of "Group creation confirmation response" 15.2.0 2018-01 SA#78 SP-170895 0110 1 B Information flows for interconnection group configuration 15.2.0 2018-01 SA#78 SP-170895 0111 1 B Interconnection call procedures 15.2.0 2018-01 SA#78 SP-170895 0112 2 B Interconnection configuration enforcement 15.2.0 2018-01 SA#78 SP-170895 0113 1 B Interconnection media replication 15.2.0 2018-01 SA#78 SP-170895 0114 1 B Serving server and system definition 15.2.0 2018-01 SA#78 SP-170897 0115 2 F Renaming of "MCService emergency state cancel" 15.2.0 2018-01 SA#78 SP-170893 0117 2 F Addition to group configuration data 15.2.0 2018-01 SA#78 SP-170894 0118 F Removal of Editor's note in the procedures for MBMS usage 15.2.0 2018-01 SA#78 SP-170887 0120 1 A Add group deletion functionality 15.2.0 2018-01 SA#78 SP-170893 0122 2 B Provision of group dynamic data 15.2.0 2018-01 SA#78 SP-170895 0123 B Defintions of interconnection, migration and MC gateway server 15.2.0 2018-04 SA#79 SP-180154 0125 4 B Signalling plane registration for MC UE migration 15.3.0 2018-04 SA#79 SP-180153 0127 2 C Multi-server MBMS bearer coordination 15.3.0 2018-04 SA#79 SP-180145 0129 1 A Correction of security specification references 15.3.0 2018-04 SA#79 SP-180154 0130 F Correction of interconnection configuration enforcement figure 15.3.0 2018-04 SA#79 SP-180154 0131 1 B Interconnection subscription to group configuration 15.3.0 2018-04 SA#79 SP-180154 0131 6 B User authorization for interconnection and migration 15.3.0 2018-04 SA#79 SP-180154 0133 2 B Group configuration for interconnection 15.3.0 2018-04 SA#79 SP-180145 0135 1 A Aligning 10.9.3.1 procedure with diagram 15.3.0 2018-04 SA#79 SP-180149 0137 1 A Update of references to stage 1 specifications 15.3.0 2018-04 SA#79 SP-180154 0138 2 B Description of MC system identity 15.3.0 2018-04 SA#79 SP-180154 0139 2 B Functional model update for interconnection 15.3.0 2018-04 SA#79 SP-180154 0140 1 B Removal of editor's notes related to interconnection 15.3.0 2018-04 SA#79 SP-180154 0141 1 B Service configuration for migration 15.3.0 2018-04 SA#79 SP-180154 0142 1 B Update to connectivity for interconnection 15.3.0 2018-06 SA#80 SP-180371 0143 4 F Correction of MC service system 15.4.0 2018-06 SA#80 SP-180364 0145 2 A Clarification on MBMS bearer announcement 15.4.0 2018-06 SA#80 SP-180368 0146 F Functional model corrections 15.4.0 2018-06 SA#80 SP-180368 0149 1 F Handling of group configuration and group state over MBMS 15.4.0 2018-09 SA#81 SP-180676 0151 2 C Multicast application level control signal clarification 16.0.0 2018-12 SA#82 SP-181171 0153 2 A Editorial correction of figure in TS 23.280 16.1.0 2018-12 SA#82 SP-181172 0162 1 A Removal of notes for FEC and ROHC 16.1.0 2018-12 SA#82 SP-181177 0165 4 C Proposal for affiliation status information in group management server 16.1.0 2018-12 SA#82 SP-181177 0167 C Spelling of ProSe 16.1.0 2018-12 SA#82 SP-181177 0169 2 F Align UE configuration with TS 33.180 16.1.0 2018-12 SA#82 SP-181177 0171 1 B Regroup group configuration 16.1.0 2018-12 SA#82 SP-181174 0172 A Correcting title of a functional alias management subclause 16.1.0 2019-03 SA#83 SP-190073 0173 3 C Improvement of the group creation request 16.2.0 2019-03 SA#83 SP-190073 0174 2 B Broadcast group regroup 16.2.0 2019-03 SA#83 SP-190073 0178 1 B Group status notification over MBMS 16.2.0 2019-03 SA#83 SP-190075 0179 1 F Migration connectivity information 16.2.0 2019-03 SA#83 SP-190071 0180 - A Correction of emergency location triggering criteria 16.2.0 2019-03 SA#83 SP-190073 0181 4 B MBMS listening status report 16.2.0 2019-06 SA#84 SP-190482 0184 1 A Clarifications on functional alias controlling role 16.3.0 2019-06 SA#84 SP-190488 0185 3 B Functional alias information query 16.3.0 2019-06 SA#84 SP-190484 0186 1 F Add location management sever URI to initial MC service UE configuration 16.3.0 2019-06 SA#84 SP-190488 0187 4 F Functional alias alternative addressing for MCX services 16.3.0 2019-06 SA#84 SP-190488 0188 1 B Implicit functional alias management 16.3.0 2019-06 SA#84 SP-190484 0190 F Corrections to affiliation procedures 16.3.0 2019-06 SA#84 SP-190484 0191 3 F Affiliation clarifications 16.3.0 2019-06 SA#84 SP-190484 0192 1 C Preconfigured regroup information in dynamic data 16.3.0 2019-06 SA#84 SP-190484 0194 2 F Remove the duplicated Key Management Server URI definiton 16.3.0 2019-06 SA#84 SP-190484 0196 3 B Change to Location Subscription for notification immediate 16.3.0 2019-06 SA#84 SP-190488 0201 2 B Functional alias subscription and notification 16.3.0 2019-06 SA#84 SP-190488 0203 3 B Location information reporting based on functional alias 16.3.0 2019-06 SA#84 SP-190488 0204 2 F Functional alias clarifications 16.3.0 2019-06 SA#84 SP-190484 0205 2 F Abbreviations 16.3.0 2019-06 SA#84 SP-190484 0206 2 F Clarifications for group regroup rules 16.3.0 2019-09 SA#85 SP-190731 0182 4 C Configuration of the user notification in temporary group formation 16.4.0 2019-09 SA#85 SP-190731 0210 5 F Corrections to the emergency alert procedures 16.4.0 2019-09 SA#85 SP-190731 0211 3 F Corrections to clauses in 10.9 Location Management (on-network) 16.4.0 2019-09 SA#85 SP-190730 0220 2 F Functional model update for interconnection and migration 16.4.0 2019-09 SA#85 SP-190735 0207 3 B Providing activated functional alias information to the group controlling server 17.0.0 2019-09 SA#85 SP-190735 0208 2 B Providing the list of functional aliases used by affiliated group members 17.0.0 2019-09 SA#85 SP-190735 0209 1 B Prevent from de-affiliation when using a specific functional alias(es) 17.0.0 2019-12 SA#86 SP-191113 0221 4 F Introducing descriptive text describing the urgency handling in the MC service system 17.1.0 2019-12 SA#86 SP-191114 0222 2 B Addition of preconfigured regroup procedures 17.1.0 2019-12 SA#86 SP-191113 0223 1 F Corrections on functional alias to group binding 17.1.0 2019-12 SA#86 SP-191113 0224 C Resolving EN on functional alias to group binding impacts 17.1.0 2019-12 SA#86 SP-191114 0226 1 F Alignment on MCX emergency alert procedures 17.1.0 2019-12 SA#86 SP-191109 0228 1 A Alignment on MCX emergency alert procedures 17.1.0 2020-03 SA#87-E SP-200119 0233 1 F Add temporary group teardown within an MC system 17.2.0 2020-03 SA#87-E SP-200118 0236 1 B Purpose of requested priority 17.2.0 2020-07 SA#88-E SP-200342 0243 1 B Additional details to the Location information report 17.3.0 2020-07 SA#88-E SP-200342 0244 1 B Additional details to the Location information notification 17.3.0 2020-07 SA#88-E SP-200342 0245 1 B Additional details to the Location report response 17.3.0 2020-07 SA#88-E SP-200342 0246 1 B Additional details to the Location reporting procedures 17.3.0 2020-07 SA#88-E SP-200342 0248 1 F Replacing the usage of MCPTT with MC Service 17.3.0 2020-07 SA#88-E SP-200342 0249 3 F Corrections to the location information flows 17.3.0 2020-07 SA#88-E SP-200342 0250 1 F Location information in the emergency alert request 17.3.0 2020-07 SA#88-E SP-200342 0251 1 B Configuration location history reporting 17.3.0 2020-07 SA#88-E SP-200342 0252 1 B Cancel location history transmission 17.3.0 2020-07 SA#88-E SP-200342 0253 1 B Location history reporting 17.3.0 2020-07 SA#88-E SP-200342 0254 1 B Status location history reporting 17.3.0 2020-07 SA#88-E SP-200342 0255 1 B Clarification on setting the MBMS broadcast areas when activating MBMS bearer 17.3.0 2020-07 SA#88-E SP-200340 0257 1 B Communication security context when using functional alias 17.3.0 2020-07 SA#88-E SP-200342 0260 1 B Dynamic data associated with a group at GMS 17.3.0 2020-09 SA#89-E SP-200844 0258 5 B Clarification on user subscription, group policy and functional alias policy 17.4.0 2020-09 SA#89-E SP-200844 0261 1 F Removal of Editors Note related to functional alias resolution by LMS 17.4.0 2020-09 SA#89-E SP-200844 0267 F Private calls in emergency state 17.4.0 2020-09 SA#89-E SP-200844 0269 1 B Individual emergency alert cancel 17.4.0 2020-09 SA#89-E SP-200844 0270 1 D Clarification of MCX Administrator 17.4.0 2020-09 SA#89-E SP-200843 0273 B Functional alias configuration 17.4.0 2020-12 SA#90-E SP-200995 0275 1 C MC service emergency alert clarifications 17.5.0 2020-12 SA#90-E SP-200995 0278 1 B Request for network resources at session establishment from the MC service server 17.5.0 2021-04 SA#91-E SP-210180 0282 - F EN removal regarding MC system ID 17.6.0 2021-04 SA#91-E SP-210180 0283 1 B Introduction of MC service UE label for location reporting 17.6.0 2021-04 SA#91-E SP-210180 0284 1 F Functional alias takeover request related correction 17.6.0 2021-06 SA#92-E SP-210567 0262 3 C Clarification to location information cancel subscription 17.7.0 2021-06 SA#92-E SP-210567 0289 F Addition of MBMS suspension report information flow 17.7.0 2021-06 SA#92-E SP-210567 0290 1 F General corrections to MBMS procedures 17.7.0 2021-06 SA#92-E SP-210567 0291 F Corrections to location management procedures 17.7.0 2021-09 SA#93-E SP-210960 0292 2 A Clarification of MC service server retry for dedicated bearer request 17.8.0 2021-09 SA#93-E SP-210963 0293 2 F Clarifications for Location management PLUS NEW enhancements for MC service UE label 17.8.0 2021-09 SA#93-E SP-210963 0293 2 F Corrections to Location Information table in 10.9.2.3 17.8.0 2021-12 SA#94-E SP-211524 0296 F Clarification for Location reporting configuration 17.9.0 2021-12 SA#94-E SP-211524 0297 F Clarification for location reporting within MBSFN 17.9.0 2021-12 SA#94-E SP-211524 0304 1 F Clarification to MC group configuration procedures for interconnect 17.9.0 2021-12 SA#94-E SP-211529 0298 1 B Addition of definitions of terms and introduction related to MC gateway UE function 18.0.0 2021-12 SA#94-E SP-211529 0299 2 B Introduction of subclauses to capture MC gateway UE function details 18.0.0 2021-12 SA#94-E SP-211529 0300 B MCGWUE 3GPP access network related location information management 18.0.0 2021-12 SA#94-E SP-211529 0301 1 B MCGWUE_MBMS support for MC clients residing on non-3GPP devices 18.0.0 2021-12 SA#94-E SP-211529 0302 1 B Connection authorisation mechanisms 18.0.0 2021-12 SA#94-E SP-211529 0303 B Functional architecture 18.0.0 2022-03 SA#95-E SP-220109 0305 F Correction to On-demand usage of location information procedure 18.1.0 2022-03 SA#95-E SP-220106 0306 D Editorial corrections in section 11 on MC Gateway UE 18.1.0 2022-03 SA#95-E SP-220106 0307 1 B Functional model reference points 18.1.0 2022-03 SA#95-E SP-220106 0308 1 B Functional model media plane aspects 18.1.0 2022-03 SA#95-E SP-220106 0309 1 B Using identities behind the MC gateway UE 18.1.0 2022-03 SA#95-E SP-220106 0310 B MC gateway UE routing capabilties 18.1.0 2022-06 SA#96 SP-220478 0311 1 B MC gateway UE – MC client disconnection procedure 18.2.0 2022-06 SA#96 SP-220478 0312 1 F Clean-up of clause 11 specifying MC gateway UE support 18.2.0 2022-06 SA#96 SP-220478 0313 1 B Clarification regarding the protocol used on new reference points 18.2.0 2022-06 SA#96 SP-220478 0314 1 B Clarify the association between certain entities 18.2.0 2022-06 SA#96 SP-220477 0315 1 B Migration during an ongoing group communication 18.2.0 2022-06 SA#96 SP-220477 0317 1 B Private call using functional alias towards a partner MC system 18.2.0 2022-06 SA#96 SP-220478 0318 B Clarification of MC gateway UE selection 18.2.0 2022-06 SA#96 SP-220476 0319 F Corrections to the use of MC service system 18.2.0 2022-06 SA#96 SP-220478 0320 B Added MC GW UnMapGroupToBearer request and response support 18.2.0 2022-06 SA#96 SP-220477 0322 B Sharing location information across MC systems (functional model) 18.2.0 2022-06 SA#96 SP-220477 0323 1 B Sharing location information across MC systems (on-demand) 18.2.0 2022-06 SA#96 SP-220477 0324 B Sharing location information across MC systems (triggered) 18.2.0 2022-06 SA#96 SP-220477 0325 B Sharing location information across MC systems (subscription) 18.2.0 2022-06 SA#96 SP-220477 0326 B Sharing location information across MC systems (configuration) 18.2.0 2022-06 SA#96 SP-220477 0327 1 B Functional alias support for migrated users 18.2.0 2022-06 SA#96 SP-220478 0328 B MC GW UnMapGroupToBearer request and response procedure 18.2.0 2022-06 SA#96 SP-220477 0330 2 B Migration procedure during and ongoing private communication 18.2.0 2022-06 SA#96 SP-220477 0331 1 B Allow no roaming migration 18.2.0 2022-06 SA#96 SP-220478 0332 1 B IP Assignment support by MC Gateway UE 18.2.0 2022-09 SA#97 SP-220924 0329 2 B Allow the user to restrict the dissemination of the location information 18.3.0 2022-09 SA#97 SP-220926 0334 1 B Functional alias as target address towards a partner MCData system 18.3.0 2022-09 SA#97 SP-220924 0335 1 F Functional Alias URI requirement 18.3.0 2022-09 SA#97 SP-220927 0336 1 F MC client IP address relationship 18.3.0 2022-09 SA#97 SP-220926 0339 1 F Addition of functional alias that corresponds to the location information requesting MC service user 18.3.0 2022-09 SA#97 SP-220924 0340 1 B LMS access to all the MCX user profiles (functional model) 18.3.0 2022-09 SA#97 SP-220927 0341 2 C MC gateway UE association with one MC service 18.3.0 2022-09 SA#97 SP-220924 0342 1 C Removing unicast bearer status from MBMS bearer information 18.3.0 2022-09 SA#97 SP-220926 0346 1 F Terminology clean-up on the architectural requirements for migration 18.3.0 2022-09 SA#97 SP-220926 0347 1 D Editorial corrections in clause 10.16.2.3 18.3.0 2022-09 SA#97 SP-220924 0348 1 F Corrections to reference point CSC-16 18.3.0 2022-09 SA#97 SP-220924 0349 1 F SIP interface corrections for reference points CSC-7, CSC-19, CSC-20 18.3.0 2022-12 SA#98-e SP-221243 0351 1 F Clarification of use of QCI-69 bearer for HTTP-1 reference point 18.4.0 2022-12 SA#98-e SP-221247 0352 1 C Updating migration overview 18.4.0 2022-12 SA#98-e SP-221247 0353 5 B Private call towards a migrated MC service user 18.4.0 2022-12 SA#98-e SP-221243 0354 2 F Description for the terms used in the location management procedures 18.4.0 2022-12 SA#98-e SP-221247 0355 4 B Partner MC service server stores necessary information for communication redirection 18.4.0 2023-03 SA#99 SP-230289 0356 3 B Introduction of the ad hoc group emergency alert 18.5.0 2023-03 SA#99 SP-230287 0358 5 C Add Criteria to the Preconfigured Group Regroup Request 18.5.0 2023-03 SA#99 SP-230288 0363 3 B Migration service de-authorization procedure initiated by MC service server 18.5.0 2023-03 SA#99 SP-230287 0366 2 B Preconfigured regrouping support for MCPTT 18.5.0 2023-03 SA#99 SP-230288 0367 3 F Clarification on storing of MC service IDs mapping in Primary system during migration service authorization 18.5.0 2023-06 SA#100 SP-230710 0360 5 F Corrections related to MC gateway UE and identities 18.6.0 2023-06 SA#100 SP-230703 0364 3 B Updating the MC service user ID list within preconfigured user regroup 18.6.0 2023-06 SA#100 SP-230710 0365 3 F Terminology alignment within MC GW UE 18.6.0 2023-06 SA#100 SP-230703 0369 1 B User Location Authorization and Profile 18.6.0 2023-06 SA#100 SP-230703 0376 D Correct the repeated space errors in TS 23.280 18.6.0 2023-06 SA#100 SP-230703 0377 D Correct the spelling errors of words in TS 23.280. 18.6.0 2023-06 SA#100 SP-230708 0378 1 B Updates procedures for allowing subsequent MCVideo and MCData communications after an adhoc group emergency alert 18.6.0 2023-06 SA#100 SP-230708 0379 1 B Adhoc group emergency alert participants list notification 18.6.0 2023-06 SA#100 SP-230708 0380 1 B Clarification on emergency states in conjunction with adhoc group alert procedures 18.6.0 2023-06 SA#100 SP-230708 0382 2 F Behaviour corrections on ad hoc group emergency alert removal 18.6.0 2023-06 SA#100 SP-230708 0383 1 F Clarification on subsequent group call on ad hoc group for emergency alert 18.6.0 2023-06 SA#100 SP-230707 0384 2 F MC service authorization notification alignment 18.6.0 2023-06 SA#100 SP-230708 0389 4 B Ad hoc group emergency alert between multiple MC systems 18.6.0 2023-06 SA#100 SP-230703 0392 D Correct the errors in the use of singular and plural forms in TS 23.280 18.6.0 2023-06 SA#100 SP-230703 0393 D Remove the duplicate and extra words in the expression of TS 23.280. 18.6.0 2023-06 SA#100 SP-230703 0394 2 B Group de-affiliation for specific UE 18.6.0 2023-06 SA#100 SP-230710 0395 1 B MC gateway UE routing capabilities 18.6.0 2023-06 SA#100 SP-230703 0396 1 D Syncing Criteria changes with 23.379 18.6.0 2023-06 SA#100 SP-230703 0397 1 D Reference corrections in 10.6.3.3.2 18.6.0 2023-06 SA#100 SP-230708 0398 3 B Addressing EN related to implicit affiliation to ad hoc group alert participants 18.6.0 2023-06 SA#100 SP-230707 0399 1 B Updating private call using FA 18.6.0 2023-06 SA#100 SP-230703 0400 1 F Corrections to Ad hoc group emergency alert request information flow 18.6.0 2023-06 SA#100 SP-230703 0401 1 F Corrections to preconfigured regroup request information flow 18.6.0 2023-06 SA#100 SP-230703 0402 1 D Moving emergency alert information flow under emergency alert section 18.6.0 2023-06 SA#100 SP-230710 0403 F Corrections of the GW-local and GW-core interface 18.6.0 2023-09 SA#101 SP-231001 0361 6 F Resolving the target KMS URI for a migrated MC service user 18.7.0 2023-09 SA#101 SP-230998 0408 2 F Correction for group de-affiliation for specific UE 18.7.0 2023-09 SA#101 SP-230998 0411 1 F Adding group definitions (Common Core) 18.7.0 2023-09 SA#101 SP-231005 0414 1 F PDN connection establishment for MC service clients behind MC GW UE 18.7.0 2023-09 SA#101 SP-231005 0415 2 F GW reference point protocol 18.7.0 2023-09 SA#101 SP-231005 0416 F Correcting figure 11.4.3-1 18.7.0 2023-09 SA#101 SP-230998 0421 F Remove the EN in 10.15.1 18.7.0 2023-09 SA#101 SP-230998 0422 2 F Resolve the affiliation related EN in clause 5.2.5 18.7.0 2023-09 SA#101 SP-230998 0427 F Corrections to the informative wordings 18.7.0 2023-09 Re-implementation of CR 0422 Rev. 2 18.7.1 2023-09 SA#101 SP-231007 0409 3 B Adding chapter ‘Sharing administrative configuration between interconnected MC systems’ 19.0.0 2023-09 SA#101 SP-231002 0413 3 B Modify list of participants by changing the criteria during an ongoing ad hoc group emergency alert (single MC system) 19.0.0 2023-09 SA#101 SP-230999 0417 1 D Resources management procedures update 19.0.0 2023-09 SA#101 SP-230999 0418 1 F Resources management clauses title update 19.0.0 2023-09 SA#101 SP-230999 0419 2 F IE related to resources management 19.0.0 2023-09 Re-implementation of CR 0422 Rev. 2 19.0.1 2023-12 SA#102 SP-231560 0429 2 B Introduction of functional entities for supporting MCShAC 19.1.0 2023-12 SA#102 SP-231560 0430 3 B ACM client user profile configuration data 19.1.0 2023-12 SA#102 SP-231556 0431 1 C Additional information for ad hoc group emergency alert cancellation 19.1.0 2023-12 SA#102 SP-231556 0432 2 B Changing the criteria during an ongoing ad hoc group emergency alert (multiple MC systems) 19.1.0 2023-12 SA#102 SP-231557 0436 1 D Fixing typo in clause 10.16.5.2 19.1.0 2023-12 SA#102 SP-231554 0437 1 F Resolve regroup issue - general clause update 19.1.0 2023-12 SA#102 SP-231554 0438 2 F Preconfigured Group Regroup formation in a single MC system alignment in 10.15.3.2.1 19.1.0 2023-12 SA#102 SP-231554 0439 2 F Update Preconfigured User Regroup formation in a single MC system in 10.15.3.2.2 19.1.0 2023-12 SA#102 SP-231554 0440 1 F Update 10.15.3.3.1 Preconfigured Group Regroup formation in multiple MC systems 19.1.0 2023-12 SA#102 SP-231554 0441 1 B Add the regroup group member update during MCX session 19.1.0 2023-12 SA#102 SP-231554 0442 1 F Update preconfigured regroup information flows 19.1.0 2023-12 SA#102 SP-231554 0444 3 F Resolve the MCX-1 EN in clause 7.5.2.19 19.1.0 2023-12 SA#102 SP-231559 0446 1 A Definition of MC server 19.1.0 2023-12 SA#102 SP-231559 0455 2 A Correction to information flow description in 10.9.2.16 19.1.0 2023-12 SA#102 SP-231558 0458 1 A Reporting success or failure of an ad hoc group emergency alert request 19.1.0 2023-12 SA#102 SP-231558 0460 1 A Reporting success or failure of an ad hoc group emergency alert cancel request 19.1.0 2023-12 SA#102 SP-231558 0462 2 A Improving reliability of MC ad hoc group emergency alert 19.1.0 2023-12 SA#102 SP-231556 0464 2 B Distribute criteria of an ad hoc group emergency alert request to authorised users 19.1.0 2023-12 SA#102 SP-231560 0465 2 B Common ACM Procedure 19.1.0 2023-12 SA#102 SP-231560 0466 3 B ACM Group configuration management 19.1.0 2023-12 SA#102 SP-231554 0468 1 D Fix typing errors in TS 23.280 19.1.0 2023-12 SA#102 SP-231554 0469 1 B Corrections to MC service emergency alert cancel request information flow 19.1.0 2023-12 SA#102 SP-231556 0474 1 F Corrections on modifying the criteria during an ad hoc group alert (single MC system) 19.1.0 2023-12 SA#102 SP-231559 0496 1 A Connection/disconnection authorisation procedures 19.1.0 2023-12 SA#102 SP-231559 0501 1 A Corrections of the use of MC client term in MCGWUE 19.1.0 2024-03 SA#103 SP-240315 0506 1 B ACM providing interconnection MC service group ID 19.2.0 2024-03 SA#103 SP-240315 0507 1 B ACM user migration management 19.2.0 2024-03 SA#103 SP-240315 0508 1 B ACM updating MC service UE initial configuration for migration 19.2.0 2024-03 SA#103 SP-240315 0509 1 B ACM updating MC service user profiles assigned from partner MC system 19.2.0 2024-03 SA#103 SP-240305 0517 1 A Corrections to the IP model figures 19.2.0 2024-03 SA#103 SP-240313 0520 F Alignments regarding HTTP-3 and SIP-3 19.2.0 2024-03 SA#103 SP-240313 0521 2 F Minor corrections in clause 10.11 19.2.0 2024-03 SA#103 SP-240304 0534 1 A Reporting success or failure of an ad hoc group emergency alert initiation request (multiple MC systems) 19.2.0 2024-03 SA#103 SP-240304 0536 1 A Reporting success or failure of an ad hoc group emergency alert cancel request (multiple MC systems) 19.2.0 2024-03 SA#103 SP-240313 0537 F Reporting success or failure of an ad hoc group emergency alert modify criteria request 19.2.0 2024-03 SA#103 SP-240313 0538 F Reporting success or failure of an ad hoc group emergency alert modify criteria request (multiple MC systems) 19.2.0 2024-03 SA#103 SP-240297 0543 1 A Removal of procedure 10.1.6.2 on signalling plane registration between MC systems 19.2.0 2024-03 SA#103 SP-240313 0546 2 F Multiple logon device location reporting clarification 19.2.0 2024-03 SA#103 SP-240315 0549 1 F Correction of Information Flow 10.17.2.5 - Group membership update response 19.2.0 2024-06 SA#104 SP-240758 0551 1 A MC gateway UE updates for security alignment 19.3.0 2024-06 SA#104 SP-240768 0552 1 F Priority-based floor overriding when using multi-talker control 19.3.0 2024-06 SA#104 SP-240758 0558 1 A Clarification on MC gateway UE definition 19.3.0 2024-06 SA#104 SP-240758 0560 1 A Configuration for MC client on non-3GPP device 19.3.0 2024-06 SA#104 SP-240758 0561 1 F Indication for updating location reporting configuration 19.3.0 2024-07 SA#104 SP-240768 0551 1 F Reimplementation of the CR#0551 rev 1 19.3.1 2024-09 SA#105 SP-241226 0565 B Adding authorized actions to ACM client user profile configuration data 19.4.0 2024-09 SA#105 SP-241223 0567 1 B Functional architecture for MC service logging, recording and replay 19.4.0 2024-09 SA#105 SP-241226 0568 1 F MCShAC cleanup 19.4.0 2024-09 SA#105 SP-241226 0576 F MCShAC - corrections to clause numbers 19.4.0 2024-09 SA#105 SP-241224 0579 1 B Ad hoc group call procedure towards a migrated MC service user 19.4.0 2024-09 SA#105 SP-241224 0580 1 B Migration during Ad hoc group call procedure 19.4.0 2024-12 SA#106 SP-241722 0532 8 B MC service group ID(s) usage for location information request 19.5.0 2024-12 SA#106 SP-241721 0569 4 B Location reporting information obtained from the PLMN operator (LTE) 19.5.0 2024-12 SA#106 SP-241722 0584 3 B Updated functional architecture for recording and replay 19.5.0 2024-12 SA#106 SP-241721 0585 3 B Initial UE configuration for recording and replay 19.5.0 2024-12 SA#106 SP-241722 0586 3 B Configuration data for recording and replay service authorizations 19.5.0 2024-12 SA#106 SP-241721 0587 1 C Target group configuration for recording 19.5.0 2024-12 SA#106 SP-241723 0588 1 C Adding information elements to adhoc group emergency alert 19.5.0 2024-12 SA#106 SP-241723 0590 F Clarification on MC gateway UE routing capabilities 19.5.0 2024-12 SA#106 SP-241721 0591 3 F Clarifications to client-triggered location reporting procedure 19.5.0 2024-12 SA#106 SP-241721 0592 1 F Clarifications to client-triggered periodic location information report using functional alias 19.5.0 2024-12 SA#106 SP-241721 0593 1 F Correction to client-triggered one-time location information report for shared functional alias procedure 19.5.0 2024-12 SA#106 SP-241721 0594 1 F Correction to event-triggered location information notification procedure across MC systems 19.5.0 2024-12 SA#106 SP-241721 0596 1 F Clarifications in general location management clause 19.5.0 2024-12 SA#106 SP-241721 0597 2 C Including UE capabilities and information in the third-party registration step 19.5.0 2024-12 SA#106 SP-241721 0598 2 C Updating location user profile configuration data 19.5.0 2024-12 SA#106 SP-241723 0600 1 F Potential IMS limitations based on deployment scenarios after migration 19.5.0 2024-12 SA#106 SP-241707 0604 1 A Removing external applications access to MC services 19.5.0 2024-12 SA#106 SP-241721 0605 1 B Client-triggered location reporting cancel procedure 19.5.0 2024-12 SA#106 SP-241721 0609 1 B Requesting specific location information of MC service user on-demand or periodic 19.5.0 2024-12 SA#106 SP-241722 0610 1 B Amendments to location reporting configuration 19.5.0 2024-12 SA#106 SP-241721 0611 1 B Procedures for recording admin and replay service configuration 19.5.0 2024-12 SA#106 SP-241721 0612 1 B Information flows and procedures to set users and groups as targets for recording 19.5.0 2024-12 SA#106 SP-241722 0613 1 B Recording admin and replay service user profile requirements 19.5.0 2024-12 SA#106 SP-241721 0615 F Updated flowcharts for MC service configuration 19.5.0 2024-12 SA#106 SP-241722 0616 1 F Corrections 19.5.0 2024-12 SA#106 SP-241721 0617 1 B Trigger override and cancel trigger override procedure for location reporting 19.5.0 2024-12 SA#106 SP-241721 0618 1 F Adding default location reporting configuration to user profile 19.5.0 2024-12 SA#106 SP-241721 0619 B Editor's note about migration vs recording 19.5.0 2024-12 SA#106 SP-241721 0621 C Updating location procedures to align with the agreed configurations in CR0598 19.5.0 2024-12 SA#106 SP-241721 0622 1 C Including UE capabilities towards the partner MC system during migration 19.5.0 2024-12 SA#106 SP-241722 0623 2 C MC service server to Recording server interface description 19.5.0 2024-12 SA#106 SP-241707 0626 2 A Void MBMS bearer event notification procedure 19.5.0 2024-12 SA#106 SP-241707 0628 1 A Removing EN on Entering MC service emergency alert area 19.5.0 2024-12 SA#106 SP-241722 0629 1 B MCX Replay procedure 19.5.0 2024-12 SA#106 SP-241722 0630 1 B MC Recording procedures using Session Recording Protocol 19.5.0 2025-02 Re-application of CRs CR0611r1, CR0612r1 CR0629r1, CR0630r1 (and undoing CR0595r1 included in CR0630r1) 19.5.1 2025-03 SA#107 SP-250212 0624 4 F MC gateway UE fixes 19.6.0 2025-03 SA#107 SP-250211 0631 1 F Remove MCData recording from Rel-19 19.6.0 2025-03 SA#107 SP-250211 0632 1 F Corrections to IETF references 19.6.0 2025-03 SA#107 SP-250199 0635 1 A Resolve the EN in clause 7.5.2.23 19.6.0 2025-03 SA#107 SP-250199 0637 1 A Resolve the EN in clause 7.5.2.24 19.6.0 2025-03 SA#107 SP-250199 0639 1 A Resolve the EN in clause 7.5.3.4 19.6.0 2025-03 SA#107 SP-250199 0641 1 A Resolve the EN in clause 7.5.3.7 19.6.0 2025-03 SA#107 SP-250199 0645 1 A Resolve the EN in clause 10.8.3.2a.2 19.6.0 2025-03 SA#107 SP-250211 0646 1 F Adding a reference to TS 23.273 19.6.0 2025-03 SA#107 SP-250211 0647 1 F Correcting figure 7.3.1.2-1 and the text order in clause 10.9.1 19.6.0 2025-03 SA#107 SP-250199 0649 1 A Correction in MC service configuration on primary MC system 19.6.0 2025-03 SA#107 SP-250211 0650 1 F Clarifications to the definitions 19.6.0 2025-03 SA#107 SP-250199 0652 A Resolving an editor's note in clause describing MC service group affiliation and MC service group de-affiliation 19.6.0
|
89176587a041225641da2ef55c9ebaf5
|
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 are defined in 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3].
The present document is applicable primarily to mission critical video service using E-UTRAN access based on the common functional architecture for mission critical services defined in 3GPP TS 23.280 [6] and the EPC architecture defined in 3GPP TS 23.401 [8].
The MCVideo service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
|
89176587a041225641da2ef55c9ebaf5
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1".
[3] 3GPP TS 22.281: "Mission Critical Video services".
[4] 3GPP TS 23.002: "Network Architecture".
[5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[6] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[10] Void
[11] 3GPP TS 23.203: "Policy and charging control architecture".
[12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[13] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3".
[14] 3GPP TS 33.180: "Security of the mission critical service".
[15] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
3 Definitions, symbols and abbreviations
| |
89176587a041225641da2ef55c9ebaf5
|
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 client application function for the MCVideo service.
MCVideo group: An MC service group configured for MCVideo service.
MCVideo group affiliation: An MC service group affiliation for MCVideo.
MCVideo group de-affiliation: An MC service group de-affiliation for MCVideo.
MCVideo group home system: The mission critical system where the MCVideo group is defined.
MCVideo group host server: The MCVideo server within a mission critical system which provides centralised support for MCVideo services of an MCVideo group defined in a MCVideo group home system.
MCVideo ID: An instance of an MC service ID within the MCVideo service.
MCVideo server: An instance of an MC service server that provides the server application function for the MCVideo service.
MCVideo service: A video communication service supporting applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with strong security, high availability, reliability and priority handling.
MCVideo system: The collection of applications, services, and enabling capabilities required to provide Mission Critical video for a Mission Critical Organization.
MCVideo UE: An MC service UE that can be used to participate in MCVideo services.
MCVideo user: An MC service user who is authorized for MCVideo services via an MCVideo UE.
Transmission control: Video transmitting control mechanism in an MCVideo service that determines which participants have the authority to transmit video, and determines the onward downlink video transmission during a video call.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply:
Mission Critical
Mission Critical Applications
Mission Critical Service
Mission Critical Organization
Mission Critical System
For the purposes of the present document, the following terms given in 3GPP TS 22.179 [15] apply
Group-broadcast group
User-broadcast group
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.281 [3] apply:
Real Time
Real Time Video
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [6] apply:
Ad hoc Group Communication
MC service client
MC service group
MC service group affiliation
MC service group de-affiliation
MC service group home system
MC service group host
MC service ID
MC service server
Pre-arranged group
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
3.2 Symbols
|
For the purposes of the present document, the following symbols given in 3GPP TS 22.280 [2] apply:
Nc2
|
89176587a041225641da2ef55c9ebaf5
|
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
EPC Evolved Packet Core
GCS AS Group Communication Service Application Server
GCSE_LTE Group Communication Service Enabler over LTE
HTTP Hyper Text Transfer Protocol
IMS IP Multimedia Subsystem
MC Mission Critical
MCVideo Mission Critical Video
MCVideo group ID MCVideo group identity
MCVideo ID MCVideo user identity
ProSe Proximity-based Services
SIP Session Initiated Protocol
|
89176587a041225641da2ef55c9ebaf5
|
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 functional architecture for mission critical communication services defined in 3GPP TS 23.280 [6].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
5 Architectural requirements
| |
89176587a041225641da2ef55c9ebaf5
|
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 same organisation.
b) Option 2: The video media flow may be routed locally, under the control of the primary MCVideo system, through an entity allowing the duplication of the media flow to the primary MCVideo system of each user.
The video media flow for a group call shall be routed to the group home MCVideo system.
|
89176587a041225641da2ef55c9ebaf5
|
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 affiliated MCVideo group(s).
- MCVideo users select an affiliated MCVideo group to initiate a new group MCVideo call or transmit media in an existing MCVideo group call.
- MCVideo users receive media and events from their affiliated MCVideo group(s).
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
5.5 Bearer management
| |
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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.
|
89176587a041225641da2ef55c9ebaf5
|
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 depending on the MCVideo mode of the MCVideo call/session, as per table 5.5.3-1. For transmission and reception control signalling, the QCI value of 69 is recommended as specified in 3GPP TS 23.203 [11]. The request of resources over Rx shall include an application identifier for MCVideo in order for the PCRF to evaluate the correct QCI.
Table 5.5.3-1: QCI values to use for EPS unicast bearers for each MCVideo mode
MCVideo mode
QCI value utilised
(as specified in 3GPP TS 23.203 [11])
Urgent real-time mode
67
Non-urgent real-time mode
67
Non real-time mode
4
The MCVideo audio media and video media may transmit over separate EPS bearers, in which case the priority for each bearer is determined by the operator policy. Depending on operator policy, the MCVideo system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer.
NOTE: Operator policy takes into account regional/national requirements.
When MCVideo audio media and video media are multiplexed into one EPS bearer, then different QCI and/or ARP values are not possible for video and audio media.
|
89176587a041225641da2ef55c9ebaf5
|
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].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6 MCVideo Functional model
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.1 Functional model description
| |
89176587a041225641da2ef55c9ebaf5
|
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 accordance with 3GPP TS 23.280 [6].
- The MCVideo server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [9].
- MCVideo-9 carries signalling over multicast bearer between the transmission control server of the MCVideo server and the transmission control participant of the MCVideo UE.
- MCVideo-4 carries signalling over unicast bearer between the transmission control server of the MCVideo server and the transmission control participant of the MCVideo UE.
|
89176587a041225641da2ef55c9ebaf5
|
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
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2 Functional entities description
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.1 General
|
Each subclause is a description of a functional entity and does not imply a physical entity.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2 MCVideo service application plane
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.1 General
|
Entities within the application plane of MCVideo service provide application control, media transmission control and distribution functions.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.2 Common services core
|
The description of the common services core entities is contained in common functional architecture for MC services over LTE in 3GPP TS 23.280 [6].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3 MCVideo application service
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.1 MCVideo client
|
The MCVideo client functional entity acts as the user agent for all MCVideo application transactions.
The MCVideo client is responsible for remote device control. This functional entity is located in the UE for both on-network and off-network operations.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.2 MCVideo server
|
The MCVideo server functional entity provides centralised support for MCVideo services.
All the MCVideo clients supporting users belonging to a single group are required to use the same MCVideo server for that group. An MCVideo client supporting a user involved in multiple groups can have relationships with multiple MCVideo servers.
The MCVideo server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [6].
The MCVideo server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [9] to control multicast and unicast operations for group communications.
The MCVideo server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.
This MCVideo server provides support for centralised media transmission control for on-network and distributed media transmission control for off-network operation.
The MCVideo server is responsible for managing and providing the device information that can participate in MCVideo communications. The device information is further associated to MCVideo users to manage remote device control authorization. The device information is provisioned to the MCVideo server by the MCVideo service provider, mission critical organization and the MCVideo user.
The MCVideo server performing the functional alias controlling role is responsible for:
- interfacing with the functional alias management server for functional alias policy;
- functional alias activation, deactivation, take over and interrogation support for MCVideo user.
The controlling roles for group call, private call and functional alias are independent with each other.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.3 Media distribution function
|
The media distribution function is responsible for the distribution of media to MCVideo clients. The media distribution function may use different IP addresses than the MCVideo server. By means of information provided by the MCVideo server (e.g. IP addresses, transport layer ports), it will provide the following functionality:
- provide for the reception of uplink MCVideo UE media transmission by means of the MCVideo-7 reference point;
- storing the received media stream as MCVideo content files;
- replicate the media as needed for distribution to those participants using unicast transport;
- distribute downlink media to MCVideo UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCVideo-7 reference point;
- distribute downlink media to MCVideo UEs using multicast downlink transport of media for the call by means of the MCVideo-8 reference point; and
- provide a media mixing function where multiple media streams are combined into a single media stream for transmission to the MCVideo UE.
NOTE 1: If media mixing function occurs within the media distribution function, it operates independently of the media mixer in the UE.
NOTE 2: A media mixing function within the media distribution function is not possible where the media is end to end encrypted.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.4 Media mixer
|
This functional entity exists on the UE and provides support for sending and receiving one or multiple media streams. It also provides support for combining multiple media streams into one media stream through the enforcement of media policy information. It supports the storing of a media stream as MCVideo content files.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.5 MCVideo user database
|
This functional entity contains information of the MCVideo user profile associated with an MCVideo ID that is held by the MCVideo service provider at the application plane. The MCVideo user profile is determined by the mission critical organization, the MCVideo service provider, and potentially the MCVideo user.
The MCVideo ID is a MC service ID as described in clause 8 of 3GPP TS 23.280 [6]. The MCVideo user profile is a MC service user profile as described in clause 10.1.4 of 3GPP TS 23.280 [6].
The MCVideo user profile can be co-located with other MC service user profiles and stored in a common MC service user database.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.6 Transmission control server
|
This functional entity provides support for centralised transmission control for on-network and distributed transmission control for off-network operation. It may schedule transmission requests according to uplink criteria from different transmission control participants, send a notification to all transmission control participants to allow them to receive the video according to downlink criteria if the transmission request is granted, and provide queuing in cases of contention. Transmission control applies to all MCVideo communications including group call and private call. For on-network operation, this functional entity is located with the MCVideo server, however, the transmission control server may use different IP address. For off-network operation, this functional entity is located in the UE.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.7 Transmission control participant
|
The transmission control participant functional entity is responsible for handling outgoing transmission requests and the incoming video stream invitations and notifications. This functional entity is located in the UE for both on-network and off-network operations.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.2.2.3.8 MC gateway server
|
The MC gateway server provides support for MCVideo interconnection services with a partner MCVideo system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCVideo servers in the partner MCVideo system without needing to expose the MCVideo servers in the primary MCVideo system outside the trusted domain of the primary MCVideo system. It may be a role of the MCVideo server described in subclause 6.2.2.3.2 of the present document.
The MC gateway server is responsible for relaying call control and floor control signalling messages, and media between MCVideo servers within the MCVideo system and the interconnected MCVideo system.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3 Reference points
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.1 Reference point MCVideo-1 (between the MCVideo client and the MCVideo server)
|
The MCVideo-1 reference point, which exists between the MCVideo client and the MCVideo server, is used for MCVideo application signalling for establishing a session in support of MCVideo service.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.2 Reference point MCVideo-2 (between the MCVideo server and the MCVideo user database)
|
The MCVideo-2 reference point, which exists between the MCVideo server and the MCVideo user database, is used by the MCVideo server to obtain information about a specific user.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.3 Reference point MCVideo-3 (between the MCVideo server and the MCVideo server and between the MCVideo server and the MC gateway server)
|
The MCVideo-3 reference point exists between the MCVideo server and another MCVideo server and between the MCVideo server and the MC gateway server, and is used for MCVideo application signalling.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.4 Reference point MCVideo-4 (between the transmission control participant and the transmission control server)
|
The MCVideo-4 reference point, which exists between the transmission control participant and the transmission control server, is used for MCVideo transmission control signalling over unicast. The MCVideo-4 reference point uses the SGi reference point defined in 3GPP TS 23.002 [4].
6.3.4A Reference point MCVideo-5 (between the MCVideo server and the EPS)
The MCVideo-5 reference point, which exists between the MCVideo and the EPS, is used, subject to the conditions below, by the MCVideo server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [11].
MCVideo-5 is not used when the MCVideo service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCVideo service provider domain.
MCVideo-5 may be used 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.
NOTE: Any coordination between the P-CSCF use of Rx and the MCVideo server use of Rx (via MCVideo-5) from the MCVideo service provider domain is not specified in this release of this specification.
6.3.4B Reference point MCVideo-6 (between the MCVideo server and the EPS)
The MCVideo-6 reference point, which exists between the MCVideo server and the EPS, is used to request the allocation and activation of multicast transport resources for MCVideo application usage. The MCVideo-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [13].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.5 Reference point MCVideo-7 (between the media distribution function and the media mixer)
|
The MCVideo-7 reference point, which exists between the media distribution function and the media mixer, is used to exchange unicast media between the media distribution function of the MCVideo server and the media mixer of the MCVideo client. The MCVideo-7 reference point uses the SGi reference point defined in 3GPP TS 23.002 [4].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.6 Reference point MCVideo-8 (between the media distribution function and the media mixer)
|
The MCVideo-8 reference point, which exists between the media distribution function and the media mixer, is used by the media distribution function of the MCVideo server to send multicast media to the media mixer of the MCVideo client. The MCVideo-8 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.7 Reference point MCVideo-9 (between the transmission control participant and the transmission control server)
|
The MCVideo-9 reference point, which exists between the transmission control participant and the transmission control server, is used MCVideo transmission control signalling over multicast. The MCVideo-9 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
6.3.8 Reference point MCVideo-10 (between the MC gateway server and the MC gateway server in a different MCVideo system)
|
The MCVideo-10 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCVideo system for MCVideo application signalling for establishing MCVideo sessions, shall use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCVideo‑10 reference point between interconnected MCVideo systems.
6A Identities
The MCVideo service specific identities (e.g. MCVideo ID, MCVideo group ID) are described in clause 8 of 3GPP TS 23.280 [6].
6B Application of functional model to deployments
The application of the functional model to deployments, and description of various deployment scenarios for the MCVideo service, can be found in clause 9 of 3GPP TS 23.280 [6].
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7 Procedures and information flows
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.1 Group call
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.1.1 General
|
Group calls are enabled in both on-network and off-network.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.1.2 On-network group call
| |
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.1.2.1 General
|
This subclause contains procedures for group call across a single and multiple MCVideo servers, and associated functions such as emergency call, broadcast call and others.
Two variations of group call model are described in subclause 7.1.2.3, the pre-arranged group call and the chat group call. Each of the subsequent group call types in subclause 7.1.2.4 onwards are applicable to either call model.
|
89176587a041225641da2ef55c9ebaf5
|
23.281
|
7.1.2.2 Information flows for group call in on-network
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.