hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.3 IWF GSM-R IWF ad-hoc group call response | Table 7.1.1.1.3-1 contains the GSM-R IWF group call response information flow. Table 7.1.1.1.3-1: GSM-R IWF group call response Information Element Status Description Connected Address O P-Asserted-Identity, as defined in clause 6.3.3.5. This information element can hold an E.164 SIP-R URI or an EIR+ENE SIP-R URI, as defined in ETSI TS 103 389 [6] User to User Information O This information element may contain user to user information, e.g. a called GSM-R functional number for the PFN service (see clause 6). This information element is specified in ETSI TS 103 389 [6]. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.2 Stage 3 Information flows | For IWF GSM-R group call requests the following shall apply: • For calls from GSM-R to FRMCS: GSM-R VGCS/VBS including a terminating dispatcher representing a group on the FRMCS domain (e.g. CT5 FN) - referenced as terminating dispatcher in the GCR - parameters shall be mapped as follows: - E.164 calling party in PAI (ETSI TS 129 163 [12]); - CT5 FN in From Header (ETSI TS 103 389 [6]); - calling OTDI in User-To-User hdr (ETSI TS 103 389 [6]). • For calls from FRMCS to GSM-R: FRMCS adhoc group call including an MCPTT user representing the GSM-R group (CT5 VGCS/VBS) as terminating user, parameters shall be mapped as follows: - E.164 calling party in PAI (ETSI TS 129 163 [12]); - CT5 FN in From Header (ETSI TS 103 389 [6]); - calling OTDI in User-To-User hdr (ETSI TS 103 389 [6]). • From the point of view of the SIP trunk between the IWF and the MGCF, the connection between the MCPTT group call and the GSM-R group call shall be performed as a point-to-point call with two-way audio connection. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 32 For IWF GSM-R group call response the following shall apply: SIP 200 (OK) according to ETSI TS 103 389 [6]. For further details see GSM-R IWF Group Call Response information flow in clause 7.1.1.1. This message is based on the SIP INVITE request for MCPTT adhoc group call as defined in ETSI TS 124 379 [10]. For IWF MCPTT adhoc group call request the following shall apply: This message is based on the SIP INVITE request for MCPTT adhoc group call as defined in ETSI TS 124 379 [10]. For IWF MCPTT adhoc group call response the following shall apply: This message is based on the SIP 200 (OK) request for MCPTT adhoc group call as defined in ETSI TS 124 379 [10]. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2 Group call principles | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1 Group call initiated by a GSM-R user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1 Group call initiated by a GSM-R user interacting with MCPTT group call | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1.1 Stage 2 procedure | Pre-conditions: 1) The Group Call Register (GCR) of the GSM-R system contains an additional entry under terminating dispatchers for a user on the IWF that represents the location defined group on the MCPTT system. Figure 7.2.1.1.1-1 illustrates the procedure for a group call initiated by a GSM-R user interacting with an MCPTT group call. MCPTT client 2 MCPTT server IWF MCPTT client 1 8. Media plane is established 3. IWF MCPTT ad hoc group call request 6. IWF MCPTT ad hoc group call response 5. Call the MCPTT users determined in step 4 GSM-R MSC 1. IWF GSM-R group call request 7. IWF GSM-R group call response 4. Determine the list of participants based on the criteria included in step 3 2. Determine the criteria to be used for the MCPTT ad hoc group call based on the CT5 number received in step 1 Figure 7.2.1.1.1-1: Group call initiated by GSM-R user interacting with MCPTT group call ETSI ETSI TS 103 792 V1.1.1 (2026-01) 33 The procedure shall be as follows: 1. The procedure shall be as follows: Triggered by a group call in GSM-R the GSM-R system sends a GSM-R IWF group call request to the IWF. 2. Based on the CT5 FN received in step 1 the IWF determines the criteria to be used in the ad-hoc group call. NOTE 1: An international EIRENE CT 5 number has the following format: IC+50/1+SSSSS+GID. The format of the criteria for the ad-hoc group call used by FRMCS is defined in FRMCS FIS-7970 [3]. The IWF generates the criteria based on the location part (SSSSS) and the GID part of the EIRENE CT5 FN. For REC for example, GID 299 is mapped to a criteria with the value of group call type that represents REC. GID 200 is mapped to a criteria with the value of group call type that represents "all trains in area" Then GSM-R location part SSSSS is mapped to the corresponding value for location in FRMCS. The GSM-R calltype 50 is mapped to a normal ad-hoc group call in MCPTT, while the calltype 51 is mapped to a broadcast call. 3. The IWF shall send an IWF MCPTT adhoc group call request to the MCPTT server. 4. The MCPTT server determines the list of users to be included based on the criteria included in the IWF MCPTT adhoc group call request in step 3. 5. The MCPTT server sends individual MCPTT adhoc group call requests to all concerned MCPTT users. 6. The MCPTT server sends a IWF MCPTT adhoc group call response to the IWF. 7. The IWF shall send a IWF GSM-R group call response to the GSM-R system. 8. The media plane between all concerned users in the MCPTT system and in the GSM-R system is established. The link between the two systems is established as two-way channel. i.e. the group calls are linked with a two- way speech channel which is always open for talking/listening. NOTE 2: The handling of talker control is described in clause 7.2.5, and the handling of mute and unmute is described in clause 7.2.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1.2 Stage 3 procedure | Pre-conditions: 1) The Group Call Register (GCR) of the GSM-R system contains an additional entry under terminating dispatchers for a user on the IWF that represents the location defined group on the MCPTT system. 2) The MCPTT server has location criteria defined that can be used to determine the users of an ad-hoc group call. Figure 7.2.1.1.2-1 illustrates the procedure for a group call initiated by a GSM-R user interacting with an MCPTT group call. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 34 MCPTT client 2 MCPTT server IWF MCPTT client 1 8. Media plane is established 3. SIP INVITE request for adhoc group call containing criteria determined in step 2 6. SIP 200 (OK) response 5. Send individual SIP INVITE requests to the MCPTT users determined in step 4 GSM-R 1. SIP INVITE request for terminating dispatcher 7. SIP 200 (OK) response 4. Determine the list of participants based on the criteria included in step 3 2. Determine the criteria to be used based on the value of the CT5 FN used by the GSM-R group call Figure 7.2.1.1.2-1: Group call initiated by GSM-R user interacting with MCPTT group call The procedure shall be as follows: 1. Triggered by a group call in GSM-R the GSM-R system sends a SIP INVITE request towards the IWF as defined in ETSI TS 103 389 [6] with the request URI set to the value of the terminating dispatcher corresponding to the matching MCPTT group. NOTE 1: From GSM-R perspective it is a terminating dispatcher having a special function to act as logical entry for a group call in MCPTT. 2. The IWF determines the criteria to be used for the ad-hoc group call based on the value of the GSM-R group GCRef (international EIRENE CT5 FN) contained in the SIP From header. NOTE 2: An international EIRENE CT 5 number has the following format: IC+50/1+SSSSS+GID. The format of the criteria for the ad-hoc group calls used by FRMCS is defined in FRMCS FIS-7970 [3]. The IWF generates the criteria based on the location part (SSSSS) and the GID part of the EIRENE CT5 FN. For REC for example, GID 299 is mapped to a criteria with the value of group call type that represents REC. GID 200 is mapped to a criteria with the value of group call type that represents "all trains in area". Then GSM-R location part SSSSS is mapped to the corresponding value for location in FRMCS. The GSM-R calltype 50 is mapped to a normal ad-hoc group call in MCPTT, while the calltype 51 is mapped to a broadcast call, indicated by the <broadcast-ind> element present with a value of "true". NOTE 3: The criteria used in FRMCS are defined in the FRMCS FIS-7970 [3]. NOTE 4: The IWF performs the mapping of the international CT5 EIRENE number and the criteria to be used in the MCPTT system according to clause 6. 3. The IWF sends a SIP INVITE request for an MCPTT adhoc group call to the MCPTT server, that contains the criteria as determined in step 2. A Resource-Priority header field is added, set to "normal priority" mcptt.x value, x=0 (as defined in IETF RFC 8101 [5]). In addition the <user-requested-priority> field shall be added, set according to the Communication Session Category to an mcptt.x value, x=0 to 15, based on the received GSM-R Call Priority and depending on the priority mapping between GSM-R and MCPTT. The emergency flag and the imminent peril flag shall not be set by the IWF. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 35 4. The MCPTT server determines the list of users to be included based on the criteria and local policy. 5. The MCPTT server sends individual SIP INVITE requests for MCPTT adhoc group call to all concerned MCPTT users. 6. The MCPTT server sends a SIP 200 (OK) response to the IWF. 7. The IWF sends a SIP 200 (OK) response to the GSM-R system. 8. The media plane between all concerned users in the MCPTT system and in the GSM-R system is established. The link between the two systems is established as two-way channel i.e. the group calls are linked with a two-way speech channel which is always open for talking/listening. NOTE 5: The handling of talker control is described in clause 7.2.5, and the handling of mute and unmute is described in clause 7.2.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2 Group call initiated by an MCPTT user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1 Group call setup initiated by MCPTT user interacting with the GSM-R system | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1.1 Stage 2 procedure | Pre-conditions: 1) The configuration on the MCPTT server for the criteria used in the adhoc group call contains an additional entry with an MCPTT ID that represents CT5 numbers on the GSM-R system. 2) The IWF contains configuration data containing the value of an MCPTT ID used for the interworking of adhoc group calls with group calls on the GSM-R system. When it receives an adhoc group call request targeted to the MCPTT ID that is configured on the IWF for the interworking of adhoc group calls, the IWF derives the CT5 number based on the criteria received in the adhoc group call request. 3) The group call register (GCR) of the GSM-R system contains an additional entry under originating dispatchers that has the same value as the originating ID (MSISDN or FN) sent in the request from the IWF to trigger the group call in the GSM-R system in step 9. NOTE 1: This entry is required to authenticate the Dispatcher Leg on GSM-R GCR and allow group call establishment. Figure 7.2.2.1.1-1 illustrates the procedure for a group call initiated by an MCPTT user interacting with an GSM-R group call. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 36 MCPTT client 1 MCPTT server IWF 2. Ad hoc group call request 11. IWF MCPTT Ad hoc group call response 12. Ad hoc group call response 1. Initiate group call 3. Check authorisation 7. IWF MCPTT Ad hoc group call request MCPTT client 2 GSM-R 9. IWF GSM-R Group call request 10. IWF GSM-R Group call response GSM-R MCPTT IWF 4.Ad hoc group call request return 5. Determine the list of participants based on the rule set specified in step 2 MCPTT client 3 6. Call the MCPTT users determined in step 5 13. Media plane is established 8. Determine the CT5 number to be used for the GSM-R group call based on the criteria received in step 7 Figure 7.2.2.1.1-1: Group call setup initiated by MCPTT user interacting with GSM-R group call The procedure shall be as follows: 1. The user at MCPTT client 1 initiates an adhoc group call to a group that is involving a GSM-R system. 2. The MCPTT client 1 sends an adhoc group call request containing the details of the criteria to be applied by the MCPTT server. 3. The MCPTT server receives the adhoc group call request and checks if the adhoc group call is supported and authorized. 4. The MCPTT server sends an adhoc group call request return message to MCPTT client 1 containing the following information elements: i) the MCPTT adhoc group ID generated by the MCPTT server; ii) the group ID of the pre-configured group to be used for the adhoc group call (only included if the adhoc group call is authorized); and iii) result of whether the adhoc group call is authorized or not. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 37 If the adhoc group call request is not authorized, the MCPTT server and client 1does not proceed with the rest of the steps. 5. The MCPTT server determines the list of users to be included in the adhoc group call. NOTE 2: Based on the criteria provided in step 2 and based on configuration within the MCPTT server, the MCPTT server determines an MCPTT user representing the GSM-R group to be included in the adhoc group call. NOTE 3: The list of users determined at step 5 will not contain additional MCPTT users representing a GSM-R group to avoid chained group calls and loops. 6. The MCPTT server sends individual MCPTT adhoc group call requests to all MCPTT users determined in step 5. 7. The MCPTT server sends an IWF MCPTT adhoc group call request to the IWF inviting the MCPTT user represented by the GSM-R group determined in step 5. 8. Based on the criteria received in step 7 and based on configuration within the IWF, the IWF determines the CT5 FN to be used in the subsequent group call request towards GSM-R. NOTE 4: The format of the criteria for the ad-hoc group calls used by FRMCS is defined in FRMCS FIS-7970 [3]. An international EIRENE CT5 number has the following format: IC+50/1+SSSSS+GID. The IWF generates the CT5 FN to be used for the group call in GSM-R by deriving the location portion SSSSS from the location part of the criteria, and the GID from the group call type part of the criteria. The GSM-R calltype 50 or 51 is determined depending on the presence of a <broadcast-ind> element present with a value of "true". 9. The IWF sends an IWF GSM-R group call request to the GSM-R system. 10. The GSM-R system sends an IWF GSM-R group call response to the IWF. 11. The IWF sends an IWF adhoc group call response to the MCPTT server. 12. The MCPTT server sends an adhoc group call response to MCPTT client 1. 13. The media plane between all concerned users in the MCPTT system and in the GSM-R system is established. The link between the two systems is established as two-way channel i.e. the group calls are linked with a two-way speech channel which is always open for talking/listening. NOTE 5: The handling of talker control is described in clause 7.2.5, and the handling of mute and unmute is described in clause 7.2.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1.2 Stage 3 procedure | Pre-conditions: 1) The configuration on the MCPTT server for the criteria used in the adhoc group call contains an additional entry with an MCPTT user representing the corresponding CT5 number in GSM-R. 2) The IWF contains a configuration containing the value of an MCPTT ID representing the groups on the GSM- R system. When it receives a SIP INVITE request targeting the MCPTT ID that is configured on the IWF, the IWF shall derive the CT5 number based on the criteria received in the SIP INVITE request. 3) The Group Call Register (GCR) of the GSM-R system contains an additional entry under originating dispatchers that has the same value as the originating ID (MSISDN or FN) sent in the request from the IWF to trigger the group call in the GSM-R system in step 9. Figure 7.2.2.1.2-1 illustrates the procedure for a group call initiated by an MCPTT user interacting with a GSM-R group call. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 38 MCPTT client 1 MCPTT server IWF 2. SIP INVITE request 11. SIP 200 (OK) response 12. SIP 200 (OK) response 1. Initiate group call 3. Check authorisation 7. SIP INVITE request MCPTT client 2 GSM-R 9. SIP INVITE request 10. SIP 200 (OK) response GSM-R MCPTT IWF 5. Determine the list of participants based on the rule set specified in step 2 MCPTT client 3 6. Send individual SIP INVITE requests to the users determined in step 5 13. Media plane is established 4. Determine group ID if required 8. Determine the CT5 number to be used for the GSM-R group call based on the criteria received in step 7 Figure 7.2.2.1.2-1: Group call setup initiated by MCPTT user interacting with GSM-R group call The procedure shall be as follows: 1. The user at MCPTT client 1initiates an adhoc group call to a group that is involving a GSM-R system. 2. The MCPTT client 1 sends a SIP INVITE request for adhoc group call request according to ETSI TS 124 379 [10] containing the details of the criteria to be applied by the MCPTT server. 3. The MCPTT server accepts the adhoc group call request checks if the adhoc group call is supported and authorized. 4. According to the conditions required in ETSI TS 124 379 [10], the MCPTT server generates a group ID to be used for the adhoc group call. Otherwise, the group ID included in the SIP INVITE request from step 2 is used. 5. The MCPTT server determines the list of users to be included in the adhoc group call. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 39 NOTE 1: Based on the criteria provided in step 2 and based on configuration within the MCPTT server, the MCPTT server determines an MCPTT user representing the GSM-R group to be included in the adhoc group call. Additionally, the list of users to be included typically contain MCPTT users matching the criteria and may also include terminating GSM-R dispatchers. 6. The MCPTT server sends individual MCPTT adhoc group call requests to all MCPTT users determined in step 5. 7. The MCPTT server sends a SIP INVITE request for an MCPTT adhoc group call towards the IWF for the MCPTT user representing the GSM-R group determined in step 5. 8. Based on the criteria received in step 7 and based on configuration within the IWF, the IWF determines the CT5 FN to be used in the subsequent group call request towards GSM-R. NOTE 2: The format of the criteria for the ad-hoc group calls is defined in FRMCS FIS-7970 [3]. An international EIRENE CT 5 number has the following format: IC+50/1+SSSSS+GID. The IWF generates the CT5 FN to be used for the group call in GSM-R by deriving the location portion SSSSS from the location part of the criteria, and the GID from the group call type part of the criteria. The GSM-R calltype 50 or 51 is determined depending on the presence of a <broadcast-ind> element present with a value of "true". 9. The IWF sends a SIP INVITE request according to ETSI TS 103 389 [6] towards the GSM-R system for the CT5 FN to be used in the GSM-R system according to clause 6 to the GSM-R system. 10. The GSM-R system sends a SIP 200 (OK) response according to ETSI TS 103 389 [6] to the IWF. 11. The IWF sends a SIP 200 (OK) response to the MCPTT server. 12. The MCPTT server sends a SIP 200 (OK) response to MCPTT client 1. 13. The media plane between all concerned users in the MCPTT system and in the GSM-R system is established. The link between the two systems is established as two-way channel. i.e. the group calls are linked with a two-way speech channel which is always open for talking/listening. NOTE 3: The handling of talker control is described in clause 7.2.5, and the handling of mute and unmute is described in clause 7.2.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3 Late entry | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1 Late entry of an MCPTT user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1.1 Stage 2 procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.3.1.1-1 illustrates the procedure for late joining of an MCPTT user into an ongoing group call already established between the MCPTT system and the GSM-R system. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 40 MCPTT client 1 MCPTT server IWF 3. Ad hoc group call request 4. Ad hoc group call response MCPTT client 2 GSM-R GSM-R MCPTT IWF 2. The MCPTT server detects that the MCPTT client 1 meets the criteria to be included in the ad hoc group call MCPTT client 3 1. As a result of an established group call, the media plane between the MCPTT users at MCPTT client 2, client 3 on the MCPTT system and users on the GSM-R system is established 5. Ad hoc group call changed by adding MCPTT client 1 to the existing ad hoc group call 6. The MCPTT server detects that the MCPTT client 1 no longer meets the criteria to be included in the ad hoc group call 7. Ad hoc group leave request 8. Ad hoc group leave response 9. Ad hoc group call changed by removing MCPTT client 1 from the existing ad hoc group call Figure 7.2.3.1.1-1: Late call entry of an MCPTT user on an interworking group defined in MCPTT system The procedure shall be as follows: 1. As a result of a previously initiated group call, an adhoc group call is established between the MCPTT client 2 and MCPTT client 3 and the GSM-R system. 2. The MCPTT server detects that the MCPTT client 1 starts to meet the criteria to be included in the adhoc group call. 3. The MCPTT server sends an adhoc group call request to MCPTT client 1. 4. The MCPTT client 1 sends an adhoc group call response to the MCPTT server. 5. As a result, the adhoc group call is changed and the MCPTT client 1 is added to the ongoing MCPTT adhoc group call. 6. The MCPTT server detects that the MCPTT client 1 no longer meets the criteria to be included in the adhoc group call. 7. The MCPTT server sends an adhoc group leave request to MCPTT client 1. 8. The MCPTT client 1 sends an adhoc group leave response to the MCPTT server. 9. As a result, the adhoc group call is changed and the MCPTT client 1 is removed from the ongoing MCPTT adhoc group call. NOTE: For late entry of MCPTT users no interaction with GSM-R is required. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 41 |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1.2 Stage 3 procedure | No impact on existing stage 3 procedures. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.2 Late entry of a GSM-R user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.2.1 Stage 2 procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.3.2.1-1 illustrates the procedure for late joining of an MCPTT user into an ongoing group call already established between the MCPTT system and the GSM-R system. MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF 1. As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS 1 and MS2 on the GSM-R system is established 3. The group call changed on the GSM-R side that GSM-R MS 3 is added to the ongoing group call GSM-R MS 1 GSM-R MS 2 GSM-R MS 3 2. The GSM-R MS 3 detects that it has entered the group call area of the ongoing group call 4. The GSM-R MS 3 detects that it is no longer in the group call area of the ongoing group call 5. The group call changed on the GSM-R side that GSM-R MS 3 is no longer participating in the ongoing group call Figure 7.2.3.2.1-1: Late call entry of an GSM-R user on an interworking group defined in GSM-R system The procedure shall be as follows: 1. As a result of a previously initiated group call, an adhoc group call is established between the MCPTT client 1, MCPTT client 2, and GSM-R MS 1 and GSM-R MS 2 on the GSM-R system. 2. The GSM-R MS 3 detects that it has entered the group call area of the ongoing group call. 3. As a result, the group in GSM-R is changed and the GSM-R MS 3 is added to the ongoing group call. 4. The GSM-R MS 3 detects that it is no longer in the group call area of the ongoing group call. 5. As a result, the group in GSM-R is changed and the GSM-R MS 3 is removed to the ongoing group call. NOTE 1: Leaving and joining of dispatchers are as well handled purely internally in the GSM-R system. NOTE 2: For late entry of GSM-R users and leaving and joining of dispatchers no interaction with MCPTT is required. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 42 |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.2.2 Stage 3 procedure | No impact on existing stage 3 procedures. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4 Group call release | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4.1 General | Group calls can be released by various means: • In GSM-R this can be, for example, by an authorized dispatcher sending a kill sequence, or by timer expiry. Irrespective how the group call is released, each participating user connected via SIP trunk receives a SIP BYE message. • MCPTT group calls can be released due to various conditions, like timer expiry, where (unlike GSM-R) each participating user receives a SIP BYE message. The procedure for group call release is to release the complete group call when a condition to release the group call in one system (MCPTT or GSM-R) is fulfilled. NOTE: The no activity timers run on each system independently, and if one of them expires the whole call is released. Therefore, it might be necessary to increase the value. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4.2 Group call release initiated from the GSM-R side | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4.2.1 Procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.4.2.1-1 illustrates the procedure for releasing a group call from the GSM-R side. MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF GSM-R Dispatcher 1 GSM-R MS 1 GSM-R MS 2 As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS , MS2, and dispatcher 1 on the GSM-R system is established 1. kill 6. Group calls are released on both sides 2. BYE 2a. BYE 2b. BYE Figure 7.2.4.2.1-1: Group call released from GSM-R side ETSI ETSI TS 103 792 V1.1.1 (2026-01) 43 The procedure shall be as follows: 1. GSM-R Dispatcher 1 wants to release the group call and sends a kill message towards the GSM-R MSC. 2. The GSM-R MSC sends a SIP BYE messages towards all users connected via fixed line (including the IWF), and sends messages towards the mobile users. 2a. The IWF shall send a SIP BYE message towards the MCPTT server. 2b-c. The MCPTT server sends SIP BYE messages towards all participants of the MCPTT group call. NOTE: Based on session release policy the MCPTT server releases the adhoc group call if a user with a specific MCPTT ID (the user representing the GSM-R leg of the call) leaves the call. 2d-e. The GSM-R MSC sends disconnect messages towards the GSM-R mobile users. 3b-c. The MCPTT clients 1 and 2 respond with a SIP 200 (OK) to the MCPTT server. 4. The MCPTT server respond with a SIP 200 (OK) to the IWF. 5. The GSM-R MSC sends Disconnect messages towards all GSM-R mobile users of the GSM-R group call. 6. The group call is released in MCPTT and in GSM-R. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4.3 Group call release initiated from the MCPTT side | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.4.3.1 Procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.4.3.1-1 illustrates the procedure for releasing a group call from the MCPTT side. MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF GSM-R Dispatcher 1 GSM-R MS 1 GSM-R MS 2 As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS 1 , MS2, and dispatcher 1 on the GSM-R system is established 9. Group calls are released on both sides 2a. BYE 2. BYE 1. MCPTT server detects condition to release the group call 7. BYE 4. Convert MCPTT SIP BYE into GSM-R KILL 3a. 200 (OK) 3b. 200 (OK) 3c. 200 (OK) Figure 7.2.4.3.1-1: Group call released from MCPTT side ETSI ETSI TS 103 792 V1.1.1 (2026-01) 44 The procedure shall be as follows: 1. The MCPTT server detects a condition to release the group call. 2. The MCPTT server sends a BYE message towards the IWF. 2a-b. The MCPTT server sends BYE messages towards the MCPTT clients of the other MCPTT users. 3a-b. The MCPTT clients of the other MCPTT users respond with a SIP 200 (OK) response. 3c. The IWF responds with a SIP 200 (OK) response. 4. The IWF converts the MCPTT SIP BYE into a GSM-R KILL. 5. The IWF sends a KILL message using explicit signalling according to ETSI TS 103 389 [6] towards the GSM-R MSC. 6a-b. The GSM-R MSC sends Disconnect messages towards all mobile GSM-R mobile users of the GSM-R group call. 7. The GSM-R MSC sends a SIP BYE message towards the dispatcher connected via fixed line. 8. The fixed line dispatcher responds with a SIP 200 (OK) response. 9. The group call is released in MCPTT and in GSM-R. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5 Talker control | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5.1 General | In GSM-R, talker control procedures depend on the type of user requesting to talk. This clause covers talker control for mobile users (called service subscribers), which is done by uplink control procedures. Uplink control operations in GSM-R have no impact on the MCPTT side hence also no impact on the IWF (see ETSI TR 103 768 [i.1]). Dispatchers connected via fixed line networks can talk at any time. However, to ensure that a service subscriber that has the uplink granted hears the audio of the dispatcher talking, the dispatcher unmutes the downlink when talking. Mute/Unmute is discussed in clause 7.2.6. Figure 7.2.5.2-1 illustrates the procedure. NOTE: Mute-Unmute indication is required only in case 1 channel mode is used on GSM-R side. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5.2 Talker control operation initiated from the GSM-R side | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5.2.1 Procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.5.2.1-1 illustrates the procedure for talker control from the GSM-R side. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 45 MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF GSM-R Dispatcher 1 GSM-R MS 1 GSM-R MS 2 As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS 1, MS2, and dispatcher 1 on the GSM-R system is established 1. Uplink request 3. The user at MS 1 has the uplink and can talk 5. Uplink release 6. Uplink release response 7. The user at MS 1 has relased the uplink 4. No change on the MCPTT side 8. No change on the MCPTT side Figure 7.2.5.2.1-1: Talker control from GSM-R side The procedure shall be as follows: 1. GSM-R Mobile user at MS 1 wants to talk and requests the uplink. 2. GSM-R Mobile user at MS 1 gets the uplink. 3. GSM-R Mobile user at MS 1 has the uplink and can talk. 4. No impact on the MCPTT side. 5. GSM-R Mobile user at MS 1 releases the uplink. 6. GSM-R Mobile user at MS 1 gets a release response message. 7. GSM-R Mobile user at MS 1 has released the uplink and cannot talk any more. 8. No impact on the MCPTT side. NOTE: For floor control operations performed within GSM-R no interaction with MCPTT is required. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5.3 Talker control operation initiated from the MCPTT side | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.5.3.1 Procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. In MCPTT talker control is done for both dispatchers and other users in the same way. Figure 7.2.5.3-1 illustrates the conclusion agreed in ETSI TR 103 768 [i.1]. The main principle is that if any user in MCPTT has the floor, the IWF is aware of that and sends an "Unmute" message towards GSM-R to make sure a service subscriber that has the uplink can ETSI ETSI TS 103 792 V1.1.1 (2026-01) 46 hear the audio from the MCPTT side. If the floor is released on the MCPTT side, the IWF is also aware of that and sends a "Mute" message towards GSM-R to mute the downlink of the service subscriber to avoid unnecessary echo. MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF GSM-R Dispatcher 1 GSM-R MS 1 GSM-R MS 2 As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS 1, MS 2, and Dispatcher 1 on the GSM-R system is established 1. Uplink request 2. Uplink granted 3. The user at MS 1 has the uplink and can talk. To avoid echo, his downlink gets muted. 11. The user at MS 1can still talk, but can also hear the user at MCPTT client 1 talking 4. No change on the MCPTT side 5. Floor request 6. Floor granted 7. Floor taken 8. Floor taken 10. Unmute 12 Floor release 13. Floor idle 14. Floor idle 15. Floor idle 17. Mmute 18. The user at MS 1can still talk, but echo is avoided, as his downlink is muted 9. Convert RTCP „Floor taken“ into Unmute 16. Convert RTCP „Floor idle“ into Mute Figure 7.2.5.3-1: Talker control from MCPTT side The procedure shall be as follows: 1. GSM-R Mobile user at MS 1 wants to talk and requests the uplink. 2. GSM-R Mobile user at MS 1 gets the uplink. 3. GSM-R Mobile user at MS 1 has the uplink and can talk. To avoid echo, his downlink is muted. 4. No impact on the MCPTT side. 5. MCPTT user at client 1 wants to talk and requests the floor. 6. MCPTT user at client 1 receives a floor granted message and gets the floor. 7. The MCPTT server sends a floor taken message towards MCPTT client 2. 8. The MCPTT server sends a floor taken message towards the IWF. 9. The IWF converts the RTCP floor taken message received from MCPTT into a GSM-R Unmute message. 10. The IWF sends an Unmute message using explicit signalling according to ETSI TS 103 389 [6] towards the GSM-R MSC. 11. The downlink of the GSM-R user at MS 1 is unmuted. GSM-R Mobile user at MS 1 can hear the audio from the MCPTT user at client 1. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 47 12. The MCPTT user at client 1 releases the floor. 13. The MCPTT server sends a floor idle message towards MCPTT client 1. 14. The MCPTT server sends a floor idle message towards MCPTT client 2. 15. The MCPTT server sends a floor idle message towards the IWF. 16. The IWF converts the RTCP floor idle message received from MCPTT into a GSM-R Mute message. 17. The IWF sends a Mute message using explicit signalling according to ETSI TS 103 389 [6] towards the GSM-R MSC. 18. The downlink of the GSM-R user at MS 1 is muted, therefore echo is avoided. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.6 Handling of mute and unmute in GSM-R | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.6.1 General | In GSM-R a dispatcher connected via fixed line has to send an unmute message when he wants to talk (indicated by pressing the PTT button) to ensure that service subscribers that have the uplink can hear him. When the GSM-R dispatcher connected via fixed line does not want to talk any more (indicated by releasing the PTT button), a mute message will be sent. As analysed in ETSI TR 103 768 [i.1], these operations have no impact on the MCPTT side, hence also not on the IWF. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.6.2 Procedure | Figure 7.2.6.2-1 illustrates the mute and unmute procedure on GSM-R. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 48 MCPTT client 1 MCPTT server IWF MCPTT client 2 GSM-R GSM-R MCPTT IWF GSM-R Dispatcher 1 GSM-R MS 1 GSM-R MS 2 As a result of an established group call, the media plane between the MCPTT users at MCPTT client 1, client 2 on the MCPTT system and GSM-R MS 1, MS 2, and Dispatcher 1 on the GSM-R system is established 1. Uplink request 2. Uplink granted 3. The user at MS 1 has the uplink and can talk. To avoid echo, his downlink gets muted. 4. No change on the MCPTT side 11. The user at MS 1can still talk, but echo is avoided, as his downlink is muted 5. Dispatcher 1 wants to talk and presses the PTT button 6. Unmute 7. The user at MS 1 still has the uplink and can talk, but his downlink is unmuted an he can hear dispatcher 1. 8. No change on the MCPTT side 9. Dispatcher 1 does not want to talk any more and releases the PTT button 10. Mute 12. No change on the MCPTT side Figure 7.2.6.2-1: Mute/Unmute in GSM-R The procedure shall be as follows: 1. GSM-R Mobile user at MS 1 wants to talk and requests the uplink. 2. GSM-R Mobile user at MS 1 gets the uplink. 3. GSM-R Mobile user at MS 1 has the uplink and can talk. To avoid echo, his downlink is muted. 4. No impact on the MCPTT side. 5. GSM-R dispatcher 1 wants to talk and presses the PTT button. 6. GSM-R dispatcher 1 sends an unmute message towards the GSM-R MSC. 7. GSM-R Mobile user at MS 1 continues to have the uplink and can talk, but his downlink is unmuted, and he can hear the audio from GSM-R dispatcher 1. 8. No impact on the MCPTT side. 9. GSM-R dispatcher 1 does not want to talk anymore and releases the PTT button. 10. GSM-R dispatcher 1 sends a mute message towards the GSM-R MSC. 11. GSM-R Mobile user at MS 1 still has the uplink and can talk, but to avoid echo, his downlink is muted. 12. No impact on the MCPTT side. NOTE: Mute/unmute operations performed within GSM-R require no interaction with MCPTT. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 49 |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.7 Media encryption | As described in ETSI TR 103 768 [i.1], the media between GSM-R and MCPTT is exchanged between the systems via a call leg with duplex voice path. In the present document media is mixed on the GSM-R and on the MCPTT side. The mixing on the MCPTT side is planned to be done either centrally or locally (at the IWF). If the mixing is done centrally on the MCPTT side, as stated in ETSI TS 123 379 [i.6], end-to-end encryption of the media is not possible. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.8 Codec negotiation | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.8.1 Codec negotiation for calls initiated by MCPTT user | Figure 7.2.8.1-1 is a simplified call setup procedure that illustrates the codec negotiation for calls initiated by a MCPTT user. The main characteristic of the procedure is to avoid transcoding by the MCPTT server by using AMR-WB as preferred codec. Additionally, the IWF removes the EVS-SWB codec with the result that only the AMR-WB codec is present in the outgoing offer from the IWF to GSM-R. MCPTT client 1 MCPTT server (CF/MRF) IWF 1. Initiate group call MCPTT client 2 GSM-R GSM-R MCPTT IWF MCPTT client 3 IWF removes EVS-SWB (only AMR-WB remains for group calls with GSM-R) No transcoding Existing transcoding in GSM-R network Negotiating codec by means of prefered codec Figure 7.2.8.1-1: Codec negotiation for call initiated by an MCPTT user |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.8.2 Codec negotiation for calls initiated by GSM-R user | Figure 7.2.8.2-1 is a call setup procedure that illustrates the codec negotiation for calls initiated by a GSM-R user. The main characteristic of the procedure is that the IWF removes G.711 from all outgoing offers for group calls between MCPTT and GSM-R. Additionally within MCPTT transcoding is avoided by using AMR-WB as preferred codec. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 50 MCPTT client 1 MCPTT server (CF/MRF) IWF Answer1 (AMR-WB) MCPTT client 2 GSM-R MCPTT IWF MCPTT client 3 Offer3 (AMR-WB) Answer2 ( AMR-WB) Answer3 ( AMR-WB) IWF removes G711 (only AMR-WB remains for group calls with GSM-R) No transcoding Existing transcoding in GSM-R network Offer ( AMR-WB) Answer (AMR-WB) Answer (AMR-WB) GSM-R Initiate group call Figure 7.2.8.2-1: Codec negotiation for call initiated by a GSM-R user |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.9 Codec transcoding | FRMCS uses high-definition voice codec AMR-WB or EVS-SWB ("FRMCS codecs"). In the rest of the clause, the term "FRMCS codec" is used to designate the codec selected on the FRMCS side. Clause 7.2.8 illustrates how the IWF is involved during codec negotiation to avoid transcoding by the MCPTT server. For a call involving FRMCS and GSM-R users, transcoding may be required between G.711 and AMR-WB depending on the codecs supported by the GSM-R system. If AMR-WB is supported by the GSM-R system, as per clause 7.2.8, AMR-WB is used for a call involving FRMCS and GSM-R users. If FRMCS codec is not supported by the GSM-R system, transcoding between G.711 and FRMCS codec needs to take place. Annex A documents a set of possible approaches to ensure transcoding between G.711 and FRMCS codec which enables calls between FRMCS and GSM-R users. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8 Point-to-point call | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.1 General | This clause contains descriptions of stage 2 and stage 3 procedures for point-to-point calls interworking between GSM- R and FRMCS systems. For stage 3 procedures, it is described how information elements are mapped between GSM-R and MC messages. Other information elements in those GSM-R and MC messages which are not determined from such mapping are not described and should be determined by implementation, e.g. based on local service or configuration. The messages and information elements shown in the mapping in this clause are specified in ETSI TS 103 389 [6] for GSM-R, in ETSI TS 123 283 [11] for MCPTT stage 2, and in ETSI TS 129 379 [8] and ETSI TS 124 379 [10] for MCPTT stage 3. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 51 An MCPTT user is represented within the GSM-R system by an E.164 or EIRENE number. Therefore, calls placed by a GSM-R user to an MCPTT user are addressed to an E.164 or EIRENE number and calls received by a GSM-R user from an MCPTT user are identified by an E.164 or EIRENE number. If a point-to-point call is originated by a GSM-R user, the GSM-R MSC shall act as the controlling system for the call. If the call is originated by an MCPTT user, the MCPTT system shall act as the controlling system for the call. NOTE 1: Due to the assignment of controlling role to the system where the call originates (either GSM-R or FRMCS System), use of procedures of ETSI TS 129 379 [8] where the IWF acts in a participating role for call origination (clause 11.1.2.1) or in a controlling role for call termination (clause 11.1.3.2) are out of scope of the present document. A point-to-point call is known as a 'private call' in 3GPP specifications. A point-to-point call placed by a GSM-R user is set up without end-to-end encryption and the private call received by the GSM-R user from an MCPTT user also set up without end-to-end encryption. NOTE 2: Media encryption for private calls is not available in the present document. 8.2 Point-to-point call from GSM-R user to user on MCPTT system |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.1 Point-to-point call | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.1.1 Stage 2 procedure | Point-to-point call known as 'private call with manual commencement mode' in 3GPP specifications shall be supported for GSM-R and FRMCS interworking. Figure 8.2.1.1-1: Point-to-point call from GSM-R user to user on MCPTT system (stage 2) In Figure 8.2.1.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF private call request is defined in ETSI TS 123 283 [11], clause 10.4.1.2. • IWF private call response is defined in ETSI TS 123 283 [11], clause 10.4.1.3. • IWF ringing is defined in ETSI TS 123 283 [11], clause 10.4.1.4. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.1.2 Stage 3 procedure | The 3GPP procedures for IWF originated calls are contained in ETSI TS 129 379 [8], clause 11.2.2.1 for calls without floor control (full duplex calls). IWF GSM-R MSS/MGCF MCPTT server IWF private call request SIP INVITE 180 RINGING IWF ringing 200 OK IWF private call response ETSI ETSI TS 103 792 V1.1.1 (2026-01) 52 Figure 8.2.1.2-1: Point-to-point call from GSM-R user to user on MCPTT system (stage 3) Figure 8.2.1.2-1 illustrates the procedure for a point-to-point call initiated by a GSM-R user to a user on an MCPTT system. Construction of SIP INVITE at IWF The IWF shall map the GSM-R identities to corresponding MCPTT identities: • Calling party E.164/EIRENE number from the 'From' header field of the SIP INVITE is mapped (rules defined in clause 6.3.3) to an MCPTT ID/Functional Alias representing the calling GSM-R user. • Called party E.164/EIRENE number from the 'Request-URI' header field is mapped (rules defined in clause 6.3.3) to the MCPTT ID/Functional Alias of the called user on the MCPTT system. The SIP INVITE from IWF to MCPTT server shall be constructed according to ETSI TS 129 379 [8], clause 11, and shall include: • A Resource-Priority header field is added, set to "normal priority" mcptt.x value, x=0 as (as defined in IETF RFC 8101 [5]). In addition the <user-requested-priority> field shall be added, set according to the Communication Session Category as specified in clause 6.2.5 in ETSI TS 103 765-2 [4] based on the received GSM-R Call Priority and depending on the configurable priority mapping between GSM-R and MCPTT. • An Answer-Mode header field with the value "Manual" according to the rules and procedures of IETF RFC 5373[15]. • The MCPTT ID of the called MCPTT user copied into the <mcptt-request-uri> element in the application/vnd.3gpp.mcptt-info+xml MIME body of the outgoing SIP INVITE request. • An mcptt-info MIME xml body that contains the MCPTT ID representing the calling GSM-R user in the <mcptt-calling-user-id> sub-element, and also containing: - an <mcptt-params> element in the MIME body with <session-type> element set to "private"; - an encryption-mode attribute set to no encryption used. No media-level section for a media-floor control entity is included according to the MCPTT client procedures specified in ETSI TS 124 379 [10], clause 11.1.2 for duplex calls. NOTE: Media encryption for private calls is not available in the present document Handling of SIP 180 RINGING at IWF On receipt of a SIP 180 RINGING from the MCPTT server, the IWF shall send forward a SIP 180 RINGING message towards the GSM-R MSS/MGCF with elements according to ETSI TS 103 389 [6]. IWF MCPTT server SIP INVITE SIP INVITE 180 RINGING 180 RINGING 200 OK 200 OK GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 53 Handling of SIP 200 OK at IWF On receipt of a SIP 200 OK from the MCPTT server, the IWF shall verify the media parameters in the SDP body match those requested. The IWF shall send a SIP 200 OK message towards the GSM-R MSS/MGCF with elements according to ETSI TS 103 389 [6]. The SIP 200 OK response from the MCPTT server includes a Contact header field, which contains the MCPTT session identity allocated to that session. This MCPTT session identity shall be retained by the IWF to be able to associate a later SIP BYE to that session. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.2 Point-to-point call rejected by MCPTT system | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.2.1 Stage 2 procedure | Figure 8.2.2.1-1 shows the case where a call setup request initiated by a GSM-R user is rejected by the MCPTT system. Figure 8.2.2.1-1: Point-to-point call rejected by MCPTT system (stage 2) In Figure 8.2.2.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF private call request is defined in ETSI TS 123 283 [11], clause 10.4.1.2. • IWF private call response is defined in ETSI TS 123 283 [11], clause 10.4.1.3. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.2.2.2 Stage 3 procedure | Figure 8.2.2.2-1 shows the stage 3 procedure for an unsuccessful call setup from GSM-R user to an MCPTT user. Figure 8.2.2.2-1: Point-to-point call rejected by MCPTT system (stage 3) Construction of SIP INVITE The SIP INVITE sent to the MCPTT server by the IWF is constructed as described in clause 8.2.1.2 of the present document. IWF MCPTT server IWF private call request SIP INVITE SIP 4xx IWF private call response GSM-R MSS/MGCF IWF MCPTT server SIP INVITE SIP INVITE SIP 4xx / SIP 5xx SIP 4xx / SIP 5xx GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 54 Handling SIP 4xx and SIP 5xx On receipt of a SIP 4xx or SIP 5xx rejection response from the MCPTT server, the IWF shall forward the SIP rejection response to the GSM-R MSS/MGCF. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3 Point-to-point call initiated by an MCPTT user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.1 Point-to-point call | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.1.1 Stage 2 procedure | Figure 8.3.1.1-1 shows the procedure for a successful point-to-point call initiated by a user on the MCPTT system to a GSM-R user. Figure 8.3.1.1-1: Point-to-point call initiated by an MCPTT user (stage 2) In Figure 8.3.1.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF private call request is defined in ETSI TS 123 283 [11], clause 10.4.1.2. • IWF private call response is defined in ETSI TS 123 283 [11], clause 10.4.1.3. • IWF ringing is defined in ETSI TS 123 283 [11], clause 10.4.1.4. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.1.2 Stage 3 procedure | The 3GPP procedures for IWF terminated calls are contained in ETSI TS 129 379 [8], clause 11.2.2.1 for calls without floor control (full duplex calls). Figure 8.3.1.2-1: Point-to-point call initiated by an MCPTT user (stage 3) IWF GSM-R MSS/MGCF MCPTT server IWF private call request SIP INVITE 180 RINGING IWF ringing 200 OK IWF private call response IWF MCPTT server SIP INVITE 180 RINGING 180 RINGING 200 OK 200 OK GSM-R MSS/MGCF SIP INVITE ETSI ETSI TS 103 792 V1.1.1 (2026-01) 55 Figure 8.3.1.2-1 illustrates the procedure for a point-to-point call initiated by an MCPTT user to a user on an GSM-R system. Construction of SIP INVITE The IWF shall map the MCPTT identities to corresponding GSM-R identities: • Calling party MCPPT ID/Functional Alias of the SIP INVITE is mapped (rules defined in clause 6.3.3) to an E.164 or EIRENE SIP-R URI representing the calling user on the MCPTT system. • Called party MCPTT ID/Functional Alias is mapped (rules defined in clause 6.3.3) to the E.164 or EIRENE SIP-R URI of the called user on the GSM-R system. The SIP INVITE from IWF to GSM-R MSS/MGCF shall be constructed based on ETSI TS 103 389 [6], and shall include: • GSM-R Call Priority depending on the configurable priority mapping between GSM-R and MCPTT. Handling SIP 180 RINGING On receipt of a SIP 180 RINGING from the GSM-R MSS/MGCF, the IWF shall send forward a SIP 180 RINGING message towards the MCPTT server with elements according to ETSI TS 129 379 [8]. Handling SIP 200 OK On receipt of a SIP 200 OK from the GSM-R MSS/MGCF, the IWF shall verify the media parameters in the SDP body match those requested. The IWF shall send a SIP 200 OK message towards the MCPTT server with elements according to ETSI TS 129 379 [8]. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.2 Point-to-point call rejected by GSM-R system | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.2.1 Stage 2 procedure | Figure 8.3.2.1-1 shows the case where a call setup request initiated by a MCPTT user is rejected by the GSM-R system. Figure 8.3.2.1-1: Point-to-point call rejected by GSM-R system (stage 2) In Figure 8.3.2.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF private call request is defined in ETSI TS1 23.283 [11], clause 10.4.1.2. • IWF private call response is defined in ETSI TS 123 283 [11], clause 10.4.1.3. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.3.2.2 Stage 3 procedure | Figure 8.3.2.2-1 shows the stage 3 procedure for an unsuccessful call setup from MCPTT user to a GSM-R user. IWF MCPTT server IWF private call request SIP INVITE SIP 4xx IWF private call response GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 56 Figure 8.3.2.2-1: Point-to-point call rejected by GSM-R system (stage 3) Construction of SIP INVITE The SIP INVITE sent to the GSM-R MSS/MGCF by the IWF is constructed as described in clause 8.3.1.2 of the present document. Handling SIP 4xx and SIP 5xx On receipt of a SIP 4xx or SIP 5xx rejection response from the GSM-R MSS/MGCF, the IWF shall forward the SIP 4xx or SIP 5xx rejection response to the MCPTT server. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4 Point-to-point call release | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.1 Individual call release by GSM-R user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.1.1 Stage 2 procedure | Figure 8.4.1.1-1 shows the stage 2 procedure for disconnection of a point-to-point call, where the disconnection is initiated by a GSM-R user. Figure 8.4.1.1-1: Point-to-point call release (stage 2) In Figure 8.4.1.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF call end request is defined in ETSI TS 123 283 [11], clause 10.4.1.5. • IWF call end response is defined in ETSI TS 123 283 [11], clause 10.4.1.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.1.2 Stage 3 procedure | Figure 8.4.1.2-1 shows the stage 3 procedure for disconnection of a point-to-point call, where the disconnection is initiated by a GSM-R user. IWF MCPTT server SIP INVITE SIP INVITE SIP 4xx / SIP 5xx SIP 4xx / SIP 5xx GSM-R MSS/MGCF IWF MCPTT server IWF call end request SIP BYE SIP 200 OK IWF call end response GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 57 Figure 8.4.1.2-1: Point-to-point call release (stage 3) On receipt of a SIP BYE message from the GSM-R MSS/MGCF, the IWF shall forward the SIP BYE message to the MCPTT server. The IWF shall forward the 200 OK to the GSM-R MSS/MGCF when received from the MCPTT server. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.2 Individual call release by FRMCS user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.2.1 Stage 2 procedure | Figure 8.4.2.1-1 shows the stage 2 procedure for disconnection of a point-to-point call, where the disconnection is initiated by an FRMCS user. Figure 8.4.2.1-1: Individual call release by FRMCS user (stage 2) In Figure 8.4.2.1-1: • The SIP interface between the MGCF and IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF call end request is defined in ETSI TS 123 283 [11], clause 10.4.1.5. • IWF call end response is defined in ETSI TS 123 283 [11], clause 10.4.1.6. |
05f8beb7977a67521a875d86df071465 | 103 792 | 8.4.2.2 Stage 3 procedure | Figure 8.4.2.2-1 shows the stage 3 procedure for disconnection of a point-to-point call, where the disconnection is initiated by an FRMCS user. IWF MCPTT server SIP BYE SIP BYE SIP 200 OK SIP 200 OK GSM-R MSS/MGCF IWF MCPTT server IWF call end request SIP BYE SIP 200 OK IWF call end response GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 58 Figure 8.4.2.2-1: Individual call release by FRMCS user (stage 3) On receipt of a SIP BYE message from the MCPTT server, the IWF shall forward the SIP BYE message to the GSM-R MSS/MGCF. The IWF shall forward the 200 OK to the MCPTT server when received from the GSM-R MSS/MGCF. |
05f8beb7977a67521a875d86df071465 | 103 792 | 9 Text messaging service | |
05f8beb7977a67521a875d86df071465 | 103 792 | 9.1 General | This clause contains Stage 2 and Stage 3 protocol procedures for the interworking of short data enabled services between GSM-R and 3GPP MC systems supported in the present document. |
05f8beb7977a67521a875d86df071465 | 103 792 | 9.2 One-to-one text messaging procedures | |
05f8beb7977a67521a875d86df071465 | 103 792 | 9.2.1 One-to-one SDS to Instant Messaging interworking principles | The IWF receives text messages as Instant Messages from the GSM-R IP-SM-GW. It is assumed that the IP-SM-GW use Service Level Interworking (SLI) according to ETSI TS 129 311 [i.10], in order to create Instant Messages from SMS and to create SMS from Instant Messages. The IWF shall interwork Instant Messages (at the IWF-g5 reference point) with MCData SDS messages (at the IWF-2 reference point). The IWF behaves as MCData participating function to the MCData controlling function on the FRMCS side and it implements the ISC interface as an S-CSCF to the IP- SM-GW on the GSM-R side. The GSM-R users behind the IWF are represented by MCData IDs, MCData group IDs or by Functional Aliases, as appropriate. ETSI TS 129 311 [i.10] specifies the Instant Messaging to be based on OMA-TS-SIMPLE_IM protocol. MCData SDS IWF messaging shall be supported using the signalling plane. ETSI TS 123 283 [11] describes the functional model for the IWF-2 interface used for the SDS message interworking. IWF-2 supports a subset of the functionality of MCData-SDS 1, as defined in ETSI TS 123 282 [i.7] with some differences, as specified in the present document. The IWF-2 interface is supported by the same signalling plane protocol(s) as defined for MCData 3 except as specified in the present document. MCData-SDS-1 reference point is used for MCData application signalling during session establishment in support of SDS data transfer. MCData-SDS-1 reference point is also used for unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the IWF Gateway. GSM-R users behind the IWF are mapped to MCData IDs as described above in the Point-to-Point call mapping and so the MCData server shall be capable of routing messages towards identities located behind the IWF. The procedure for an MCData user requesting to send a signalling control plane SDS to a GSM-R user is as specified in ETSI TS 123 282 [i.7], clause 7.4.2.2 for the one-to-one standalone short data service using the signalling control plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the GSM-R user. The IWF behaves as a peer MCData server. IWF MCPTT server SIP BYE SIP BYE SIP 200 OK SIP 200 OK GSM-R MSS/MGCF ETSI ETSI TS 103 792 V1.1.1 (2026-01) 59 SDS messages can support a maximum of 1000 bytes. IP-SM-GW outside of the IWF will be responsible for concatenation to individual SMS messages or cropping the message to fit on SMS message. This is out of the scope of the IWF Gateway. In the direction of IWF to IP-SM-GW, the S-CSCF function of the IWF shall send Instant Messages using the SIP MESSAGE request. Applying the related procedures for an Application Server acting as an originating User Agent as defined in clause 5.7.3 in ETSI TS 124 229 [i.11] as well as IETF RFC 3428 [14]. The SIP MESSAGE shall contain a body, using the standard MIME header fields to identify the content. In addition, the S-CSCF function of the IWF shall include in the SIP MESSAGE request: a) the Request URI set to a Tel URI corresponding to the MSISDN of the recipient. The IMSI is derived from the mapping procedures used in a point-to-point call above. The called MCData User Identity or the Functional Alias Identity is mapped to obtain the destination MSISDN; In the SIP MESSAGE this element shall be placed in the to: field; b) the SIM MESSAGE from: field is derived from the mapping procedures used in a point-to-point call above. The calling MCData User Identity or the Functional Alias Identity is mapped to obtain the originating MSISDN in a Tel URI format; c) the appropriate MIME type(s) in the Content-Type header field; The Content-Type is always text/plain; d) an Accept-Contact header field with the IM feature-tag "+g.oma.sip-im"; e) a User-Agent header field to indicate the IM release version as specified in OMA-TS-SIMPLE_IM; f) a Request-Disposition header field with the value "no-queue", as specified in IETF RFC 3841 [17], in order to ensure the SIP MESSAGE request is not queued for delivery if the recipient is temporarily unreachable; and g) the contents of the Body set to the contents of the Short Message(s) formatted in appropriate MIME type based on received content in MCData SDS. Since an MCData SDS can contain up to 1 000 bytes there is an option of sending a large Instant Message. It is the responsibility of the IP-SM-GW to concatenate or crop the large Instant Message based on configuration. This is out of the scope of the present document. The IP-SM-GW will respond with a SIP Message 200 OK upon successful disposition of the message with the same Call-ID and Cseq as the original message for disposition correlation. A SIP 4xx or SIP 5xx response indicates that the message was not delivered successfully. A SIP 6xx response means it was delivered successfully but refused. In the direction of IP-SM-GW to IWF, the S-CSCF function shall: 1) send a SIP MESSAGE request as defined in IETF RFC 3428 [14]. The SIP MESSAGE shall contain a body, using the standard MIME header fields to identify the content; 2) the FA(164) corresponding to the MSISDN or Functional Number of the recipient. This element shall be placed in the to: field; 3) The SIP MESSAGE from: field is the originating MSISDN or originating EIRENE Functional Number in a Tel URI format; 4) the appropriate MIME type(s) in the Content-Type header field; The Content-Type is always text/plain; 5) a Request-Disposition header field with the value "no-queue", as specified in IETF RFC 3841 [17], in order to ensure the SIP MESSAGE request is not queued for delivery if the recipient is temporarily unreachable; and 6) the contents of the Body set to the contents of the Short Message(s) formatted in appropriate MIME type based on based on received content in GSM-R SMS. The S-CSCF of the IWF will respond with a SIP Message 200 OK upon successful disposition of the message with the same Call-ID and Cseq as the original message for disposition correlation. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 60 A SIP 4xx or SIP 5xx response indicates that the message was not delivered successfully. A SIP 6xx response means it was delivered successfully but refused. Table 9.2.1-1 describes the information elements sent from the MCData server to the IWF for the MCData standalone data request (defined in ETSI TS 123 282 [i.7], clauses 7.4.2.2.2 and 7.4.2.3.2). Table 9.2.1-1: IWF MCData standalone data request MCDATA SDS Information element Instant Message Parameter Status Description MCData ID SIP Tel URI in from: field M The identity of the MCData user sending Functional alias SIP URI (EIRENE) in from: field O The associated functional alias of the MCData user sending data MCData ID SIP URI (MSISDN) In SIP MESSAGE to: field P-Asserted Identity M The identity of the MCData user towards which the data is sent Functional alias SIP URI (EIRENE)in to: field O The associated functional alias of the destination MCData user mapped from EIRENE Functional Number in IWF Conversation Identifier (see note) Call-ID M Identifies the conversation Transaction Identifier (see note) Identifies the MCData transaction Ignored by IWF Reply Identifier O Identifies the original MCData transaction to which the current transaction is a reply to Disposition Type O GSM-R SMS supports delivery disposition only Payload MIME message body M SDS Content Application identifier (see note) O Not applicable to FRMCS M SDS content NOTE: A reserved value of the Information Element needs to be defined which indicates that the sender does not support this Information Element. Table 9.2.1-2 describes the information elements sent from the IWF to the MCData server for the MCData data disposition notification (defined in ETSI TS 123 282 [i.7], clauses 7.4.2.2.2 and 7.4.2.3.2). Table 9.2.1-2: IWF MCData data disposition notification Information element Status Description MCData ID M The identity of the MCData user towards which the notification is sent MCData ID M The identity of the MCData user sending notification Conversation Identifier (see note) M Identifies the conversation associated with SIP MESSAGE Call-ID Disposition association M Identity of the original MCData transaction Disposition M Disposition which is delivered or read or both (only delivery is supported in GSM-R) NOTE: A reserved value of the Information Element needs to be defined which indicates that the sender does not support this Information Element. For both the point-to-point text messaging GSM-R SMS to MCData service user and the vice versa MCData short message to GSM-R Subscriber, the addressing framework as described in clause 6 shall be used. The interworking framework utilizes the IWF-g5 reference on the GSM-R side and the IWF-2 reference point on the FRMCS side as depicted in Figure 5.1-1. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 61 9.3 One-to-One text messaging protocols IWF to/from the MCData server In the direction of MCData server to IWF Gateway The MCData server shall send a SIP MESSAGE request for standalone SDS for terminating GSM-R subscriber. This SIP MESSAGE request is routed to the IWF GW with 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.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field. This URN indicates that the device has the capabilities to support the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service. This URN is also used by the device to associate a SIP request with the Mission Critical Data (MCData) Short Data Service (SDS) IMS communication service. This SIP MESSAGE is routed to the MCData client with 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.mcdata.sds", and an ICSI value "urn:urn-7:3gpp- service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field, and with an application/vnd.3gpp.mcdata-signalling MIME body containing an SDS NOTIFICATION message. If the IWF Gateway is unable to process the request due to a lack of resources or a risk of congestion exists, the IWF Gateway may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The IWF Gateway may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261[16] and skip the rest of the steps. The IWF Gateway shall determine the MCData ID of the calling user from the user identity in the P-Asserted-Identity header field of the SIP MESSAGE. The IWF Gateway shall perform the mapping of the MCData ID of the calling user to a GSM-R identity in the same manner as described in the Point-to-Point call procedures above. If the IWF Gateway cannot find a mapping between a GSM-R identity and an MCData ID, then IWF Gateway shall reject the SIP MESSAGE 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.9 of ETSI TS 124 282 [9] and shall not continue with any of the remaining steps. When the SDS message is successfully sent to the GSM-R side and a delivery disposition is received, the IWF shall send to the MCData server a SDS Notification message with the following information elements as described in ETSI TS 124 282 [9]. In order to generate an SDS notification, the IWF Gateway: 1) shall generate an SDS NOTIFICATION message as specified in clause 15.1.5 of ETSI TS 124 282 [9]; and 2) shall include in the SIP request, the SDS NOTIFICATION message in an application/vnd.3gpp.mcdata- signalling MIME body as specified in clause E.1 of ETSI TS 124 282 [9]. When generating an SDS NOTIFICATION message as specified in clause 15.1.5 of ETSI TS 124 282 [9], the MCData client: 1) if sending a delivered notification, shall set the SDS disposition notification type IE as "DELIVERED" as specified in clause 15.2.5 of ETSI TS 124 282 [9]; 2) if the SDS message could not be delivered to the user or application (e.g. due to lack of storage), shall set the SDS disposition notification type IE as "UNDELIVERED" as specified in clause 15.2.5 of ETSI TS 124 282 [9]; 3) shall set the Date and time IE to the current time to as specified in clause 15.2.8 of ETSI TS 124 282 [9]; 4) shall set the Conversation ID to the value of the Conversation ID that was received in the SDS message as specified in clause 15.2.9 of ETSI TS 124 282 [9]; 5) shall set the Message ID to the value of the Message ID that was received in the SDS message as specified in clause 15.2.10 of ETSI TS 124 282 [9]; ETSI ETSI TS 103 792 V1.1.1 (2026-01) 62 6) shall not include an Application ID IE (as specified in clause 15.2.7 of ETSI TS 124 282 [9]) and shall not include an Extended application ID IE (as specified in clause 15.2.24 of ETSI TS 124 282 [9]). In the direction of IWF to MCData server, the IWF Gateway shall 1) shall determine the public service identity of the called MCData user associated with the mapped identity in the received SIP MESSAGE request from the SM-IW-GW. The mapping procedure is identical to that of point-to-point call as described above; 2) shall generate an SDS SIGNALLING PAYLOAD message in the application/vnd.3gpp.mcdata-signalling MIME body as specified in clause 15.1.2 of ETSI TS 124 282 [9]; 3) shall generate a DATA PAYLOAD message as specified in clause 15.1.4 of ETSI TS 124 282 [9]; 4) shall include in the SIP request, the SDS SIGNALLING PAYLOAD message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in clause E.1 of ETSI TS 124 282 [9]; and 5) shall include in the SIP request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in clause E.2 of ETSI TS 124 282 [9]. When generating an SDS SIGNALLING PAYLOAD message as specified in clause 15.1.2 of ETSI TS 124 282 [9], the MCData client: 1) shall set the Date and time IE to the current time as specified in clause 15.2.8 of ETSI TS 124 282 [9]; 2) shall set the Conversation ID IE to a newly generated Conversation ID value as specified in clause 15.2.9 of ETSI TS 124 282 [9]; 3) shall set the Message ID IE to a newly generated Message ID value as specified in clause 15.2.10 of ETSI TS 124 282 [9] 4) shall not include an Application ID IE as specified in clause 15.2.7 of ETSI TS 124 282 [9] and shall not include an Extended application ID IE as specified in clause 15.2.24 of ETSI TS 124 282 [9]; 5) shall include a SDS disposition request type IE set to "DELIVERY" as specified in clause 15.2.3 of ETSI TS 124 282 [9]; When generating an DATA PAYLOAD message for SDS as specified in clause 15.1.4 of ETSI TS 124 282 [9], the IWF Gateway: 1) shall set the Number of payloads IE to 1, as specified in clause 15.2.12 of ETSI TS 124 282 [9]; 2) shall include the Security parameters and Payload IE with security parameters as described in ETSI TS 133 180 [13] 3) shall set the Payload content type as "TEXT" as specified in clause 15.2.13 of ETSI TS 124 282 [9]; 4) shall include the data to be sent in the Payload data. When the SDS message is successfully sent to the MCData server and a delivery disposition is expected, the MCData server will send to the IWF a SDS Notification message with the information elements as described in ETSI TS 124 282 [9], clause 6.2.2.1 [9]. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 63 Annex A (informative): Voice transcoding to and from AMR-WB when AMR-WB is not supported by a GSM-R system A.1 Introduction This annex identifies a set of technical approaches to ensure transcoding between G.711 and FRMCS codec to enable a call involving FRMCS users served by a FRMCS Domain and GSM-R users served by a GSM-R system when GSM-R system does not support the FRMCS codec or transcoding between AMR-WB and G.711. A.2 Transcoding in a GSM-R system In this clause, the FRMCS Operator is assumed to also operate a GSM-R system which is able to do the transcoding. The transcoding from the FRMCS codec to the GSM-R codec would take place as described in clause 7.2.8 with the GSM-R system being the GSM-R system associated to the FRMCS operator. Subsequently, the call path would be completed through the interconnection between the two GSM-R systems. A.3 Implementation of transcoding in the FRMCS Domain The FRMCS Operator may implement a transcoding function within FRMCS Domain. The transcoding function performs transcoding between the FRMCS codec and the G.711 codec used at the interface to the GSM-R System. The transcoding function could take different forms such as a MGCF/MGW combination, the usage of the MCX MDF or the IWF itself. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 64 History Version Date Status V1.0.0 July 2025 SRdAP process EV 20251008: 2025-07-10 to 2025-10-08 V1.1.1 January 2026 Publication |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 1 Scope | The present document defines all common ITS Release 2 terms, symbols and abbreviations ensuring consistency and compliancy for the ETSI ITS Release 2 specifications. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 2 References | |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 2.1 Normative references | Normative references are not applicable in the present document. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ISO 26262-1 (2018): "Road vehicles — Functional safety — Part 1: Vocabulary". [i.2] ISO 1176:1990: "Road vehicles — Masses — Vocabulary and codes". [i.3] Recommendation ITU-T X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". [i.4] Directive 2010/40/EU of the European Parliament and of the Council of 7 July 2010 on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport Text with EEA relevance. [i.5] Directive (EU) 2023/2661 of the European Parliament and of the Council of 22 November 2023 amending Directive 2010/40/EU on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport. [i.6] ISO 21448 (2022): "Road vehicles — Safety of the intended functionality". [i.7] Recommendation ITU-T I.350: "General aspects of quality of service and network performance in digital networks, including ISDNs". [i.8] World Geodetic System 1984 (WGS84). [i.9] ISO/IEC TS 5723:2022: "Trustworthiness — Vocabulary". ETSI ETSI TR 103 902 V2.1.1 (2026-01) 7 |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3 Definition of terms, symbols, and abbreviations | |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1 Terms | |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.0 Introduction | For the purposes of the present document, the following terms apply. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.1 A | absolute accuracy: degree to which a measurement, or the position of an object, precisely corresponds to its true, real- world location within an established coordinate system NOTE: It answers the question: "How close is this measurement to the actual, known position in the real world?". access layer: ITS layer composed of the OSI model physical and data link layers accuracy: performance criterion that describes the degree of correctness with which a function is performed NOTE 1: The function may or may not be performed with the desired speed. NOTE 2: It is defined in Recommendation ITU-T I.350 [i.7]. agile methodology: approach development method seeking for continuous delivery of working functionalities created in rapid iterations NOTE 1: It is the ability to create and respond to change. It is a way of dealing with, and ultimately succeeding in, an uncertain and turbulent environment. NOTE 2: See https://www.agilealliance.org/agile101/. anycast: delivery of data to any node out of a group of nodes, typically the one nearest to the source using a one-to-one- of-many associations where datagrams are routed to any single member of a group of potential receivers that are all identified by the same destination address NOTE: The routing algorithm selects the single receiver from the group based on which is the nearest according to some distance or cost measure. application: process (often implemented as software program) which processes technical input information and provides a functional result which delivers a user service to a user NOTE: In an ITS-S, applications may have sourcing parts sharing their information with sinking parts in other ITS-Ss. area of relevance: geographical zone in which the information disseminated is of relevance architecture: abstract representation of a communication system architecture enterprise: architecture of a complete organization, a top-level architecture NOTE: It recognizes general aspects, mission, objectives, organization considering common aspects often identified as part of Ecosystem requirements. architecture functional: architecture describing the purpose of a design architecture solution: architecture describing what functionalities a specific system needs to perform NOTE: It is a description of the functionalities needed to meet the functional objectives (services) meeting the Ecosystem requirements, the logic that governs them, and the information associated with them. Within ITS reference is made to the functional architecture of an application or a system. It is specific for the system and therefore relevant for profiling but not for functionality standardization. ETSI ETSI TR 103 902 V2.1.1 (2026-01) 8 architecture technical: technical architecture providing descriptions of technical components; their relations and the data associated with them NOTE: At the higher level, the technical architecture shows the relations of software and hardware architectures and can have a direct relation with solution architectures when considering systems. automated system: computer (ICT) system that collects information and can react and perform tasks based on the data NOTE: Automated systems are made using three components: Sensors. Microprocessors. Actuators. awareness area: geographic area in which information concerning the event is potentially applicable for use or for further distribution. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.2 B | backward compatibility of a system: property according to which an ITS-S based on Release x+1 (Rx+1) system is able to obtain the same level of service of a Rx station in an environment based on Rx. NOTE 1: Cooperative Intelligent Transportation Systems (C-ITS) supporting ITS-S based on Rx are able to maintain their full functionality in an environment based on Rx+1 NOTE 2: This definition is a technical translation of the original requirement which comes from the EU ITS regulation Directive 2010/40/EU [i.4] defined in article 4, compatibility as "the general ability of a device or system to work with another device or system without modification". In the Annex II of the Directive 2010/40/ EU [i.4], the ITS backward compatibility is identified as "ensuring, where appropriate, the capability for ITS systems to work with existing systems that share a common purpose, without hindering the development of new technologies". These have been increased clarified in Directive 2023/2661/EU [i.5]. NOTE 3: A Release x+1 ITS-S can provide additional services not available in Rx. backward compatibility of encoded protocol: property according to which changes made to an ASN.1 module directly or indirectly modify a type representing a protocol (of encoded protocol) data unit only in such a way that the new version of the modified type is not "extension-related" to the older version of the type according to Recommendation ITU-T X.680 [i.3] NOTE: This means that the protocol data unit encoded according to the new version of the module cannot be decoded according to the previous version(s) of the same module. backward compatibility in ASN.1 encoding: property according to which changes made to a module potentially do not affect the IMPORT statement of other modules such that the compiler will produce errors when compiling those modules together with the new version of the revised module Basic Set of Applications: group of applications, supported by the vehicular communication system bounding box: rectangular shape covering all parts of an empty load vehicle projected from top view broadcasting: communication capability which denotes unidirectional distribution from a single source to all users connected to the network. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.3 C | C-ITS ecosystem: Cooperative ITS specific ecosystem C-ITS functionality: functionality which complies to C-ITS Ecosystem requirements ETSI ETSI TR 103 902 V2.1.1 (2026-01) 9 classification confidence level: measure related to the certainty, generally a probability, with which a perceived object can be linked to a specific object class or type (e.g. with X % probability the object is of type A) NOTE: The sum of the object classification confidence levels for each perceived object may not exceed 100 % (e.g. in the example above, the classification confidence for an object to be of type B will not exceed (100-X) %). communication flows: data path the information follows through ITS from the source ITS-S to the sinking ITS-Ss or within an ITS-S component: concrete part or element that contributes to the function of a larger system, including hardware (like CPUs and hard drives), software (such as operating systems and applications), and other elements like data, procedures confidence: degree of certainty or trust in the given information or parameter confidence level: probability with which the estimate of a statistical parameter (e.g. an arithmetic mean) in a sample survey is also true for the entire population from which the samples were taken confidence value: estimated absolute accuracy of a measured value of a parameter with a specified confidence level (generally 95 % in the present document) confidence interval: range of values, calculated from sample data, that is likely to contain the true population parameter Cooperative Intelligent Transportation Systems (C-ITS): Intelligent Transportation Systems in which ITS stations share information in a non-discriminating manner and without costs, allowing road users to realize safety relevant and traffic efficiency related information for all benefit NOTE: The European legal definition is provided by the Regulation Directive 2010/40/EU [i.4]. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.4 D | data element: data type that contains one single data data frame: data type that contains more than one data element in a predefined order destination area: geographical area in which the message is intended to be disseminated NOTE: In case of intended, then it is the target destination area. direct V2X (Short V2X): vehicle to everything interface used for localized data exchange directly between data sourcing ITS-Ss and data sinking ITS-Ss, without involvement of intermediary IP networks, base-stations or routing functions such as Internet documents: within the context of standardization these are ENs, ESs, EGs, TSs, TRs, SRs, GSs and GRs domain: area of interest NOTE: In case used in the context of communications, it refers to any group of users, workstations, devices, printers, computers and database servers that share different types of data via network resources. downstream traffic: portion of road traffic in a given direction that is beyond (past) a certain point and is going away from it driver awareness zone: area in which the driver will be informed about upcoming situations |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.5 E | ecosystem: concept in which technical systems e.g. information, technologies, applications, are considered in their user and environmental context e.g. policies, strategies, and organizational processes empty vehicle: complete vehicle kerb mass as defined in ISO 1176 [i.2], clause 4.6 entity: abstract thing that exists, did exist, or can possibly exist, including associations among these things ETSI ETSI TR 103 902 V2.1.1 (2026-01) 10 equivalent bandwidth: computed value coming from a computation of relevant statistical properties of the traffic source (e.g. Markov-modulated arrivals, moment generating functions, or large-deviation techniques), ensuring that the probability of exceeding resource limits remains below a defined threshold NOTE: Equivalent bandwidth originates from wired networks and refers to the bandwidth that a given service effectively requires to meet its QoS constraints. event: road hazard, driving environment, or traffic condition event reference position: position that is used as a reference to describe the location of the event extra ITS: external ITS-S communication using a non-interoperable ITS or interference from non-ITS sources, also inter ITS |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.6 F | facilities layer: ITS layer representing the OSI layers five, six and seven layers facility: functionality, service or data provided by the ITS facilities layer farm animal: animal living under the supervision of an owner forwarding (ITS-S): Intelligent Transport System Station (ITS-S) that forwards messages according to any specific protocol function: self-contained element that accomplishes a specific technical task. Functions usually "take in" data, process it, and "return" a result and are realized by an entity functional safety: absence of unreasonable risk due to hazards caused by malfunctioning behaviour of electrical or electronic systems NOTE: For Road Vehicles Functional Safety ISO 26262-1 [i.1] applies. functionality: abstraction of a collection of functions realizing a specific functional process and can be realized by one or more components and/or processes. Proving a service to other functionalities, users or systems |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.7 G | Void. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.8 H | heading: orientation of the horizontal velocity vector with respect to the WGS84 [i.8] North (clockwise), unless otherwise noted horizontal speed: magnitude of horizontal velocity-vector of the reference position point horizontal velocity vector: projection of the 3D velocity vector on the WGS84 [i.8] ellipsoid |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.9 I | in radio media: distribution of information to a dispersed audience via any electronic mass communications medium, but typically one using the electromagnetic spectrum (radio waves), in a one-to-many model indirect V2X: vehicle to everything interface that uses IP-based protocols over a cellular/mobile and of fixed line network for the data exchange between ITS-Ss and between ITS-Ss and service providers information: data with specific meaning innovation cycle: continuous cycle of product discovery, development and commercialization that enables companies to keep reinvesting in the next generation of technology ETSI ETSI TR 103 902 V2.1.1 (2026-01) 11 Intelligent Transport Systems (ITSs): Systems that integrate information and communication technologies with transport infrastructure and vehicles to improve safety, efficiency, and sustainability in transport networks NOTE 1: A system in which ITS Stations (ITS-S) exchange information. NOTE 2: The European legal definition is provided by European Regulation Directive 2010/40/ EU [i.4]. interface: medium through which components or systems exchange data interoperability: ability of systems to exchange information and to make mutual use of the information that has been exchanged NOTE: The European legal definition is provided by European Regulation Directive 2010/40/EU [i.4]. intra ITS: internal ITS communication using interoperable ITS ITS application: functionality providing a service to an ITS-S external user. NOTE1: This could be an HMI functionality communicating with the driver or an automated system, or a functionality detecting road transport specific events and triggering the dissemination of a message or messages for the purpose of informing applications at syncing ITS-Ss NOTE 2: The European legal definition for the syncing applications is provided by European Regulation Directive 2010/40/ EU [i.4]. ITS common data dictionary: repository of the commonly data elements and data frames used in the ITS applications and ITS facilities layer ITS Constellation (ITS-C): group of ITS-Ss which actively exchange information ITS domain: everything what can be considered part of ITS including ITS/ITSC elements specified in ITS/ITSC standards and by relevant regulations ITS ecosystems: all ITS Ecosystems excluding all defined ITS Ecosystems such as the C-ITS Ecosystem ITS messages: data frames including ITS information which are generated and disseminated by ITS-S and exchanged between ITS-Ss ITS service: service provided by an ITS application to an end user or automated system outside ITS (considering ITS in the overall equipment context) NOTE: The European legal definition is provided by European Regulation Directive 2010/40/ EU [i.4]. ITS-S service: facilities Layer functionality which provides a service to applications by generating or processing data, triggered by an application, provided by or gathered from other ITS-S Services or from lower layers NOTE: A Facilities Layer service could also execute control functions for the support of the operation of other ITS-S services or applications. ITS station (ITS-S): functional entity specified by the ITS station (ITS-S) reference architecture realizing ITS specific services |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.10 J | Void. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.11 K | Void. ETSI ETSI TR 103 902 V2.1.1 (2026-01) 12 |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.12 L | layering: organization of functionalities that interact in some sequential and hierarchical way, with each layer usually providing a service for the layer above Local Dynamic Map (LDM): ITS-S service which stores and maintains Data Objects that are timestamped and location referenced as long as relevant for the ITS-S functionalities logic: logical representation low-risk geographical area: area part of the road infrastructure where the safety related traffic context is relaxed |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.13 M | minimum dissemination area: minimum area where an information is disseminated by an ITS-S based on application requirements misbehaviour: act by which a C-ITS station transmits false or misleading information, or information that was not authorized by a commonly agreed policy, either purposefully or unintendedly Multi-Modal: Multimodal transport (also known as combined transport) is the transportation of goods or people realized by least two different modes of transport multicast: delivery of a message to a group of nodes that have expressed interest in receiving the message using a one- to-many-of-many or many-to-many-of-many associations; datagrams are routed simultaneously in a single transmission to many recipients NOTE: Multicast differs from broadcast in that the destination address designates a subset, not necessarily all, of the accessible nodes. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.14 N | networked V2X (V2N2X): data exchange in which the data sourcing ITS-Ss provides the data to intermediary networks, base-stations or routing functions such as Internet, which transfers it to the interested data sinking ITS-Ss networking configuration: method in which there is a process of assigning network settings, polities, flows and controls NOTE: This process could be physically or virtual. IP networks are configuration based. networking constellation: method in which there is no configuration process but where the network settings, policies, flows and controls are commonly agreed Networking & Transport Layer: ITS layer representing the OSI layers three and four non-reversible countermeasures: measures that are taken to limit the impact on personal wellbeing and limit the material damage leading to a situation that is different from the intended one |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.15 O | object: material thing that can be seen and touched and therefore detected and with which parameters can be associated that can be measured and/or estimated object list: collection of objects originating ITS-S: Intelligent Transport System Station that generates messages and implements the related message protocol ETSI ETSI TR 103 902 V2.1.1 (2026-01) 13 |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.16 P | party: singular individual, stakeholder, organization, governmental institution or business entity. It is sole responsible plane: logical grouping of functions in a networking context, over different layers NOTE: The main planes recognized are the management or control plane, the data plane, and the security plane. prescriptive document: document that specifying specific requirements to which other documents within a certain context need to comply to private organizations: organizations which are owned, controlled and managed by individuals, groups or business entities public organizations: organizations which are owned, controlled and managed by governmental or other state or locally managed bodies |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.17 Q | Void. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.18 R | receiving ITS-S: Intelligent Transport System Station that receives messages and implements the relevant specific protocol reference direction: direction which is used as reference to indicate the applicability of the event release: handover of a consistent set of specifications at a defined level of maturity relevance zone: area where the information is applicable |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.19 S | safety of the intended functionality: absence of unreasonable risk due to hazards resulting from functional insufficiencies of the intended functionality or by reasonably foreseeable misuse by persons NOTE: For Road Vehicles, Safety of the Intended Functionality ISO 21448 [i.6] applies. safety related: everything which can have a direct or indirect positive impact on the safety situation. NOTE 1: Direct (tactical) in terms of having a direct impact on the cause of action as a response to immediate situations. Indirect (strategical) in terms of bringing awareness about possible upcoming safety situations to be managed NOTE 2: This includes preventive measures like traffic lights. service: process which processes technical input information and provide a technical result NOTE: In case this is a translation from technical values in other technical values e.g. Decentralized Environmental Notification Service (DENS) it acts as a facilities layer service. In case input information is technical or functional but at least represents functional aspects the service includes both application layer as well as facilities layer entities e.g. Cooperative Awareness Service (CAS). service access point: access point between layers via interfaces are realized connecting entities from different layers NOTE: These could be connections between entities of the same but also between entities of different functionality. service animal: animal which supports a specific service to a human, like a guiding dog or a police horse without person ETSI ETSI TR 103 902 V2.1.1 (2026-01) 14 sink: type of computer program or device that collects, stores and possibly processes data from other devices, programs or sources NOTE: It can be thought of as a destination point for data, where it is stored and processed for later use. sinking applications: application that only consumes information from other applications source: location where data originates from NOTE 1: A data source may be the initial location where data is born or where physical information is first digitized. NOTE 2: Even the most refined data may serve as a source, as long as another process accesses and utilizes it. sourcing applications: application that only provides information to other applications specifications: documents including normative measurable requirements for the interoperable implementation or testing of functions and functionalities state space representation: mathematical description of a detected object consisting of state variables such as position, velocity, attitude, angular rate, etc. strategical: information which brings awareness about possible upcoming safety situation to be managed NOTE: There is no direct impact. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.20 T | tactical: information or processes which have direct impact on the cause of action as a response to trust domain: defined scope (logical, organizational, technical or regulatory) within which entities adhere to common trust assumptions, policies, technical specifications, and validation/identity standards trust model: arrangement of entities and the trust relationships between them that define how trust is established and evaluated in a given context trust/trustworthiness: ability to meet stakeholders' expectations in a verifiable way NOTE: Source ISO/IEC TS 5723 [i.9]. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.21 U | unicast: delivery of a data frame to a single specific node using a one-to-one association between a sender and destination: each destination address uniquely identifies a single receiver endpoint upstream traffic: portion of road traffic in a given direction that has not yet arrived at a certain point and is going towards it user: human, animal, technical system e.g. automation system user services: service provided by an application to the user |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.22 V | Vehicle-to-Everything (V2X): endpoint to endpoint communication such as Vehicle-to-Vehicle (V2V), Vehicle-to Infrastructure (V2I), Infrastructure-to-Vehicle (I2V) V-model: graphical representation of a systems development lifecycle NOTE: See Wikipedia: https://en.wikipedia.org/wiki/V-model. velocity: vector indicating speed in a particular direction vertical velocity vector: projection of the 3D velocity vector on the normal vector of the WGS84 [i.8] Ellipsoid ETSI ETSI TR 103 902 V2.1.1 (2026-01) 15 |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.23 W | wild animal: animal living without any supervision |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.1.24 X - Z | Void. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.2 Symbols | Void. |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3 Abbreviations | |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.0 Introduction | For the purposes of the present document, the following abbreviations apply: |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.1 0-9 | 3GPP 3rd Generation Partnership Project 5G-NR 5th Generation New Radio |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.2 A | ADU Application Data Unit AI Artificial Intelligence AID Application IDentifier AIF Arbitration Inter-Frame AL Access Layer ALI Access Layer Instance ALN Access Layer Notifications API Application Programming Interface ASIL Automotive Safety Integrity Level ASN Abstract Syntax Notation ASN.1 Abstract Syntax Notation One AVM Automated Vehicle Marshalling |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.