hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
83467b4cecd63b9b30ec88effa5306da | 103 152 | 5.3.4 Interface to the ITS-S security entity | The MCD basic service may exchange information with the ITS-S security entity via the interface IF.SEC as illustrated in Figure 3. NOTE: Specifications of the SF-SAP and the corresponding protocol are out of scope of the present document. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6 Multimedia Content Dissemination | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1 Multimedia content dissemination concept | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1.1 Introduction | An MCDM may be used by various ITS-S applications for different purposes. For some applications it could be necessary to link the multimedia content delivery to some other messages, e.g. the signaling of an obstacle on the road. Data Requirement (see note 3) Remarks GN communication profile As defined in ETSI EN 302 63... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1.2 Request / Event Identification | If the MCD basic service segments and reassembles the MCDM, the MCD request issued by the application shall be uniquely identified with the actionID generated by the MCD Basic Service in order to ensure the consistent units reassembly at the receiving ITS-S. So, in that circumstance, a unique identifier shall be used t... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1.3 Repetition of the MCDM | An MCDM is transmitted to the destination specified in the application request. This MCDM can be repeated according to the application requirements. Such repetition could be justified to ensure that a minimum number of destinations are receiving the MCDM in spite of packet lost due to the length of the message or becau... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1.4 Update of the MCDM | The parameter referenceTime is the identifier for MCDM update referring to a specific actionID. The referenceTime represents the time at which an MCDM is generated by the MCD basic service, after receiving the application request. For each MCDM update, the referenceTime shall be updated and the value shall be greater t... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.1.5 Segmentation | Segmentation of an MCDM by the MCD basic service may be needed when the segmentation is not supported by the lower communication layers or it does not intend to rely on the lower layer for the segmentation. When an ITS-S application requests MCDM dissemination to the MCD basic service, it may indicate an access layer t... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.2 MCDM dissemination constraints | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.2.1 General confidence constraints | Specified data confidence constraints may apply to some data provided in the MCDM, depending on the detection capabilities of the ITS-S, such as position accuracy constraints, time accuracy constraints and event detection quality constraints when relevant. The confidence constraints are presented in the data elements a... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.2.2 General security constraints | Security header is not included in MCDM. NOTE: The detailed specifications of the MCDM security mechanism is out of the scope of the present document. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 6.2.3 General priority constraints | The MCDM priority is defined according to the class of application requesting the service. Priority information is provided in the PCI across the OSI layer. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7 MCDM format specification | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1 General structure | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.1 Overview | An MCDM is segmented into a certain number of units according to packet size limits rules provided by the selected access layer. The first unit to be transmitted includes a management container enabling the linkage of transmitted successive units of the same MCDM. The first MCDM ITS PDU includes: • The ITS PDU header w... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.2 ITS PDU header | The ITS PDU header shall be as specified in ETSI TS 102 894-2 [3]. Detailed data presentation rules of the ITS PDU header in the context of MCDM is specified in Annex A and clause B.9. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.3 MCDM management container | The MCDM management container includes information required for the MCD management and the operation of the MCD protocol, the format of the multimedia, the link to an actionID of DENM, etc. The container shall include data as specified in Annex A and clause B.14 of the present document. The syntax and semantic specific... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.4 MCDM situation container | The MCDM situation container includes information describing the event that the provided multimedia content refers to. The container shall include data as specified in Annex A and clause B.27 of the present document. The syntax and semantic specifications of DE and DFs of the container shall be as specified in Annex B ... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.5 MCDM location container | The MCDM location container describes the location of the event that the provided multimedia content refers to. The container shall include data as specified in Annex A and clause B.13 of the present document. The syntax and semantic specifications of DE and DFs of the container shall be as specified in Annex B of the ... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.6 MCDM application container | The MCDM application container contains data elements which are specific to the application. The container shall include data as specified in Annex A and clause B.3 of the present document. The syntax and semantic specifications of DE and DFs of the container shall be as specified in Annex B of the present document. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.1.7 MCDM multimedia container | The MCDM multimedia container contains the multimedia content describing an event. This container comprises multimedia data unit(s) which size(s) and type(s) is (are) specified in the management container. The container shall include data as specified in Annex A and clause B.20 of the present document. The syntax and s... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.2 MCDM format and decoding rules | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.2.1 Common data dictionary | The MCDM format makes use of the data dictionary as defined in ETSI TS 102 894-2 [3]. Where applicable, DEs and DFs that are not defined in the present document shall be imported from the common data dictionary as specified ETSI TS 102 894-2 [3]. Detailed descriptions of all DEs and DFs in the context of MCDM are prese... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 7.2.2 MCDM data presentation | Unaligned packet encoding rules (PER) as defined in Recommendation ITU-T X.691/ISO/IEC 8825-2 [4] shall be used for the MCDM encoding and decoding for all MCDM containers, excepted for multimedia containers. The ASN.1 representation of the MCDM shall be as specified in the normative Annex A of the present document. Con... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8 Protocol operation of the MCD basic service | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.1 Introduction | This clause specifies the protocol operations of the MCD basic service for two main roles: • Originating ITS-S operation (clause 8.2). • Receiving ITS-S operation (clause 8.3). The specification of the protocol operation is organized in three parts: 1) Protocol data setting rules specify the setting of the relevant par... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.2 Originator ITS-S operation | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.2.1 Protocol data setting rules | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.2.1.1 General requirements | The data setting for the originator ITS-S operation shall be as specified in Annex B. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.2.1.2 actionID | The actionID shall be generated by the application. It shall be updated when the stationID is updated. NOTE: An application may request the blocking of pseudo change if it considers that the stationID should remain unchanged among different segmentation. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.2.2 General protocol operation | The protocol operation is illustrated in Figure 5. Figure 5: General protocol operation of the originator ITS-S ETSI ETSI TS 103 152 V2.1.1 (2019-11) 22 Upon reception of a request from ITS application via the interface IF.MCD.1, the MCD basic service shall execute the following operations: 1) Process the application r... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3 Receiver ITS-S operation | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3.1 Protocol data setting rules | The data setting for the receiver ITS-S operation shall be as specified in Annex B. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3.2 General protocol operation | Upon reception of an MCDM, the MCD basic service shall execute the following operations: 1) Verify if the received MCDM is relevant to one local application, e.g. the logical entity or the peer is locally recognized. 2) Decode the received ITS–PDU. 3) Re-assemble the received multimedia contents in a consistent way reg... |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3.3 Exception handling | |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3.3.1 General requirements | The receiver ITS-S shall apply the exception handling rules specified in clause 8.3.3.2. |
83467b4cecd63b9b30ec88effa5306da | 103 152 | 8.3.3.2 MCDM decoding exception | If the received MCDM cannot be decoded by the MCD basic service or there is not enough memory to store the enough portion of the multimedia content data (when it is non-real time content), the operation shall stop, discard the MCDM and wait for a next MCDM or timer event. ETSI ETSI TS 103 152 V2.1.1 (2019-11) 24 Annex ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 1 Scope | The purpose of the present document is to describe and define the XML based low profile information service "Journaline®". Journaline is a text based data application highly optimized for digital broadcast systems such as DAB (Digital Audio Broadcasting [1]) and DRM (Digital Radio Mondiale [3]). The present document de... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI EN 300 401: "Radio Broadcasting Systems; Digital... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 3 Definitions, abbreviations and conventions | |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: broadcaster/encoder: instance that encodes and provides a Journaline service content section: part of a JML object after the header section that carries the useful content DS payload: block of data contained in escape sequences of type... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CRC Cyclic Redundancy Check DAB Digital Audio Broadcasting DRM Digital Radio Mondiale ID IDentifier IPA International Phonetic Alphabet JML Journaline Markup Language LSB Least Significant Bit MOT Multimedia Object Transfer MSb Most Significan... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 3.3 Conventions | All numerical values shall be encoded as MSB-first and MSb-first (MSB: Most Significant Byte, MSb: Most Significant bit). Hexadecimal numbers are preceded by the string "0x", i.e. 0x20 is equivalent to 2016 (hexadecimal) or 3210 (decimal). All text characters (including all textual parameter values) shall be encoded as... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4 Overview | Journaline is a text based information service for digital radio, optimized for simple data aggregation and re-use, as well as highly efficient broadcast transmission. It supports the widest range of receiver types, from low-cost solutions with a small text display up to high-end receivers with graphical user interface... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.1 JML objects | Each piece of information (i.e. every menu, news article, ticker message, etc.) is transmitted to the receiver as a self- contained and self-describing "JML object". To minimize the decoder footprint in the receiver, the receiver does not need to build or store any overall hierarchy or index information to render a JML... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2 Types of JML objects | JML ("Journaline Markup Language"), an XML based binary coded content representation, structures a JML object's content into blocks of information like title, body text, menu items, etc. Journaline currently specifies 4 types of JML objects: • Menus. • Plain text messages. • Title-only messages. • List messages. These ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2.1 Menu object | A JML object of type menu ("menu object") consists of a title block followed by a list of link items. Link items consist of a visible label plus a reference to another JML object. The user must be able to navigate through the list of link items and select one of them. If the user activates one of the provided links, th... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2.2 Message objects | |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2.2.1 Plain text message | Plain text messages consist of a title block followed by a block of body text. This type of JML object is intended for the presentation of longer messages. When presented to the user, the title text and the following body text should be rendered on the screen with automatic line wrapping. The user must be able to acces... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2.2.2 Title-Only message | Title-Only messages consist of one title block. The intended functionality is that of an automatically updated news ticker. The title text should be rendered on the screen with automatic line wrapping. Whenever possible, the full text should be visible on screen at once. The user must be able to access the full text in... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.2.2.3 List message | List messages consist of a title block and a list of content lines. Their purpose is to present information in list form (like sports results, stock market information, etc.) in an ordered fashion. The title block may remain on screen even if the user scrolls through the lines of information in the body section. Column... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 4.3 JML object hierarchy | The logical structure of a Journaline service is presented to the user as a tree of menus, sub-menus and messages. All JML objects that form a Journaline service can be distinguished by their unique object ID. A Journaline service must at least comprise one JML object with the object ID value 0x0000, the "root object".... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5 JML object - format specification | |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.1 Overview | Every JML object is self-descriptive. No external information (like filename or type specification) is required to reference and access a JML object and to present it to the user. An JML object consists of the "header section" followed by the "content section". The size of a JML object is limited to 4 092 bytes. This s... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.2 Header section | The header section of a JML object consists of a mandatory "standard header" and an optional "extended header". The standard header comprises the object ID and the object description. The presence of an extended header is indicated as part of the service signalling (see clause8.1.2). If present, it has an equal size fo... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3 Content section | The content section of a JML object contains text information to be presented on screen, and may contain escape sequences to implement extended functionality. The text information carried in the content section is formatted according to [7] in UTF-8 encoding. The content section of every JML object is structured by JML... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3.1 JML codes | An JML object's content section is divided into logical blocks of information (e.g. title, body text) by JML codes. Every block is started with a type specific JML code and ended by: • the JML code "end", • the occurrence of another JML code (starting a new block and thereby implicitly ending the previous), or • the en... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3.2 Escape Sequences | An JML object's content section may carry any number of escape sequences to introduce text formatting information and rendering hints (e.g. highlighted text, preferred line breaks, etc.) as well as additional functionality. A receiver is free to evaluate the content and meaning of escape sequences. If a receiver is not... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3.2.1 Escape sequence 'extended codes' | Extended codes allow the extension of the range of available escape sequence codes by another 256 values. If an 'extended code' exists in a "begin" and an "end" version (e.g. to signal the start and end of a special formatting rule), then the same extended code value is used: To start the sequence it is preceded by the... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3.2.2 Escape sequence "data section" structure and content | Data sections are special multi-byte escape sequences that allow the insertion of extended signalling or binary data to an object's content section, while ensuring full backwards compatibility to any Journaline receiver that cannot interpret the Data section's content. Data sections shall completely be discarded by a r... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 5.3.2.3 Data section "general link target" structure and content | The data section's DS type value 0x03 defines a general link target, i.e. a target that may be presented/activated if the user explicitly request to proceed ("hot button" for user interaction). General link targets may be defined for all types of JML objects. The availability of any general link target for the currentl... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6 Management data | Management data can be broadcast in parallel to the JML objects described in the previous clause. Management data provides additional information to the receiver that for example supports advanced management of JML objects on the receiver side. Note that JML objects (see clauses 4 and 5) are fully self-describing and t... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6.1 General rules | Management data is sent in blocks of information. For a management data block the same restrictions as for JML objects apply: • Every block of management data is self-contained and self-describing. • Every block of management data is limited to 4 092 bytes. • Every block of management data may be compressed, but shall ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6.2 TOC - "Table of Contents" | |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6.2.1 Overview | Blocks of management data carrying TOC ("Table Of Contents") information are called "TOC blocks". They are intended to support the receiver's caching strategy by listing all JML objects currently broadcast in the Journaline service along with their revision. Each description of a JML object is called "TOC entity". A re... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6.2.2 TOC block layout | A TOC block consists of: • the mandatory TOC standard header; followed by • the optional TOC extended header; followed by • the mandatory list of TOC entities (each TOC entity describing one JML object). Every TOC block has the following layout. Parameters of the TOC standard header: • Management data block type 8 bits... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 6.2.3 TOC block transmission | If more than one TOC block is required to carry the full list of TOC entities, the TOC content may be split up in multiple TOC fragments. In this case multiple TOC blocks will be sent in carousel mode. In case of TOC fragmentation the following rules shall apply: • Each TOC block may be sent at any time in any order at... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7 Expected receiver behaviour | Some general rules apply to Journaline compliant receivers. |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.1 Mandatory functionality | Support for the following functionality is a minimum requirement for a Journaline compliant receiver: • The standard header of a JML object must fully be interpreted. If the extended header is present and its content cannot be interpreted, the extended header shall be discarded. • Deflate decompression for the content ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2 Recommended functionality | A Journaline compliant receiver should support as much of the Journaline functionality as possible according to its screen and user interface capabilities. A Journaline compliant receiver does not need to evaluate escape sequences or management data, with the exceptions stated in clause 7.1. The following behavioural d... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.1 User history | The receiver should keep a record of all object IDs traversed by the user from the root object (object ID 0x0000) or an alternative point of entry object ID (on initial access of the Journaline service) to the currently presented JML object (the history path). In this way it can easily provide a "back to previous menu"... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.2 Content update behaviour | An update to a cached version of a JML object (with identical object ID) can for example be identified by a different revision index or object size. If a JML object with a certain object ID is currently presented to the user when an updated version is received, it should be signalled to the user that an updated version... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.3 Reception status indication | If the user selects a link item of a menu object which points to a JML object that is not yet available in the receiver's cache, the user may need to wait for the target JML object's next reception. This may take some time and should be indicated to the user (e.g. by presenting a "receiving - please wait" text or icon)... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.4 Favourites functionality | The "favourites" functionality greatly enhances the Journaline functionality perceived by the user by enabling the user to store certain JML objects for quick and direct future access. This storage does not refer to the content of the JML object, but to its object ID, i.e. when recalling the favourite, then the current... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.5 Object caching strategy | A Journaline compliant receiver does not need any caching support to present a fully functional Journaline service to the user. Only the currently presented JML object must be decoded (and possibly decompressed) in memory before being presented on screen. Whenever the user requests to proceed to a different JML object ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 7.2.6 Support for text to speech engines | Journaline as a low-profile text based information service is an ideal basis for text-to-speech synthesis on sophisticated high-end receivers. Text-to-speech guiding information is optionally available in a JML object in form of data section escape sequences (see clause 5.3.2.2). • "Default language" defines the genera... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 8 Data application definition | |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 8.1 Transport in DAB - Digital Audio Broadcasting | A Journaline service can be broadcast as a user application via DAB - Digital Audio Broadcasting (see [1]). |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 8.1.1 Data transport | A Journaline service component can be broadcast as PAD as part of the audio stream or in a packet mode subchannel. Both transmission modes can be freely mixed on the same multiplex. It is highly recommended for every receiver supporting the Journaline service component to be able to decode both transport modes. If the ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 8.1.2 User application signalling | The following information shall be used to signal the DAB data application "Journaline": The "user application type", signalled in figure 0/13 shall be set according to the table entry in [2]) for "Journaline". The "user application data" field shall have the following structure: • Version 8 bits. • Length of extended ... |
9d982214be3c7410e2ea0fb1241c159b | 102 979 | 8.2 Transport in DRM - Digital Radio Mondiale | Journaline can be broadcast via DRM - Digital Radio Mondiale (see [3]), as a data service component. The data application Journaline is signalled in SDC data entity 5 "application information data entity" (see [3], clause 6.4.3.6). It may, in addition, be signalled in the FAC "application identifier" (see [3] clause 6.... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 1 Scope | The present document describes the GSM-R Core Network Redundancy which is based on several features described in ETSI/3GPP Technical Specifications. In particular these features are: - Intra-domain connection of RAN nodes to multiple CN nodes (RANflex). - Coexistence of VGCS/VBS and RANflex. - GCSMSC and GCR Redundancy... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 2 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 reference document (including any amendments) applies. Referenced documents which ar... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EN 301 515 (V2.3.0): "Global System for Mobile communication (GSM); Requirements for GSM operation on railways". [i.2] ETSI TS 102 281: "Railways... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 3 Definitions and abbreviations | |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Mobile-service Switching Center (MSC): CN node which might be a single Mobile-switching Center entity or the couple MSC-Server + Media Gateway RANflex: feature "Intra-domain connection of RAN nodes to multiple CN nodes" which has been ... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: BSC Base Station Controller CN Core Network CS Circuit Switched EIRENE European Integrated Radio Enhanced Network GCR Group Call Register GCSMSC Group Call Serving MSC GSM-R Global System for Mobile communication for Railways applications IMSI... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 4 General description | |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 4.1 Basic concept | Railway traffic management is a safety and quality of service critical related operation; therefore, redundancy in the core network is required in order to cope with MSC single outages. This redundancy functionality is required in case of unplanned external events (as e.g. earthquakes, fire, terrorist attacks) as well ... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 4.2 Technical Requirements | This list provides a (non-exhaustive) set of technical requirements: - The basic requirement of the GSM-R Core Network Redundancy is the ability to reach more than one MSC from the same geographical location. - GSM-R Core Network Redundancy is required for point to point calls and for voice group calls and voice broadc... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 4.3 System Architecture | In principle the GSM-R Core Network Redundancy as described in the present document is architecture neutral, i.e. it is applicable to either Rel-99 CN architecture or Rel-4 CN architecture. However in order to reach the high QoS requirements of GSM-R networks the GSM-R Core Network Redundancy is assumed to be implement... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5 Components of GSM-R Core Network Redundancy | As explained in clause 4.1, the GSM-R Core Network Redundancy is a combination of several features described in 3GPP/ETSI Technical Specifications. This clause contains one clause for each of these features containing a high level description for the sake of reminder and a list of the references describing the feature ... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5.1.1 Main concept | RANflex is answering the need for a flexible network structure as the former requirements to have a BSC controlled by a single MSC server or SGSN lead to certain limitations. Allowing the BSCs to connect to a number of MSC servers increases the networks performance in terms of scalability, distributing the network load... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5.1.2 References specifying RANflex | Intra-domain connection of RAN nodes to multiple CN nodes (RANflex) has been added to the 3GPP standard in Rel-5. 3GPP Work Item: 3GPP Work Item = 2243 (IUFLEX) "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" Applicable Technical Specifications: TS 123 236 [i.6] |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5.2 Coexistence of VGCS/VBS and RANflex | |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5.2.1 Main concept | In railway operation the point-to-multipoint communication services Voice Group Call Service and Voice Broadcast Service (TS 143 068 [i.4] and TS 143 069 [i.5]) are frequently used. RANflex introduces redundancy of CN nodes while VGCS/VBS require a specific hierarchy for service and traffic plane control. So without fu... |
fa742d9028d9c2c0545129f7155d0c8e | 103 147 | 5.2.2 References specifying "Coexistence of VGCS/VBS and RANflex" | The enhancement for support of coexistence of VGCS/VBS and RANflex have been added to 3GPP Rel-7. 3GPP Work Item: 3GPP Work Item 7043 (VGCSFlex) "Interoperability between VGCS/VBS and A/Gb flexibility" Applicable Technical Specifications: TS 143 068 [i.4], TS 143 069 [i.5], TS 129 002 [i.3] Applicable clauses: The feat... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.