hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.19 GROUP EMERGENCY ALERT CANCEL ACK message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.19.1 Message definition
| This message is sent by the UE to other UEs to indicate receipt of emergency alert cancel. For contents of the message see Table 15.1.19.1-1.
Message type: GROUP EMERGENCY ALERT CANCEL ACK
Direction: UE to other UEs
Table 15.1.19.1-1: GROUP EMERGENCY ALERT CANCEL ACK message content
IEI
Information Element
Type/R... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.20 GROUP CALL BROADCAST message
| |
603c77cd0da93e5e476a024643c0ef1c | 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
Fo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.21 GROUP CALL BROADCAST END message
| |
603c77cd0da93e5e476a024643c0ef1c | 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
Pr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.22 MCVIDEO MESSAGE CARRIER message
| |
603c77cd0da93e5e476a024643c0ef1c | 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 CARR... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.23 MCDATA MESSAGE CARRIER message
| |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.2 General message format and information elements coding
| |
603c77cd0da93e5e476a024643c0ef1c | 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 significa... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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... |
603c77cd0da93e5e476a024643c0ef1c | 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 oc... |
603c77cd0da93e5e476a024643c0ef1c | 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 ... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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.... |
603c77cd0da93e5e476a024643c0ef1c | 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
oc... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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
octe... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 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... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16 Regroup using a preconfigured group
| |
603c77cd0da93e5e476a024643c0ef1c | 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 S... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.2 Group regroup using a preconfigured group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.2.1 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 ... |
603c77cd0da93e5e476a024643c0ef1c | 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;... |
603c77cd0da93e5e476a024643c0ef1c | 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)... |
603c77cd0da93e5e476a024643c0ef1c | 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
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.2.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 S... |
603c77cd0da93e5e476a024643c0ef1c | 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 MESSA... |
603c77cd0da93e5e476a024643c0ef1c | 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 t... |
603c77cd0da93e5e476a024643c0ef1c | 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 wit... |
603c77cd0da93e5e476a024643c0ef1c | 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 SI... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.2.3 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 (Ser... |
603c77cd0da93e5e476a024643c0ef1c | 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)... |
603c77cd0da93e5e476a024643c0ef1c | 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 tha... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.2.4 Non-controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 50... |
603c77cd0da93e5e476a024643c0ef1c | 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 I... |
603c77cd0da93e5e476a024643c0ef1c | 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 ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.3 User regroup using a preconfigured group
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.3.1 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 t... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.3.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 S... |
603c77cd0da93e5e476a024643c0ef1c | 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 MESSAG... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 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... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 16.3.3 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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 (Serv... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17 Adhoc group call
| |
603c77cd0da93e5e476a024643c0ef1c | 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 s... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.2 Adhoc group call setup
| This clause describes the originating, and terminating call setup procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.2.1 Call setup procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 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-suppo... |
603c77cd0da93e5e476a024643c0ef1c | 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/... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.2.2 Call setup procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 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 contai... |
603c77cd0da93e5e476a024643c0ef1c | 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... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.3 Adhoc group call release
| This clause describes the originating, and terminating call release procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.3.1 Call release procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.3.1.1 Client originating procedures
| Upon receiving a request from an MCPTT user to release an MCPTT ad hoc 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 ad hoc group session either of the MCPTT emergency ad hoc group call or the MCPTT immi... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.3.2 Call release procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.3.2.1 Client originating procedures
| Upon receiving a request from an MCPTT user to release an MCPTT ad hoc 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 ad hoc group session either of the MCPTT emergency ad hoc group call or the MCPT... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.4 Adhoc group call leave
| This clause describes the originating, and terminating call leave procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.4.1 Call leave procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 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 ... |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.4.2 Call leave procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 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 imm... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.5 Adhoc group call rejoin
| This clause describes the originating, and terminating call rejoin procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.5.1 Call rejoin procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 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: H... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.5.2 Call rejoin procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 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 accordan... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.6 Adhoc group call participants modify
| |
603c77cd0da93e5e476a024643c0ef1c | 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.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.6.1 Modification of the participant list or criteria for the participant list procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 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 bo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.7 Ad hoc group call notifications
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.2.7.1 Receiving notification of ad hoc group call redirection
| Upon receiving a "SIP MESSAGE request with notification of ad hoc group call redirection", the MCPTT client:
1) should notify the MCPTT user of the ad hoc group call redirection; and
2) shall send a 200 (OK) response to the MCPTT server according to 3GPP TS 24.229 [4].
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3 Participating MCPTT function procedures
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.