hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1.1 Application registration procedure | Upon invocation of the "/registrations" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to create an OBAPP Application Context for the application. The following steps are undertaken: 1) If an OBAPP Application Context associated with OBAPP Application Tuple already exists in the On-Board FRMCS, the On... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.1.2 Application-initiated deregistration procedure | Upon invocation of the "/registrations/{dynamicId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clean up any context associated with the application. The following steps are undertaken: 1) For each ongoing MCData IPcon session associated with the application, the On-Board FRMCS shall execute t... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2 /sessions endpoint procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.1 On-Board-FRMCS-initiated session initiation procedure | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to open a session towards a remote endpoint. In the rest of the present clause, the parameters communicationCategory, localAppIPAddress, and recipient (containing remoteId) are those retrieved from the JSON p... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.2 On-Board-FRMCS-initiated session termination procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to terminate the referred session. The following steps are undertaken: 1) The On-Board FRMCS shall execute the MCData IPcon session release procedure as identified in ETSI TS 103 765-2 [2], clau... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.3 On-Board-FRMCS-terminated incoming session invite procedure | NOTE 1: The present document only specifies the handling of incoming MCData IPcon session invites. Upon receipt of a "SIP INVITE request for IP Connectivity session for terminating MCData client" by the MC Client associated with a Loose-Coupled Application, the On-Board FRMCS is expected to notify the application. The ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.4 On-Board-FRMCS-terminated incoming session response procedure | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP PUT verb, the On-Board FRMCS is expected to provide a response to the "SIP INVITE request for IP Connectivity session for terminating MCData client" received prior. The following steps are undertaken: 1) The On-Board FRMCS shall clear the... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.5 On-Board-FRMCS-terminated session termination procedure | Upon receipt of a "SIP BYE" request for releasing an MCData IPcon session by the terminating MC Client associated with a Loose-Coupled Application, if there is a sessionId in OBAPP Application context associated to the MCData IPCon session and if the RELEASE_CAUSE in the SIP Reason header field of SIP BYE is set to 1 (... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.6 Information query on ongoing sessions for an application | Upon invocation of the "/sessions/{dynamicId}" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide information on the ongoing sessions associated to the application. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], cl... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.2.7 Information query on a specific ongoing session for an application | Upon invocation of the "/sessions/{dynamicId}/{sessionId}" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide information on the designated session. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7950 [5], clause 9.12.2. The... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3 /notifications endpoint procedures | |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.1 Procedure for opening the notification event stream | Upon invocation of the "/notifications/{dynamicId}/events" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to open an SSE notification stream towards the application. The following steps are undertaken: 1) The On-Board FRMCS shall register the notification types identified in FRMCS FFFIS-7950 [5], claus... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.2 Procedure upon subscription to a channel | Upon invocation of the "/notifications/{dynamicId}/channels/{channel}" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to add the notification types associated with the requested channel to the list of notification types in the OBAPP Application Context. The following steps are undertaken: 1) The On-Bo... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.3 Procedure upon unsubscription from all channels | Upon invocation of the "/notifications/{dynamicId}/channels" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clear all subscription to notification types in the OBAPP Application Context, except for those identified in clause 7.3.3.1. The following steps are undertaken: 1) The On-Board FRMCS shall... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.4 Procedure upon unsubscription from a channel | Upon invocation of the "/notifications/{dynamicId}/channels/{channel}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to clear the subscription to notification types associated with the requested channel from the list of notification types in the OBAPP Application Context. The following steps are un... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.5 Procedure of notification to an application over a channel | The SSE data field shall be filled with the JSON data structure as passed to the procedure. EXAMPLE: For a successful final answer notification, the JSON data structure would be: { "openSessionFinalAnswerNotif": "success": { "sessionId": <data>, "nextHopIpAddress": <data>, "destApplicationIPAddress": <data> } } The SSE... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.6 Procedure upon subscription to location reporting channel | Upon invocation of the "/notifications/{dynamicId}/channels/location" endpoint with the HTTP POST verb, the On-Board FRMCS is expected to add the notification types associated to the requested channel to the list of notification types in the OBAPP Application Context. The following steps are undertaken: 1) If the locRe... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.7 Procedure to list subscriptions of an application | Upon invocation of the "/notifications/{dynamicId}/channels" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide a list of notifications to which application has subscriptions. If the query is authorized, the On-Board FRMCS shall respond with a 200 (OK) response code as specified in FRMCS FFFIS-7... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.3.8 Procedure to unsubscribe an application from a specific subscription | Upon invocation of the "/notifications/{dynamicId}/channels/{subscriptionId}" endpoint with the HTTP DELETE verb, the On-Board FRMCS is expected to unsubscribe an application from a specific notification subscription. If the query is authorized, the On-Board FRMCS shall respond with a 204 (No Content) response code as ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.4 /versions endpoint procedure | Upon invocation of the "/versions" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide the list of versions it supports. The following steps are undertaken: 1) The On-Board FRMCS shall prepare an API VersionsData data structure with the list of versions supported as specified in FRMCS FFFIS-7950 ... |
7846de44f9b024650e4ec622089d8142 | 103 765-3 | 7.3.5 /keepalive endpoint procedure | Upon invocation of the "/keepalive" endpoint with the HTTP GET verb, the On-Board FRMCS is expected to provide a HTTP-level response to indicate the OBAPP reference point is responsive. The On-Board FRMCS shall respond with a 204 (No Content) response code as specified in FRMCS FFFIS-7950 [5], clause 9.13. ETSI ETSI TS... |
05f8beb7977a67521a875d86df071465 | 103 792 | 1 Scope | The present document defines the functional model including reference points as well as the protocol and procedure for interworking between GSM-R R4 and FRMCS and covers the following services: • Group call. • Emergency group call. • Point-to-point call. • Text messaging Service. |
05f8beb7977a67521a875d86df071465 | 103 792 | 2 References | |
05f8beb7977a67521a875d86df071465 | 103 792 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
05f8beb7977a67521a875d86df071465 | 103 792 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
05f8beb7977a67521a875d86df071465 | 103 792 | 3 Definition of terms, symbols and abbreviations | |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 103 791 [i.12] and the following apply: E.164 SIP-R URI: SIP-R URI which describes an international E.164 address EIRENE SIP-R URI: SIP-R URI which describes an international EIRENE address FA(164): Functional Alias (FA) which takes the form of an E.1... |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.2 Symbols | Void. |
05f8beb7977a67521a875d86df071465 | 103 792 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AMR-WB Adaptative MultiRate-Wide Band CdA Called Address CgA Calling Address CHPC Confirmation of High Priority Call CSC Coding Scheme Code CT Call Type CT5 Call Type 5 ECT Explicit Call Transfer EIR Equ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 4 Services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.1 General | This clause describes the services for interworking between GSM-R and FRMCS 3GPP MC systems supported in the present document. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.2 Group call | This clause describes group call services that are supported for groups defined on the MC system and groups defined on the GSM-R system. The following group call procedures are supported: • Initiation of a group call by a FRMCS user. • Initiation of a group call by a GSM-R user. • Late entry. • Termination of a group c... |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.3 Emergency group call | Emergency group calls, i.e. group calls with pre-emptive priority, are supported for the same cases as described in clause 4.2. |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.4 Point-to-point call | The following point-to-point call procedures are supported: • Initiating a point-to-point call from a user on the GSM-R system to a user on the MC system. • Initiating a point-to-point call from a user on the FRMCS system to a user on the GSM-R system. • Interworking of the media codecs and encryption between GSM-R and... |
05f8beb7977a67521a875d86df071465 | 103 792 | 4.5 Text messaging service | The GSM-R system includes Mobile Stations (MS) capable of performing various types of calls, such as voice and data calls, and also supports text messaging by enabling the transmission of Short Messages (SMs) between mobile stations. EIRENE System Requirements Specification [i.2] specifies that, whenever text messaging... |
05f8beb7977a67521a875d86df071465 | 103 792 | 5 Functional model | |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.1 Functional model description | The present document defines the reference points between the IWF and the FRMCS servers as well as the reference points between the IWF and the GSM-R nodes. Additionally, it defines the functionality of the IWF, which acts as an MC service server connected with the FRMCS MC service server utilizing the IWF-1 or IWF-2 r... |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2 Reference points | |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.0 General | The normative requirements placed on a FRMCS SIP Core are detailed in ETSI TS 103 765-2 [4]. The reference points only need to be derived from IMS specific reference points as shown in Table 5.2.0-1. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 15 Table 5.2.0-1: Proposed mapping of refence points on GSM-R side according to ET... |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.1 Reference point IWF-1 (between the IWF and the MCPTT server) | The IWF-1 reference point, defined between the IWF and the MCPTT server, enables peer-to-peer interconnection between the GSM-R system and the MCPTT system. IWF-1 supports a subset of the MCPTT-3 functionalities as defined in ETSI TS 123 379 [i.6], with some differences detailed in the present document. The IWF-1 inter... |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.2 Reference point IWF-2 (between the IWF and the MCData server) | The IWF-2 reference point, defined between the IWF and the MCData server, enables SDS interconnection between the GSM-R system and the MCData system. IWF-2 supports a subset of the functionalities of MCData-SDS-1 and MCData-SDS-2, as specified in ETSI TS 123 282 [i.7] with some differences as detailed in the present do... |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.5 Reference point IWF-g2 (between the IWF and MGW) | The IWF-g2 reference point, defined between the IWF and the MGW, would enable media plane protocol for voice communication. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 16 |
05f8beb7977a67521a875d86df071465 | 103 792 | 5.2.6 Reference point IWF-g5 (between the IWF and IP-SM-GW) | The IWF-g5 reference point is defined between the IP-SM-GW on the GSM-R side and the IWF. If SIP interfaces are used, the IP-SM-GW on the GSM-R side converts the SMPP MAP protocol to SIP (ISC). |
05f8beb7977a67521a875d86df071465 | 103 792 | 6 Identities and addressing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.0 General | In the present document, the IWF provides network support for interworking between FRMCS and GSM-R for voice and messaging services. The IWF shall provide the following services: • Routing service(s) that can manage addressing. • Identity mapping service(s) that can manage a set of identities. The IWF is connected with... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.1 Identity definitions | From a logical point of view, the IWF performs an identity mapping between the FRMCS reference points IWF-1/IWF-2 and the GSM-R reference points IWF-g1/IWF-g5. Figure 6.1-1 shows the location of the IWF between FRMCS Domains and GSM-R Domains. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 17 Figure 6.1-1: Domains involved in i... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.2 Representation in interworking systems | E.164 SIP-R URIs and EIRENE SIP-R URIs shall be used at IWF-g1 and IWF-g5 to represent E.164 addresses and EIRENE addresses, respectively. MCX IDs and FAs shall be used at IWF-1 and IWF-2, as defined in the 3GPP MC standards. FA(164) and FA(EIRENE) shall be special FAs that are SIP URIs as defined in ETSI TS 103 389 [6... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3 Identity mapping and addressing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.0 General | The IWF shall perform mapping of identities between GSM-R entities and FRMCS entities. The IWF shall be configurable in such a way that enables identity mapping services to be performed. Clause 6.3 specifies: • IWF routing service(s). • IWF identity mapping Service(s). |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1 Management policies for identity mapping and routing | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1.1 General | Within an FRMCS domain, the following provisions shall be done: • An IWF domain shall be defined for interworking with GSM-R: - The IWF domain is used to indicate that call(s) may be routed to another domain by using the IWF service(s). - The IWF domain shall be used by the IWF, in order to indicate to FRMCS entities t... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.1.2 Examples for the changing of the domain in SIP URIs | As specified in clause 6.3.1, the IWF will change the domain of protocol address parameters, so that: • FRMCS entities can address GSM-R entities by using the IWF Domain (which will be changed into a GSM-R Domain by the IWF). • GSM-R entities can address FRMCS entities by using the IMS Domain (which will be changed int... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2 SIP routing services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2.1 GSM-R to FRMCS out-of-dialog SIP requests | GSM-R to FRMCS out-of-dialog SIP requests are out-of-dialog SIP requests that are routed from a GSM-R domain to a FRMCS domain by the IWF. For the purpose(s) of the present document, the following list applies to routing of GSM-R to FRMCS out-of-dialog SIP request(s): • Any out-of-dialog SIP request received at the IMS... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.2.2 FRMCS to GSM-R out-of-dialog SIP requests | FRMCS to GSM-R out-of-dialog SIP requests are out-of-dialog SIP requests that are routed from a FRMCS domain to a GSM-R domain by the IWF. For the purpose(s) of the present document, the following list applies to the routing of FRMCS to GSM-R out-of-dialog SIP request(s): • Any FRMCS to GSM-R out-of-dialog SIP INVITE r... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3 Identity mapping services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.0 General | The IWF identity mapping service(s) shall provide mapping of the following types of identities, and also considering group call criteria: • MC Service ID. • FA. • Group Call Criteria. • MC Service Group ID. Mapping of MC Service ID provides identity mapping between MC Service ID and SIP-R URI. Mapping of FA provides id... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1 Generic procedures for identity mapping | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.0 General | A set of address parameters are subject to a generic identity mapping as specified within this clause. The first decision of generic identity mapping is to determine if the address parameters of a SIP/SDP message are subject to a GSM-R to FRMCS domain transition or subject to a FRMCS to GSM-R domain transition. Based o... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.1 Generic identity mapping for GSM-R to FRMCS SIP messages | For the case of a GSM-R to FRMCS interworking (as defined in cause 6.3.3.1.0) and for each SIP/SDP address parameter subject to generic identity mapping, the following processing steps shall be applied: NOTE: For the case of mapping of GSM-R to FRMCS addresses, the set of addresses subject to mapping can be one of the ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.1.2 Generic identity mapping for FRMCS to GSM-R SIP messages | For SIP messages received by an IWF from an FRMCS domain that have a GSM-R domain as destination (as defined in cause 6.3.3.1.0) and for each protocol address parameter subject to generic identity mapping, one of the following processing steps shall be applied to these parameter(s): 1) MC Service ID If the address para... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2 Mapping of basic address parameters for MCPTT private calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.0 General | The set of basic address parameters applicable for private calls using MCPTT, applying generic address parameter naming as defined in clause 6.2 are: • Called Address. • Calling Address. • Additional Calling Address. • Connected Address. The above set of basic address parameters shall be mapped according to clause 6.3.... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.1 Basic address parameters for GSM-R to FRMCS private calls | For any request detected within the IWF domain for a GSM-R to FRMCS private MCPTT call that is received from a GSM-R domain, analysis as specified in clause 6.3.3.1.1 for the Called Address shall be performed to determine if the MCPTT private call is intended to be established in a FRMCS domain. If the call is not inte... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.2.2 Basic address parameters for FRMCS to GSM-R private calls | If the request for an MCPTT private call is forwarded by the IWF from an FRMCS domain to another domain, then the IWF shall apply one of the following identity mappings to the Called Address, as defined in Table 6.3.3.2.2-1, before the routing services of the IWF take any routing decision. ETSI ETSI TS 103 792 V1.1.1 (... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3 Identity mapping for MCData SDS | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.0 General | The IWF will receive the Text Message from the GSM-R IP-SM-GW and map it to the MCData SDS. In the reverse direction the IWF will map the MCDATA SDS to an Instant Message and send it to the GSM-R IP-SM-GW. The set of basic address parameters applicable for text messaging using MCData SDS, also applying generic address ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.1 Address parameters for GSM-R to FRMCS text messages | For any request detected within the IWF domain for a GSM-R to FRMCS Text Message that is received from a GSM-R domain, analysis as specified in clause 6.3.3.1.1 for the Called Address shall be performed to determine if the Instant Message is intended to be delivered to an FRMCS domain. If the text message is not intend... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.3.2 Address parameters for FRMCS to GSM-R text messages | If the request for an MCDATA SDS message is forwarded by the IWF from an FRMCS domain to a GSM-R domain, then the IWF shall apply one of the following identity mappings to the Called Address, as defined in Table 6.3.3.3.2-1, before the routing services of the IWF take any routing decision. Table 6.3.3.3.2-1: Cases of m... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4 Identity mapping for supplementary services | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.0 General | The identity mapping services of the IWF shall be applicable to the interworking of supplementary services, whenever supplementary identity (address) information is exchanged between an FRMCS domain and a GSM-R domain. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 26 Explicitly listed, these supplementary identities are: • MCP... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.1 Presentation of Functional Number - User To User Information | The mapping of Basic Address Parameters (see clause 6.3.3.2) covers MCPTT IDs and MCDATA IDs in the Called Address parameter and functional aliases (FRMCS FA, FA(164), FA(EIRENE)). The Calling Address is supposed to always carry MCPTT IDs or MCDATA IDs on the IWF-1 reference point (e.g. in the XML element <mcptt-callin... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.2 Call Diversion - Call History Address List | The Call History Address List is transmitted as follows: • At the IWF-g1 reference point, the call history information shall be transmitted within History-Info header fields, according to ETSI TS 103 389 [6]. ETSI ETSI TS 103 792 V1.1.1 (2026-01) 27 • At the IWF-1 reference point, the call history information shall be ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.4.3 Explicit Call Transfer - Connected Address | The Connected Addresses transmitted during the execution of a call transfer service shall be mapped according to the description of generic identity mapping in clause 6.3.3.1. |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5 Mapping of Identities, Criteria and Domains for MCPTT group calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.0 General | MCPTT Group Calls are group calls that are controlled by the Controlling Function of an MCPTT Server beyond the IWF-1 reference point, as seen from the IWF. As described in clause 7, MCPTT Ad-Hoc Group calls can be coupled with GSM-R VGCS/VBS calls, where either the MCPTT Group call invites an MCPTT ID as participant t... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.1 Mapping of basic address parameters for MCPTT group calls | The content of Called Address and Calling Address at the IWF-1 and IWF-g1 reference points is specified in Tables 6.3.3.5.1-1 and 6.3.3.5.1-2. Table 6.3.3.5.1-1: Content of basic address parameters during the setup of FRMCS to GSM-R group calls Address Parameter Content at IWF-1 Content at IWF-g1 Called Address GCRep (... |
05f8beb7977a67521a875d86df071465 | 103 792 | 6.3.3.5.2 Mapping of FRMCS criteria and EIRENE CT5 FN | The MCPTT call control protocol, defined in ETSI TS 124 379 [10] specifies the criteria for determining the participants, that an MCPTT UE shall send when initiating an ad-hoc group call. These criteria are transmitted in the <call-participants-criterias> element in the <anyExt> element of the <mcptt- Params> element o... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7 Group calls | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1 Interworking procedures | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.0 General | This clause contains stage 2 and stage 3 procedures for interworking of group calls between 3GPP MCPTT systems and GSM-R systems. The messages and information elements used in the procedures in this clause are specified in the following documents: • ETSI TS 103 389 [6] for GSM-R. • ETSI TS 123 283 [11] for MCPTT stage ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1 Information flows | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1 Stage 2 information flows | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.1 General | This clause introduces the stage 2 information flows related to the interworking of group calls between MCPTT and GSM-R: • The SIP interface between the MGCF and the IWF is based on implementation of the reference point Mg/Mj as defined by ETSI TS 129 163 [12] and extended by parts of ETSI TS 103 389 [6]. • IWF ringing... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.2 IWF GSM-R IWF ad-hoc group call request | Table 7.1.1.1.2-1 contains the GSM-R IWF group call request information flow. Table 7.1.1.1.2-1: GSM-R IWF group call request Information Element Status Description Called Address M SIP Request-URI, as defined in clause 6.3.3.5. This information element can hold an E.164 SIP-R URI or an EIRENE SIP-R URI, as defined in ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.1.3 IWF GSM-R IWF ad-hoc group call response | Table 7.1.1.1.3-1 contains the GSM-R IWF group call response information flow. Table 7.1.1.1.3-1: GSM-R IWF group call response Information Element Status Description Connected Address O P-Asserted-Identity, as defined in clause 6.3.3.5. This information element can hold an E.164 SIP-R URI or an EIR+ENE SIP-R URI, as d... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.1.1.2 Stage 3 Information flows | For IWF GSM-R group call requests the following shall apply: • For calls from GSM-R to FRMCS: GSM-R VGCS/VBS including a terminating dispatcher representing a group on the FRMCS domain (e.g. CT5 FN) - referenced as terminating dispatcher in the GCR - parameters shall be mapped as follows: - E.164 calling party in PAI (... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2 Group call principles | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1 Group call initiated by a GSM-R user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1 Group call initiated by a GSM-R user interacting with MCPTT group call | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1.1 Stage 2 procedure | Pre-conditions: 1) The Group Call Register (GCR) of the GSM-R system contains an additional entry under terminating dispatchers for a user on the IWF that represents the location defined group on the MCPTT system. Figure 7.2.1.1.1-1 illustrates the procedure for a group call initiated by a GSM-R user interacting with a... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.1.1.2 Stage 3 procedure | Pre-conditions: 1) The Group Call Register (GCR) of the GSM-R system contains an additional entry under terminating dispatchers for a user on the IWF that represents the location defined group on the MCPTT system. 2) The MCPTT server has location criteria defined that can be used to determine the users of an ad-hoc gro... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2 Group call initiated by an MCPTT user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1 Group call setup initiated by MCPTT user interacting with the GSM-R system | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1.1 Stage 2 procedure | Pre-conditions: 1) The configuration on the MCPTT server for the criteria used in the adhoc group call contains an additional entry with an MCPTT ID that represents CT5 numbers on the GSM-R system. 2) The IWF contains configuration data containing the value of an MCPTT ID used for the interworking of adhoc group calls ... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.2.1.2 Stage 3 procedure | Pre-conditions: 1) The configuration on the MCPTT server for the criteria used in the adhoc group call contains an additional entry with an MCPTT user representing the corresponding CT5 number in GSM-R. 2) The IWF contains a configuration containing the value of an MCPTT ID representing the groups on the GSM- R system.... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3 Late entry | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1 Late entry of an MCPTT user | |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1.1 Stage 2 procedure | Pre-conditions: 1) An active group call involving the MCPTT users at MCPTT client 1 and client 2 on the MCPTT system and users on the GSM-R system is in place. Figure 7.2.3.1.1-1 illustrates the procedure for late joining of an MCPTT user into an ongoing group call already established between the MCPTT system and the G... |
05f8beb7977a67521a875d86df071465 | 103 792 | 7.2.3.1.2 Stage 3 procedure | No impact on existing stage 3 procedures. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.