hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.1.3.1 Handling of a SIP MESSAGE request for emergency notification
| Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function", 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 contr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.1.3.2 Handling of a SIP MESSAGE request for emergency alert cancellation
| Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <alert-ind> element set to a value of "false", the controlling MCPTT function:
1) if the received SIP MESSAGE request is an unauthorised request for an ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.1.3.3 Handling of a SIP MESSAGE request for in-progress emergency group state cancellation
| Upon receipt of a "SIP MESSAGE request for emergency notification for controlling MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <emergency-ind> element set to a value of "false" and no call is ongoing on the group on which in-progress emergency cancellation request is made, the co... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.1.3.4 Late emergency alert initiated by controlling MCPTT function
| When controlling MCPTT function is notified that an MCPTT client is newly affiliated or comes back from out of coverage, the controlling MCPTT function:
NOTE: How the MCPTT function is informed when an MCPTT client is coming back from out of coverage is out of scope of present document.
1) if there is an outstanding ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2 Off-network emergency alert
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.1 General
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2 Basic state machine
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2.1 General
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2.2 Emergency alert state machine
| The figure 12.2.2.2-1 gives an overview of the main states and transitions on the UE for emergency alert.
Each emergency alert state machine is per MCPTT group.
Figure 12.2.2.2-1: Emergency alert state machine
The following pieces of information are associated with the emergency alert state machine:
a) the stored... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2.3 Emergency alert states
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2.3.1 E1: Not in emergency state
| This state is the start state of this state machine.
The UE stays in this state while not in emergency state.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.2.3.2 E2: Emergency state
| This state exists for UE, when the UE has sent a GROUP EMERGENCY ALERT message.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3 Procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.1 Originating user sending emergency alert
| When in state "E1: Not in emergency state", upon receiving an indication from the MCPTT user to transmit an emergency alert for an MCPTT group ID, and the values of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Authorised" leaf node present in the user profile and "/<x>/<x>/Common/AllowedEmergencyAlert" present in gro... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.2 Emergency alert retransmission
| When in state "E2: Emergency state", upon expiry of timer TFE2 (emergency alert retransmission), the MCPTT client:
1) shall generate a GROUP EMERGENCY ALERT message as specified in clause 15.1.16. In the GROUP EMERGENCY ALERT message, the MCPTT client:
a) shall set the MCPTT group ID IE to the stored MCPTT group ID;
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.3 Terminating user receiving emergency alert
| When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE not stored in the list of users in emergency, the MCPTT client:
1) shall store the Originating MCPTT user ID IE and location IE in the list of users in emergency;... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.4 Terminating user receiving retransmitted emergency alert
| When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:
1) may update the stored location of the user with the received Location IE;
2) shall restart the ass... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.5 Originating user cancels emergency alert
| When in "E2: Emergency state", upon receiving an indication from the MCPTT user to cancel an emergency alert and the value of "/<x>/<x>/Common/MCPTTGroupCall/EmergencyAlert/Cancel" leaf node present in the user profile as specified in 3GPP TS 24.483 [45] set to "true", the MCPTT client:
1) shall set the stored emergen... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.6 Terminating user receives GROUP EMERGENCY ALERT CANCEL message
| When in state "E1: Not in emergency state" or in "E2: Emergency state", upon receiving a GROUP EMERGENCY ALERT CANCEL message with the Originating MCPTT user ID IE stored in the list of users in emergency, the MCPTT client:
1) shall remove the MCPTT user ID and associated location information from the stored list of u... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 12.2.3.7 Implicit emergency alert cancel
| When in state "E1: Not in emergency state" or in "E2: Emergency state", upon expiry of timer TFE1 (emergency alert) associated with a stored MCPTT user ID, the MCPTT client:
1) shall remove the MCPTT user ID and associated location information from the stored list of users in emergency; and
2) shall remain in the cur... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13 Location procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.1 General
| If the participating MCPTT function needs to obtain location information, the participating MCPTT function configures the MCPTT client upon successful service authorization. The configuration contains information the MCPTT client uses to set up filter criteria for when the MCPTT client shall send location reports to th... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2 Participating MCPTT function location procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.1 General
| The participating MCPTT function has procedures to:
- configure the location reporting at the UE;
- request the UE to report the location of the UE; and
- receive a location information report from the UE.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.2 Location reporting configuration
| The participating MCPTT function may configure the location reporting in the MCPTT client by generating a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function:
1) shall include a Request-URI set to the public user identity corresponding to the identity of t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.3 Location information request
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.3.1 Location information request to MCPTT client
| If the participating MCPTT function needs to request the MCPTT client to report its location, the participating MCPTT functions shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33]. The participating MCPTT function:
1) shall include a Request-URI set to the URI correspondin... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.3.2 Location information request from authorized MCPTT client
| Upon receiving a SIP MESSAGE containing a location information request from an MCPTT client, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, may includ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.3.3 Location information request from another MCPTT server
| Upon receiving a SIP MESSAGE containing a location information request from an another MCPTT server, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or if a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response, ma... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.4 Location information report
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.4.1 Location information report from an MCPTT client
| If the participating MCPTT function receives a SIP request containing:
1) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
2) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element included in the <location-info> root element;
then the participating MC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.4.2 Location information report from another MCPTT server
| If the participating function receives a location information report from another server containing:
1) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
2) an application/vnd.3gpp.mcptt-location-info+xml MIME body with a <Report> element including a <ReportID> attribute and a <mc... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.2.5 Abnormal cases
| Upon receipt of a SIP request:
1) where the P-Asserted-Identity identifies a public user identity not associated with an MCPTT user served by the participating MCPTT function; or
2) with a MIME body with Content-Type header field set to "application/vnd.3gpp.mcptt-info+xml" and with a <mcptt-request-URI> element cont... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3 MCPTT client location procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.1 General
| The MCPTT client sends a location report when one of the trigger criteria is fulfilled or when it receives a request from the participating MCPTT function to send a location report. To send the location report the MCPTT client can use an appropriate SIP message that it needs to send for other reasons, or it can include... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.2 Location reporting configuration
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.2.1 MCPTT client receiving location reporting configuration
| Upon receiving a SIP MESSAGE request containing:
1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
3) an application/vnd.3gpp.mcptt-location-i... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.2.2 Authorized MCPTT client sending location reporting configuration
| To request replacement or modification of the location reporting configuration for one or several MCPTT clients, an authorized MC user’s MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33], as follows:
1) shall include the ICSI value "urn:urn-7:3gpp-service.im... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.3 Location information request
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.3.1 Location information request to MCPTT client
| Upon receiving a SIP MESSAGE request containing
1) an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref set to the value "urn:urn-7:3gpp-service.ims.icsi.mcptt";
2) a Content-Type header field set to "application/vnd.3gpp.mcptt-location-info+xml"; and
3) an application/vnd.3gpp.mcptt-location-in... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.3.2 Location information request from authorized MCPTT client
| If a MC user needs to request the location information for one or several MCPTT clients, the MCPTT client shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33].
1) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcptt" (coded as specified in 3GPP TS 24.229 [4])... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.4 Location information report
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.4.1 Report triggering
| If a location reporting trigger fires the MCPTT client checks if the minimumReportInterval timer is running. If the timer is running the MCPTT client waits until the timer expires. When the minimumReportInterval timer fires, the MCPTT client:
1) shall, if any of the reporting triggers are still true, send a location i... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 13.3.4.2 Sending location information report
| If the MCPTT client needs to send a SIP request for other reasons (e.g. a SIP MESSAGE request containing an MBMS listening report as described in clause 14), the MCPTT client:
1) shall include an application/vnd.3gpp.mcptt-location-info+xml MIME body and in the <location-info> root element the MCPTT client shall inclu... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14 MBMS transmission usage procedure
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.1 General
| This clause describes the participating MCPTT function and the MCPTT client procedure for:
1) MBMS bearer announcements;
2) MBMS bearer listening status; and
3) MBMS bearer suspension status.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2 Participating MCPTT function MBMS usage procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.1 General
| This clause describes the procedures in the participating MCPTT function for:
1) sending an MBMS bearer announcements to the MCPTT client;
2) receiving an MBMS bearer listening status from the MCPTT client; and
3) receiving an MBMS bearer suspension status from the MCPTT client.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2 Sending MBMS bearer announcement procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2.1 General
| The availability of a MBMS bearer is announced to MCPTT clients by means of an MBMS bearer announcement message. One or more MBMS bearer announcement elements are included in an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body.
An MBMS bearer announcement message can contain new MBMS bearer announcements, upda... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2.2 Sending an initial MBMS bearer announcement procedure
| For each MCPTT client that the participating MCPTT function is sending an MBMS bearer announcement to, the participating MCPTT function:
1) shall generate an SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
2) shall set the Request-URI to the URI received in the To header field in a t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2.3 Updating an announcement
| When the participating MCPTT function wants to update a previously sent announcement, the participating MCPTT function sends an MBMS bearer announcement in an SIP MESSAGE request as specified in clause 14.2.2.2 where the participating MCPTT function in the <announcement> element to be updated:
1) shall include the sam... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2.4 Cancelling an MBMS bearer announcement
| When the participating MCPTT function wants to cancel an MBMS bearer announcement associated with an <announcement> element, the participating MCPTT function sends an MBMS bearer announcement as specified in clause 14.2.2.2 where the participating MCPTT function in the <announcement> element to be cancelled:
1) shall ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.2.5 Sending a MuSiK download message
| For each MCPTT client that the participating MCPTT function is intending to use an MBMS bearer to transmit confidentiality protected floor control signalling (SRTCP) to the client, the participating MCPTT function shall perform a key download procedure for each Multicast Signalling Key (MuSiK). Two kinds of MuSiK downl... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.3 Receiving an MBMS bearer listening status from an MCPTT client
| Upon receiving a "SIP MESSAGE request for an MBMS listening status update", the participating MCPTT function shall handle the request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33].
If the SIP MESSAGE request contains:
1) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body with an <mbms-listenin... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.2.4 Abnormal cases
| Upon receipt of a SIP MESSAGE request with an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body:
1) where the P-Asserted-Identity identifies a public user identity not associated with MCPTT user served by the participating MCPTT function; or
2) with an application/vnd.3gpp.mcptt-info+xml MIME body and with a <... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3 MCPTT client MBMS usage procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.1 General
| This clause describes the procedures in the MCPTT client for:
1) receiving an MBMS bearer announcement from the participating MCPTT function;
2) sending an MBMS bearer listening status report to the participating MCPTT function; and
3) sending an MBMS bearer suspension status report to the participating MCPTT functi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.2 Receiving an MBMS bearer announcement
| The MCPTT client associates each received application/sdp MIME body and each received security key with a general purpose MBMS subchannel announced in the same MBMS Bearer Announcement message. When receiving a Map Group To Bearer message, the MCPTT client interprets its content (e.g. the m= line number) in the context... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.3 The MBMS bearer listening status and suspension report procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.3.1 Conditions for sending an MBMS listening status report
| If one of the following conditions is fulfilled:
1) if the MCPTT client:
a) receives a Map Group To Bearer message over the general purpose MBMS channel;
b) participates in a group session identified by the Map Group To Bearer message; and
c) the status "listening" is not already reported; or
2) if the MCPTT clien... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.3.2 Sending the MBMS bearer listening or suspension status report
| When the MCPTT client wants to report the MBMS bearer listening status, the MCPTT client:
NOTE 1: The application/vnd.3gpp.mcptt-mbms-usage-info+xml can contain both the listening status "listening" and "not listening" at the same time.
1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 14.3.4 Receiving a MuSiK download message
| When the MCPTT client receives a SIP MESSAGE request containing:
1) a P-Asserted-Service header field containing the "urn:urn-7:3gpp-service.ims.icsi.mcptt"; and
2) with one of the following:
a) an application/vnd.3gpp.mcptt-mbms-usage-info+xml MIME body containing an <mbms-explicitMuSiK-download> element with at le... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15 Off-network message formats
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1 MONP message functional definitions and contents
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.1 General
| The following clauses describe the MONP message functional definitions and contents. Each message consist of a series of information elements. Annex I describes the standard format of a MONP message and the encoding rules for each type of information element.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.2 GROUP CALL PROBE message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.2.1 Message definition
| This message is sent by the UE to other UEs to check for an ongoing group call. For contents of the message see Table 15.1.2.1-1.
Message type: GROUP CALL PROBE
Direction: UE to other UEs
Table 15.1.2.1-1: GROUP CALL PROBE message content
IEI
Information Element
Type/Reference
Presence
Format
Length
Group c... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.3 GROUP CALL ANNOUNCEMENT message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.3.1 Message definition
| This message is sent by the UE to other UEs to announce an ongoing group call to other UEs. For contents of the message see Table 15.1.3.1-1.
Message type: GROUP CALL ANNOUNCEMENT
Direction: UE to other UEs
Table 15.1.3.1-1: GROUP CALL ANNOUNCEMENT message content
IEI
Information Element
Type/Reference
Presence
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.4 GROUP CALL ACCEPT message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.4.1 Message definition
| This message is sent by the UE to other UEs to indicate acceptance of a group call. For contents of the message see Table 15.1.4.1-1.
Message type: GROUP CALL ACCEPT
Direction: UE to other UEs
Table 15.1.4.1-1: GROUP CALL ACCEPT message content
IEI
Information Element
Type/Reference
Presence
Format
Length
G... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.5 PRIVATE CALL SETUP REQUEST message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.5.1 Message definition
| This message is sent by a UE to another UE to request setup of a private call. For contents of the message see Table 15.1.5.1-1.
Message type: PRIVATE CALL SETUP REQUEST
Direction: UE to another UE
Table 15.1.5.1-1: PRIVATE CALL SETUP REQUEST message content
IEI
Information Element
Type/Reference
Presence
Forma... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.6 PRIVATE CALL RINGING message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.6.1 Message definition
| This message is automatically sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message. This message indicates that the UE has presented the incoming call notification to the user and is awaiting user response. For contents of the message see Table 15.1.6.1-1.
Message type: PRIVATE CALL RINGING
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.7 PRIVATE CALL ACCEPT message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.7.1 Message definition
| This message is sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message when user accepts the call. This message indicates that the UE accepts the call setup request. For contents of the message see Table 15.1.7.1-1.
Message type: PRIVATE CALL ACCEPT
Direction: UE to another UE
Table 15.1.7.1-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.8 PRIVATE CALL REJECT message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.8.1 Message definition
| This message is sent by a UE to another UE in response to a PRIVATE CALL SETUP REQUEST message when user rejects the call. This message indicates that the UE rejects the call setup request. For contents of the message see Table 15.1.8.1-1.
Message type: PRIVATE CALL REJECT
Direction: UE to another UE
Table 15.1.8.1-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.9 PRIVATE CALL RELEASE message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.9.1 Message definition
| This message is sent by a UE to another UE to terminate an ongoing private call. For contents of the message see Table 15.1.9.1-1.
Message type: PRIVATE CALL RELEASE
Direction: UE to another UE
Table 15.1.9.1-1: PRIVATE CALL RELEASE message content
IEI
Information Element
Type/Reference
Presence
Format
Length
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.10 PRIVATE CALL RELEASE ACK message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.10.1 Message definition
| This message is sent by a UE to another UE in response to a PRIVATE CALL RELEASE message. This message indicates that the UE has terminated the call. For contents of the message see Table 15.1.10.1-1.
Message type: PRIVATE CALL RELEASE ACK
Direction: UE to another UE
Table 15.1.10.1-1: PRIVATE CALL RELEASE ACK messa... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.11 PRIVATE CALL ACCEPT ACK message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.11.1 Message definition
| This message is sent by a UE to another UE in response to a PRIVATE CALL ACCEPT message. This message acknowledges the receipt of PRIVATE CALL ACCEPT message. For contents of the message see Table 15.1.11.1-1.
Message type: PRIVATE CALL ACCEPT ACK
Direction: UE to another UE
Table 15.1.11.1-1: PRIVATE CALL ACCEPT AC... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.12 PRIVATE CALL EMERGENCY CANCEL message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.12.1 Message definition
| This message is sent by a UE to another UE to indicate termination of emergency mode in private call. For contents of the message see Table 15.1.12.1-1.
Message type: PRIVATE CALL EMERGENCY CANCEL
Direction: UE to another UE
Table 15.1.12.1-1: PRIVATE CALL EMERGENCY CANCEL message content
IEI
Information Element
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.13 PRIVATE CALL EMERGENCY CANCEL ACK message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.13.1 Message definition
| This message is sent by a UE to another UE to indicate receipt of PRIVATE CALL EMERGENCY CANCEL message. For contents of the message see Table 15.1.13.1-1.
Message type: PRIVATE CALL EMERGENCY CANCEL ACK
Direction: UE to another UE
Table 15.1.13.1-1: PRIVATE CALL EMERGENCY CANCEL ACK message content
IEI
Informatio... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.14 GROUP CALL IMMINENT PERIL END message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.14.1 Message definition
| This message is sent by the UE to other UEs to indicate termination of imminent peril mode in the group call. For contents of the message see Table 15.1.14.1-1.
Message type: GROUP CALL IMMINENT PERIL END
Direction: UE to other UEs
Table 15.1.14.1-1: GROUP CALL IMMINENT PERIL END message content
IEI
Information El... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.15 GROUP CALL EMERGENCY END message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.15.1 Message definition
| This message is sent by the UE to other UEs to indicate termination of emergency mode in the group call. For contents of the message see Table 15.1.15.1-1.
Message type: GROUP CALL EMERGENCY END
Direction: UE to other UEs
Table 15.1.15.1-1: GROUP CALL EMERGENCY END message content
IEI
Information Element
Type/Ref... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.16 GROUP EMERGENCY ALERT message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.16.1 Message definition
| This message is sent by the UE to other UEs to indicate an emergency situation. For contents of the message see Table 15.1.16.1-1.
Message type: GROUP EMERGENCY ALERT
Direction: UE to other UEs
Table 15.1.16.1-1: GROUP EMERGENCY ALERT message content
IEI
Information Element
Type/Reference
Presence
Format
Lengt... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.17 GROUP EMERGENCY ALERT ACK message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.17.1 Message definition
| This message is sent by the UE to other UEs to indicate receipt of emergency alert. For contents of the message see Table 15.1.17.1-1.
Message type: GROUP EMERGENCY ALERT ACK
Direction: UE to other UEs
Table 15.1.17.1-1: GROUP EMERGENCY ALERT ACK message content
IEI
Information Element
Type/Reference
Presence
F... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.18 GROUP EMERGENCY ALERT CANCEL message
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 15.1.18.1 Message definition
| This message is sent by the UE to other UEs to indicate end of emergency situation. For contents of the message see Table 15.1.18.1-1.
Message type: GROUP EMERGENCY ALERT CANCEL
Direction: UE to other UEs
Table 15.1.18.1-1: GROUP EMERGENCY ALERT CANCEL message content
IEI
Information Element
Type/Reference
Prese... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.