hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5 Architectural requirements
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.1 General requirements
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.1.1 Description
|
This clause specifies the general requirements for the support of MC services in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.1.2 Requirements
|
[AR-5.1.2-a] For the case of a backhaul failure between the radio access network and the macro 3GPP core network, the IOPS MC system shall provide support for MC services in the IOPS mode of operation until the failure is recovered.
[AR-5.1.2-b] MC service UEs within the coverage of the local IOPS 3GPP systems shall be able to provide MC services over the IOPS MC system.
[AR-5.1.2-c] The IOPS MC system shall provide mechanisms to verify the availability of MC service UEs within the IOPS MC system.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.2 MC service requirements
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.2.1 Description
|
This clause specifies the MC service requirements in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.2.2 Requirements
|
[AR-5.2.2-a] The following MCPTT service features shall be supported in the IOPS mode of operation
- MCPTT group call
- MCPTT emergency group call
- MCPTT private call
- MCPTT emergency private call
[AR-5.2.2-b] The following MCData service features shall be supported in the IOPS mode of operation
- MCData short data service
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.3 Network broadcast/multicast session requirements
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.3.1 Description
|
This clause specifies the network bearer requirements in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.3.2 Requirements
|
[AR-5.3.2-a] The IOPS MC system shall provide support for unicast session establishment and modification to support MC services via unicast transmissions in the IOPS mode of operation.
[AR-5.3.2-b] The IOPS MC system shall provide support for broadcast/multicast session establishment and modification to support MC services via multicast transmissions in the IOPS mode of operation.
[AR-5.3.2-c] The IOPS MC system shall support announcement of broadcast/multicast session to the MC service UEs.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.4 IP connectivity functionality
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.4.1 Description
|
The support of MC services in the IOPS mode of operation can be based on the support of the IP connectivity functionality. The IP connectivity functionality enables that MC services are provided by the MC service clients via the IOPS MC connectivity function.
An IOPS MC connectivity function supporting the IP connectivity functionality does not provide MC services. Instead, the IOPS MC connectivity function enables discovering MC service users and provides IP connectivity for the communication among the discovered MC service users, i.e. it distributes the related IP traffic to the MC service UEs over IP unicast and/or multicast transmissions. A MC service UE supporting the IP connectivity functionality in the IOPS mode of operation enables transmitting the IP packets related to a MC service communication over the IOPS MC connectivity function.
This clause specifies requirements for the support of the IP connectivity functionality in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.4.2 General requirements
|
[AR-5.4.2-a] The IOPS MC connectivity function supporting the IP connectivity functionality shall support discovering MC service users within the coverage of the local IOPS 3GPP system.
[AR-5.4.2-b] The IOPS MC connectivity function supporting the IP connectivity functionality shall support announcement, subscription and notification mechanisms for discovered MC service users supporting the IP connectivity functionality.
[AR-5.4.2-c] The IOPS MC connectivity function supporting the IP connectivity functionality shall provide IP connectivity for communication among MC service users requesting the support of the IP connectivity functionality.
[AR-5.4.2-d] The MC service UEs supporting the IP connectivity functionality in the IOPS mode of operation shall enable transmitting the IP packets related to a MC service communication over the IOPS MC connectivity function.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
5.4.3 Bearer management requirements
|
[AR-5.4.3-a] The MC service UEs shall use specific APNs or DNNs for the support of the IP connectivity functionality, as follows:
- An APN/DNN for the IOPS related application signalling related to the IP connectivity functionality support, e.g. for IOPS discovery, subscription and notification.
- An MC service APN/DNN for the communication with another MC user or group via the IOPS MC connectivity function based on the IP connectivity functionality, e.g. for the signalling and media.
[AR-5.4.3-b] The APNs for the IP connectivity functionality support shall be made available to the MC service UEs either via UE (pre)configuration or via initial UE configuration, as described in 3GPP TS 23.280 [3] , and 3GPP TS 23.289 [12].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
6 Involved business relationships
|
The description of the involved business relationships for the support of MC services in the IOPS mode of operation is contained in clause 6 of 3GPP TS 23.280 [3], and clause 6.4 of 3GPP TS 23.289 [12].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7 Functional model
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.1 General
|
The functional model to support MC services in the IOPS mode of operation in case of a backhaul failure consists of a set of functions and reference points.
NOTE: Terminology such as client and server are not meant to imply specific physical implementation of a functional entity.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.2 Description of the planes
|
The functional model for the support of MC services in the IOPS mode of operation is defined as a series of planes to allow for the breakdown of the architectural description.
The application plane supports all the necessary functions to establish and provide MC services in the IOPS mode of operation. The application plane uses the services of the signalling control plane to establish the association of the users involved in an MC service. The signalling control plane also offers access to and control of services across MC services.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.3 Functional model description
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.3.1 General
|
The application plane and signalling plane supporting the functional model for the IOPS mode of operation are described in this clause.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.3.2 Functional model for the signalling control plane in the IOPS mode of operation
|
Figure 7.3.2-1 shows the common functional model for the signalling control plane in the IOPS mode of operation.
Figure 7.3.2-1: Functional model for the signalling control plane in the IOPS mode of operation
NOTE: The functional model for the signalling plane in the IOPS mode of operation is described as a common functional model across MC services.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.3.3 MCPTT functional model for the application plane in the IOPS mode of operation
|
Figure 7.3.3-1 shows the MCPTT functional model for the application plane in the IOPS mode of operation.
Figure 7.3.3-1: MCPTT functional model for the application plane in the IOPS mode of operation
NOTE: MC-IOPS-1, MC-IOPS-5 and MC-IOPS-6 reference points are common across MC services.
In the model shown in figure 7.3.3-1, the following apply:
- MCPTT-IOPS-2 carries signalling related to the support of broadcast/multicast transmissions, e.g. MBMS bearer announcement, or 5G MBS session announcement, between the IOPS MC connectivity function and the MCPTT client.
- MCPTT-IOPS-3 carries signalling and media over IP unicast transmissions between the IOPS distribution function and the MCPTT client of the MCPTT UE.
- MCPTT-IOPS-4 carries signalling and media on downlink over IP multicast transmissions between the IOPS distribution function and the MCPTT client of the MCPTT UE.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.3.4 MCData functional model for the application plane in the IOPS mode of operation
|
Figure 7.3.4-1 shows the MCData functional model for the application plane in the IOPS mode of operation.
Figure 7.3.4-1: MCData functional model for the application plane in the IOPS mode of operation
NOTE: MC-IOPS-1, MC-IOPS-5 and MC-IOPS-6 reference points are common across MC services.
In the model shown in figure 7.3.4-1, the following apply:
- MCData-IOPS-2 carries signalling related to the support of broadcast/multicast transmissions, e.g. MBMS bearer announcement, or 5G MBS session announcement, between the IOPS MC connectivity function and the MCData client.
- MCData-IOPS-3 carries signalling and media over IP unicast transmissions between the IOPS distribution function and the MCData client of the MCData UE.
- MCData-IOPS-4 carries signalling and media on downlink over IP multicast transmissions between the IOPS distribution function and the MCData client of the MCData UE.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4 Functional entities description
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1 Application plane
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1.1 General
|
Entities within the application plane of an IOPS MC system provide application specific functions to support MC services in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1.2 IOPS connectivity client
|
The IOPS connectivity client functional entity provides support for enabling that a user at the MC service client is registered and discovered by the IOPS MC system in the IOPS mode of operation. This functional entity is located in the MC service UE.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1.3 IOPS MC connectivity function
|
The IOPS MC connectivity function entity provides supporting MC services in the IOPS mode of operation. It includes registering and discovering users within the IOPS MC system. The IOPS MC connectivity functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [4] for EPS or Application Function (AF) for 5GS to manage unicast and multicast transmissions for group communication related sessions.
The IOPS MC connectivity function entity is supported by the signalling application server functional entity of the signalling control plane.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1.4 IOPS distribution function
|
The IOPS distribution function entity provides support for distributing the IP packets containing the MC service application data received from a MC service UE in the IOPS mode of operation.
By means of information provided by the IOPS MC connectivity function (e.g. IP addresses, transport layer ports), it will provide the following functionality:
- receiving uplink IP transmissions from the MC service UE by means of the MCPTT-IOPS-3 reference point for MCPTT and the MCData-IOPS-3 reference point for MCData;
- distributing the related IP packets via downlink IP unicast transmissions to MC service UEs by means of the MCPTT-IOPS-3 reference point for MCPTT and the MCData-IOPS-3 reference point for MCData;
- distributing the related IP packets via downlink IP multicast transmissions to MC service UEs by means of the MCPTT-IOPS-4 reference point for MCPTT and the MCData-IOPS-4 reference point for MCData.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.1.5 MC service client
|
The MC service client functional entity, e.g. a MCPTT client and a MCData client, supporting the IOPS mode of operation acts as the user agent for the corresponding MC service transactions as well as all IOPS related application transactions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.2 Signalling control plane
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.2.1 Signalling user agent client
|
The signalling user agent client functional entity supports at the MC service client all required transactions related to the IOPS discovery. This includes supporting registration, publication, subscription and notification events.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.4.2.2 Signalling application server
|
The signalling application server functional entity supports at the IOPS MC system all required transactions related to the IOPS discovery. This includes supporting registration, publication, subscription and notification events.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5 Reference points
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1 Application plane
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.1 Reference point MC-IOPS-1 (between the IOPS MC connectivity function and the IOPS connectivity client)
|
The MC-IOPS-1 reference point, which exists between the IOPS MC connectivity function and the IOPS connectivity client, is used for IOPS related application signalling (e.g. registration, publication, subscription and notification events). The MC-IOPS-1 reference point utilizes the MC-IOPS-X1 reference point for transport and routing of the IOPS related signalling.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.2 Reference point MCPTT-IOPS-2 (between the IOPS MC connectivity function and the MCPTT client)
|
The MCPTT-IOPS-2 reference point, which exists between the IOPS MC connectivity function and the MCPTT client, is used to communicate signalling related to the broadcast/multicast sessions utilized for multicast transmissions, e.g. MBMS bearer announcement or 5G MBS session announcement in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.3 Reference point MCData-IOPS-2 (between the IOPS MC connectivity function and the MCData client)
|
The MCData-IOPS-2 reference point, which exists between the IOPS MC connectivity function and the MCData client, is used to communicate signalling related to the broadcast/multicast sessions utilized for multicast transmissions, e.g. MBMS bearer announcement or 5G MBS session announcement in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.4 Reference point MCPTT-IOPS-3 (between the IOPS distribution function and the MCPTT client)
|
The MCPTT-IOPS-3 reference point, which exists between the IOPS distribution function and the MCPTT client, is used for IP unicast transmissions in uplink and downlink. The MCPTT-IOPS-3 reference point uses the SGi reference point as defined in 3GPP TS 23.002 [7] or N6 reference point as defined in 3GPP TS 23.501 [13].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.5 Reference point MCData-IOPS-3 (between the IOPS distribution function and the MCData client)
|
The MCData-IOPS-3 reference point, which exists between the IOPS distribution function and the MCData client, is used for IP unicast transmissions in uplink and downlink. The MCData-IOPS-3 reference point uses the SGi reference point as defined in 3GPP TS 23.002 [7] or N6 reference point as defined in 3GPP TS 23.501 [13].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.6 Reference point MCPTT-IOPS-4 (between the IOPS distribution function and the MCPTT client)
|
The MCPTT-IOPS-4 reference point, which exists between the IOPS distribution function and the MCPTT client, is used for IP multicast transmissions in downlink. The MCPTT-IOPS-4 reference point uses the MB2-U reference point as defined in 3GPP TS 23.468 [4] or Nmb8/ Nmb6 reference point as defined in 3GPP TS 23.247 [14].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.7 Reference point MCData-IOPS-4 (between the IOPS distribution function and the MCData client)
|
The MCData-IOPS-4 reference point, which exists between the IOPS distribution function and the MCData client, is used for IP multicast transmissions in downlink. The MCData-IOPS-4 reference point uses the MB2-U reference point as defined in 3GPP TS 23.468 [4] or Nmb8/ Nmb6 reference point as defined in 3GPP TS 23.247 [14].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.8 Reference point MC-IOPS-5 (between the IOPS MC connectivity function and the IOPS 3GPP system)
|
The MC-IOPS-5 reference point, which exists between the IOPS MC connectivity function and the IOPS 3GPP system, is used to obtain unicast sessions with appropriate QoS from the IOPS 3GPP system. The MC-IOPS-5 reference point utilizes the Rx interface of the EPS according to 3GPP TS 23.203 [8] , or N5 interface of 5GS according to 3GPP TS 23.503 [15].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.1.9 Reference point MC-IOPS-6 (between the IOPS MC connectivity function and the IOPS 3GPP system)
|
The MC-IOPS-6 reference point, which exists between the IOPS MC connectivity function and the 3GPP system (IOPS EPS), is used to request the allocation and activation of broadcast/multicast transport resources, i.e. MBMS bearers or 5G MBS sessions, during the IOPS mode of operation. The MC-IOPS-6 reference point uses the MB2-C interface as defined in 3GPP TS 23.468 [4], or Nmb10, Nmb13, or N33, as defined in 3GPP TS 23.247 [14].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.2 Signalling control plane
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
7.5.2.1 Reference point MC-IOPS-X1 (between the signalling application server and the signalling user agent client)
|
The MC-IOPS-X1 reference point, which exists between the signalling application server and the signalling user agent client, is used to support the IOPS related application signalling (e.g. registration, publication, subscription and notification events).
NOTE: The IOPS related signalling supporting, e.g., the IOPS discovery, subscription and notification events can be SIP-based. In such a case, the signalling application server acts as a SIP application server (AS) or application function (AF) and the signalling user agent client acts as the SIP user agent for all SIP related transactions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8 Identities
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1 Application plane
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.1 IOPS MC user identity (IOPS MC ID)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.1.1 General
|
The IOPS MC ID is used for identifying an MC user in the IOPS mode of operation. The IOPS MC ID uniquely identifies an MC user on the IOPS MC system.
The IOPS MC ID can be used for the user authentication with the IOPS MC system.
NOTE: The specific security and authentication mechanisms required in order to use the IOPS MC user identity need to be specified by SA3.
Editor's Note: Adding reference to the IOPS user authentication procedure in SA3 TS is FFS.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.2 IOPS MC service user identity (IOPS MC service ID)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.2.1 General
|
The IOPS MC service ID is a unique identifier within the MC service that represents the MC service user in the IOPS mode of operation. The IOPS MC service ID is the IOPS MCPTT ID for the MCPTT service as defined in 3GPP TS 23.379 [5], and is the IOPS MCData ID for the MCData service as defined in 3GPP TS 23.282 [6].
NOTE: MCVideo service as defined in 3GPP TS 23.281 [10] is not supported in the current release.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.3 IOPS MC service group identity (IOPS MC service group ID)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.3.1 General
|
An IOPS MC service group ID is used for identifying an MC service group in the IOPS mode of operation. The MC service UE is able to make one or more MC service communications (as per the group configuration) with other member UEs whose users are within the same IOPS MC service group ID.
The general description of an MC service group ID is provided in 3GPP TS 23.280 [3].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
8.1.3.2 IOPS MC service group ID management (IP connectivity functionality)
|
Figure 8.1.3.2-1 illustrates how the IOPS MC service group ID and the IOPS group IP multicast address are mapped to each other for the support of the IP connectivity functionality. The IOPS group IP multicast address is pre-configured in the MC service UEs supporting the IOPS mode of operation in accordance with the IOPS MC service group ID.
NOTE: The association between the IOPS MC service group ID and the IOPS group IP multicast address may be pre-defined in the MC services UEs.
Figure 8.1.3.2-1: IOPS MC service group ID management (IP connectivity functionality)
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9 Application of functional model to deployments
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.1 Overview
|
The IOPS architectural model includes application functions at the IOPS MC system and UEs to support MC services in the IOPS mode of operation during a backhaul failure. The IOPS MC system provides MC services support to the MC service UE via a single PLMN dedicated to the IOPS mode of operation.
The architectural model to support MC services in the IOPS mode of operation consists of a signalling control plane and an application plane. The signalling control plane provides the necessary signalling support for the related IOPS application layer transactions, e.g. the registration and discovery of UEs on the IOPS MC system. The IOPS application plane provides the necessary support for the transport of the IOPS operation related application data as well as the IP packets containing the MC service application data to be distributed via the IOPS MC system.
The MC service application data includes all signalling control data and application data (control and media) required to provide MC services between MC service clients. The IP related transmissions are established over the IOPS MC system via IP unicast and multicast transmissions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.2 IOPS architectural model diagram
|
Figure 9.2-1 shows the IOPS architectural model for the IOPS MC system solution in case of a backhaul failure.
Figure 9.2-1: Architectural model in the IOPS mode of operation
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.2.1 IOPS application services support layer
|
The IOPS MC system is composed of the following functional entities for the support of MC services in the IOPS mode of operation:
- an IOPS MC connectivity function as described in clause 7.4.1.3, an IOPS distribution function as described in clause 7.4.1.4 and a signalling application server as described in clause 7.4.2.2.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.2.2 IOPS 3GPP system
|
A IOPS 3GPP system can comprise either:
- a local core network and a single isolated IOPS-capable base station, which may be co-located or have connectivity to the local core network; or
- a local core network and two or more IOPS-capable base station, which have connectivity to a single local core network.
NOTE: For 4G IOPS, the implementation and deployment guidelines using a Local EPC approach is described in 3GPP TS 23.401 [2].
The IOPS 3GPP system provides point-to-point and/or point-to-multipoint transmission services with QoS in the IOPS mode of operation, e.g., as described in 3GPP TS 23.401 [2] for EPS.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.2.3 UE 1
|
The UE 1 is an MC service UE supporting the IOPS mode of operation. It supports bearer services and applications to provide MC services over the IOPS MC system. The UE 1 is composed of the following functional entities:
- for MC services over the IOPS MC system, MC service client(s) as described in clause 7.4.1.5;
- for IOPS application plane, an IOPS connectivity client as described in clause 7.4.1.2; and
- for IOPS signalling control, a signalling user agent as described in subclause 7.4.2.1.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
9.2.4 UE 2
|
The UE 2 represents one or more UEs with the same functionality as UE 1.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10 Procedures and information flows
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.1 User authentication in the IOPS mode of operation
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.1.1 General
|
The following clause describes a high level procedure used for the user authentication in the IOPS mode of operation.
NOTE: The specific user authentication required in the IOPS mode of operation needs to be specified by SA3.
Editor's Note: Adding reference to the IOPS user authentication procedure in SA3 TS is FFS.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.1.2 Procedure
|
A procedure for the user authentication in the IOPS mode of operation is illustrated in figure 10.1.2-1.
Figure 10.1.2-1 User authentication in the IOPS mode of operation
1. The IOPS connectivity client initiates the IOPS user authentication procedure with the IOPS MC connectivity function.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2 IOPS discovery (IP connectivity functionality)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.1 General
|
The support of the IP connectivity functionality in the IOPS mode of operation enables that MC services are provided by the MC service clients via the IOPS MC connectivity function. An IOPS MC connectivity function provides IP connectivity for the communication among MC service users based on an IOPS discovery procedure.
The IOPS discovery procedure enables that the IOPS MC connectivity function discovers MC service users within the coverage of the system and receives connectivity information required to establish a communication between discovered users based on the IP connectivity functionality.
The following clauses specify the IOPS discovery procedure and information flows for the IP connectivity functionality in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.2 Information flows
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.2.1 IP connectivity request
|
Table 10.2.2.1-1 describes the information flow for the IP connectivity request from the IOPS connectivity client to the IOPS MC connectivity function.
Table 10.2.2.1-1: IP connectivity request
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the user requesting support of the IP connectivity functionality
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.2.2 IP connectivity response
|
Table 10.2.2.2-1 describes the information flow for the IP connectivity response from the IOPS MC connectivity function to the IOPS connectivity client.
Table 10.2.2.2-1: IP connectivity response
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the user requesting support of the IP connectivity functionality
IP connectivity support
M
It indicates if the IP connectivity functionality is supported or not for the user
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.2.3 IOPS discovery request
|
Table 10.2.2.3-1 describes the information flow for the IOPS discovery request from the IOPS connectivity client to the IOPS MC connectivity function.
Table 10.2.2.3-1: IOPS discovery request
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the requesting MC user
IP connectivity information
M
It includes the requesting MC service UE's IP address (see NOTE 1)
List of IOPS MC service group ID (see NOTE 2)
M
It includes the IOPS group (IOPS MC service group ID and its associated IOPS group IP multicast address) or list of IOPS groups the requesting MC user is configured with
Availability of connectivity information
O
It indicates if the connectivity information of the requesting MC user can be made available to other users on the system
List of IOPS MC service IDs (see NOTE 2 and NOTE 3)
O
The specific list of IOPS MC service IDs that the requesting MC user's connectivity information can be shared with
Priority state
M
Indicates whether the requesting MC user is requesting higher priority or not
NOTE 1: The MC service UE's IP address is assigned by the IOPS 3GPP system based on the PDN connection or PDU session established by the MC user for the IOPS IP connectivity functionality.
NOTE 2: The list of IOPS MC service IDs or IOPS MC service group IDs shall be of the same MC service as the MC user requesting to be discovered.
NOTE 3: If present, the user's connectivity information availability can be only made available to the provided specific list of IOPS MC service IDs.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.2.4 IOPS discovery response
|
Table 10.2.2.4-1 describes the information flow for the IOPS discovery response from the IOPS MC connectivity function to the IOPS connectivity client.
Table 10.2.2.4-1: IOPS discovery response
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the user requesting to be discovered
Connectivity status
M
It indicates the connectivity status of the requesting MC user on the system
IOPS discovery request periodicity
M
It indicates the periodicity at which the requesting MC user is required to transmit IOPS discovery requests (see NOTE)
NOTE: An MC user is required to periodically transmit an IOPS discovery request. The periodic IOPS discovery requests are used by the IOPS MC connectivity function to verify the availability of the MC user and its IP connectivity information within the IOPS MC system.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.2.3 Procedure
|
After an MC service user is authenticated on the IOPS MC connectivity function, the IOPS discovery procedure is initiated by the MC users requesting support of the IP connectivity functionality to the IOPS MC connectivity function. If the IOPS MC connectivity function indicates the support of the IP connectivity functionality, the MC service users can send an IOPS discovery request.
The procedure for requesting support of the IP connectivity functionality by the IOPS connectivity client to the IOPS MC connectivity function is described in figure 10.2.3-1.
NOTE 1: The procedure for requesting support of the IP connectivity functionality is only required when the IOPS connectivity client does not contain information about the support of this functionality by the serving IOPS MC connectivity function.
Pre-conditions:
- The MC service user is authenticated on the IOPS MC connectivity function.
- The MC service user has an active PDN connection or a PDU session to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The IOPS connectivity client does not contain information about the support of the IP connectivity functionality by the serving IOPS MC connectivity function
Figure 10.2.3-1 IP connectivity functionality request in the IOPS mode of operation
1. The IOPS connectivity client requests to the IOPS MC connectivity function the support of the IP connectivity functionality.
2. The IOPS MC connectivity function indicates to the IOPS connectivity client if the IP connectivity functionality is supported or not for the MC user.
The procedure for the discovery of MC users in the IOPS mode of operation is described in figure 10.2.3-2. The IOPS discovery is initiated by the MC users to support MC services based on the IP connectivity functionality.
As part of the IOPS discovery procedure, an MC user can request higher priority from the IOPS MC connectivity function by including a priority state indication within the IOPS discovery request. Based on this indication, the IOPS MC connectivity function can decide to handle with higher priority the transactions related to the MC user, e.g. the distribution of packets related to any MC communication from or to the corresponding MC user, subscriptions, and notifications. When an MC user intends to establish an IOPS emergency (group or private) call, the MC user can request a priority state from the IOPS MC connectivity function.
The MC user's priority state remains unchanged until the MC user explicitly changes it (i.e. by sending a new IOPS discovery request) or the discovery status of the MC user changes to not-discovered on the IOPS MC connectivity function.
Pre-conditions:
- The MC service user is authenticated on the IOPS MC connectivity function.
- The MC service user has an active PDN connection or PDU session to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The IOPS MC connectivity function has indicated to the IOPS connectivity client the support of the IP connectivity functionality.
Figure 10.2.3-2 User discovery in the IOPS mode of operation
1. The MC user sends an IOPS discovery request to the IOPS MC connectivity function. The request includes providing connectivity information for the support of MC services based on the IP connectivity functionality.
2. The IOPS MC connectivity function stores the information received from the MC user and registers the user's connectivity status as discovered.
3. The IOPS MC connectivity function provides a response to the IOPS connectivity client indicating the success or failure of the discovery of the requesting MC user.
NOTE 2: The MC user shall send a new IOPS discovery request to update or modify information elements.
NOTE 3: The IOPS MC connectivity function shall send a new IOPS discovery response to the IOPS connectivity client for the case that the periodic IOPS discovery request has not been received yet or when the IOPS discovery request periodicity needs to be changed. The IOPS MC connectivity function can verify the availability and IP connectivity information of the discovered MC user within the IOPS MC system based on the reception of periodic IOPS discovery requests.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3 IOPS subscription and notification (IP connectivity functionality)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.1 General
|
The support of the IP connectivity functionality in the IOPS mode of operation enables that MC services are provided by the MC service clients over the IOPS MC connectivity function. An MC user that has been discovered by the IOPS MC connectivity function can subscribe to be notified about the connectivity information of other discovered MC users on the IOPS MC connectivity function. Also, a discovered MC user can subscribe to be notified about the number of other discovered MC users on the IOPS MC connectivity function within its associated IOPS groups.
The following clauses specify the IOPS subscription and notification procedures and information flows for the IP connectivity functionality in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2 Information flows
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.1 IP connectivity subscribe request
|
Table 10.3.2.1-1 describes the information flow for the IP connectivity subscribe request from the IOPS connectivity client to the IOPS MC connectivity function.
Table 10.3.2.1-1: IP connectivity subscribe request
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the requesting MC user
List of IOPS MC service IDs (see NOTE 1)
O
List of IOPS MC service IDs the requesting MC user subscribes to receive connectivity information from
List of IOPS groups
(see NOTE 1 and NOTE 2)
O
List of IOPS groups (IOPS MC service group IDs) the requesting MC user subscribes to receive group connectivity information from
NOTE 1: The list of IOPS MC service IDs or IOPS MC service group IDs shall be of the same MC service as the MC user subscribing to receive the connectivity information. At least one should be present.
NOTE 2: The IOPS group(s) should belong to the list of IOPS groups the requesting MC user included in its IOPS discovery request.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.2 IP connectivity subscribe response
|
Table 10.3.2.2-1 describes the information flow for the IP connectivity subscribe response from the IOPS MC connectivity function to the IOPS connectivity client.
Table 10.3.2.2-1: IP connectivity subscribe response
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the requesting MC user
Subscription status
M
It lists the subscription status, success or failure, of the requested subscription(s)
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.3 IP connectivity notify request
|
Table 10.3.2.3-1 describes the information flow for the IP connectivity notify request from the IOPS MC connectivity function to the IOPS connectivity client.
Table 10.3.2.3-1: IP connectivity notify request
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the MC user with active subscription(s)
IOPS MC service ID
(see NOTE 1)
M
The IOPS MC service ID associated to the active subscription for which connectivity information is being notified
Connectivity information
(see NOTE 1)
M
It provides connectivity information about the MC service ID of the corresponding subscription. It includes the MC service UE's IP address of the associated IOPS MC service ID in the system and its connectivity status on the system (see NOTE 2)
NOTE 1: It can be a list associated to multiple active subscriptions.
NOTE 2: Whether the IOPS MC connectivity function provides within the IP connectivity notify request the actual MC service UE's IP address or an associated application IP address assigned by the IOPS MC connectivity function is implementation specific. For the latter, it is up to the IOPS MC connectivity function to correctly maintain the defined association.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.4 IP connectivity notify response
|
Table 10.3.2.4-1 describes the information flow for the IP connectivity notify response from the IOPS connectivity client to the IOPS MC connectivity function.
Table 10.3.2.4-1: IP connectivity notify response
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the responding MC user
IOPS MC service ID
(see NOTE)
M
The IOPS MC service ID for which connectivity information was received
NOTE: It can be a list associated to multiple active subscriptions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.5 IP connectivity group notify request
|
Table 10.3.2.5-1 describes the information flow for the IP connectivity group notify request from the IOPS MC connectivity function to the IOPS connectivity client.
Table 10.3.2.5-1: IP connectivity group notify request
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the MC user with active subscription(s)
IOPS group
(see NOTE)
M
The IOPS MC service group ID related to the active group subscription for which group connectivity information is being notified
Group connectivity information (see NOTE)
M
It indicates the number of other discovered MC users on the IOPS MC connectivity function of the corresponding group subscription
NOTE: It can be a list associated to multiple active group subscriptions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.2.6 IP connectivity group notify response
|
Table 10.3.2.6-1 describes the information flow for the IP connectivity group notify response from the IOPS connectivity client to the IOPS MC connectivity function.
Table 10.3.2.6-1: IP connectivity group notify response
Information element
Status
Description
IOPS MC service ID
M
The IOPS MC service ID of the responding MC user
IOPS group
(see NOTE)
M
The IOPS MC service group ID for which group connectivity information was received
NOTE: It can be a list associated to multiple active group subscriptions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.3.3 Procedures
|
The procedure for the IP connectivity subscription of MC users in the IOPS mode of operation is described in figure 10.3.3-1.
Pre-conditions:
- The MC service user has an active PDN connection or PDU session to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The MC service user is discovered by the IOPS MC connectivity function to support MC services based on the IP connectivity functionality.
- The MC service user has decided to subscribe to receive connectivity information of other discovered MC users and/or IOPS groups on the IOPS MC connectivity function.
Figure 10.3.3-1 IP connectivity subscription in the IOPS mode of operation
1. The IOPS connectivity client subscribes to receive connectivity information of other discovered MC users and/or groups on the IOPS MC connectivity function.
2. The IOPS MC connectivity function checks if a subscription for the MC service ID(s) and/or IOPS group(s) included in the request can be activated for the requesting MC user.
NOTE: A subscription cannot be activated if an MC user associated to the requested MC service ID has indicated in its IOPS discovery request that its connectivity information is not available to other users on the IOPS MC connectivity function. Besides, a subscription may not be activated if a requested IOPS group does not belong to the list of IOPS groups the requesting MC user has included in its IOPS discovery request.
3. The IOPS MC connectivity function indicates to the IOPS connectivity client the subscription status associated to the request.
The procedure for the IP connectivity notification of MC users in the IOPS mode of operation is described in figure 10.3.3-2.
Pre-conditions:
- The MC service user has an active PDN connection or PDU session to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The MC service user has an active IP connectivity subscription associated to one or multiple MC service IDs.
- The IOPS MC connectivity function has available information related to an IP connectivity subscription associated to one or multiple MC service IDs.
Figure 10.3.3-2 IP connectivity notification in the IOPS mode of operation
1. The IOPS MC connectivity function notifies to the IOPS connectivity client the connectivity information related to an active IP connectivity subscription associated to one or multiple MC service IDs. The connectivity information can be retrieved by the MC service client to establish an MC service communication based on the IP connectivity functionality.
2. The IOPS connectivity client provides an IP connectivity notify response to the IOPS MC connectivity function.
The procedure for the IP connectivity group notification of MC users in the IOPS mode of operation is described in figure 10.3.3-3.
Pre-conditions:
- The MC service user has an active PDN connection or PDU session to the IOPS MC connectivity function for the specific IP connectivity functionality procedure
- The MC service user has an active IP connectivity subscription associated to one or multiple IOPS MC service group IDs.
- The IOPS MC connectivity function has available information related to an IP connectivity subscription associated to one or multiple IOPS MC service group IDs.
Figure 10.3.3-3 IP connectivity group notification in the IOPS mode of operation
1. The IOPS MC connectivity function notifies to the IOPS connectivity client the group connectivity information related to an active IP connectivity group subscription associated to one or multiple IOPS MC service group IDs. The group connectivity information can be retrieved by the MC service client to establish an MC service group communication based on the IP connectivity functionality.
2. The IOPS connectivity client provides an IP connectivity group notify response to the IOPS MC connectivity function.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4 Use of broadcast/multicast transmissions
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.1 General
|
An IOPS MC connectivity function can provide support for group communications based on broadcast/multicast transmissions. Broadcast/multicast transmissions can be used for the downlink delivery of MC service application signalling and media to the MC service UEs over broadcast/multicast session (e.g., MBMS bearers in EPS, MBS session in 5GS).
The use of broadcast/multicast transmissions in the IOPS mode of operation are based on the related information flows and procedures specified in 3GPP TS 23.280 [3], 3GPP TS 23.379 [5], 3GPP TS 23.282 [6], and 3GPP TS 23.289 [12].
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.2 Information flows
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.2.1 MapIOPSGroupToNetworkSession (IP connectivity functionality)
|
Table 10.4.2.1-1 describes the information flow to associate a group session based on the IP connectivity functionality to a broadcast/multicast session. It is sent from the IOPS MC connectivity function to the MC service client.
Table 10.4.2.1-1: MapIOPSGroupToNetworkSession (IP connectivity functionality)
Information element
Status
Description
IOPS MC service group ID
M
This element identifies the IOPS MC service group, in which the group session is started.
Media stream identifier
M
This element identifies the media stream of the SDP used for the group session (e.g. MBMS subchannel).
Identifier of broadcast/multicast session
(see NOTE)
O
The identifier of the network broadcast/multicast session (e.g., TMGI) if the media of the group session is not sent on the same broadcast/multicast session as this MapIOPSGroupToNetworkSession message.
Session acknowledgement indicator
O
Indication that the group session requires acknowledgement from receiving MC service clients.
NOTE: “Identifier of broadcast/multicast session” IE shall be present if this message is sent over a different broadcast/multicast session than the media of the group session; This IE may be present if this message is sent over the same broadcast/multicast session as the media of the group session.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.2.2 UnmapIOPSGroupFromNetworkSession (IP connectivity functionality)
|
Table 10.4.2.2-1 describes the information flow to disconnect a group session based on the IP connectivity functionality from a broadcast/multicast session. It is sent from the IOPS MC connectivity function to the MC service client.
Table 10.4.2.2-1: UnmapIOPSGroupFromNetworkSession
Information element
Status
Description
IOPS MC service group ID
M
This element identifies the IOPS MC service group, in which the group session is started.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.3 Use of pre-established broadcast/multicast session
|
The MC services in the IOPS mode of operation shall support the procedure for using pre-established broadcast/multicast session as specified 3GPP TS 23.280 [3] or 3GPP TS 23.289 [12] with the following clarification:
- The MC service server is the IOPS MC connectivity function.
The MCPTT service shall use the MCPTT-IOPS-2, MCPTT-IOPS-4, and MC-IOPS-6 reference points for this procedure.
The MCData service shall use the MCData-IOPS-2, MCData-IOPS-4, and MC-IOPS-6 reference points for this procedure.
The IOPS MC system may use pre-established broadcast/multicast sessions for distributing the media associated to group sessions. Depending on the capacity of the broadcast/multicast session, the broadcast/multicast session can be used to broadcast one or more group sessions in parallel.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.4 Use of dynamic broadcast/multicast session establishment
|
The MC services in the IOPS mode of operation shall support the procedure for using dynamic broadcast/multicast session as specified 3GPP TS 23.280 [3] or 3GPP TS 23.289 [12] with the following clarification:
- The MC service server is the IOPS MC connectivity function.
The MCPTT service shall use the MCPTT-IOPS-2, MCPTT-IOPS-4, and MC-IOPS-6 reference points for this procedure.
The MCData service shall use the MCData-IOPS-2, MCData-IOPS-4, and MC-IOPS-6 reference points for this procedure.
The IOPS MC system may use dynamic MBMS bearer establishment for distributing the media associated to group sessions.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.5 Group session connect and disconnect over broadcast/multicast session (IP connectivity functionality)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.5.1 General
|
MBMS bearers can be used for group sessions based on the IP connectivity functionality. One broadcast/multicast session can be associated to one or more specific groups or group sessions. Before sending packets related to a group session, i.e. signalling and media, over a broadcast/multicast session, the IOPS MC connectivity function transmits the association information between the group session and the broadcast/multicast session. When the group session over the broadcast/multicast session is finished, this temporary association information of a group session to specific resources on a broadcast/multicast session is undone. Prior to the association of a group session to a broadcast/multicast session the broadcast/multicast session is activated and announced to the MC service clients.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.5.2 Procedure
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.5.2.1 Group Session connect over broadcast/multicast session
|
In figure 10.4.5.2.1-1 the MC service client 1 is the client that initiates a group session, e.g. an MCPTT client initiating a group call. The MC service client 1 may be within the broadcast/multicast service area. The MC service clients 2 … n represent MC service clients, e.g. MCPTT clients, receiving the group session packets over an MBMS bearer. There may be other receiving MC service clients both over unicast bearers and over this or other broadcast/multicast session(s), however, they are not illustrated in this figure.
Pre-conditions:
- The MC service user profile used for the IOPS mode of operation is pre-provisioned in the MC service UEs
- The IOPS MC service group ID and its associated IOPS group IP multicast address are pre-configured in the MC service clients
- The MC service users have an active PDN connection to the IOPS MC connectivity function for the communication based on the IP connectivity functionality
- The MC service users are discovered by the IOPS MC connectivity function to support MC services based on the IP connectivity functionality
Figure 10.4.5.2.1-1: Group session connect on broadcast/multicast session (IP connectivity functionality)
1. Activation and announcement of broadcast/multicast session availability.
2. MC user at the MC service client 1 wants to initiate an MC service group session with a specific IOPS MC service group based on the IP connectivity functionality.
3. The MC service client 1 transmits the related group session packets via the IOPS MC connectivity function targeting the IOPS MC service group (i.e. using the corresponding IOPS group IP multicast address)
4. The IOPS MC connectivity function determines that the received packets correspond to a group session. Therefore, the IOPS MC connectivity function transmits a MapIOPSGroupToNetwork message over a previously established broadcast/multicast session to all users monitoring the broadcast/multicast session. The MapIOPSGroupToNetwork message includes association information between the group session and the broadcast/multicast session. It includes the corresponding IOPS MC service group ID associated to the IOPS group IP multicast address related to the group session.
5. The IOPS MC connectivity function distributes the received group session packets from the MC service client 1 to other MC service clients (e.g. MC service clients 2 … n) over the broadcast/multicast session.
NOTE: MC service clients receiving the group session packets over the broadcast/multicast session only decode the packets that are addressed to their pre-configured IOPS group IP multicast address(es). Otherwise, the MC service clients discard the packets.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.4.5.2.2 Group session disconnect over broadcast/multicast session
|
Figure 10.4.5.2.2-1 shows the high-level procedure where an UnmapIOPSGroupFromNetworkSession message is transmitted from the IOPS MC connectivity function to MC service clients to indicate that a group session is being disconnected or dissociated from the broadcast/multicast session.
Figure 10.4.5.2.2-1: Group session disconnect on broadcast/multicast session (IP connectivity functionality)
1. A group session based on the IP connectivity functionality is ongoing; the group session packets received from the MC service client 1 are distributed over broadcast/multicast session to other MC service clients within the system.
2. The IOPS MC connectivity function has determined to disconnect the group session from the broadcast/multicast session for the MC service clients within the system.
NOTE: The IOPS MC connectivity function may decide to disconnect a group session from a broadcast/multicast session if group session packets are not anymore received addressing the corresponding IOPS MC service group (or IOPS group IP multicast address).
3. An UnmapGroupFromBearer message is transmitted from the IOPS MC connectivity function to the MC service clients and possibly to the MC service client 1 (if it is within the broadcast/multicast coverage area) on broadcast/multicast session(s).
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.5 MCPTT service
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.5.1 IOPS group call (IP connectivity functionality)
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.5.1.1 General
|
The support of MCPTT group calls based on the IP connectivity functionality in the IOPS mode of operation enables that the service is provided by the MCPTT clients over the IOPS MC connectivity function. The IOPS MC connectivity function provides IP connectivity for the communication among MCPTT users.
IOPS group calls based on the IP connectivity functionality can use pre-configured information provided to MCPTT clients prior to the IOPS group call. Therefore, when a MCPTT client initiates an IOPS group call it uses the pre-configured IOPS group IP multicast address associated to the target IOPS MCPTT group ID to establish the IOPS group call based on the IP connectivity functionality. The related packets, i.e. signalling and media, of the IOPS group call are transmitted to the IOPS MC connectivity function for distribution to the corresponding discovered MC users of the target IOPS MCPTT group.
The IOPS MC connectivity function can distribute the group session packets to the discovered MC users over MBMS bearers as described in clause 10.4.5.
The IOPS MC connectivity function can also replicate and distribute the group session packets over unicast transmissions to MCPTT UEs associated to the target IOPS MCPTT group. MCPTT UEs receiving the group session packets are associated to discovered MC users that included the target IOPS MCPTT group ID in the IOPS discovery request, as described in clause 10.5.2.3.
The following clauses specify the IOPS group call procedures and information flows for the IP connectivity functionality in the IOPS mode of operation.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
10.5.1.2 Information flows
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.