hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.3 AMF services
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.3.1 General
|
AMF supports to expose AIoT services towards the AIOTF as described in Table 7.3.1-1. The Namf_AIoT AMF service is used when NG-RAN and the AIoTF communicate indirectly via an AMF.
Table 7.3.1-1: NF services provided by the AMF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Namf_AIoT
MessageDelivery
Request/Response
AIOTF
Notify
Subscribe/Notify
AIOTF
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.3.2 Namf_AIoT_MessageDelivery service operation
|
Service operation name: Namf_AIoT_MessageDelivery
Description: The NF consumer requests to send AIoT data (i.e. AIoT inventory/command messages) towards NG-RAN or AIoT devices.
Inputs, Required:
1) AIoT messages to deliver to NG-RAN.
2) NG-RAN ID.
Outputs, Required: AIoT messages received from NG-RAN, Result indication (Success or Failure), Failure Cause in case of Failure.
Editor’s note: It is FFS whether the Correlation identifier or AIOTF ID is included in the Namf_AIoT_MessageDelivery.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.3.3 Namf_AIoT_Notify service operation
|
Service operation name: Namf_AIoT_Notify
Description: The NF consumer requests to receive AIoT data from NG-RAN or AIoT devices. If the NF consumer invokes the Namf_AIoT_MessageDelivery, the NF consumer implicitly subscribes to receive the AIoT data from NG-RAN or AIoT devices.
Inputs, Required:
1) AIoT messages received from NG-RAN.
Input, Optional: None.
Outputs, Required: Operation execution result indication.
Output, Optional: None.
Editor's note: AIoT messages is FFS and coordination with RAN3 is needed.
Editor's note: It is FFS how to make AIOT be aware of the report is finished in case there are multiple notify for the same operation.
Editor's note: It is FFS whether the Correlation identifier is included in the Namf_AIoT_Notify.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.4 NEF services
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.4.1 General
|
In addition to those defined in clause 7.2.8 of TS 23.501 [3] and clause 5.2.6 of TS 23.502 [4], table 7.4.1-1 illustrates additional NEF services to support AIoT.
Table 7.4.1-1: NF Services provided by NEF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnef_AIoT
Inventory
Request/Response
AF
Command
Request/Response
AF
Notify
Subscribe/Notify
AF
Editor’s note: It is FFS whether to use separate service operation to respectively support read, write or disable command procedure.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.4.2 Nnef_AIoT_Inventory service operation
|
Service operation name: Nnef_AIoT_Inventory
Description: The consumer requests to perform an inventory operation for an AIoT Device or multiple AIoT Devices.
Input, Required: AF ID, Target area information or AIoT Device ID(s) or AIoT Device ID filter information for the inventory operation.
Input, Optional: Approximate number of AIoT Devices.
Output, Required: AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional: None.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.4.3 Nnef_AIoT_Command service operation
|
Service operation name: Nnef_AIoT_Command
Description: The consumer requests to perform a command operation for an AIoT Device or multiple AIoT Devices.
Input, Required: AF ID, Target area information or AIoT Device ID(s) or AIoT Device ID filter information for the command operation, Command type (Read, Write, or Disable).
Editor’s note: The AIoT Data specific for the Read/Write/Disable command is FFS.
Input, Optional: Approximate number of AIoT Devices, Approximate message size from the AIoT Device for Read command type.
Editor’s note: It is FFS whether the Approximate message size from the AIoT Device can also apply for the other command types.
Output, Required: AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional: None.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.4.4 Nnef_AIoT_Notify service operation
|
Service operation name: Nnef_AIoT_Notify
Description: The consumer receives notification of the status or results of the requested service operation. If the consumer invokes the Nnef_AIoT_Inventory, or Nnef_AIoT_Command service operation, the consumer implicitly subscribes to the results of the requested service operation.
Input, Required: AF Transaction ID, a list of AIoT Device ID(s) or Failure Cause in case of Failure, Information obtained from each target AIoT Device.
Input, Optional: None.
Output, Required: Result indication.
Output, Optional: None.
Editor’s note: The NEF AIoT service operation definition needs to be revisited to align with AIOTF services.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.5 ADM services
| |
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.5.1 General
|
The following table shows the Nadm_DM Service and Service Operations.
Table 7.5.1-1: NF services provided by ADM
NF service name
Service Operations
Operation Semantics
Example Consumer(s)
Nadm_DM
Query
Request/Response
AIOTF, NEF
Update
Request/Response
AIOTF
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.5.2 Nadm_DM_Query service operation
|
Service operation name: Nadm_DM_Query
Description: NF service consumer may request the AIoT device profile data or the AF authorization data from the ADM.
Inputs, Required: AIoT Device Permanent ID, or AF ID.
Input, Optional: None.
Outputs, Required: the AIoT device profile data or the AF authorization data.
Output, Optional: None.
Editor's note: Whether AF authorization data is stored in ADM is FFS.
|
9852d074e0fb77fb47b7198efe6957c3
|
23.369
|
7.5.3 Nadm_DM_Update service operation
|
Service operation name: Nadm_DM_Update Description: NF service consumer may update the AIoT device profile data in the ADM. Inputs, Required: AIoT Device Permanent ID, updated AIoT device profile data. Input, Optional: None. Outputs, Required: Result indication (Success or Failure), Failure Cause in case of Failure. Output, Optional: None. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2025-01 SA2#166 AH-e S2-2501256 - - - Proposed skeleton agreed at SA2#166AH-e 0.0.0 2025-01 SA2#166 AH-e - - - - Inclusion of documents approved in SA2#166AH-e: S2-2501253, S2-2501254, S2-2501255, S2-2501257, S2-2501258. 0.1.0 2025-02 SA2#167 - - - - Inclusion of documents approved in SA2#167: S2-2502368, S2-2502555, S2-2502564, S2-2502578, S2-2502579, S2-2502581, S2-2502582, S2-2502585, S2-2502586, S2-2502588, S2-2502589, S2-2502590 0.2.0 2025-04 SA2#168 - - - - Inclusion of documents approved in SA2#168: S2-2504012, S2-2504013, S2-2504063, S2-2504275, S2-2504280, S2-2504281, S2-2504283, S2-2504286, S2-2504287, S2-2504289, S2-2504290, S2-2504291, S2-2504292, S2-2504318, S2-2504319, S2-2504320, S2-2504321 0.3.0
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
1 Scope
|
This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service. The MCPTT service utilizes the common functional architecture to support MC services over LTE including the common services core defined in 3GPP TS 23.280 [16].Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.179 [2] and 3GPP TS 22.280 [17].
The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [8]. Certain application functions of the MCPTT service such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats.
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.179: "Mission Critical Push to Talk (MCPTT)"; Stage 1.
[3] 3GPP TS 23.002: "Network Architecture".
[4] 3GPP TS 23.203: "Policy and charging control architecture".
[5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[6] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; 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] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[11] Void
[12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[13] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[14] void
[15] void
[16] 3GPP TS 23.280: "Common functional architecture to support mission critical services".
[17] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1".
[18] 3GPP TS 29.283: "Diameter data management applications".
[19] 3GPP TS 33.180: "Security of the mission critical service".
[20] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
3 Definitions, symbols and abbreviations
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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].
Automatic commencement mode: A mode in which the initiation of the private call does not require any action on the part of the receiving MCPTT user.
First-to-answer call: A call that is started when the first MCPTT user among multiple potential target recipients' answers. This call requires the answering MCPTT user to answer manually; automatic answer is not allowed
Group call: A mechanism by which an MCPTT user can make a one-to-many MCPTT transmission to other users that are members of MCPTT group(s).
Group home MCPTT system: The MCPTT system where the MCPTT group is defined.
Group host MCPTT server: The MCPTT server within an MCPTT system that provides centralised support for MCPTT services of an MCPTT group defined in a group home MCPTT system.
Manual commencement mode: A mode in which the initiation of the private call requires the receiving MCPTT user to perform some action to accept or reject the call setup.
MCPTT client: An instance of an MC service client that provides the client application function for the MCPTT service.
MCPTT group: An MC service group configured for MCPTT service.
MCPTT group affiliation: An MC service group affiliation for MCPTT.
MCPTT group de-affiliation: An MC service group de-affiliation for MCPTT.
MCPTT ID: An instance of an MC service ID within the MCPTT service.
MCPTT server: An instance of an MC service server that provides the server application function for the MCPTT service.
On-network MCPTT service: The collection of functions and capabilities required to provide MCPTT via EPS bearers using E-UTRAN to provide the last hop radio bearers.
Preconfigured MCPTT group: an MCPTT group used only for regrouping that has been configured in advance of a group or user regrouping operation to serve as the source of regroup group configuration.
Pre-selected MCPTT user profile: An instance of the pre-selected MC service user profile for MCPTT.
UE-to-network relay MCPTT service: The collection of functions and capabilities required to provide MCPTT via a ProSe UE-to-network relay using ProSe direct communication paths to provide the last hop radio bearer(s).
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 [2] apply:
Dispatcher
Floor control
Group-broadcast group
MCPTT administrator
MCPTT service
MCPTT system
MCPTT UE
MCPTT user
MCPTT User Profile
Mission Critical Organization
Mission Critical Push To Talk
Off-network MCPTT service
Partner MCPTT system
Primary MCPTT system
Private call
Multi-talker control
User-broadcast group
For the purposes of the present document, the following terms and definitions given in IETF RFC 5245 [13] apply:
Candidate
Candidate pair
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [16] apply:
Ad hoc Group Communication
Active MC service user profile
Chat group
MC service client
MC service group
MC service group affiliation
MC service group de-affiliation
MC service ID
MC service server
Pre-arranged group
Pre‑selected MC service user profile
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [17] apply:
Functional alias
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
3.2 Symbols
|
For the purposes of the present document, the following symbols given in 3GPP TS 22.179 [2] apply:
B1
B2
N2
N3
N4
N5
N6
N7
N10
N11
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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].
APN Access Point Name
ARP Allocation and Retention Priority
BM-SC Broadcast Multicast Service Centre
CHAP Challenge-Handshake Authentication Protocol
CSCF Call Server Control Function
DL Downlink
DPF Direct Provisioning Function
E-UTRAN Evolved Universal Terrestrial Radio Access Network
E2EE End to End Encryption
ECGI E-UTRAN Cell Global Identifier
EPC Evolved Packet Core
EPS Evolved Packet System
GBR Guaranteed Bit Rate
GCS AS Group Communication Service Application Server
GCSE_LTE Group Communication Service Enabler over LTE
GRUU Globally Routable User agent URI
HLR Home Location Register
HSS Home Subscriber Server
HTTP Hyper Text Transfer Protocol
I-CSCF Interrogating CSCF
ICE Interactive Connectivity Establishment
IM CN IP Multimedia Core Network
IMPI IP Multimedia Private Identity
IMPU IP Multimedia PUblic identity
IMS IP Multimedia Subsystem
ITSI Individual TETRA Subscriber Identity
LMR Land Mobile Radio
MBMS Multimedia Broadcast and Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MC Mission Critical
MC ID Mission Critical user identity
MCPTT Mission Critical Push To Talk
MCPTT AS MCPTT Application Server
MCPTT group ID MCPTT group identity
MCPTT ID MCPTT user identity
NAT Network Address Translation
PAP Password Authentication Protocol
P-CSCF Proxy CSCF
PCC Policy and Charging Control
PCRF Policy and Charging Rules Function
PLMN Public Land Mobile Network
ProSe Proximity-based Services
PSI Public Service Identity
PTT Push To Talk
QCI QoS Class Identifier
QoS Quality of Service
RAN Radio Access Network
RF Radio Frequency
RSI Radio Set Identity
S-CSCF Serving CSCF
SAI Service Area Identifier
SDF Service Data Flow
SIP Session Initiated Protocol
SSL Secure Sockets Layer
TLS Transport Layer Security
TMGI Temporary Mobile Group Identity
UM Unacknowledged Mode
URI Uniform Resource Identifier
USB Universal Serial Bus
WLAN Wireless Local Area Network
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
4 Introduction
|
The MCPTT service supports communication between several users (i.e. group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users.
The MCPTT architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [16] and aspects of the IMS architecture defined in 3GPP TS 23.228 [5], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in 3GPP TS 23.468 [9] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [6] to enable support of the MCPTT service.
The MCPTT UE primarily obtains access to the MCPTT service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [8]. Certain application functions of MCPTT service such as dispatch and administrative functions can be supported using either MCPTT UEs in E-UTRAN or using MCPTT UEs via non-3GPP access networks.
NOTE: Dispatch consoles and devices used by MCPTT service administrators are considered MCPTT UEs in the MCPTT architecture.
MCPTT UEs that use non-3GPP access can only support a subset of the functionality specified in this specification that is supported by the non-3GPP access network.
The MCPTT system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [20].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5 Architectural requirements
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.1 Media routing requirements
|
The voice media flow for a private call shall be routed according to one of the following two options:
a) Option 1:
1) Through the primary MCPTT system if both users in the call belong to the same organisation; or
2) Through the primary MCPTT system of both users, if the users in the call do not belong to the same organisation.
b) Option 2: The voice media flow may be routed locally, under the control of the primary MCPTT system, through an entity allowing the duplication of the media flow to the primary MCPTT system of each user.
The voice media flow for a group call shall be routed to the group home MCPTT system.
The routing of media flow shall be end-to-end from transmitter to receiver(s), except for the MCPTT control function.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.2 Requirements for user identity management
|
To allow for confidentiality of user identities in various cases of business relationship as defined in clause 6, the MCPTT application may provide public user identities to the MCPTT UE, to be used by MCPTT UE for MCPTT services.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.3 MCPTT group affiliation and MCPTT group de-affiliation
|
MCPTT group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [16]. In addition, the following requirements shall be fulfilled by the MCPTT service for MCPTT users affiliated to MCPTT groups:
- MCPTT users receive notifications for MCPTT group call setup and invitations for their affiliated MCPTT group(s).
- MCPTT users receive media and events from their affiliated MCPTT group(s).
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.4 MCPTT call requirements
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.4.1 General
|
The on-network MCPTT service shall support the use of pre-established sessions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.4.2 Group call requirements
|
The MCPTT service shall support the chat group (restricted) call model for MCPTT group call.
The MCPTT service shall support the pre-arranged group call model for MCPTT group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.5 GCS AS requirements for the MCPTT service
|
The GCS AS architecture requirements for MC services are specified in 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.6 Group selection
|
The following functionalities shall be supported by the MCPTT service.
a. The MCPTT user shall select an affiliated group to initiate a new group call or transmit media in an existing group call.
b. An authorized MCPTT user (e.g., dispatcher) may remotely force or request to change other on-network MCPTT users' selected MCPTT group to a particular affiliated group.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7 Bearer management
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.1 General
|
The MCPTT UE shall use the APNs as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.2 EPS bearer considerations
|
The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [16] shall apply.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.2.1 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.2.2 Void
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.3 EPS unicast bearer considerations for MCPTT
|
For an MCPTT call session request, resources shall be requested utilising interaction with dynamic PCC. The MCPTT system shall request resources over Rx to a PCRF. The dedicated bearer for voice shall utilise the QCI value of 65 (as specified in 3GPP TS 23.203 [4]) and the bearer for MCPTT-4 reference point messaging shall utilise the QCI value of 65 or the QCI value of 69 (as specified in 3GPP TS 23.203 [4]). The request of resources over Rx shall include an application identifier for MCPTT in order for the PCRF to evaluate the correct QCI.
The UE is required to support at minimum one UM bearer which is used for MCPTT voice (see annex A in 3GPP TS 36.331 [12]).
Depending on operator policy:
- the MCPTT 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; or
- the EPS bearers for MCPTT call may enable pre-emption of lower priority EPS bearers if the maximum number of UM bearers has been reached in favour of MCPTT initiated EPS bearer, if the EPS bearer used for MCPTT call has higher priority level (ARP) than the UM bearer(s) used for other application(s) and if the bearers for non MCPTT application are pre-emptable. In this case, the EPS bearer for MCPTT call pre-empts one of the existing EPS bearers when the maximum number of bearers is established for other applications.
NOTE 1: Operator policy takes into account regional/national requirements.
The EPS bearer for MCPTT emergency call shall have highest priority level among MCPTT call types. The EPS bearer for MCPTT imminent peril call shall have higher priority level than one for MCPTT call.
To ensure that the MCPTT service always has access to a dedicated bearer for MCPTT media, a pre-established session may be setup that includes a request for resources at the first MCPTT group affiliation.
This means that the PCC may multiplex MCPTT media streams from multiple concurrent MCPTT calls into one EPS bearer on one shared network priority regardless of MCPTT call priority.
NOTE 2: A single UM bearer is used to multiplex the media streams from multiple concurrent MCPTT calls.
NOTE 3: The sharing of a single GBR bearer for voice means that different QCI and/or ARP values are not possible for different voice media streams.
NOTE 4: Multi-talker control may require additional bearer resources if multiple audio streams are sent to the UE when the floor is granted to additional participants during an established MCPTT group session.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.7.4 MBMS bearer management
|
The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
5.8 MCPTT system interconnect requirements
|
The architecture for interconnect between MCPTT systems is specified, allowing the affiliation of MCPTT users from an MCPTT system with MCPTT groups defined in another MCPTT system. When both MCPTT systems are served by different networks, interconnect of signalling and media is achieved using the interfaces defined for interconnect between PLMNs.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
6 Involved business relationships
|
The description of the involved business relationships for the MCPTT service is contained in clause 6 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7 Functional model
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.1 General
|
The functional model for the support of MCPTT is defined as a series of planes to allow for the breakdown of the architectural description.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.2 Description of the planes
|
The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.3 Functional model description
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.3.1 On-network functional model
|
Figure 7.3.1-1 shows the functional model for the application plane of the MCPTT service.
Figure 7.3.1-1: Functional model for application plane of the MCPTT service
In the model shown in figure 7.3.1-1, the following apply:
- The MCPTT server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [16].
- The MCPTT server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [9].
- MCPTT-9 carries multicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE.
- MCPTT-4 carries unicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE.
- MCPTT-7 carries unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT UE.
- MCPTT-8 carries multicast media from the media distribution function of the MCPTT server to the media mixer of the MCPTT UE.
Figure 7.3.1-2 shows the relationships between the reference points of the application plane and the signalling plane.
Figure 7.3.1-2: Relationships between reference points of MCPTT application and signalling control planes
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.3.2 Off-network functional model
|
Figure 7.3.2-1 shows the functional model for off-network operation of MCPTT service.
Figure 7.3.2-1: Functional model for off-network operation of MCPTT service
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4 Functional entities description
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.1 General
|
Each subclause is a description of a functional entity and does not imply a physical entity.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2 Application plane of MCPTT service
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.1 General
|
Entities within the application plane of MCPTT service provide application control, media control and distribution functions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.2 Common services core
|
The description of the common services core entities are contained in common functional architecture to support MC services in 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3 MCPTT application service
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.1 MCPTT client
|
The MCPTT client functional entity acts as the user agent for all MCPTT application transactions. The client reports the information of where the client is currently located.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.2 MCPTT server
|
The MCPTT server functional entity provides centralised support for MCPTT services.
All the MCPTT clients supporting users belonging to a single group are required to use the same MCPTT server for that group. An MCPTT client supporting a user involved in multiple groups can have relationships with multiple MCPTT servers.
NOTE 1: Possible requirements for handling multiple distinct media on different MCPTT servers are not covered in this version of the document.
The MCPTT 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 MCPTT server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.
By assuming the role of a GCS AS, the MCPTT server functional entity is responsible for:
- requesting the allocation of multicast resources utilizing the media distribution function;
- announcing the association of multicast resources to calls to MCPTT UEs;
- determining for each MCPTT UE involved in a given call whether to use unicast or multicast transport;
- announcing the assignment of multicast transport for specific calls to MCPTT UEs; and
- informing the media distribution function of the media streams requiring support for a given call.
The MCPTT server shall support the controlling role and the participating role. The MCPTT server may perform the controlling role for private calls and group calls. The MCPTT server performing the controlling role for a private call or group call may also perform a participating role for the same private call or group call. For each private call and group call, there shall be only one MCPTT server assuming the controlling role, while one or more MCPTT servers in participating role may be involved.
The MCPTT server performing the controlling roles is responsible for:
- call control (e.g. policy enforcement for participation in the MCPTT group calls) towards all the MCPTT users of the group call and private call;
- interfacing with the group management server for group policy and affiliation status information of this MCPTT server's served affiliated users;
- enforcing functional alias priority handling;
- managing floor control entity in a group call and private call; and
- managing media handling entity in call i.e. conferencing, transcoding.
The MCPTT server performing the functional alias controlling role is responsible for:
- interfacing with the functional alias management server for functional alias policy from the functional alias configuration;
- functional alias activation, deactivation, take over and interrogation support for MCPTT user.
The controlling roles for group call, private call and functional alias are independent with each other.
The MCPTT server performing the participating roles is responsible for:
- call control (e.g. authorization for participation in the MCPTT group calls) to its MCPTT users for group call and private call;
- group affiliation support for MCPTT user, including enforcement of maximum N2 number of simultaneous group affiliations by a user;
- enforcing functional alias priority handling;
- relaying the call control and floor control messages between the MCPTT client and the MCPTT server performing the controlling role; and
- media handling in call for its MCPTT users, i.e. transcoding, recording, lawful interception for both unicast and multicast media.
NOTE 2: The MCPTT server in the controlling role and the MCPTT server in the participating role can belong to the same MCPTT system or to different MCPTT systems.
For group regrouping involving multiple groups from primary and partner MCPTT systems,
- the group host MCPTT server of the temporary group performs the controlling role and is responsible for the centralized floor control, and for arbitration according to the temporary group or user policies (e.g., priority);
- the group host MCPTT server of the constituent MCPTT group is responsible for providing call invitations to their group members, and for filtering between constituent group members' floor control requests according to the constituent group or user policies (e.g., priority); and
- the MCPTT server responsible for the constituent MCPTT group members performs the participating role.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.3 Floor participant
|
The floor participant functional entity is responsible for floor requests. This functional entity is located in the UE for both on-network and off-network operations.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.4 Floor control server
|
This functional entity provides support for centralised floor control for on-network and distributed floor control for off-network operation. It may provide arbitration between floor control requests between different users, grant the floor in response to successful requests, and provide queuing in cases of contention. For on-network operation, this functional entity is located with the MCPTT server, however, the floor control server may use different IP addresses. For off-network operation, this functional entity is located in the UE.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.5 Media distribution function
|
The media distribution function is responsible for the distribution of media to call participants. The media distribution function may use different IP addresses than the MCPTT server. By means of information provided by the MCPTT server (e.g. IP addresses, transport layer ports), it will provide the following functionality:
- provide for the reception of uplink MCPTT UE media transmission by means of the MCPTT-7 reference point;
- replicate the media as needed for distribution to those participants using unicast transport;
- distribute downlink media to MCPTT UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCPTT-7 reference point;
- distribute downlink media to MCPTT UEs using multicast downlink transport of media for the call by means of the MCPTT-8 reference point; and
- provide a media mixing function where multiple media streams are combined (e.g. multi-talker control) into a single media stream for transmission to the MCPTT 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.
Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the MCPTT server.
NOTE 3: If media mixing in the network is utilized, care should be taken to minimize the feedback of the user's own voice from the mixed audio in order to avoid echoes.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.6 Media mixer
|
This functional entity exists on the UE and provides support for combining multiple media streams (e.g. multi-talker control) into one media stream through the enforcement of media policy information. Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the UE.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.7 MCPTT user database
|
This functional entity contains information of the MCPTT user profile associated with an MCPTT ID that is held by the MCPTT service provider at the application plane. The MCPTT user profile is determined by the mission critical organization, the MCPTT service provider, and potentially the MCPTT user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.2.3.8 MC gateway server
|
The MC gateway server provides support for MCPTT interconnection services with a partner MCPTT system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCPTT servers in the partner MCPTT system without needing to expose the MCPTT servers in the primary MCPTT system outside the trusted domain of the primary MCPTT system. It may be a role of the MCPTT server described in subclause 7.4.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 MCPTT servers within the MCPTT system and the interconnected MCPTT system.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.4.3 Signalling control plane
|
The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5 Reference points
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.1 General reference point principle
|
The protocols on any reference point that is exposed for MCPTT service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [3].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2 Application plane of MCPTT service
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.1 General
|
The reference points for the application plane of MCPTT service are described in the following subclauses.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server)
|
The MCPTT-1 reference point, which exists between the MCPTT client and the MCPTT server, is used for MCPTT application signalling for establishing a session in support of MCPTT. The MCPTT-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. The MCPTT-1 reference point may use the HTTP-1 and HTTP-2 reference points.
The TMGI is communicated between the MCPTT server and the MCPTT client using the MCPTT-1 reference point.
Information that is reported to the MCPTT server from the MCPTT client shall be configurable at the application layer. This interface may include the area where a UE is currently located, described as ECGI of the serving and neighbouring cell(s), MBMS SAIs, MBSFN Area ID. This information comes from the broadcast by the local cell, e.g. from SIB1 and SIB15 (see 3GPP TS 36.331 [12]) as decoded by the UE.
NOTE: This reference point includes the GC1 reference point as described in 3GPP TS 23.468 [9]. It is assumed that the MCPTT server is performing the function of GCS AS. While 3GPP TS 23.468 [9] does not specify GC1 it does include high level descriptions of certain interactions on GC1, including those relating to the availability of multicast delivery for the application client. The MCPTT-1 reference point fulfils the requirements of the GC1 reference point for MCPTT.
Messages supported on this interface may also include the MCPTT server providing the MCPTT client with information describing the mapping of transport resources to specific group calls.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.3 Reference point MCPTT-2 (between the MCPTT server and the MCPTT user database)
|
The MCPTT-2 reference point, which exists between the MCPTT server and the MCPTT user database, is used by the MCPTT server to obtain information about a specific user. The MCPTT-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [18] and shall be intra-network.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.4 Reference point MCPTT-3 (between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server)
|
The MCPTT-3 reference point exists between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server for MCPTT application signalling for establishing MCPTT sessions. The MCPTT-3 reference point shall use the SIP-2 reference point for transport and routing of signalling. If a pair of MCPTT servers, or an MCPTT server and an MC gateway server, are served by different SIP cores then the MCPTT-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-3 reference point.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.5 Reference point MCPTT-4 (unicast between the floor control server and the floor participant)
|
The MCPTT-4 reference point, which exists between the floor control server in the MCPTT server and the floor participant in the MCPTT client, provides floor control signalling between the floor control server in the MCPTT server and the floor participant over a unicast bearer. The MCPTT-4 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.6 Reference point MCPTT-5 (between the MCPTT server and the EPS)
|
The MCPTT-5 reference point, which exists between the MCPTT server and the EPS, is used, subject to the conditions below, by the MCPTT 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 [4].
MCPTT-5 is not used when the MCPTT service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCPTT service provider domain.
MCPTT-5 may be used when the MCPTT service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCPTT service provider domain.
NOTE: Any coordination between the P-CSCF use of Rx and the MCPTT server use of Rx (via MCPTT-5) from the MCPTT service provider domain is not specified in this release of this specification.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.7 Reference point MCPTT-6 (between the MCPTT server and the EPS)
|
The MCPTT-6 reference point, which exists between the MCPTT server and the EPS, is used to request the allocation and activation of multicast transport resources for MCPTT application usage. The MCPTT-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [10].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.8 Reference point MCPTT-7 (unicast between the media distribution function and the media mixer)
|
The MCPTT-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 MCPTT server and the media mixer of the MCPTT client. The MCPTT-7 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.9 Reference point MCPTT-8 (multicast between the media distribution function and the media mixer)
|
The MCPTT-8 reference point, which exists between the media distribution function and the media mixer, is used by the media distribution function of the MCPTT server to send multicast media to the media mixer of the MCPTT client. The MCPTT-8 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.10 Reference point MCPTT-9 (multicast between the floor control server and the floor participant)
|
The MCPTT-9 reference point, which exists between the floor control server and the floor participant, provides floor control signalling between the floor control server and the floor participant over a multicast bearer. The MCPTT-9 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.11 Reference point IWF-1 (between the MCPTT server and the interworking function to legacy systems)
|
The IWF-1 reference point is specified in 3GPP TS 23.283 [20].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.12 Reference points of common services core used in the MCPTT service
|
The descriptions for reference points of the common services core are contained in the common functional architecture to support MC services specified in 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
7.5.2.13 Reference point MCPTT-10 (between the MC gateway server and the MC gateway server in a different MCPTT system)
|
The MCPTT-10 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCPTT system for MCPTT application signalling for establishing MCPTT sessions, shall use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-10 reference point between interconnected MCPTT systems.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
8 Identities
|
The MCPTT service specific identities (e.g. MCPTT ID, MCPTT group ID) are described in clause 8 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
9 Application of functional model to deployments
|
The application of the functional model to deployments, and description of various deployment scenarios for the MCPTT service, can be found in clause 9 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10 Procedures and information flows
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.1 MCPTT service configuration
|
The MCPTT service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [16] with the following clarifications:
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
- The MC service ID is the MCPTT ID; and
- The MC service user profile index is the MCPTT user profile index.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.2 User authentication and authorization for MCPTT service
|
NOTE 1: Flow 10.2-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [19] defines the specific user authentication and authorization architecture required by the MCPTT service in order to realize the MCPTT user authentication and authorization requirements as defined in 3GPP TS 22.179 [2].
A procedure for user authentication is illustrated in figure 10.2-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280[16].
Figure 10.2-1: MCPTT user authentication and registration, single domain
1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280[16].
2. MCPTT client performs the MCPTT service authorization for the user. Step 2 utilizes the results of step 1.
NOTE 2: The MCPTT server may reject a request for service authorization by an MCPTT user if the number of simultaneous service authorizations for that MCPTT user would be exceeded.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.3 Affiliation and de-affiliation to/from MCPTT group(s)
|
The MCPTT service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [16] with the following clarifications:
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
- The MC service group is the MCPTT group;
- The MC service ID is the MCPTT ID; and
- The MC service group ID is the MCPTT group ID.
When an MCPTT user has affiliated to an MCPTT group then the MCPTT user can send and receive MCPTT related media for that MCPTT group. When an MCPTT user has de-affiliated from an MCPTT group then the MCPTT user cannot send and receive MCPTT related media to and from that MCPTT group.
10.3a Activation and de-activation of/from functional alias(es)
The MCPTT service shall support the procedures and related information flows as specified in subclause 10.13.4 and subclause 10.13.5 of 3GPP TS 23.280 [16].
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
- The MC service ID is the MCPTT ID.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4 MCPTT group selection
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.1 General
|
When an MCPTT user wants to transmit on a MCPTT group, an affiliated MCPTT group shall be set as the selected MCPTT group to the MCPTT user. Only one MCPTT group can be set as the selected MCPTT group to an MCPTT user from one particular MCPTT UE at any given time. This subclause describes the detailed procedures for the MCPTT group selection.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.2 Information flows for group selection
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.2.1 Group selection change request
|
Table 10.4.2.1-1 describes the information flow group selection change request from the MCPTT client to the MCPTT server.
Table 10.4.2.1-1: Group selection change request
Information element
Status
Description
MCPTT ID
M
MCPTT user identity whose group selection information is to be changed
MCPTT group ID
M
MCPTT group identity for which the selection is made for the MCPTT ID
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.2.2 Group selection change response
|
Table 10.4.2.2-1 describes the information flow group selection change response from the MCPTT server to the MCPTT client.
Table 10.4.2.2-1: Group selection change response
Information element
Status
Description
Result
M
Result indicates success or failure of group selection change
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.2.3 Group selection change notification
|
Table 10.4.2.3-1 describes the information flow group selection change notification from the MCPTT server to the MCPTT client.
Table 10.4.2.3-1: Group selection change notification
Information element
Status
Description
MCPTT ID
M
MCPTT user identity whose group selection information is to be changed
MCPTT group ID
M
MCPTT group identity for which the selection is made for the MCPTT ID
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.4.3 Authorized user remotely changes another MCPTT user's selected MCPTT group – mandatory mode
|
Procedure for an authorized user to change other MCPTT users' selected MCPTT group without requiring target user's approval is described in figure 10.4.3-1.
Pre-conditions:
- The MCPTT client 1 has already been provisioned (statically or dynamically) with the target MCPTT user's information and its group information, that the selected MCPTT group of target MCPTT user 2 is allowed to be changed;
Figure 10.4.3-1: Remotely change MCPTT group selection – mandatory mode
1. When an authorized user changes other MCPTT users' selected MCPTT group, the MCPTT client 1 sends MCPTT group selection change request to the MCPTT server. The information (i.e. target MCPTT ID, MCPTT group ID) used to set the requested MCPTT group as the selected MCPTT group of the target MCPTT user shall be included.
2. The MCPTT server shall check if the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group. The MCPTT server shall perform the affiliation relationship check based on the stored affiliation status.
3. If the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group, and if the target MCPTT user is not already affiliated to the requested MCPTT group, the remotely change of affiliation procedures shall be performed (see subclause 10.8 in 3GPP TS 23.280 [16]).
4. The MCPTT server then shall send the MCPTT group selection change notification including the target user ID and the selected MCPTT group ID to the MCPTT client 2.
5. The group selection change response then returns to the MCPTT client 1.
6. Target MCPTT client 2 are notified about the change of its selected MCPTT group.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5 Pre-established session (on-network)
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.1 General
|
The MCPTT server and client may use one or more pre-established sessions as defined in 3GPP TS 23.280 [16] for the following procedures for on-network:
- Group calls (as specified in subclause 10.6.2.3 and subclause 10.6.2.4);
- Private calls (as specified in subclause 10.7.2.2 and subclause 10.7.2.3);
- MCPTT emergency group calls (as specified in subclause 10.6.2.6.1);
- MCPTT imminent peril group calls (as specified in subclause 10.6.2.6.2);
- MCPTT emergency private calls (as specified in subclause 10.7.2.4); and
- MCPTT emergency alerts (as specified in subclause 10.6.2.6.3).
For outgoing MCPTT call setup for a private call or a pre-arranged group call using a pre-established session, an MCPTT UE uses SIP procedures to establish the call.
For incoming MCPTT call setup for a pre-arranged group call using a pre-established session, media plane control procedures are used to establish the call between the MCPTT server and client.
For incoming MCPTT call setup for a private call using a pre-established session, SIP procedures are used to establish the call between the MCPTT client and server in manual commencement mode and media plane control procedures in automatic commencement mode.
An MCPTT UE can join an MCPTT chat group using a pre-established session by sending a group join request using SIP procedures.
NOTE: A chat group call is started and notified using floor control messages regardless of whether pre-established session is used.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2 Information flows for pre-established session
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.1 Pre-established session establishment
|
Table 10.5.2.1-1 describes the information flow create pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.1-1: Create pre-established session request
Information element
Status
Description
MCPTT ID of requester (originator)
M
This element identifies the MCPTT user that wishes to create a pre-established session.
SDP offer
M
SDP with media information offered by client (e.g. ports, codec, protocol id).
Table 10.5.2.1-2 describes the information flow create pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.1-2: Create pre-established session response
Information element
Status
Description
SDP Answer
M
SDP with media information offered by server (e.g. ports, codec, protocol id)
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.2 Pre-established session modification
|
Table 10.5.2.2-1 describes the information flow modify pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.2-1: Modify pre-established session request
Information element
Status
Description
MCPTT ID of requester (originator)
M
This element identifies the MCPTT user that wishes to create a pre-established session.
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
SDP offer
M
SDP with media information offered by client (e.g. ports, codec, protocol id).
Table 10.5.2.2-2 describes the information flow modify pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.2-2: Modify pre-established session response
Information element
Status
Description
SDP Answer
M
SDP with media information offered by server (e.g. ports, codec, protocol id).
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.3 Pre-established session release - client initiated
|
Table 10.5.2.3-1 describes the information flow release pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.3-1: Release pre-established session request - client initiated
Information element
Status
Description
MCPTT ID of requester (originator)
M
This element identifies the MCPTT user that wishes to release a pre-established session.
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
Release reason
M
This element indicates that reason for the session release.
Table 10.5.2.3-2 describes the information flow release pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.3-2: Release pre-established session response - client initiated
Information element
Status
Description
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.4 Pre-established session release - server initiated
|
Table 10.5.2.4-1 describes the information flow release pre-established session request from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.4-1: Release pre-established session release request - server initiated
Information element
Status
Description
MCPTT ID of target
M
This element identifies the MCPTT user that is the target of the for pre-established session release.
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
Release reason
M
This element indicates the reason for the session release.
Table 10.5.2.4-2 describes the information flow release pre-established session response from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16].
Table 10.5.2.4-2: Release pre-established session response - server initiated
Information element
Status
Description
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.5 Pre-established session call connect request
|
Table 10.5.2.5-1 describes the information flow pre-established session call connect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.1 of the present document.
Table 10.5.2.5-1: Pre-established session call connect request
Information element
Status
Description
MCPTT group ID
O
Identity of the MCPTT group (see NOTE)
MCPTT ID
O
MCPTT ID of the private call MCPTT user (see NOTE)
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.2.6 Pre-established session call disconnect request
|
Table 10.5.2.1.6-1 describes the information flow pre-established session call disconnect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.2 of the present document.
Table 10.5.2.6-1: Pre-established session call disconnect request
Information element
Status
Description
MCPTT group ID
O
Identity of the MCPTT group (see NOTE)
MCPTT ID
O
MCPTT ID of the private call MCPTT user (see NOTE)
Session ID
M
This element identifies the specific session ID used for pre-established sessions.
Reason code
O
Information about call disconnect reason
NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.3 Procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.3.1 General
|
The MCPTT server and MCPTT client make use of the procedures defined in the following subclauses of the present document and the following procedures in 3GPP TS 23.280 [16]:
- pre-established session establishment;
- pre-established session modification; and
- pre-established session release.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.5.3.2 Call connect and disconnect procedures using pre-established session
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.