hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 Handhel... |
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 D... |
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... |
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... |
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 Netw... |
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 ... |
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... |
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 ... |
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 b... |
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 p... |
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... |
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 undertak... |
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 consider... |
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: ... |
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 ... |
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 FR... |
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. deployme... |
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], c... |
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.... |
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 t... |
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 define... |
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 a... |
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 i... |
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 compl... |
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 D... |
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 1... |
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 interconnect... |
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 serv... |
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; ... |
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 o... |
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 ser... |
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 Do... |
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 invol... |
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 U... |
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 spec... |
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. T... |
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 3... |
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 h... |
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 mode... |
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... |
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... |
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... |
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 t... |
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> ele... |
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 t... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4.5 Data transfer from the On-Board-FRMCS to the FRMCS Trackside Gateway | For Data transfer from the On-Board-FRMCS to the FRMCS Trackside Gateway, the following steps are undertaken (see Figure 6.2.2.4.5-1 and clause 6.2.2.2.2): 1) The MCData client within the On-Board FRMCS encapsulates the incoming IP packets from the On-Board LC Application (source: OBA1, destination: ViOB TSA1) into the... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.4.6 Data transfer from the FRMCS Trackside Gateway to the On-Board-FRMCS | For Data transfer from a FRMCS Trackside Gateway to an On-Board-FRMCS, the following steps are undertaken (see Figure 6.2.2.4.5-1 and clause 6.2.2.2.2): 1) The Trackside Application Network NAT shall replace the source and destination IP addresses (source: TSA1, destination: ViTS OBA1) in the incoming IP packets from t... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.2.5 MCData IPcon session release | When this procedure is called by either On-Board FRMCS or FRMCS Trackside Gateway, the corresponding MCData client shall initiate the release of the MCData communication (see clause 6.2.2.2.3). |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.3 MCData SDS | The FRMCS Service Domain shall support ETSI TS 124 282 [9], clauses 9.2.2.3.1 (excluding step 4a) and 9.2.2.4.2 (excluding step 6). |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.4 MCData File Distribution | The present document does not specify normative requirements for MCData file distribution service. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.5 QoS and priority signalling | User's requested priority from MC session request as per ETSI TS 123 280 [2] shall be used for indicating the requested QoS and priority to the MC Service Server. Requested priority shall be used to uniquely identify railway communication session categories. The conveyance of <user-requested-priority> in the SIP INVITE... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.6 Functional aliasing | This clause describes the functional aliasing for FRMCS Service Domain. The procedures for MCData server serving the MCData user for management of functional alias shall conform to ETSI TS 124 282 [9], clause 8.3.2. The procedures for MCData server owning functional alias shall conform to ETSI TS 124 282 [9], clause 8.... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.2.7 Arbitration | The present document does not specify normative requirements with respect to arbitration. |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3 MC User deregistration | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.1 MC User deregistration in Home FRMCS Service Domain | This clause describes the MC Service User deregistration in Home FRMCS Service Domain. MC Service User deregistration implies MC Service User can no longer receive MC services and SIP services. Pre-requisite: the ongoing communications of the MC Service User are released. If this procedure is initiated by its caller en... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.2 MC User deregistration in Foreign FRMCS Service Domain | This clause describes the MC Service User deregistration in Foreign FRMCS Service Domain. MC Service User deregistration implies MC Service User can no longer receive MC services and SIP services. Pre-requisite: the ongoing communications of the MC Service User is released. If this procedure is initiated by its caller ... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.3.3 Network initiated MC User deregistration | The present document does not specify network initiated MC Service User deregistration. ETSI ETSI TS 103 765-2 V1.1.1 (2026-01) 30 |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4 Inter FRMCS service domain transition | |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4.1 MC Service User migration | This clause describes the steps that shall be undertaken for MC User migration of a given MC User. The values passed into this procedure by its caller entity shall be used by the IdM Client and individual MC Service clients involved in the procedures referenced below. Precondition: The MC User is authenticated, and the... |
4512d63c6de502e416921955aa495103 | 103 765-2 | 6.4.2 Migrated MC Service user deauthorization | This clause describes the requirements for migrated MC Service user deauthorization when the user leaves a Foreign FRMCS Service Domain (to move to another Foreign FRMCS Service Domain or to go back to the Home FRMCS Service Domain). The MCPTT client procedure for MC user migration deauthorization shall conform to ETSI... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.