hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4.5 Data transfer from the On-Board-FRMCS to the FRMCS Trackside Gateway | For Data transfer from the On-Board-FRMCS to the FRMCS Trackside Gateway, the following steps are undertaken (see Figure 6.2.2.4.5-1 and clause 6.2.2.2.2): 1) The MCData client within the On-Board FRMCS encapsulates the incoming IP packets from the On-Board LC Application (source: OBA1, destination: ViOB TSA1) into the MCData IPcon GRE over UDP tunnel. 2) The MCData client within FRMCS Trackside Gateway decapsulates the packets arriving from the GRE tunnel. 3) The Trackside Application Network NAT shall replace the source and destination IP addresses (source: OBA1, destination: ViOB TSA1) in the decapsulated IP packet of step 2 by (source: ViTS OBA1, destination: TSA1). 4) The FRMCS Trackside Gateway shall forward the packet resulting from step 3 towards the Trackside LC Application. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 27 Figure 6.2.2.4.5-1: H2H data transfer in both direction: (top) from On-Board to Trackside and (bottom) from Trackside to On-Board ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 28 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4.6 Data transfer from the FRMCS Trackside Gateway to the On-Board-FRMCS | For Data transfer from a FRMCS Trackside Gateway to an On-Board-FRMCS, the following steps are undertaken (see Figure 6.2.2.4.5-1 and clause 6.2.2.2.2): 1) The Trackside Application Network NAT shall replace the source and destination IP addresses (source: TSA1, destination: ViTS OBA1) in the incoming IP packets from the Trackside LC Application by (source: ViOB TSA1, destination: OBA1). 2) The MCData client within the FRMCS Trackside Gateway encapsulates the IP packets resulted from the step 1 (source: ViOB TSA1, destination: OBA1) into the MCData IPcon GRE over UDP tunnel. 3) The MCData client within the On-Board FRMCS decapsulates the packets arriving from the GRE tunnel. 4) The On-Board FRMCS shall forward the packet resulting from step 3 towards the On-Board LC Application. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.5 MCData IPcon session release | When this procedure is called by either On-Board FRMCS or FRMCS Trackside Gateway, the corresponding MCData client shall initiate the release of the MCData communication (see clause 6.2.2.2.3). |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.3 MCData SDS | The FRMCS Service Domain shall support ETSI TS 124 282 [9], clauses 9.2.2.3.1 (excluding step 4a) and 9.2.2.4.2 (excluding step 6). |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.4 MCData File Distribution | The present document does not specify normative requirements for MCData file distribution service. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.5 QoS and priority signalling | User's requested priority from MC session request as per ETSI TS 123 280 [2] shall be used for indicating the requested QoS and priority to the MC Service Server. Requested priority shall be used to uniquely identify railway communication session categories. The conveyance of <user-requested-priority> in the SIP INVITE messages during the call establishment is defined per MC Service in clause 6. The <user-requested-priority> value shall be 6 digit non-negative integer starting with non-zero digit. Format of <user-requested-priority> shall be [Communication Session Category] [Sub-category] where: • [Communication Session Category] is 4 digit field that uniquely indicates Communication Session Category. • [Sub-category] is 2-digit field that uniquely indicates further priority distinction within the same Communication Session Category. The <user-requested-priority> field of the SIP INVITE shall be used between the MC Service Client and (MC Service Server of) the FRMCS Service Domain. The Resource-Priority header field of the SIP INVITE shall always be set to "Normal". NOTE: The mapping of the combination of Communication Session Category and Sub-category to the <user-requested-priority> field of SIP INVITE needs to be consistent between the MC Service Client and its serving FRMCS Service Domains (an example of such mapping is presented in Table A-1). The Application Function shall send relevant QoS and priority parameters (i.e. afAppId and resPrio, as specified in ETSI TS 103 765-1 [15], clause 8.1) over Rx or N5 interfaces. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 29 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.6 Functional aliasing | This clause describes the functional aliasing for FRMCS Service Domain. The procedures for MCData server serving the MCData user for management of functional alias shall conform to ETSI TS 124 282 [9], clause 8.3.2. The procedures for MCData server owning functional alias shall conform to ETSI TS 124 282 [9], clause 8.3.3. The procedures for MCPTT server serving the MCPTT user for management of functional alias shall conform to ETSI TS 124 379 [7], clause 9A.2.2.2. The procedures for MCPTT server owning functional alias shall conform to ETSI TS 124 379 [7], clause 9A.2.2.3. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.7 Arbitration | The present document does not specify normative requirements with respect to arbitration. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3 MC User deregistration | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.1 MC User deregistration in Home FRMCS Service Domain | This clause describes the MC Service User deregistration in Home FRMCS Service Domain. MC Service User deregistration implies MC Service User can no longer receive MC services and SIP services. Pre-requisite: the ongoing communications of the MC Service User are released. If this procedure is initiated by its caller entity (e.g. within On-Board FRMCS or FRMCS Trackside Gateway), the MC Service Client shall perform the user-initiated SIP deregistration procedure as specified in ETSI TS 124 229 [13], clause 5.1.1.6. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.2 MC User deregistration in Foreign FRMCS Service Domain | This clause describes the MC Service User deregistration in Foreign FRMCS Service Domain. MC Service User deregistration implies MC Service User can no longer receive MC services and SIP services. Pre-requisite: the ongoing communications of the MC Service User is released. If this procedure is initiated by its caller entity (i.e. On-Board FRMCS in ETSI TS 103 765-3 [i.3]), the MC Service Client deregistration procedure in Foreign FRMCS Service Domain is constituted of the following steps: Step 1- Migrated MC Service User deauthorization For a migrated MC Service user, the MC Service Client shall initiate migration service deauthorization procedure as described in clause 6.4.2. of the present document. Step 2 - User-initiated SIP deregistration The MC Service Client shall perform the user-initiated SIP deregistration procedure as specified in ETSI TS 124 229 [13], clause 5.1.1.6. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.3 Network initiated MC User deregistration | The present document does not specify network initiated MC Service User deregistration. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 30 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4 Inter FRMCS service domain transition | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4.1 MC Service User migration | This clause describes the steps that shall be undertaken for MC User migration of a given MC User. The values passed into this procedure by its caller entity shall be used by the IdM Client and individual MC Service clients involved in the procedures referenced below. Precondition: The MC User is authenticated, and the MC Service client has selected the user profile which permits migration to the selected partner MC system as described in ETSI TS 133 180 [5], clause C.2. NOTE 1: The "selected partner MC system" is the one which is associated to the Foreign FRMCS Service Domain. Step 1 - Security token acquisition from the primary MC system The IdM Client procedures for security token acquisition from primary MC system shall conform to ETSI TS 124 482 [3], clause 6.2.2. The IdM Server procedures for security token acquisition from primary MC system shall conform to ETSI TS 124 482 [3], clause 6.3.2. Step 2 - MC token acquisition from the partner MC system The IdM Client procedures for token acquisition from partner MC system shall conform to ETSI TS 124 482 [3], clause 6.2.3. The IdM Server procedures for user authentication in the partner MC system shall conform to ETSI TS 124 482 [3], clause 6.3.3. Step 3 - Configuration of MC service user profile and MC service group in the partner MC system The MC procedures for subscribing to the MCS UE configuration document, the MCS user profile configuration document and the MCS service configuration document for each enabled MC Service shall conform to ETSI TS 124 484 [4], clause 4.2.2 for the online configuration case. Step 4 - Service authorization for migration to the partner MC system The MCPTT client procedure for migration service authorization shall conform to ETSI TS 124 379 [7], clause 7A.2. The partner MCPTT server procedure for migration service authorization shall conform to ETSI TS 124 379 [7], clause 7A.3. The partner MCPTT gateway server procedure for migration service authorization shall conform to ETSI TS 124 379 [7], clause 7A.4. The primary MCPTT gateway server procedure for migration service authorization shall conform to ETSI TS 124 379 [7], clause 7A.5. The primary MCPTT server procedure for migration service authorization shall conform to ETSI TS 124 379 [7], clause 7A.6. NOTE 2: How the MCPTT gateway server determines the public service identity of the targeted MCPTT function in the interconnected MCPTT system or the URI of the MCPTT gateway server in the interconnected MCPTT system is out of the scope of the present document. The MCData client procedure for migration service authorization shall conform to ETSI TS 124 282 [9], clause 7A.2. The partner MCData server procedure for migration service authorization shall conform to ETSI TS 124 282 [9], clause 7A.3. The partner MCData gateway server procedure for migration service authorization shall conform to ETSI TS 124 282 [9], clause 7A.4. The primary MCData gateway server procedure for migration service authorization shall conform to ETSI TS 124 282 [9], clause 7A.5. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 31 The primary MCData server procedure for migration service authorization shall conform to ETSI TS 124 282 [9], clause 7A.6. NOTE 3: How the MCData gateway server determines the public service identity of the targeted MCData function in the interconnected MCData system or the URI of the MCData gateway server in the interconnected MCData system is out of the scope of the present document. NOTE 4: FSNNI interface is used for Inter-domain exchanges. For out of band sharing between Home & Foreign FRMCS Service Domain, FSNNI conforms to SAP interconnection as described in clause 5.2.2 of the present document. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4.2 Migrated MC Service user deauthorization | This clause describes the requirements for migrated MC Service user deauthorization when the user leaves a Foreign FRMCS Service Domain (to move to another Foreign FRMCS Service Domain or to go back to the Home FRMCS Service Domain). The MCPTT client procedure for MC user migration deauthorization shall conform to ETSI TS 124 379 [7], clause 7A.2.3. The partner MCPTT server procedure for migration service deauthorization shall conform to ETSI TS 124 379 [7], clause 7A.3.7. The partner MCPTT gateway server procedure for migration service deauthorization shall conform to ETSI TS 124 379 [7], clause 7A.4. The primary MCPTT gateway server procedure for migration service deauthorization shall conform to ETSI TS 124 379 [7], clause 7A.5. The primary MCPTT server procedure for migration service deauthorization shall conform to ETSI TS 124 379 [7], clause 7A.6.2. NOTE 1: How the MCPTT gateway server determines the public service identity of the targeted MCPTT function in the interconnected MCPTT system or the URI of the MCPTT gateway server in the interconnected MCPTT system is out of the scope of the present document. The MCData client procedure for migration service deauthorization shall conform to ETSI TS 124 282 [9], clause 7A.2.3. The partner MCData server procedure for migration service deauthorization shall conform to ETSI TS 124 282 [9], clause 7A.3.6. The partner MCData gateway server procedure for migration service deauthorization shall conform to ETSI TS 124 282 [9], clause 7A.4. The primary MCData gateway server procedure for migration service deauthorization shall conform to ETSI TS 124 282 [9], clause 7A.5. The primary MCData server procedure for migration service deauthorization shall conform to ETSI TS 124 282 [9], clause 7A.6.2. NOTE 2: How the MCData gateway server determines the public service identity of the targeted MCData function in the interconnected MCData system or the URI of the MCData gateway server in the interconnected MCData system is out of the scope of the present document. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 32 6.5 Communications encompassing multiple FRMCS Service Domains |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.5.1 MCPTT voice services in interconnected FRMCS service Domains | The MCPTT procedures in clause 6.2.1 apply for interconnected FRMCS Service Domains. If the interconnected FRMCS Service Domains are considered to be in different trust domains, the FRMCS Service Domain shall conform to the procedures regarding MC Gateway Server as defined in ETSI TS 124 379 [7], clause 6.8. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.5.2 MCData IP Connectivity in interconnected FRMCS Service Domains | The MCData IPcon procedures in clause 6.2.2 apply for interconnected FRMCS Service Domains. If the interconnected FRMCS Service Domains are considered to be in different trust domains, the FRMCS Service Domain shall conform to the procedures regarding MC Gateway Server as defined in ETSI TS 124 282 [9], clause 6.8. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 33 Annex A (informative): Mapping table for Communication Session Category with User Requested Priority Table A-1 provides an example mapping table between some Communication Session Category, Sub-category and the <user-requested-priority> field of the SIP INVITE. Table A-1: Mapping for QoS and priority signalling Communication Session Category Sub-category <user-requested-priority> field of the SIP request FRMCS Signaling N/A 100000 Predefined Default N/A 100100 Emergency Voice N/A 101100 Voice Urgent Driver-to-Controller 100200 Normal Driver-to-Controller 100201 TCMS N/A 111900 ATP Regular Data N/A 110400 ATP Compl. Data N/A 111800 ATO Data N/A 110500 ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 34 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 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 1 Scope | The present document specifies non-3GPP network functions and interfaces applicable to the FRMCS Trackside Infrastructure. The present document describes the trackside network architecture and proceeds with specifying the non-3GPP trackside network functional entities (such as the FRMCS Trackside Gateway), including functions, interfaces and procedures they need to comply to. The present document does not consider message sequences within and between 3GPP and non-3GPP building blocks. These message sequences will be defined by related 3GPP specifications, ETSI FRMCS transport stratum definition and FRMCS service stratum definition documents or UIC FRMCS FIS [i.3] and UIC FRMCS FFFIS [1]. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 2 References | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 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 FFFIS-7950 (V2.1.0): "FRMCS FFFIS Form Fit Functional Interface Specification". [2] ETSI TS 103 765-2: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building blocks and functions; Part 2: Service Stratum". [3] ETSI TS 103 765-1: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building blocks and functions; Part 1: Transport Stratum". [4] ETSI TS 123 280 (V18.12.0): "LTE; Common functional architecture to support mission critical services; Stage 2 (3GPP TS 23.280 version 18.12.0 Release 18)". [5] 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)". [6] ETSI TS 103 792: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Interworking with GSM-R". [7] 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)". [8] 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)". [9] ISO 8601 (2019): "Date and time — Representations for information interchange". ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 7 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 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 791: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Terminology for FRMCS specifications". [i.2] UIC FW-AT 7800 (V2.1.0): "Future Railway Mobile Communication System - System Requirements Specification". [i.3] UIC FIS-7970 (V2.1.0): "Future Railway Mobile Communication System - Functional Interface Specification". [i.4] 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)". |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3 Definition of terms, symbols and abbreviations | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.1] and the following apply: Hosting Clients: MC Service Client located in FRMCS Trackside Gateway NOTE: Hosting Client connects Loose-Coupled FRMCS applications to FRMCS system. Reference point TAP TS: reference point represents the connection from FRMCS Trackside Gateway to transport core network(s) and to the FRMCS Service Server TSAPP Application Context: context maintained by the FRMCS Trackside Gateway for an application instance (identified by the TSAPP application tuple), in between registration and de-registration TSAPP application tuple (RegisterData): tuple of (appCategory, staticId, couplingMode) as specified in UIC FRMCS FFFIS-7950 [1], clause 10.8.1 and Annex B, clause A.3 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.2 Symbols | Void. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DNS Domain Name Server FRMCS Future Railway Mobile Communication System H2H Host-to-Host H2N Host-to-Network HTTP Hyper Text Transfer Protocol IP Internet Protocol ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 8 IWF Interworking Function JSON JavaScript Object Notation MC Mission Critical MCPTT Mission Critical Push-To-Talk MCX Mission Critical Communications NAT Network Address Translation SIP Session Initiation Protocol SSE Server Sent Events TAP TS TAP Trackside TAP Transport Access Point TSAPP Trackside Application Reference Point TSCTRL Reference point between VAS Controller Equipment and FRMCS System VAS Voice Application Subsystem |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 4 Trackside network architecture | FRMCS trackside architecture consists of at least one FRMCS Transport Domain (as described in ETSI TS 103 765-1 [3], clause 4.2) and zero or more non-FRMCS Transport Domains. The FRMCS Service Domain (as described in ETSI TS 103 765-2 [2], clause 5.1) enables communication as services between two or multiple FRMCS Users for voice and data applications. The Service Stratum is specified over the 3GPP Mission Critical Communications (MCX) Framework and decouples the application from the underlying transport networks. The focus of clause 5 is the FRMCS Trackside Gateway, which provides access to communication and complementary services supported by the FRMCS System to and from trackside applications. The IWF provides centralized support for interworking between an MCPTT or MCData system and a GSM-R system specified in ETSI TS 103 792 [6], clause 5. Figure 4-1 shows the FRMCS trackside architecture. The TSAPP reference point in Figure 4-1 is described in UIC FRMCS FFFIS-7950 [1] (Form Fit Functional Interface Specification). The TSAPP reference point supports the coupling modes for FRMCS (outlined in UIC FRMCS SRS (FW-AT 7800) [i.2]) defined in ETSI TR 103 791 [i.1]. The TSCTRL reference point is described in clause 7 of the present document. NOTE: Multipath Gateway can be combined with the FRMCS Trackside Gateway. The selected deployment option is the choice of the FRMCS operator. Figure 4-1: FRMCS trackside architecture 5G Core Data Network Multipath Gateway Data Network MCx Server FRMCS Trackside Gateway Trackside Application VAS- Controller Equipment Data Network IWF ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 9 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5 FRMCS Trackside Gateway | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.1 General | The FRMCS Trackside Gateway is a logical component which is used to host specific functions. The FRMCS Trackside Gateway is the logical symmetrical component to the On-Board FRMCS. It is the link between the Transport Network and the Application at the infrastructure side (see UIC FRMCS SRS (FW-AT 7800) [i.2], Figure 6-4). NOTE: Implementors have the choice of combining the FRMCS Trackside Gateway functionalities with the functionalities of the Multipath Gateway as specified in ETSI TS 103 765-1 [3], clause 5.3. In this case, the combined entity inherits the Reference points from both the FRMCS Trackside Gateway (TSAPP and TAP TS) and from the Multipath Gateway (TAP Service Agents and FSMPM). |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.2 FRMCS Trackside Gateway architecture | The functional architecture of FRMCS Trackside Gateway is illustrated in Figure 5.2-1. The FRMCS Trackside Gateway links the trackside application. FRMCS Trackside Gateway TAP TS TSAPP Multipath Gateway TAP Service Agents FRMCS Service Serverl Figure 5.2-1: Functional architecture of FRMCS Trackside Gateway The generic reference points of the FRMCS Trackside Gateway are shown in Figure 5.2-1: • TSAPP. • TAP TS (TAP Trackside). Reference point TSAPP: This reference point represents the connection from the FRMCS Trackside Gateway to the Application(s). The TSAPP reference point is specified in UIC FRMCS FFFIS [1]. The behaviour expected from the FRMCS Trackside in relation with TSAPP is specified in clause 6.3. Reference point TAP TS: This reference point represents the connection from FRMCS Trackside Gateway to transport core network(s) and to the FRMCS Service Server. It consists of a control plane and a user plane and is defined as per FRMCS Service Stratum based on MCX control plane (FRMCS Service Control Plane) and MCX user plane (FRMCS Service User Plane) client interfaces and information flows. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.3 FRMCS Trackside Gateway functionalities | The FRMCS Trackside Gateway hosts the FRMCS Service Stratum functions when the FRMCS Trackside Gateway is configured to serve a Loose-Coupled Application (including H2H and H2N models). The detailed functional architecture of the FRMCS Trackside Gateway is depicted in Figure 5.3-1 (note that the figure does not resume a specific internal implementation variant of the different functions). ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 10 FRMCS Service Server CP/N5 or N33 M ultipath Gateway (M PG) UP/N6 TAP Service Agents Hosting Client 1 (MC Service Client 1) handling Loose-Coupled Applications Hosting Client 2 (MC Service Client 2) handling Loose-Coupled Applications Hosting Client n LC Application TSAPP Server TSAPP Trackside Gateway (TS-GW) TAP TS FRMCS Service CP and UP UserPlane handling (ApplNAT, …) UserPlane handling TAP TS I/F (incl. Trackside Service NAT, …) Figure 5.3-1: Functions of FRMCS Trackside Gateway The following functions are provided by the FRMCS Trackside Gateway: • Hosting Clients: For Loose-Coupled Applications the FRMCS Trackside Gateway provides MC service clients for integration into the MC service system. • TSAPP Server: Server for handling communication via TSAPP reference point towards applications. The FRMCS Trackside Gateway shall implement the functionalities associated with the Trackside Application Network NAT Function as specified in clause 5.4.1. The FRMCS Trackside Gateway shall implement the functionalities associated with the Trackside Service NAT Function as specified in clause 5.4.2. The FRMCS Trackside Gateway shall support the functionalities required for Host-to-Network provisioning as specified in clause 6.1.2. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4 FRMCS Trackside Gateway Functions | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4.1 Trackside Application Network NAT Function | The FRMCS Trackside Gateway requires the implementation of NAT functionality when enabling communication with an On-Board FRMCS. The Trackside Application Network NAT Function is responsible for NAT for the Application Plane communication between an on-Board Loose-Coupled application and a Trackside application. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 11 When a MCData IPcon session of type Host-to-Host or Host-to-Network is established between an On-Board Loose- Coupled Application using IP address OBA1 on the Application Plane and a Trackside Loose-Coupled Application using IP address TSA1 on the Application Plane, the Trackside Application Network NAT Function shall maintain a mapping for the duration of the session between the tuple of IP addresses (OBA1, ViOB TSAx) and the tuple of IP addresses (ViTS OBA1, TSAx) where: • ViOB TSAx is a virtual IP selected by the On-Board FRMCS to represent for this session TSAx within the On-Board FRMCS. • ViTS OBA1 is a virtual IP selected by the FRMCS Trackside Gateway to represent for this session OBA1 within the FRMCS Trackside Gateway. When a Host-to-Host or Host-to-Network session is terminated, the Trackside Application Network NAT Function shall delete the mapping between the two tuple of IP addresses it created at session establishment. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4.2 Trackside Service NAT Function | The FRMCS Trackside Gateway requires the implementation of NAT functionality when enabling communication with an On-Board FRMCS. The Trackside Service NAT Function is responsible for NAT or the following particular aspects listed in the bullet point s below: • For the FRMCS Service Control Plane communication between a MC Service Client within the FRMCS Trackside Gateway towards the FRMCS Service Domain. • For the FRMCS Service User Plane communication between a MC Service Client within the FRMCS Trackside Gateway and, for example, a MC Service Client within the On-Board FRMCS. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5 FRMCS Trackside Gateway interfaces | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.0 Introduction | As defined in clause 5.2, the FRMCS Trackside Gateway supports two interfaces: • TSAPP. • TAP TS. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.1 TSAPP | The TSAPP interface is the interface between trackside applications and the FRMCS Trackside Gateway. The FRMCS Trackside Gateway shall implement the procedures associated to the TSAPP interface specified in clause 6.3. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.2 TAP TS | The TAP TS reference point connects the FRMCS Trackside Gateway and a FRMCS Domain. The FRMCS Trackside Gateway acts a MC Service Client over the TAP TS reference point. The TAP TS is composed of the MC Client reference points identified in ETSI TS 103 765-2 [2], clause 5.1.2. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 12 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6 FRMCS Trackside Gateway procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1 General procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1.1 General provisioning | The FRMCS Trackside Gateway needs to be provisioned as part of the FRMCS Railway Trackside Profile (defined in ETSI TR 103 791 [i.1]) with configuration data to enable the operation over the TSAPP. This includes in particular: • Mapping rules to derive a MC User ID for a Loose-Coupled Application doing a Local Binding. • Mapping rules to derive a destination MC Service User ID/Functional Alias for the recipient of a FRMCS-Trackside-Gateway-initiated session. • MC credentials associated to MC User IDs. • Scope (see ETSI TS 123 280 [4], clause B.4.2.2) associated to MC User IDs. • IMS/SIP credentials associated to MC User IDs. • Specific configuration related to Host-to-Network (see clause 6.1.2). NOTE: The detailed contents of the FRMCS Railway Trackside Profile is not specified in the present document. It is planned to be formalized in a UIC document following the lessons learned from the industrial testing and validation programmes currently ongoing as of time of publication. Nevertheless, the present document indicates when information from the FRMCS Railway Trackside Profile is necessary to the execution of a procedure. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1.2 Host-to-Network provisioning | To enable the MCData IPcon session establishment procedures and the data transfer procedures specified in ETSI TS 103 765-2 [2], clauses 6.2.2.3 and 6.2.2.4 for Host-to-Network operation, the FRMCS Trackside Gateway relies on the provisioning of information associated to the network towards which it enables the connectivity. For each IP network for which it enables Host-to-Network operation, the FRMCS Trackside Gateway shall: • be configured with the MC Service User ID to use for that network; • be configured with the required credentials to execute the MC user registration procedure as specified in ETSI TS 103 765-2 [2], clause 6.1; • be configured with the IP address of the DNS server associated to that network; • be configured with a route towards the gateway associated to that network; • be configured in a way that the Trackside Application Network NAT Function can determine adequate NATing to enable routing of NATed IP addresses from and towards that network. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2 Procedures not associated to a reference point | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.1 MC Service Client IP assignment procedure | At setup of an MC Service Client inside the FRMCS Trackside Gateway an IP address shall be assigned for the Interface towards the TAP TS. The IP address assignment may be set statically based on configuration inside the FRMCS Trackside Gateway or set dynamically via locally-defined dynamic IP address assignment methods when the MC Service Client can act as a standard IP-host in the IP network associated to the TAP TS reference point. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 13 The IP address assignment procedure shall ensure IP connectivity of the MC Service Client to the FRMCS service control according to local IP network requirements. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.2 MC Service Client readiness procedure | The following steps are undertaken: 1) The FRMCS Trackside Gateway shall retrieve from FRMCS Railway Trackside 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 [5], clause B.4.2.2); d) the IMS/SIP credentials associated to this MC User ID in the Home (and Foreign, if relevant) FRMCS Domain(s). NOTE: The implementation of the storage of the FRMCS Railway Trackside Profile is out of scope of the present document. 2) The MC Service 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. 3) If the application is in the Application_Locally_Bound state, the FRMCS Trackside Gateway 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 6.3.3.2 of the present specification. The JSON structure being passed is of type "fsdAvlNotif" (as specified in FRMCS FFFIS-7950 [1], clause 10.9.1.12) filled as follows: a) The fsdAVL field shall be set to TRUE. b) The nwTransition field shall be set to FALSE. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.3 MC Service 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 6.3.3.2 of the present specification. 2) For each ongoing communication associated to the MC Client, the ongoing communication release shall be performed as specified in clause 6.2.5. 3) For each MC Service User associated with the application, the FRMCS Trackside Gateway shall execute the MC user deregistration procedure as specified in ETSI TS 103 765-2 [2], clause 6.3. 4) The FRMCS Trackside Gateway 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 6.3.3.2. 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) After steps 3 and 4, 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 6.3.3.2 of the present document. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 14 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.4 TSAPP Application Context clearance procedure | The following steps are undertaken: 1) For each ongoing session associated with the application, the FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The FRMCS Trackside Gateway shall clear the TSAPP application context associated with the TSAPP application tuple. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.5 Ongoing communication release | The following steps are undertaken for releasing an ongoing communication associated to a Loose-Coupled Application: 1) The FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) 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 6.3.3.2 of the present specification. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.6 Logging | For all procedures specified in clause 6.3, the FRMCS Trackside Gateway shall log the endpoint invocations which lead to a HTTP status code 400, 401, 403 or 404. For all procedures specified in clause 6.3.2 (/sessions), the FRMCS Trackside Gateway shall log all endpoint invocations. For each logged event, the FRMCS Trackside Gateway shall capture: • Timestamp (ISO 8601 [9] as UTC). • Source IP and TSAPP Application Tuple (appCategory, staticId). • HTTP method + endpoint + status code. • Specific parameters: - SessionId for session endpoints The FRMCS Trackside Gateway shall not include sensitive information like credentials or passwords in logged events. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3 Procedures associated with TSAPP endpoints | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.0 Introduction | The present clause specifies the behaviour expected from the FRMCS Trackside Gateway in relation with the TSAPP reference point as specified in FRMCS FFFIS-7950 [1]. For all TSAPP endpoint procedures defined below, the FRMCS Trackside Gateway 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. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 15 • 404 Not Found: Resource (dynamicId/sessionId/channel) not found. Additional specific behaviours are noted in individual procedures below. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1 /registrations endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.1 Application registration procedure | Upon invocation of the "/registrations" endpoint with the HTTP POST verb, the FRMCS Trackside Gateway is expected to create an TSAPP Application Context for the application. The following steps are undertaken: 1) If a TSAPP Application Context associated with a TSAPP Application Tuple already exists in the FRMCS Trackside Gateway, the FRMCS Trackside Gateway shall execute the TSAPP Application Context clearance procedure as specified in clause 6.2.4. 2) The FRMCS Trackside Gateway shall create a TSAPP Application Context for the TSAPP Application Tuple. 3) The FRMCS Trackside Gateway shall set the application state to Application_Registered. 4) The FRMCS Trackside Gateway shall respond with a 201 Created response code as specified in FRMCS FFFIS-7950 [5], clause 10.1.8.4. The JSON structure being passed is of type "RegisteredData" with a newly generated dynamicId as specified in FRMCS FFFIS-7950 [5], clause 10.1.8.5. NOTE: For the Local Binding to be complete, the application is expected to open the notification event stream (clause 6.3.3.1). |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.2 Application-initiated deregistration procedure | Upon invocation of the "/registrations/{dynamicId}" endpoint with the HTTP DELETE verb, the FRMCS Trackside Gateway is expected to clean up any context associated to the application. The following steps are undertaken: 1) For each ongoing MCData IPcon session associated with the application, the FRMCS Trackside Gateway 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 FRMCS Trackside Gateway shall execute the MC user deregistration procedure as specified in ETSI TS 103 765-2 [2], clause 6.3. 3) In parallel to steps 2 and 3, the FRMCS Trackside Gateway shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 10.8.2. 4) The FRMCS Trackside Gateway shall clear the TSAPP Application Context associated to the TSAPP Application Tuple. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.3 FRMCS-Trackside-Gateway-initiated deregistration procedure | The following steps are undertaken: 1) For each application in Locally Bound state: a) the FRMCS Trackside Gateway shall notify the application of its upcoming 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 6.3.3.2 of the present specification; and b) the FRMCS Trackside Gateway shall start a deregistration timer, T_DEREGISTRATION_TIMER, allowing the applications to take actions (e.g. for cleaning up their contexts). ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 16 2) At the expiry of the T_DEREGISTRATION_TIMER a) For a Loose-Coupled Application: i) The FRMCS Trackside Gateway shall perform for each ongoing session the ongoing communication release as specified in clause 6.2.5. ii) The FRMCS Trackside Gateway shall execute the MC Client teardown procedure as specified in clause 6.2.3 of the present specification. iii) The FRMCS Trackside Gateway shall perform the TSAPP Application Context clearance procedure as specified in clause 6.2.4. b) For a Tight-Coupled Application, the FRMCS Trackside Gateway shall perform the TSAPP Application Context clearance procedure as specified in clause 6.2.4. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2 /sessions endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.1 FRMCS-Trackside-Gateway-initiated session initiation procedure | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP POST verb, the FRMCS Trackside Gateway is expected to open a session towards a remote endpoint. In the following, the parameters communicationCategory, localAppIPAddress, and recipient (containing remoteId) are those retrieved from the JSON payload of request. The following steps are undertaken: 1) The FRMCS Trackside Gateway shall check in the FRMCS Railway Trackside Profile that the requesting application is authorized to initiate an FRMCS-Trackside-Gateway-initiated session. If the requesting application is not authorized, the FRMCS Trackside Gateway shall respond with a 403 Forbidden response code as specified in FRMCS FFFIS-7950 [1], clause 10.10.1. 2) The FRMCS Trackside Gateway shall respond with a 201 Created response code. The JSON structure being passed is of "TSSessionOpenedData" and includes a newly generated sessionId as specified in FRMCS FFFIS-7950 [1], clause 10.10.1. 3) If the MC Service Client readiness procedure has not been executed for the application, the FRMCS Trackside Gateway shall execute the MC Service Client readiness procedure as specified in clause 6.2.2 of the present document. 4) The FRMCS Trackside Gateway shall retrieve: a) From the FRMCS Railway Trackside Profile: i) the destination MC Service User ID/Functional Alias associated to remoteId field of the TSAPP request; and ii) the Communication Session Category (ETSI TS 103 765-2 [2], clause 6.2.5) associated to communicationCategory field of the TSAPP request. b) The IP address provided by the application in the localAppIPAddress field of the TSAPP request. 5) The FRMCS Trackside Gateway shall execute the MCData IPcon session establishment procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.2.1 with the MC Service User ID/Functional Alias for the recipient(s) and the Communication Session Category determined at the previous step. 6) Upon success of the procedure in step 5, the FRMCS Trackside Gateway shall set up a route and an associated NAT for IP packets coming from the tunnel established at step 5 to the Local Application IP address provided in the JSON payload of the POST request. In addition, the FRMCS Trackside Gateway shall add the sessionId to the TSAPP Application Context. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 17 7) The FRMCS Trackside Gateway shall notify the application with a final answer on the notification event stream associated to the application as specified in clause 6.3.3.2: a) The JSON structure being passed is of type "openSessionFinalAnswerNotif" (as specified in FRMCS FFFIS-7950 [1], clause 10.9.1) filled as follows: i) Upon success of the procedure at step 5, the openSessionFinalAnswerNotif is of type "success" with the following structure: 1) The sessionId field shall be set to the sessionId sent at step 2. 2) The nextHopIPAddress field shall be set to the local FRMCS Trackside Gateway IP address to be used by the application for the session. 3) In the case of a Host-to-Host addressing mode session, the destApplicationIPAddress field shall be set to the virtual IP address representing the On-Board Application within the FRMCS Trackside Gateway for this TSAPP session. ii) Upon 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 2. 2) The ErrorCause field shall be set as in Table 6.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: In case 3 from Table 6.3.2.1-1, the FRMCS Trackside Gateway can perform a number of retrials of MCData IPcon establishment before sending openSessionFinalAnswerNotif to the application. iii) Upon decline of the procedure at step 5, the openSessionFinalAnswerNotif is of type "declined" with the following structure: 1) The sessionId field shall be set to the sessionId sent at step 2. 2) The ErrorCause field shall be set to REMOTE_ENDPOINT_DECLINED. 3) The ErrorDetail field can provide more details. Table 6.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 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.2 FRMCS-Trackside-Gateway-initiated session termination procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP DELETE verb, the FRMCS Trackside Gateway is expected to terminate the referred session. The following steps are undertaken: 1) The FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The FRMCS Trackside Gateway shall unset the route and an associated NAT 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-4 V1.1.1 (2026-01) 18 If all the previous steps are successful, the FRMCS Trackside Gateway shall respond with a 204 No Notification response code and include a payload as specified in FRMCS FFFIS-7950 [1], clause 10.10.4. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.3 FRMCS-Trackside-Gateway-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 Service Client associated with a Loose-Coupled Application, the FRMCS Trackside Gateway is expected to notify the application. The following steps shall be undertaken: 1) If the parameters fetched from the FRMCS Trackside Application Profile indicate that the application is not allowed to receive incoming sessions, the FRMCS Trackside Gateway 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.1 with warning text "FRMCS-Terminating application is not allowed to receive an incoming session" to reject the request. 2) The FRMCS Trackside Gateway shall notify the application of the incoming session request on the notification event stream associated to the application as specified in clause 6.3.3.2. a) The JSON structure being passed is of type "incomingSessionNotif" (as specified in FRMCS FFFIS-7950 [1], clause 10.9.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. 3) The FRMCS Trackside Gateway shall start a timer T_INCOMING_SESSION associated with the application and the session. 4) If the timer T_INCOMING_SESSION set at step 3 expires before being cleared, the FRMCS Trackside Gateway 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.1 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 according to ETSI TS 124 229 [i.4] is presumed. If T_INCOMING_SESSION is shorter than SIP Timer B, the normative statement of step 4 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 6.3.2.4. 6.3.2.4 FRMCS-Trackside-Gateway-terminated incoming session response procedure Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP PUT verb, the FRMCS Trackside Gateway 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 FRMCS Trackside Gateway shall clear the timer T_INCOMING_SESSION associated with the application and the session. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 19 2) If the field incomingSessionAppResponse in the IncomingSessionNotificationResponseData JSON payload is set to "accepted": a) The FRMCS Trackside Gateway shall provide the MC Service Client associated with the application with the IP address provided by the application in the field localAppIPAddress. b) The MC Service 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.1 and include the IP address provided at step 2.a as part of the <application-data> element within the AnyExt extension field. c) The FRMCS Trackside Gateway shall respond with a 201 Created response code as specified in FRMCS FFFIS-7950 [1], clause 10.10.5. 3) If the field incomingSessionAppResponse in the IncomingSessionNotificationResponseData JSON payload is set to "rejected": a) The MC Service 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.1 to reject the SIP INVITE request. b) The FRMCS Trackside Gateway shall respond with a 204 No Notification response code as specified in FRMCS FFFIS-7950 [1], clause 10.10.5. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.5 FRMCS-Trackside-Gateway-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 TSAPP 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 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 6.3.3.2. 2) The FRMCS Trackside Gateway 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. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.6 Information query on ongoing sessions for an application | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide information on the ongoing sessions associated to the application. If the query is authorized, the FRMCS Trackside Gateway shall respond with a 200 OK response code as specified in FRMCS FFFIS-7950 [5], clause 10.10.3. The JSON structure being passed is of type "SessionsListData" (as specified in FRMCS FFFIS-7950 [5], clause 10.10.3.2). |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.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 FRMCS Trackside Gateway is expected to provide information on the designated session. If the query is authorized, the FRMCS Trackside Gateway shall respond with a 200 OK response code as specified in FRMCS FFFIS-7950 [5], clause 10.10.2. The JSON structure being passed is of type "SessionStatusData" (as specified in FRMCS FFFIS-7950 [5], clause 10.10.2.2). |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3 /notifications endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3.1 Procedure for opening the notification event stream | Upon invocation of the "/notifications/{dynamicId}/events" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to open an SSE notification stream towards the application. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 20 The following steps are undertaken: 1) The FRMCS Trackside Gateway shall register the notification types identified in FRMCS FFFIS-7950 [5], clause 10.9.1.2 in the TSAPP Application Context. NOTE: The notifications associated to a TSAPP session (i.e. OpenSessionFinalAnswerNotif, IncomingSessionNotif, and SessionClosureNotif) are only relevant to Loose-Coupled applications. 2) The FRMCS Trackside Gateway shall open an SSE event stream and respond with a 200 OK response code. 3) The FRMCS Trackside Gateway shall set the application state to Application_Locally_Bound. 4) If the application is a Loose-Coupled Application for which "Trackside-application-terminated sessions" are allowed in FRMCS Railway Trackside Profile and if the MC Service Client readiness procedure has not yet been executed for the application, the FRMCS Trackside Gateway shall execute the MC Service Client readiness procedure as specified in clause 6.2.2 of the present specification. 5) If the application is a Loose-Coupled Application and the MC Service Client readiness procedure has been successfully executed for the application, the FRMCS Trackside Gateway shall notify the application of the availability of the FRMCS Service Domain on the notification event stream associated to the application as specified in clause 6.3.3.2: a) The JSON structure being passed is of type "fsdAvlNotifData" (as specified in FRMCS FFFIS-7950 [1], clause 10.9.1.12) filled as follows: i) The fsdAVL field shall be set to TRUE. ii) The nwTransition field shall be set to FALSE. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3.2 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. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.4 /versions endpoint procedures | Upon invocation of the "/versions" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide the list of versions it supports. The following steps are undertaken: 1) The FRMCS Trackside Gateway shall prepare an API VersionsData data structure with the list of versions supported as specified in FRMCS FFFIS-7950 [1], clause 10.7. 2) The FRMCS Trackside Gateway shall respond with a 200 OK response code as specified in FRMCS FFFIS-7950 [1], clause 10.7. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.5 /keepalive endpoint procedures | Upon invocation of the "/keepalive" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide a HTTP-level response to indicate the TSAPP reference point is responsive. The FRMCS Trackside Gateway shall respond with a 204 No Content response code as specified in FRMCS FFFIS-7950 [1], clause 10.11. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 21 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7 VAS-Controller Equipment connection | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7.1 Functions | VAS Controller functions are not specified in the present document. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7.2 Interfaces | The reference point between VAS Controller Equipment and FRMCS System is TSCTRL. The VAS Controller Equipment (Dispatcher System) shall support the following ETSI reference points to access FRMCS service domain: • CSC-1, CSC-2, CSC-4 and CSC-8 for the FRMCS Service User Plane as specified in ETSI TS 123 280 [4], clauses 7.5.2.2, 7.5.2.3, 7.5.2.5 and 7.5.2.8. • MCPTT-1 and MCPTT-4 for the FRMCS Service Control Plane (Voice) as specified in ETSI TS 123 379 [7], clauses 7.5.2.2 and 7.5.2.5. • MCPTT-7 for the FRMCS Service Media Plane (Voice) as specified in ETSI TS 123 379 [7], clause 7.5.2.8. • MCData-7 for the FRMCS Service User Plane as specified in ETSI TS 123 282 [8], clause 6.4.4.1.6. • MCData-SDS-1 for the FRMCS Service Control Plane (Data) as specified in ETSI TS 123 282 [8], clause 6.5.4.1.1. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 22 History Version Date Status V1.0.0 July 2025 SRdAP process EV 20251008: 2025-07-10 to 2025-10-08 V1.1.1 January 2026 Publication |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 1 Scope | The present document specifies the interfaces of the On-Board FRMCS enabling either interaction with On-Board applications or with FRMCS entities outside the train. The present document also specifies the On-Board Multipath Function and a set of procedures the On-Board FRMCS will need to conform to. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 2 References | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 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] ETSI TS 103 765-1: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 1: Transport Stratum". [2] ETSI TS 103 765-2: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 2: Service Stratum". [3] ETSI TS 103 765-5: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 5: User Equipment (UE) capabilities". [4] ETSI TS 103 793: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Radio Characteristics". [5] UIC FFFIS-7950 (V2.1.0): "FRMCS FFFIS Form Fit Functional Interface Specification". [6] IETF RFC 6960: "X.509 Internet Public Key Infrastructure, Online Certificate Status Protocol - OCSP". [7] IETF RFC 9654: "Online Certificate Status Protocol (OCSP) Nonce Extension". [8] IETF RFC 6066: "Transport Layer Security (TLS) Extensions: Extension Definitions". [9] IETF RFC 6961: "The Transport Layer Security (TLS) Multiple Certificate Status Request Extension". [10] IETF RFC 8555: "Automated Certificate Management Environment (ACME)". [11] IETF RFC 7030: "Enrollment over Secure Transport". [12] 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)". [13] 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)". [14] ISO 8601 (2019): "Date and time — Representations for information interchange". ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 7 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 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] UIC FRMCS SRS: "FRMCS System Requirements Specification". [i.2] ETSI TR 103 791: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Terminology for FRMCS specifications". [i.3] GSMA™ SGP.21 V3.1: "RSP Architecture". [i.4] GSMA™ SGP.22 V3.1: "RSP Technical Specification". [i.5] 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.6] ETSI TS 103 764: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); System Architecture". |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3 Definition of terms, symbols and abbreviations | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.2] and the following apply: OBAPP Application Context: context maintained by the On-Board FRMCS for an application instance (identified by the OBAPP Application Tuple), in between registration and de-registration OBAPP Application Tuple: tuple of appCategory, staticId, couplingMode NOTE: As specified in UIC FRMCS FFFIS-7950 [5], clause 9.10.1. service continuity: capability of the FRMCS system to maintain the communication service for the user in an acceptable level during the Inter-FRMCS-Domain Transition Serving FRMCS Transport/Service Domain: FRMCS Transport/Service Domain which is currently carrying/serving the communications of applications of Type I (IM interoperable applications) NOTE: In the Inter-FRMCS-Transport-Domain transition procedure, this is the FRMCS Transport/Service Domain before the transition takes place. Serving On-Board FRMCS Radio Module: On-Board FRMCS Radio Module carrying in the Serving FRMCS Transport Domain at least the active communication services for applications of Type I (IM interoperable applications) with service continuity requirement Target FRMCS Transport/Service Domain: FRMCS Transport/Service Domain which is the target of network transition for applications of Type I (IM interoperable applications) NOTE: At the completion of network transition (from GSM-R or from a previous FRMCS Domain), the Target FRMCS Domain becomes the Serving FRMCS Domain. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 8 Target On-Board FRMCS Radio Module: On-Board FRMCS Radio Module which is intended to be attached to the Target FRMCS Transport Domain following the FRMCS domain transition NOTE: At the completion of network transition (from GSM-R or from a previous FRMCS Domain), the Target On-Board FRMCS Radio Module becomes the Serving On-Board FRMCS Radio Module in the new FRMCS Domain. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.2 Symbols | Void. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACME Automated Certificate Management Environment API Application Programming Interface CellID Cell IDentifier EST Enrollment over Secure Transport FA Functional Alias FCOP FRMCS Close of OPeration FFFIS Form Fit Functional Interface Specification FOAP FRMCS On-Board Application Profile FRMCS Future Railway Mobile Communication System FROP FRMCS Railway On-Board Profile FSOP FRMCS Start of OPeration GNSS Global Navigation Satellite System GSMA GSM Association GSM-R Global System for Mobile Communications - Railway HSM Hardware Security Module HTTP Hyper Text Transfer Protocol ID Identity IdM Identity Management IETF Internet Engineering Task Force IFDT Inter FRMCS Domain Transition IFSDT Inter-FRMCS Service Domain Transition IM Infrastrcuture Manager IMS IP Multimedia Subsystem IP Internet Protocol ISO International Organisation for Standardisation JSON JavaScript Object Notation MC Mission Critical NTT Network Transition Trigger OCSP Online Certificate Status Protocol PLMN Public Land Mobile Network RFC Request For Comments RSP Remote SIM Provisioning SDS Short Data Service SIM Subscriber Identity Module SIP Session Initiation Protocol SRS System Requirement Specification SSE Server Sent Events TLS Transport Layer Security TPM Trusted Platform Module UIC International Union of Railways UTC Coordinated Universal Time ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 9 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4 On-Board FRMCS reference points | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.1 Background | This clause covers the external reference points of the On-Board FRMCS (see Figure 4.1-1) as defined in UIC FRMCS SRS [i.1]. On-Board FRMCS Application(s) OBAPP FSOMR OBANT OBOM Figure 4.1-1: On-Board FRMCS external reference points |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.2 OBApp | The on-board communication system will interact with several on-board applications. Due to this, the interface OBAPP has to ensure the proper handling and management of the interconnected applications and grant access to the communication services provided taking into account the priority and quality of service profile requested by those applications. The OBAPP reference point is fully specified in UIC FRMCS FFFIS [5]. The behaviour expected from the On-Board FRMCS in relation with the OBAPP is specified in clause 7.3. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3 FSOMR | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3.1 Introduction | The present document only covers a subset of FSOMR functionality defined in UIC FRMCS SRS [i.1], namely those for the purpose of obtaining FRMCS Railway On-Board Profile (FROP) and FRMCS On-Board Application Profile (FOAP). |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3.2 Profiles management | The FSOMR enables profiles management in FRMCS for the On-Board FRMCS across three essential functionalities: • SIM profile management. • TLS certificates management. • Management of other profile information. For SIM profile management, the functionalities are delegated to individual On-Board FRMCS Radio Modules using the GSMA Remote SIM Provisioning architecture (see GSMA SGP.21 [i.3] and GSMA SGP.22 [i.4]), as specified in ETSI TS 103 765-5 [3], clause 4.1.2. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 10 For TLS certificates management, the On-Board FRMCS shall support: • For certificates revocation checking: - The Online Certificate Status Protocol (OCSP) with extensions as specified in IETF RFC 6960 [6] and IETF RFC 9654 [7]. - OCSP stapling as specified in IETF RFC 6066 [8] and IETF RFC 6961 [9]. • For automated certificate lifecycle management, one of the following protocols: - Automated Certificate Management Environment (ACME), as specified in IETF RFC 8555 [10]. - Enrollment over Secure Transport (EST), as specified in IETF RFC 7030 [11]. NOTE: For automated certificate lifecycle management, the choice of protocols reflects that different railway organizations can have different approaches on this matter. For management of other profile information, the On-Board FRMCS need to implement a MCData client with support for establishment of MCData IPcon connectivity and MCData Short Data Service. The MCData client for FSOMR within the On-Board FRMCS shall: • Support the MCData client general procedures for SDS as specified in ETSI TS 124 282 [13], clauses 9.2.1.2 and 9.2.1.3. • Support the MCData client terminating procedures for Standalone SDS using signalling control plane as specified in ETSI 124 282 [13], clause 9.2.2.2.2. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.4 OBANT | The present document does not specify the OBANT reference point or its use within an On-Board FRMCS. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.5 OBOM | The present document does not specify the OBOM reference point or its use within an On-Board FRMCS. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5 On-Board FRMCS general requirements | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.1 On-Board FRMCS Radio Modules | An On-Board FRMCS Radio Module shall comply with ETSI TS 103 765-5 [3], clause 4. An On-Board FRMCS Radio Module shall comply with ETSI TS 103 793 [4], clauses 4 and 6. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2 Location and positioning | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2.1 Generalities | The On-Board FRMCS is expected to provide location information based on three possible sources: cellular network, GNSS and external sources. Obtaining information from external sources is out of scope of the present document. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 11 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2.2 Functional requirements | The On-Board FRMCS shall be equipped with a GNSS receiver. The GNSS receiver of the On-Board FRMCS shall be capable of receiving and processing signals from at least two satellite constellations. The On-Board FRMCS shall be able to obtain CellID information from each of its On-Board FRMCS Radio Modules. NOTE: The present document does not specify the criteria to select one CellID among several different ones received by the On-Board FRMCS Radio Modules. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.3 Profile Storage | The support of Loose-Coupled Applications by an On-Board FRMCS and the distribution of functionalities between the MC Clients within the On-Board FRMCS on the one hand and the On-Board FRMCS Radio Module(s) on the other hand imply that the On-Board FRMCS has to store and manage sensitive information (such as credentials) that would traditionally be stored within a SIM card. The On-Board FRMCS shall be equipped with a secure enclave, i.e. a tamper resistant secure hardware component (e.g. TPM, HSM) or equivalent storage protection mechanisms. NOTE 1: The present document does not specify specific requirements on the implementation of the secure enclave. The On-Board FRMCS shall store at least the following elements in the secure enclave: • Credentials associated with each MC User ID required by supported On-Board Loose-Coupled Applications. • IMS/SIP Core credentials associated with each MC User ID required by supported On-Board Loose-Coupled Applications. NOTE 2: The Voice Application Service or other Tight-Coupled Applications are expected to be equipped with their own secure profile storage capabilities. The credentials shall be integrity protected within the On-Board FRMCS secure enclave. The long-term key(s) of the subscription credential(s) shall be confidentiality protected within the On-Board FRMCS secure enclave. The long-term key(s) of the subscription credential(s) shall never be available in the clear outside of the secure enclave. The authentication algorithm(s) that make use of the subscription credentials shall always be executed within the secure enclave. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 6 On-Board Multipath Function | An On-Board FRMCS supporting FRMCS Multipath shall: • Implement a Multipath Client as specified in ETSI TS 103 765-1 [1], clause 5.3.5. • Comply with the procedures related to the Multipath Client as specified in ETSI TS 103 765-1 [1], clause 5.3.7. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 12 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7 On-Board FRMCS procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1 General procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.1 FRMCS Start of Operation | The FRMCS Start of Operation (FSOP) procedure is supporting the transition of On-Board FRMCS operational mode from the train power-up until the moment On-Board FRMCS is in FRMCS Domain availability state. The procedure describes the expected behaviour from On-Board FRMCS and FRMCS Domain upon power-up of the train and the attempt from an On-Board FRMCS to acquire the FRMCS Domain. Pre-requisite: The On-Board FRMCS knows the FRMCS Transport Domain to connect to. The following steps are undertaken: 1) The On-Board FRMCS shall select one or more On-Board FRMCS Radio Modules. The mechanism for selection is not specified in the present document. 2) For each On-Board FRMCS Radio Module selected at the previous step, the On-Board FRMCS shall execute the On-Board FRMCS Radio Module registration to the FRMCS Transport Domain procedure as specified in ETSI TS 103 765-1 [1], clause 6.1. 3) The On-Board FRMCS shall select one On-Board FRMCS Radio Module amongst the On-Board FRMCS Radio Modules selected at step 2 to use for FRMCS Multipath discovery. 4) The On-Board FRMCS shall execute the FRMCS Multipath discovery procedure as specified in ETSI TS 103 765-1 [1], clause 5.3.7.1 with the On-Board FRMCS Radio Module selected at the previous step. 5) The On-Board FRMCS shall retrieve from the FRMCS Railway On-Board Profile the list of Startup Applications and their associated parameters. The mechanism for retrieval of the information from the FRMCS Railway On-Board Profile is not specified in the present document. 6) For each Loose-Coupled Application identified at the previous step, the On-Board FRMCS shall execute the MC Client IP assignment procedure as specified in clause 7.2.1 of the present document and assign it to a MC Client. The mechanism for selection of a MC Client to assign is not specified in the present document. 7) For each Loose-Coupled Application identified at the previous step, if the FRMCS Multipath discovery (step 4) was successful and if FRMCS Multipath is enabled according to the FRMCS Railway On-Board Profile (step 5), the On-Board FRMCS shall execute the FRMCS Multipath data path selection procedure as specified in ETSI TS 103 765-1 [1], clause 5.3.7.2 with the FRMCS Multipath parameters obtained at step 5. 8) The On-Board FRMCS shall execute the Transport path establishment for Mission Critical signalling procedure as specified in ETSI TS 103 765-1 [1], clause 6.2. 9) For each Tight-Coupled Application identified at step 5 and in Locally Bound state, the On-Board FRMCS shall notify the application of the availability of the FRMCS Transport Domain by sending a notification of type ftdAvlNotif on the notification event stream associated with the application as specified in clause 7.3.3.5 of the present document. 10) For each Loose-Coupled Application identified at step 5, the MC Client assigned to the application at step 6 should execute the MC Client readiness procedure as specified in clause 7.2.2. NOTE: The timely execution of the procedure at step 11 would allow a faster session establishment time. It is left to implementation as to when the On-Board FRMCS executes the procedure. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.2 FRMCS Close of Operation | The FRMCS Close of Operation (FCOP) procedure describes the expected behaviour of On-Board FRMCS and FRMCS Domain upon attempt by an On-Board FRMCS to disconnect from the FRMCS System. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 13 The following steps are undertaken: 1) For each application in Locally Bound state: a) the On-Board FRMCS shall notify the application of its upcoming deregistration from the On-Board FRMCS by sending a notification of type upcomingDeregistration on the notification event stream associated with the application as specified in clause 7.3.3.5; and b) the On-Board FRMCS shall start a deregistration timer, T_DEREGISTRATION_TIMER, allowing the applications to take actions (e.g. for cleaning up their contexts). 2) At the expiry of the T_DEREGISTRATION_TIMER: a) For a Loose-Coupled Application: i) The On-Board FRMCS shall perform for each ongoing session the ongoing communication release as specified in clause 7.2.6. ii) The On-Board FRMCS shall execute the MC Client teardown procedure as specified in clause 7.2.4. iii) The On-Board FRMCS shall perform the OBAPP Application Context clearance procedure as specified in clause 7.2.5. b) For a Tight-Coupled Application: i) The On-Board FRMCS shall perform the OBAPP Application Context clearance procedure as specified in clause 7.2.5. 3) If a FRMCS Multipath control link is established, the On-Board FRMCS shall execute the Multipath Control Protocol cleanup procedure as specified in ETSI TS 103 765-1 [1], clause 5.3.7.6. 4) For each On-Board FRMCS Radio Module, the On-Board FRMCS shall execute the On-Board Radio Module deregistration to the FRMCS Transport Domain procedure as specified in ETSI TS 103 765-1 [1], clause 6.3. 7.1.3 Inter-FRMCS Domain Transition using two On-Board FRMCS Radio Modules |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.1 Inter-FRMCS Domain Transition (IFDT) 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. • The Target On-Board FRMCS Radio Module is different from the Serving On-Board FRMCS Radio Module and does not carry any other communication which requires service continuity. The following steps are undertaken: 1) For each ongoing communication carried by the Target On-Board FRMCS Radio Module, the On-Board FRMCS shall perform the ongoing communication release as specified in clause 7.2.6. 2) The On-Board FRMCS shall perform the registration of the Target On-Board FRMCS Radio Module in the Target FRMCS Transport Domain as specified in ETSI TS 103 765-1 [1], clause 6.1. 3) 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 as specified in ETSI TS 103 765-1 [1], clause 6.2. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 14 NOTE 1: In the case of IFDT with dual On-Board FRMCS Radio Modules, during the transition, the On-Board FRMCS can still maintain a transport path on the Serving On-Board FRMCS Radio Module towards the Serving FRMCS Domain (e.g. for the purpose MC signalling that allows the proper release of an ongoing communication in Serving FRMCS Service Domain during the transition - see step 4b). NOTE 2: If the Serving FRMCS Service Domain is not the Home FRMCS Service Domain, the On-Board FRMCS also 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). 4) For each Loose-Coupled Application in Locally Bound state and identified as Type I or III in the FRMCS Railway On-Board Profile: a) If the application has no open session, the On-Board FRMCS shall execute the procedure identified in clause 7.1.3.2.1. b) If the application has an open session, the On-Board FRMCS shall execute the procedure identified in clause 7.1.3.2.2. 5) For each Loose-Coupled Application in Locally Bound state and identified as Type II in the FRMCS Railway On-Board Profile: a) 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.3.3.1. b) If the On-Board FRMCS is entering a FRMCS Domain which is not in the Domain of applicability of the application, the On-Board FRMCS shall execute the procedure identified in clause 7.1.3.3.2. 6) 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. 7) 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: i) The ftdAVL field shall be set to TRUE. ii) The nwTransition field shall be set to TRUE. iii) 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. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 15 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.2 Inter-FRMCS Domain transition: Type I or Type III applications | 7.1.3.2.1 Inter-FRMCS Domain transition: Type I or Type III applications with no open session For each Loose-Coupled Application in Locally Bound state and identified as interoperable in any FRMCS Domain in the FRMCS Railway On-Board Profile, if the application has no open session, the following steps are undertaken: 1) One of the following cases is performed depending on whether the Target FRMCS service Domain is the Home FRMCS Service Domain or a Foreign FRMCS Service Domain: a) If the Target FRMCS Service Domain is a Foreign FRMCS Service Domain, the On-Board FRMCS shall perform the "MC Service User migration" procedure between Serving FRMCS Service Domain and Target FRMCS Service Domain as specified in ETSI TS 103 765-2 [2], clause 6.4.1, using the MC credentials and IMS credentials retrieved from the FRMCS Railway On-Board Application. b) If the Target FRMCS Service Domain is the Home FRMCS Service Domain, the On-Board FRMCS shall perform "MC User registration" in Home FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.1). If the step is unsuccessful, it shall be repeated every T_RETRY_MCUSR_MIG seconds for a maximum of N_RETRY_MCUSR_MIG times before it can be considered as a failure in step 4. 2) If the Serving FRMCS Service Domain is not the Home FRMCS Service Domain, the On-Board FRMCS shall perform "Migrated MC Service User deauthorization" in Serving FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.4.2). NOTE: This procedure is performed on the same MC User ID which was serving the application in the Serving FRMCS Service Domain before the transition. 3) 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. 4) 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. 7.1.3.2.2 Inter-FRMCS Domain transition: Type I or Type III applications with an open session For each Loose-Coupled Application in Locally Bound state and identified as interoperable in any FRMCS Domain in the FRMCS Railway On-Board Profile, if the application has at least one open session, the following steps are undertaken: 1) If the FRMCS Railway On-board Profile for the Loose-Coupled Application does not include the "IFSDT_Dual_MCID" parameter: a) The On-Board FRMCS shall perform the "MCData IPcon release" procedure as specified in ETSI TS 103 765-2 [2], clause 6.2.2.5 for the open sessions in the Serving FRMCS Service Domain. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 16 NOTE 1: This allows the MC Service Server to clean up the session context but also allows the remote application endpoint to be notified of the intentional closure of this session. This step can include the release of the corresponding transport path on the Serving On-Board FRMCS Radio Module. However, the failure of this step does not prevent proceeding to the next step. b) One of the following cases is performed depending on whether the nature of the Target FRMCS service Domain: i) If the Target FRMCS Service Domain is a Foreign FRMCS Service Domain, the On-Board FRMCS shall perform the "MC Service User migration" procedure between Serving FRMCS Service Domain and Target FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.4.1), using the IMS credentials retrieved from the FRMCS Railway On-Board Application. ii) If the Target FRMCS Service Domain is the Home FRMCS Service Domain, the On-Board FRMCS shall perform "MC User registration" in Home FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.1). If the procedure is unsuccessful, it shall be repeated every T_RETRY_MCUSR_MIG seconds for a maximum of N_RETRY_MCUSR_MIG times before it can be considered as a failure in step 1e). c) If the Serving FRMCS Service Domain is not the Home FRMCS Service Domain, the On-Board FRMCS shall perform "Migrated MC Service user de-authorization" in Serving FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.4.2). NOTE 2: Step 1b) is performed on the same MC User ID which was serving the application in the Serving FRMCS Service Domain before the transition. d) If step 1b) is successful, the On-Board FRMCS shall notify the application of the availability 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: 1) The fsdAVL field shall be set to TRUE. 2) The nwTransition field shall be set to TRUE. e) If step 1b) 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: 1) The fsdAVL field shall be set to FALSE. 2) The nwTransition field shall be set to TRUE. 2) If the FRMCS Railway On-board Profile for the Loose-Coupled Application includes the "IFSDT_Dual_MCID" parameter: a) The On-Board FRMCS shall set the flag "IFSDT_DUAL_MCID_IN_PROGRESS" in the application context. b) The On-Board FRMCS shall execute the MC Client readiness procedure as specified in clause 7.2.2. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.3 Inter-FRMCS Domain transition: Type II applications | 7.1.3.3.1 Inter-FRMCS Domain 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 from the FRMCS Railway On-Board Profile, the following step is undertaken: 1) The On-Board FRMCS shall execute the MC Client readiness for network transition procedure as specified in clause 7.2.3. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 17 7.1.3.3.2 Inter-FRMCS Domain transition: Type II applications entering a FRMCS Domain which is not in the Domain of applicability For each Loose-Coupled Application which are in Locally Bound state and for which the On-Board FRMCS entering a FRMCS Domain which is not in the Domain of applicability of the application as identified from the FRMCS Railway On-Board Profile, the following steps are undertaken: 1) For open sessions associated to the Loose-Coupled Application: a) The On-Board FRMCS shall perform the "MCData IPcon release" procedure (both SIP and MC layers) in Serving FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6.2.2.5). b) 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 execute the "MC User deregistration" procedure in Serving FRMCS Service Domain as specified in ETSI TS 103 765-2 [2], clause 6.3. 3) 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: i) The fsdAVL field shall be set to FALSE. ii) The nwTransition field shall be set to TRUE. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.4 Inter-FRMCS Domain 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 FRMCS Radio Modules as specified in 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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.