hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c2b51129ee43b3e90986e5a93c752d52 | 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 figu... |
c2b51129ee43b3e90986e5a93c752d52 | 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 fi... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.4 Functional entities description
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.4.1 Application plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 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 Applica... |
c2b51129ee43b3e90986e5a93c752d52 | 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 provid... |
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.4.2 Signalling control plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.5 Reference points
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.5.1 Application plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 transp... |
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 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.... |
c2b51129ee43b3e90986e5a93c752d52 | 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].... |
c2b51129ee43b3e90986e5a93c752d52 | 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 [1... |
c2b51129ee43b3e90986e5a93c752d52 | 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]... |
c2b51129ee43b3e90986e5a93c752d52 | 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 [... |
c2b51129ee43b3e90986e5a93c752d52 | 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 a... |
c2b51129ee43b3e90986e5a93c752d52 | 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 t... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 7.5.2 Signalling control plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 di... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 8 Identities
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 8.1 Application plane
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 8.1.1 IOPS MC user identity (IOPS MC ID)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 as defined in 3GPP 33.180 [16] clause 5.1.3.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 8.1.2 IOPS MC service user identity (IOPS MC service ID)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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].
N... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 8.1.3 IOPS MC service group identity (IOPS MC service group ID)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 M... |
c2b51129ee43b3e90986e5a93c752d52 | 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 IO... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 9 Application of functional model to deployments
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 mod... |
c2b51129ee43b3e90986e5a93c752d52 | 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
|
c2b51129ee43b3e90986e5a93c752d52 | 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.... |
c2b51129ee43b3e90986e5a93c752d52 | 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: Fo... |
c2b51129ee43b3e90986e5a93c752d52 | 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;
-... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 9.2.4 UE 2
| The UE 2 represents one or more UEs with the same functionality as UE 1.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10 Procedures and information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.1 User authentication in the IOPS mode of operation
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 as defined in 3GPP 33.180 [16] clause 5.1.3.
|
c2b51129ee43b3e90986e5a93c752d52 | 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.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.2 IOPS discovery (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 procedur... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.2.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 th... |
c2b51129ee43b3e90986e5a93c752d52 | 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 ... |
c2b51129ee43b3e90986e5a93c752d52 | 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 connecti... |
c2b51129ee43b3e90986e5a93c752d52 | 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 discove... |
c2b51129ee43b3e90986e5a93c752d52 | 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 functi... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.3 IOPS subscription and notification (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 ... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.3.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 requestin... |
c2b51129ee43b3e90986e5a93c752d52 | 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 request... |
c2b51129ee43b3e90986e5a93c752d52 | 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 ac... |
c2b51129ee43b3e90986e5a93c752d52 | 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... |
c2b51129ee43b3e90986e5a93c752d52 | 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 ... |
c2b51129ee43b3e90986e5a93c752d52 | 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 r... |
c2b51129ee43b3e90986e5a93c752d52 | 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 servic... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.4 Use of broadcast/multicast transmissions
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 E... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.4.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 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)
Informa... |
c2b51129ee43b3e90986e5a93c752d52 | 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
Descr... |
c2b51129ee43b3e90986e5a93c752d52 | 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-I... |
c2b51129ee43b3e90986e5a93c752d52 | 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, M... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.4.5 Group session connect and disconnect over broadcast/multicast session (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 connec... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.4.5.2 Procedure
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 sessio... |
c2b51129ee43b3e90986e5a93c752d52 | 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 sessi... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5 MCPTT service
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1 IOPS group call (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 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 call... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.2.1 IOPS group call announcement
| Table 10.5.1.2.1-1 describes the information flow for the IOPS group call announcement from one MCPTT client to other MCPTT clients. The packet(s) carrying the IOPS group call announcement are transmitted from the originating MCPTT client to the IOPS MC connectivity function for distribution to the target MCPTT clients... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.2.2 IOPS group call response
| Table 10.5.1.2.2-1 describes the information flow for the IOPS group call response from one MCPTT client to other MCPTT clients. The packet(s) carrying the IOPS group call response is transmitted from the called MCPTT client to the IOPS MC connectivity function for distribution to the target MCPTT clients.
Table 10.5.... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.2.3 IOPS emergency group call upgrade
| Table 10.5.1.2.3-1 describes the information flow for the IOPS emergency group call upgrade from one MCPTT client to other MCPTT clients. The packet(s) carrying the IOPS emergency group call upgrade are transmitted from the originating MCPTT client to the IOPS MC connectivity function for distribution to the target MCP... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.2.4 IOPS emergency group call state cancel
| Table 10.5.1.2.4-1 describes the information flow for the IOPS emergency group call state cancel from one MCPTT client to other MCPTT clients. The packet(s) carrying the IOPS emergency group call state cancel are transmitted from the originating MCPTT client to the IOPS MC connectivity function for distribution to the ... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.3 IOPS group call setup
| The procedure in figure 10.5.1.3-1 illustrates the procedure for an IOPS MCPTT group call establishment based on the IP connectivity functionality. The procedure describes how an MCPTT client initiates and establishes an IOPS MCPTT group call with other MCPTT clients.
Pre-conditions:
- MCPTT user profile used for the... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.4 IOPS emergency group call
| The procedure in figure 10.5.1.4-1 illustrates the procedure for an IOPS MCPTT emergency group call establishment based on the IP connectivity functionality. The IOPS emergency group call is a special case of the IOPS group call setup procedure described in clause 10.5.1.3, wherein the IOPS group call announcement cont... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.1.5 IOPS group call release
| Each MCPTT client may release itself from an ongoing IOPS group call without the transmission of any signalling if the call has been inactive for a specific duration.
NOTE: Inactivity time can be set according to the policy of the MCPTT service provider.
|
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2 IOPS private call (IP connectivity functionality)
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.1 General
| The support of MCPTT private 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.
When an MCPTT... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2 Information flows
| |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.1 IOPS call setup request
| Table 10.5.2.2.1-1 describes the information flow for the IOPS call setup request from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS call setup request are transmitted from the calling MCPTT client to the IOPS MC connectivity function for distribution to the called MCPTT client.
Table 10.5.... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.2 IOPS call setup response
| Table 10.5.2.2.2-1 describes the information flow for the IOPS call setup response from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS call setup response are transmitted from the called MCPTT client to the IOPS MC connectivity function for distribution to the calling MCPTT client.
Table 10.... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.3 IOPS MCPTT ringing
| Table 10.5.2.2.3-1 describes the information flow for the IOPS MCPTT ringing from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS MCPTT ringing are transmitted from the called MCPTT client to the IOPS MC connectivity function for distribution to the calling MCPTT client.
Table 10.5.2.2.3-1: I... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.4 IOPS call release request
| Table 10.5.2.2.4-1 describes the information flow for the IOPS call release request from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS call release request are transmitted from one MCPTT client to the IOPS MC connectivity function for distribution to the other MCPTT client.
Table 10.5.2.2.4... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.5 IOPS call release response
| Table 10.5.2.2.5-1 describes the information flow for the IOPS call release response from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS call release response are transmitted from one MCPTT client to the IOPS MC connectivity function for distribution to the other MCPTT client.
Table 10.5.2.2... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.2.6 IOPS emergency private call upgrade
| Table 10.5.2.2.6-1 describes the information flow for the IOPS emergency private call upgrade from one MCPTT client to another MCPTT client. The packet(s) carrying the IOPS emergency private call upgrade are transmitted from the originating MCPTT client to the IOPS MC connectivity function for distribution to the targe... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.3 IOPS private call setup in automatic commencement mode procedure
| The procedure in figure 10.5.2.3-1 is the basic procedure for an MCPTT client initiating the establishment of an IOPS MCPTT private call with a target MCPTT client based on the IP connectivity functionality.
The procedure focuses on the case of an IOPS MCPTT private call using an automatic commencement mode.
Pre-cond... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.4 IOPS private call setup in manual commencement mode procedure
| The procedure in figure 10.5.2.4-1 focuses on the case where an MCPTT user is initiating an IOPS MCPTT private call for communicating with another MCPTT user using a manual commencement mode. The IOPS MCPTT private call is based on the IP connectivity functionality.
Pre-conditions:
- MCPTT user profile used for the I... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.5 IOPS private call release
| The procedure in figure 10.5.2.5-1 focuses on the case where an MCPTT client is requesting to release an ongoing IOPS MCPTT private call based on the IP connectivity functionality. Either MCPTT client can initiate the call release procedure.
Pre-conditions:
- Two MCPTT users are currently engaged in an IOPS MCPTT pri... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.2.6 IOPS emergency private call
| The procedure in figure 10.5.2.6-1 is the basic procedure for an MCPTT client initiating the establishment of an IOPS emergency private call with a target MCPTT client based on the IP connectivity functionality. The IOPS emergency private call is a special case of the IOPS private call setup procedures described in cla... |
c2b51129ee43b3e90986e5a93c752d52 | 23.180 | 10.5.3 IOPS floor control (IP connectivity functionality)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.