hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.32 Zone Configuration Index | The Zone Configuration Index IE contains the Zone Configuration Index of a zone. Table 7.32-1 Name Presence Type or reference Description Zone Configuration Index M INTEGER (0 to 127) Identifies the configuration of the zone. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.33 Message Type | The Message Type IE contains information used to identify the message. Table 7.33-1 Name Presence Type or reference Description Message Type M INTEGER (0 to 1 023) The following values shall be used: "0" - REGISTRATION REQUEST message "1" - REGISTRATION RESPONSE message "2" - DEREGISTRATION REQUEST message "3" - DEREGI... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.34 Transaction ID | The Transaction ID IE contains information used to identify the specific instance of a procedure which the message belongs to do. Table 7.34-1 Name Presence Type or reference Description Transaction ID M INTEGER (0 to 4 095) Indicates the specific instance of the procedure. Transaction IDs may be reused after the compl... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.35 ELR ID | The ELR ID IE enables the eLC to identify the eLR involved in the message exchange via LSA1. Table 7.35-1 Name Presence Type or reference Description ELR ID M INTEGER (0 to 4 095) Indicates the eLR. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.36 ELC ID | The ELC ID IE enables the eLR to identify the eLC involved in the message exchange via LSA1. Table 7.36-1 Name Presence Type or reference Description ELC ID M INTEGER (0 to 65 535) Indicates the eLC. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.37 VSP ID | The VSP ID IE enables the eLR to identify the VSP involved in the message exchange via LSA1. The VSP identity equal to zero (0) is used to identify all VSPs registered in an eLC and shall not be allocated to identify a specific VSP. Table 7.37-1 Name Presence Type or reference Description VSP ID M INTEGER (0 to 65 535)... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.38 L-ID | The L-ID IE enables the eLR to identify the license or lease involved in the message exchange via LSA1. Table 7.38-1 Name Presence Type or reference Description L-ID M INTEGER (0 to 65 535) Indicates the license or lease. ETSI ETSI TS 103 652-3 V1.1.2 (2021-06) 44 |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.39 Mode of Operation | The Mode of Operation IE is used to identify the detached operation mode. Table 7.39-1 Name Presence Type or reference Description Mode of Operation M ENUMERATED (DOM) Indicates the mode of operation. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.40 eLSA1 Availability in DOM | The eLSA1 Availability in DOM IE indicates activation or deactivation of the eLSA1. Table 7.40-1 Name Presence Type or reference Description eLSA1 Availability in DOM M ENUMERATED (Activate, Deactivate) Indicates the activation or deactivation of the eLSA1 interface. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.41 Result | The Result IE is included in a response message and indicates whether the procedure is successful. Table 7.41-1 Name Presence Type or reference Description Result M ENUMERATED (Successful, Unsuccessful) Indicates the result of the procedure. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.42 Sync ID | The Sync ID IE is used to identify the specific synchronization process. Table 7.42-1 Name Presence Type or reference Description Sync ID M INTEGER (0 to 255) Indicates that the message is part of the synchronization process associated with this ID. Sync IDs may be reused after the completion of the respective synchron... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.43 Sync Zone List | The Sync Zone List IE contains information about the zones received during a synchronization process. Table 7.43-1 Name Presence Type or reference Description Number of zones M INTEGER (0 to 65 535) Identifies the number of zones N received during the synchronization process. If set to "0", it indicates that the follow... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.44 Synched Zone | The Synched Zone IE contains information about a zone received during the synchronization process. Table 7.44-1 Name Presence Type or reference Description Zone ID M 7.47 Identifies the zone ID. Zone Configuration Index M 7.32 Identifies the configuration of the zone. 7.45 Cause The Cause IE indicates the reason for a ... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.46 Cause Details | The Cause Details IE may be used when a Cause IE responds with a value "The request cannot be granted because of not enough available resources". The Cause Details IE identifies what spectrum resources are available for the requested area (allowance zone). ETSI ETSI TS 103 652-3 V1.1.2 (2021-06) 47 Table 7.46-1 Name Pr... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.47 Zone ID | The Zone ID IE is used to identify a zone uniquely over all instances of the LSA1 interface for a given eLR. Table 7.47-1 Name Presence Type or reference Description Zone ID M INTEGER (0 to 16 777 215) Identifies the zone. |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.48 Protocol Version List | The Protocol Version List IE contains information about the protocol versions supported by a protocol endpoint. Table 7.48-1 Name Presence Type or reference Description Number of versions M INTEGER (1 to 63) Identifies the number N of versions supported by the endpoint. Protocol Version 1 M 7.49 Supported protocol vers... |
8d636e0ef003ee832fdbb78633d5f228 | 103 652-3 | 7.49 Protocol Version | The Protocol Version IE is used to identify the protocol version. Table 7.49-1 Name Presence Type or reference Description Protocol Version M INTEGER (1 to 255) Indicates the protocol version. ETSI ETSI TS 103 652-3 V1.1.2 (2021-06) 48 Annex A (informative): Detached Operation Mode Scenarios and Workflow Typical use ca... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 1 Scope | The present document defines the IP based signaling and media interfaces between any two GSM-R Core networks of a set of GSM-R Core networks that share a GIRA and that agree to interconnect via IP based technology. Furthermore it defines the IP based signaling and media interface between any GSM-R Core network that wan... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 2 References | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 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... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 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... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 3 Definition of terms, symbols and abbreviations | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 3.1 Terms | For the purposes of the present document, the following terms apply: downlink path: IP path from a hub to a GSM-R Core network, optionally traversing one or more transit networks end-to-end path: IP path from one GSM-R Core network to another GSM-R Core network, optionally traversing one or more transit networks or eve... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 3.2 Symbols | Void. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Address Complete Message ANM Answer message AoCC Advice of Charge (Charging) AoCI Advice of Charge (Information) BAIC Barring All Incoming Calls BAOC Barring All Outgoing Calls BGP Border Gateway Protocol BICC Bearer Independant Call Contr... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 4 Reference system architecture | The reference system architecture describes a layered network, which can be used to display the different use cases of a GIRA, in case that at least one of both GSM-R Core networks connects to the other via IP based transport. Use Case I: Both networks use IP based transport to connect to each other (IP Interconnect). ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5 Interface functionality | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.0 General description | This clause specifies functional requirements for the IP Interconnect interfaces, sorted by domain (CS domain, PS domain, IMS domain, etc.) and by service. ETSI ETSI TS 103 672 V1.1.1 (2020-12) 15 The IP Interconnect interfaces shall be used to transport following traffic of the CS domain: • SIP-I traffic for call cont... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1 CS domain - transport of SIP-I, SCCP/MTP3, RTP/RTCP | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.0 General information | Clause 5.1 establishes the requirements about how the IP paths established by clause 5.0 shall be used within the CS domain: • Clauses 5.1.1 to 5.1.4: Common requirements for Use Case I and Use Case II. • Clause 5.1.5: Requirements specific to Use Case II. The paths shall be used for the transport of traffic specific t... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.1 CS bearer services | EIRENE SRS [1] specifies in clause 2.3.1, table 2-2, which Bearer Services have to be supported in GSM-R networks. Clauses 5.1.1, 6.4.1.1 and 7.4.1.1 deal with the requirements and realization of those bearer services, with the exception of GPRS and eGPRS. The real-time transport protocol RTP shall be used for the tran... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2 Teleservices | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2.0 General | EIRENE SRS [1] specifies in clause 2.2.1, table 2-1, which GSM Teleservices have to be supported in GSM-R networks. The headings of the sub-clauses of clause 5.1.2, of clause 6.4.1.2 and of clause 7.4.1.2 have been setup according to the rows of that table. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2.1 Speech (telephony, emergency calls) | Roaming and Handover shall be available by the MAP mobility management protocol as specified in ETSI TS 129 002 [5] for inbound and outbound roamers of GSM-R Core network A and GSM-R Core network B. Every SS7 traffic between the two GSM-R Core networks, i.e. MTP3, SCCP, MAP, CAP and so on (except ISUP), shall be routed... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2.2 Short Message Service | Interworking of SMS MT with SMS MO shall be possible by routing MAP traffic between GSM-R Core network A and GSM-R Core network B. MAP is specified at ETSI TS 129 002 [5]. NOTE: Routing of SS7 traffic via the IP Interconnect interfaces is already required generally by clause 5.1.2.1. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2.3 Facsimile transmission | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.2.4 Voice Group Service (VGCS, VBS) | The support of VGCS/VBS needs an international connection to support international group calls, i.e.: • Connecting an anchor MSC with a relay MSC of an international GSM-R network. • A VGCS/VBS including international dispatchers. All these use cases are supported via the IP Interconnect interfaces and via the hub, if ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3 GSM supplementary services | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.0 General | EIRENE SRS [1] specifies in clause 2.4.1, table 2-3, which GSM Supplementary services are mandatory for GSM-R networks and which are not. The headings of the sub-clauses of clause 5.1.3, of clause 6.4.1.3 and of clause 7.4.1.3 have been setup according to the rows of that table. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.1 CLIP / CLIR | Interworking of CLIP / CLIR information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C, with following changes and clarifications. Since CLIP is mandatory according to EIRENE SRS [1], but CLIR is not, hence the support of CLI... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.2 CoLP / CoLR | Interworking CoLP / CoLR information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C, with following changes and clarifications. Since CoLP is mandatory according to EIRENE SRS [1], but CoLR is not, hence the support of CoLR i... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.3 Call Forwarding (CFU, CFB, CFNRy, CFNRc) | Interworking Call Forwarding information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C, with following changes and clarifications. Since CFU and CFB are mandatory according to EIRENE SRS [1], but CFNRy and CFNRc are not, hen... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.4 Call Waiting (CW) | Interworking Call Waiting information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. ETSI ETSI TS 103 672 V1.1.1 (2020-12) 21 |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.5 Call Hold (HOLD) | Interworking Call Hold information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. NOTE: Recommendation ITU-T Q.1912.5 [3] assumes that possible hold announcements are applied at the same network, at which the subscriber is a... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.6 Multi Party service (MPTY) | Interworking information about Manual Conferences (CONF or 3PTY) at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.7 Closed User Group (CUG) | Interworking CUG information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.8 Advice of Charge (Information) (AoCI) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.9 Advice of Charge (Charging) (AoCC) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.10 Barring (BAOC, BOIC, BOIC-exHC, BAIC, BIC-Roam) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.11 Unstructured Supplementary Service Data (USSD) | During roaming scenarios, the USSD, e.g. for Follow Me service, may traverse the IP Interconnect interface. NOTE: The routing of SCCP and MTP3 traffic at the IP Interconnect interface is already required by clause 5.1.2.1. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.12 Follow me | During roaming scenarios, the USSD for Follow Me service, may traverse the IP Interconnect interface. NOTE: The routing of SCCP and MTP3 traffic at the IP Interconnect interface is already required by clause 5.1.2.1. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.13 Sub-addressing | Interworking SUB information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.14 eMLPP | Interworking MLPP information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. ETSI ETSI TS 103 672 V1.1.1 (2020-12) 22 |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.15 ECT | Interworking ECT notifications at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C, with following changes and clarifications. Since ECT is optional according to EIRENE SRS [1], hence the support of ECT notifications is up to bila... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.16 Completion of Calls to Busy Subscribers (CCBS) | Interworking CCBS information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C, with following changes and clarifications. Since CCBS is optional according to EIRENE SRS [1], hence the support of CCBS is up to bilateral agreeme... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.3.17 User-to-User Signalling (UUS1) | Interworking User to User information at the boundary of GSM-R Core networks via IP Interconnect interfaces shall be done according to Recommendation ITU-T Q.1912.5 [3], profile C. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4 Railway specific services | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.0 General | EIRENE SRS [1] specifies in clause 2.5.1, table 2-4, which Railway Specific Services are supported in GSM-R networks. The headings of the sub-clauses of clause 5.1.4, of clause 6.4.1.4 and of clause 7.4.1.4 have been setup according to the rows of that table. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.1 Functional addressing | Functional addressing shall be supported by the support of EIRENE numbers at the IP Interconnect interfaces (already required by clause 5.1.2.1) and by the UUS1 (see clause 5.1.3.17). |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.2 Location dependent addressing | Functional addressing shall be supported by the support of EIRENE numbers at the IP Interconnect interfaces (already required by clause 5.1.2.1) and by the UUS1 (see clause 5.1.3.17). |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.3 Shunting mode | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.4 Multiple driver communications | The MPTY service shall be supported at the IP Interconnect interfaces (see clause 5.1.3.6). |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.4.5 REC / eREC | REC and eREC shall be supported by the support of eMLPP (clause 5.1.3.14), of VGCS/VBS (clause 5.1.2.4) and of UUS1 (see clause 5.1.3.17) at the IP Interconnect interfaces. ETSI ETSI TS 103 672 V1.1.1 (2020-12) 23 |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.5 IP/TDM interworking for the CS domain | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.5.0 Introduction | Clauses 5.1.1 to 5.1.4 describe the common requirements for Use Case I and Use Case II that are applicable to the IP Interconnect and to the interworking at the edges of the GSM-R Core Networks. Use Case I: Normal: GSM-R Core A --- IP Interconnect --- GSM-R Core B In case of use case I a fall back should not be necessa... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.5.1 Interworking SIP-I with ISUP, Interworking SS7 | Teleservices + Supplementary Services GSM Teleservices and GSM Supplementary Services shall be interworked at the hub between SIP-I protocol and ISUP protocol according to ETSI TS 129 164 [8], based on ETSI TS 129 1633 [i.5], based on Recommendation ITU-T Q.1912.5 [3], profile C, in case of Use Case II. Furthermore, th... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.1.5.2 Interworking the bearer services | All bearer services that are routed over the hub shall be interworked at the hub, in case of Use Case II. For this purpose, the speech data or the clearmode data from the RTP payload shall be interworked with the 64 kbit/s channels at the TDM Interconnect interfaces. Interworking of DTMF is required by clause 5.1.2.4. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.2 PS domain - transport of GTP-C, DNS, GTP-U | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.2.1 PS bearer services | To establish connectivity between SGSN and GGSN, GPRS Tunnelling Protocol shall be used according to clause 8.5 of UIC REFERENCE O-8350 2.0 [4]. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.2.2 DNS services | The GPRS Domain Name System (GNS) shall be utilized to resolve APNs. If the local GNS is unable to resolve the DNS APN request, the local DNS shall contact the ROOT DNS operated by the IP-hub/IPX, as specified by clause 8.5 of UIC REFERENCE O-8350 2.0 [4]. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 5.2.3 IP/TDM interworking for the PS domain | Interworking of SCCP/MTP3 is handled in clause 5.1.5.1 completely, i.e. for the CS domain and for the PS domain. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6 Signalling interface | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.0 General description | The signalling interface (clause 6) and the media interface (clause 7) of the IP Interconnect interfaces shall be used to transport: • SIP-I traffic for call control and maintenance; • RTP/RTCP traffic for the handling of the bearer; • SCCP / MTP3 / M2PA and SCCP / M3UA traffic for the handling of mobility management, ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.1 Network layer protocol | Clause 6.1 specifies the common properties of the network protocol IP, which is used at the media interface (see clause 7) and at the signaling interface (clause 6). The key characteristics of the external SIP-I network are specified in ETSI TS 129 164 [8], clause 4.2, with following changes and clarifications regardin... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.2 Transport layer protocols | Clause 6.2 specifies the properties of the transport protocols UDP, TCP and SCTP, as they are used at the signaling interface and at the media interface (UDP is also used at the media interface). The key characteristics of the external SIP-I network are specified in ETSI TS 129 164 [8], clause 4.2, with following chang... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.3 Signalling protocols | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.3.1 SIP-I | SIP-I - as it shall be used at IP Interconnect interfaces - is specified by Recommendation ITU-T Q.1912.5 [3], profile C -, with refinements by ETSI TS 129 163 [i.5], by ETSI TS 129 164 [8] and by the present document. NOTE 1: Not all features of the ISDN can be currently transported via the SIP protocol, unless implem... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.3.2 SS7 | If Figure 12 is applied to SS7 traffic, then the term "network connection" can only mean: • An SCTP association - M2PA or M3UA is transported over SCTP; and nothing else. The SCTP association is then equivalent to an M2PA link according to IETF RFC 4165 [10], which is used by the MTP3 to transmit SS7 messages from one ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4 Interface functionality to signalling interface mapping | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1 CS domain - transport of SIP-I, SCCP/MTP3 | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.1 CS bearer services | The Bearer Services are actually provided by the media interface (see clause 7), however the used RTP sessions shall be setup, torn down and maintained by means of the signalling plane. The Session Initiation Protocol (SIP) carries Session Description Protocol (SDP) information therefore, which shall be used by the MGW... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2 Teleservices | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2.0 General | EIRENE SRS [1] specifies in clause 2.2.1, table 2-1, which GSM Teleservices have to be supported in GSM-R networks. The headings of the sub-clauses of clause 5.1.2, of clause 6.4.1.2 and of clause 7.4.1.2 have been setup according to the rows of that table. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2.1 Speech (telephony, emergency calls) | 6.4.1.2.1.1 Roaming and handover MAP and CAP traffic shall be routed by the STP functions of the hub or of the GSM-R Core networks via E2E paths or via UL/DL paths, in order to support mobility management (Location Update, Insert Subscriber Data, Prepare Handover, etc.) and other services during roaming scenarios (USSD... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2.2 Short Message Service | MAP traffic shall be routed by the STP functions either via E2E paths or via UL paths and DL paths, between GSM-R Core network A and GSM-R Core network B, in order to support Short Message Service (Interworking SMS MT with SMS MO). General information about MAP can be found in ETSI TS 129 002 [5]. Clause 6.3.2 defines ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2.3 Facsimile transmission | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.2.4 Voice Group Service (VGCS, VBS) | Transport of inband DTMF information shall be supported at the media interfaces of the IP Interconnect interfaces, as described in clause 7.4.1.2.4. If the interface partners agree, then the SIP INFO method may be used at the signalling interfaces of the IP Interconnect interfaces, according to the syntax defined at ET... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3 GSM supplementary services | |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.0 General | EIRENE SRS [1] specifies in clause 2.4.1, table 2-3, which GSM Supplementary services are mandatory for GSM-R networks and which are not. The headings of the sub-clauses of clause 5.1.3, of clause 6.4.1.3 and of clause 7.4.1.3 have been setup according to the rows of that table. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.1 CLIP / CLIR | Recommendation ITU-T Q.1912.5 [3] describes the transport of CLIP / CLIR information in SIP INVITE messages (with embedded ISUP IAM). Appendix B.1 and clause 6.1.3.6 of [3], profile C - shall be applied at the O-IWU and at the I-IWU, when CLIP / CLIR information is interworked between BICC/ISUP and SIP-I at the edge of... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.2 CoLP / CoLR | Recommendation ITU-T Q.1912.5 [3] describes the transport of CoLP / CoLR information in SIP INVITE messages (with embedded ISUP IAM) and SIP 200 OK messages (with embedded ISUP CON or ISUP ANM). Appendix B.2 of [3], profile C - shall be applied at the O-IWU and at the I-IWU, when CoLP / CoLR information is interworked ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.3 Call Forwarding (CFU, CFB, CFNRy, CFNRc) | Recommendation ITU-T Q.1912.5 [3] describes the transport of Call Forwarding information in SIP INVITE messages (with embedded ISUP IAM) and SIP 183 Session Progress messages (with embedded ISUP CPG). Appendix B.6 of [3], profile C - shall be applied at the O-IWU and at the I-IWU, when Call Forwarding information is in... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.4 Call Waiting (CW) | Recommendation ITU-T Q.1912.5 [3] describes the transport of Call Waiting information in SIP 180 Ringing messages and SIP 183 Session Progress messages (with embedded ISUP ACM or ISUP CPG), in addition to an optional call waiting announcement, which can be transported via the media interface within the stream of early ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.5 Call hold (HOLD) | Recommendation ITU-T Q.1912.5 [3] describes the transport of Call Hold information in SIP INVITE messages and SIP UPDATE messages (with embedded ISUP CPG messages), in addition to optional call hold announcements, which can be transported via the media interface within the stream of media. Appendix B.9 of [3], profile ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.6 Multi Party service (MPTY) | Recommendation ITU-T Q.1912.5 [3] describes the transport of Manual Conferencing information in SIP messages (with embedded ISUP CPG messages). Appendices B.12 and B.13 of [3], profile C - shall be applied at the O-IWU and at the I-IWU, when Manual Conferencing information is interworked between BICC/ISUP and SIP-I at ... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.7 Closed User Group (CUG) | Recommendation ITU-T Q.1912.5 [3] describes the transport of CUG information in SIP INVITE messages (with embedded ISUP IAM messages). Appendix B.14 of [3], profile C - shall be applied at the O-IWU and at the I-IWU, when CUG information is interworked between BICC/ISUP and SIP-I at the edge of the GSM-R Core network o... |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.8 Advice of Charge (Information) (AoCI) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.9 Advice of Charge (Charging) (AoCC) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.10 Barring (BAOC, BOIC, BOIC-exHC, BAIC, BIC-Roam) | N/A. |
c944c4c8dc93d999be762098d3598962 | 103 672 | 6.4.1.3.11 Unstructured Supplementary Service Data (USSD) | During roaming scenarios, the USSD, e.g. for Follow Me service, may traverse the IP Interconnect interface. NOTE: The routing of SCCP and MTP3 traffic at the IP Interconnect interface is already defined by clause 6.4.1.2.1.1. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.