hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4 GSM-R to FRMCS transition | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.1 GSM-R to FRMCS transition procedure | Precondition: • The On-Board FRMCS has received a Network Transition Trigger (NTT) indicating the Target FRMCS Transport Domain (identified by a PLMN ID). • The On-Board FRMCS has selected a Target On-Board FRMCS Radio Module. • For a given train, all running applications are served either by GSM-R or by FRMCS at a given time during the train journey. NOTE 1: The present document excludes the implementation scenario where at the given time during the train journey, some applications are running on GSM-R and some others are running on FRMCS. The following steps are undertaken: 1) The On-Board FRMCS shall perform the registration of the Target On-Board FRMCS Radio Module in the Target FRMCS Transport Domain (see ETSI TS 103 765-1 [1], clause 6.1). 2) The On-Board FRMCS shall perform transport path establishment on the Target On-Board FRMCS Radio Module to enable MC signaling towards the Target FRMCS Service Domain (see ETSI TS 103 765-1 [1], clause 6.2). ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 18 NOTE 2: If the Serving FRMCS Service Domain is not the Home FRMCS Service Domain, the On-Board FRMCS needs in the following step a transport path towards the Home FRMCS Service Domain (e.g. for the purpose of the HTTP exchanges with primary IdM server). 3) For each Loose-Coupled Application in Locally Bound state and identified as Type I or III in the FRMCS Railway On-Board Profile, the On-Board FRMCS shall execute the procedure identified in clause 7.1.4.2. 4) For each Loose-Coupled Application in Locally Bound state and identified as Type II in the FRMCS Railway On-Board Profile, if the On-Board FRMCS is entering a FRMCS Domain within the Domain of applicability of the application, the On-Board FRMCS shall perform the procedure identified in clause 7.1.4.3. 5) For each Loose-Coupled Application in Locally Bound state and identified as Type IV in the FRMCS Railway On-Board Profile, the On-Board FRMCS shall execute the procedure identified in clause 7.1.3.4. 6) For each Tight-Coupled Application in Locally Bound state, the On-Board FRMCS shall notify the application of the availability of the Target FRMCS Transport Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "ftdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.11) filled as follows: a) The ftdAVL field shall be set to TRUE. b) The nwTransition field shall be set to TRUE. c) The FrmcsDomain field shall be set to the PLMN ID representing the Target FRMCS Transport Domain. NOTE 3: The On-Board FRMCS needs to uniquely associate a Target FRMCS Service Domain to a Target FRMCS Transport Domain (PLMN ID) for the network transition points. NOTE 4: On-Board Tight-Coupled Application will need to uniquely associate a Target FRMCS Service Domain to a Target FRMCS Transport Domain (PLMN ID) for the network transition points. This is however out of scope of the present document and left to the discretion of the implementers of these applications. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.2 GSM-R to FRMCS transition: Type I or Type III applications | For each Loose-Coupled Application in Locally Bound state and identified as interoperable in any FRMCS Domain in the FRMCS Railway On-Board Profile, the On-Board FRMCS shall execute the MC Client readiness for network transition procedure as specified in clause 7.2.3 of the present document. 7.1.4.3 GSM-R to FRMCS transition: Type II applications entering the Domain of applicability For each Loose-Coupled Application in Locally Bound state and for which the On-Board FRMCS is entering a FRMCS Domain within the Domain of applicability of the application as identified the On-Board FRMCS shall execute the MC Client readiness for network transition procedure as specified in clause 7.2.3 of the present document. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.4 GSM-R to FRMCS transition: Type IV applications | For each Loose-Coupled Application in Locally Bound state and identified as Type IV in the FRMCS Railway On-Board Profile, if the application has at least one open session: 1) The On-Board FRMCS shall establish home-routed transport path on the On-Board Radio Modules (see ETSI TS 103 765-1 [1], clause 4.2.3 for relevant reference points). 2) The On-Board FRMCS recovers the ongoing MCData IPcon session towards Home FRMCS Service Domain on the transport path established in step 1. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 19 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2 Procedures not associated with a reference point | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.1 MC Client IP assignment procedure | Each MC Client is reachable via a unique IP address and port from the IP range SD_PUB_IP as described in ETSI TS 103 764 [i.6]. The On-Board FRMCS manages this public IP/port mapping to the private MC Client IP addresses from the IP range OB_PRV_IP as described in ETSI TS 103 764 [i.6]. The IP address assignment procedure shall ensure IP connectivity of the MC Service Client to the FRMCS Service Domain according to local IP network requirements. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.2 MC Client readiness procedure | The following steps are undertaken: 1) The On-Board FRMCS shall retrieve from FRMCS Railway On-Board Profile the following information: a) The mapping rule which allows to derive the MC User ID. b) The password credentials for this MC User ID. c) The scope associated to this MC User ID (as specified in ETSI TS 133 180 [12], clause B.4.2.2). d) The IMS/SIP credentials associated to this MC User ID in Serving and Home FRMCS Domain. 2) The MC Client shall execute the MC User registration procedure as specified in ETSI TS 103 765-2 [2], clause 6.1 using the retrieved parameters in step 1. Depending on whether this procedure is executed in Home FRMCS Domain or a Foreign FRMCS Domain, different subclauses of ETSI TS 103 765-2 [2], clause 6.1 are applied. 3) If the application is in the Application_Locally_Bound state, the On-Board FRMCS shall notify the application of the availability of the FRMCS Service Domain by sending a notification of type fsdAvlNotif on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: a) The fsdAVL field shall be set to TRUE. b) The nwTransition field shall be set to FALSE. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.3 MC Client readiness for network transition procedure | If the flag "IFSDT_DUAL_MCID_IN_PROGRESS" is not set in the application context within the On-Board FRMCS, the following steps are undertaken: 1) The On-Board FRMCS shall perform the "MC User registration" procedure in Target FRMCS Service Domain using the IMS credentials retrieved from the FRMCS Railway On-Board Application Profile. Depending on whether this procedure is executed in Home FRMCS Domain or a Foreign FRMCS Domain, different clauses of ETSI TS 103 765-2 [2], clause 6.1 are applied. If the procedure is unsuccessful, it shall be repeated every T_RETRY_MCUSR_REG seconds for a maximum of N_RETRY_MCUSR_REG times before it can be considered as a failure for the following steps. 2) If step 1 is successful, the On-Board FRMCS shall notify the application of the availability of the FRMCS Service Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotifData" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: i) The fsdAVL field shall be set to TRUE. ii) The nwTransition field shall be set to TRUE. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 20 3) If step 1 failed, the On-Board FRMCS shall notify the application of the unavailability of the Target FRMCS Service Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotifData" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: i) The fsdAVL field shall be set to FALSE. ii) The nwTransition field shall be set to TRUE. For a Loose-Coupled Application for which the FRMCS Railway On-board Profile includes the "IFSDT_ Dual_MCID" parameter, the FRMCS Railway On-Board Profile contains a second MC User ID (in Home FRMCS Service Domain) and its associated parameters for a given instance of application (single staticId). In the rest of the present clause, this second MC User ID is called the secondary MC User ID. If the flag "IFSDT_DUAL_MCID_IN_PROGRESS" is set in the application context within the On-Board FRMCS, the following steps are undertaken: 1) The secondary MC User ID (and associated parameters) shall be retrieved from the FRMCS Railway On-Board Profile. 2) If the Target FRMCS Service Domain is a Foreign FRMCS Service Domain, the On-Board FRMCS shall execute the procedure for MC User registration in Foreign FRMCS Service Domain, as specified in ETSI TS 103 765-2 [2], clause 6.1, using the parameters retrieved in step 1. Otherwise, if the Target FRMCS Service Domain is the Home FRMCS Service Domain, the On-Board FRMCS shall execute the procedure for MC User registration in Home FRMCS Service Domain, as specified in ETSI TS 103 765-2 [2], clause 6.1, using the parameters retrieved in step 1. If the procedure is unsuccessful, it shall be repeated every T_RETRY_MCUSR_REG seconds for a maximum of N_RETRY_MCUSR_REG times before it can be considered as a failure in step 4. 3) If step 2 is successful, the On-Board FRMCS shall notify the application of the availability of the FRMCS Service Domain by sending a notification of type fsdAvlNotif on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: a) The fsdAVL field shall be set to TRUE. b) The nwTransition field shall be set to TRUE. 4) If step 2 failed: a) The On-Board FRMCS shall notify the application of the unavailability of the FRMCS Service Domain by sending a notification of type fsdAvlNotif on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: i) The fsdAVL field shall be set to FALSE. ii) The nwTransition field shall be set to TRUE. b) The On-Board FRMCS shall unset the "IFSDT_DUAL_MCID_IN_PROGRESS" flag from the OBAPP application context. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.4 MC Client teardown procedure | The following steps are undertaken: 1) For each ongoing session associated with the application, the FRMCS Trackside Gateway shall notify the application of the termination of the session by sending a notification of type sessionClosure on the notification event stream associated with the application as specified in clause 7.3.3.5 of the present document. 2) For each ongoing communication associated to the MC Client, the ongoing communication release shall be performed as specified in clause 7.2.6. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 21 3) For each MC User associated with the application, the On-Board FRMCS shall execute the MC Service User deregistration procedure as specified in ETSI TS 103 765-2 [2], clause 6.3. 4) The On-Board FRMCS shall notify the application of the unavailability of the FRMCS Service Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotifData" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: a) The fsdAVL field shall be set to FALSE. b) The nwTransition field shall be set to TRUE if the release is due to a network transition. Otherwise, it is set to FALSE. 5) The FRMCS Trackside Gateway shall notify the application of its deregistration from the FRMCS Trackside Gateway by sending a notification of type upcomingDeregistration on the notification event stream associated with the application as specified in clause 7.3.3.5 of the present document. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.5 OBAPP Application Context clearance procedure | The following steps are undertaken: 1) If the application is a Loosed Coupled application, for each ongoing MCData IPcon session associated with the application, the On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The On-Board FRMCS shall clear the OBAPP Application Context associated with the OBAPP Application Tuple. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.6 Ongoing communication release procedure | The following steps are undertaken for releasing an ongoing communication associated to a Loose-Coupled application: 1) For an ongoing session associated with a Loose-Coupled application, the On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) In parallel to step 1, the On-Board FRMCS shall notify the application of the termination of the session by sending a notification of type sessionClosure on the notification event stream associated with the application as specified in clause 7.3.3.5. 3) The On-Board FRMCS shall release the transport path associated to the released MCData IPcon session as defined in ETSI TS 103 765-1 [1], clause 6.5. The following steps are undertaken for releasing an ongoing communication associated to a Tight-Coupled application: 1) For a Tight-Coupled Application, the On-Board FRMCS shall release the transport path associated to the ongoing communication as defined in ETSI TS 103 765-1 [1], clause 6.5. 2) The On-Board FRMCS shall notify the application of the unavailability of the FRMCS Transport Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "ftdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.11) filled as follows: i) The ftdAVL field shall be set to FALSE. ii) The nwTransition field shall be set to TRUE if the release is due to a network transition. Otherwise, it is set to FALSE. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.7 Logging | For all procedures specified in clause 7.3, the On-Board FRMCS shall log the endpoint invocations which lead to a HTTP status code 400, 401, 403 or 404. For all procedures specified in clause 7.3.2 (/sessions), the On-Board FRMCS shall log all endpoint invocations. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 22 For each logged event, the On-Board FRMCS shall capture: • Timestamp (ISO 8601 [14] as UTC). • Source IP and OBApp Application Tuple (appCategory, staticId). • HTTP method + endpoint + status code. • Specific parameters: - SessionId for session endpoints. The On-Board FRMCS shall not include sensitive information such as credentials or passwords in logged events. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3 Procedures associated with OBAPP endpoints | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.0 Introduction | The present clause specifies the behaviour expected from the On-Board FRMCS in relation with the OBAPP reference point as specified in FRMCS FFFIS-7950 [5]. For all OBAPP endpoint procedures defined below, the On-Board FRMCS shall return HTTP error responses as specified in FRMCS FFFIS-7950 [5] when encountering the following conditions applicable to a given endpoint and HTTP verb: • 400 Bad Request: Malformed/invalid request syntax. • 401 Unauthorized: Unauthenticated application access attempt. • 403 Forbidden: Authorized user but operation not permitted per profile. • 404 Not Found: Resource (dynamicId/sessionId/channel) not found. Additional specific behaviours are noted in individual procedures below. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1 /registrations endpoint procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1.1 Application registration procedure | Upon invocation of the "/registrations" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to create an OBAPP Application Context for the application. The following steps are undertaken: 1) If an OBAPP Application Context associated with OBAPP Application Tuple already exists in the On-Board FRMCS, the On-Board FRMCS shall execute the OBAPP Application Context clearance procedure as specified in clause 7.2.5. 2) The On-Board FRMCS shall create an OBAPP Application Context for the OBAPP Application Tuple. 3) The On-Board FRMCS shall set the application state to Application_Registered. 4) The On-Board FRMCS shall respond with a 201 Created response code as specified in FRMCS FFFIS-7950 [5], clause 9.10.1.2. The JSON structure being passed is of type "RegisteredData" with a newly generated DynamicID as specified in FRMCS FFFIS-7950 [5], clause 9.10.1.5. NOTE: For the Local Binding to be complete, the application is expected to open the notification event stream (clause 7.3.3.1). ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 23 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1.2 Application-initiated deregistration procedure | Upon invocation of the "/registrations/{dynamicId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clean up any context associated with the application. The following steps are undertaken: 1) For each ongoing MCData IPcon session associated with the application, the On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) For each MC Service User associated with the application, the On-Board FRMCS shall execute the MC Service User deregistration procedure as specified in ETSI TS 103 765-2 [2], clause 6.3. 3) In parallel to steps 1 and 2, the On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.10.2. 4) The On-Board FRMCS shall clear the OBAPP Application Context associated with the OBAPP Application Tuple. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2 /sessions endpoint procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.1 On-Board-FRMCS-initiated session initiation procedure | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to open a session towards a remote endpoint. In the rest of the present clause, the parameters communicationCategory, localAppIPAddress, and recipient (containing remoteId) are those retrieved from the JSON payload of request. The following steps are undertaken: 1) The On-Board FRMCS shall respond with a 201 (Created) response code and include a payload with the sessionId as specified in FRMCS FFFIS-7950 [5], clause 9.12.1. 2) If the MC Client readiness procedure has not been executed for the application, the On-Board FRMCS shall execute the MC Client readiness procedure as specified in clause 7.2.2. 3) The On-Board FRMCS shall retrieve: a) from the FRMCS Railway On-Board Profile: i) the destination MC Service User ID/Functional Alias associated to remoteId field of the OBAPP request; and ii) the Communication Session Category (ETSI TS 103 765-2 [2], clause 6.2.5) associated to communicationCategory field of the OBAPP request; b) the IP address provided by the application in the localAppIPAddress field of the OBAPP request. 4) The On-Board FRMCS shall execute the MCData IPcon session establishment procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.3 with the MC Service User ID/Functional Alias for the recipient(s) and the Communication Session Category determined at the previous step. If the FRMCS Railway On-Board Profile indicates that the recipient identifier determined at the previous step is a Functional Alias (FA), the On-Board FRMCS shall set the Functional Alias (FA) parameters for the procedure, as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3. NOTE 1: If the flag "IFSDT_DUAL_MCID_IN_PROGRESS" is set in the application context within the On-Board FRMCS, the MCData ID which is used as the originator of the session in this step is associated to the secondary MC User ID. 5) Upon the success of the procedure at step 4, the On-Board FRMCS shall set up a route for IP packets coming from the tunnel established at step 4 to the Local Application IP address provided in the JSON payload of the POST request. In addition, the On-Board FRMCS shall add the sessionId to the OBAPP Application Context. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 24 6) The On-Board FRMCS shall notify the application with a final answer on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "openSessionFinalAnswerNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1) filled as follows: i) Upon the success of the procedure at step 4, the openSessionFinalAnswerNotif is of type "success" with the following structure: 1) The sessionId field shall be set to the sessionId sent at step 1. 2) The nextHopIPAddress field shall be set to the local On-Board FRMCS IP address to be used by the application for the session. 3) The destApplicationIPAddress field shall be set to the virtual IP address representing the Trackside Application within the On-Board FRMCS for this OBAPP session. ii) Upon the failure of the procedure at step 5, the openSessionFinalAnswerNotif is of type "failed" with the following structure: 1) The sessionId field shall be set to the sessionId sent at step 1. 2) The ErrorCause field shall be set as in Table 7.3.2.1-1, depending on the error code and warning text within MCData IPcon response. 3) The ErrorDetail field can provide more details. NOTE 2: In case 3 from Table 7.3.2.1-1, the On-Board FRMCS can perform a number of retrials of MCData IPcon establishment before sending openSessionFinalAnswerNotif to the application. iii) If the procedure at step 4 indicates that the terminating application endpoint has declined the incoming session, the openSessionFinalAnswerNotif is of type "declined" with the following structure: 1) The sessionId field shall be set to the sessionId sent at step 1. 2) The ErrorCause field shall be set to REMOTE_ENDPOINT_DECLINED. 3) The ErrorDetail field can provide more details. Table 7.3.2.1-1: ErrorCause in openSessionFinalAnswerNotif Case Error code (and warning text) in MCData IPcon response ErrorCause in openSessionFinalAnswerNotif 1 480 ("FRMCS - terminating application is not locally bound") TERMINATING_APPLICATION_ENDPOINT_NOT_REACHABLE 2 408 ("FRMCS-Terminating application did not respond in time to session invitation") TERMINATING_APPLICATION_ENDPOINT_NOT_REACHABLE 3 408 (without the warning text in case 2) MCX_ENDPOINT_NOT_REACHABLE 4 403 ("FRMCS - terminating application is not allowed by profile to receive incoming session") TERMINATING_APPLICATION_ENDPOINT_NOT_ALLOWED |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.2 On-Board-FRMCS-initiated session termination procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to terminate the referred session. The following steps are undertaken: 1) The On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The On-Board FRMCS shall unset the route for IP packets coming from the tunnel established for the station towards the Local Application IP address associated with the session. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 25 3) If all the previous steps are successful, the On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.4. If an error occurs at the previous steps for which an error response has not been specified above, the On-Board FRMCS shall respond as indicated below. 4) If the flag "IFSDT_DUAL_MCID_IN_PROGRESS" is set in the application context within On-Board FRMCS, upon a successful execution of step 1: a) the On-Board FRMCS shall execute the MC Service User deregistration procedure as specified in ETSI TS 103 765-2 [2], clause 6.3; and b) the On-Board FRMCS shall unset the "IFSDT_DUAL_MCID_IN_PROGRESS" flag from the application context. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.3 On-Board-FRMCS-terminated incoming session invite procedure | NOTE 1: The present document only specifies the handling of incoming MCData IPcon session invites. Upon receipt of a "SIP INVITE request for IP Connectivity session for terminating MCData client" by the MC Client associated with a Loose-Coupled Application, the On-Board FRMCS is expected to notify the application. The following steps shall be undertaken: 1) If the application is not in the Application_Locally_Bound state, the On-Board FRMCS shall send a 480 (Temporarily Unavailable) response with the warning text equal to "FRMCS - terminating application is not locally bound" as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3 to reject the request. 2) If the parameters fetched from the FRMCS On-Board Application Profile indicate that the application is not allowed to receive incoming sessions, the On-Board FRMCS shall send a 403 (Forbidden) response with the warning text equal to "FRMCS - terminating application is not allowed by profile to receive incoming session" as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3 with warning text "FRMCS-Terminating application is not allowed to receive an incoming session" to reject the request. 3) The On-Board FRMCS shall notify the application of the incoming session request on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "incomingSessionNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1) filled as follows: i) The sessionId field shall be set to a new sessionId. ii) The remoteId field shall be set to the originating application identity value within the <application-data> attribute of the SIP INVITE received by the terminating MCData client. iii) The communicationCategory field shall be set to the value mapped to the <user-requested-priority> retrieved from the SIP INVITE. 4) The On-Board FRMCS shall start a timer T_INCOMING_SESSION associated with the application and the session. 5) If the timer T_INCOMING_SESSION set at step 4 expires before being cleared, the On-Board FRMCS shall send a 408 (Request Timeout) response with the warning text equal to "FRMCS-Terminating application did not respond in time to session invitation" as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3 to reject the request. NOTE 2: If T_INCOMING_SESSION is longer than SIP Timer B (64* timer T1 or about 32 seconds), the standard behaviour ETSI TS 124 229 [i.5] is presumed. If T_INCOMING_SESSION is shorter than SIP Timer B, the normative statement of step 5 applies. NOTE 3: The actual positive response to the SIP INVITE needs to be sent as part of the handling of the HTTP PUT verb on /sessions/{dynamicId}/{sessionId}in clause 7.3.2.4. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 26 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.4 On-Board-FRMCS-terminated incoming session response procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP PUT verb, the On-Board FRMCS is expected to provide a response to the "SIP INVITE request for IP Connectivity session for terminating MCData client" received prior. The following steps are undertaken: 1) The On-Board FRMCS shall clear the timer T_INCOMING_SESSION associated with the application and the session. 2) If the field incomingSessionAppResponse in the IncomingSessionNotificationResponseData JSON payload is set to "accepted": a) The On-Board FRMCS shall provide the MC Client associated with the application with the IP address provided by the application in the field localAppIPAddress. b) The MC Client associated with the application shall accept the SIP INVITE request as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3 and shall include the IP address provided at step 2.a as part of the <application-data> element within the AnyExt extension field. c) The On-Board FRMCS shall respond with a 201 (Created) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.5. 3) If the field incomingSessionAppResponse in the IncomingSessionNotificationResponseData JSON payload is set to "rejected": a) The MC Client associated with the application shall send a 603 (Decline) response as specified in ETSI TS 103 765-2 [2], clause 6.2.2.3 to reject the SIP INVITE request. b) The On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.5. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.5 On-Board-FRMCS-terminated session termination procedure | Upon receipt of a "SIP BYE" request for releasing an MCData IPcon session by the terminating MC Client associated with a Loose-Coupled Application, if there is a sessionId in OBAPP Application context associated to the MCData IPCon session and if the RELEASE_CAUSE in the SIP Reason header field of SIP BYE is set to 1 ("user ends call"): 1) The On-Board FRMCS shall notify the application of the termination of the session by sending a notification of type sessionClosure on the notification event stream associated with the application as specified in clause 7.3.3.5. 2) The On-Board FRMCS shall unset the route for IP packets coming from the tunnel established for the session towards the Local Application IP address associated with the session. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.6 Information query on ongoing sessions for an application | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide information on the ongoing sessions associated to the application. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.3. The JSON structure being passed is of type "SessionsListData" (as specified in FRMCS FFFIS-7950 [5], clause 9.12.3.2). |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.7 Information query on a specific ongoing session for an application | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide information on the designated session. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.2. The JSON structure being passed is of type "SessionStatusData" (as specified in FRMCS FFFIS-7950 [5], clause 9.12.2.2). ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 27 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3 /notifications endpoint procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.1 Procedure for opening the notification event stream | Upon invocation of the "/notifications/{dynamicId}/events" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to open an SSE notification stream towards the application. The following steps are undertaken: 1) The On-Board FRMCS shall register the notification types identified in FRMCS FFFIS-7950 [5], clause 9.11.1.2 in the OBAPP Application Context. NOTE: The notifications associated to an OBAPP session (i.e. OpenSessionFinalAnswerNotif, IncomingSessionNotif, and SessionClosureNotif) are only relevant to Loose-Coupled applications. 2) The On-Board FRMCS shall open a SSE event stream and respond with a 200 (OK) response code. 3) The On-Board FRMCS shall set the application state to Application_Locally_Bound. 4) If the application is a Loose-Coupled Application for which "On-Board-application-terminated sessions" are allowed in FRMCS Railway On-Board Profile and if the MC Client readiness procedure has not yet been executed for the application, the On-Board FRMCS shall execute the MC Client readiness procedure as specified in clause 7.2.2 of the present document. 5) If the application is a Loose-Coupled Application and the MC Client readiness procedure has been successfully executed for the application, the On-Board FRMCS shall notify the application of the availability of the FRMCS Service Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "fsdAvlNotifData" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.12) filled as follows: i) The fsdAVL field shall be set to TRUE. ii) The nwTransition field shall be set to FALSE. 6) If the application is a Tight-Coupled Application, the On-Board FRMCS shall notify the application of the availability of the FRMCS Transport Domain on the notification event stream associated with the application as specified in clause 7.3.3.5. The JSON structure being passed is of type "ftdAvlNotif" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.1.11) filled as follows: i) The ftdAVL field shall be set to TRUE. ii) The nwTransition field shall be set to FALSE. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.2 Procedure upon subscription to a channel | Upon invocation of the "/notifications/{dynamicId}/channels/{channel}" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to add the notification types associated with the requested channel to the list of notification types in the OBAPP Application Context. The following steps are undertaken: 1) The On-Board FRMCS shall register the notification types associated with the channel in the OBAPP Application Context. 2) The On-Board FRMCS shall respond with a 200 (OK) response code and include a payload with the subscriptionId as specified in FRMCS FFFIS-7950 [5], clause 9.11.3. NOTE: A specific procedure for the location channel is specified in clause 7.3.3.6. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 28 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.3 Procedure upon unsubscription from all channels | Upon invocation of the "/notifications/{dynamicId}/channels" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clear all subscription to notification types in the OBAPP Application Context, except for those identified in clause 7.3.3.1. The following steps are undertaken: 1) The On-Board FRMCS shall deregister all notification types in the OBAPP Application Context except for those identified in clause 7.3.3.1. 2) The On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.11.4. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.4 Procedure upon unsubscription from a channel | Upon invocation of the "/notifications/{dynamicId}/channels/{channel}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clear the subscription to notification types associated with the requested channel from the list of notification types in the OBAPP Application Context. The following steps are undertaken: 1) The On-Board FRMCS shall deregister the notification types associated with the channel in the OBAPP Application Context. 2) The On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.11.5. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.5 Procedure of notification to an application over a channel | The SSE data field shall be filled with the JSON data structure as passed to the procedure. EXAMPLE: For a successful final answer notification, the JSON data structure would be: { "openSessionFinalAnswerNotif": "success": { "sessionId": <data>, "nextHopIpAddress": <data>, "destApplicationIPAddress": <data> } } The SSE event and the SSE id fields shall not be used. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.6 Procedure upon subscription to location reporting channel | Upon invocation of the "/notifications/{dynamicId}/channels/location" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to add the notification types associated to the requested channel to the list of notification types in the OBAPP Application Context. The following steps are undertaken: 1) If the locReportType in the JSON payload of HTTP POST is set to travelledDistanceLocRep and the On-Board FRMCS does not support distance-based location report, the On-Board FRMCS shall respond with a 501 (Not Implemented) response code and skip the below steps. 2) The On-Board FRMCS shall register the notification types associated to the location reporting in the OBAPP Application Context. 3) The On-Board FRMCS shall respond with a 200 (OK) response code and include a payload with the locReportId as specified in FRMCS FFFIS-7950 [5], clause 9.11.3. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 29 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.7 Procedure to list subscriptions of an application | Upon invocation of the "/notifications/{dynamicId}/channels" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide a list of notifications to which application has subscriptions. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], clause 9.11.2.2. The JSON structure being passed is of type "SubscriptionsListData" (as specified in FRMCS FFFIS-7950 [5], clause 9.11.2.2). |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.8 Procedure to unsubscribe an application from a specific subscription | Upon invocation of the "/notifications/{dynamicId}/channels/{subscriptionId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to unsubscribe an application from a specific notification subscription. If the query is authorized, the On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.11.6.2. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.4 /versions endpoint procedure | Upon invocation of the "/versions" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide the list of versions it supports. The following steps are undertaken: 1) The On-Board FRMCS shall prepare an API VersionsData data structure with the list of versions supported as specified in FRMCS FFFIS-7950 [5], clause 9.6. 2) The On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], clause 9.6. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.5 /keepalive endpoint procedure | Upon invocation of the "/keepalive" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide a HTTP-level response to indicate the OBAPP reference point is responsive. The On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.13. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 30 History Version Date Status V1.0.0 July 2025 SRdAP process EV 20251008: 2025-07-10 to 2025-10-08 V1.1.0 November 2025 SRdAP process VA 20260106: 2025-11-07 to 2026-01-06 V1.1.1 January 2026 Publication |
05f8beb7977a67521a875d86df071465 | 103 792 | 1 Scope | The present document defines the functional model including reference points as well as the protocol and procedure for interworking between GSM-R R4 and FRMCS and covers the following services: • Group call. • Emergency group call. • Point-to-point call. • Text messaging Service. |
05f8beb7977a67521a875d86df071465 | 103 792 | 2 References | |
05f8beb7977a67521a875d86df071465 | 103 792 | 2.1 Normative 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. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. 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 are necessary for the application of the present document. [1] UIC FU-7120: "Future Railway Mobile Communication System - Functional Requirements Specification", Version 2.0.0 December 13th, 2024. [2] UIC FW-AT 7800: "Future Railway Mobile Communication System - System Requirements Specification", Version 2.0.0 December 13th, 2024. [3] UIC FIS-7970: "Future Railway Mobile Communication System - Functional Interface Specification", Version 2.0.0 December 13th, 2024. [4] ETSI TS 103 765-2: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building blocks and functions; Part 2: Service Stratum". [5] IETF RFC 8101: "IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service". [6] ETSI TS 103 389 (V3.4.1): "Rail Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways". [7] ETSI TS 123 228 (V18.9.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 18.9.0 Release 18)". [8] ETSI TS 129 379 (V18.0.0): "LTE; 5G; Mission Critical Push To Talk (MCPTT) call control interworking with Land Mobile Radio (LMR) systems; Stage-3 (3GPP TS 29.379 version 18.0.0 Release 18)". [9] ETSI TS 124 282 (V18.10.0): "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282 version 18.10.0 Release 18)". [10] ETSI TS 124 379 (V18.10.0): "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379 version 18.10.0 Release 18)". ETSI ETSI TS 103 792 V1.1.1 (2026-01) 9 [11] ETSI TS 123 283 (V18.3.0): "LTE; Mission Critical Communication Interworking with Land Mobile Radio Systems (3GPP TS 23.283 version 18.3.0 Release 18)". [12] ETSI TS 129 163 (V18.1.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 version 18.1.0 Release 18)". [13] ETSI TS 133 180 (V18.1.0): "LTE; Security of the Mission Critical (MC) service (3GPP TS 33.180 version 18.1.0 Release 18)". [14] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". [15] IETF RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)". [16] IETF RFC 3261: "SIP: Session Initiation Protocol". [17] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)". |
05f8beb7977a67521a875d86df071465 | 103 792 | 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] ETSI TR 103 768: "Rail Telecommunications (RT); Future Rail Mobile Communication System (FRMCS); Interworking study with legacy systems". [i.2] EIRENE System Requirements Specification, Version 16.1.0, February 2023. [i.3] ETSI TS 123 280 (V18.12.0): "LTE; Common functional architecture to support mission critical services; Stage 2". [i.4] ETSI TS 123 040 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Technical realization of the Short Message Service (SMS) (3GPP TS 23.040 version 18.0.0 Release 18)". [i.5] ETSI TS 123 002 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 18.0.0 Release 18)". [i.6] ETSI TS 123 379 (V18.12.0): "LTE; Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 (3GPP TS 23.379 version 18.12.0 Release 18)". [i.7] ETSI TS 123 282 (V18.10.0): "LTE; Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 (3GPP TS 23.282 version 18.10.0 Release 18)". [i.8] ETSI TS 143 068 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Voice Group Call Service (VGCS); Stage 2 (3GPP TS 43.068 version 18.0.0 Release 18)". [i.9] ETSI TS 123 236 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes (3GPP TS 23.236 version 18.0.0 Release 18)". [i.10] ETSI TS 129 311 (V18.0.0): "Universal Mobile Telecommunications System (UMTS); LTE; Service Level Interworking (SLI) for messaging services (3GPP TS 29.311 version 18.0.0 Release 18)". ETSI ETSI TS 103 792 V1.1.1 (2026-01) 10 [i.11] ETSI TS 124 229 (V18.7.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 18.7.0 Release 18)". [i.12] ETSI TR 103 791: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Terminology for FRMCS specifications". [i.13] ETSI TS 123 283 (V18.2.0): "LTE; Mission Critical Communication Interworking with Land Mobile Radio Systems (3GPP TS 23.283 version 18.2.0 Release 18)". |
05f8beb7977a67521a875d86df071465 | 103 792 | 3 Definition of terms, symbols and abbreviations | |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.12] and the following apply: E.164 SIP-R URI: SIP-R URI which describes an international E.164 address EIRENE SIP-R URI: SIP-R URI which describes an international EIRENE address FA(164): Functional Alias (FA) which takes the form of an E.164 SIP-R URI and is transmitted in MCX related messages, according to the transmission of FAs NOTE: As specified in ETSI TS 124 379 [10] and ETSI TS 124 282 [9]. FA(EIRENE): Functional Alias (FA) which takes the form of an EIRENE SIP-R URI and is transmitted in MCX related messages, according to the transmission of FAs NOTE: As specified in ETSI TS 124 379 [10] and ETSI TS 124 282 [9]. FRMCS Entity: entity which is either: a) a user of the MCX system; b) a user of a partner MC system of the MCX system; c) a group of users of the MCX system; d) a group of users of a partner MC system of the MCX system; e) a railway function that is registered or activated as FA at the MCX system; or f) a railway function that is registered or activated as FA at a partner MC system of the MCX system. GSM-R Entity: entity which is either GSM-R user, a GSM-R service or a railway function that is not an FRMCS entity identity and criteria mapping: local service of the IWF for mapping between identities and criteria achieved without requests from the IWF to external data bases or other remote storage (i.e. it is achieved by local address lookup or by rule-based rephrasing) local address lookup: local lookup of identity mappings within the IWF, e.g. by tables that have been setup during provisioning time rephrasing: rule-based mapping of EIRENE addresses to FRMCS FAs and vice versa NOTE: This rule-based rephrasing is based on FRMCS FRS [1]. subscribers: user identified by E.164 addresses. NOTE: This can mean: a) GSM-R subscribers; ETSI ETSI TS 103 792 V1.1.1 (2026-01) 11 b) Users of the MCX system; c) Groups of users of the MCX system. |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.2 Symbols | Void. |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AMR-WB Adaptative MultiRate-Wide Band CdA Called Address CgA Calling Address CHPC Confirmation of High Priority Call CSC Coding Scheme Code CT Call Type CT5 Call Type 5 ECT Explicit Call Transfer EIR Equipment Identity Register EIRENE European Integrated Railway Radio Enhanced Network ETSI European Telecommunications Standards Institute EVS-SWB Enhanced Voice Service - Super Wide Band FA Functional Alias FIS Functional Interface Specification FN Functional Number FRMCS Future Railway Mobile Communication System FRS Functional Requirement Specification FTS Fixed Terminal Subsystem GCR Group Call Register GCref Group Call Reference GID Group call Identity GPS Global Positioning System GSM Global System for Mobile communications GSM-R Global System for Mobile communications - Railways GW GateWay HLR Home Location Register IC International Code IE Information Element IETF Internet Engineering Task Force IM Intstant Messaging IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IP Internet Protocol IP-SM-GW IP Short Message Gateway ISC IP multimedia subsystem Service Control interface IWF InterWorking Function IW-GW InterWorking-GateWay MAP Mobile Application Part MC Mission-Critical MCData Mission-Critical Data MCPPT Mission Critical Push To Talk MCPTT Mission-Critical Push-To-Talk MCX Mission Critical communications MDF Media Distribution Frame MGCF Media Gateway Control Function MGW Media GateWay MIME Multipurpose Internet Mail Extensions ETSI ETSI TS 103 792 V1.1.1 (2026-01) 12 MS Mobile Station MSC Mobile Switching Centre MSS Mobile Switching Subsystem OIP Originating Identification Presentation OMA-TS Open Mobile Alliance-Technical Specification OTDI Originator To Dispatcher Information PABX Private Automatic Branch eXchange PAI P-Asserted Identity PFN Presentation Functional Number PTT Push-To-Talk REC Railway Emergency Call RFC Request For Comments RTCP Real time Ta S-CSCF Serving-Call Session Control Function SDP Session Description Protocol SDS Short Data Service SIM Subscriber Identity Module SIP Session Initiation Protocol SIP-R Session Initiation Protocol for Railways SLI Service Level Interworking SM Short Message SMPP Short Message Peer-to-Peer protocol SMS Short Message Service SMSC Short Message Service Center SRS System Requirement Specification TIP Terminating Identification Presentation TR Technical Report TS Technical Specification UE User Equipment URI Uniform Resource Identifier URN Uniform Resource Number VBS Voice Broadcast Service VGCS Voice Group Call Service XML eXtensible Markup Language |
05f8beb7977a67521a875d86df071465 | 103 792 | 4 Services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.1 General | This clause describes the services for interworking between GSM-R and FRMCS 3GPP MC systems supported in the present document. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.2 Group call | This clause describes group call services that are supported for groups defined on the MC system and groups defined on the GSM-R system. The following group call procedures are supported: • Initiation of a group call by a FRMCS user. • Initiation of a group call by a GSM-R user. • Late entry. • Termination of a group call. • Interworking of floor control on MCPTT with uplink control and dispatcher mute/unmute in GSM-R. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 13 • Interworking of the media codecs and encryption between GSM-R and MCPTT. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.3 Emergency group call | Emergency group calls, i.e. group calls with pre-emptive priority, are supported for the same cases as described in clause 4.2. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.4 Point-to-point call | The following point-to-point call procedures are supported: • Initiating a point-to-point call from a user on the GSM-R system to a user on the MC system. • Initiating a point-to-point call from a user on the FRMCS system to a user on the GSM-R system. • Interworking of the media codecs and encryption between GSM-R and MCPTT. • Termination of a point-to-point call. NOTE: Point-to-point calls for interworking are without floor control. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.5 Text messaging service | The GSM-R system includes Mobile Stations (MS) capable of performing various types of calls, such as voice and data calls, and also supports text messaging by enabling the transmission of Short Messages (SMs) between mobile stations. EIRENE System Requirements Specification [i.2] specifies that, whenever text messaging is implemented in the GSM-R network, the Short Message Service (SMS) - is to be used (see clause 12.2.1 of EIRENE System Requirements Specification [i.2]). The Short Message Service and Short Messages are defined in ETSI TS 123 040 [i.4]. The present document specifies Short Data Service (SDS) interworking between GSM-R users and MCData clients using one-to-one standalone SDS messages. The IWF behaves as a peer MCData server to other MCData servers for the FRMCS side and it implements the ISC interface as an S-CSCF, as the IP-SM-GW (SMS application server) is considered a part of the GSM-R side. When a GSM-R user attempts to send a GSM-R message to the MCData service, the IWF converts the Instant Message from the IP-SM Gateway into a request to send an MCData SDS message. When an MCData user sends an SDS message to the GSM-R system, the IWF converts the message to an Instant Message and converts the destination and originating address using the same mapping techniques as in point-to-point voice calls. The IWF then forwards the Instant Message via the IP-SM-GW to the GSM-R SMSC. NOTE: MCDATA SDS is limited to MCDATA SDS Text Messaging. |
05f8beb7977a67521a875d86df071465 | 103 792 | 5 Functional model | |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.1 Functional model description | The present document defines the reference points between the IWF and the FRMCS servers as well as the reference points between the IWF and the GSM-R nodes. Additionally, it defines the functionality of the IWF, which acts as an MC service server connected with the FRMCS MC service server utilizing the IWF-1 or IWF-2 reference points, including protocol translation, identity mapping, transcoding, routing and other functions, to be performed by the IWF between the reference points on the FRMCS MC service side and the GSM-R side and vice versa. The IWF provides centralized support for interworking between an MCPTT or MCData system and a GSM-R system. In MCPTT or MCData systems, the identity of a GSM-R user is provided as an MCPTT or MCData ID, and the identity of a GSM-R group is provided as a MCPTT or MCData group ID. The identity is used by the IWF to derive the corresponding identities used in the GSM-R system and vice versa. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 14 The IWF performs the identity mapping between an MCPTT system or MCData system and a GSM-R system during exchange of signalling and media messages. The IWF acts as MCX participating function in the context of GSM-R interworking. Figure 5.1-1 illustrates the functional model of the application plane for interworking between GSM-R, MCPTT, and MCData. Common services core Identity management server Group management server Configuration management server MCPTT server Key management server Location management server IWF IWF-1 MCData server IWF-2 IWF-3 MGCF MGW IWF-g1 IWF-g2 GSM-R MCX GCR IP-SM-GW IWF-g5 MSC server Figure 5.1-1: Interworking functional model This model is based on ETSI TS 123 283 [11]. The protocols used at any reference point exposed for MCPTT service interoperability with a FRMCS SIP core, are to be compatible with the protocols defined for the corresponding reference point defined in ETSI TS 123 002 [i.5]. |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2 Reference points | |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.0 General | The normative requirements placed on a FRMCS SIP Core are detailed in ETSI TS 103 765-2 [4]. The reference points only need to be derived from IMS specific reference points as shown in Table 5.2.0-1. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 15 Table 5.2.0-1: Proposed mapping of refence points on GSM-R side according to ETSI TS 129 163 [12] Original IMS reference point Derived IWF-gx reference point Mg/Mj IWF-g1 Mb IWF-g2 ISC IWF-g5 |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.1 Reference point IWF-1 (between the IWF and the MCPTT server) | The IWF-1 reference point, defined between the IWF and the MCPTT server, enables peer-to-peer interconnection between the GSM-R system and the MCPTT system. IWF-1 supports a subset of the MCPTT-3 functionalities as defined in ETSI TS 123 379 [i.6], with some differences detailed in the present document. The IWF-1 interface uses the same signalling plane protocol(s) defined for MCPTT-3. Additionally, floor control signalling and media are also transferred using the IWF-1 reference point. |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.2 Reference point IWF-2 (between the IWF and the MCData server) | The IWF-2 reference point, defined between the IWF and the MCData server, enables SDS interconnection between the GSM-R system and the MCData system. IWF-2 supports a subset of the functionalities of MCData-SDS-1 and MCData-SDS-2, as specified in ETSI TS 123 282 [i.7] with some differences as detailed in the present document. The IWF-2 interface uses the same signalling plane protocol(s) defined for MCData-3 except where otherwise detailed in the present document. 5.2.3 Reference point IWF-3 (between the IWF and the group management server) The IWF-3 reference point, defined between the IWF and the group management server, would enable group management interconnection between the GSM-R system and the MC service system. IWF-3 is based upon CSC-16, as specified in ETSI TS 123 280 [i.3]. IWF-3 is not used for interworking with GSM-R. 5.2.4 Reference point IWF-g1 (between the IWF and the MSC server/MGCF) The IWF-g1 reference point, defined between the IWF and the MSC server via MGCF, enables signalling plane for voice communication based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12]. Additional information on GCR from ETSI TS 143 068 [i.8]: "The general architecture of GSM is maintained. In addition, a network function is required which is used for registration of the group call attributes, the Group Call Register (GCR)". The IWF has no direct interface towards the GCR. NOTE: The GCR implementation is not specified. It is to be realized e.g. as a new network node, in a PABX directly attached to an MSC, inside an MSC or as an HLR. The interface between the GCR function and other functions is not specified in the GSM technical specifications. As a consequence, the functional split between MSC and GCR as developed in the present document is only indicative. The GCR data for a specific voice group call is set at the creation of the group call attributes and is to be subsequently modified. No support for these functions is specified in the GSM technical specifications. In a RANflex configuration as defined in ETSI TS 123 236 [i.9] with group call redundancy, GCRs associated to MSCs belonging to the same redundancy pool need to communicate with each other by means of SYNC_GCR messages. |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.5 Reference point IWF-g2 (between the IWF and MGW) | The IWF-g2 reference point, defined between the IWF and the MGW, would enable media plane protocol for voice communication. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 16 |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.6 Reference point IWF-g5 (between the IWF and IP-SM-GW) | The IWF-g5 reference point is defined between the IP-SM-GW on the GSM-R side and the IWF. If SIP interfaces are used, the IP-SM-GW on the GSM-R side converts the SMPP MAP protocol to SIP (ISC). |
05f8beb7977a67521a875d86df071465 | 103 792 | 6 Identities and addressing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.0 General | In the present document, the IWF provides network support for interworking between FRMCS and GSM-R for voice and messaging services. The IWF shall provide the following services: • Routing service(s) that can manage addressing. • Identity mapping service(s) that can manage a set of identities. The IWF is connected with: • MC Service Server(s) using IWF-1 and IWF-2; • MGCF using IWF-g1; and • IP-SM-GW using IWF-g5; to enable those routing services and identity mapping services (besides other services of the IWF). Clause 6 specifies the routing services and the identity mapping services of the IWF. Clause 6 refers to address parameters by generic parameter names, as identified in Table 6.0-1: Table 6.0-1: Used generic parameter names Generic Parameter Name Applicable Communication or Service Called Address Private Call, OIP, Messaging Calling Address Additional Calling Address Connected Address TIP, ECT, Conferencing User To User Information Presentation of FN Call History Info Call Diversion NOTE: Generic parameter names are introduced for the purpose of specifying identity mapping services in clause 6.3. The mapping between these generic address parameters and the protocol parameters at the various reference points are described in the stage 3 parts of the present document. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.1 Identity definitions | From a logical point of view, the IWF performs an identity mapping between the FRMCS reference points IWF-1/IWF-2 and the GSM-R reference points IWF-g1/IWF-g5. Figure 6.1-1 shows the location of the IWF between FRMCS Domains and GSM-R Domains. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 17 Figure 6.1-1: Domains involved in identity mapping Identity mapping refers to the mapping of protocol address parameters during the interworking of SIP calls and SIP messages between FRMCS domain(s) (i.e. the MCPTT/MCData system and its partner MC systems) and GSM-R domain(s) (i.e. the GSM-R core and other non-MC systems). The following identities shall be represented by protocol address parameters, at the reference points IWF-1, IWF-2, IWF-g1 and IWF-g5: • E.164 addresses specify addresses of subscribers. • EIRENE addresses specify addresses of railway functions. • MC service IDs specify the addresses of MCPTT or MCData users. • MC service group IDs specify the addresses of groups of MCPTT users. • FAs specify addresses of railway functions and can be rephrased as EIRENE addresses. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.2 Representation in interworking systems | E.164 SIP-R URIs and EIRENE SIP-R URIs shall be used at IWF-g1 and IWF-g5 to represent E.164 addresses and EIRENE addresses, respectively. MCX IDs and FAs shall be used at IWF-1 and IWF-2, as defined in the 3GPP MC standards. FA(164) and FA(EIRENE) shall be special FAs that are SIP URIs as defined in ETSI TS 103 389 [6], clause 6.3.6. The following set of identity types defined in Table 6.2-1 shall be applicable to the IWF identity mapping service(s). Table 6.2-1: Usage of identities at FRMCS and GSM-R reference points Identity Type Endpoint Identity example MC Service ID IWF-1/2 'sip:alice@mcx.railway.example.at MC Service Group ID IWF-1/2 'sip:grup.1900.200@mcx.railway.example.at FA(164) IWF-1/2 'sip:+991471154321@mcx.railway.example.at;user=phone' FA(EIRENE) IWF-1/2 'sip:04371234501@mcx.railway.example.at;user=gsmr' FA IWF-1/2 'sip:loc-12345.Control_1@0080' E.164 SIP-R URI IWF-g1/g5 'sip:+991471154321@ims.railway.example.at;user=phone' EIRENE SIP-R URI IWF-g1/g5 'sip:04371234501@ims.railway.example.at;user=gsmr' Clause 6.3 will describe the identity mapping by using the names of the generic address parameters. Protocol address parameters shall be referred to by the generic parameter names as defined in Tables 6.2-2 and 6.2-3. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 18 Table 6.2-2: Mapping of generic and protocol address parameters for MCPTT Generic Address Parameter Protocol Parameters, as Defined in Stage 3 Applicable SIP Message Endpoint IWF-1 Endpoint IWF-g1 Called Address, see note 1 <mcptt-request-uri> / <resources-list> Request URI INVITE request Calling Address, see note 2 <mcptt-calling-user-id> P-Asserted-Identity INVITE request Additional Calling Address, see note 3 <mcptt-calling-group-id> From INVITE request Connected Address <mcptt-called-party-id> P-Asserted-Identity reINVITE request UPDATE request 200 OK (INVITE) User To User Information (PFN) <functional-alias-URI> User-To-User (ETSI TS 103 389 [6]) INVITE request 180 Ringing Response 200OK(INVITE) response BYE request Call History Info <forwarding-immediate- list> <forwarding-other-list> History-Info (ETSI TS 103 389 [6]) INVITE request NOTE 1: At IWF-1, the Called Address can contain an MC Service ID, an FA, an FA(164) or an FA(EIRENE). NOTE 2: At IWF-1, the Calling Address can contain an MC Service ID. NOTE 3: The Additional Calling Address is relevant, if a group communication invites either a participant or another group communication. E.g. if a GSM-R VGCS/VBS invites an MCPTT user as participant, then the MGCF will send the CT5 number of the group call as an EIRENE SIP-R URI in the From header field. Table 6.2-3: Mapping of generic and protocol address parameters for MCData Generic Address Parameter Protocol Parameters, as Defined in Stage 3 Applicable SIP Message Endpoint IWF-2 Endpoint IWF-g5 Called Address, see note 1 <mcdata-request-URI> Request URI MESSAGE request Calling Address, see note 2 <mcdata-calling-user-id> P-Asserted-Identity MESSAGE request NOTE 1: At IWF-1, the Called Address can contain an MC Service ID, an FA, an FA(164) or an FA(EIRENE). NOTE 2: At IWF-1, the Calling Address can contain an MC Service ID. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3 Identity mapping and addressing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.0 General | The IWF shall perform mapping of identities between GSM-R entities and FRMCS entities. The IWF shall be configurable in such a way that enables identity mapping services to be performed. Clause 6.3 specifies: • IWF routing service(s). • IWF identity mapping Service(s). |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1 Management policies for identity mapping and routing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1.1 General | Within an FRMCS domain, the following provisions shall be done: • An IWF domain shall be defined for interworking with GSM-R: - The IWF domain is used to indicate that call(s) may be routed to another domain by using the IWF service(s). - The IWF domain shall be used by the IWF, in order to indicate to FRMCS entities that an identity belongs to a GSM-R entity. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 19 • An FRMCS domain shall be defined: - The default FRMCS domain shall be used by the IWF, in order to replace the domain of GSM-R to FRMCS protocol address parameters that point to FRMCS entities. Within the FRMCS SIP Core, the following provisions shall be made: • The IMS domain, which is configured at the FRMCS SIP Core, shall be reachable from the GSM-R domain(s). • A configurable routing function shall be defined in such a way that: - Set(s) of E.164 digits or set(s) of EIRENE digits of address parameters can be assigned to set(s) of FRMCS entities. - Rule(s) can be applied that determine the processing of GSM-R to FRMCS address parameters for set(s) of FRMCS entities. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1.2 Examples for the changing of the domain in SIP URIs | As specified in clause 6.3.1, the IWF will change the domain of protocol address parameters, so that: • FRMCS entities can address GSM-R entities by using the IWF Domain (which will be changed into a GSM-R Domain by the IWF). • GSM-R entities can address FRMCS entities by using the IMS Domain (which will be changed into an FRMCS Domain by the IWF). Figure 6.3.1.2-1 depicts an example for IWF changing the domain of SIP URIs. It uses the following abbreviations: • CdA = Called Address • CgA = Calling Address • A1 Party = first example of a calling party (within a GSM-R Domain) • A2 Party = second example of a calling party (within an FRMCS Domain) • B Party = called party • ims.com = IMS Domain • mgcf.com = GSM-R Domain • frmcs.com = FRMCS Domain • iwf.com = IWF Domain NOTE: The user parameter ("user=gsmr", "user=phone") is omitted in the SIP URIs, for the sake of brevity. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 20 Figure 6.3.1.2-1: Example for IWF changing the domain of SIP URIs NOTE: Figure 6.3.1.2-1 shows only the domain mapping for an FA(EIRENE) as a Called Address and for two alphanumeric MCPTT IDs as Calling Addresses, because the focus of this example is on the domain changing. Some more complete examples might be added in a later version. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2 SIP routing services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2.1 GSM-R to FRMCS out-of-dialog SIP requests | GSM-R to FRMCS out-of-dialog SIP requests are out-of-dialog SIP requests that are routed from a GSM-R domain to a FRMCS domain by the IWF. For the purpose(s) of the present document, the following list applies to routing of GSM-R to FRMCS out-of-dialog SIP request(s): • Any out-of-dialog SIP request received at the IMS domain that originates from a GSM-R domain shall be routed by the IWF routing service(s) to an MC service server using IWF-1 or IWF-2, if this is not forbidden by operator policy. • If the forwarding of a GSM-R to FRMCS out-of-dialog SIP request to an MC service server using IWF-1 or IWF-2 is forbidden by operator policy, then the SIP request shall be rejected with a "403 MCX Interworking Forbidden" final SIP response. • Any provisions for routing service(s) regarding forwarding of GSM-R to FRMCS out-of-dialog SIP requests to non-FRMCS domain(s) are out of scope. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2.2 FRMCS to GSM-R out-of-dialog SIP requests | FRMCS to GSM-R out-of-dialog SIP requests are out-of-dialog SIP requests that are routed from a FRMCS domain to a GSM-R domain by the IWF. For the purpose(s) of the present document, the following list applies to the routing of FRMCS to GSM-R out-of-dialog SIP request(s): • Any FRMCS to GSM-R out-of-dialog SIP INVITE request shall be routed by the IWF routing service(s) to a GSM-R MGCF using IWF-g1. • Any FRMCS to GSM-R out-of-dialog SIP MESSAGE request shall be routed by the IWF routing service(s) to a GSM-R IP-SM-GW using IWF-g5. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 21 • Any provisions for routing service(s) regarding forwarding of FRMCS to GSM-R out-of-dialog SIP requests to non-FRMCS domain(s) are out of scope. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3 Identity mapping services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.0 General | The IWF identity mapping service(s) shall provide mapping of the following types of identities, and also considering group call criteria: • MC Service ID. • FA. • Group Call Criteria. • MC Service Group ID. Mapping of MC Service ID provides identity mapping between MC Service ID and SIP-R URI. Mapping of FA provides identity mapping between FA(164), FA(EIRENE) or FA and SIP-R URI. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1 Generic procedures for identity mapping | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.0 General | A set of address parameters are subject to a generic identity mapping as specified within this clause. The first decision of generic identity mapping is to determine if the address parameters of a SIP/SDP message are subject to a GSM-R to FRMCS domain transition or subject to a FRMCS to GSM-R domain transition. Based on this decision, the appropriate procedure described in either clause 6.3.3.1.1 or 6.3.3.1.2 shall be applied. NOTE: The decision about whether the SIP message is being forwarded from FRMCS to GSM-R or vice versa, can be done based on the incoming interface: if the message is received via IWF-g1 or IWF-g5, then the interworking is from GSM-R to FRMCS, if the message is received via IWF-1 or IWF-2, then the interworking is from FRMCS to GSM-R. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.1 Generic identity mapping for GSM-R to FRMCS SIP messages | For the case of a GSM-R to FRMCS interworking (as defined in cause 6.3.3.1.0) and for each SIP/SDP address parameter subject to generic identity mapping, the following processing steps shall be applied: NOTE: For the case of mapping of GSM-R to FRMCS addresses, the set of addresses subject to mapping can be one of the types: E.164 SIP-R URI or EIRENE SIP-R URI. 1) Configurable Routing Function The analysis part of the routing function determines if the address parameter identifies an FRMCS entity or a GSM-R entity. 2) FRMCS Entity For FRMCS entities, the configurable routing function shall deliver an indication of the type of how the identity mapping services shall handle the input SIP-R URI when mapping it to a concrete address parameter valid in the FRMCS domain. The identity mapping service(s) shall map the input SIP-R URI into: • MC Service ID; or • FA(164); or • FA(EIRENE); or ETSI ETSI TS 103 792 V1.1.1 (2026-01) 22 • FA. Means for protocol address parameter mapping may be locally hosted. If the content of the address parameter is mapped to an FA(164), to an FA(EIRENE), or to an FA, then the domain part of the resulting SIP URI shall be set to the FRMCS domain. 3) GSM-R Entity For GSM-R entities, one of the following protocol address mappings are applicable: • E.164 SIP-R URI shall be mapped to FA(164). • EIRENE SIP-R URI shall be mapped to FA(EIRENE). The domain part of the resulting SIP URI shall be set to an IWF domain. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.2 Generic identity mapping for FRMCS to GSM-R SIP messages | For SIP messages received by an IWF from an FRMCS domain that have a GSM-R domain as destination (as defined in cause 6.3.3.1.0) and for each protocol address parameter subject to generic identity mapping, one of the following processing steps shall be applied to these parameter(s): 1) MC Service ID If the address parameter contains an MC Service ID, then it shall be mapped to an E.164 SIP-R URI or to an EIRENE SIP-R URI, depending on the indication provided by the configurable routing function. 2) E.164 Address If the address parameter carries an FA(164), then it shall be mapped to an E.164 SIP-R URI. The domain of the resulting SIP-R URI shall be set to the IMS domain. 3) EIRENE Address or FA If the address parameter carries an FA(EIRENE) or an FA, then it shall be mapped to an EIRENE SIP-R URI. The domain of the resulting SIP-R URI shall be set to the IMS domain. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2 Mapping of basic address parameters for MCPTT private calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.0 General | The set of basic address parameters applicable for private calls using MCPTT, applying generic address parameter naming as defined in clause 6.2 are: • Called Address. • Calling Address. • Additional Calling Address. • Connected Address. The above set of basic address parameters shall be mapped according to clause 6.3.3.2. The Called Address shall, following the mapping according to clause 6.3.3.2, be used by IWF routing service(s) to determine the next destination endpoint for a SIP INVITE to an MCPTT private call dialog. NOTE 1: Called Address, Calling Address and Additional Calling Address are applicable to SIP INVITE message(s) that initiates a MCPTT Private Call dialog. NOTE 2: Connected Address is applicable to a successful response (200 OK) to a request that initiates a MCPTT private Call dialog. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 23 NOTE 3: The set of basic address parameters mentioned above covers functional aliases in the called address, but it does not cover functional aliases in the calling address (except EIRENE addresses and FAs in the additional calling address for group communication). The mapping of calling functional aliases (PFN) is not considered a mapping of "basic" addresses and it is covered in clause 6.3.3.4.1. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.1 Basic address parameters for GSM-R to FRMCS private calls | For any request detected within the IWF domain for a GSM-R to FRMCS private MCPTT call that is received from a GSM-R domain, analysis as specified in clause 6.3.3.1.1 for the Called Address shall be performed to determine if the MCPTT private call is intended to be established in a FRMCS domain. If the call is not intended to be established, the call shall be rejected by a final and non-successful SIP response. If the call is intended to be established in a FRMCS domain, the following list of steps is applicable: 1) Identity mapping on Called Address (based on indicative result as given by procedure(s) in clause 6.3.3.1.1) shall be applied as specified in Table 6.3.3.2.1-1. Table 6.3.3.2.1-1: Cases of mapping of Called Address for GSM-R to FRMCS private calls Type of Address Called Address at IWF-g1 Called Address at IWF-1 MC Service ID E.164 SIP-R URI MC Service ID (e.g. by local address lookup) FA(164) E.164 SIP-R URI FA(164) FA(EIRENE) E.164 or EIRENE SIP-R URI FA(EIRENE) FA E.164 or EIRENE SIP-R URI FA NOTE: The Type of Address for FRMCS entities is asserted by the configurable routing function as specified in clause 6.3.3.1.1, bullet 2. FRMCS Entity. 2) If identity mapping on Called Address based on Table 6.3.3.2.1-1 results to FA(164), FA(EIRENE) or FA, the domain part of a resulting SIP URI for Called Address shall be set to a FRMCS domain. 3) The Calling Address shall be used for identity mapping as specified in Table 6.3.3.2.1-2. Table 6.3.3.2.1-2: Cases of mapping of Calling Address for GSM-R to FRMCS private calls Calling Address at IWF-g1 Calling Address at IWF-1 E.164 SIP-R URI FA(164) from Calling Address The domain part of a resulting SIP URI for Calling Address shall be set to a IWF domain. 4) If Connected Address is present and is populated with data in a SIP response message from a FRMCS domain that indicates successful setup of dialog (SIP 200 OK), the Connected Address shall be used for identity mapping as specified in Table 6.3.3.2.1-3. Table 6.3.3.2.1-3: Cases of mapping of Connected Address for GSM-R to FRMCS private calls Connected Address at IWF-1 Connected Address at IWF-g1 MC Service ID E.164 SIP-R URI (e.g. by local address lookup) FA(164) E.164 SIP-R URI FA(EIRENE) or FA EIRENE SIP-R URI 5) The domain part of a resulting SIP URI for Connected Address shall be set to a IMS domain if the Connected Address was previously mapped from FA(164), FA(EIRENE) or FA as part of an initial SIP dialog request (SIP INVITE). |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.2 Basic address parameters for FRMCS to GSM-R private calls | If the request for an MCPTT private call is forwarded by the IWF from an FRMCS domain to another domain, then the IWF shall apply one of the following identity mappings to the Called Address, as defined in Table 6.3.3.2.2-1, before the routing services of the IWF take any routing decision. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 24 Table 6.3.3.2.2-1: Cases of mapping of Called Address and Calling Address for FRMCS to GSM-R private calls Called/Calling Address at IWF-1 Called/Calling Address at IWF-g1 MC Service ID E.164 or EIRENE SIP-R URI (e.g. by local address lookup) FA(164) see note E.164 SIP-R URI FA(EIRENE) or FA (see note) EIRENE SIP-R URI NOTE: The Called Address can contain MC Service ID, FA, FA(164) or FA(EIRENE), the Calling Address can only contain MC Service ID. If the resulting Called Address was mapped from an FA(164), from an FA(EIRENE) or from an FA, then the domain of the resulting SIP URI needs to be retrieved and then set as specified at ETSI TS 123 228 [7], clause 4.3.5. The routing decisions may result in the fact that the call request may be looped back via the IWF to a FRMCS domain, as described in clause 6.3.3.2.1, after all of the identity mappings of the FRMCS to GSM-R call request as defined in clause 6.3.3.2.2.will have been done. Also, if the request for an MCPTT private call is forwarded by the IWF from a FRMCS domain to a GSM-R domain, then the IWF shall apply the identity mapping to the Calling Address as defined in Table 6.3.3.2.2-1. The domain of the resulting SIP URI shall be set to the IMS domain. The final SIP 200 OK response to the call request can contain a Connected Address. If the final SIP 200 OK response to the call is received from another domain and if it contains a Connected Address, then the IWF shall apply one of the following identity mappings to the Connected Address, as defined in Table 6.3.3.2.2-2. Table 6.3.3.2.2-2: Cases of mapping of Connected Address for FRMCS to GSM-R private calls Connected Address at IWF-g1 Connected Address at IWF-1 E.164 SIP-R URI FA(164) EIRENE SIP-R URI FA(EIRENE) The domain of the resulting SIP URI shall be set to the IWF domain. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3 Identity mapping for MCData SDS | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.0 General | The IWF will receive the Text Message from the GSM-R IP-SM-GW and map it to the MCData SDS. In the reverse direction the IWF will map the MCDATA SDS to an Instant Message and send it to the GSM-R IP-SM-GW. The set of basic address parameters applicable for text messaging using MCData SDS, also applying generic address parameter naming as defined in clause 6.2 are: • Called Address. • Calling Address. The Called Address shall, following the mapping according to clause 6.3.3.3, be used by IWF routing service(s) to determine the next destination endpoint for a SIP MESSAGE. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.1 Address parameters for GSM-R to FRMCS text messages | For any request detected within the IWF domain for a GSM-R to FRMCS Text Message that is received from a GSM-R domain, analysis as specified in clause 6.3.3.1.1 for the Called Address shall be performed to determine if the Instant Message is intended to be delivered to an FRMCS domain. If the text message is not intended to be delivered, it shall be rejected by a final and non-successful SIP response. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 25 If the text message is intended to be delivered to an FRMCS domain, the following list of steps is applicable: 1) Identity mapping on Called Address (based on indicative result as given by procedure(s) in clause 6.3.3.1.1) shall be applied as specified in Table 6.3.3.3.1-1. Table 6.3.3.3.1-1: Cases of mapping of Called Address for GSM-R to FRMCS text message Type of Address Called Address at IWF-g5 Called Address at IWF-2 MC Service ID E.164 SIP-R URI MC Service ID (e.g. by local address lookup) FA(164) E.164 SIP-R URI FA(164) FA(EIRENE) E.164 or EIRENE SIP-R URI FA(EIRENE) FA E.164 or EIRENE SIP-R URI FA NOTE: The Type of Address for FRMCS entities is asserted by the configurable routing function. For details, refer to the definition provided in clause 6.3.3.1.1, bullet 2. FRMCS Entity. 2) If identity mapping on Called Address based on Table 6.3.3.3.1-1 results to FA(164), FA(EIRENE) or FA, the domain part of a resulting SIP URI for Called Address shall be set to a FRMCS domain. 3) The Calling Address shall be used for identity mapping as specified in Table 6.3.3.3.1-2. Table 6.3.3.3.1-2: Mapping of Calling Address for GSM-R to FRMCS text message Calling Address at IWF-g5 Calling Address at IWF-2 E.164 SIP-R URI FA(164) from Calling Address The domain part of a resulting SIP URI for Calling Address shall be set to an IWF domain. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.2 Address parameters for FRMCS to GSM-R text messages | If the request for an MCDATA SDS message is forwarded by the IWF from an FRMCS domain to a GSM-R domain, then the IWF shall apply one of the following identity mappings to the Called Address, as defined in Table 6.3.3.3.2-1, before the routing services of the IWF take any routing decision. Table 6.3.3.3.2-1: Cases of mapping of Called Address and Calling Address for FRMCS to GSM-R text messages Called/Calling Address at IWF-2 Called/Calling Address at IWF-g5 MC Service ID E.164 or EIRENE SIP-R URI (e.g. by local address lookup) FA(164) E.164 SIP-R URI FA(EIRENE) or FA EIRENE SIP-R URI If the resulting Called Address was mapped from an FA(164), from an FA(EIRENE) or from an FA, then the domain of the resulting SIP URI shall be retrieved and then set as specified in ETSI TS 123 228 [7], clause 4.3.5. The routing decisions may result in the loop back of the text message to a FRMCS domain via the IWF, as described in clause 6.3.3.3.1. This occurs after completing all identity mappings between the FRMCS and the GSM-R systems. Also, if the request for an MCPTT text message is forwarded by the IWF from a FRMCS domain to GSM-R domain, then the IWF shall apply one of the identity mappings to the Calling Address, as defined in Table 6.3.3.3.2-1. The domain of the resulting SIP URI shall be set to the IMS domain. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4 Identity mapping for supplementary services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.0 General | The identity mapping services of the IWF shall be applicable to the interworking of supplementary services, whenever supplementary identity (address) information is exchanged between an FRMCS domain and a GSM-R domain. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 26 Explicitly listed, these supplementary identities are: • MCPTT functional aliases and GSM-R functional numbers, when handling the PFN service. • Call history information - i.e. a list of all forwarded identities - in the case of call diversion. • Mutual exchange of connected identities, in the case of call transfer. • Information about all connected identities, in the case of group calls. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.1 Presentation of Functional Number - User To User Information | The mapping of Basic Address Parameters (see clause 6.3.3.2) covers MCPTT IDs and MCDATA IDs in the Called Address parameter and functional aliases (FRMCS FA, FA(164), FA(EIRENE)). The Calling Address is supposed to always carry MCPTT IDs or MCDATA IDs on the IWF-1 reference point (e.g. in the XML element <mcptt-calling-user-id>) and E.164 SIP-R URIs on the IWF-g1 reference point (in the P-Asserted.Identity header field). The Additional Calling Address for group communication carries an FRMCS FA or an FA(EIRENE) on the IWF-1 reference point and an equivalent CT5x EIRENE FN in a SIP-R URI on the IWF-g1 reference point. A possible calling functional alias, and its equivalent EIRENE FN will be carried in the User To User Information (PFN), which is the <functional-alias-URI> on IWF-1 and the User-to-User header field on IWF-g1. GSM-R Functional Numbers (FNs) carried in the User-to-User header field shall be interworked with FRMCS in one of the following two ways: • A GSM-R FN can be rephrased as FRMCS FA and vice versa as specified in FRMCS FRS [1] and FRMCS SRS [2]. • A GSM-R FN can be mapped to an FA(EIRENE) and vice versa. In both cases, the FRMCS identity shall be carried in the <functional-alias-URI> element of the MCPTT-INFO XML body. In the second case, GSM-R FNs can be mapped to FA(EIRENE) (but not rephrased as FRMCS FA). This shall be accomplished by just taking the FN as the user part of the resulting SIP URI. The domain of the resulting SIP URI shall be set to the IWF domain. If an FA(EIRENE) is mapped to an FN, this shall be accomplished by taking the user part of the SIP URI as an international address, which is then used in the SIP User-to-User header field. The User-to-User header field shall be forwarded transparently from the FRMCS domain to the GSM-R domain and vice versa, as the User-to-User header field can contain more information as just an FN/FA, e.g. CHPC information, GPS, etc. The mapping from GSM-R FN to FRMCS FA (or FA(EIRENE)) shall be done additionally, as described above, by adding the <functional-alias-URI> XML element. If a SIP message is forwarded from the FRMCS domain to the GSM-R domain, and if the User-to-User header field is not present, then the IWF shall perform the mapping from FRMCS FA (or FA(EIRENE)) to GSM-R FN and create a User-to-User header field that contains a GSM-R FN. NOTE: A GSM-R FN can be carried in the User-to-User header field in one of two different formats: a) with the help of a PFN tag b) as uncompressed OTDI. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.2 Call Diversion - Call History Address List | The Call History Address List is transmitted as follows: • At the IWF-g1 reference point, the call history information shall be transmitted within History-Info header fields, according to ETSI TS 103 389 [6]. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 27 • At the IWF-1 reference point, the call history information shall be transmitted within the <forwarding- immediate-list> and within the <forwarding-other-list>, according to ETSI TS 124 379 [10]. The address parameters in the History-Info header fields of GSM-R to FRMCS messages and the address parameters in the <forwarding-immediate-list> and in the <forwarding-other-list> of FRMCS to GSM-R messages shall be applied to the generic procedures for identity mapping according to clause 6.3.3.1. The reason for call forwarding shall be mapped between the "cause" URI parameter at the IWF-g1 reference point and the <forwarding-reason> element at the IWF-1 reference point, as defined in Tables 6.3.3.4.2-1 and 6.3.3.4.2-2. Table 6.3.3.4.2-1: Mapping of the Forwarding Reason for FRMCS to GSM-R messages Forwarding Reason at IWF-1 Forwarding Reason at IWF-g1 Immediate 480 - default No-answer 408 Manual-input 487 Table 6.3.3.4.2-2: Mapping of the Forwarding Reason for GSM-R to FRMCS messages Forwarding Reason at IWF-g1 Forwarding Reason at IWF-1 404 (Unknown/Not available) no-answer (<forwarding-other-list>) - default 486 (User busy) no-answer (<forwarding-other-list>) 408 (No reply) no-answer (<forwarding-other-list>) 302 (Unconditional) immediate (<forwarding-immediate-list>) 487 (Deflection during alerting) manual-input (<forwarding-other-list>) 480 (Deflection immediate response) immediate (<forwarding-immediate-list>) 503 (Mobile subscriber not reachable) no-answer (<forwarding-other-list>) |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.3 Explicit Call Transfer - Connected Address | The Connected Addresses transmitted during the execution of a call transfer service shall be mapped according to the description of generic identity mapping in clause 6.3.3.1. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5 Mapping of Identities, Criteria and Domains for MCPTT group calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.0 General | MCPTT Group Calls are group calls that are controlled by the Controlling Function of an MCPTT Server beyond the IWF-1 reference point, as seen from the IWF. As described in clause 7, MCPTT Ad-Hoc Group calls can be coupled with GSM-R VGCS/VBS calls, where either the MCPTT Group call invites an MCPTT ID as participant that represents any called GSM-R VGCS/VBS at the IWF, or the GSM-R VGCS/VBS invites an E.164 SIP-R URI or an EIRENE SIP-R URI that represents any MCPTT Ad-Hoc group call at the IWF. During the setup of such coupled FRMCS/GSM-R group calls, the IWF maps the FRMCS Criteria (of the ad-hoc group call) into a GSM-R CT5 Functional Number or vice versa, as shown in Figure 6.3.3.5.0-1 and defined in clause 6.3.3.5.2. This mechanism is sketched in Figure 6.3.3.5.0-1. FRMCS GSM-R IWF EIRENE CT5 Criteria GCRep GCRep Figure 6.3.3.5.0-1: Coupled FRMCS/GSM-R Group Call ETSI ETSI TS 103 792 V1.1.1 (2026-01) 28 The Group Call Representation (GCRep) used at the IWF-1 reference point shall be configured as MCPTT ID of a participant of the ad-hoc group call at the MC Service Server and at the IWF. The Group Call Representation (GCRep) used at the IWF-g1 reference point shall be configured either as an international E.164 address or as an international EIRENE number, corresponding to the originating or terminating dispatcher at both the GCR and at the IWF. The term FRMCS to GSM-R group call is used in clause 6.3.3.5 to describe the SIP dialog that is established by an MCPTT group call, when the group call invites a GSM-R VGCS/VBS call via the IWF. The term GSM-R to FRMCS group call is used in clause 6.3.3.5 to describe the SIP dialog that is established by a GSM-R VGCS/VBS call via the IWF, in order to create an MCPTT group call. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.1 Mapping of basic address parameters for MCPTT group calls | The content of Called Address and Calling Address at the IWF-1 and IWF-g1 reference points is specified in Tables 6.3.3.5.1-1 and 6.3.3.5.1-2. Table 6.3.3.5.1-1: Content of basic address parameters during the setup of FRMCS to GSM-R group calls Address Parameter Content at IWF-1 Content at IWF-g1 Called Address GCRep (an MCPTT ID) EIRENE CT5 SIP-R URI Criteria Criteria for determining the participants n/a Calling Address MC Service ID E.164 SIP-R URI (e.g. by local address lookup) Table 6.3.3.5.1-2: Content of basic address parameters during the setup of GSM-R to FRMCS group calls Address Parameter Content at IWF-g1 Content at IWF-1 Called Address GCRep (E.164 SIP-R URI or EIRENE SIP-R URI) n/a Criteria n/a Criteria for determining the participants Calling Address E.164 SIP-R URI MC Service ID (e.g. by local address lookup) Additional Calling Address EIRENE CT5 SIP-R URI FA(EIRENE) |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.2 Mapping of FRMCS criteria and EIRENE CT5 FN | The MCPTT call control protocol, defined in ETSI TS 124 379 [10] specifies the criteria for determining the participants, that an MCPTT UE shall send when initiating an ad-hoc group call. These criteria are transmitted in the <call-participants-criterias> element in the <anyExt> element of the <mcptt- Params> element of the <mcpttinfo> element of the application/vnd.3gpp.mcpttinfo+xml MIME body in the SIP INVITE request. The content of these criteria is just a string with comma separated parameters, where the parameters are defined in the FRMCS FIS [3] specification. The specification in the FRMCS FIS [3] considers that the criteria will be mapped to and from an EIRENE CT5 Functional Number at the IWF, as follows: • An EIRENE CT5 international number is specified as IC + CT + LLLLL + GID, where: - IC International Code (3 digits). - CT Calltype (2 digits). - LLLLL Group Call Area (5 digits). - GID Group ID (3 digits). ETSI ETSI TS 103 792 V1.1.1 (2026-01) 29 • FRMCS FIS specifies the following criteria relevant for the mapping to and from an EIRENE CT5 FN: - FRMCS_CallType (string). - FRMCS_ListOfAdressedArea (string). The mapping identified in Table 6.3.3.5.2-1 shall apply for the setup of coupled FRMCS/GSM-R group calls. Table 6.3.3.5.2-1: Mapping of FRMCS criteria and EIRENE CT5 for coupled FRMCS/GSM-R group calls Parameter at IWF-g1 Part of the EIRENE CT5 FN Parameter at IWF-1 Part of the FRMCS Criteria IC Group Call Representation (domain) CT, GID FRMCS_CallType LLLLL FRMCS_ListOfAddressedArea |
05f8beb7977a67521a875d86df071465 | 103 792 | 7 Group calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1 Interworking procedures | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.0 General | This clause contains stage 2 and stage 3 procedures for interworking of group calls between 3GPP MCPTT systems and GSM-R systems. The messages and information elements used in the procedures in this clause are specified in the following documents: • ETSI TS 103 389 [6] for GSM-R. • ETSI TS 123 283 [11] for MCPTT stage 2. • ETSI TS 129 379 [8] and ETSI TS 124 379 [10] for MCPTT stage 3. Figure 7.1.0-1 illustrates an interworking scenario with an area that has is commonly used by GSM-R and FRMCS users as base scenario for the information flows and procedures in the following clauses. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 30 GSM-R cell A GSM-R cell B GSM-R cell C GSM-R cell D Group call area 1 corresponds to CT5loc1 Group call area 2 corresponds to CT5loc2 Polygon for MCPTT Loc group1 Polygon for MCPTT Loc group2 GSM-R train FRMCS train Figure 7.1.0-1: Network overview If a group call is initiated by a train driver that is connected to the FRMCS domain, the call will be initiated in the respective FRMCS area (MCPTT Loc group1 or MCPTT Loc group2) and the call has to trigger and include also the corresponding VGCS group call reference number (GCref) according to E.164 numbering plan using EIRENE numbering scheme in GSM-R (CT5loc1 or CT5loc2). Similar if a group call is initiated by a train driver that is connected to the GSM-R domain, the call has to trigger and include also the corresponding MCPTT group call in FRMCS. The following clauses define these two procedures in more detail. |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1 Information flows | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1 Stage 2 information flows | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.1 General | This clause introduces the stage 2 information flows related to the interworking of group calls between MCPTT and GSM-R: • The SIP interface between the MGCF and the 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 ringing is defined in ETSI TS 123 283 [11], clause 10.4.1.4. • IWF MCPTT ad-hoc group call request is defined in ETSI TS 123 283 [i.13] with the following clarification: - The parameter Criteria for determining the participants shall be set according to clause 6.3.3.5.2 of the present document. - The parameter Requested priority shall be set according to ETSI TS 103 765-2 [4]. - The parameter Additional application specific data shall be set according to clause 6.3.3.4.1 of the present document. • IWF MCPTT ad-hoc group call response is defined in ETSI TS 123 283 [i.13]. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 31 |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.2 IWF GSM-R IWF ad-hoc group call request | Table 7.1.1.1.2-1 contains the GSM-R IWF group call request information flow. Table 7.1.1.1.2-1: GSM-R IWF group call request Information Element Status Description Called Address M SIP Request-URI, as defined in clause 6.3.3.5. This information element can hold an E.164 SIP-R URI or an EIRENE SIP-R URI, as defined in ETSI TS 103 389 [6] Calling Address M P-Asserted-Identity, as defined in clause 6.3.3.5. This information element can hold an E.164 SIP-R URI, as defined in ETSI TS 103 389 [6]. Additional Calling Address O From header field, as defined in clause 6.3.3.5. This information element is considered being present, when the From header field contains an EIRENE SIP-R URI. Resource Priority M The Resource-Priority header field, 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 calling GSM-R functional number for the PFN service (see clause 6). This information element is specified in ETSI TS 103 389 [6]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.