Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.18…   10.6.2.2.34…   10.6.2.3…   10.6.2.3.2…   10.6.2.4…   10.6.2.5…   10.6.2.6…   10.6.2.7…   10.6.2.9…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.6…   10.9…   10.9.1.3…   10.9.2…   10.10…   10.14…   A…   A.4…   B…

 

10.7.2.3  Private call within several MCPTT systems

10.7.2.3.1  Private call setup in automatic commencement mode - MCPTT users in multiple MCPTT systems
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled.
Procedures in Figure 10.7.2.3.1-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user.
Pre-conditions:
  1. The calling MCPTT user has selected automatic commencement mode for the call; or
  2. The called MCPTT client is set to automatic commencement mode.
(not reproduced yet)
Figure 10.7.2.3.1-1: Private call setup in automatic commencement mode - users in multiple MCPTT systems
Up
Step 1.
It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2.
Step 2.
MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. For a private call with floor control, floor control is to be established.
Step 3.
MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core) using a service identifier as defined in TS 23.228 for MCPTT, for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. The MCPTT private call request contains the MCPTT id of invited user and an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. If the private call request request the floor it may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user.
Step 4.
MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in automatic commencement mode.
Step 5.
MCPTT server 1 may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
Step 6.
If authorized, MCPTT server 1 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes an automatic commencement mode indication if automatic commencement mode was requested by and authorised for the calling user and sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
Step 7.
MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call.
Step 8.
MCPTT server 2 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes a requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the received MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
Step 9.
The receiving MCPTT client 2 notifies the user about the incoming private call.
Step 10.
The receiving MCPTT client 2 accepts the private call automatically, and an acknowledgement is sent to the MCPTT server 1 (via SIP core and MCPTT server 2).
Step 11.
Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment.
Step 12.
MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken.
Up
10.7.2.3.2  Private call setup in manual commencement mode - MCPTT users in multiple MCPTT systemsWord‑p. 139
The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled.
Procedures in Figure 10.7.2.3.2-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the selected MCPTT user.
Pre-conditions:
  1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and
  2. The called MCPTT client is set to manual commencement mode.
(not reproduced yet)
Figure 10.7.2.3.2-1: Private call setup in manual commencement mode - users in multiple MCPTT systems
Up
Step 1.
It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2.
Step 2.
MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. For a private call with floor control, floor control is to be established.
Step 3.
MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core), for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. For a private call with floor control, the MCPTT private call request contains an element that indicates that MCPTT client 1 is requesting the floor. If the call request requests the floor the call request may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user.
Step 4.
MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. The MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode.
Step 5.
If authorized, MCPTT server 1 sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
Step 6.
MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process.
Step 7.
The MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call and also checks the commencement mode setting of MCPTT client 2.
Step 8.
The MCPTT server 2 offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE.
Step 9.
The MCPTT user is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server 1 (via server 2).
Step 10.
The MCPTT server 1 sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted.
Step 11.
MCPTT user 2 has accepted the call using manual commencement mode (i.e. has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server 1 (via SIP core and MCPTT server 2)
Step 12.
Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment.
Step 13.
MCPTT client 1 and client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted the floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken.
Up
10.7.2.3.3  Private call release - MCPTT users in multiple MCPTT systemsWord‑p. 141
The procedure in this subclause is for the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) established in either of the two commencement modes (manual or automatic), and the MCPTT users are in multiple MCPTT systems.
Procedures are similar to those described for private call release when MCPTT users are in single MCPTT system as in subclause 10.7.2.2.3.1, with the addition that the MCPTT call end request and the corresponding acknowledgement are routed through the MCPTT server in partner MCPTT system.
Up

10.7.2.4  MCPTT emergency private call

10.7.2.4.1  MCPTT emergency private call commencement
This procedure focuses on the case where an authorized MCPTT user is initiating an MCPTT emergency private call with unicast signalling for communicating with another MCPTT user. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications.
Procedures in Figure 10.7.2.4.1-1 are the procedures for the MCPTT client initiating establishment of an MCPTT emergency private call.
Pre-conditions:
  1. Both members of the MCPTT private call belong to the same MCPTT system.
  2. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert prior to initiating an MCPTT emergency private call.
  3. Optionally, MCPTT client 1 may use an activated functional alias for the call.
  4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
(not reproduced yet)
Figure 10.7.2.4.1-1: MCPTT emergency private call
Up
Step 1.
The user at the MCPTT client 1 initiates an MCPTT emergency private call. MCPTT client 1 sets its MCPTT emergency state. MCPTT client 1 retains the MCPTT emergency state until explicitly cancelled by the user of MCPTT client 1.
Step 2.
MCPTT client 1 sends an MCPTT emergency private call request towards the MCPTT server. The request contains an indication of the MCPTT emergency. MCPTT user at MCPTT client 1 may select a functional alias as calling party address and the MCPTT server verifies whether the provided functional alias can be used. Instead of an MCPTT ID the MCPTT user at MCPTT client 1 may also select a functional alias as called party address, which the MCPTT server replaces by an appropriate MCPTT ID. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency private call until the MCPTT emergency is cancelled. If the MCPTT client is configured to send an MCPTT emergency alert when initiating an MCPTT emergency private call, the request also contains an indication that an MCPTT emergency alert is to be initiated.
Step 3.
MCPTT server sends the MCPTT emergency private call request towards the target MCPTT client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert.
Step 4.
The MCPTT user on MCPTT client 2 is notified of the incoming MCPTT emergency private call and may display the functional alias of MCPTT client 1.
Step 5.
The receiving MCPTT client acknowledges the MCPTT emergency private call request to the MCPTT server.
Step 6.
The MCPTT server adjusts the priority of the underlying bearer.
Step 7.
The MCPTT server informs MCPTT client 1 about the successful MCPTT emergency private call establishment.
Step 8.
MCPTT client 1 and MCPTT client 2 establish the media plane for communication. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state.
Up
10.7.2.4.2  MCPTT private call emergency upgradeWord‑p. 143
This procedure describes the case where an authorized MCPTT user is upgrading a private call to an MCPTT emergency private call while the private call is already in progress.
Procedures in Figure 10.7.2.4.2-1 are the signalling procedures for the MCPTT client upgrading a private call to an MCPTT emergency private call.
Pre-conditions:
  1. Both members of the private call belong to the same MCPTT system.
  2. A private call is already in progress.
(not reproduced yet)
Figure 10.7.2.4.2-1: MCPTT private call upgrade
Up
Step 1.
The MCPTT user at MCPTT client 1 initiates an emergency. MCPTT client 1 sets its MCPTT emergency state. MCPTT client 1 retains the MCPTT emergency state until explicitly cancelled by the user of MCPTT client 1.
Step 2.
MCPTT client 1 requests the MCPTT server to upgrade the private call to in-progress emergency by sending an MCPTT emergency request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. If the emergency private call request includes an implicit floor reques it may also include location information.
Step 3.
The MCPTT server sends the MCPTT emergency request towards MCPTT client 2, the MCPTT client of the other participant. If location information was included in the emergency private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking").
Step 4.
The MCPTT user of MCPTT client 2 is notified of the in-progress emergency of the MCPTT emergency private call.
Step 5.
The receiving MCPTT client acknowledges the MCPTT emergency request to the MCPTT server.
Step 6.
The MCPTT server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends.
Step 7.
The MCPTT server confirms the upgrade request to MCPTT client 1.
Step 8.
MCPTT client 1 and MCPTT client 2 continue with the private call, which has been transformed into an MCPTT emergency private call. MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state.
Up

Up   Top   ToC