hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.20 GROUP CALL BROADCAST message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.20.1 Message definition | This message is sent by the UE to other UEs to announce a broadcast group call to other UEs. For contents of the message see Table 15.1.20.1-1.
Message type: GROUP CALL BROADCAST
Direction: UE to other UEs
Table 15.1.20.1-1: GROUP CALL BROADCAST message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call broadcast message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
Call type
Call type
15.2.11
M
V
1
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x
MCPTT group ID
Group ID
15.2.5
M
LV-E
3-x
SDP
SDP
15.2.6
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.21 GROUP CALL BROADCAST END message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.21.1 Message definition | This message is sent by the UE to other UEs to indicate termination of a broadcast group call. For contents of the message see Table 15.1.21.1-1.
Message type: GROUP CALL BROADCAST END
Direction: UE to other UEs
Table 15.1.21.1-1: GROUP CALL BROADCAST END message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group call broadcast end message identity
Message type
15.2.2
M
V
1
Call identifier
Call identifier
15.2.3
M
V
2
MCPTT group ID
MCPTT group ID
15.2.5
M
LV-E
3-x
Originating MCPTT user ID
MCPTT user ID
15.2.10
M
LV-E
3-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.22 MCVIDEO MESSAGE CARRIER message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.22.1 Message definition | This message is used to carry an MCVIDEO message.
For contents of the message see Table 15.1.22.1-1.
Message type: MCVIDEO MESSAGE CARRIER
Direction: UE to other UEs
Table 15.1.22.1-1: MCVIDEO MESSAGE CARRIER message content
IEI
Information Element
Type/Reference
Presence
Format
Length
MCVIDEO MESSAGE CARRIER
Message type
15.2.2
M
V
1
MCVIDEO message
MCVIDEO message
3GPP TS 24.281 [84] clause 17.1
M
V
2-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.23 MCDATA MESSAGE CARRIER message | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.1.23.1 Message definition | This message is used to carry an MCDATA message.
For contents of the message see Table 15.1.23.1-1.
Message type: MCDATA MESSAGE CARRIER
Direction: UE to other UEs
Table 15.1.23.1-1: MCDATA MESSAGE CARRIER message content
IEI
Information Element
Type/Reference
Presence
Format
Length
MCDATA MESSAGE CARRIER
Message type
15.2.2
M
V
1
MCDATA message
MCDATA message
3GPP TS 24.282 [85] clause 15.1.1
M
V
2-x |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2 General message format and information elements coding | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.1 General | The least significant bit of a field is represented by the lowest numbered bit of the highest numbered octet of the field. When the field extends over more than one octet, the order of bit values progressively decreases as the octet number increases.
Figure 15.2.1-1 shows an example of a field where the most significant bit of the field is marked MSB and the least significant bit of the field is marked LSB.
8
7
6
5
4
3
2
1
MSB
x
x
x
x
x
x
x
octet 1
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
LSB
octet N
Figure 15.2.1-1: Example of bit ordering of a field
Within the protocols defined in the present document, the message consists of the following parts:
a) message type information element; and
b) other information elements, as required.
The organization of a message is illustrated in the example shown in Figure 15.2.1-2.
8
7
6
5
4
3
2
1
Message type
octet 1
octet 2
Other information elements as required
octet n
Figure 15.2.1-2: General message organization example
Unless specified otherwise in the message descriptions of clause 15.1, a particular information element shall not be present more than once in a given message.
The sending entity shall set value of a spare bit to zero. The receiving entity shall ignore value of a spare bit
The sending entity shall not set a value of an information element to a reserved value. The receiving entity shall discard message containing an information element set to a reserved value. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.2 Message type | The purpose of the Message type information element is to identify the type of the message.
The value part of the Message type information element is coded as shown in Table 15.2.2-1.
The Message type information element is a type 3 information element with a length of 1 octet.
Table 15.2.2-1: Message types
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
1
GROUP CALL PROBE
0
0
0
0
0
0
1
0
GROUP CALL ANNOUNCEMENT
0
0
0
0
0
0
1
1
GROUP CALL ACCEPT
0
0
0
0
0
1
0
0
GROUP CALL EMERGENCY END
0
0
0
0
0
1
0
1
GROUP CALL IMMINENT PERIL END
0
0
0
0
0
1
1
0
GROUP CALL BROADCAST
0
0
0
0
0
1
1
1
GROUP CALL BROADCAST END
0
0
0
0
1
0
0
0
PRIVATE CALL SETUP REQUEST
0
0
0
0
1
0
0
1
PRIVATE CALL RINGING
0
0
0
0
1
0
1
0
PRIVATE CALL ACCEPT
0
0
0
0
1
0
1
1
PRIVATE CALL REJECT
0
0
0
0
1
1
0
0
PRIVATE CALL RELEASE
0
0
0
0
1
1
0
1
PRIVATE CALL RELEASE ACK
0
0
0
0
1
1
1
0
PRIVATE CALL ACCEPT ACK
0
0
0
0
1
1
1
1
PRIVATE EMERGENCY CALL CANCEL
0
0
0
1
0
0
0
0
PRIVATE EMERGENCY CALL CANCEL ACK
0
0
0
1
0
0
0
1
GROUP EMERGENCY ALERT
0
0
0
1
0
0
1
0
GROUP EMERGENCY ALERT ACK
0
0
0
1
0
0
1
1
GROUP EMERGENCY ALERT CANCEL
0
0
0
1
0
1
0
0
GROUP EMERGENCY ALERT CANCEL ACK
0
0
0
1
0
1
0
1
MCDATA MESSAGE CARRIER
0
0
0
1
0
1
1
0
MCVIDEO MESSAGE CARRIER
All other values are reserved. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.3 Call identifier | The purpose of the Call identifier information element is to uniquely identify the call.
The Call identifier information element is coded as shown in Figure 15.2.3-1 and Table 15.2.3-1.
The Call identifier information element is a type 3 information element with a length of 2 octets.
8
7
6
5
4
3
2
1
Call identifier
octet 1
octet 2
Figure 15.2.3-1: Call identifier information element
Table 15.2.3-1: Call identifier information element
Call identifier value (octet 1 to 2)
The Call identifier contains a number uniquely identifying the call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.4 Refresh interval | The refresh interval information identifier is used to indicate the minimum time period between successive periodic messages;
The Refresh interval information element is coded as shown in Figure 15.2.4-1 and Table 15.2.4-1.
The Refresh interval information element is a type 3 information element with a length of 2 octets.
8
7
6
5
4
3
2
1
Refresh interval value
Octet 1
Octet 2
Figure 15.2.4-1: Refresh interval
Table 15.2.4-1: Refresh interval information element
Refresh interval value (octet 1 to 2)
The Refresh interval contains a number denoting the minimum time interval (milliseconds) between two successive periodic announcements. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.5 MCPTT group ID | The MCPTT group ID information element is used to indicate the destination MCPTT group identifier;
The MCPTT group ID information element is coded as shown in Figure 15.2.5-1 and Table 15.2.5-1.
The MCPTT group ID information element is a type 6 information element.
8
7
6
5
4
3
2
1
Length of MCPTT group ID contents
octet 1
octet 2
octet 3
MCPTT group ID contents
octet n
Figure 15.2.5-1: MCPTT group ID information element
Table 15.2.5-1: MCPTT group ID information element
MCPTT group ID is contained in octet 3 to octet n; Max value of 65535 octets. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.6 SDP | The purpose of the SDP information element is to contain SDP message.
The SDP information element is coded as shown in Figure 15.2.6-1 and Table 15.2.6-1.
The SDP information element is a type 6 information element.
8
7
6
5
4
3
2
1
Length of SDP contents
octet 1
octet 2
octet 3
SDP contents
octet n
Figure 15.2.6-1: SDP information element
Table 15.2.6-1: SDP information element
SDP message container contents (octet 3 to octet n); Max value of 65535 octets.
This information element contains SDP message as defined in Section 10.2.1.1.2 or 11.2.1.1.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.7 Commencement mode | The purpose of the Commencement mode information element is to identify the type of the commencement mode of the private call.
The value part of the Commencement mode information element is coded as shown in Table 15.2.7-1.
The Commence mode information element is a type 3 information element with a length of 1 octet.
Table 15.2.7-1: Commencement mode
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
AUTOMATIC COMMENCEMENT MODE
0
0
0
0
0
0
0
1
MANUAL COMMENCEMENT MODE
All other values are reserved. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.8 Reason | The purpose of the Reason information element is to indicate the reason of the reject.
The Reason information element is coded as shown in table 15.2.8-1.
The Reason information element is a type 3 information element.
Table 15.2.8-1: Reason type
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
0
REJECT
0
0
0
0
0
0
0
1
MEDIA FAILURE
0
0
0
0
0
0
1
0
BUSY
0
0
0
0
0
0
1
1
E2E SECURITY CONTEXT FAILURE
0
0
0
0
0
1
0
0
FAILED
All other values are reserved. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.9 Confirm mode indication | The purpose of the Confirm mode indication information element is to indicate that the terminating MCPTT client is expected to confirm call acceptance.
The Confirm mode indication information element is coded as shown in figure 15.2.9-1.
The Confirm mode indication information element is a type 2 information element.
8
7
6
5
4
3
2
1
Confirm mode indication IEI
octet 1
Figure 15.2.9-1: Confirm mode indication information element |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.10 MCPTT user ID | The MCPTT user ID information element is used to indicate an MCPTT user ID.
The MCPTT user ID information element is coded as shown in Figure 15.2.10-1 and Table 15.2.10-1.
The MCPTT user ID information element is a type 6 information element.
8
7
6
5
4
3
2
1
Length of MCPTT user ID contents
octet 1
octet 2
octet 3
MCPTT user ID contents
octet n
Figure 15.2.10-1: MCPTT user ID information element
Table 15.2.10-1: MCPTT user ID information element
MCPTT user ID is contained in octet 3 to octet n; Max value of 65535 octets. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.11 Call type | The purpose of the Call type information element is to identify the type of the call.
The value part of the Call type information element is coded as shown in Table 15.2.11-1.
The Call type information element is a type 3 information element with a length of 1 octet.
Table 15.2.11-1: Call type
Bits
8
7
6
5
4
3
2
1
0
0
0
0
0
0
0
1
BASIC GROUP CALL
0
0
0
0
0
0
1
0
BROADCAST GROUP CALL
0
0
0
0
0
0
1
1
EMERGENCY GROUP CALL
0
0
0
0
0
1
0
0
IMMINENT PERIL GROUP CALL
0
0
0
0
0
1
0
1
PRIVATE CALL
0
0
0
0
0
1
1
0
EMERGENCY PRIVATE CALL
All other values are reserved. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.12 User location | The User location information element is used to indicate the current location of the MCPTT client;
The User location information element is coded as shown in Figure 15.2.12-1 and Table 15.2.12-1.
The User location information element is a type 6 information element.
8
7
6
5
4
3
2
1
User location IEI
octet 1
Length of User location contents
octet 2
octet 3
octet 4
User location contents
octet n
Figure 15.2.12-1: User location information element
Table 15.2.12-1: User location information element
User location is contained in octet 4 to octet n; Max value of 65535 octets.
The User location information element contains the LocationInfo structure defined in clause 7.4 of 3GPP TS 29.199‑9 [59]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.13 Organization name | The Organization name information element is used to indicate the name of the organization to which the user belongs.
The Organization name information element is coded as shown in Figure 15.2.13-1 and Table 15.2.13-1.
The Organization name information element is a type 6 information element.
8
7
6
5
4
3
2
1
Length of Organization name contents
octet 1
octet 2
octet 3
Organization name contents
octet n
Figure 15.2.13-1: Organization name information element
Table 15.2.13-1: Organization name information element
Organization name is contained in octet 3 to octet n; Max value of 65535 octets. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.14 Call start time | The Call start time information element is used to indicate the UTC time when a call was started.
The Call start time information element is coded as shown in Figure 15.2.14-1 and Table 15.2.14-1.
The Call start time information element is a type 3 information element with a length of 5 octets.
8
7
6
5
4
3
2
1
Call start time value
Octet 1
Octet 5
Figure 15.2.14-1: Call start time value
Table 15.2.14-1: Call start time value
Call start time value (octet 1 to 5)
The Call start time value is an unsigned integer containing UTC time of the time when a call was started, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds). |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.15 Last call type change time | The Last call type change time information identifier is used to indicate the last UTC time when a call priority was changed.
The Last call type change time information element is coded as shown in Figure 15.2.15-1 and Table 15.2.15-1.
The Last call type change time information element is a type 3 information element with a length of 5 octets.
8
7
6
5
4
3
2
1
Last call type change time value
Octet 1
Octet 5
Figure 15.2.15-1: Last call type change time value
Table 15.2.15-1: Last call type change time value
Last call type change time (octet 1 to 5)
The Last call type change time value is an unsigned integer containing UTC time of the time when a call priority was changed, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds). |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 15.2.16 Probe response | The purpose of the probe response information element is to indicate that the GROUP CALL ANNOUNCEMENT message was sent in response of a GROUP CALL PROBE message.
The probe response information element is coded as shown in figure 15.2.16-1.
The probe response is a type 2 information element.
8
7
6
5
4
3
2
1
Probe Response IEI
octet 1
Figure 15.2.16-1: Probe response information element |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16 Regroup using a preconfigured group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.1 General | In the procedures in this clause:
1) temporary group identity in an incoming SIP MESSAGE request refers to the temporary group identity from the <mcptt-regroup-uri> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request; and
2) preconfigured group identity in an incoming SIP MESSAGE request refers to the the group identity from the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request.
Regroup using a preconfigured group refers to the creation of a user/group regroup based on the configuration information associated with an existing group that is referred to as the preconfigured group. A regroup takes its entire configuration from the preconfigured group, including security keys. If the preconfigured group document contains a <list-service> element that contains a <preconfigured-group-use-only> element, that <preconfigured-group-use-only> element is not included in the configuration of the regroup.
All MCPTT servers and all MCPTT clients are configured with the preconfigured group to allow immediate use of the regroup for a call upon creation of the regroup.
A regroup using a preconfigured group is initiated by the MCPTT client referencing a preconfigured group document in the GMS. The advantage of regroup using a preconfigured group is speed of setup of the group, especially when large numbers of users (e.g., thousands) are involved. Control of the regroup using a preconfigured group is focused in the controlling MCPTT function. Creation and removal of a regoup is normally initiated by an MCPTT client. Removal can also be initiated by the controlling MCPTT function. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2 Group regroup using a preconfigured group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.1 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.1.1 Requesting a group regroup using a preconfigured group | Upon receiving a request from an MCPTT user to establish an MCPTT group regroup using a preconfigured group, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
1) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
3) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
5) shall include 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-Id header field according to IETF RFC 6050 [9];
6) shall contain an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
b) if the MCPTT client is aware of active functional aliases, and an active functional alias is to be included in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
c) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
7) shall contain an application/vnd.3gpp.mcptt-regroup+xml MIME body with:
a) the <regroup-action> element set to the value "create";
b) the <mcptt-regroup-uri> element set to a unique temporary group identity URI;
NOTE: How the unique temporary group identity URI is formed is an implementation decision.
c) the <preconfigured-group> element set to the group identity of the preconfigured group; and
d) the <groups-for-regroup> element set to the list of MCPTT group identities of groups that are to be included in the regroup; and
8) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client:
1) should notify the MCPTT user of the successful creation of the group regroup using preconfigured group.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:
1) should notify the MCPTT user of the failure to create the group regroup using preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.1.2 Removing a regroup using preconfigured group | Upon receiving a request from an MCPTT user to remove a user or group regroup using a preconfigured group, the MCPTT client:
1) if the MCPTT client can determine that the in-progress emergency state of the regroup is set to a value of "true":
a) should notify the user, and shall not proceed with the remaining steps;
NOTE: The MCPTT user can, if authorised, cancel the emergency state of the regroup and then reattempt to remove the regroup, if so desired.
2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
3) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
5) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
6) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4];
7) shall include 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-Id header field according to IETF RFC 6050 [9];
8) shall contain an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
b) if the MCPTT client is aware of active functional aliases, and an active functional alias is to be included in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
9) shall contain an application/vnd.3gpp.mcptt-regroup+xml MIME body with:
a) the <mcptt-regroup-uri> element set to the unique temporary group identity URI representing the regroup to be removed; and
b) the <regroup-action> element set to "remove"; and
10) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client:
1) should notify the MCPTT user of the successful removal of the regroup using preconfigured group.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:
1) should notify the MCPTT user of the failure to remove the regroup using preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.1.3 Receiving a notification of creation of a regroup using preconfigured group | Upon receiving a "SIP MESSAGE request to the MCPTT client to request creation of a regroup using preconfigured group", the MCPTT client:
1) should notify the MCPTT user of the creation of the regroup using preconfigured group;
2) shall send a 200 (OK) response to the MCPTT server according to 3GPP TS 24.229 [4];
3) in the application/vnd.3gpp.mcptt-regroup+xml MIME body contained in the incoming SIP MESSAGE request:
a) shall store the value of the <mcptt-regroup-uri> element as the temporary group identity and associate that with the group identity received in the <mcptt-regroup-uri> element;
b) if a <users-for-regroup> element is included in that MIME body, should store the contents of the <users-for-regroup> element as the list of users that are part of that regroup and shall consider the regroup as a user regroup; and
NOTE 1: The MCPTT client can choose to display the list of users in the user regroup to the MCPTT user.
c) if a <groups-for-regroup> element is included in that MIME body, should store the contents of the <groups-for-regroup> element as the list of groups that are part of that regroup and shall consider the regroup as a group regroup;
NOTE 2: The MCPTT client can choose to display the list of groups in the group regroup to the MCPTT user.
4) shall consider that the MCPTT Client is affiliated with the regroup;
5) should not initiate calls targeting any of the constituent groups but instead target the regroup for the duration of a group regroup; and
6) if the regroup is a chat group, the MCPTT client should join the regroup when this notification of creation is received. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.1.4 Receiving notification of removal of a regroup using preconfigured group | Upon receiving a "SIP MESSAGE request to the MCPTT client to request removal of a regroup using preconfigured group", the MCPTT client:
1) should notify the MCPTT user of the removal of the regroup using preconfigured group;
2) shall send a 200 (OK) response to the MCPTT server according to 3GPP TS 24.229 [4]; and
3) shall consider that the MCPTT client is de-affiliated from the regroup. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2.1 General | In the procedures in this clause:
1) temporary group identity in an incoming SIP MESSAGE request refers to the temporary group identity from the <mcptt-regroup-uri> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request; and
2) preconfigured group identity in an incoming SIP MESSAGE request refers to the the group identity from the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2.2 Requesting a group regroup using a preconfigured group | Upon receipt of a "SIP MESSAGE request to the originating participating MCPTT function to request creation of a group regroup using preconfigured group", the originating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The originating participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The originating participating MCPTT function shall skip the rest of the steps;
2) shall determine the MCPTT ID of the user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
3) shall authorise the user. If the user profile identified by the MCPTT ID does not contain an <allow-regroup> element set to "true", the originating participating MCPTT function shall reject the "SIP MESSAGE request to the originating participating MCPTT function to request creation of a group regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "160 user not authorised to request creation of a regroup" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of these steps;
4) shall select a controlling MCPTT function to manage the regroup and determine the public service identity of that controlling MCPTT function;
NOTE 1: How the originating participating MCPTT function selects a controlling MCPTT function to manage the regroup is a deployment decision.
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the selected controlling MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function selected in step 4);
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
d) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request; and
e) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 480 (Temporarily Unavailable) response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall select a different controlling MCPTT function to manage the regroup and determine the public service identity of that controlling MCPTT function;
NOTE 7: How the originating participating MCPTT function whether it decides to retry is a deployment decision.
NOTE 8: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 9: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 10: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 11: How the participating MCPTT function determines the public service identity of the selected controlling MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 12: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
2) shall generate a SIP MESSAGE request as specified in this clause with the Request-URI of the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function selected in step 1); and
3) shall forward the SIP MESSAGE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP MESSAGE request, the originating participating MCPTT function shall send a SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of any SIP 4xx response other than a 480 response, or a SIP 5xx or 6xx response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response; and
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2.3 Removing a regroup using preconfigured group | Upon receipt of a "SIP MESSAGE request to the originating participating MCPTT function to remove a regroup using preconfigured group" for a temporary group identity, the originating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The originating participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The originating participating MCPTT function shall skip the rest of the steps;
2) shall determine the MCPTT ID of the user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
3) shall authorise the user. If the user profile identified by the MCPTT ID does not contain an <allow-regroup> element set to "true", the originating participating MCPTT function shall reject the "SIP MESSAGE request to remove a regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "161 user not authorised to request removal of a regroup " in a Warning header field as specified in clause 4.4, and shall skip the rest of these steps;
4) shall determine the public service identity of the controlling MCPTT function associated with the regroup identity in the SIP MESSAGE request;
NOTE 1: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the participating MCPTT function determines the public service identity of the controlling MCPTT function associated with the regroup or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4;
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
d) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request; and
e) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2;
2) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response;
3) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function; and
4) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response; and
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2.4 Notification of creation of a regroup using preconfigured group | When receiving a "SIP MESSAGE request to the terminating participating MCPTT function to create a group regroup using preconfigured group", the terminating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The terminating participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The terminating participating MCPTT function shall skip the rest of the steps;
2) shall send a SIP 200 (OK) response as specified in 3GPP TS 24.229 [4];
3) for each MCPTT ID contained in the <users-for-regroup> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body, the terminating participating MCPTT function:
a) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
b) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated with the MCPTT ID;
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request with the exception that any <users-for-regroup> elements shall not be copied;
f) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
g) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
h) shall consider the MCPTT ID as affiliated with the temporary group identity representing the regroup identified in the <mcptt-regroup-uri> element in the incoming SIP MESSAGE request; and
4) shall store:
a) the value of the <mcptt-regroup-uri> element as the identity of the regroup based on a preconfigured group;
b) the value of the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the identity of the preconfigured group; and
c) the set of MCPTT IDs contained in the <users-for-regroup> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the list of the users that are members of the group regroup;
until the regroup is removed. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.2.5 Notification of removal of a regroup using preconfigured group | When receiving a "SIP MESSAGE request to the terminating participating MCPTT function to remove a regroup using preconfigured group", the terminating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The terminating participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The terminating participating MCPTT function shall skip the rest of the steps;
2) shall generate a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and shall send the SIP 200 (OK) response as specified in 3GPP TS 24.229 [4];
3) for each served MCPTT ID affiliated with the temporary group identity in the incoming SIP MESSAGE, the terminating participating MCPTT function:
a) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
b) include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated with the MCPTT ID;
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request, with the exceptions that any <users-for-regroup> or <groups-for-regroup> elements shall not be copied;
f) shall copy the contents of the P-Asserted-Identity header field of the incoming SIP MESSAGE request to the P-Asserted-Identity header field of the outgoing SIP MESSAGE request;
g) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];and
h) shall consider the MCPTT ID as deaffiliated from the regroup. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.3 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.3.1 Request to create a group regroup using preconfigured group | When receiving a "SIP MESSAGE request to the controlling MCPTT function to request creation of a group regroup using preconfigured group" the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and shall skip the rest of the steps;
2) if the controlling MCPTT function is not able to handle the regroup based on the MCPTT group indicated in the <preconfigured-group> element in an application/vnd.3gpp.mcptt-regroup+xml MIME body:
a) shall generate a SIP 480 (Temporarily Unavailable) response to the incoming SIP MESSAGE request; and
b) shall send the SIP 480 (Temporarily Unavailable) response as specified in 3GPP TS 24.229 [4] and skip the rest of the steps;
3) if the controlling MCPTT function determines that the proposed group ID for the regroup is already in use, shall reject the "SIP MESSAGE request to the controlling MCPTT function to request creation of a group regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "165 group ID for regroup already in use" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
4) for each group identified in the <groups-for-regroup> element:
a) shall determine the controlling MCPTT function serving that group;
NOTE 1: The controlling MCPTT function serving a consitituent group assumes the role of a non-controlling MCPTT function for the regroup.
b) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
c) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
d) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the non-controlling MCPTT function;
NOTE 2: The public service identity can identify the non-controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function associated with the constituent MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
e) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
f) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
g) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
h) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
5) shall wait to receive SIP responses from all of the non-controlling MCPTT functions that were sent a SIP MESSAGE request above;
6) if all of the SIP responses received above are SIP 200 (OK) responses:
a) shall send a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall store the list of group identities contained in the <groups-for-regroup> element;
c) shall store the value of the <mcptt-regroup-uri> element as the identity of the group regroup based on a preconfigured group; and
d) shall store the value of the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the identity of the preconfigured group; and
7) if at least one of the SIP responses received above is not a SIP 2xx response:
a) shall send a SIP 480 (Temporarily Unavailable) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) for each non-controlling MCPTT function that returned a SIP 200 (OK) response in step 4:
i) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
ii) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the non-controlling MCPTT function;
NOTE 7: The public service identity can identify the non-controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 8: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 9: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 10: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function associated with the constituent MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 11: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
iii) shall include an application/vnd.3gpp.mcptt-regroup+xml MIME body in the outgoing SIP MESSAGE request with;
A) an <mcptt-regroup-uri> element set to the identity of the regroup; and
B) a <regroup-action> element set to "remove"; and
iv) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.3.2 Request to remove a regroup using preconfigured group | When receiving a "SIP MESSAGE request to the controlling MCPTT function to remove a regroup using preconfigured group" the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The controlling MCPTT function shall skip the rest of the steps;
2) if the in-progress emergency state of the regroup is set to a value of "true", then:
a) shall send a SIP 403 (Forbidden) response to the received SIP MESSAGE request including warning text set to "169 user not authorised to remove regroup in an emergency state" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
NOTE 1: The MCPTT client that receives the SIP 403 (Forbidden) response is expected to notify the MCPTT user that the remove of the regroup was not accomplished because the regroup is in an emergency state. The MCPTT user can then, if authorised, cancel the emergency state of the regroup and reattempt to remove the regroup, if so desired.
3) if the controlling MCPTT function determines that the requested group ID for the regroup removal does not exist, shall reject the "SIP MESSAGE request to the controlling MCPTT function to remove a regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "163 the group identity indicated in the request does not exist" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
4) shall send a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
5) if the regroup is a group regroup based on preconfigured group, then:
a) for each constituent group belonging to the regroup:
i) shall determine the non-controlling MCPTT function serving that group;
ii) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
iii) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
iv) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the non-controlling MCPTT function;
NOTE 2: The public service identity can identify the non-controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function associated with the constituent MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
v) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
vi) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
vii) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
viii) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
6) if the regroup is a user regroup based on preconfigured group, then for each user belonging to the regroup, the controlling MCPTT function shall create a separate list of MCPTT IDs for users belonging to and affiliated with the regroup who are served by the same terminating participating MCPTT function and for each terminating participating MCPTT function;
a) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 7: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 8: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 9: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 10: How the controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 11: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
f) shall use the list of affiliated MCPTT IDs for this terminating participating MCPTT function to create and include a <users-for-regroup> element contained in the application/vnd.3gpp.mcptt-regroup+xml MIME body;
g) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
h) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.3.3 Decision to remove a regroup using preconfigured group | When the controlling MCPTT function decides to remove a regroup using preconfigured group, the controlling MCPTT function:
1) if the regroup is a group regroup based on preconfigured group, then:
a) for each constituent group belonging to the regroup:
i) shall determine the non-controlling MCPTT function serving that group;
ii) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
iii) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the non-controlling MCPTT function determined in step i);
NOTE 1: The public service identity can identify the non-controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the non-controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the non-controlling MCPTT function associated with the constituent MCPTT group or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
iv) shall create an application/vnd.3gpp.mcptt-regroup+xml MIME body and include it in the outgoing SIP MESSAGE request with:
A) an <mcptt-regroup-uri> element set to the identity of the regroup;
B) a <regroup-action> element set to "remove"; and
v) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
2) if the regroup is a user regroup based on preconfigured group, then the controlling MCPTT function shall create a list of terminating participating MCPTT functions serving users belonging to and affiliated with the regroup and shall create a list of MCPTT IDs that are affiliated to the regroup and served by the same terminating partificpating MCPTT function for each of the members of the list of terminating participating MCPTT functions, and for each terminating participating MCPTT function in the list:
a) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 6: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 7: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 8: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 9: How the controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 10: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
c) shall create an application/vnd.3gpp.mcptt-regroup+xml MIME body and include it in the outgoing SIP MESSAGE request with:
i) an <mcptt-regroup-uri> element set to the identity of the regroup;
ii) a <regroup-action> element set to "remove"; and
iii) a <users-for-regroup> element set to the list of MCPTT IDs served by this terminating participating MCPTT function that are affiliated to the regroup; and
d) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.4 Non-controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.4.1 Notification of creation of a group regroup using preconfigured group | When receiving a "SIP MESSAGE request to a non-controlling MCPTT function to request creation of a group regroup using preconfigured group" the non-controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24], and shall skip the rest of the steps;
2) for each group identified in the <groups-for-regroup> element of an application/vnd.3gpp.mcptt-regroup+xml MIME body in the incoming SIP MESSAGE request for which the MCPTT function is the non-controlling MCPTT function:
a) shall determine if the group is already regrouped, and if the group is already regrouped:
i) shall reject the SIP request with a SIP 403 (Forbidden) response including warning text set to "148 group is regrouped" in a Warning header field as specified in clause 4.4; and
ii) shall not process the remaining steps;
3) shall store:
a) the list of group identities contained in the <groups-for-regroup> element;
b) the value of the <mcptt-regroup-uri> element as the identity of the group regroup;
c) the value of the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the identity of the preconfigured group; and
d) information that each of the groups identified in the <groups-for-regroup> element has been regrouped using a preconfigured group;
4) shall send a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
5) for each group identified in the <groups-for-regroup> element of an application/vnd.3gpp.mcptt-regroup+xml MIME body in the incoming SIP MESSAGE request for which the MCPTT function is the non-controlling MCPTT function shall create a separate list of MCPTT IDs for users belonging to and affiliated with the identified group who are served by the same terminating participating MCPTT function;
6) shall merge the lists of MCPTT IDs associated with each terminating participating MCPTT function such that the resulting list associated with a terminating participating MCPTT function contains the MCPTT IDs of all users served by the participating MCPTT function that belong to and are affiliated with any of the groups identified in the <groups-for-regroup> element; and
7) for each terminating participating MCPTT function identified above:
a) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the non-controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
f) shall use the list of MCPTT IDs for this terminating participating MCPTT function as generated in step 3) to create and include the <users-for-regroup> element in the application/vnd.3gpp.mcptt-regroup+xml MIME body;
g) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the non-controlling MCPTT function; and
h) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.4.2 Notification of removal of a group regroup using preconfigured group | When receiving a "SIP MESSAGE request to the non-controlling MCPTT function to remove a group regroup using preconfigured group" the non-controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The non-controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The non-controlling MCPTT function shall skip the rest of the steps;
2) shall send a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
3) shall identify the constituent groups belonging to the regroup identified in the <mcptt-regroup-uri> in the application/vnd.3gpp.mcptt-regroup+xml MIME body contained in the incoming SIP MESSAGE for which this MCPTT function is the non-controlling MCPTT function and shall create a list of terminating participating MCPTT functions serving MCPTT IDs belonging to the identified constituent groups and for each member of the list of terminating participating MCPTT functions in the list shall create a list of MCPTT IDs affiuliated to the regroup and served by that terminating participating MCPTT function;
4) for each terminating participating MCPTT function identified in step 3):
a) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the non-controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
i) shall create and include a <users-for-regroup> element containing the list of MCPTT IDs affiliated to the regroup that are served by this terminating participating MCPTT function as determined in step 3); and
f) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the non-controlling MCPTT function; and
g) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.2.4.3 Notification of additional members of a group regroup using preconfigured group | When a non-controlling MCPTT function becomes aware of an MCPTT client affiliating with a group that it controls, where that group is a constituent group of a group regroup using preconfigured group, the non-controlling MCPTT function:
1) shall create a list of MCPTT IDs for users belonging to and affiliated with the identified constituent group who are served by the same terminating participating MCPTT function as the MCPTT client affiliating with the constituent group;
2) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
3) shall create in the SIP MESSAGE request copies of all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the SIP MESSAGE request received from the controlling MCPTT function for the group regroup to notify creation of the group regroup using preconfigured group;
4) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the non-controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall create an application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP MESSAGE request using the information from the application/vnd.3gpp.mcptt-info+xml MIME body originally included in the SIP MESSAGE request received from the controlling MCPTT function for the group regroup to notify creation of the group regroup using preconfigured group;
6) shall create an application/vnd.3gpp.mcptt-regroup+xml MIME body in the outgoing SIP MESSAGE request using the information from the application/vnd.3gpp.mcptt-regroup+xml MIME body originally included in the SIP MESSAGE request received from the controlling MCPTT function for the group regroup to notify creation of the group regroup using preconfigured group;
7) shall use the list of MCPTT IDs as generated in step 1) to create and include the <users-for-regroup> element in the application/vnd.3gpp.mcptt-regroup+xml MIME body;
8) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the non-controlling MCPTT function; and
9) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3 User regroup using a preconfigured group | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.1 Client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.1.1 Requesting a user regroup using a preconfigured group | Upon receiving a request from an MCPTT user to establish an MCPTT user regroup using a preconfigured group, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
1) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
2) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
3) shall set the Request-URI to the public service identity identifying the originating participating MCPTT function serving the MCPTT user;
4) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4];
5) shall include 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-Id header field according to IETF RFC 6050 [9];
6) shall contain an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
b) if the MCPTT client is aware of active functional aliases, and an active functional alias is to be included in the SIP MESSAGE request, the <anyExt> element with the <functional-alias-URI> element set to the URI of the used functional alias; and
c) if the MCPTT user has requested an application priority, the <anyExt> element with the <user-requested-priority> element set to the user provided value;
7) shall contain an application/vnd.3gpp.mcptt-regroup+xml MIME body with:
a) the <mcptt-regroup-uri> element set to a unique temporary group identity URI;
NOTE: How the unique temporary group identity URI is formed is an implementation decision.
b) the <preconfigured-group> element set to the group identity of the preconfigured group;
c) the <regroup-action> element set to "create"; and
d) the <users-for-regroup> element set to the list of MCPTT IDs of users that are to be included in the regroup; and
8) shall send the SIP MESSAGE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP MESSAGE request, the MCPTT client:
1) should notify the MCPTT user of the successful creation of the user regroup using preconfigured group.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:
1) should notify the MCPTT user of the failure to create the user regroup using preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.1.2 Removing a regroup using preconfigured group | When the user requests the MCPTT client to remove a user regroup, the MCPTT client uses the procedure in clause 16.2.1.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.1.3 Creating a user regroup using preconfigured group | The procedure in clause 16.2.1.3 is used by the MCPTT client when the MCPTT server notifies the MCPTT client of the creation of a user regroup using preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.1.4 Removing a user regroup using preconfigured group | The procedure in clause 16.2.1.4 is used by the MCPTT client when the MCPTT server notifies the MCPTT client of the removal of a user regroup using preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2.1 General | In the procedures in this clause:
1) temporary group identity in an incoming SIP MESSAGE request refers to the temporary group identity from the <mcptt-regroup-uri> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request; and
2) preconfigured group identity in an incoming SIP MESSAGE request refers to the the group identity from the <preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body of the incoming SIP MESSAGE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2.2 Requesting a user regroup using a preconfigured group | Upon receipt of a "SIP MESSAGE request to the originating participating MCPTT function to request creation of a user regroup using preconfigured group", the originating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The originating participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The originating participating MCPTT function shall skip the rest of the steps;
2) shall determine the MCPTT ID of the user from the public user identity in the P-Asserted-Identity header field of the SIP MESSAGE request;
3) shall authorise the user. If the user profile identified by the MCPTT ID does not contain an <allow-regroup> element set to "true", the originating participating MCPTT function shall reject the "SIP MESSAGE request to the originating participating MCPTT function to request creation of a user regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "160 user not authorised to request creation of a regroup" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of these steps;
4) shall select a controlling MCPTT function to manage the regroup and determine the public service identity of the controlling MCPTT function;
NOTE 1: How the originating participating MCPTT function selects a controlling MCPTT function to manage the regroup is a deployment decision.
NOTE 2: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 3: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 4: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 5: How the participating MCPTT function determines the public service identity of the selected controlling MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 6: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
5) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] and:
a) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
b) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCPTT function determined in step 4);
c) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request; and
d) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request; and
e) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function; and
6) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
Upon receipt of a SIP 480 (Temporarily Unavailable) response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall select a different controlling MCPTT function to manage the regroup and determine the public service identity of that controlling MCPTT function;
NOTE 7: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 8: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 9: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 10: How the participating MCPTT function determines the public service identity of the selected controlling MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 11: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
2) shall generate a SIP MESSAGE request as specified in this clause with the Request-URI of the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function determined in step 1); and
3) shall forward the SIP MESSAGE request according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall generate a SIP 200 (OK) response as specified in the clause 6.3.2.1.5.2;
2) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response;
3) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function; and
4) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 4xx response that is not a 480 response, or a SIP 5xx or 6xx response to the above SIP MESSAGE request, the originating participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response; and
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2.3 Removing a regroup using preconfigured group | When the originating participating MCPTT function needs to remove a user regroup, the originating participating MCPTT function uses the procedure in clause 16.2.2.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2.4 Notification of creation of a user regroup using preconfigured group | When receiving a "SIP MESSAGE request to the terminating participating MCPTT function to create a user regroup using preconfigured group", the terminating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The terminating participating MCPTT function shall skip the rest of the steps;
2) shall send a SIP 200 (OK) response in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
3) for each MCPTT ID contained in the <users-for-regroup> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body, the terminating participating MCPTT function is aware from stored information that the MCPTT client has not previously been notified of the creation of the user regroup:
a) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]:
b) include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public user identity associated with the MCPTT ID;
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request, with the exception that any <groups-for-regroup> elements shall not be copied;
f) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the participating MCPTT function;
g) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4]; and
h) shall consider the MCPTT ID as affiliated with the temporary group identity representing the regroup identified in the <mcptt-regroup-uri> element in the incoming SIP MESSAGE request; and
4) shall store:
a) the value of the <mcptt-regroup-uri> element as the identity of the regroup based on a preconfigured group;
b) the value of the preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the identity of the preconfigured group; and
c) the list of the users that are members of the user regroup;
until the regroup is removed. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.2.5 Notification of removal of a user regroup using preconfigured group | When the terminating participating MCPTT function receives a request to remove a user regroup it uses the procedure in clause 16.2.2.5. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.3 Controlling MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.3.1 Request to create a user regroup using preconfigured group | When receiving a "SIP MESSAGE request to the controlling MCPTT function to request creation of a user regroup using preconfigured group" the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The controlling MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. The controlling MCPTT function shall skip the rest of the steps;
2) if the controlling MCPTT function is unable to handle the user regroup it shall send a SIP 480 (Temporarily Unavailable) response to the incoming SIP MESSAGE request and shall skip the rest of the steps;
3) if the controlling MCPTT function determines that the proposed group ID for the regroup is already in use, shall reject the "SIP MESSAGE request to the controlling MCPTT function to request creation of a user regroup using preconfigured group" with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "165 group ID for regroup already in use" in a Warning header field as specified in clause 4.4, and shall skip the rest of the steps;
4) shall create a separate list of MCPTT IDs containing all users identified in the <users-for-regroup> element in the application/vnd.3gpp.mcptt-regroup+xml MIME body who are served by the same terminating participating MCPTT function;
5) for each terminating participating MCPTT function identified in step 3):
a) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
b) shall include in the SIP MESSAGE request all Accept-Contact header fields and all Reject-Contact header fields, with their feature tags and their corresponding values along with parameters according to rules and procedures of IETF RFC 3841 [6] that were received (if any) in the incoming SIP MESSAGE request;
c) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the terminating participating MCPTT function;
NOTE 1: The public service identity can identify the terminating participating MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 2: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 3: If the terminating participating MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system
NOTE 4: How the controlling MCPTT function determines the public service identity of the targeted terminating participating MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 5: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
d) shall copy the contents of the application/vnd.3gpp.mcptt-info+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP MESSAGE request;
e) shall copy the contents of the application/vnd.3gpp.mcptt-regroup+xml MIME body received in the incoming SIP MESSAGE request into an application/vnd.3gpp.mcptt-regroup+xml MIME body included in the outgoing SIP MESSAGE request;
f) shall use the list of MCPTT IDs for this participating MCPTT function as generated in step 3) to create and include a <users-for-regroup> element contained in the application/vnd.3gpp.mcptt-regroup+xml MIME body;
g) shall include a P-Asserted-Identity header field in the outgoing SIP MESSAGE request set to the public service identity of the controlling MCPTT function; and
h) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4];
6) when the controlling MCPTT function receives a SIP 200 (OK) response from any of the terminating participating MCPTT functions that were sent a SIP MESSAGE request in step 4) the controlling MCPTT function shall:
a) send a SIP 200 (OK) response to the incoming SIP MESSAGE request; and
b) store the the value of the <mcptt-regroup-uri> element as the identity of the user regroup based on a preconfigured group;
c) the value of the preconfigured-group> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the identity of the preconfigured group; and
d) store the set of MCPTT IDs contained in the <users-for-regroup> element of the application/vnd.3gpp.mcptt-regroup+xml MIME body as the the list of the users that are members of the user regroup; and
7) if no SIP 200 (OK) response is received for a SIP MESSAGE sent in step 4), the controlling MCPTT function shall send a SIP 480 (Temporarily Unavailable) response to the incoming SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.3.2 Request to remove a user regroup using preconfigured group | When the controlling MCPTT function receives a request to remove a user regroup it uses the procedure in clause 16.2.3.2. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 16.3.3.3 Decision to remove a regroup using preconfigured group | When the controlling MCPTT function decides to remove a user regroup it uses the procedure in clause 16.2.3.3. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17 Adhoc group call | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.1 General | This clause describes the adhoc group call procedures for on-network across single or multiple MCPTT systems, and associated functions such as emergency calls, Imminent peril calls, broadcast calls and others.
The adhoc group calls can use the participant list provided by either an initiator of the call or the MCPTT server. The MCPTT server can use the criteria provided by the initiator of the call to determine the participant list along with local criteria or local policies. The resulting adhoc group uses the configuration of a separate preconfigured MCPTT group. The MCPTT client of an authorized MCPTT user can request to modify the criteria which were used to determine the participant list.
NOTE 1: A preconfigured group that is intended only to provide configuration for the adhoc group is identified by a parameter in the group configuration described in 3GPP TS 23.280 [82].
Editor’s Note: It is FFS an additional parameter is needed in group configuration.
The preconfigured MCPTT group that provides the configuration is not used for the MCPTT group communication, it only provides configuration for one or more adhoc group calls. The MCPTT group ID of the adhoc group call is provided by the MCPTT server when the adhoc group call originated. To establish a security context for the end-to-end secured adhoc group call, the security related information is used from this preconfigured group. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2 MCPTT client procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.1 General | This clause describes the adhoc group call procedures using on-demand and pre-established sessions to setup adhoc group calls, release the ongoing adhoc group calls, and modify (criteria for) the participant list of the ongoing adhoc group calls. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2 Adhoc group call setup | This clause describes the originating, and terminating call setup procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.1 Call setup procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.1.1 Client originating procedures | Upon receiving a request from an MCPTT user to establish an MCPTT adhoc group session, the MCPTT client shall determine whether the service configuration document contains an <on-network> element that contains an <anyExt> element that contains an <adhoc-group-call> element that contains an <allow-adhoc-group-call-support> element and if an <allow-adhoc-group-call-support> element does not exist, or is set to a value of "false, then the MCPTT client:
1) should indicate to the MCPTT user that adhoc group calls are not allowed; and
2) shall skip the remainder of this procedure.
Upon receiving a request from an MCPTT user to establish an MCPTT adhoc group session, the MCPTT client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client:
1) shall set the Request-URI of the SIP INVITE request to a public service identity identifying the participating MCPTT function serving the MCPTT user;
2) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP INVITE request according to IETF RFC 3840 [16];
3) shall include an Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
4) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP INVITE request;
5) shall include an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
6) should include the "timer" option tag in the Supported header field;
7) should include the Session-Expires header field according to IETF RFC 4028 [7]. It is recommended that the "refresher" header field parameter is omitted. If included, the "refresher" header field parameter shall be set to "uac";
8) may include a P-Preferred-Identity header field in the SIP INVITE request containing a public user identity as specified in 3GPP TS 24.229 [4];
9) if the MCPTT user has requested the origination of a broadcast adhoc group call, the MCPTT client shall comply with the procedures in clause 6.2.8.2;
10) shall contain in an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <session-type> element set to a value of "adhoc";
b) if the call setup request follows an emergency alert for an adhoc group, or if the MCPTT client needs to include an identity of adhoc group, the <mcptt-request-uri> element set to the identity of the adhoc group;
NOTE 1: If the call setup request follows an emergency alert for an adhoc group then this element is included and the identity of adhoc group learned during an adhoc group emergency alert procedures is used.
NOTE 2: The MCPTT client can optionally include an identity of adhoc group if it learns by any other means or generated by the MCPTT client using required parameters.
c) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client; and
NOTE 3: The MCPTT client does not include the MCPTT ID of the originating MCPTT user in the body, as this will be inserted into the body of the SIP INVITE request that is sent from the originating participating MCPTT function.
d) an <anyExt> element containing:
i) if the MCPTT client needs to include an active functional alias in the initial SIP INVITE request, the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 4: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
ii) if the MCPTT user has requested an application priority, the <user-requested-priority> element set to the user provided value;
iii) if end-to-end security needs to be established for the MCPTT adhoc group session, the <end-to-end-security> element set to "true"; and
iv) if the call setup request follows an emergency alert for an adhoc group, the <adhoc-grp-emg-alert-grp-ind> element set to "true";
11) if the MCPTT user has requested to include the list of MCPTT users to be called and the call setup request does not follow an adhoc group for emergency alert, shall insert in the SIP INVITE request an application/resource-lists+xml MIME body with the MCPTT ID of the invited MCPTT users to be called, according to rules and procedures of IETF RFC 5366 [20];
12) if the MCPTT user has requested to include the criteria for determining the list of MCPTT users to be called and the call setup request does not follow an adhoc group for emergency alert, shall insert a <call-participants-criterias> with one or more criteria as a comma separated list into <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the SIP INVITE request;
NOTE 5: The MCPTT client can include either a list of MCPTT users or the criteria for determining the list of MCPTT users to be called. These two information elements are not included if the call setup request follows an adhoc group for emergency alerts.
13) shall include an SDP offer according to 3GPP TS 24.229 [4] with the clarifications given in clause 6.2.1;
14) if an implicit floor request is required, shall indicate this as specified in clause 6.4 and
a) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true", shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
15) if the MCPTT user has requested the origination of an MCPTT emergency adhoc group call or is originating an MCPTT adhoc group call and the MCPTT emergency state is already set, the MCPTT client shall comply with the procedures in clause 6.2.8.1.21;
16) if the MCPTT user has requested the origination of an MCPTT imminent peril adhoc group call, the MCPTT client shall comply with the procedures in clause 6.2.8.1.25; and
17) shall send the SIP INVITE request towards the MCPTT server according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP INVITE request, the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];
2) may notify the answer state to the user (i.e. "Unconfirmed" or "Confirmed") if received in the P-Answer-State header field;
3) if the <preconfigured-group-id> element received in the application/vnd.3gpp.mcptt-info+xml MIME body, shall use the security related information from the group configuration associated with the received preconfigured group identity;
4) may notify the user with the adhoc group identity received in the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
5) if not yet subscribed, may subscribe to the conference event package as specified in clause 10.1.3.1; and
6) if received response to a SIP request for a priority adhoc group call, the MCPTT client shall perform the actions specified in clause 6.2.8.1.22.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP INVITE request:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];
2) if received response to a SIP request for a priority adhoc group call, shall perform the actions specified in clause 6.2.8.1.23; and
3) may notify the user about call setup failure with an appropriate response along with the description. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.1.2 Client terminating procedures | In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <adhoc-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.3gpp.mcptt-info+xml MIME body.
Upon receipt of an initial SIP INVITE request, the MCPTT client shall follow the procedures for the termination of multimedia sessions in the IM CN subsystem as specified in 3GPP TS 24.229 [4] with the clarifications below.
The MCPTT client:
1) may reject the SIP INVITE request if any of the following conditions are met:
a) MCPTT client does not have enough resources to handle the call;
b) the number of the maximum simultaneous MCPTT emergency adhoc group calls supported for the specific calling functional alias as specified in the <MaxSimultaneousEmergencyGroupCalls> element within the <FunctionalAliasList> list element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) has been reached; or
c) any other reason outside the scope of this specification;
2) if the SIP INVITE request is rejected in step 1), shall respond toward participating MCPTT function either with an appropriate reject code as specified in 3GPP TS 24.229 [4] and warning texts as specified in clause 4.4.2 or with SIP 480 (Temporarily unavailable) response not including warning texts if the user is authorised to restrict the reason for failure and skip the rest of the steps of this clause;
NOTE: If the SIP INVITE request contains an adhoc emergency indication or adhoc imminent peril indication, the MCPTT client can by means beyond the scope of this specification choose to accept the request.
3) shall check if a Resource-Priority header field is included in the incoming SIP INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
4) if the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <adhoc-emergency-ind> element set to a value of "true":
a) should display to the MCPTT user an indication that this is a SIP INVITE request for an MCPTT emergency adhoc group call;
b) shall set the MCPTT emergency adhoc group state to "MEAG 2: in-progress"; and
c) shall set the MCPTT imminent peril adhoc group call state to "MIAGC 1: imminent-peril-capable" and the MCPTT imminent peril adhoc group state to "MIAG 1: no-imminent-peril";
5) if the SIP INVITE request contains an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with the <imminentperil-ind> element set to a value of "true":
a) should display to the MCPTT user an indication that this is a SIP INVITE request for an MCPTT imminent peril adhoc group call; and
b) shall set the MCPTT imminent peril adhoc group state to "MIAG 2: in-progress";
5) may display to the MCPTT user the MCPTT ID of the inviting MCPTT user;
6) may display to the MCPTT user the functional alias of the inviting MCPTT user, if present;
7) if the <preconfigured-group-id> element received in the application/vnd.3gpp.mcptt-info+xml MIME body, shall use the security related information from the group configuration associated with the received preconfigured group identity;
8) may notify the user with the adhoc group identity received in the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body;
9) shall perform the automatic commencement procedures specified in clause 6.2.3.1.2 if one of the following conditions are met:
a) SIP INVITE request contains an Answer-Mode header field with the value "Auto" and the MCPTT service setting at the invited MCPTT client for answering the call is set to automatic commencement mode; or
b) SIP INVITE request contains an Answer-Mode header field with the value "Auto" and the MCPTT service setting at the invited MCPTT client for answering the call is set to manual commencement mode, yet the invited MCPTT client allows the call to be answered with automatic commencement mode;
10) shall perform the manual commencement procedures specified in clause 6.2.3.2.2 if one of the following conditions are met:
a) SIP INVITE request contains an Answer-Mode header field with the value "Manual" and the MCPTT service setting at the invited MCPTT client for answering the call is to use manual commencement mode; or
b) SIP INVITE request contains an Answer-Mode header field with the value "Manual" and the MCPTT service setting at the invited MCPTT client for answering the call is set to automatic commencement mode, yet the invited MCPTT client allows the call to be answered with manual commencement mode; and
11) when the SIP 200 (OK) response to the SIP INVITE request is sent, and if not yet subscribed, may subscribe to the conference event package as specified in clause 10.1.3.1. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.2 Call setup procedures using pre-established session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.2.1 Client originating procedures | Upon receiving a request from an MCPTT user to establish an MCPTT adhoc group session within the pre-established session, the MCPTT client shall determine whether the service configuration document contains an <on-network> element that contains an <anyExt> element that contains an <adhoc-group-call> element that contains an <allow-adhoc-group-call-support> element and if an <allow-adhoc-group-call-support> element does not exist, or is set to a value of "false", then the MCPTT client:
1) should indicate to the MCPTT user that adhoc group calls are not allowed; and
2) shall skip the remainder of this procedure.
The MCPTT client shall generate a SIP REFER request outside a dialog in accordance with the procedures specified in 3GPP TS 24.229 [4], IETF RFC 4488 [22] and IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27], with the clarifications given below.
The MCPTT client:
1) shall include the Request-URI set to the public service identity identifying the pre-established session on the MCPTT server serving the MCPTT user;
2) shall include the Refer-Sub header field with value "false" according to rules and procedures of IETF RFC 4488 [22];
3) shall include the Supported header field with value "norefersub" according to rules and procedures of IETF RFC 4488 [22];
4) shall include the option tag "multiple-refer" in the Require header field;
5) may include a P-Preferred-Identity header field in the SIP REFER request containing a public user identity as specified in 3GPP TS 24.229 [4];
6) shall include a P-Preferred-Service header field set to the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4]), according to IETF RFC 6050 [9];
7) if the MCPTT user has requested to include the list of MCPTT users to be called and the call setup request does not follow an adhoc group for emergency alert:
a) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20], and with the Content-ID header field set to this "cid" URL and Content-Type header filed set to "application/resource-lists+xml";
b) shall include in the application/resource-lists MIME body an <entry> element for each of the targeted MCPTT users, with each <entry> element containing a "uri" attribute set to the MCPTT ID of the targeted user, extended with hname "body" parameter in the headers portion of the SIP URI containing:
NOTE 1: Characters that are not formatted as ASCII characters are escaped in the following parameters in the headers portion of the SIP URI.
i) the Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; and
ii) an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) shall include Content-ID header field value set to "cid" URL of the Refer-To header field of the SIP REFER request into the application/resource-lists MIME body part; and
d) may include an identity of adhoc group in <mcptt-request-uri> element with value set to the identity of the adhoc group in an application/vnd.3gpp.mcptt-info MIME body;
NOTE 2: The MCPTT client can optionally include an identity of adhoc group if it learns by any other means or generated by the MCPTT client using required parameters.
8) if the MCPTT user has requested to include the criteria for determining the list of MCPTT users to be called and the call setup request does not follow an adhoc group for emergency alert:
a) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an MIME body section which conatins one or more MIME bodies, and with the Content-ID header field set to this "cid" URL and Content-Type header filed set to "application/vnd.3gpp.mcptt-info+xml";
b) the Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
d) shall include Content-ID header field value set to "cid" URL of the Refer-To header field of the SIP REFER request into the application/resource-lists MIME body part;
e) may include an identity of adhoc group in <mcptt-request-uri> element with value set to the identity of the adhoc group in an application/vnd.3gpp.mcptt-info MIME body; and
NOTE 3: The MCPTT client can optionally include an identity of adhoc group if it learns by any other means or generated by the MCPTT client using required parameters.
f) shall include the <call-participants-criterias> element set to one or more criteria as a comma separated list in an application/vnd.3gpp.mcptt-info MIME body;
9) if the call setup request follows an emergency alert for an adhoc group:
a) shall set the Refer-To header field of the SIP REFER request as specified in IETF RFC 3515 [25] with a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20], and with the Content-ID header field set to this "cid" URL and Content-Type header filed set to "application/resource-lists+xml";
b) shall include in the application/resource-lists+xml MIME body a single <entry> element in a <list> element in the <resource-lists> element where the <entry> elment contains a "uri" attribute set to the identity of the adhoc group learned during an adhoc group emergency alert procedure, extended with hname "body" parameter in the headers portion of the SIP URI containing:
NOTE 4: Characters that are not formatted as ASCII characters are escaped in the following parameters in the headers portion of the SIP URI.
i) the Accept-Contact header field containing the g.3gpp.mcptt media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; and
ii) an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
c) shall include Content-ID header field value set to "cid" URL of the Refer-To header field of the SIP REFER request into the application/resource-lists MIME body part; and
d) shall include the <adhoc-grp-emg-alert-grp-ind> element set to "true" in an application/vnd.3gpp.mcptt-info MIME body;
NOTE 5: The MCPTT client can include either a list of MCPTT users or the criteria for determining the list of MCPTT users to be called. These two information elements are not included if the call setup request follows an adhoc group for emergency alerts.
10) if the MCPTT user has requested the origination of an MCPTT emergency adhoc group call or is originating an MCPTT adhoc group call and the MCPTT emergency state is already set, the MCPTT client shall comply with the procedures in clause 6.2.8.1.21;
11) if the MCPTT user has requested the origination of an MCPTT imminent peril adhoc group call, the MCPTT client shall comply with the procedures in clause 6.2.8.1.25;
12) shall contain in an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element with:
a) the <session-type> element set to a value of "adhoc";
b) the <mcptt-client-id> element set to the MCPTT client ID of the originating MCPTT client;
c) an <anyExt> element containing:
i) if the MCPTT client needs to include an active functional alias in the SIP REFER request, shall include the <functional-alias-URI> element set to the URI of the used functional alias;
NOTE 6: The MCPTT client learns the functional aliases that are activated for an MCPTT ID from procedures specified in clause 9A.2.1.3.
ii) if the MCPTT user has requested an application priority, the <user-requested-priority> element set to the user provided value;
iii) if end-to-end security needs to be established for the MCPTT adhoc group session, the <end-to-end-security> element set to "true";
13) if:
a) implicit floor control is requested; and
b) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
i) implicit floor control is requested; and
ii) if the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
14) shall include an application/sdp MIME body containing an SDP offer, if the session parameters of the pre-established session require modification or if implicit floor control is requested, according to the conditions specified in clause 6.4;
15) if several MIME bodies to be included in the request, shall include the MIME bodies according to the procedures specified in clause 6.5;
16) shall include a Target-Dialog header field as specified in IETF RFC 4538 [23] identifying the pre-established session;
17) shall include the g.3gpp.mcptt media feature tag and the g.3gpp.icsi-ref media feature tag with the value of "urn:urn-7:3gpp-service.ims.icsi.mcptt" in the Contact header field of the SIP REFER request according to IETF RFC 3840 [16]; and
18) shall send the SIP REFER request according to 3GPP TS 24.229 [4].
On receiving a final SIP 2xx response to the SIP REFER request, the MCPTT client:
1) shall interact with the user plane as specified in 3GPP TS 24.380 [5];
2) if the <preconfigured-group-id> element received in the application/vnd.3gpp.mcptt-info+xml MIME body, shall use the security related information from the group configuration associated with the received preconfigured group identity;
3) may notify the user with the adhoc group identity received in the <mcptt-calling-group-id> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body; and
4) when the MCPC Connect message to the MCPTT adhoc group session is acknowledged, and if not yet subscribed, may subscribe to the conference event package as specified in clause 10.1.3.1.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the SIP REFER request:
1) may notify the user about call setup failure with an appropriate response along with the description; and
2) if received response to a SIP request for a priority adhoc group call, shall perform the actions specified in clause 6.2.8.1.23.
On receiving a SIP re-INVITE request within the pre-established session targeted by the sent SIP REFER request, and if the sent SIP REFER request was a request for an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call, the MCPTT client:
1) shall perform the actions specified in clause 6.2.8.1.26;
2) shall check if a Resource-Priority header field is included in the incoming SIP re-INVITE request and may perform further actions outside the scope of this specification to act upon an included Resource-Priority header field as specified in 3GPP TS 24.229 [4];
3) shall accept the SIP re-INVITE request and generate a SIP 200 (OK) response according to rules and procedures of 3GPP TS 24.229 [4];
4) shall include an SDP answer in the SIP 200 (OK) response to the SDP offer in the incoming SIP re-INVITE request according to 3GPP TS 24.229 [4], based upon the parameters already negotiated for the pre-established session; and
5) shall send the SIP 200 (OK) response towards the participating MCPTT function according to rules and procedures of 3GPP TS 24.229 [4].
On call release by interaction with the media plane as specified in clause 9.2.2 of 3GPP TS 24.380 [5] if the sent SIP REFER request was a request for an MCPTT emergency adhoc group call or an MCPTT imminent peril adhoc group call, the MCPTT client shall perform the procedures specified in clause 6.2.8.1.27. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.2.2.2 Client terminating procedures | Upon receiving a SIP re-INVITE request within a pre-established Session without an associated MCPTT session or when generating SIP responses to the SIP re-INVITE request, the MCPTT client shall follow the procedures as specified in clause 17.2.2.1.2 with the clarification as below:
1) when the SIP 200 (OK) response to the SIP re-INVITE request is sent, the subsequent MCPC Connect message to the MCPTT adhoc group session is acknowledged, and if not yet subscribed, may subscribe to the conference event package as specified in clause 10.1.3.1.
NOTE: In clause 17.2.2.1.2, the reader is assumed to replace occurrences of SIP INVITE request with SIP re-INVITE request. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3 Adhoc group call release | This clause describes the originating, and terminating call release procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3.1 Call release procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3.1.1 Client originating procedures | Upon receiving a request from an MCPTT user to release an MCPTT adhoc group session established using on-demand session, the MCPTT client shall follow the procedures as specified in clause 6.2.5.1 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3.1.2 Client terminating procedures | Upon receiving a SIP BYE request for releasing the MCPTT adhoc group session, the MCPTT client shall follow the procedures as specified in clause 6.2.6 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3.2 Call release procedures using pre-established session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.3.2.1 Client originating procedures | Upon receiving a request from an MCPTT user to release an MCPTT adhoc group session established using pre-established session, the MCPTT client shall follow the procedures as specified in clause 6.2.5.2 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4 Adhoc group call leave | This clause describes the originating, and terminating call leave procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4.1 Call leave procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4.1.1 Client originating procedures | Upon receiving a request from an MCPTT user to leave an MCPTT adhoc group session established using on-demand session, the MCPTT client shall follow the procedures as specified in clause 6.2.4.1 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4.1.2 Client terminating procedures | Upon receiving a SIP BYE request for leave the MCPTT adhoc group session, the MCPTT client shall follow the procedures as specified in clause 6.2.6 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4.2 Call leave procedures using pre-established session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.4.2.1 Client originating procedures | Upon receiving a request from an MCPTT user to leave an MCPTT adhoc group session established using pre-established session, the MCPTT client shall follow the procedures as specified in clause 6.2.4.2 and clause 6.2.8.1.27 for the MCPTT adhoc group session either of the MCPTT emergency adhoc group call or the MCPTT imminent peril adhoc group call. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.5 Adhoc group call rejoin | This clause describes the originating, and terminating call rejoin procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.5.1 Call leave procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.5.1.1 Client originating procedures | Upon receiving a request from an MCPTT user to rejoin an ongoing MCPTT session or triggered by coming back from out of coverage, the MCPTT client shall generate an initial SIP INVITE request by following the UE originating session procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
NOTE: How an MCPTT client is informed whether it comes back from out of coverage is out of scope of present document.
The MCPTT client shall follow the procedures specified in clause 17.2.2.1.1 with the clarification in step 1) of clause 17.2.2.1.1 that the Request-URI of the SIP INVITE request shall contain a URI of the MCPTT session identity to rejoin. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.5.2 Call rejoin procedures using pre-established session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.5.2.1 Client originating procedures | Upon receiving a request from an MCPTT user to rejoin an ongoing MCPTT call within the pre-established session or triggered by coming back from out of coverage, the MCPTT client shall generate a SIP REFER request as specified in IETF RFC 3515 [25] as updated by IETF RFC 6665 [26] and IETF RFC 7647 [27], and in accordance with the UE procedures specified in 3GPP TS 24.229 [4], with the clarifications given below.
The MCPTT client shall follow the procedures specified in clause 17.2.2.2.1 with the clarification in step 7, step 8 and step 9 of clause 17.2.2.2.1 that the Refer-To header field of the SIP REFER request:
1) shall contain a URI of the MCPTT session identity to rejoin; and
2) shall contain a Content-Type header field in the headers portion of the SIP URI containing an application/vnd.3gpp.mcptt-info+xml MIME type of the hname "body" parameter in the headers portion of the SIP URI and the hname "body" parameter in the headers portion of the SIP URI containing the <mcpttinfo> element with the <mcptt-Params> element and with the <session-type> element set to a value of "adhoc". |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.6 Adhoc group call participants modify | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.6.0 General | This clause describes the originating ad hoc group call modification procedures in terms of (criteria for) the participant list. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.6.1 Modification of the participant list or criteria for the participant list procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.2.6.1.1 Client originating procedures | Upon receiving a request from an authorized MCPTT user to modify an ongoing MCPTT session to update the participant list or criteria for the participant list, the MCPTT client shall generate a SIP re-INVITE request as specified in 3GPP TS 24.229 [4]. and:
1) shall include an application/vnd.3gpp.mcptt-info+xml MIME body populated as currently established session;
2) if the authorized user requests to modify the participant list, shall insert in the SIP re-INVITE request an application/resource-lists+xml MIME body with:
a) if MCPTT users to be invited to a call, the MCPTT ID of the invited MCPTT users to be called with the "method" SIP URI parameter set to the value "INVITE" in the "uri" attribute of the each <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body; and
b) if MCPTT users to be removed from a call, the MCPTT ID of the MCPTT users to be removed with the "method" SIP URI parameter with the value "BYE" in the "uri" attribute of the each <entry> element of a <list> element of the <resource-lists> element of the application/resource-lists+xml MIME body;
2a) if the current session is established based on a request from the MCPTT user to include the criteria for determining the list of MCPTT users to be called and the authorized user requests to modify criteria for the participant list, shall insert a <call-participants-criterias> element with one or more criteria as a comma separated list into <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body;
NOTE: An MCPTT user can request to update either the participant list or criteria for the participant list of an ongoing MCPTT session. If an MCPTT user requests to update both the participant list and criteria for the participant list, the MCPTT client will reject the request. How the MCPTT client rejects the request is out of the scope of the current specification.
3) shall include an SDP offer with the media parameters as currently established according to 3GPP TS 24.229 [4]; and
4) shall send the SIP re-INVITE request according to 3GPP TS 24.229 [4].
On receiving a SIP 2xx response to the SIP re-INVITE request, the MCPTT client:
1) may notify the user about successful call modification request.
On receiving a SIP 4xx response, a SIP 5xx response or a SIP 6xx response to the re-SIP INVITE request, the MCPTT client:
1) may notify the user about call participants modify request failure with an appropriate response along with the description. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.3 Participating MCPTT function procedures | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.3.1 General | This clause describes the adhoc group call participating MCPTT function procedures using on-demand and pre-established sessions to setup adhoc group calls, release the ongoing adhoc group calls, and modify the ongoing adhoc group calls participants. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.3.2 Adhoc group call setup | This clause describes the originating, and terminating call setup participating MCPTT function procedures. |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.3.2.1 Call setup procedures using on-demand session | |
133fe75ad74e43ce3dae7fa700a45c85 | 24.379 | 17.3.2.1.1 Originating procedures | In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <adhoc-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.3gpp.mcptt-info+xml MIME body.
Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "adhoc", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Error) response. The participating MCPTT function may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
NOTE 1: if the SIP INVITE request contains an adhoc emergency indication or an adhoc imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.8, the participating MCPTT function can according to local policy choose to accept the request.
2) shall determine the MCPTT ID of the calling user from public user identity in the P-Asserted-Identity header field of the SIP INVITE request;
NOTE 2: The MCPTT ID of the calling user is bound to the public user identity at the time of service authorisation, as documented in clause 7.3.
3) if the participating MCPTT function cannot find a binding between the public user identity and an MCPTT ID or if the validity period of an existing binding has expired, then the participating MCPTT function shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text set to "141 user unknown to the participating function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
4) if through local policy in the participating MCPTT function, the user identified by the MCPTT ID is not authorised to initiate adhoc group calls, shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response to the SIP INVITE request, with warning text set to "184 user not authorised to make adhoc group calls" in a Warning header field as specified in clause 4.4;
5) shall validate the media parameters and if the MCPTT speech codec is not offered in the SIP INVITE request shall reject the request with a SIP 488 (Not Acceptable Here) response. Otherwise, continue with the rest of the steps;
6) shall check if the number of maximum simultaneous MCPTT group calls supported for the MCPTT user as specified in the <MaxSimultaneousCallsN6> element of the <MCPTT-group-call> element of the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) has been exceeded. If exceeded, the participating MCPTT function shall respond with a SIP 486 (Busy Here) response with the warning text set to "103 maximum simultaneous MCPTT group calls reached" in a Warning header field as specified in clause 4.4. Otherwise, continue with the rest of the steps;
NOTE 3: If the SIP INVITE request contains an adhoc emergency indication set to a value of "true" or an adhoc imminent peril indication set to a value of "true" and this is an authorised request for originating a priority call as determined by clause 6.3.2.1.8.8, the participating MCPTT function can according to local policy choose to allow for an exception to the limit for the maximum simultaneous MCPTT sessions supported for the MCPTT user.
7) shall determine the public service identity of the controlling MCPTT function for the adhoc group call service associated with:
a) the originating user's identity i.e. MCPTT ID, if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with a <call-participants-criterias> element or if the incoming SIP INVITE request contained an application/resource-lists+xml MIME body without the <adhoc-grp-emg-alert-grp-ind> element set to "true" in application/vnd.3gpp.mcptt-info+xml MIME body;
b) the adhoc group identity i.e. MCPTT Group ID, if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with the <adhoc-grp-emg-alert-grp-ind> element set to "true"; and
c) in case of rejoining an ongoing adhoc group call, the session identity of the ongoing adhoc group call;
NOTE 4: The public service identity can identify the controlling MCPTT function in the primary MCPTT system or in a partner MCPTT system.
NOTE 5: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the public service identity can identify the MCPTT gateway server that acts as an entry point in the partner MCPTT system from the primary MCPTT system.
NOTE 6: If the controlling MCPTT function is in a partner MCPTT system in a different trust domain, then the primary MCPTT system can route the SIP request through an MCPTT gateway server that acts as an exit point from the primary MCPTT system to the partner MCPTT system.
NOTE 7: How the participating MCPTT function determines the public service identity of the targeted controlling MCPTT function or of the MCPTT gateway server in the partner MCPTT system is out of the scope of the present document.
NOTE 8: How the primary MCPTT system routes the SIP request through an exit MCPTT gateway server is out of the scope of the present document.
NOTE 9: The controlling MCPTT function is always in the same system as the adhoc group call was initiated.
8) if the participating MCPTT function is unable to identify the controlling MCPTT function for the adhoc group call service associated with the originating user's MCPTT ID identity, it shall reject the SIP INVITE request with a SIP 404 (Not Found) response with the warning text "142 unable to determine the controlling function" in a Warning header field as specified in clause 4.4, and shall not continue with any of the remaining steps;
9) if the <allow-adhoc-group-call> element of the <ruleset> element is not present in the MCPTT user profile document on the participating MCPTT function or is present with the value "false" (see the MCPTT user profile document in 3GPP TS 24.484 [50]), indicating that the user identified by the MCPTT ID is not authorised to initiate adhoc group calls, shall reject the "SIP INVITE request for originating participating MCPTT function" with a SIP 403 (Forbidden) response, with warning text set to "185 user is not authorised to initiate the adhoc group call" in a Warning header field as specified in clause 4.4, and shall not continue with the rest of the steps;
9A) if received SIP INVITE request includes an application/vnd.3gpp.mcptt-info+xml MIME body with an <adhoc-emergency-ind> element included or an <imminentperil-ind> element included, shall validate the request as described in clause 6.3.2.1.8.9;
9B) if the SIP INVITE request contains in the application/vnd.3gpp.mcptt-info+xml MIME body:
a) an <adhoc-emergency-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT emergency adhoc group call as determined by clause 6.3.2.1.8.8;
b) an <imminentperil-ind> element set to a value of "true" and this is an unauthorised request for an MCPTT imminent peril adhoc group call as determined by clause 6.3.2.1.8.8;
then shall reject the SIP INVITE request with a SIP 403 (Forbidden) response and skip the rest of the steps;
10) shall generate a SIP INVITE request as specified in clause 6.3.2.1.3;
11) shall set the Request-URI to the public service identity of the controlling MCPTT function as determined in step 7;
12) shall not copy the following header fields from the incoming SIP INVITE request to the outgoing SIP INVITE request, if they were present in the incoming SIP INVITE request:
a) Answer-Mode header field as specified in IETF RFC 5373 [18]; and
b) Priv-Answer-Mode header field as specified in IETF RFC 5373 [18];
13) shall set the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the SIP INVITE request to the MCPTT ID of the calling user;
14) shall include in the SIP INVITE request an SDP offer based on the SDP offer in the received SIP INVITE request from the MCPTT client as specified in clause 6.3.2.1.1.1;
15) if the received SIP request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, then check if the status of the functional alias is activated for the MCPTT ID. If the functional alias status is activated, then set the <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request to the received value, if the status is not activated then do not include a <functional-alias-URI> element;
NOTE 10: The participating MCPTT server learns the functional alias state for an MCPTT ID from procedures specified in clause 9A.2.2.2.7.
16) if a Resource-Priority header field was included in the received SIP INVITE request, shall include a Resource-Priority header field according to rules and procedures of 3GPP TS 24.229 [4] set to the value indicated in the Resource-Priority header field of the SIP INVITE request from the MCPTT client;
NOTE 11: The participating MCPTT function will leave the verification of the Resource-Priority header field to the controlling MCPTT function.
17) if, according to clause 6.4, the SIP INVITE request is regarded as being received with an implicit request to grant the floor to the originating MCPTT client:
if:
a) the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall copy the application/vnd.3gpp.mcptt-location-info+xml MIME body from the received SIP INVITE request into the outgoing SIP INVITE request;
otherwise:
if:
a) the participating MCPTT function has the location of the originating MCPTT client available; and
b) the <allow-location-info-when-talking> element of the <ruleset> element of the MCPTT user profile document identified by the MCPTT ID of the calling MCPTT user (see the MCPTT user profile document in 3GPP TS 24.484 [50]) is set to a value of "true";
then shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
17A) if the incoming SIP INVITE request contained an application/vnd.3gpp.mcptt-info+xml MIME body with the <mcpttinfo> element containing the <mcptt-Params> element containing the <anyExt> element with a <call-participants-criterias> element, may modify based on local policy the content of the <call-participants-criterias> element of the <anyExt> element of <mcptt-Params> element of <mcpttinfo> element of the application/vnd.3gpp.mcptt-info+xml MIME body in the outgoing SIP INVITE request; and
18) shall forward the SIP INVITE request, according to 3GPP TS 24.229 [4].
Upon receipt of a SIP 2xx response in response to the above SIP INVITE request, the participating MCPTT function:
1) shall generate a SIP 200 (OK) response as in clause 6.3.2.1.5.2 with the clarification that if an <MKFC-GKTPs> element was contained in the received SIP 2xx response it is not included in the generated SIP 200 (OK) response;
NOTE 12: If an <MKFC-GKTPs> element is received in a SIP 2xx response, the participating MCPTT function essentially ignores it and does not forward it, resulting in unicast media plane transmission being used for the originating client.
2) shall include in the SIP 200 (OK) response an SDP answer as specified in the clause 6.3.2.1.2.1;
3) shall include Warning header field(s) that were received in the incoming SIP 200 (OK) response;
4) shall include a P-Asserted-Identity header field in the outgoing SIP 200 (OK) response set to the public service identity of the participating MCPTT function;
5) shall include an MCPTT session identity mapped to the MCPTT session identity provided in the Contact header field of the received SIP 200 (OK) response;
6) shall include the answer state into the P-Answer-State header field of the outgoing SIP 200 (OK) response, if received in the P-Answer-State header field of the incoming SIP 200 (OK) response;
7) shall send the SIP 200 (OK) response to the MCPTT client according to 3GPP TS 24.229 [4];
8) shall interact with Media Plane as specified in 3GPP TS 24.380 [5]; and
10) shall start the SIP Session timer according to rules and procedures of IETF RFC 4028 [7].
Upon receipt of a SIP 4xx, 5xx or 6xx response to the above SIP INVITE request, the participating MCPTT function:
1) shall generate a SIP response according to 3GPP TS 24.229 [4];
2) shall include Warning header field(s) that were received in the incoming SIP response; and
3) shall forward the SIP response to the MCPTT client according to 3GPP TS 24.229 [4]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.