hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
68307306d039047e470f288ba4891560 | 103 764 | 3.2 Symbols | Void. |
68307306d039047e470f288ba4891560 | 103 764 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 5G 5th Generation 5GC 5G Core API Application Programming Interface APP APPlication ATO Automatic Train Operation ATP Automatic Train Protection EIRENE European Integrated Railway radio Enhanced NEtwork ETCS European Train Control System FCOP FRMCS Close of OPeration FFFIS Form Fit Functional Interface Specification FIS Functional Interface Specification FRMCS Future Railway Mobile Communication System FS FRMCS System FSD FRMCS Service Domain FSOP FRMCS Start of OPeration FTD FRMCS Transport Domain GRE Generic Routing Encapsulation GSM Global System for Mobile GSM-R Global System for Mobile communications - Railway H2N Host-To-Network IM Infrastructure Manager IP Internet Protocol IWF InterWorking Function LB Local Binding MC Mission Critical MCPTT Mission Critical Push To Talk MCS Mission Critical Service MCX Mission Critical Communications MPM MultiPath Management NAT Network Address Translation NNI Network-to-Network Interface NR New Radio NTT Network Transition Trigger OB On-Board OM Operation and Maintenance OMR OM Remote Interface ONI Other Network-to-Network Interface PDU Packet Data Unit QoS Quality of Service REC Railway Emergency Communication ETSI ETSI TS 103 764 V1.1.1 (2026-01) 8 RMR Railway Mobile Radio RU Railway Undertaking SIP Session Initiation Protocol SRS System Requirements Specification SSE Server Sent Events TCMS Train Control Management System TLS Transport Layer Security UE User Equipment UIC Union Internationale des Chemins de Fer (International Union of Railways) VAS Voice Application Subsystem |
68307306d039047e470f288ba4891560 | 103 764 | 4 Architecture principles and model | |
68307306d039047e470f288ba4891560 | 103 764 | 4.1 Introduction | The present document defines the architecture for the Future Railway Mobile Communications System (FRMCS) in on-network mode. FRMCS architecture is described and specified based on a transport stratum and a service stratum. FRMCS transport stratum provides connectivity for data transport and FRMCS service stratum enables communication as services between two or multiple FRMCS Users for voice, video and data applications. The following is described: • overall architecture of FRMCS within one FRMCS Domain with principles and components; • procedures applicable for an FRMCS Domain and interactions between FRMCS Domains. FRMCS System Architecture is designed based on the high-level principles outlined in clause 4.2. In addition, the architecture reference model is described. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2 General principles | |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.0 Overview | The FRMCS System Architecture is defined to support communications between various types of FRMCS Users such as train and trackside end-users/applications, and railway personnel. The FRMCS System Architecture satisfies the following key principles: • Maximizing the decoupling between the strata to facilitate an independent evolution of the Transport Stratum and/or of the Service Stratum without mandating an evolution of the Application Stratum. • Supporting QoS and priority policies that allows differentiating the communications of different types of railway applications. • Supporting multiple Radio Access Technologies. • Supporting Service Stratum security and Transport Stratum security. • Supporting Operation and Maintenance for on-board FRMCS. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.1 Strata | The FRMCS System Architecture is structured in two strata called Service Stratum and Transport Stratum as illustrated in Figure 4.2.1-1. External to the FRMCS System, railway applications using the FRMCS System are grouped in a third stratum named Railway Application Stratum (see Figure 4.2.1-1). ETSI ETSI TS 103 764 V1.1.1 (2026-01) 9 Figure 4.2.1-1: Strata in FRMCS System Architecture The Transport Stratum provides data connectivity and corresponding services (e.g. mobility, QoS, policy control, authentication, etc.). The Service Stratum is centered around the 3GPP Mission Critical Communications (MCX) Framework and decouples the application from the underlying transport networks. The FRMCS Transport Stratum is described in more detail in ETSI TS 103 765-1 [1]. The FRMCS Service Stratum is described in more detail in ETSI TS 103 765-2 [2]. The Application Stratum is not considered to be part of the FRMCS architecture and therefore it will not be described in the present document. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.2 Modularity of deployment | The FRMCS System Architecture is intended to be deployed in different ways: • Stand-alone deployment, i.e. deployment of an FRMCS Domain with no external connection to other FRMCS Domains. • Deployment as part of an international network of networks, i.e. deployment of an FRMCS Domain connected to other FRMCS Domains. • Deployment encompassing interworking with GSM-R, deployment of an FRMCS Domain with users interacting with or moving to, or from a GSM-R system, under the control of the same operator or not. • Deployment encompassing interconnection with non-EIRENE non-FRMCS networks. The minimal deployment of the FRMCS System Architecture is that of a stand-alone FRMCS Domain. For a description of the deployment scenarios of FRMCS, see clause 7 of the present document. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.3 Modes of operation | The FRMCS System Architecture enables: • The communication of an FRMCS User served by its Home FRMCS Domain or served by a foreign FRMCS Domain. • The mobility of an FRMCS User within an FRMCS Domain as well as across FRMCS Domains. In general, mobility procedures defined at the FRMCS Transport Stratum and migration procedures defined in the FRMCS Service Stratum apply. The specific modes of operation of an On-Board FRMCS need to be taken into account: 1) In some deployment scenarios, the On-Board FRMCS is equipped with more than one On-Board Radio Module, potentially operating under the FRMCS Multipath Framework. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 10 2) The On-Board FRMCS has to facilitate the continuity of communication under mobility conditions for the applications it enables through the OBAPP reference point. For a description of high-level procedures applicable in FRMCS, see clause 6 of the present document. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.4 Applications enablement | Within trains, FRMCS applications interact with the FRMCS System via the OBAPP reference point exposed by the On-Board FRMCS. All applications directly interfacing with the On-Board FRMCS are expected to call a Local Binding procedure to authenticate themselves with the On-Board FRMCS. Subsequently, two modes of interactions are then defined, either using the standard reference points of the 3GPP MCX Framework ("tight-coupled mode") or through additional API features of the OBAPP reference point ("loose-coupled mode"). On the trackside, the FRMCS Trackside Gateway exposes the TSAPP reference point with features similar to the OBAPP reference point. When operating in "loose-coupled mode", applications are represented in the 3GPP MCX Framework by one or more MC Service User identities associated to one of the standardized mission critical services of the 3GPP MCX Framework (i.e. MCPTT, MCData and MCVideo). Four Application Types are identified in the UIC FRMCS SRS [i.3]: • Type I: Interoperable IM applications (e.g. ATP, ATO, REC, driver-controller voice communication). • Type II: Non-interoperable IM applications. • Type III: Interoperable RU applications. • Type IV: Non-Interoperable RU applications in the scope of FRMCS (e.g. TCMS). For more details on the interrelation between the API end points and the FRMCS Service Domain procedures, see ETSI TS 103 765-3 [3] for the OBAPP reference point and to ETSI TS 103 765-4 [4] for the TSAPP reference point. In addition to the above, the TSCTRL reference point (see UIC FRMCS SRS [i.3]) is exposed for the use of controller devices and applications. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.5 Cybersecurity | For an FRMCS Domain, the approach to cybersecurity in FRMCS is multi-layered by leveraging cybersecurity measures at the FRMCS Transport Stratum and FRMCS Service Stratum levels. Applications can also implement their own additional security measures at the Application Stratum level. At the periphery of an FRMCS Domain, additional cybersecurity measures are leveraged: • Between On-Board applications and the On-Board FRMCS, the OBAPP reference point specified in UIC FRMCS FFFIS-7950 [i.1] requires the usage of the Local Binding procedure which establishes a secured TLS-backed mutually-authenticated control plane link complemented by lower layers' security measures in train network deployments. • Similarly, between trackside applications and the FRMCS Trackside Gateway, the TSAPP reference point specified in UIC FRMCS FFFIS-7950 [i.1] requires the usage of the Local Binding procedure. • For a deployment as part of an international network of FRMCS Domains, requirements related to cybersecurity are identified in clause 7.3 of the present document. • For a deployment in interaction with an EIRENE GSM-R system, requirements related to cybersecurity are identified in clause 7.4 of the present document. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.6 GSM-R interworking | Requirements induced by interworking with GSM-R are specified in ETSI TS 103 792 [5]. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 11 In particular, interworking scenarios for various services (group calls, point-to-point calls, text messaging) are specified. An overview of the mobility procedure applied in GSM-R/FRMCS Domain transition is documented in clause 6.4 of the present document. |
68307306d039047e470f288ba4891560 | 103 764 | 4.2.7 FRMCS Multipath | FRMCS Multipath introduces a capability to establish communication between the On-Board FRMCS Multipath Function (called Multipath Client in ETSI TS 103 765-1 [1]) and an FRMCS Infrastructure Multipath Function (called Multipath Gateway in ETSI TS 103 765-1 [1]) over one or more data paths (called Multipath Datapaths in ETSI TS 103 765-1 [1]) for a given application, subject to FRMCS Multipath policies set in the FRMCS Domain and to parameters within the FRMCS On-Board Application. The data paths are established over one or multiple of the following Transport Domains: 1) FRMCS Transport Domain. 2) Non-FRMCS Transport Domains. The FRMCS Multipath Function is specified in ETSI TS 103 765-1 [1], clause 5.3. |
68307306d039047e470f288ba4891560 | 103 764 | 4.3 Architecture reference model | |
68307306d039047e470f288ba4891560 | 103 764 | 4.3.1 General | The interaction between functional blocks is represented with point-to-point reference points, showing how various network functions interact with each other. |
68307306d039047e470f288ba4891560 | 103 764 | 4.3.2 FRMCS System Architecture components | The FRMCS system consists of: 1) FRMCS Domain (see clause 5.1): - Transport Domain (see clause 5.1.1): FRMCS Infrastructure Multipath Function (see clause 5.7). - FRMCS Service Domain (see clause 5.1.2). 2) On-board FRMCS (see clause 5.2): - On-Board FRMCS Multipath Function (see clause 5.6). 3) FRMCS-capable Handheld (see clause 5.3). 4) FRMCS-capable Object (see clause 5.4). 5) FRMCS Trackside Gateway (see clause 5.5). The FRMCS System Architecture also allows interactions with external systems such as: 1) EIRENE System (GSM-R based System) (see clause 5.8). 2) Non-EIRENE non-FRMCS System (see clause 5.9). ETSI ETSI TS 103 764 V1.1.1 (2026-01) 12 |
68307306d039047e470f288ba4891560 | 103 764 | 4.3.3 Stand-alone reference architecture | Figure 4.3.3-1 depicts the stand-alone reference architecture of FRMCS System showing how various components relate to each other. Figure 4.3.3-1: Stand-alone reference architecture of the FRMCS System The FRMCS trust domain (see Figure 4.3.3-1) covers FRMCS communicating entities that are protected by adequate FRMCS Domain security. The FRMCS communicating entities and FRMCS reference points within the FRMCS trust domain may all be within the control of an FRMCS Operator, or some may be controlled by a trusted business partner which has a trust relationship with the FRMCS Operator e.g. another FRMCS Operator or a 3rd party. Applications that have authenticated against and have been authorized by a specific FRMCS Domain on Transport and Service Stratum level are considered to be part of the trust domain of that specific FRMCS domain. Applications operating in the FRMCS trust domain shall be able to access FRMCS communicating entities on Transport and Service Stratum level as described in ETSI TS 103 765-1 [1] and ETSI TS 103 765-2 [2]. Applications and devices situated physically and logically outside of the Trust Domain shall use the Local Binding (LB) mechanism. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 13 |
68307306d039047e470f288ba4891560 | 103 764 | 4.3.4 Interconnected reference architecture | Figure 4.3.4-1 depicts the FRMCS System Architecture in the roaming and interworking cases showing how various Systems and FRMCS Domains relate to each other. NOTE: EIRENE System (GSM-R based System) and Non-EIRENE non-FRMCS System are not components of the FRMCS System Architecture but could be interacted with in some deployment scenarios. Figure 4.3.4-1: FRMCS reference System Architecture - interconnected and interworking cases |
68307306d039047e470f288ba4891560 | 103 764 | 4.3.5 FRMCS Reference points at system level | The FRMCS System Architecture contains the following FRMCS reference points: OBAPP: Reference point between on-board Railway Application and on-board FRMCS. This reference point is described and specified in UIC FRMCS FFFIS-7950 [i.1] and the associated procedures are specified in ETSI TS 103 765-3 [3]. OBOM: Reference point between on-board Operations and Maintenance Application and on-board FRMCS. TSAPP: Reference point between trackside Railway Application and FRMCS Trackside Gateway. This reference point is described and specified in UIC FRMCS FFFIS-7950 [i.1] and the associated procedures are specified in ETSI TS 103 765-4 [4]. FSMPM: Reference point between the On-Board FRMCS Multipath Function within the On-Board FRMCS and the FRMCS Infrastructure Multipath Function. This reference point is specified in ETSI TS 103 765-1 [1]. FSIWF: Reference point between an FRMCS System and an EIRENE System (GSM-R based System). This reference point is comprised of the reference points IWF-g1, IWF-g2 and IWF-g5 specified in ETSI TS 103 792 [5]. FSNNI: Reference point between two interconnected FRMCS Domains. The functionalities applicable to FRMCS Transport Domain are specified in ETSI TS 103 765-1 [1]. The functionalities applicable to FRMCS Service Domain are specified in ETSI TS 103 765-2 [2]. FSONI: Reference point between an FRMCS System and another non-GSM-R, non-FRMCS System. The functionalities applicable to FRMCS Transport Stratum are specified in ETSI TS 103 765-1 [1]. The functionalities applicable to FRMCS Service Stratum are specified in ETSI TS 103 765-2 [2]. FSOMR: Reference point between on-board FRMCS and FRMCS trackside infrastructure for Operation and Maintenance purposes. The functionalities are specified in ETSI TS 103 765-3 [3]. TSCTRL: Reference point between VAS controllers using a non-3GPP access and the FRMCS Service Domain. This reference point is solely intended for VAS controllers. TSCTRL is described in ETSI TS 103 765-4 [4]. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 14 |
68307306d039047e470f288ba4891560 | 103 764 | 5 FRMCS System Architecture components | |
68307306d039047e470f288ba4891560 | 103 764 | 5.1 FRMCS Domain | |
68307306d039047e470f288ba4891560 | 103 764 | 5.1.0 Overview | An FRMCS Domain is an administrative domain which comprises a Transport Domain as described in clause 5.1.1, and an FRMCS Service Domain as described in clause 5.1.2 under the control of an FRMCS Operator. The interface between two FRMCS Domains, namely FSNNI, is defined in clause 4.3.5. |
68307306d039047e470f288ba4891560 | 103 764 | 5.1.1 Transport Domain | The Transport Domain comprises one or more FRMCS Transport Domain(s) and zero or more Non-FRMCS Transport Domain(s). An FRMCS Transport Domain includes a 5G Core Network administrated by an FRMCS Operator, and one or more Radio Access Networks (e.g. terrestrial, satellite, Wi-Fi®) under the control of this 5G Core Network. The Access Networks include at least one 5G NR access operating on RMR harmonized spectrum. A Non-FRMCS Transport Domain does not satisfy the mandatory requirements of an FRMCS Transport Domain (e.g. its 5GC is not administrated by an FRMCS Operator or the transport domain is not a 5G system). The functionalities required for the FRMCS Transport Domain are specified in ETSI TS 103 765-1 [1]. |
68307306d039047e470f288ba4891560 | 103 764 | 5.1.2 FRMCS Service Domain | An FRMCS Service Domain is administrated by an FRMCS Operator. The functionalities required for the FRMCS Service Domain are specified in ETSI TS 103 765-2 [2]. |
68307306d039047e470f288ba4891560 | 103 764 | 5.2 On-board FRMCS | The On-Board FRMCS is installed on-board the trains and enabling communication services and complementary services with the FRMCS Domain(s). The On-Board FRMCS shall comply to ETSI TS 103 765-3 [3]. |
68307306d039047e470f288ba4891560 | 103 764 | 5.3 FRMCS-capable Handheld | The present document does not specify normative requirements applicable to FRMCS-capable Handhelds. |
68307306d039047e470f288ba4891560 | 103 764 | 5.4 FRMCS-capable Object | The present document does not specify normative requirements applicable to FRMCS-capable Objects. |
68307306d039047e470f288ba4891560 | 103 764 | 5.5 FRMCS Trackside Gateway | The FRMCS Trackside Gateway enables communication services and complementary services supported by the FRMCS System to and from authorized trackside applications. The FRMCS Trackside Gateway shall comply to ETSI TS 103 765-4 [4], clauses 4 and 5. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 15 |
68307306d039047e470f288ba4891560 | 103 764 | 5.6 On-Board FRMCS Multipath Function | The On-Board FRMCS Multipath Function enables the use of multiple transport paths over multiple On-Board FRMCS Radio Modules, through the interaction with the FRMCS Infrastructure Multipath Function of the Transport Domain. The On-Board FRMCS Multipath Function is specified in ETSI TS 103 765-1 [1]. |
68307306d039047e470f288ba4891560 | 103 764 | 5.7 FRMCS Infrastructure Multipath Function | The FRMCS Infrastructure Multipath Function enables, through the interaction with the On-Board FRMCS Multipath function, the use of multiple transport paths over multiple On-Board FRMCS Radio Modules of each On-board FRMCS (over one or more Transport Domain(s)). The FRMCS Infrastructure Multipath Function is specified in ETSI TS 103 765-1 [1]. |
68307306d039047e470f288ba4891560 | 103 764 | 5.8 EIRENE System (GSM-R based System) | An EIRENE System is a railway telecommunications system based on the ETSI GSM standard, which complies with all related mandatory requirements as specified in the EIRENE specifications. NOTE: EIRENE Systems are also known as GSM-R Systems. The functionalities required for interacting with an EIRENE System are specified in ETSI TS 103 792 [5] (see FSIWF). |
68307306d039047e470f288ba4891560 | 103 764 | 5.9 Non-EIRENE non-FRMCS System | The present document does not specify normative requirements applicable to interaction of FRMCS with Non-EIRENE non-FRMCS System. |
68307306d039047e470f288ba4891560 | 103 764 | 6 Non-application-specific procedures | |
68307306d039047e470f288ba4891560 | 103 764 | 6.1 Introduction | The following clauses describe the procedures which are non-application specific from a high-level perspective. It is also identified where the detailed specification of the respective procedures in the normative manner can be found. The same procedures are defined, where relevant, in a normative format in ETSI TS 103 765-3 [3] if initiated by an On-Board FRMCS and in ETSI TS 103 765-4 [4] if initiated by an FRMCS Trackside Gateway. NOTE: UIC FRMCS FIS-7970 [i.2] defines the end-to-end application-specific procedures required to achieve the functional requirements of Railway Applications within FRMCS (such as critical voice, ETCS, etc.) and specifies which communication service procedures have to be used and how to use them by any client application using the FRMCS system. |
68307306d039047e470f288ba4891560 | 103 764 | 6.2 FRMCS Start of Operation | |
68307306d039047e470f288ba4891560 | 103 764 | 6.2.0 Overview | The FRMCS Start of Operation (FSOP) procedure is supporting the transition of an On-Board FRMCS operational mode from the train power-up till the moment the On-Board FRMCS is ready to use an FRMCS Domain to serve communication needs (incoming or outgoing) of on-board applications. The procedure describes the expected behavior from On-Board FRMCS and FRMCS Domain upon power up of the train and the steps undertaken to establish connectivity between an On-Board FRMCS and an FRMCS Domain. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 16 |
68307306d039047e470f288ba4891560 | 103 764 | 6.2.1 FRMCS Start of Operation served by the Home FRMCS Domain | Figure 6.2.1-1: FRMCS Start of Operation served by the Home FRMCS Domain procedure Figure 6.2.1-1 depicts the FRMCS Start of Operation for an On-Board FRMCS being served by the Home FRMCS Domain. The following steps are undertaken: 1) The On-Board FRMCS selects at least one On-Board Radio Module to be involved in the procedure (see ETSI TS 103 765-3 [3], clause 7). 2) The On-Board FRMCS executes the On-Board Radio Module registration to the FRMCS Transport Domain procedure (see ETSI TS 103 765-1 [1], clause 6) on the On-Board Radio Modules identified in the previous step. 3) (Optional) If equipped with On-Board Radio Modules associated to Non-FRMCS Transport Domains, the On-Board FRMCS can also execute the On-Board Radio Module registration to the Non-FRMCS Transport Domain (not subject to specification). 4) The On-Board FRMCS selects an On-Board Radio Module to use for FRMCS Multipath discovery. 5) The On-Board FRMCS executes the FRMCS Multipath discovery procedure (see ETSI TS 103 765-1 [1], clause 6). This step assumes that a default transport path has been established on this On-Board Radio Module towards the FRMCS Transport Domain in order to enable FRMCS Multipath control signalling. 6) For each Loose-Coupled Application identified within the list of Startup Applications in the FRMCS Railway On-Board Profile, the On-Board FRMCS executes the MC Client IP assignment procedure (see ETSI TS 103 765-3 [3], clause 7). If the FRMCS Multipath discovery (step 3) is successful, the On-Board FRMCS executes the FRMCS Multipath data path selection procedure (see ETSI TS 103 765-1 [1], clause 6). ETSI ETSI TS 103 764 V1.1.1 (2026-01) 17 7) If the On-Board FRMCS does not have an established PDU session for MC signaling, the On-Board FRMCS executes the Transport path establishment for MC signaling procedure (see ETSI TS 103 765-1 [1], clause 6). 8) The On-Board FRMCS notifies each Tight-Coupled Application identified as Startup Applications in the FRMCS Railway On-Board Profile and which are in the Application_Locally_Bound state of the availability of the FRMCS Transport Domain (see ETSI TS 103 765-3 [3], clause 7). 9) For each Loose-Coupled Application identified as Startup Applications in the FRMCS Railway On-Board Profile: a) The On-Board FRMCS executes the MC user registration procedure (see ETSI TS 103 765-2 [2], clause 6). b) If the application is in the Application_Locally_Bound state, the On-Board FRMCS notifies the availability of the FRMCS Service Domain (see ETSI TS 103 765-3 [3], clause 7). |
68307306d039047e470f288ba4891560 | 103 764 | 6.2.2 FRMCS Start of Operation served by a Foreign FRMCS Domain | The procedure to apply for FRMCS Start of Operation when served by a Foreign FRMCS Domain is similar to the procedure in clause 6.2.1. The main difference resides in the fact that the On-Board Radio Module registration and the MC user registration need to be done with the Foreign FRMCS Domain. The detailed procedure is specified in ETSI TS 103 765-3 [3], clause 7.1.1. |
68307306d039047e470f288ba4891560 | 103 764 | 6.3 FRMCS Close of Operation | The FRMCS Close of Operation (FCOP) procedure describes the expected behavior from On-Board FRMCS and FRMCS Domain upon attempt from an On-Board FRMCS to terminate connectivity to the FRMCS System. Figure 6.3-1: FRMCS Close of Operation procedure ETSI ETSI TS 103 764 V1.1.1 (2026-01) 18 The following steps are undertaken: 1) For each application in Locally-Bound state: a) the On-Board FRMCS notifies the application of the upcoming deregistration within FRMCS (with reason being set to "FCOP") (see ETSI TS 103 765-3 [3], clause 7); and b) the On-Board FRMCS sets up a deregistration timer (see ETSI TS 103 765-3 [3], clause 7) allowing the applications to take actions (e.g. for cleaning up their contexts). At the expiry of the timer, the next step of the procedure is executed. 2) For each Loose-Coupled Application which are in the Locally Bound state, the On-Board FRMCS executes the MCData termination procedure (see ETSI TS 103 765-2 [2], clause 6) for open MC sessions, 3) For each Loose-Coupled Application which are in the Locally Bound state, the On-Board FRMCS executes the MC deregistration procedure (see ETSI TS 103 765-2 [2], clause 6). This includes the SIP deregistration procedure. 4) If an FRMCS Multipath Control Plane connection is active, the On-Board FRMCS executes the FRMCS Multipath Control Plane cleanup procedure (see ETSI TS 103 765-1 [1], clause 6). 5) The On-Board FRMCS executes for each On-Board Radio Module the "deregistration from the FRMCS Transport Domain" procedure (see ETSI TS 103 765-1 [1], clause 6). |
68307306d039047e470f288ba4891560 | 103 764 | 6.4 Domain transitions | |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.1 Inter-FRMCS Domain transition | |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.1.0 General | The Inter-FRMCS Domain transition procedure applies in the case of mobility of an On-Board FRMCS from an FRMCS Domain to another. The present document details the procedure whereby the Transport Stratum transition is followed by the Service Stratum change in short succession. NOTE 1: Other procedures are under consideration that are susceptible to be incorporated in future versions of the present document. Similarly, variants on the number of MC Clients and number of UEs are susceptible to be documented in future versions of the present document. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 19 Figure 6.4.1.0-1: Inter-FRMCS Domain transition procedure The following steps are undertaken: 1) The On-Board FRMCS receives a Network Transition Trigger (NTT) indicating a change to the Target FRMCS Domain. NOTE 2: The nature and contents of the Network Transition Trigger is not specified in the present document. 2) The On-Board FRMCS selects at least one On-Board Radio Module to be involved in the procedure. The On-Board FRMCS performs transport path establishment towards the Target FRMCS Transport Domain using this On-Board Radio Module (see ETSI TS 103 765-1 [1], clause 6). 3) For each Tight-Coupled Application in Locally Bound state: a) The On-Board FRMCS notifies of availability of the FRMCS Transport Domain 2 (see ETSI TS 103 765-3 [3], clause 7). 4) 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 the FRMCS Domain corresponding to the Domain of applicability of the application, the On-Board FRMCS executes the procedure identified in clause 6.4.1.2.1. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 20 b) If the On-Board FRMCS is exiting the FRMCS Domain corresponding to the Domain of applicability of the application, the On-Board FRMCS executes the procedure identified in clause 6.4.1.2.2. 5) 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 executes the procedure identified in clause 6.4.1.1.1. b) If the application has an open session, the On-Board FRMCS executes the procedure identified in clause 6.4.1.1.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 executes the procedure identified in clause 6.4.1.3. |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.1.1 Inter-FRMCS Domain transition: Type I or Type III applications | 6.4.1.1.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 sessions, the following steps are undertaken: 1) the On-Board FRMCS executes the "MC user migration" procedure (see ETSI TS 103 765-2 [2], clause 6) between Serving FRMCS Domain and Target FRMCS Domain; and 2) the On-Board FRMCS notifies the application of the availability of the Target FRMCS Service Domain (see ETSI TS 103 765-3 [3], clause 7). 6.4.1.1.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) the On-Board FRMCS executes the "MC user migration" procedure (see ETSI TS 103 765-2 [2], clause 6) between Serving FRMCS Domain and Target FRMCS Domain; and 2) the On-Board FRMCS notifies the application of the availability of the Target FRMCS Service Domain (see ETSI TS 103 765-3 [3], clause 7). NOTE: Depending on the type of application, the On-Board FRMCS can request the release of the open sessions in the Serving FRMCS Service Domain before the Step 1 (see ETSI TS 103 765-3 [3], clause 7.1.3 for the details). |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.1.2 Inter-FRMCS Domain transition: Type II applications | 6.4.1.2.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 the FRMCS Domain corresponding to the Domain of applicability of the application as identified from the FRMCS Railway On-Board Profile, the following steps are undertaken: 1) the On-Board FRMCS executes the "MC user registration" procedure (both SIP and MC layers) in Target FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6); and 2) the On-Board FRMCS notifies the availability of the Target FRMCS Service Domain (see ETSI TS 103 765-3 [3] ETSI TS 103 765-3 [3], clause 7). ETSI ETSI TS 103 764 V1.1.1 (2026-01) 21 6.4.1.2.2 Inter-FRMCS Domain transition: Type II applications entering an FRMCS Domain which is not in the Domain of applicability For each Loose-Coupled Application which is in Locally Bound state and for which the On-Board FRMCS is entering an 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) The On-Board FRMCS executes the "MCS session release" procedure (both SIP and MC layers) in FRMCS Service Domain 1 (see ETSI TS 103 765-2 [2], clause 6) for open sessions associated to the Loose-Coupled Application. 2) The On-Board FRMCS notifies the application of the closure of its previously opened sessions (see ETSI TS 103 765-3 [3], clause 7). 3) The On-Board FRMCS executes the "MC user deregistration" procedure in Serving FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6). 4) The On-Board FRMCS notifies the application of the unavailability of the FRMCS Service Domain (see ETSI TS 103 765-3 [3], clause 7). |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.1.3 Inter-FRMCS Domain transition: Type IV applications | For each Loose-Coupled Application of Type IV according to the FRMCS Railway On-Board Profile, if the application has at least one open session: 1) the On-Board FRMCS executes "home-routed transport path establishment" procedure on the On-Board Radio Modules (see ETSI TS 103 765-1 [1], clause 6); and 2) the On-Board FRMCS executes "recovery of MCS session" in Serving FRMCS Service Domain (see ETSI TS 103 765-2 [2], clause 6). |
68307306d039047e470f288ba4891560 | 103 764 | 6.4.2 Transition between GSM-R and FRMCS Domain | The present document does not specify the procedures for transitions from GSM-R to an FRMCS Domain and for transitions from FRMCS to a GSM-R System. |
68307306d039047e470f288ba4891560 | 103 764 | 7 Deployment scenarios of FRMCS | |
68307306d039047e470f288ba4891560 | 103 764 | 7.1 Introduction | FRMCS addresses two elements of strategic importance for the future of the railways: end of life of GSM-R and rail transport digitalisation while ensuring rail system interoperability across countries. The FRMCS System Architecture is aimed at deployment in a variety of contexts: • Stand-alone deployment, i.e. deployment of an FRMCS Domain with no external connection to other FRMCS Domains. • Deployment as part of an international network of networks, i.e. deployment of an FRMCS Domain connected to other FRMCS Domains. • Deployment encompassing interworking with GSM-R, deployment of an FRMCS Domain with users interacting with or moving to or from a GSM-R system, under the control of the same operator or not. • Deployment encompassing interconnection with non-EIRENE non-FRMCS networks. NOTE 1: The present document does not specify the requirements associated with non-EIRENE non-FRMCS networks. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 22 NOTE 2: The deployment scenarios are not necessarily disjoint, i.e. an FRMCS Domain that would interact with another FRMCS Domain within the FRMCS System interacting with a GSM-R system would essentially need to meet the requirements of clauses 7.2, 7.3 and 7.4. |
68307306d039047e470f288ba4891560 | 103 764 | 7.2 Stand-alone FRMCS Domain | A stand-alone FRMCS Domain shall: • Comply with the FRMCS Transport Domain stand-alone deployment requirements as specified in ETSI TS 103 765-1 [1], clause 4.2.2. • Comply with the FRMCS Service Domain stand-alone deployment requirements as specified in ETSI TS 103 765-2 [2], clause 5.1. |
68307306d039047e470f288ba4891560 | 103 764 | 7.3 FRMCS Domain in interaction with other FRMCS Domains | An FRMCS Domain deployed to interact with another FRMCS Domain shall: • Comply with the requirements for an FRMCS Domain stand-alone deployment as specified in clause 7.2 of the present document. • Comply with the FRMCS Transport Domain network-to-network deployment requirements as specified in ETSI TS 103 765-1 [1], clause 4.2.3. • Comply with the FRMCS Service Domain network-to-network deployment requirements as specified in ETSI TS 103 765-2 [2], clause 5.2. • Implement the FSNNI reference point. |
68307306d039047e470f288ba4891560 | 103 764 | 7.4 FRMCS Domain in interaction with a GSM-R system | An FRMCS Domain deployed to interact with a GSM-R system shall: • Comply with the requirements for an FRMCS Domain stand-alone deployment as specified in clause 7.2 of the present document. • Comply with the FRMCS Service Domain network-to-network deployment requirements as specified in ETSI TS 103 765-2 [2], clause 5.3. • Implement the FSIWF reference point (clause 4.3.5) and the IWF function as specified in ETSI TS 103 792 [5]. 7.5 FRMCS Domain in interaction with a non-EIRENE non-FRMCS network The present document does not specify the interactions between an FRMCS Domain and a non-EIRENE non-FRMCS network as a deployment model. |
68307306d039047e470f288ba4891560 | 103 764 | 8 IP addresses and routing | |
68307306d039047e470f288ba4891560 | 103 764 | 8.0 Generalities | For applications enablement, the FRMCS system provides communication services between endpoints which are connected to a diverse set of networks. For example, an On-Board FRMCS enables the connectivity of applications residing on the train network which usually operates on the basis of a private IP range which can be the same, differ or overlap with the IP range of the train network of another train. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 23 Likewise, when using the Host-to-Host addressing scheme, an FRMCS Trackside Gateway enables the connectivity of applications which can reside on a subnetwork under complete control of the operator of the FRMCS Trackside Gateway but it also enables the connectivity of applications which can reside on a network which operates on a private IP range and for which the routing from or towards the FRMCS Trackside Gateway subnetwork would require some form of NAT. Finally, when using the Host-to-Network addressing scheme, an FRMCS Trackside Gateway also enables the connectivity to a set of subnetworks (one per H2N Network endpoint) for which the routing from or towards the FRMCS Trackside Gateway subnetwork would require some form of NAT. Figure 8.0-1 depicts these variants of situations. Figure 8.0-1: Variants of IP address ranges of the train networks and of the trackside networks In Figure 8.0-1: • OB_PRV_IP1 is a private IP range for Train 1. • OB_PRV_IP12 is a private IP range for Train 2, overlapping with OB_PRV_IP1. • OB_PRV_IP3 is a private IP range for Train 3, disjoint from OB_PRV_IP1. • TS_FTG_IP is an IP range under control (from an IP routing perspective) of the operator of the FRMCS Trackside Gateway. • TS_EXT_IP is an IP range not under complete control (from an IP routing perspective) of the operator of the FRMCS Trackside Gateway but for which IP routing from or towards the FRMCS Trackside Gateway subnetwork can be established, possibly through some interim NAT. • TS_H2N_IP is an IP range associated to a H2N Network Endpoint. The Trackside Network IP range (TS_NET_IP) can be any of TS_FTG_IP, TS_EXT_IP, and TS_H2N_IP defined above. This concept is used in the subsequent clauses. NOTE: Routing is in the present document assumed to be solely based on IP. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 24 8.1 IP address ranges - Loose-Coupled Applications, without FRMCS Multipath Figure 8.1-1: Overview of FRMCS IP ranges for Loose-Coupled Applications without FRMCS Multipath The IP address ranges for Loose-Coupled Applications without FRMCS Multipath are depicted in Figure 8.1-1. Several different IP address ranges are used as depicted in Figure 8.1-1: • On-Board Network Private IP (OB_PRV_IP) range: the local private IP Address range within the On-Board network: - It is used for IP exchanges on OBAPP between On-Board Applications and the On-Board FRMCS. - It is also used for data transfer between an On-Board Application and a Trackside Application but NATing will need to occur in the FRMCS Trackside Gateway. - OB_PRV_IP can be the same or overlap for different On-Board FRMCS. This can have an impact on the Trackside Application Network NAT Function. • FRMCS Service Domain Public IP (SD_PUB_IP) range: the public IP address range (within the address realm of the FRMCS Service Domain) used by the On-Board FRMCS and the FRMCS Trackside Gateway to connect to the FRMCS Service Domain. • FRMCS Transport Domain Public IP (TD_PUB_IP) range: the public IP address range (within the address realm of the FRMCS Transport Domain) used by the On-Board FRMCS and the FRMCS Trackside Gateway to connect to the FRMCS Transport Domain. • Trackside Application Network IP (TS_NET_IP) range: the local IP Address range within the trackside network: - It is used for IP exchanges on TSAPP between Trackside Applications and the FRMCS Trackside Gateway. - It is also used for the data transfer between a Trackside Application and an On-Board Application: For data flowing from an On-Board Application to a Trackside Application, the source IP address in the OB_PRV_IP range is NATed into TS_NET_IP. For data flowing from a Trackside Application to an On-Board Application, the destination IP address in TS_NET_IP is reverse NATed into the OB_PRV_IP range. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 25 In addition, NAT may occur at the service layer. In this case, the following additional IP ranges may be needed: • On-Board Service NATed IP (OB_NAT_IP) range: the IP range used by the on-board MCData Clients to connect to the FRMCS Service server and NATed by the On-Board FRMCS to the FRMCS Service Domain Public IP address range. • Trackside Service NATed IP (TS_NAT_IP) range: the IP range used by the trackside MCData Clients to connect to the FRMCS Service server and NATed by the FRMCS Trackside Gateway to the FRMCS Service Domain Public IP address range. 8.2 IP address ranges - Tight-Coupled Applications, without FRMCS Multipath Figure 8.2-1: Overview of FRMCS IP ranges for Tight-Coupled Applications without FRMCS Multipath The IP address ranges for Tight-Coupled Applications without FRMCS Multipath are depicted in Figure 8.2-1. Several different IP address ranges are used as depicted in Figure 8.2-1: • On-Board Network Private IP (OB_PRV_IP) range: the local private IP Address range within the On-Board network: - It is used for IP exchanges on OBAPP between On-Board Applications and the On-Board FRMCS. - It is NATed within the On-Board FRMCS into SD_PUB_IP range. - OB_PRV_IP can be the same or overlap for different On-Board FRMCS. • FRMCS Service Domain Public IP (SD_PUB_IP) range: the public IP address range (within the address realm of the FRMCS Service Domain) used by the On-Board FRMCS and the FRMCS Trackside Gateway to connect to the FRMCS Service Domain. • FRMCS Transport Domain Public IP (TD_PUB_IP) range: the public IP address range (within the address realm of the FRMCS Transport Domain) used by the On-Board FRMCS and the FRMCS Trackside Gateway to connect to the FRMCS Transport Domain. • Trackside Application Network IP (TS_NET_IP) range: the IP Address range within the trackside network: - It is used for IP exchanges on TSAPP between Trackside Applications and the FRMCS Trackside Gateway. - If this IP address range is not within SD_PUB_IP, it is NATed into the SD_PUB_IP range. NOTE: Trackside Application Network IP is not applicable to TSCTRL. ETSI ETSI TS 103 764 V1.1.1 (2026-01) 26 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 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 1 Scope | The present document defines the Service Stratum for the Future Railway Mobile Communications System (FRMCS). In general, the FRMCS Service Stratum provides communication service and corresponding complementary service resulting from 3GPP Mission Critical Services (MCX) and 3GPP multimedia system. While FRMCS is defined in various FRMCS ETSI Technical Specifications, the present document determines necessary components of the FRMCS Service Stratum, encompassing: • Building blocks and corresponding reference points of 3GPP MCX/IMS. • Reference points between MC systems/IMS for interconnection and unilateral use by MC organizations (MC migration). • Reference points between the MC system/IMS and external systems. • QoS and priority management. • User identification, authentication and authorization for the use of the FRMCS service stratum. • Communication security aspects. • Complementary and auxiliary service, e.g. alternative user addressing schemes. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 2 References | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 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 123 228 (V18.9.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 18.9.0 Release 18)". [2] 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)". [3] ETSI TS 124 482 (V18.0.1): "LTE; Mission Critical Services (MCS) identity management; Protocol specification (3GPP TS 24.482 version 18.0.1 Release 18)". [4] ETSI TS 124 484 (V18.7.0): "LTE; Mission Critical Services (MCS) configuration management; Protocol specification (3GPP TS 24.484 version 18.7.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 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)". [7] ETSI TS 124 379 (V18.10.0): "LTE; Mission Critical Push To Talk (MCPTT) call control; Protocol specification (3GPP TS 24.379 version 18.10.0 Release 18)". ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 8 [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] ETSI TS 124 282 (V18.10.0): "LTE; Mission Critical Data (MCData) signalling control; Protocol specification (3GPP TS 24.282 version 18.10.0 Release 18)". [10] ETSI TS 124 582 (V18.2.0): "LTE; Mission Critical Data (MCData) media plane control; Protocol specification (3GPP TS 24.582 version 18.2.0 Release 18)". [11] ETSI TS 123 281 (V18.9.0): "LTE; Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2 (3GPP TS 23.281 version 18.9.0 Release 18). [12] ETSI TS 123 002 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 18.0.0 Release 18)". [13] 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)". [14] ETSI TS 133 203 (V18.1.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Access security for IP-based services (3GPP TS 33.203 version 18.1.0 Release 18)". [15] ETSI TS 103 765-1: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 1: Transport Stratum". [16] ETSI TS 103 792: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Interworking with GSM-R". [17] UIC FIS-7970: "Future Railway Mobile Communication System; Functional Interface Specification", Version 2.1.0. [18] ETSI TS 123 283 (V18.2.0): "LTE; Mission Critical Communication Interworking with Land Mobile Radio Systems (3GPP TS 23.283 version 18.2.0 Release 18)". [19] ETSI TS 123 203 (V18.0.0): "Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control architecture (3GPP TS 23.203 version 18.0.0 Release 18)". [20] ETSI TS 123 503 (V18.9.0): "5G; Policy and charging control framework for the 5G System (5GS); Stage 2 (3GPP TS 23.503 version 18.9.0 Release 18)". |
4512d63c6de502e416921955aa495103 | 103 765-2 | 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] ETSI TS 103 764: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); System Architecture". ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 9 [i.3] ETSI TS 103 765-3: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 3: Train On-Board functions and interfaces". [i.4] ETSI TS 103 765-4: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Building Blocks and Functions; Part 4: Trackside functions and interfaces". |
4512d63c6de502e416921955aa495103 | 103 765-2 | 3 Definition of terms, symbols and abbreviations | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.1] and the following apply: FRMCS SIP Core: Set of entities either: • compliant with ETSI TS 123 228 [1] (3GPP IP multimedia core network subsystem); • or supporting the reference points identified in ETSI TS 123 280 [2], clause 7.5.3 compliant with the reference points defined in ETSI TS 123 002 [12]. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 3.2 Symbols | Void. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3G Partnership Project 5GC 5G Core AKA Authentication and Key Agreement API Application Programming Interface APP Application AS Application Server ATO Automatic Train Operation ATP Automatic Train Protection CSC Common Service Core DNS Domain Name Service FIS Functional Requirement Specification (UIC) FQDN Fully Qualified Domain Name FRMCS Future Railway Mobile Communication System FROP FRMCS On-Board Profile FRS Functional Requirement Specification (UIC) FSIWF FRMCS InterWorking Function FSNNI FRMCS Network-to-Network Interface FSONI FRMCS Other Network Interface GRE Generic Routing Encapsulation GSM-R Global System for Mobile communications - Railways H2H Host-to-Host H2N Host-to-Network HTTP Hyper Text Transfer Protocol IBCF Interconnect Border Control Function IdM Identity Management IMS IP Multimedia Subsystem IP Internet Protocol IPcon IP connectivity IWF InterWorking Function LC Loose-Coupled (Application) ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 10 MC Mission-Critical MCPTT Mission-Critical Push-To-Talk MCX Mission Critical Service MFCN Mobile Fixed Communication Network NAT Network Address Translation NDS Network Domain Security NEF Network Exposure Function NNI Network-to-Network Interface OB On-Board FRMCS ONI Other Network Interface NOTE: ONI only gets used as part of FSoni, which is in the list already. PCF Policy Control Function PLMN Public Land Mobile Network QoS Quality of Service SAP Service Access Point SCTP Stream Control Transmission Protocol SDS (MCData) Short Data Service SIP Session Initiation Protocol SLC Super-Loose Coupled SRS System Requirement Specification (UIC) TAP Transport Access Point TCMS Train Control and Management System TLS Transport Layer Security TrGW Transition GateWay TS TrackSide UDP User Datagram Protocol UE User Equipment URI Uniform Resource Identifier |
4512d63c6de502e416921955aa495103 | 103 765-2 | 4 Architecture principles | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 4.1 General | Clause 4 describes system architecture of the Service Stratum to support communication services and complementary services for FRMCS. The system architecture is applicable for FRMCS using 3GPP Mission Critical Services (MCX) and the related MCX architecture defined in ETSI TS 123 280 [2], ETSI TS 123 379 [6], ETSI TS 123 281 [11] and ETSI TS 123 282 [8] from 3GPP Release 18 onwards. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 4.2 Architecture | The system architecture of the FRMCS service stratum is illustrated in Figure 4.2-1. The FRMCS service stratum may consist of different domains, independent of the geographical allocation, and follows the Service Client - Server approach (Figure 4.2-1) applicable in on-network operation mode. The necessary interconnection between the different FRMCS service domains enables the service stratum users to communicate between them using SAP interconnection via FSNNI reference point. For communication with legacy railway communication systems, i.e. GSM-R, the FRMCS Service Stratum enables the necessary interworking using SAP Legacy Systems via FSIWF reference point (Figure 4.2-1) for this purpose. For the communication with external systems, e.g. MFCN, the FRMCS Service Stratum enables the necessary interconnection/interworking using the SAP External Systems via FSONI reference point (Figure 4.2-1). For the transmission of the communications between Service Client and Service Server encompassing signalling and user data, the FRMCS service stratum (Figure 4.2-1) uses unicast transmission paths of the FRMCS transport stratum using the TAPs in accordance with ETSI TS 103 765-1 [15]. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 11 The components of the various SAPs are described in more detail in the following clauses. Figure 4.2-1: FRMCS Service Stratum - system architecture |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5 FRMCS Service Stratum constituents | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.1 Stand-alone FRMCS Service Domain | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.1.1 Functional entities | The signalling control functions of the FRMCS Service Stratum shall comply with ETSI TS 123 280 [2]. The FRMCS Service Domain shall support the following functional server entities as described in ETSI TS 123 280 [2], clause 7.4.2.2: • Configuration management server. • Identity management server. • Key management server. • Location management server. • Functional alias management server. The FRMCS Service Domain shall support the following functional server entities for the MCPTT service (limited to MCPTT ad hoc group call and emergency alert realized through MCPTT ad hoc group call): • MCPTT server as described in ETSI TS 123 379 [6], clause 7.4.2.3.2. • Floor control server as described in ETSI TS 123 379 [6], clause 7.4.2.3.4. • Media distribution function as described in ETSI TS 123 379 [6], clause 7.4.2.3.5. • MCPTT user database as described in ETSI TS 123 379 [6], clause 7.4.2.3.7. FRMCS Service Server(s) FRMCS Service Client (s) Legacy Service Domain GSM-R Other FRMCS Service Domains Data Network 5GS Transport Stratum Scope of ETSI TS 103 765-2 c c Application Interconnection FSNNI Interworking FS ONI Legacy Interworking FSIWF Application Interconnection OBAPP TS APP TAP TAP FRMCS Service Domain FRMCS Service Domain Service Function(s) Non -FRMCS & Non -EIRENE Service Domains ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 12 The FRMCS Service Domain shall support the following functional server entities for the MCData service (limited to MCData IPCon and MCData SDS): • MCData server as described in ETSI TS 123 282 [8], clause 6.4.3.1.2. • MCData user database as described in ETSI TS 123 282 [8], clause 6.4.3.1.3. • MCData notification server as described in ETSI TS 123 282 [8], clause 6.4.3.5. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.1.2 Reference points | The FRMCS Service Domain shall support the following reference points between Service Client and Service Server: • reference points for IMS/SIP and HTTP signalling as listed in Table 5.1.2-1; • reference points for Common service core as listed in Table 5.1.2-2; • reference points for MCPTT as listed in Table 5.1.2-3; and • reference points for MCData (SDS, IPcon) as listed in Table 5.1.2-4. Table 5.1.2-1: Reference Points of a stand-alone FRMCS Service Domain for IMS/SIP and HTTP Signalling MCx Reference Point Endpoints Underlying MCx signalling/control plane ETSI Reference SIP-1 SIP Signalling user agent - FRMCS SIP Core Gm ETSI TS 123 002 [12] SIP-2 FRMCS SIP Core - Application Server (AS) ISC and Ma ETSI TS 123 002 [12] HTTP-1 HTTP client - HTTP proxy Ut ETSI TS 123 002 [12] HTTP-2 HTTP proxy - HTTP server HTTP ETSI TS 123 280 [2] AAA-1 SIP database - FRMCS SIP core Cx ETSI TS 123 002 [12] AAA-2 FRMCS SIP core - Diameter proxy Cx ETSI TS 123 002 [12] Table 5.1.2-2: Reference Points of a stand-alone FRMCS Service Domain for Common Service Core MCx Reference Point Endpoints Underlying MCx signalling/control plane ETSI Reference CSC-1 Identity management Client - Identity management Server HTTPS (TLS) ETSI TS 133 180 [5] CSC-4 Configuration management Client - Configuration management Server HTTP-1 and HTTP-2 SIP-1 and SIP-2 ETSI TS 123 280 [2] CSC-5 Configuration management Server - MC service server HTTP-1 and HTTP-2, SIP-2 ETSI TS 123 280 [2] CSC-8 Key management Client - Key management Server HTTP-1 and HTTP-2 ETSI TS 123 280 [2] CSC-9 Key management Server - MC service server HTTP-1 and HTTP-2 ETSI TS 123 280 [2] CSC-10 Key management Server - Group management Server HTTP-1, HTTP-2 (and may use HTTP-3) ETSI TS 123 280 [2] CSC-13 Configuration management Server - MC service user database ETSI TS 123 280 [2] CSC-14 Location management Client - Location management Server SIP-1 and SIP-2, HTTP-1 and HTTP-2 ETSI TS 123 280 [2] CSC-15 Location management Server - MC service server SIP-1 and SIP-2, HTTP-1 and HTTP-2 ETSI TS 123 280 [2] ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 13 Table 5.1.2-3: Reference Points of a stand-alone FRMCS Service Domain for MCPTT MCx Reference Point Endpoints Underlying MCx signalling/control plane ETSI Reference MCPTT-1 MCPTT Server - MCPTT Client (via SIP/IMS Core) SIP-1, SIP-2, HTTP-1, HTTP-2 ETSI TS 123 379 [6] MCPTT-2 MCPTT Server - MCPTT User database AAA-1 ETSI TS 123 379 [6] MCPTT-4 Floor control server - Floor participant SGi ETSI TS 123 379 [6] ETSI TS 123 002 [12] MCPTT-5 MCPTT Server - 5GC N5/Rx (via PCF for trusted domain) N33 (via NEF for un-trusted domain) ETSI TS 123 379 [6] ETSI TS 123 203 [19] ETSI TS 123 503 [20] MCPTT-7 Media distribution function - Media mixer SGi ETSI TS 123 379 [6] ETSI TS 123 002 [12] Table 5.1.2-4: Reference Points of a stand-alone FRMCS Service Domain for MCData (SDS and IPcon) MCx Reference Point Endpoints Underlying MCx signalling/control plane ETSI Reference MCData-2 MCData server - MCData user database SCTP based Diameter management application protocol ETSI TS 123 282 [8] ETSI TS 123 283 [18] MCData-5 MCData server - 5GC N5/Rx (via PCF for trusted domain) N33 (via NEF for un-trusted domain) ETSI TS 123 282 [8] ETSI TS 123 203 [19] ETSI TS 123 503 [20] MCData-10 Message notification client - MCData notification server ETSI TS 123 282 [8] MCData-SDS-1 MCData Server - MCData Client SIP-1 SIP-2 ETSI TS 123 282 [8] MCData-SDS-2 SDS distribution function - SDS function (unicast) SGi ETSI TS 123 282 [8] ETSI TS 123 002 [12] MCData-IPcon-1 MCData Server - MCData Client SIP-1 SIP-2 ETSI TS 123 282 [8] MCData-IPcon-2 U-IPcon distribution function - U-IPcon function (unicast) ETSI TS 123 282 [8] NOTE: Interface AAA-1 may not be exposed as described in ETSI TS 123 280 [2], clause 9.2.2.2, note 1. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.1.3 Procedures | The FRMCS Service Domain shall support the functionalities required for the following procedures of clause 6: • MC User registration in Home FRMCS Service Domain. • MC User deregistration in Home FRMCS Service Domain. • FRMCS nominal operation procedures. 5.2 FRMCS Service Domain in interaction with other FRMCS Domains |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.2.1 Functional entities | To provide the necessary signalling and voice codec adaptation for interworking with external networks, the FRMCS Service Domain shall support the following functions of the IP Multimedia Core Network Subsystem defined in ETSI TS 123 228 [1]: • IBCF and TrGW for interworking with public wireless systems, such as PLMN or other FRMCS service domains as described in ETSI TS 124 229 [13]. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 14 The FRMCS Service Domain shall support the following functional server entities for the MCPTT service: • MC gateway server as described in ETSI TS 123 379 [6], clause 7.4.2.3.8. The FRMCS Service Domain shall support the following functional server entities for the MCData service: • MC gateway server as described in ETSI TS 123 282 [8], clause 6.4.3.1.5. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.2.2 Reference points | This clause specifies the reference points between two FRMCS service domains. FSNNI provides the following functionalities to comply with SAP Interconnection: • Support of inter-FRMCS service domain application and control plane signalling (SIP and HTTP signalling). • Communication services between MC Service Users served by different FRMCS Service Domains. • Topology hiding support. • Inter-FRMCS service domain out of band sharing (certificate exchange between FRMCS service domains). • Inter-FRMCS service domain interconnection security. NOTE: Out of band sharing mechanism is not specified in the present document and subject to agreement between FRMCS operators. The FRMCS Service Domain shall support the following reference points which constitute FSNNI at the Service Stratum for the MC application plane and MC signalling control plane: • MCX-1 as specified in ETSI TS 123 280 [2], clause 7.5.2.19. • CSC-17 as specified in ETSI TS 123 280 [2], clause 7.5.2.17. • CSC-20 as specified in ETSI TS 123 280 [2], clause 7.5.2.21. • CSC-21 as specified in ETSI TS 123 280 [2], clause 7.5.2.22. • CSC-22 as specified in ETSI TS 123 280 [2], clause 7.5.2.23. • CSC-23 as specified in ETSI TS 123 280 [2], clause 7.5.2.24. • CSC-24 as specified in ETSI TS 123 280 [2], clause 7.5.2.25. • SIP-3 as specified in ETSI TS 123 280 [2], clause 7.5.3.4. • HTTP-3 as specified in ETSI TS 123 280 [2], clause 7.5.3.7. • AAA-2 as specified in ETSI TS 123 280 [2], clause 7.5.3.9. The FRMCS Service Domain shall support the following reference points which constitute FSNNI at the Service Stratum for the MCPTT service: • MCPTT-3 as specified in ETSI TS 123 379 [6], clause 7.5.2.4. • MCPTT-10 as specified in ETSI TS 123 379 [6], clause 7.5.2.13. The FRMCS Service Domain shall support the following reference points which constitute FSNNI at the Service Stratum for the MCData service: • MCData-3 as specified in ETSI TS 123 282 [8], clause 6.4.4.1.3. • MCData-9 as specified in ETSI TS 123 282 [8], clause 6.4.4.1.8. • MCData-10 as specified in ETSI TS 123 282 [8], clause 6.4.4.1.9. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 15 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.2.3 Procedures | The FRMCS Service Domain shall support the functionalities required for the following procedures of clause 6: • MC User registration in Foreign FRMCS Service Domain. • MC User deregistration in Foreign FRMCS Service Domain. • Inter FRMCS service domain transition. • Communications encompassing multiple FRMCS Service Domains. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.3 FRMCS Domain in interaction with a GSM-R system | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.3.1 Functional entities | No additional functional entities are required for a FRMCS Service Domain in interaction with a GSM-R system. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.3.2 Reference points | The FRMCS Service Domain shall support the following reference points as specified ETSI TS 103 792 [16], clause 5.2: • IWF-1. • IWF-2. • IWF-3. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.3.3 Procedures | No additional procedures are required for a FRMCS Service Domain in interaction with a GSM-R system. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 5.4 FRMCS interaction with non-FRMCS non-EIRENE System | The present document does not specify normative requirements applicable to interaction of FRMCS with non-FRMCS non-EIRENE System. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6 FRMCS service procedures | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.1 MC User registration | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.1.1 MC User registration in Home FRMCS Service Domain | This clause describes the MC User registration procedure in Home FRMCS Service Domain. The values passed into this procedure by its caller entity (e.g. On-Board FRMCS in ETSI TS 103 765-3 [i.3] or FRMCS Trackside Gateway in ETSI TS 103 765-4 [i.4]) shall be used by the IdM Client and individual MC Service clients involved in the procedures referenced below. These values are MC User ID and its associated password, scope and IMS/SIP credential. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 16 The MC User registration procedure in Home FRMCS Service Domain is constituted of the following steps: Step 1 - Bootstrap of MC default/initial configurations The MC procedures for the configuration of MCS UE initial configuration Management Object and the default MCS user profile configuration Management Object(s) shall conform to ETSI TS 124 484 [4], clause 4.2.2 for the online configuration case. NOTE: The URIs of Configuration Management Server and the Identity Management Server are retrieved from FROP. Step 2 - MC User authentication and MC token acquiring The IdM Client procedures for user authentication in primary MC system shall conform to ETSI TS 124 482 [3], clause 6.2.1. The IdM Server procedures for user authentication in primary MC system shall conform to ETSI TS 124 482 [3], clause 6.3.1. Step 3 - Configuration of MC service user profile and MC service group 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 - SIP registration The signalling user agent shall establish a secure connection to the SIP core for the purpose of SIP authentication and registration and subsequently perform the SIP level registration as per ETSI TS 133 180 [5], clause 5.1.1, step B-1. Step 5 - MC Service User authorization per MC Service in the scope All MC clients scoped for the authenticated MC User ID in step 2 shall perform the MC service authorization sending the access token to the MC server using SIP PUBLISH message as per ETSI TS 133 180 [5], clause 5.1.3.2.3. SIP Digest shall be used as security mechanism with for MC clients of tight coupled and loose coupled applications. SIP Digest shall be used for FRMCS SIP Core access authentication over non-3GPP access including NDS/IP as per Annex N (SIP Digest without TLS) and Annex O (SIP Digest with TLS) of ETSI TS 133 203 [14]. IMS AKA as specified in ETSI TS 133 203 [14] should be limited to FRMCS Handhelds. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.1.2 MC User registration in Foreign FRMCS Service Domain | This clause describes the MC User registration in Foreign FRMCS Service Domain. The values passed into this procedure by its caller entity (i.e. On-Board FRMCS in ETSI TS 103 765-3 [i.3]) shall be used by the IdM Client and individual MC Service clients involved in the procedures referenced below. These values are MC User ID and its associated password, scope and the IMS/SIP credentials in the Home FRMCS Service Domain and in the Foreign FRMCS Service Domain. The MC User registration procedure in Foreign FRMCS Service Domain for a MC user associated to interoperable applications is constituted of the following steps: Step 1 - MC User authentication in primary MC system and selection of user profile to permit migration to the selected partner MC system If this has not been executed previously, the steps 1 to 3 in clause 6.1.1 shall be performed. In this step, the MC client obtains the MC service user profile from the primary MC system to permit migration to the selected partner MC system (each user profile received from the primary MC system contains a list of partner MC systems to which migration is permitted using that user profile, together with their access information). NOTE 1: The "selected partner MC system" is the one which is associated to the Foreign FRMCS Service Domain. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 17 Step 2 - The MC User migration procedure as defined in clause 6.4.1 shall be performed on the authenticated MC User in Step 1 MC users associated with non-interoperable applications of Type IV cannot be permitted to migrate to the partner MC system. MC user authentication and corresponding MC service user authorization for each MC service associated with non-interoperable applications shall be as described in clause 6.1.1. NOTE 2: The transport path to the home FRMCS Service Domain is as described in ETSI TS 103 765-1 [15]. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2 FRMCS nominal operation procedures | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1 MCPTT voice services | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.1 General | The FRMCS Service Domain shall support ETSI TS 123 379 [6], clause 10.19.3.1 for MCPTT ad hoc group call procedures using "on-demand" Session. The FRMCS Service Domain shall support for the ad hoc group call criteria the comma-separated list as specified in UIC FRMCS FIS-7970 [17], clause 4.3.6.10.3 with values as specified in UIC FRMCS FIS-7970 [17], clause 4.3.6.10.4, Table 2 and clause 4.4.6.1.4, Table 4. NOTE: The present document does not specify any normative requirements related to MCPTT private call, in particular related to ETSI TS 103 792 [16], clause 8. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.2 Call setup | The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 17.3.2.1 and 17.4.2 for MCPTT ad hoc group call setup. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.3 Call rejoin, modify and determine participants | The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 17.3.4.1 and 17.4.4.1 for MCPTT ad hoc group call rejoin. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 17.3.5.1 and 17.4.5.1 for MCPTT ad hoc group call modification of the participant list or criteria for the participant list. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 17.3.6 and 17.4.6 for MCPTT ad hoc group call participants determination. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.4 Location service | The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 13.2.2 for MCPTT ad hoc group call location reporting configuration. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 13.2.3 for MCPTT ad hoc group call location information request. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 13.2.4 for MCPTT ad hoc group call location information report. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.5 Emergency alert | The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 6.3.3.1.13.8 and 6.3.3.1.13.9 for initiating and cancelling an MCPTT ad hoc group emergency alert. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 6.3.3.1.13.10 for determining MCPTT users that are authorized for receiving MCPTT ad hoc group emergency alert participant information. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 18 The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 6.3.3.1.23 to populate mcptt-info MIME bodies for ad hoc group emergency alert. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 6.3.3.1.24 for generating a SIP MESSAGE request to containing the participant lists of an MCPTT ad hoc group emergency alert. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clause 6.3.3.1.25 to validate ad hoc group priority request parameters. The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 12.1A2 and 12.1A3 for MCPTT ad hoc group emergency alert. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.1.6 Call release | The FRMCS Service Domain shall support ETSI TS 124 379 [7], clauses 17.3.3.1 and 17.4.3 for MCPTT ad hoc group call release. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2 MCData IP Connectivity | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.1 General | MCData IPCon is used to provide transparent IP connection between FRMCS Service Clients acting as MCData IPcon clients as per ETSI TS 124 282 [9] and ETSI TS 124 582 [10]. The transparent IP data connection is achieved by using an GRE over UDP Tunnelling of the application layer IP flow. Two different connectivity models are defined within FRMCS: • Host-to-Host Connectivity Model (H2H), providing a transparent IP connection between two host entities each with a defined IP address. • Host-to-Network Connectivity Model (H2N), providing a transparent IP connection between a single host entity (defined via an IP address) and an IP network where multiple hosts can be connected. Figure 6.2.2.1-1 depicts the service layer model for both Host-to-Host and Host-to-Network connectivity. NOTE: The relevant OBAPP/TSAPP API services (open session, incoming sessing, etc.) depend on whether the On-Board-FRMCS/FRMCS-Trackside-Gateway is acting as originator or terminator of the end-to-end (reference ETSI TS 103 765-3 [i.3] for On-Board FRMCS and to ETSI TS 103 765-4 [i.4] for FRMCS Trackside Gateway. Figure 6.2.2.1-1: Service Layer model of Host-to-Host (H2H) and Host-to-Network (H2N) connectivity ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 19 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.2 Basic mandatory procedures | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.2.1 MCData IPcon session establishment | The originating MCData client procedures for MCData IPcon session establishment shall conform to ETSI TS 124 282 [9], clause 20.2.1. The terminating MCData client procedures for MCData IPcon session establishment shall conform to ETSI TS 124 282 [9], clause 20.2.2. The FRMCS Service Domain shall support ETSI TS 124 282 [9], clauses 20.3 and 20.4 for MCData IPcon session establishment. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.2.2 MCData IPcon media plane | The originating MCData client procedures for MCData IPcon media plane shall conform to ETSI TS 124 582 [10], clause 13.1.2. The terminating MCData client procedures for MCData IPcon media plane shall conform to ETSI TS 124 582 [10] clause 13.1.3. The FRMCS Service Domain shall support ETSI TS 124 582 [10], clauses 13.2 and 13.3 for MCData IPcon media plane. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.2.3 MCData IPcon session release | The originating MCData client procedures for MCData IPcon session release shall conform to ETSI TS 124 282 [9], clause 13.2.2.2.2.1. The terminating MCData client procedures for MCData IPcon session release shall conform to ETSI TS 124 282 [9], clause 13.2.2.2.2.2. The FRMCS Service Domain shall support ETSI TS 124 282 [9], clauses 13.2.2.2.3, 13.2.2.2.4.2, 13.2.2.2.4.3 and 13.2.2.2.4.4 for MCData IPcon session release. If the caller entity indicates that the user has ended the call, the RELEASE_CAUSE in the SIP Reason header field of SIP BYE shall be set to 1 ("user ends call") as defined in ETSI TS 124 229 [13], clause 5.1.5 and Table 7.2A.18.11-2) on each hop from originating MCData client up to the terminating MCData client. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.3 MCData IPcon session establishment | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.3.1 On-Board-FRMCS-originated MCData IPcon session establishment | The originating MCData client shall send a MCData IPcon session request to the MCData server (see clause 6.2.2.2.1): • If the MCData client is configured by the On-Board FRMCS to use the Functional Alias as the recipient identifier, the originating MCData Client shall set the <call-to-functional-alias-ind> element in the SIP INVITE to "true" as per ETSI TS 124 282 [9], clause 20.2.1 step 8, and shall insert the URI of the functional alias, which is passed to this procedure by the On-Board FRMCS, as a part of <resource-lists> element as per ETSI TS 124 282 [9], clause 20.2.1 step 7. • The originating MCData client shall fill the <user-requested-priority> element in the SIP INVITE as per ETSI TS 124 282 [9], clause 20.2.1 step 8, if a value is passed into this procedure by the On-Board FRMCS. NOTE 1: The value of <user-requested-priority> is associated to the Communication Session Category as specified in clause 6.2.5 of the present document. The following SIP response codes with the FRMCS-specific warning texts shall be supported by the MCData clients and the FRMCS Service Domain: • If the terminating application is not locally bound, the SIP response shall be set to 480 with warning text "FRMCS-Terminating application is not locally bound". ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 20 • If the terminating application is not allowed by profile to receive an incoming session, the SIP response shall be set to 403 with warning text "FRMCS-Terminating application is not allowed to receive an incoming session". • If the incoming session timer (i.e. T_INCOMING_SESSION) is expired at the terminating FRMCS entity, the SIP response shall be set to 408 with warning text "FRMCS-Terminating application did not respond in time to session invitation". • If the terminating application entity declined the request, the SIP response shall be set to 603 with warning text "FRMCS-Terminating application declined the request". The IP management during the establishment of On-Board originated sessions of type Host-to-Host and Host-to-Network is described in clauses 6.2.2.4.2 and 6.2.2.4.3 respectively. The <application-data> element within the AnyExt extension field of MCData IPcon session request, sent on each hop from originating MCData client up to the terminating MCData client, shall be set as specified in clauses 6.2.2.4.2 and 6.2.2.4.3, respectively for Host-to-Host and Host-to-Network addressing schemes. NOTE 2: The detailed format of <application-data> is not specified in the present document. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.3.2 FRMCS-Trackside-originated MCData IPcon session establishment | The originating MCData client shall send a MCData IPcon session request to the MCData server (see clause 6.2.2.2.1): • If the MCData client is configured by the FRMCS Trackside Gateway to use the Functional Alias as the recipient identifier, the originating MCData Client shall set the <call-to-functional-alias-ind> element in the SIP INVITE to "true" as per ETSI TS 124 282 [9], clause 20.2.1 step 8, and shall insert the URI of the functional alias, which is passed to this procedure by the FRMCS Trackside Gateway, as a part of <resource-lists> element as per ETSI TS 124 282 [9], clause 20.2.1 step. • The originating MCData client shall fill the <user-requested-priority> element in the SIP INVITE as per ETSI TS 124 282 [9], clause 20.2.1 step 8, if a value is passed into this procedure by the FRMCS Trackside Gateway. NOTE 1: The value of <user-requested-priority> is associated to the Communication Session Category as specified in clause 6.2.5 of the present document. The following SIP response codes with the FRMCS-specific warning texts shall be supported by the MCData clients and the FRMCS Service Domain: • If the terminating application is not locally bound, the SIP response shall be set to 480 with warning text "FRMCS-Terminating application is not locally bound". • If the terminating application is not allowed by profile to receive an incoming session, the SIP response shall be set to 403 with warning text "FRMCS-Terminating application is not allowed to receive an incoming session". • If the incoming session timer (i.e. T_INCOMING_SESSION) is expired at the terminating FRMCS entity, the SIP response shall be set to 408 with warning text "FRMCS-Terminating application did not respond in time to session invitation". • If the terminating application entity declined the request, the SIP response shall be set to 603 with warning text "FRMCS-Terminating application declined the request". NOTE 2: FRMCS Trackside Gateway cannot originate a Host-to-Network MCData IPcon session. The IP management during the establishment of a Trackside originated session of type Host-to-Host is described in clause 6.2.2.4.4. The <application-data> element within the AnyExt extension field of MCData IPcon session request, sent on each hop from originating MCData client up to the terminating MCData client, shall be set as specified in clause 6.2.2.4.4. NOTE 3: The detailed format of <application-data> is not specified in the present document. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 21 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4 IP management and data transfer for H2H and H2N addressing schemes | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4.1 IP layer model | The set of different IP address ranges relevant to a Loose Coupled Application is defined in ETSI TS 103 764 [i.2], clause 8. The MCData signaling to setup MCData IPcon tunnel between the On-Board FRMCS and the FRMCS Trackside Gateway is using the service domain IP address range (SD_PUB_IP). If a MCData client within the On-Board FRMCS is not using an IP within SD_PUB_IP, the On-Board FRMCS shall implement a NAT function to translate IP addresses used for MCData signalling to and from the SD_PUB_IP range. If a MCData client within the FRMCS Trackside Gateway is not using an IP within SD_PUB_IP, the FRMCS Trackside Gateway, shall implement a NAT function to translate IP addresses used for MCData signalling to and from the SD_PUB_IP range. The following are the pre-requisite for the procedures in clauses 6.2.2.4.2 to 6.2.2.4.4: • The On-Board Loose-Coupled Application has completed the Local Binding as per ETSI TS 103 765-3 [i.3], clause 7.3.1.1. • The Trackside Application has completed the local binding as per ETSI TS 103 765-4 [i.4], clause 6.3.1.1. • The On-Board FRMCS maintains a pool of virtual IPs in the range of OB_PRV_IP, called ViOB. • The FRMCS Trackside Gateway maintains a pool of virtual IPs in the range of TS_FTG_IP, called ViTS. NOTE: In the OBAPP/TSAPP API context, references to the Loose-Coupled Application also include the Super Loose-Coupled Application that utilizes an external API agent. 6.2.2.4.2 IP management during an On-Board-FRMCS-originated Host-to-Host session establishment The IP management during the session establishment phase is done as follows (illustrated in Figure 6.2.2.4.2-1): 1) Upon the reception of a request on OBAPP for opening a session of type H2H, the On-Board FRMCS acts as specified in ETSI TS 103 765-3 [i.3], clause 7.3.2.1. If the request is valid: a) the On-Board Loose-Coupled Application IP address, namely OBA1, is retrieved from the request. b) The On-Board FRMCS selects one IP address from the ViOB, representing the Trackside Application for this OBAPP session within the On-Board FRMCS, namely the ViOB TSA1. 2) The MCData IPcon session request initiated by the originating MCData Client is forwarded up to the terminating MCData Client as defined in clause 6.2.2.2.1 of the present document: a) The <application-data> in the SIP requests sent on each hop from originating MCData client up to the terminating MCData client shall include IP address ViOB TSA1. 3) Upon reception of a MCData IPcon session request at the FRMCS Trackside Gateway: a) The FRMCS Trackside Gateway selects a virtual IP address out of the ViTS, representing the On-Board Loose-Coupled Application within the FRMCS Trackside Gateway, namely ViTS OBA1. b) The FRMCS Trackside Gateway sends a notification of type "incomingSessionNotif" to the Trackside Application as per ETSI TS 103 765-4 [i.4], clause 6.3.2.3. 4) Upon reception of an incoming session acceptance response from the Trackside Application, the FRMCS Trackside Gateway retrieves the Trackside Application IP address (i.e. TSA1) from the response. 5) The Trackside Application Network NAT function (definition in ETSI TS 103 765-4 [i.4], clause 5.4.1) shall maintain the mapping between the couple IP addresses (OBA1, ViOB TSA1) and (ViTS OBA1, TSA1). 6) The MCData IPcon session response initiated by the terminating MCData Client is forwarded up to the originating MCData Client as defined in clause 6.2.2.2.1 of the present document. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 22 7) Upon the reception of the response in step 6, the On-Board FRMCS sends a notification of type "openSessionFinalAnswerNotif " to the On-Board Loose-Coupled Application (as per ETSI TS 103 765-3 [i.3], clause 7.3.2.1). 8) Upon the reception of SIP OK, the FRMCS Trackside Gateway should send a notification of type "openSessionFinalAnswerNotif " to the Trackside Application. NOTE 1: Following this procedure, the On-Board Loose-Coupled Application will use the ViOB TSA1 (obtained at step 7) as the destination IP address for its outgoing IP packets linked to this H2H session. NOTE 2: (If step 8 is not implemented): When the session is On-Board Originated, the first IP packet needs to be sent from On-Board towards the Trackside. The Trackside Application learns from the previously received packets which IP address to use as the destination IP address for its outgoing packets (i.e. ViTS OBA1). NOTE 3: (If step 8 is implemented): Following this procedure, the Trackside Application will use the ViTS OBA1 (obtained at step 8) as the destination IP address for its outgoing IP packets linked to this H2H session. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 23 Figure 6.2.2.4.2-1: H2H session establishment ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 24 6.2.2.4.3 IP management during an On-Board-FRMCS-originated Host-to-Network session establishment Pre-requisite: the H2N network endpoint is configured within FRMCS Trackside Gateway as defined in ETSI TS 103 765-4 [i.4], clause 6.1.2. The IP management during the session establishment phase is done as follows: 1) Upon the reception of a request on OBAPP for opening a session of type H2N, the On-Board FRMCS acts as specified in ETSI TS 103 765-3 [i.3], clause 7.3.2.1. If the request is valid: a) The On-Board Loose-Coupled Application IP address, namely OBA1, is retrieved from the request. b) For this H2N session request, the On-Board FRMCS selects one IP address from the ViOB, representing the Trackside Application for this OBAPP session within the On-Board FRMCS, namely the ViOB TSAx. c) The remoteId provided in the OBAPP request for a H2N session is mapped within the FROP to Functional Alias/MC Service ID representing the H2N network endpoint within FRMCS Trackside Gateway. The terminating MCData Client in the following steps is the one associated to this MC Service ID. NOTE 1: The dns_request provided in the OBAPP request for a H2N session carries the FQDN of the intended application server whose DNS resolution is requested at the same time of session establishment. Alternatively, the application can directly provide the IP address of the intended application server (i.e. TSAx) in dns_request. 2) The MCData IPcon session request initiated by the originating MCData IPcon is forwarded up to the terminating MCData Client as defined in clause 6.2.2.2.1 of the present document. The <application-data> in the SIP requests sent on each hop from originating MCData client up to the terminating MCData client shall include the value provided in dns_request of the OBAPP request and the IP address ViOB TSAx. 3) Upon reception of a MCData IPcon session request addressing a MCData client representing the H2N Network endpoint within the FRMCS Trackside Gateway, if the <application-data> contains the FQDN of the Trackside Application server: a) A DNS client within the FRMCS Trackside Gateway sends a DNS request for the resolution of the FQDN retrieved from <application-data> to the DNS server. b) Upon the reception of the DNS response including TSAx as the resolved IP address, the FRMCS Trackside Gateway selects a virtual IP address out of the ViTS, representing the On-Board Loose-Coupled Application within the FRMCS Trackside Gateway, namely ViTS OBA1. 4) The FRMCS Trackside Gateway maintains a mapping between the couple IP addresses (OBA1, ViOB TSAx) and (ViTS OBA1, TSAx) as specified in ETSI TS 103 765-4 [i.4], clause 5.4.1. 5) The MCData IPcon session response initiated by the terminating MCData Client is forwarded up to the originating MCData Client as defined in clause 6.2.2.2.1 of the present document. 6) Upon the reception of the response in step 5, the On-Board FRMCS sends a notification of type "openSessionFinalAnswerNotif" towards the On-Board Loose-Coupled Application (as per ETSI TS 103 765-3 [i.3], clause 7.3.2.1). NOTE 2: If the On-Board application is Super-Loose Coupled, the API agent needs also to include a DNS server. Upon reception of a DNS request from the On-Board SLC Application, the API agent sets the dns_request parameter of OBAPP for opening a session to the FQDN to be resolved (which is retrieved from the DNS request). ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 25 6.2.2.4.4 IP management during a Trackside-Gateway-originated Host-to-Host session establishment The IP management during the session establishment phase is done as follows: 1) Upon the reception of a request on TSAPP for opening a session of type H2H, the FRMCS Trackside Gateway acts as specified in ETSI TS 103 765-4 [i.4], clause 6.3.2.1. If the request is valid: a) The Trackside Loose-Coupled Application IP address, namely TSA1, is retrieved from the request. b) The FRMCS Trackside Gateway selects one IP address from the ViTS, representing the On-Board Application for this TSAPP session within the FRMCS Trackside Gateway, namely the ViTS OBA1. 2) The MCData IPcon session request initiated by the originating MCData Client is forwarded up to the terminating MCData Client as defined in clause 6.2.2.2.1 of the present document. 3) Upon reception of a MCData IPcon session request at the On-Board FRMCS: a) The On-Board FRMCS selects a virtual IP address out of the ViOB, representing the Trackside Loose-Coupled Application within the On-Board FRMCS, namely ViOB TSA1. b) The On-Board FRMCS sends a notification of type "incomingSessionNotif" to the On-Board Application as per ETSI TS 103 765-3 [i.3], clause 7.3.2.3. 4) Upon reception of an incoming session acceptance response from the On-Board Application, the On-Board FRMCS retrieves the On-Board Application IP address (i.e. OBA1) from the response. 5) The MCData IPcon session response initiated by the terminating MCData Client is forwarded up to the originating MCData Client as defined in clause 6.2.2.2.1 of the present document: a) The <application-data> in the SIP requests sent on each hop from terminating MCData client up to the originating MCData client shall include IP address ViOB TSA1. 6) The Trackside Application Network NAT function (definition in ETSI TS 103 765-4 [i.4], clause 5.4.1) shall maintain the mapping between the couple IP addresses (OBA1, ViOB TSA1) and (ViTS OBA1, TSA1). 7) Upon the reception of the response in step 5, the FRMCS Trackside Gateway sends a notification of type "openSessionFinalAnswerNotif " to the Trackside Loose-Coupled Application (as per ETSI TS 103 765-4 [i.4], clause 6.3.2.1). 8) Upon the reception of SIP OK, the On-Board FRMCS should send a notification of type "openSessionFinalAnswerNotif " to the On-Board Application. NOTE 1: Following this procedure, the Trackside Loose-Coupled Application will use the ViTS OBA1 (obtained at step 5) as the destination IP address for its outgoing IP packets linked to this H2H session. NOTE 2: If step 8 is not implemented: When the session is Trackside Originated, the first IP packet needs to be sent from Trackside towards the On-Board. The On-Board Application learns from the previously received packets which IP address to use as the destination IP address for its outgoing packets (i.e. ViOB TSA1). NOTE 3: If step 8 is implemented: Following this procedure, the On-Board Application can use the ViOB TSA1 (obtained at step 8) as the destination IP address for its outgoing IP packets linked to this H2H session. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 26 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.