hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.5 Verifying the availability of services at a client | When attempting to request one service to the DVB-HB Local Server, it is recommended that the DVB-HB Client checks beforehand the actual availability of the service, so that a potential unavailability could be handled with user friendly experience, e.g.: • Showing a logo with the currently unavailable service and an in... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.4.6 Reserving exclusive resources by a DVB-HB Local Server for a client | A DVB-HB Local Server may, with or without request, reserve a resource on exclusive basis. This may be especially the case if the DVB-HB Local Server detects that a DVB-HB Client is zapping quickly through services, or when the DVB-HB Local Server is proceeding with an update scan. A temporary exclusive assignment may ... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.6 Dependencies and backwards compatibility (informative) | Since in the ServiceAvailabilityMap.xml document the services are referred to using the same unique identifier (@serviceRef attribute) as in the corresponding DVB-I formatted Service List, only DVB-HB Clients and DVB-HB Local Servers supporting DVB-I formatted Service Lists can take advantage of the service availabilit... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.7 Implementation recommendations on client devices (informative) | |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.7.1 Broadcast-only mode | When switching amongst services (e.g. using P+/P- keys), it is a recommended that the DVB-HB Client does no skip the temporarily unavailable services but shows an info banner. This allows the user to keep orientation on his service list. This is also valid if the user explicitly selects the service by typing the corres... |
98d566ac142ee06783f646c81587b072 | 104 025 | 7.3.7.2 Client mode supporting DVB-HB and DVB-I services | The Service Availability Map feature only addresses availability of broadcast services, received at the DVB-HB Local Server front-ends and redistributed on the LAN. In case a specific service is flagged as currently unavailable due to lack of resources, a DVB-HB Client with also a broadband connection may use an Intern... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8 Extensions to SAT>IP specification | |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.1 Introduction | This clause defines the optional extensions to EN 50585 [1], applicable to Profile A DVB-HB Local Servers and Profile A DVB-HB Clients. |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.2 Support to DVB-S2X | The table in EN 50585 [1], clause 5.5.12 is extended as defined in table 5 below. Table 5: Query attributes for DVB-S, DVB-S2 and DVB-S2X signals Name Attribute Value Example Frontend identifier fe Numerical value between 1 and 65535. Not required in normal client queries. fe=1 Signal source src Numerical value between... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.3 Description of device capabilities | The "XML Device Description" defined in EN 50585 [1], clause 5.4 is extended with a <dvbhb:X_SATIP_DVBHB> element according to pseudocode 12 and table 6. Pseudocode 12: X_SATIP_DVBHB schema <complexType name="X_SATIP_DVBHB"> <sequence> <element name="ServiceListOffering" type="dvbi-types:ServiceListOfferingType" minOcc... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.4 Network resilience in Profile A | |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.4.1 Introduction | Audio/video content redistributed by a Profile A DVB-HB Local Server using UDP-based transport protocol, which does not support packet retransmission, may suffer from network packet losses, especially in case of wireless communication. While error protection mechanisms are provided as part of the relevant network stand... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.4.2 Optional AL-FEC | The optional AL-FEC which can be used in the transmission from a Profile A DVB-HB Local Server to a Profile A DVB-HB Client shall be according to the DVB Internet Protocol TeleVision (DVB-IPTV) specification as defined in ETSI TS 102 034 [12], Annex E. The presence of an AL-FEC layer shall be signalled by the DVB-HB Lo... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.4.3 Implementation considerations (informative) | Figure 5 describes the functional diagram of the AL-FEC generation included in a Profile A DVB-HB Local Server, showing the layers involved. It is part of the Network resilience (Tx) subfunction of the Content publication function in the DVB-HB reference architecture (see clause 5). ETSI ETSI TS 104 025 V1.1.1 (2024-07... |
98d566ac142ee06783f646c81587b072 | 104 025 | 8.4.4 Backwards compatibility (informative) | The DVB-IPTV AL-FEC consists of a Forward Error Correction (FEC) stream sent in parallel to the (untouched) media stream, on a different UDP port. Therefore, Profile A DVB-HB Clients not implementing this optional feature can decode the media stream simply ignoring the AL-FEC stream (of course without benefiting from t... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9 Extensions to the DVB-I specification | |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.1 Introduction | This clause defines the extensions to ETSI TS 103 770 [3], applicable to Profile B DVB-HB Local Servers and Profile B DVB-HB Clients. These extensions leverage the extensibility defined in ETSI TS 103 770 [3], and are therefore backwards-compatible with DVB-I Clients. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 45 |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.2 Extended Service List Entry Points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.2.1 Introduction | As described in clause 7.2, a Profile B DVB-HB Local Server shall expose basic information about itself in the form of an extended Service List Entry Points XML document. The HBxServiceListEntryPointsType defined in this clause extends the dvbisld:ServiceListEntryPoints element of ETSI TS 103 770 [3]. NOTE: Legacy DVB-... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.2.2 Extension to dvbisld:ServiceListEntryPoints | Based on extensibility of ServiceListEntryPointsType allowed by ETSI TS 103 770 [3], clause 5.3.2, the extension is defined according to pseudocode 13 and table 7. Pseudocode 13: HBxServiceListEntryPointsType schema <complexType name="HBxServiceListEntryPointsType" abstract="false"> <annotation> <documentation xml:lang... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.2.3 Example of use of the extended ServiceListEntryPoints | The example in pseudocode 14 describes an extended Service List Entry Points document published by a DVB-HB Local Server. Pseudocode 14: Example of an extended Service List Entry Points document published by a Profile B DVB-HB Local Server <?xml version="1.0" encoding="UTF-8"?> <!-- Example of ServiceListEntryPoints pu... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.3.1 Introduction | The Service List published by a DVB-HB Local Server can identify, per service, that the service provided originates from the DVB-HB Local Server tuners and not from an external source. This identification is achieved by means of <OriginalDeliverySource> element as defined in HBxDASHDeliveryParametersType, which extends... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.3.2 Extension to dvbisd:DASHDeliveryParametersType | Based on extensibility of DASHDeliveryParametersType allowed by ETSI TS 103 770 [3], clause 5.5.18.6, the extension is defined according to pseudocode 15 and table 8. Pseudocode 15: HBxDASHDeliveryParametersType schema <complexType name="HBxDASHDeliveryParametersType" abstract="false"> <annotation> <documentation xml:l... |
98d566ac142ee06783f646c81587b072 | 104 025 | 9.3.3 Example of use of the extended DASHDeliveryParametersType | The example in pseudocode 16 describes an extended DASH service instance published by a DVB-HB Local Server. Pseudocode 16: Example of extended DASH service instance published by a DVB-HB Local Server <?xml version="1.0" encoding="UTF-8"?> <ServiceList version="1" xml:lang="en" id="tag:dvbhb-local-server-manufacturer.c... |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.1 Introduction | The service list published by a DVB-HB Local Server in a DVB-I compatible format (be it a Profile A DVB-HB Local Server implementing this optional functionality or a Profile B DVB-HB Local Server) can be generated by the Service List publication function based on the DVB SI metadata according to ETSI EN 300 468 [18], c... |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.2 Service description | Table 9 lists the association of some of the fields of the SI Service Description Table (SDT) with the elements in the output DVB-I Service List. Table 9: Generation of DVB-I Service List elements from SI SDT fields DVB-I service discovery element SI table SI descriptor SI field Service.ServiceName (multiple service na... |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.3 Content Guide | |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.3.1 ScheduleInfo endpoint | A DVB-HB Local Server should support a Content Guide server functionality as defined in ETSI TS 103 770 [3], clause 6. A DVB-HB Local Server should host such Content Guide ScheduleInfo endpoint via the Web server subfunction of the Service List publication function. The endpoint URL should be included in the ServiceLis... |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.3.2 Example of Content Guide (present/following) | Pseudocode 17 shows an example of a query to the ScheduleInfo endpoint on present/following schedule, i.e.: <ScheduleInfoEndpoint>?sid=<service_id>&now_next=true Pseudocode 17: Example of result of a query to the Content Guide server (present/following) <?xml version="1.0" encoding="UTF-8"?> <TVAMain xmlns="urn:tva:met... |
98d566ac142ee06783f646c81587b072 | 104 025 | 10.4 LCN Tables, Subscription Package and regionalization | The DVB-I specification includes standardized LCN, regionalization and Subscription Package features [3]. A DVB-HB Local Server should be able to publish a DVB-I Service List in an ordered way by using these features. A broadcast Integrated Receiver Decoder (IRD) derives a selection of service instances, their order ba... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.1 Introduction | In case of Profile B, the interaction over the M_B reference point between the Service discovery and selection function of a DVB-HB Client and the Service List publication function of a DVB-HB Local Server (see also clause 5) is based on HTTP or HTTPS. The present document supports the delivery by the DVB-HB Local Serv... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.2 Background | The acronym HTTPS is used to reference HTTP over Transport Layer Security (TLS). TLS is a presentation layer protocol (Layer 6 of the ISO/OSI model), designed to provide a secure channel between two communicating peers (IETF RFC 8446 [i.4]). HTTP data is handled by TLS as agnostic application data payload (IETF RFC 911... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3 Enforcing security | |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3.1 Reliability of communication in the LAN | According to ETSI TS 103 770 [3], any communication between DVB-I Service List Providers and DVB-I Clients is required to use HTTPS except for the specific case of a Service List that a client obtains from a server located on the same private subnet. In that specific case, HTTP may be used. As a consequence, a DVB-HB L... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3.2 Combination of HTTP and HTTPS ("mixed content") | A DVB-HB Client loaded as HTTP (e.g. retrieved from the DVB-HB Local Server, or from a public web server) is allowed to fetch resources (e.g. the Service List, or DASH-delivered audio/video streams) either as HTTP or HTTPS. Instead, a browser-based DVB-HB Client loaded as HTTPS (e.g. from a public web server) is not al... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3.3 TLS certificates issued by the DVB-HB Local Server | This approach is also known as self-signed certificates and requires the DVB-HB Local Server to act as a private CA, possibly limiting this function to the home LAN environment and to the DVB-HB services. This approach, in fact, is typically used for closed groups and private services. The implementation details of thi... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3.4 TLS intermediate certificates with DDNS | This approach is known to be used by some existing client-server media player systems. Despite the higher security level offered (i.e. it uses publicly-trusted CA intermediate certificates), this method is more complex than the previous one and needs some extra prerequisites to be matched in order to work properly: • A... |
98d566ac142ee06783f646c81587b072 | 104 025 | 11.3.5 Private Network Access | As mentioned in clause 11.2, some modern browsers implement the Private Network Access specification [i.7], previously known as CORS-RFC1918, which restricts the ability of websites to send requests to servers on private networks, except those from secure contexts, in order to mitigate the risks associated with uninten... |
98d566ac142ee06783f646c81587b072 | 104 025 | 12 Guidelines on encoding and packaging (informative) | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.1 Introduction | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.1.1 General | The present clause attempts to provide some recommendations on how a DVB-HB Local Server can process the received audio and video bit streams to ensure interoperability with DVB-I Clients. DVB-HB Local Servers have limited resources, typically like any other consumer electronics products, i.e. processing power below PC... |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.1.2 A note on support of mobile devices | ETSI TS 101 154 [11], clause L.1 and clauses L.2.4 to L.2.17 define conformance points for mobile devices. These are very close to conformance points for broadcast services. Whilst these conformance points may be supported in many mobile devices, some other references [i.12] recommend other parameters to ensure interop... |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.2 Simple video repackaging without transcoding | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.2.1 Overview and limitations | Broadcast services that are encoded in Advanced Video Coding (AVC) or High Efficiency Video Coding (HEVC) can be repackaged without encoding since they are compliant with ETSI TS 101 154 [11], clauses L.1 and L.2.4. A DVB-HB Local Server can avoid transcoding and preserve the original broadcast quality by simply repack... |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.2.2 Parameters | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.2.2.1 Segment length | Broadcast services use a regular Group Of Pictures (GOP) structure with respect to RAP spacing, to enable fast channel switching. A GOP between two or more RAPs is suitable for segmentation. The maximal duration is rarely beyond 1- 2 s, however there is no exact prediction or rule on the duration. Table 13 shows a samp... |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.3 Transcoding and packaging | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.3.1 General | A pragmatic option may be to systematically transcode and repackage the incoming broadcast signal to ensure interoperability. In this case, [i.12] may be a suitable option for transcoding parameters. |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.3.2 Parameters | |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.3.2.1 Single or multiple representations | Optimizations exist for multiple bit-rate encoding [i.13] and [i.14]; however, a single representation is considered as enough to ensure interoperability with DVB-I Clients. Encoding and Signalling are defined in ETSI TS 101 154 [11], annex L and ETSI TS 103 285 [2]. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 59 |
98d566ac142ee06783f646c81587b072 | 104 025 | 12.3.2.2 Segment length | It is recommended that segment length corresponds to the duration of a GOP between two or more RAPs. This allows to encode separately segments and limit latency. For example, in case of broadcast MPEG-2 Standard Definition (Video) (SD) services, a GOP is fixed with 12 pictures, which leads to segments of 0,48 s or 0,96... |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 1 Scope | ...................................................................................................................................................... 11 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 2 References | .............................................................................................................................................. 11 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 2.1 Normative references | ....................................................................................................................................... 11 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 2.2 Informative references | ...................................................................................................................................... 14 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 3 Definition of terms, symbols and abbreviations | ..................................................................................... 14 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 3.1 Terms | ................................................................................................................................................................ 14 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 3.2 Abbreviations | ................................................................................................................................................... 16 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 4 General | ................................................................................................................................................... 17 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 4.1 Conventions | ...................................................................................................................................................... 17 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 4.2 Void | .................................................................................................................................................................. 17 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 4.3 Revision and compatibility handling | ................................................................................................................ 17 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 4.4 Namespace compatibility handling | .................................................................................................................. 18 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5 High level description | ............................................................................................................................ 18 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.1 Top level functional description, terminology, including hybrid, hierarchical | ................................................ 18 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.1.1 Architecture for O-RAN WG4 fronthaul functional split | ........................................................................... 18 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.1.2 M-Plane architecture model | ........................................................................................................................ 19 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.1.3 Transport network | ....................................................................................................................................... 20 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.1.4 M-Plane functional description | ................................................................................................................... 20 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.2 Interfaces | .......................................................................................................................................................... 21 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.3 YANG module introduction | ............................................................................................................................. 22 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 5.4 Security | ............................................................................................................................................................ 22 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6 "Start-up" installation | ............................................................................................................................. 24 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.1 General | ............................................................................................................................................................. 24 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2 Management plane transport aspects | ................................................................................................................ 27 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.1 Transport establishment | .............................................................................................................................. 27 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.2 O-RU identification in DHCP | ..................................................................................................................... 30 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.3 Management plane VLAN discovery aspects | ............................................................................................. 31 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.4 O-RU management plane IP address assignment | ....................................................................................... 31 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.5 O-RU controller discovery | .......................................................................................................................... 32 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.6 Certificate handling | ..................................................................................................................................... 33 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.6.0 Trust anchor provisioning | ..................................................................................................................... 33 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.6.1 Certificate enrolment | ............................................................................................................................. 34 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.6.2 CMPv2 based certificate enrolment | ...................................................................................................... 34 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.6.3 Operation with vendor-signed certificates | ............................................................................................ 35 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.2.7 Event-Collector discovery | .......................................................................................................................... 35 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.3 NETCONF call home to O-RU controller(s) | .................................................................................................... 36 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4 NETCONF connection establishment | .............................................................................................................. 39 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.0 General | ........................................................................................................................................................ 39 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.1 NETCONF security | .................................................................................................................................... 39 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.2 NETCONF authentication | .......................................................................................................................... 39 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.3 User account provisioning | .......................................................................................................................... 40 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.3.1 General | .................................................................................................................................................. 40 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.4.3.2 Certificates to NETCONF usernames mapping list provisioning | ......................................................... 41 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.5 NETCONF access control | ................................................................................................................................ 41 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.6 NETCONF capability discovery | ...................................................................................................................... 43 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.7 Monitoring NETCONF connectivity | ................................................................................................................ 44 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.8 Closing a NETCONF session | ........................................................................................................................... 47 ETSI ETSI TS 104 023 V12.01 (2024-05) 4 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.9 PNF registration | ............................................................................................................................................... 47 |
fdee9ac80b8378a9e0391b2084a424c1 | 104 023 | 6.9.1 Introduction | ................................................................................................................................................. 47 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.