hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 5 Background | The IPCablecom architecture is an end-end broadband architecture that supports voice, video, and other multimedia services. The individual components that compose the IPCablecom architecture are defined in [i.3]. The OSS back office contains business, service, and network management components supporting the core busin... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7 Management Event Reporting Mechanism | The Management Event Mechanism and the associated Management Event MIB must be implemented on the MTA. The Management Event Mechanism and the associated Management Event Mechanism MIB may be implemented on any IPCablecom element such as the CMS, MGC, and others. |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.1 Event Notification Categories | All events delivered by (event mechanism document) fit into two main categories: • IPCablecom-specific • Vendor-specific IPCablecom-specific events are defined in the present document and referenced by concerned specifications whereas vendor-specific events are left to vendor implementation and are out of scope of the ... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.1.1 Event ID Assignments | • The EventID is a 32-bit unsigned integer. • IPCablecom-specific EventIDs must be defined in the range of 0x80000000 (decimal 2 147 483 648) to 0xFFFFFFFF (decimal 4 294 967 295). • Vendor-specific EventIDs must be defined in the range of 0x00000000 (decimal 0) to 0x7FFFFFFF (decimal 2 147 483 647). • Vendor-specific ... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.2 IPCablecom Management Event Format | The format of an IPCablecom Management Event is made up of the following information: • Event Counter - indicator of event sequence • Event Time - time of occurrence • Event severity - severity of condition as defined in clause 7.5 • Event Enterprise number - Vendor specific enterprise number • Event ID - determines ev... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.3 IPCablecom Management Event Access Method | The IPCablecom event access method is defined through the use of SNMPv3 in the case of local log access and trap or inform access. The SYSLOG uses UDP packets to convey the event data. For local event log access, an EMS may send SNMP GET, GET-NEXT or GET-BULK requests to the IPCablecom element, accessing rows of the lo... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.4 Management Event ID | IPCablecom management events are defined in an annex of IPCablecom specifications. Not all IPCablecom specifications define management events. Each management event described in the annex of an IPCablecom specification is assigned an IPCablecom Event ID. For a complete list of IPCablecom Event IDs, refer to annexes A a... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.5 Management Event Severities | Each event is assigned an initial (default) IPCablecom MultiMedia-centric Severity. The definitions for the IPCablecom MultiMedia-centric severities are loosely based on ITU-T Recommendation M.3100 [i.5] and OSI System Management Alarm Reporting Function X.733 [i.6]. IPCablecom expands on the definition provided in Tel... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.5.1 Changing Default Event Severities | The default event severity must be changeable to a different value for each given event via the SNMP interface. |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.6 Notification Mechanism | The notification mechanism for each event must be programmable via the SNMP interface. Each event must be able to be sent to one or more notification mechanisms. The notification mechanism definitions are as follows: • local: The event is stored locally on the device in which it is generated. The event can be retrieved... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.7 Local Log of Events | The MTA must support local logging of events. The local log must be accessed via SNMP using the objects defined in [1]. A vendor may provide alternative access procedures. The MTA may implement local logging either in volatile memory, non-volatile memory or both. The index provided in [1] provides relative ordering of ... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.8 Syslog | All Syslog messages sent by an IPCablecom eMTA must comply with the following requirements: • It must use UDP as the transport mechanism with 514 as the destination port as defined in clause 2 of the BSD syslog protocol [5]. • It should use port 514 as the source port, as recommended in clause 2 of SNMP applications [5... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.8.1 Syslog Message Format | This clause defines the usage of the Syslog fields as defined in clause 4 of [5]. |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.8.2 PRI Part of a Syslog Packet | For the PRI part defined in clause 4.1.1 the facility to use must be: 16 local use 0 (local0) The severity is the severity as indicated in the definition of the Event message (0-7). The 'Priority Code' is as defined in clause 4.1 and ranges between 128 and 135 for IPCablecom. |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.8.3 MSG Part of a Syslog Packet | The MTA must include the following components: TIMESTAMP, HOSTNAME, TAG and the CONTEXT where: • TIMESTAMP is the time recorded by the MTA (This must reflect the time in UTC as obtained from the Cable Modem). • HOSTNAME must be the hostname received by the MTA in Option 12 of the DHCP ACK. (Refer to [2] for more detail... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.9 Event Throttling | Throttling is implemented globally through a rate based threshold mechanism, as defined in the IPCablecom Management Event MIB [1]. Control of the throttling mechanism is through a MIB object that specifies one of four states. • Event generation inhibited - events defined through the event mechanism are no longer sent ... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 7.10 Severity and Priority Definition | Severity is the degree of failure related to a specific event by a reporting device. Telcordia document GR-474-CORE [i.4], Network Maintenance: Alarm and Control for Network Elements defines three degrees of severity: • Critical - Used to indicate a severe, service-affecting condition has occurred and that immediate co... |
0398a82475d224a1275357d60ec53c35 | 103 161-12 | 8 IPCablecom Management Event Data Template | In order to ensure multi-vendor interoperability of network management functionality, the specific meaning of IPCablecom management events are defined. Because the IPCablecom management events are based on conditions identified in IPCablecom specifications, management events are defined in the separate appendices of th... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 1 Scope | The present document defines rules of implementation for certain service information features. These rules have been developed to provide a reliable and consistent experience for digital radio listeners; they provide implementation details for how the Fast Information Channel (FIC) signalling is used and how receivers ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 2 References | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 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... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 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... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 3 Definition of terms, symbols and abbreviations | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 3.1 Terms | For the purposes of the present document, the following terms apply: alarm announcement: announcement of type 'alarm' which has elevated priority announcement: short audio message containing information categorized by an announcement type Change Event Indication (CEI): set of FIG fields with particular values to indica... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 3.2 Symbols | Void. ETSI ETSI TS 103 176 V2.5.1 (2026-02) 14 |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding AMSS Amplitude Modulation Signalling System ASu Announcement Support ASw Announcement Switching C/N Current/Next CA Conditional Access CAId Conditional Access Identifier CEI Change Event Indication DAB Digital Audio B... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 4 Overview | Service information (SI) in DAB is carried in the Fast Information Channel (FIC) as a series of Fast Information Groups (FIGs) carried in Fast Information Blocks (FIBs). Different FIGs are used for different service information, and several different FIGs may be needed to implement a particular service information feat... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5 Service following | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1 Introduction | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1.0 General | Service following is the term applied to maintaining the same audio or data content that the user has selected in spite of the varying reception conditions that occur, for example, when travelling by car or train. Many broadcast network topologies are possible, and the tuned service may be carried on an ensemble with m... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1.1 Service linking information | Service linking information, carried using FIG 0/6, allows the service provider to establish one or more sets of identifiers that carry identical, in the case of a hard link, or related, in the case of a soft link, content. The set of identifiers is called a linkage set. There may be several linkage sets that are valid... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1.2 OE Services | In order to assist the receiver, the service provider may signal a list of geographically adjacent alternative ensembles using FIG 0/24 on which the current and other services can be found. FM-RDS service PI = s DAB service(s) SId ≠ s FM-RDS service(s) DRM or AMSS service(s) DAB service(s) SId = s EId ≠ e DAB service(s... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1.3 Frequency information | In order to assist the receiver, the service provider may signal a list of alternative frequencies using FIG 0/21 on which the tuned ensemble and other ensembles may be found. FIG 0/21 may also signal frequency information for other bearers such as FM-RDS, DRM and AMSS. The receiver may use this information to identify... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.1.4 Country information, LTO and International Table | Service following requires receivers to compare identifiers. To ensure that DAB services are uniquely identified in all situations, the ECC shall be known. FIG 0/9 allows the ECC of each programme (audio) service to be provided (data services include the ECC in the SId). If all programme services have the same ECC, the... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2 Service linking | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.0 General | The FIG 0/6 consists of a header field and one or more service linking fields. The service linking fields can take the short form or the long form and this is determined by the state of the Id list flag. The database key for FIG 0/6 consists of the OE and P/D flags from the header field and the S/H, ILS, and LSN fields... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.1 Short form - Activation state and change event indication | The short form has the Id list flag set to 0. It is used for signalling the activation state of all the linkage sets signalled in the ensemble and to indicate that changes to the database content of a linkage set will be made. The C/N flag in the FIG 0/6 header is used to determine which type of information is being si... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.2 Long form - Database definition | The long form has the Id list flag set to 1. It is used to build up the database of identifiers that are linked together to form linkage sets. The C/N flag is used in the database definition mode and the flag indicates the start of the database definition when set to 0 or a continuation of the database definition when ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.3 Linkage sets | A linkage set is a collection of identifiers (DAB SIds, RDS PI codes, etc.) that correspond to alternative sources of the same content (hard link) or related content (soft link) - effectively a linkage set represents a particular transmission network configuration and so is essentially static. However, a particular ser... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.4 Signalling a link | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.4.0 General | There are different phases to signalling a link. Each linkage set is signalled as a FIG 0/6 database entry. It shall be defined using the long form, and activated and deactivated using the short form. A linkage set may be changed by signalling the CEI (short form) corresponding to the database entry and then redefined ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.4.1 Defining a linkage set | The transmission order list of the linkage set for the tuned ensemble is determined in the planning stage (see clause 5.2.3). The identifier list shall be divided into FIG 0/6s carrying service linking fields according to the following cases: Step A: a start of database FIG 0/6 (C/N = 0) contains a service linking fiel... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.4.2 Changing the linkage set | If the network configuration represented by a particular linkage set changes, then the transmission order of the linkage set for each ensemble shall be redetermined (see clause 5.2.3). The CEI is signalled at least once per second for a period of five seconds. The CEI is defined as the short form service linking field ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.4.3 Signalling the activation state of linkage sets | The activation state of all the linkage sets in the database shall be signalled at least every 10 seconds. This shall be accomplished by either repeating the definition of a linkage set at least every 10 seconds, or by signalling the activation state of the linkage set by using the short form of the service linking fie... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.5 Receiver behaviour for a link | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.5.0 General | When a receiver initially tunes to a particular ensemble, it shall begin to assemble the service linkage database entry associated with each database key- OE flag, P/D flag, S/H flag, ILS flag, LSN. Some linkage sets may be activated, others deactivated, as indicated by the LA flag for each database key. FIG 0/6 in the... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.5.1 Reaction to CEI | When the CEI is received, that is a FIG 0/6 in short form with the C/N flag set to 0, receivers are informed that the part of the linkage database corresponding to the database key - OE, P/D, S/H, ILS, LSN - is about to be changed or deleted. The database entry corresponding to the database key is deleted (if present) ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.5.2 Reaction to definition | Receivers shall begin to assemble the information when they receive a FIG 0/6 in the long form with the C/N flag set to 0, indicating the start of the database entry corresponding to the database key - OE, P/D, S/H, ILS, LSN. When P/D = 0 and ILS = 0, the Ensemble ECC provided in FIG 0/9 shall apply to all services in ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.2.5.3 Reaction to activation and deactivation | Reception of the short form of FIG 0/6 with the C/N flag set to 1 provides information on the activation and deactivation of defined linkage sets. The activation state of all linkage sets is transmitted every 10 seconds. When changes to the activation state take place, the activation state of the affected linkage sets ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3 OE Services | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.0 General | The FIG 0/24 consists of a header field and one or more OE Services fields. The OE Services fields can take the short form or the long form and this is determined by the state of the Number of EIds field. The database key for FIG 0/24 consists of the OE and P/D flags from the header field and the SId field from the OE ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.1 Short form - Change event indication | The short form has the Number of EIds field equal to 0. It is used for signalling changes to the database entry of the service indicated by the database key. The C/N flag is set to 0. ETSI ETSI TS 103 176 V2.5.1 (2026-02) 24 |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.2 Long form - Database definition | The long form has the Number of EIds field not equal to 0. It is used to build up the database of EIds that also carry the service indicated in the SId field. The C/N flag is used in the database definition mode and the flag indicates the start of the database definition when set to 0 or a continuation of the database ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.3 OE Services fields | The P/D flag determines the length of the SId field that corresponds with a service in the tuned ensemble when the OE flag = 0, or in another ensemble when the OE flag = 1. It is most probable that the information will change very infrequently with a network configuration change when a service is added to or withdrawn ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.4 Signalling | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.4.0 General | There are different phases to signalling. The database shall be defined (using the long form) and may be changed by signalling the CEI (short form) corresponding to the database entry and then redefined using the long form. Database changes should be kept to a minimum. Listeners may tune to an ensemble at any time and ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.4.1 Defining the database | The database is defined using the long form OE Services field. For each database entry there is a start of database FIG 0/24 (C/N = 0) containing an OE Services field, and, if all EIds do not fit into the FIG, one or more continuation of database FIG 0/24 (C/N = 1) containing an OE service field corresponding to the sa... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.4.2 Changing the database | When a database entry needs to be changed, the CEI is signalled at least once per second for a period of five seconds. CEI is defined as the short form OE Services field with the C/N flag set to 0 and the database key - the OE flag, P/D flag, and SId - defining which part of the database is being changed. The database ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.5 Receiver behaviour | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.5.0 General | When a receiver initially tunes to a particular ensemble, it shall begin to assemble the OE Services database entry associated with each database key- OE flag, P/D flag, SId. The receiver will never know that the database is complete, and a receiver should act upon the information in the database whenever it needs to. ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.5.1 Reaction to CEI | When the CEI is received, that is a FIG 0/24 in short form with the C/N flag set to 0, receivers are informed that the part of the OE Services database corresponding to the database key - OE, P/D, SId - is about to be changed or deleted. The database entry corresponding to the database key is deleted (if present) and t... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.3.5.2 Reaction to definition | Receivers shall begin to assemble the information when they receive a FIG 0/24 in the long form with the C/N flag set to 0, indicating the start of the database entry corresponding to the database key - OE, P/D, SId. The receiver shall watch for FIG 0/24 in the long form with the C/N flag set to 1, indicating a continu... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4 Frequency information | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.0 General | The FIG 0/21 consists of a header field and one or more Frequency Information fields. The Frequency Information fields can take the short form or the long form and this is determined by the state of the Length of Freq list field. The database key for FIG 0/21 consists of the OE and P/D flags from the header field and t... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.1 Short form - Change event indication | The short form has the Length of Freq list field equal to 0. It is used for signalling changes to the database content of the frequencies indicated by the Rfa, Id field and R&M field. The C/N flag is set to 0. |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.2 Long form - Database definition | The long form has the Length of Freq list field not equal to 0. It is used to build up the database of frequency information about DAB ensembles, FM-RDS or other services. The C/N flag is used in the database definition mode and the flag indicates the start of the database definition when set to 0 or a continuation of ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.3 Frequency information fields | For DAB ensembles, the OE flag is used to indicate whether the information applies to the tuned ensemble (OE flag = 0) or to another ensemble (OE flag = 1). For other bearers (FM with RDS, AM with AMSS, DRM), the OE flag is used to indicate whether the information applies to a service (primary service component) in the... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.4 Signalling | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.4.0 General | There are different phases to signalling. The database shall be defined (using the long form) and maybe changed by signalling the CEI (short form) corresponding to the database entry and then redefined using the long form. Database changes should be kept to a minimum. Listeners may tune to an ensemble at any time and t... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.4.1 Defining the database | The database is defined using the long form Frequency information field. For each database entry there is a start of database FIG 0/21 (C/N = 0) containing a Frequency information field, and, if all frequencies do not fit into the FIG, one or more continuation of database FIG 0/21 (C/N = 1) containing a Frequency infor... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.4.2 Changing the database | When a database entry needs to be changed, the CEI is signalled at least once per second for a period of five seconds. CEI is defined as the short form Frequency information field with the C/N flag set to 0 and the database key - the OE flag, P/D flag, and SId - defining which part of the database is being changed. The... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.5 Receiver behaviour | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.5.0 General | When a receiver initially tunes to a particular ensemble, it shall begin to assemble the Frequency information database entry associated with each database key- OE flag, P/D flag, Rfa, Id field and R&M field. The receiver will never know that the database is complete, and a receiver should act upon the information in t... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.5.1 Reaction to CEI | When the CEI is received, that is a FIG 0/21 in short form with the C/N flag set to 0, receivers are informed that the part of the Frequency information database corresponding to the database key - OE, P/D, Rfa, Id field and R&M field - is about to be changed or deleted. The database entry corresponding to the database... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.4.5.2 Reaction to definition | Receivers shall begin to assemble the information when they receive a FIG 0/21 in the long form with the C/N flag set to 0, indicating the start of the database entry corresponding to the database key - OE, P/D, Rfa, Id field and R&M ETSI ETSI TS 103 176 V2.5.1 (2026-02) 27 field. The receiver shall watch for FIG 0/21 ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.5 Transmission network examples | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.5.1 DAB/DAB service following | There is no such thing as a "standard" DAB network. Depending on very many variables, networks will be built that provide the radio services that are needed. Some examples are listed below. In all cases, it is essential that proper allocation of identifiers is made such that there are no conflicts of information within... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.5.2 DAB/FM-RDS service following | In order to allow receivers to continue to provide a service carried on DAB when moving beyond the digital coverage area, service providers with the same content available from FM-RDS can provide service following information. In general, FIG 0/6 is used to provide the linkage between DAB services and the corresponding... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.5.3 DAB/DRM service following | In order to allow receivers to continue to provide a service carried on DAB when moving beyond the DAB coverage area, service providers with the same content available from DRM can provide service following information. The services may be data services, as illustrated in clause A.10, or audio services as illustrated i... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6 Receiver reference model | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.0 General | Clause 5.6 describes a conceptual model of a receiver that implements service following according to these Rules of Implementation. The purpose of the model is not to specify a particular receiver implementation, but rather to define the expected behaviour of a conformant receiver. It is expected that real receivers ma... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.1 Reception monitoring | A mobile receiver shall provide a means to monitor the received signal. This may include one or more aspects of signal reception, such as signal strength, carrier-to-noise ratio, bit-error rates, etc. For each quality indicator a threshold level allows detection of a loss of signal. The decision circuit may include hys... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.2 Information base | To identify a suitable alternative service or frequency resource, a receiver can make use of various information sources. These may include service following information received through the FIC, learning memory and pre-stored data to build the information base. The information base consists of information elements com... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3 Service following procedure | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3.1 Overview | The service following procedure deploys a multi-stage algorithm to keep track of a selected service and signal and where this fails, to identify and select an alternative signal and/or service. The service following procedure is an automated routine controlling tuning and decoding units to maintain and (re-)establish a... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3.2 Stage 1: Find same service | In this stage, the receiver attempts to locate a DAB ensemble containing a service with ECC-SId equal to the Target Id. It may use FI (FIG 0/21) to find the same ensemble on another frequency; OE Services information (FIG 0/24) and FI to find another ensemble carrying the same service; and cached MCI and SI from previo... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3.3 Stage 2: Follow hard links | At this stage, the receiver has failed to select the Target Id on any DAB ensemble, or is seeking an alternate service because the selected service has a low preference level. The receiver attempts to find a service that is hard-linked to the Target Id and is therefore carrying identical audio content to the Target Id.... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3.4 Stage 3: Follow soft links | At this stage, the receiver has failed to select the Target Id on any DAB ensemble and has also failed to select an equivalent hard-linked service on DAB or other bearers. This means a service with the same audio content is not available. In this situation, a related service may represent the best alternative according... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.3.5 Handling of bearer system transitions | The service following procedure is designed to present the best available alternative to the user selected service. In the course of this procedure the alternative service may represent a significant departure from the initial user selection. The procedure shall be designed in a way that the receiver respects the initi... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.4 Selection procedure | If the user stores a service as a preset on the receiver (either mobile or domestic), and the service is not found when the user subsequently selects the preset, the receiver shall attempt all service discovery and linking methods to locate that service, or an alternative service advertising the preset service as a lin... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.5 Linkage sets | The receiver maintains a number of linkage sets as part of an information base used for service following decisions. Each linkage set contains the identifiers for a set of one or more services, possibly on different bearers, that are equivalent (hard linked) or related (soft linked). ETSI ETSI TS 103 176 V2.5.1 (2026-0... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 5.6.6 Linkage set management | The receiver obtains the linkage sets from information supplied by service providers and signalled in FIG 0/6. Figure 4 defines the process by which a receiver may obtain and manage all of the linkage sets transmitted on the tuned ensemble. ETSI ETSI TS 103 176 V2.5.1 (2026-02) 34 Figure 4: FIG 0/6 process tree Receive... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6 Service lists | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.1 Introduction | The efficient maintenance of the list of service elements that a listener may choose is an important aspect of the satisfaction that a user gains from using a digital radio. It is important that the options available to the listener are up to date, following the changing broadcast schedule, the roll-out of the transmis... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2 Managing ensemble changes | |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2.1 Describing an ensemble | A DAB ensemble carries a number of services, each of which has one (and only one) primary service component and may have one or more secondary service components. The current arrangement of the services carried in the ensemble is described by FIG 0/2 with the C/N flag set to 0 (Current). FIG 0/8 provides additional inf... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2.2 What is the service list | The service list is a feature of a digital radio receiver and the primary means for accessing, viewing and selecting all available services. An available service can be received at the place of the receiver with clear undisturbed audio. As a minimum the service list shall show all available service elements and provide... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2.3 Establishment of the service list | When a receiver is switched on for the first time, it has no entries in the service list. Generally, in this condition, the receiver will begin an automatic scan of all the DAB channels in the receiver's tuning range and look for DAB ensembles. As each ensemble is found, the receiver will discover new service elements ... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2.4 Maintenance of the service list | After the initial establishment of the service list, maintenance processes are required to ensure the user is able to select all available services and is not confused by services that are no longer broadcast. As the user tunes to different services, the receiver shall check its service list against the received MCI an... |
c7c0df506814d94b4397027b2531f0f8 | 103 176 | 6.2.5 Signalling conventions | SCI provides a means to provide information on ensemble changes ahead of time. For service elements being introduced or off-air temporarily, full MCI and labels is not available. Then SCI is the only means to discover a service element and it shall always be accompanied by an associated label. This will allow receivers... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.