hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.5.1 MCPTT voice services in interconnected FRMCS service Domains | The MCPTT procedures in clause 6.2.1 apply for interconnected FRMCS Service Domains. If the interconnected FRMCS Service Domains are considered to be in different trust domains, the FRMCS Service Domain shall conform to the procedures regarding MC Gateway Server as defined in ETSI TS 124 379 [7], clause 6.8. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.5.2 MCData IP Connectivity in interconnected FRMCS Service Domains | The MCData IPcon procedures in clause 6.2.2 apply for interconnected FRMCS Service Domains. If the interconnected FRMCS Service Domains are considered to be in different trust domains, the FRMCS Service Domain shall conform to the procedures regarding MC Gateway Server as defined in ETSI TS 124 282 [9], clause 6.8. ETS... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 1 Scope | The present document specifies non-3GPP network functions and interfaces applicable to the FRMCS Trackside Infrastructure. The present document describes the trackside network architecture and proceeds with specifying the non-3GPP trackside network functional entities (such as the FRMCS Trackside Gateway), including fu... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 2 References | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3 Definition of terms, symbols and abbreviations | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.1] and the following apply: Hosting Clients: MC Service Client located in FRMCS Trackside Gateway NOTE: Hosting Client connects Loose-Coupled FRMCS applications to FRMCS system. Reference point TAP TS: reference point represents the connect... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.2 Symbols | Void. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DNS Domain Name Server FRMCS Future Railway Mobile Communication System H2H Host-to-Host H2N Host-to-Network HTTP Hyper Text Transfer Protocol IP Internet Protocol ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 8 IWF Interworking Function JSON JavaSc... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 4 Trackside network architecture | FRMCS trackside architecture consists of at least one FRMCS Transport Domain (as described in ETSI TS 103 765-1 [3], clause 4.2) and zero or more non-FRMCS Transport Domains. The FRMCS Service Domain (as described in ETSI TS 103 765-2 [2], clause 5.1) enables communication as services between two or multiple FRMCS User... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5 FRMCS Trackside Gateway | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.1 General | The FRMCS Trackside Gateway is a logical component which is used to host specific functions. The FRMCS Trackside Gateway is the logical symmetrical component to the On-Board FRMCS. It is the link between the Transport Network and the Application at the infrastructure side (see UIC FRMCS SRS (FW-AT 7800) [i.2], Figure 6... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.2 FRMCS Trackside Gateway architecture | The functional architecture of FRMCS Trackside Gateway is illustrated in Figure 5.2-1. The FRMCS Trackside Gateway links the trackside application. FRMCS Trackside Gateway TAP TS TSAPP Multipath Gateway TAP Service Agents FRMCS Service Serverl Figure 5.2-1: Functional architecture of FRMCS Trackside Gateway The generic... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.3 FRMCS Trackside Gateway functionalities | The FRMCS Trackside Gateway hosts the FRMCS Service Stratum functions when the FRMCS Trackside Gateway is configured to serve a Loose-Coupled Application (including H2H and H2N models). The detailed functional architecture of the FRMCS Trackside Gateway is depicted in Figure 5.3-1 (note that the figure does not resume ... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4 FRMCS Trackside Gateway Functions | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4.1 Trackside Application Network NAT Function | The FRMCS Trackside Gateway requires the implementation of NAT functionality when enabling communication with an On-Board FRMCS. The Trackside Application Network NAT Function is responsible for NAT for the Application Plane communication between an on-Board Loose-Coupled application and a Trackside application. ETSI E... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.4.2 Trackside Service NAT Function | The FRMCS Trackside Gateway requires the implementation of NAT functionality when enabling communication with an On-Board FRMCS. The Trackside Service NAT Function is responsible for NAT or the following particular aspects listed in the bullet point s below: • For the FRMCS Service Control Plane communication between a... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5 FRMCS Trackside Gateway interfaces | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.0 Introduction | As defined in clause 5.2, the FRMCS Trackside Gateway supports two interfaces: • TSAPP. • TAP TS. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.1 TSAPP | The TSAPP interface is the interface between trackside applications and the FRMCS Trackside Gateway. The FRMCS Trackside Gateway shall implement the procedures associated to the TSAPP interface specified in clause 6.3. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 5.5.2 TAP TS | The TAP TS reference point connects the FRMCS Trackside Gateway and a FRMCS Domain. The FRMCS Trackside Gateway acts a MC Service Client over the TAP TS reference point. The TAP TS is composed of the MC Client reference points identified in ETSI TS 103 765-2 [2], clause 5.1.2. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 12 |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6 FRMCS Trackside Gateway procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1 General procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1.1 General provisioning | The FRMCS Trackside Gateway needs to be provisioned as part of the FRMCS Railway Trackside Profile (defined in ETSI TR 103 791 [i.1]) with configuration data to enable the operation over the TSAPP. This includes in particular: • Mapping rules to derive a MC User ID for a Loose-Coupled Application doing a Local Binding.... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.1.2 Host-to-Network provisioning | To enable the MCData IPcon session establishment procedures and the data transfer procedures specified in ETSI TS 103 765-2 [2], clauses 6.2.2.3 and 6.2.2.4 for Host-to-Network operation, the FRMCS Trackside Gateway relies on the provisioning of information associated to the network towards which it enables the connect... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2 Procedures not associated to a reference point | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.1 MC Service Client IP assignment procedure | At setup of an MC Service Client inside the FRMCS Trackside Gateway an IP address shall be assigned for the Interface towards the TAP TS. The IP address assignment may be set statically based on configuration inside the FRMCS Trackside Gateway or set dynamically via locally-defined dynamic IP address assignment methods... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.2 MC Service Client readiness procedure | The following steps are undertaken: 1) The FRMCS Trackside Gateway shall retrieve from FRMCS Railway Trackside Profile the following information: a) the mapping rule which allows to derive the MC User ID; b) the password credentials for this MC User ID; c) the scope associated to this MC User ID (as specified in ETSI T... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.3 MC Service Client teardown procedure | The following steps are undertaken: 1) For each ongoing session associated with the application, the FRMCS Trackside Gateway shall notify the application of the termination of the session by sending a notification of type sessionClosure on the notification event stream associated with the application as specified in cl... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.4 TSAPP Application Context clearance procedure | The following steps are undertaken: 1) For each ongoing session associated with the application, the FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The FRMCS Trackside Gateway shall clear the TSAPP application context associate... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.5 Ongoing communication release | The following steps are undertaken for releasing an ongoing communication associated to a Loose-Coupled Application: 1) The FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The FRMCS Trackside Gateway shall notify the application... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.2.6 Logging | For all procedures specified in clause 6.3, the FRMCS Trackside Gateway shall log the endpoint invocations which lead to a HTTP status code 400, 401, 403 or 404. For all procedures specified in clause 6.3.2 (/sessions), the FRMCS Trackside Gateway shall log all endpoint invocations. For each logged event, the FRMCS Tra... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3 Procedures associated with TSAPP endpoints | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.0 Introduction | The present clause specifies the behaviour expected from the FRMCS Trackside Gateway in relation with the TSAPP reference point as specified in FRMCS FFFIS-7950 [1]. For all TSAPP endpoint procedures defined below, the FRMCS Trackside Gateway shall return HTTP error responses as specified in FRMCS FFFIS-7950 [5] when e... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1 /registrations endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.1 Application registration procedure | Upon invocation of the "/registrations" endpoint with the HTTP POST verb, the FRMCS Trackside Gateway is expected to create an TSAPP Application Context for the application. The following steps are undertaken: 1) If a TSAPP Application Context associated with a TSAPP Application Tuple already exists in the FRMCS Tracks... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.2 Application-initiated deregistration procedure | Upon invocation of the "/registrations/{dynamicId}" endpoint with the HTTP DELETE verb, the FRMCS Trackside Gateway is expected to clean up any context associated to the application. The following steps are undertaken: 1) For each ongoing MCData IPcon session associated with the application, the FRMCS Trackside Gateway... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.1.3 FRMCS-Trackside-Gateway-initiated deregistration procedure | The following steps are undertaken: 1) For each application in Locally Bound state: a) the FRMCS Trackside Gateway shall notify the application of its upcoming deregistration from the FRMCS Trackside Gateway by sending a notification of type upcomingDeregistration on the notification event stream associated with the ap... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2 /sessions endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.1 FRMCS-Trackside-Gateway-initiated session initiation procedure | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP POST verb, the FRMCS Trackside Gateway is expected to open a session towards a remote endpoint. In the following, the parameters communicationCategory, localAppIPAddress, and recipient (containing remoteId) are those retrieved from the JSON payload o... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.2 FRMCS-Trackside-Gateway-initiated session termination procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP DELETE verb, the FRMCS Trackside Gateway is expected to terminate the referred session. The following steps are undertaken: 1) The FRMCS Trackside Gateway shall execute the MCData IPcon session release procedure as identified in ETSI TS 1... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.3 FRMCS-Trackside-Gateway-terminated incoming session invite procedure | NOTE 1: The present document only specifies the handling of incoming MCData IPcon session invites. Upon receipt of a "SIP INVITE request for IP Connectivity session for terminating MCData client" by the MC Service Client associated with a Loose-Coupled Application, the FRMCS Trackside Gateway is expected to notify the ... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.5 FRMCS-Trackside-Gateway-terminated session termination procedure | Upon receipt of a "SIP BYE" request for releasing an MCData IPcon session by the terminating MC Client associated with a Loose-Coupled Application, if there is a sessionId in TSAPP Application context associated to the MCData IPCon session and if the RELEASE_CAUSE in the SIP Reason header field of SIP BYE is set to 1 (... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.6 Information query on ongoing sessions for an application | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide information on the ongoing sessions associated to the application. If the query is authorized, the FRMCS Trackside Gateway shall respond with a 200 OK response code as specified in FRMCS FF... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.2.7 Information query on a specific ongoing session for an application | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide information on the designated session. If the query is authorized, the FRMCS Trackside Gateway shall respond with a 200 OK response code as specified in FRMCS FFFIS-7950 [5], cl... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3 /notifications endpoint procedures | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3.1 Procedure for opening the notification event stream | Upon invocation of the "/notifications/{dynamicId}/events" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to open an SSE notification stream towards the application. ETSI ETSI TS 103 765-4 V1.1.1 (2026-01) 20 The following steps are undertaken: 1) The FRMCS Trackside Gateway shall register the... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.3.2 Procedure of notification to an application over a channel | The SSE data field shall be filled with the JSON data structure as passed to the procedure. EXAMPLE: For a successful final answer notification, the JSON data structure would be: { "openSessionFinalAnswerNotif": "success": { "sessionId": <data>, "nextHopIpAddress": <data>, "destApplicationIPAddress": <data> } The SSE e... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.4 /versions endpoint procedures | Upon invocation of the "/versions" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide the list of versions it supports. The following steps are undertaken: 1) The FRMCS Trackside Gateway shall prepare an API VersionsData data structure with the list of versions supported as specified in... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 6.3.5 /keepalive endpoint procedures | Upon invocation of the "/keepalive" endpoint with the HTTP GET verb, the FRMCS Trackside Gateway is expected to provide a HTTP-level response to indicate the TSAPP reference point is responsive. The FRMCS Trackside Gateway shall respond with a 204 No Content response code as specified in FRMCS FFFIS-7950 [1], clause 10... |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7 VAS-Controller Equipment connection | |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7.1 Functions | VAS Controller functions are not specified in the present document. |
3f58a6be5d374e4253ad93265b592016 | 103 765-4 | 7.2 Interfaces | The reference point between VAS Controller Equipment and FRMCS System is TSCTRL. The VAS Controller Equipment (Dispatcher System) shall support the following ETSI reference points to access FRMCS service domain: • CSC-1, CSC-2, CSC-4 and CSC-8 for the FRMCS Service User Plane as specified in ETSI TS 123 280 [4], clause... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 1 Scope | The present document specifies the interfaces of the On-Board FRMCS enabling either interaction with On-Board applications or with FRMCS entities outside the train. The present document also specifies the On-Board Multipath Function and a set of procedures the On-Board FRMCS will need to conform to. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 2 References | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3 Definition of terms, symbols and abbreviations | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.2] and the following apply: OBAPP Application Context: context maintained by the On-Board FRMCS for an application instance (identified by the OBAPP Application Tuple), in between registration and de-registration OBAPP Application Tuple: tu... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.2 Symbols | Void. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACME Automated Certificate Management Environment API Application Programming Interface CellID Cell IDentifier EST Enrollment over Secure Transport FA Functional Alias FCOP FRMCS Close of OPeration FFFIS Form Fit Functional Interface Specifica... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4 On-Board FRMCS reference points | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.1 Background | This clause covers the external reference points of the On-Board FRMCS (see Figure 4.1-1) as defined in UIC FRMCS SRS [i.1]. On-Board FRMCS Application(s) OBAPP FSOMR OBANT OBOM Figure 4.1-1: On-Board FRMCS external reference points |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.2 OBApp | The on-board communication system will interact with several on-board applications. Due to this, the interface OBAPP has to ensure the proper handling and management of the interconnected applications and grant access to the communication services provided taking into account the priority and quality of service profile... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3 FSOMR | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3.1 Introduction | The present document only covers a subset of FSOMR functionality defined in UIC FRMCS SRS [i.1], namely those for the purpose of obtaining FRMCS Railway On-Board Profile (FROP) and FRMCS On-Board Application Profile (FOAP). |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.3.2 Profiles management | The FSOMR enables profiles management in FRMCS for the On-Board FRMCS across three essential functionalities: • SIM profile management. • TLS certificates management. • Management of other profile information. For SIM profile management, the functionalities are delegated to individual On-Board FRMCS Radio Modules using... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.4 OBANT | The present document does not specify the OBANT reference point or its use within an On-Board FRMCS. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 4.5 OBOM | The present document does not specify the OBOM reference point or its use within an On-Board FRMCS. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5 On-Board FRMCS general requirements | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.1 On-Board FRMCS Radio Modules | An On-Board FRMCS Radio Module shall comply with ETSI TS 103 765-5 [3], clause 4. An On-Board FRMCS Radio Module shall comply with ETSI TS 103 793 [4], clauses 4 and 6. |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2 Location and positioning | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2.1 Generalities | The On-Board FRMCS is expected to provide location information based on three possible sources: cellular network, GNSS and external sources. Obtaining information from external sources is out of scope of the present document. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 11 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.2.2 Functional requirements | The On-Board FRMCS shall be equipped with a GNSS receiver. The GNSS receiver of the On-Board FRMCS shall be capable of receiving and processing signals from at least two satellite constellations. The On-Board FRMCS shall be able to obtain CellID information from each of its On-Board FRMCS Radio Modules. NOTE: The prese... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 5.3 Profile Storage | The support of Loose-Coupled Applications by an On-Board FRMCS and the distribution of functionalities between the MC Clients within the On-Board FRMCS on the one hand and the On-Board FRMCS Radio Module(s) on the other hand imply that the On-Board FRMCS has to store and manage sensitive information (such as credential... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 6 On-Board Multipath Function | An On-Board FRMCS supporting FRMCS Multipath shall: • Implement a Multipath Client as specified in ETSI TS 103 765-1 [1], clause 5.3.5. • Comply with the procedures related to the Multipath Client as specified in ETSI TS 103 765-1 [1], clause 5.3.7. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 12 |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7 On-Board FRMCS procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1 General procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.1 FRMCS Start of Operation | The FRMCS Start of Operation (FSOP) procedure is supporting the transition of On-Board FRMCS operational mode from the train power-up until the moment On-Board FRMCS is in FRMCS Domain availability state. The procedure describes the expected behaviour from On-Board FRMCS and FRMCS Domain upon power-up of the train and ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.2 FRMCS Close of Operation | The FRMCS Close of Operation (FCOP) procedure describes the expected behaviour of On-Board FRMCS and FRMCS Domain upon attempt by an On-Board FRMCS to disconnect from the FRMCS System. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 13 The following steps are undertaken: 1) For each application in Locally Bound state: a) the O... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.1 Inter-FRMCS Domain Transition (IFDT) procedure | Precondition: • The On-Board FRMCS has received a Network Transition Trigger (NTT) indicating the Target FRMCS Transport Domain (identified by a PLMN ID). • The On-Board FRMCS has selected a Target On-Board FRMCS Radio Module. • The Target On-Board FRMCS Radio Module is different from the Serving On-Board FRMCS Radio M... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.2 Inter-FRMCS Domain transition: Type I or Type III applications | 7.1.3.2.1 Inter-FRMCS Domain transition: Type I or Type III applications with no open session For each Loose-Coupled Application in Locally Bound state and identified as interoperable in any FRMCS Domain in the FRMCS Railway On-Board Profile, if the application has no open session, the following steps are undertaken: 1... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.3 Inter-FRMCS Domain transition: Type II applications | 7.1.3.3.1 Inter-FRMCS Domain transition: Type II applications entering the Domain of applicability For each Loose-Coupled Application in Locally Bound state and for which the On-Board FRMCS is entering a FRMCS Domain within the Domain of applicability of the application as identified from the FRMCS Railway On-Board Pro... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.3.4 Inter-FRMCS Domain transition: Type IV applications | For each Loose-Coupled Application in Locally Bound state and identified as Type IV in the FRMCS Railway On-Board Profile, if the application has at least one open session: 1) The On-Board FRMCS shall establish home-routed transport path on the On-Board FRMCS Radio Modules as specified in ETSI TS 103 765-1 [1], clause ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4 GSM-R to FRMCS transition | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.1 GSM-R to FRMCS transition procedure | Precondition: • The On-Board FRMCS has received a Network Transition Trigger (NTT) indicating the Target FRMCS Transport Domain (identified by a PLMN ID). • The On-Board FRMCS has selected a Target On-Board FRMCS Radio Module. • For a given train, all running applications are served either by GSM-R or by FRMCS at a giv... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.2 GSM-R to FRMCS transition: Type I or Type III applications | For each Loose-Coupled Application in Locally Bound state and identified as interoperable in any FRMCS Domain in the FRMCS Railway On-Board Profile, the On-Board FRMCS shall execute the MC Client readiness for network transition procedure as specified in clause 7.2.3 of the present document. 7.1.4.3 GSM-R to FRMCS tran... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.1.4.4 GSM-R to FRMCS transition: Type IV applications | For each Loose-Coupled Application in Locally Bound state and identified as Type IV in the FRMCS Railway On-Board Profile, if the application has at least one open session: 1) The On-Board FRMCS shall establish home-routed transport path on the On-Board Radio Modules (see ETSI TS 103 765-1 [1], clause 4.2.3 for relevan... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2 Procedures not associated with a reference point | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.1 MC Client IP assignment procedure | Each MC Client is reachable via a unique IP address and port from the IP range SD_PUB_IP as described in ETSI TS 103 764 [i.6]. The On-Board FRMCS manages this public IP/port mapping to the private MC Client IP addresses from the IP range OB_PRV_IP as described in ETSI TS 103 764 [i.6]. The IP address assignment proced... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.2 MC Client readiness procedure | The following steps are undertaken: 1) The On-Board FRMCS shall retrieve from FRMCS Railway On-Board Profile the following information: a) The mapping rule which allows to derive the MC User ID. b) The password credentials for this MC User ID. c) The scope associated to this MC User ID (as specified in ETSI TS 133 180 ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.3 MC Client readiness for network transition procedure | If the flag "IFSDT_DUAL_MCID_IN_PROGRESS" is not set in the application context within the On-Board FRMCS, the following steps are undertaken: 1) The On-Board FRMCS shall perform the "MC User registration" procedure in Target FRMCS Service Domain using the IMS credentials retrieved from the FRMCS Railway On-Board Appli... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.4 MC Client teardown procedure | The following steps are undertaken: 1) For each ongoing session associated with the application, the FRMCS Trackside Gateway shall notify the application of the termination of the session by sending a notification of type sessionClosure on the notification event stream associated with the application as specified in cl... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.5 OBAPP Application Context clearance procedure | The following steps are undertaken: 1) If the application is a Loosed Coupled application, for each ongoing MCData IPcon session associated with the application, the On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. 2) The On-Board FRMCS shal... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.6 Ongoing communication release procedure | The following steps are undertaken for releasing an ongoing communication associated to a Loose-Coupled application: 1) For an ongoing session associated with a Loose-Coupled application, the On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clause 6.2.2.5. ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.2.7 Logging | For all procedures specified in clause 7.3, the On-Board FRMCS shall log the endpoint invocations which lead to a HTTP status code 400, 401, 403 or 404. For all procedures specified in clause 7.3.2 (/sessions), the On-Board FRMCS shall log all endpoint invocations. ETSI ETSI TS 103 765-3 V1.1.1 (2026-01) 22 For each lo... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3 Procedures associated with OBAPP endpoints | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.0 Introduction | The present clause specifies the behaviour expected from the On-Board FRMCS in relation with the OBAPP reference point as specified in FRMCS FFFIS-7950 [5]. For all OBAPP endpoint procedures defined below, the On-Board FRMCS shall return HTTP error responses as specified in FRMCS FFFIS-7950 [5] when encountering the fo... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1 /registrations endpoint procedures |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.