hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.3 SIP PUBLISH request for service authorisation and service settings
| The MCPTT server shall support obtaining service authorization specific information from a SIP PUBLISH request for MCPTT server settings.
Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value;
2) an application/poc-settings+xml MIME body; and
3) an application/vnd... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.4 Receiving SIP PUBLISH request for MCPTT service settings only
| Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value;
2) an application/poc-settings+xml MIME body; and
3) an application/vnd.3gpp.mcptt-info+xml MIME body containing an <mcptt-request-uri> element and an <mcptt-client-id> element;
The MCPTT server:
1) shall ide... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.5 Receiving SIP PUBLISH request with "Expires=0"
| Upon receiving a SIP PUBLISH request containing:
1) an Event header field set to the "poc-settings" value; and
2) an Expires header field set to 0;
the MCPTT server:
1) shall identify the IMS public user identity from the P-Asserted-Identity header field;
2) shall process the SIP PUBLISH request according to rules... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.6 Subscription to and notification of MCPTT service settings
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.6.1 Receiving subscription to MCPTT service settings
| Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the participating MCPTT function of the served MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-request-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.6.2 Sending notification of change of MCPTT service settings
| In order to notify the subscriber about changes of the MCPTT service settings of the subscribed MCPTT client of the subscribed MCPTT user, the MCPTT server:
1) shall generate an application/poc-settings+xml MIME body containing:
a) the <am-settings> element of the poc-settings event package set to the current answer ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.3.7 Sending a CSK key download message
| If confidentiality protection is enabled as specified in clause 6.6.2.3.1, and if the participating MCPTT function received a Client Server Key (CSK) within a SIP REGISTER request for service authorisation or SIP PUBLISH request for service authorisation, the participating MCPTT function may decide to update the CSK. I... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4 Coding
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4.1 Extension of MIME types
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4.1.1 General
| The parent clause of this clause defines extensions of MIME type defined in other documents.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4.1.2 Extension of application/poc-settings+xml MIME type
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4.1.2.1 Introduction
| The parent clause of this clause describes extension of the application/poc-settings+xml MIME body specified in IETF RFC 4354 [55]. The extension is used to indicate the selected MCS user profile at an MC client.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 7.4.1.2.2 Syntax
| The application/poc-settings+xml MIME body indicating the selected MCS user profile at an MC client is constructed according to IETF RFC 4354 [55] and:
1) contains a <poc-settings> root element according to IETF RFC 4354 [55];
2) contains one or more <entity> child element according to IETF RFC 4354 [55] of the <poc-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8 Pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.1 General
| The MCPTT client may establish one or more pre-established sessions to the participating MCPTT function at any time after SIP registration and setting the service settings as defined in clause 7.2.2 or clause 7.2.3.
The MCPTT client may use the pre-established session for originating MCPTT calls after pre-established ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.2 Session establishment
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.2.1 MCPTT client procedures
| When the MCPTT client initiates a pre-established session the MCPTT client shall:
1) gather ICE candidates according to IETF RFC 8445 [89]; and
NOTE 1: ICE candidates are only gathered on interfaces that the MCPTT UE uses to obtain MCPTT service.
2) generate an initial SIP INVITE request by following the UE originat... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.2.2 Participating MCPTT function procedures
| Upon receipt of a "SIP INVITE request for establishing a pre-established session" the participating MCPTT function:
1) shall check whether the public service identity is allocated and perform the actions specified in clause 6.3.7.1 if it is not allocated. Otherwise, continue with the rest of the steps;
2) shall deter... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3 Session modification
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.1 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.1.1 MCPTT client initiated
| When the MCPTT client needs to modify the pre-established session outside of an MCPTT call, the MCPTT client:
1) shall generate a SIP UPDATE request or a SIP re-INVITE request according to 3GPP TS 24.229 [4];
2) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1,... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.1.2 Participating MCPTT function initiated
| Upon receiving a SIP UPDATE request or a SIP re-INVITE request to modify an existing pre-established session without an associated MCPTT call, the MCPTT client:
1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec is acceptable by the MC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.2.1 MCPTT client initiated
| Upon receiving a SIP UPDATE request or a SIP re-INVITE request to modify an existing pre-established session without associated MCPTT call, the participating MCPTT function:
1) shall validate that the received SDP offer includes at least one media stream for which the media parameters and at least one codec is accepta... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.3.2.2 Participating MCPTT function initiated
| When the participating MCPTT function needs to modify the pre-established session outside of an MCPTT call, the participating MCPTT function:
1) shall generate a SIP UPDATE request or a SIP re-INVITE request according to 3GPP TS 24.229 [4];
2) shall include an SDP offer according to 3GPP TS 24.229 [4], and include IC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4 Session release
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.1 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.1.1 MCPTT client initiated
| NOTE: The MCPTT client needs to be prepared to release the pre-established session when receiving a SIP BYE request generated by the SIP core (e.g. due to network release of media plane resources).
When a MCPTT client needs to release a pre-established session as created in clause 8.2.1, the MCPTT client:
1) shall ge... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.1.2 Participating MCPTT function initiated
| Upon receiving a SIP BYE request from the participating MCPTT function within a pre-established session the MCPTT client shall check whether there are any MCPTT calls using the pre-established session, and:
1) if there is an established MCPTT call then the MCPTT client shall remove the MCPTT client from the MCPTT cal... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.2.1 MCPTT client initiated
| Upon receiving a SIP BYE request from the MCPTT client within a pre-established session the participating MCPTT function:
1) shall check whether there is a MCPTT call using the pre-established session, and:
a) if there is an established MCPTT session then the participating MCPTT function shall remove the MCPTT clien... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 8.4.2.2 Participating MCPTT function initiated
| When a participating MCPTT function needs to release a pre-established session as created in clause 8.2.2, the participating MCPTT function:
1) shall first release any participants of all MCPTT calls that are using the pre-established session using the procedures as follows. The participating MCPTT function:
a) shall... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9 Affiliation
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.1 General
| Clause 9.2 contains the procedures for explicit affiliation at the MCPTT client, the MCPTT server serving the MCPTT user and the MCPTT server owning the MCPTT group.
Clause 9.2 contains the procedures for implicit affiliation at the MCPTT server serving the MCPTT user and the MCPTT server owning the MCPTT group.
Clau... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2 Procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.1 General
| The MCPTT client procedures consist of:
- an affiliation status change procedure;
- an affiliation status determination procedure;
- a procedure for sending affiliation status change request in negotiated mode to target MCPTT user;
- a procedure for receiving affiliation status change request in negotiated mode fro... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.2 Affiliation status change procedure
| In order:
- to indicate that an MCPTT user is interested in one or more MCPTT group(s) at an MCPTT client;
- to indicate that the MCPTT user is no longer interested in one or more MCPTT group(s) at the MCPTT client;
- to indicate that the MCPTT user continues to have interest in one or more MCPTT group(s) at an MCPT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.3 Affiliation status determination procedure
| NOTE 1: The MCPTT UE also uses this procedure to determine which MCPTT groups the MCPTT user successfully affiliated to.
In order to discover MCPTT groups:
1) which the MCPTT user at an MCPTT client is affiliated to; or
2) which another MCPTT user is affiliated to;
the MCPTT client shall generate an initial SIP SUB... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.4 Procedure for sending affiliation status change request in negotiated mode to target MCPTT user
| NOTE: Procedure for sending affiliation status change request in negotiated mode to several target MCPTT users is not supported in this version of the specification.
Upon receiving a request from the MCPTT user to send an affiliation status change request in negotiated mode to a target MCPTT user, the MCPTT client sha... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.5 Procedure for receiving affiliation status change request in negotiated mode from authorized MCPTT user
| Upon receiving a SIP MESSAGE request containing:
1) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9]; and
2) an application/vnd.3gpp.mcptt-affiliation-command+xml MIME body with a list of MCPTT groups... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.6 Subscription to group dynamic data
| In order to subscribe to changes in per-group dynamic data, the MCPTT client shall generate an initial SIP SUBSCRIBE request specified in 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
In the SIP SUBSCRIBE request, the MCPTT client:
1) shall set the Request-URI to the public service identity identify... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.7 Rules based affiliation status change procedure
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.7.1 General
| The MCPTT client can based on configuration decide to affiliate or de-affiliate to a group.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.7.2 User profile defined rules
| User profile based affiliation rules are controlled by the elements <RulesForAffiliation> or <RulesForDeAffiliation> of the MCPTT user profile document identified by the MCPTT ID of the MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]). The rules can be composed of location criteria (including hea... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.1.7.3 Group configuration defined rules
| If the <permitted-geographic-area> element of the <list-service> element of an MCS group document is present and the MCPTT client is within the area specified in the <permitted-geographic-area> element, the MCPTT client is allowed to affiliate to the group.
If the <mandatory-geographic-area> element of the <list-servi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2 MCPTT server procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.1 General
| The MCPTT server procedures consist of:
- procedures of MCPTT server serving the MCPTT user; and
- procedures of MCPTT server owning the MCPTT group.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2 Procedures of MCPTT server serving the MCPTT user
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.1 General
| The procedures of MCPTT server serving the MCPTT user consist of:
- a receiving affiliation status change from MCPTT client procedure;
- a receiving subscription to affiliation status procedure;
- a sending notification of change of affiliation status procedure;
- a sending affiliation status change towards MCPTT s... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.2 Stored information
| The MCPTT server shall maintain a list of MCPTT user information entries. The list of the MCPTT user information entries contains one MCPTT user information entry for each served MCPTT ID.
In each MCPTT user information entry, the MCPTT server shall maintain:
1) an MCPTT ID. This field uniquely identifies the MCPTT u... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.3 Receiving affiliation status change from MCPTT client procedure
| Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the MCPT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.4 Receiving subscription to affiliation status procedure
| Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains either the public service identity identifying the originating participating MCPTT function serving the MCPTT user, or the public service identity identifying the terminating participating MCPTT function serving the ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.5 Sending notification of change of affiliation status procedure
| In order to notify the subscriber about changes of the served MCPTT ID, the MCPTT server:
1) shall consider an MCPTT user information entry such that:
a) the MCPTT user information entry is in the list of MCPTT user information entries described in clause 9.2.2.2.2; and
b) the MCPTT ID of the MCPTT user information ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.6 Sending affiliation status change towards MCPTT server owning MCPTT group procedure
| NOTE 1: Usage of one SIP PUBLISH request to carry information about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order:
- to send an affiliation request of a served MCPTT ID to a handled MCPTT group ID;
- to send an de-af... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.7 Affiliation status determination from MCPTT server owning MCPTT group procedure
| NOTE 1: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
In order to discover whether a served MCPTT user was successfully affiliated to a handled MCPTT group ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.8 Procedure for authorizing affiliation status change request in negotiated mode sent to served MCPTT user
| Upon receiving a SIP MESSAGE request such that:
1) Request-URI of the SIP MESSAGE request contains the public service identity identifying the terminating participating MCPTT function serving the MCPTT user;
2) the SIP MESSAGE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-requ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.9 Forwarding affiliation status change towards another MCPTT user procedure
| Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-request-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.10 Forwarding subscription to affiliation status towards another MCPTT user procedure
| Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-req... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.11 Affiliation status determination
| This clause is referenced from other procedures.
If the participating MCPTT function needs to determine the affiliation status of an MCPTT user to an MCPTT group, the participating function:
1) shall find the user information entry in the list of MCPTT user information entries described in clause 9.2.2.2.2 such that ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.12 Affiliation status change by implicit affiliation
| This clause is referenced from other procedures.
Upon receiving a SIP request that requires implicit affiliation of the sending MCPTT client to an MCPTT group, the participating MCPTT function:
1) shall determine the served MCPTT client ID from the <mcptt-client-id> element of the application/vnd.3gpp.mcptt-info+xml ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.13 Implicit affiliation status change completion
| This clause is referenced from other procedures.
If the participating MCPTT function has received a SIP 2xx response from the controlling MCPTT function to a SIP request that had triggered performing the procedures of clause 9.2.2.2.12, the participating MCPTT function:
1) shall set the affiliation status of the MCPT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.14 Implicit affiliation status change cancellation
| This clause is referenced from other procedures.
If the participating MCPTT function determines that a received SIP request that had triggered performing the procedures of clause 9.2.2.2.12 needs to be rejected or if the participating MCPTT function receives a SIP 4xx, 5xx or 6xx response from the controlling MCPTT fu... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.15 Implicit affiliation to configured groups procedure
| This clause is referenced from other procedures.
If the participating MCPTT function has successfully performed service authorization for the MCPTT ID identified in the service authorisation procedure as described in 3GPP TS 33.180 [78], the participating MCPTT function:
1) shall identify the MCPTT ID included in the... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.2.16 Forwarding subscription to group dynamic data towards the controlling MCPTT server procedure
| Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info MIME body containing the<mcptt-re... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3 Procedures of MCPTT server owning the MCPTT group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.1 General
| The procedures of MCPTT server owning the MCPTT group consist of:
- receiving group affiliation status change procedure;
- receiving subscription to affiliation status procedure;
- sending notification of change of affiliation status procedure;
- affiliation eligibility check procedure;
- implicit affiliation elig... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.2 Stored information
| The MCPTT server shall maintain a list of MCPTT group information entries.
In each MCPTT group information entry, the MCPTT server shall maintain:
1) an MCPTT group ID. This field uniquely identifies the MCPTT group information entry in the list of the MCPTT group information entries;
2) the status of the MCPTT grou... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.3 Receiving group affiliation status change procedure
| Upon receiving a SIP PUBLISH request such that:
1) Request-URI of the SIP PUBLISH request contains the public service identity of the controlling MCPTT function associated with the served MCPTT group;
2) the SIP PUBLISH request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the <mcptt-request-ur... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.4 Receiving subscription to affiliation status procedure
| NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCPTT users served by the same MCPTT server is not supported in this version of the specification.
Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.5 Sending notification of change of affiliation status procedure
| In order to notify the subscriber identified by the handled MCPTT ID about changes of the affiliation status of the served MCPTT group ID, the MCPTT server:
1) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries described in... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.6 Implicit affiliation eligibility check procedure
| This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to check on the eligibility of the MCPTT user to be implicitly affiliated to the MCPTT group, the controlling MCPTT functi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.7 Affiliation status change by implicit affiliation procedure
| This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to perform an implicit affiliation to, the controlling MCPTT function:
1) shall identify the served MCPTT group ID in the... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.8 Affiliation eligibility check procedure
| This clause is referenced from other procedures.
Upon receiving a SIP request for an MCPTT group that the MCPTT user is not currently affiliated to and that requires the controlling MCPTT function to check on the eligibility of the MCPTT user to be affiliated to the MCPTT group, the controlling MCPTT function shall:
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.9 Receiving subscription to group dynamic data procedure
| Upon receiving a SIP SUBSCRIBE request such that:
1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the controlling MCPTT function associated with the served MCPTT group;
2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcptt-info+xml MIME body containing the<mcptt-reque... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.10 Sending notification of change of group dynamic data procedure
| In order to notify the subscriber identified by the handled MCPTT ID about changes of the per-group dynamic data of the served MCPTT group ID, the MCPTT server:
1) shall consider an MCPTT group information entry such that:
a) the MCPTT group information entry is in the list of MCPTT group information entries describe... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.2.2.3.11 Implicit affiliation status change cancellation
| This clause is referenced from other procedures.
The participating MCPTT function:
1) shall remove the MCPTT user information entry added by the procedures of clause 9.2.2.3.7 such that:
a) the MCPTT client information entry has the MCPTT client ID set to the MCPTT client ID of the MCPTT user whose affiliation statu... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3 Coding
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.1 Extension of application/pidf+xml MIME type
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.1.1 Introduction
| The clauses of the parent clause describe an extension of the application/pidf+xml MIME body specified in IETF RFC 3863 [52]. The extension is used to indicate:
- per-user affiliation information;
- per-group affiliation information; and
- per-group dynamic data information.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.1.2 Syntax
| The application/pidf+xml MIME body indicating per-user affiliation information is constructed according to IETF RFC 3863 [52] and:
1) contains a <presence> root element according to IETF RFC 3863 [52];
2) contains an "entity" attribute of the <presence> element set to the MCPTT ID of the MCPTT user;
3) contains one ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.2 Extension of application/simple-filter+xml MIME type
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.2.1 Introduction
| The clauses of the parent clause describe an extension of the application/simple-filter+xml MIME body specified in IETF RFC 4661 [63].
The extension is used to indicate per-client restrictions of presence event package notification information, per-user restrictions of presence event package notification information a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 9.3.2.2 Syntax
| The application/simple-filter+xml MIME body indicating per-client restrictions of presence event package notification information is constructed according to IETF RFC 4661 [63] and:
1) contains a <filter-set> root element according to IETF RFC 4661 [63];
2) contains a <ns-bindings> child element according to IETF RFC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10 Group call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.0 General
| This clause describes the group call procedures for on-network and off-network.
For on-network, prearranged group call including emergency group call for each functional entity are specified in clause 10.1.1 and chat group (restricted) call including emergency group call for each functional entity are specified in cla... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1 On-network group call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1 Prearranged group call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.1 General
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1 On-demand prearranged group call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.1 Client originating procedures
| Upon receiving a request from an MCPTT user to establish an MCPTT prearranged group session the MCPTT client shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-only> element. If a <preconfigured-group-use-only> element exists and is set to the value "tr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.2 Client terminating procedures
| In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/vnd.3g... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.3 MCPTT upgrade to in-progress emergency or imminent peril
| This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to upgrade the MCPTT group call to an emergency condition or an imminent peril condition on an MCPTT prearranged group, the MCPTT client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.4 MCPTT in-progress emergency cancel
| This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to cancel the in-progress emergency condition on a prearranged MCPTT group, the MCPTT client shall generate a SIP re-INVITE request while in an ongoing prearranged group call by following the UE originat... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.5 MCPTT in-progress imminent peril cancel
| This clause covers both on-demand session and pre-established sessions.
Upon receiving a request from an MCPTT user to cancel the in-progress imminent peril condition on a prearranged MCPTT group, the MCPTT client shall generate a SIP re-INVITE request while in an ongoing prearranged group call by following the proced... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.1.6 MCPTT client receives SIP re-INVITE request
| This clause covers both on-demand session and pre-established sessions.
Upon receipt of a SIP re-INVITE request the MCPTT client:
1) if the SIP re-INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <emergency-ind> elemen... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.2 Prearranged group call using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.2.1 Client originating procedures
| Upon receiving a request from an MCPTT user to establish an MCPTT group session using an MCPTT group identity identifying a prearranged MCPTT group within the pre-established session, the MCPTT client shall determine whether the group document contains a <list-service> element that contains a <preconfigured-group-use-o... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 10.1.1.2.2.2 Client terminating procedures
| Upon receiving a SIP re-INVITE request within a pre-established session without an associated MCPTT call or when generating SIP responses to the SIP re-INVITE request, the MCPTT client shall follow the procedures in clause 10.1.1.2.1.2.
NOTE: In clause 10.1.1.2.1.2, the reader is assumed to replace occurrences of SIP ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.